What telehealth platforms should ask before adding lab testing
Before adding lab testing, a telehealth platform should answer eight questions: who orders the test, which states you can serve, how patients collect samples, how specimens reach the lab, where results land, who acts on abnormal values, how patients see results, and which privacy rules apply. The answers shape your product, not just your vendor choice.
Our earlier guide on how to choose a white-label lab testing partner covers how to vet a lab. This one starts from the other side: your own platform. Most telehealth lab programs that stall don't fail at the lab bench. They fail in the hand-offs between a virtual visit, a kit, a return box and the patient's chart.
This article is educational only, not legal or medical advice. Work through the regulatory points with your own counsel and clinical leadership.
Start by mapping the patient journey
Before you compare labs, sketch every step a lab order will touch on your platform:
Intake or visit, where a clinician decides testing is needed
The order, and the requisition that goes with it
Sample collection, at home or at a draw site
Specimen return to the lab
Testing and resulting
Clinician review
The patient conversation, and any reorder or follow-up
For each step, write down which system owns it, who on your team watches it, and what happens when it breaks. The eight questions below fill in that map.
1. Who is the ordering provider?
Under CLIA, a lab must have a written or electronic test request from an authorized person, and the requisition has to identify that person and give a contact for urgent results (42 CFR 493.1241). State law decides who counts as authorized.
For a telehealth platform, that raises practical questions:
Do your own clinicians order in their name, or does a partner physician network act as the ordering provider?
Is the ordering clinician licensed in the state where the patient lives?
Who is the named contact if the lab calls with an urgent result outside business hours?
2. Which states can you actually serve?
State coverage has two layers. Your clinicians need to be licensed where patients are, and some states also regulate the out-of-state labs that test their residents' specimens. New York is the best-known example: only labs holding a New York State clinical laboratory permit may test specimens that originate there, according to the state's Clinical Laboratory Evaluation Program.
Build a simple state matrix where clinician coverage, lab licensure and shipping all line up. Ask any lab for its CLIA number and full license list. For example, IHDLab is CLIA-certified (05D2040304) and licensed in California, New York and Maryland. A lab you're considering should be able to give you a list like that just as quickly.
3. How will patients collect the sample?
Most telehealth programs choose from three collection routes:
At-home kits: fingerstick capillary blood, dried blood spot cards, urine or swabs, collected by the patient and mailed back
Mobile phlebotomy: a trained phlebotomist draws blood at the patient's home or office
Draw sites: the patient visits a patient service center for a venous draw
Each test is validated for specific specimen types, so not every test on a lab's menu can come from a fingerstick. Ask for each test's approved specimen types before you design a panel. Then plan for recollection: some home samples will arrive with too little volume or missing labels, and your support team needs a script and a reship process for those.
Clear, illustrated patient instructions do as much for sample quality as anything that happens inside the lab.
4. How do specimens get to the lab?
Specimen logistics is where many programs lose time. Confirm these details before launch:
Who stores kit inventory, and who ships kits to patients
Return packaging and prepaid labels that meet carrier rules for clinical specimens
How long each specimen type stays stable between collection and receipt
Which days the lab receives packages, so patients aren't told to collect right before a weekend or holiday
Tracking in both directions, visible to your support team
5. Where do results land?
Results can reach your platform in three main ways: structured data through an API, an interface into your EMR, or a secure portal and PDF report. Structured data lets you trigger workflows, like flagging a result for review or prompting a follow-up visit. A PDF mostly gets read.
Whatever the route, ask how the lab reports units and reference ranges, corrected results and rejected specimens. CLIA requires the test report to note specimens that didn't meet the lab's acceptability criteria (42 CFR 493.1291), and your platform needs somewhere to show that note. For a closer look at the options, see how lab ordering and results integrations can work through an API, an EMR or a portal.
6. Who acts on abnormal and critical results?
The same CLIA section requires a lab to immediately alert the person who requested the test when a result shows an imminently life-threatening condition, or panic or alert values. That alert needs somewhere to go. Before launch, name:
An on-call clinician and a phone line that someone actually answers
A documented escalation path for critical values, including nights and weekends
A review window for non-urgent abnormal results, and who contacts the patient
7. How will patients see their results?
Decide whether patients see results before or after a clinician reviews them, and what the message says. Keep in mind that patients have rights here. HIPAA gives individuals a right to access their health information from covered entities (45 CFR 164.524), and CLIA lets labs release completed reports directly to a patient who asks.
Good patient communication usually includes:
Status updates when the kit ships, arrives at the lab and has results ready
Plain-language explanations alongside the numbers
A clear next step, such as booking a follow-up visit
8. Which privacy rules cover each party?
If your platform is a HIPAA covered entity, vendors that handle protected health information on your behalf generally need a business associate agreement. HHS publishes sample business associate agreement provisions as a starting point. A clinical lab is often a covered entity in its own right, so map who is responsible for what.
Not every wellness platform is covered by HIPAA. For health apps that aren't, the FTC's Health Breach Notification Rule may apply. Draw your data flows on one page and review them with privacy counsel.
A pre-launch checklist
An ordering provider model, with state licenses mapped
A state matrix covering clinicians, lab licensure and shipping
Approved specimen types for every test in each panel
Kit storage, shipping, return and recollection processes
A results route into your platform, plus handling for rejected specimens
A 24/7 contact and escalation path for critical values
Patient messaging for every status change
Business associate agreements, or a documented reason you don't need them
Then run a small pilot, in one state or with internal staff, before a full launch. Track kit return rates, recollections, time from order to result and support tickets. The pilot will surface the hand-offs your map missed.
The bottom line
Adding lab testing to a telehealth platform is mostly an operations project. The lab's job is accurate testing. Your job is making sure every order, specimen and result has an owner. If you're mapping a program now, our lab partner for telehealth platforms page shows how kits, testing and results routing can sit with one lab.
