top of page

Lab-ordering API vs white-label kits: which fits your digital health program

Nov 9
5 min read
Illustration of an opened at-home lab test kit with tubes and a return mailer connected by data lines to a laptop showing a network diagram and code, in navy and pink

A lab-ordering API fits digital health programs that already own the patient experience and have engineers to connect orders, kit shipments and results to their own app. White-label kits fit programs that want a branded at-home test live quickly without building logistics. Many teams combine both: branded kits, ordered and tracked through an API.


The choice isn't really about technology. It's about who owns each step between "a clinician orders a test" and "a patient sees a result," and how much of that your team wants to build, brand and run. This guide compares the two models so product, operations and clinical leads can decide what fits their program today.


It's educational only, not legal, technical or medical advice.



What each model actually is


A lab-ordering API is a software connection between your platform and a lab. Your system sends orders, and the lab's system returns order IDs and status updates and, eventually, results. Typical requests include creating a kit order (the lab ships a collection kit to the patient), creating a lab order for a specimen collected another way, looking up an order and canceling it.


White-label kits are at-home collection kits that carry your brand: box, instructions and requisition. The lab or its fulfillment partner assembles, stores and ships them, and patients mail specimens back for testing.


These aren't opposites. An API is how orders and data move. A white-label kit is what the patient holds in their hands. If you're still choosing between manual, portal and API ordering, start with our comparison of lab ordering methods, then come back to this decision.



Six questions that decide the fit



1. Who owns the patient experience?


With an API, your app is the front door. Patients order, track their kit and see results inside your product, and the lab stays in the background.


With white-label kits alone, the box carries your brand, but status and results may live in a lab portal or arrive as reports your team has to pass along. That works for many programs, but your experience has more seams.



2. How much engineering can you spare?


An API needs real work:


  • Mapping your patient, provider and test data to the lab's order format

  • Handling order statuses, rejections and cancellations

  • Storing results securely and showing them to clinicians and patients

  • Testing against a sandbox or test mode before going live


A white-label kit program can launch with little or no code if orders come through a portal or a bulk order form. The work shifts to design, artwork approvals and inventory planning.



3. How fast do you need to launch?


If launch speed matters most, a white-label kit ordered through a portal is usually the shorter path, because there's no integration to build and test. An API takes longer up front but removes manual steps later. Many teams pilot with kits and a portal, then add the API once volume justifies the build.



4. Who handles logistics and fulfillment?


Kits involve physical work: sourcing collection components, assembling boxes, storing inventory, shipping to patients and providing a return mailer. Return packaging has to follow mailing rules for patient specimens. USPS Publication 52, section 346 sets packaging requirements for mailable specimens, including exempt human specimens and dried blood spots.


An API doesn't remove this work. It just tells someone else to do it. Ask whether your lab handles kitting and fulfillment itself or relies on separate vendors, and who owns a kit that is lost, damaged or returned unusable.



5. How will you scale?


At low volume, a coordinator can key orders and forward results. At hundreds of orders a week, retyping becomes a source of errors and delays. CLIA rules require labs to work from a written or electronic test request with specific details, such as the ordering provider, patient identifiers, tests and collection date, and to transcribe order information accurately (42 CFR 493.1241). An API passes those fields system to system, which is a large part of why it scales better.



6. Where are your patients?


Two separate questions apply. Can the kit reach the patient, and can the program legally serve them? Clinicians ordering through telehealth generally need to be licensed where the patient is located, as Telehealth.HHS.gov explains. Labs face their own state rules. New York, for example, requires a state permit for labs that test specimens from New York. Confirm both before you promise coverage in a new state.



Results and data routing


Whichever model you choose, results go back to the ordering clinician first. Under CLIA, labs must send results promptly and accurately to their final destination and must alert the ordering party right away about results in a panic or alert range (42 CFR 493.1291).


Plan for:


  • Where results land: your app, a lab portal or a downloadable report

  • Who reviews abnormal results, and how quickly

  • How corrected reports are handled

  • What data format your systems expect. Standards such as HL7 FHIR define common structures for orders and diagnostic reports, but ask each lab exactly what it returns rather than assuming.


Results usually take about 24 to 72 hours after the lab receives the specimen, depending on the test. Transit time comes on top of that.



When an API fits best


  • You already have a patient app and a clinician workflow

  • You expect steady or growing volume

  • You need order status inside your product, from shipped to resulted

  • You have engineering capacity to build and maintain the integration



When white-label kits fit best


  • Your brand needs to be on the box and in the patient's hands

  • You want to launch a test program quickly

  • Volume is still modest or seasonal

  • Your team would rather manage partners than code



When to combine both


Most mature programs end up here. Patients receive a branded kit, your platform places the order through the API and tracks it, and results flow back to your clinicians. The trade-off is that you carry both workloads: kit design and inventory, plus an integration.


A phased path keeps risk low:


  1. Launch branded kits with portal or form ordering.

  2. Measure volume, error rates and staff time per order.

  3. Build the API integration once manual work starts to cost more than the build.

  4. Move status and results into your own app.



Questions to ask a lab partner


  • Do you assemble, store and ship kits yourselves, or through other vendors?

  • What can your API do today: kit orders, lab orders, status tracking, cancellations?

  • Is there a test mode for simulating resulted and rejected orders?

  • Which states can you ship kits to, and which state lab licenses do you hold?

  • How do you handle rejected specimens and recollections?


For reference, IHDLab is a CLIA-certified (05D2040304) lab licensed in California, New York and Maryland that ships at-home kits to all 50 states and works B2B only. Its white-label test kits and LabFlow integrations pages show how the two models can work together.

bottom of page