top of page

FOR DIGITAL HEALTH PARTNERS AND DEVELOPERS

top

LabFlow: the lab testing API and EMR integrations for digital health partners

LabFlow connects your platform to IHDLab's CLIA-certified lab in Irvine, California. One REST integration covers ordering, kit fulfillment, status tracking and structured results, and clinics can connect through their EMR instead. IHDLab works B2B only, with telehealth companies, digital health brands, clinics and research teams.

labflow-hero-handdrawn_edited.png

Three ways to connect

EMR integrations

Clinics and practices can order from the EMR they already use. IHDLab connects to EMRs including Athena, eIVF, Practice Fusion, Office Ally, MediTab, eClinicalWorks, PrognoCIS and nAble. Most connections are bi-directional, which means orders go out and results come back through your EMR. A few are results-only. New EMR connections are available with 30 to 60 day build times. Clinic setting up a new account? See our reference lab services for clinics.

​

Bi-directional (orders and results)

Athena, eIVF, Practice Fusion, Office Ally, MediTab, Emdeon (Change Health Care), nAble, Artisan via Change Health Care, eClinicalWorks, PrognoCIS

​

Results only

GeniusDoc, AdvancedMD via EllKay, Elation, AmazinCharts via Harris

​

In progress

GreenWay Intergy, Mac Practice, AllScripts

The table below lists each current connection and its turnaround time. New EMR connections are available with 30 to 60 day build times.

​​

What the LabFlow API does

  • Create orders: kit orders, where IHDLab builds and ships the collection kit, or lab orders, where you supply the kit or specimen.

  • Ship kits: from our in-house 3PL, as IHDLab or white-label (your brand) kits, shipped overnight.

  • Register kits and record specimen receipt, so orders move into testing.

  • Track status: shipment, receipt, rejection with a reason, cancellation and result.

  • Receive results: observations with values, reference ranges and interpretation.

  • List ordering providers set up for your organization.

How an order moves from API call to result

2. Kit fulfillment or specimen intake

We kit and ship the order, and shipment updates come back as status events. In California, patients can also visit an IHDLab patient service center.

3. Testing in our CLIA lab

Specimens come straight to our CLIA-certified lab in Irvine. If a specimen can't be run, you get a rejection status with the reason.

1. Create the order

Your platform sends the patient, recipient and ordering-provider details. LabFlow returns an order ID.

4. Results to your platform

You get a v3 inbox flag or a signed v4 order.resulted webhook, then fetch the full result.

Partner API v3 and v4

​

v3 (default): REST with inbox polling

  • Authenticate with your organization's x-api-key.

  • Poll GET /v3/inbox, then GET /v3/order/{id}.

  • Covers kit orders, lab orders, kit registration, cancellation, kit lookups and provider lists.

​

v4 (opt-in per organization): FHIR-aligned JSON and webhooks

  • Field names are aligned to HL7 FHIR R4: ServiceRequest, Specimen, DiagnosticReport, Observation, Patient and Practitioner.

  • Register HTTPS endpoints for events: order.created, order.registered, order.status.changed, order.shipment.updated, order.received, order.rejected, order.resulted and order.cancelled.

  • Each delivery is signed with HMAC-SHA256 plus a timestamp, carries an event ID for de-duplication, and is retried automatically (about 5 min, 15 min, 1 h, 4 h, then every 12 h, up to 10 attempts).

  • The event log can be replayed for reconciliation.

  • v3 and v4 share one key and can run side by side while you migrate.

Tests you can order through the API

​

The same API serves every program we support, with 250+ home-collection test options and custom panels.

​

​

Security and compliance

​

  • CLIA-certified lab: CLIA 05D2040304, California license CLF00342268, FDA registration FEI 3011213917, and New York and Maryland licenses.

  • Every request is authenticated with an organization API key. Keys are issued through a one-time onboarding link and managed in the IHD admin portal.

  • v4 webhooks are signed with HMAC-SHA256 plus a timestamp. Endpoints must use HTTPS, and signing secrets can be rotated.

  • A separate staging environment with mock results tailored to your panel.

  • A HIPAA-compliant results portal.

​

​

Developer onboarding

​

  1. Request access: tell us about your program, test menu and expected volume.

  2. Get a staging key: we send a one-time link to your staging key and set up mock results that match your panel.

  3. Build and test with the API reference and the open-source example app (github.com/ihd-lab/labflow-example, React/JavaScript).

  4. Choose notifications: start with v3 polling, or ask us to enable v4 webhooks.

  5. Go live: switch to your production key.

faq

Build lab testing into your product.

Request sandbox access, or book a technical demo with the IHDLab team.

bottom of page