---
url: "https://dfylegitscript.com/blog/at-home-testing-and-medical-devices-in-a-telehealth-catalogue"
title: "At-home tests and devices, and the questions they add to a file"
description: "A telehealth catalogue containing a laboratory panel or a home test kit adds four questions to a LegitScript application that a medicines-only file never faces: which laboratory runs it, who is licensed to order it, who interprets the result, and what the marketing promises the number means."
published: "2026-06-18T12:58:22+00:00"
modified: "2026-06-18T12:58:22+00:00"
---

# At-home tests and devices, and the questions they add to a file

A telehealth catalogue containing a laboratory panel or a home test kit adds four questions to a LegitScript application that a medicines-only file never faces: which laboratory runs it, who is licensed to order it, who interprets the result, and what the marketing promises the number means.

## Key takeaways

- A laboratory panel or a home test adds four questions per test: which laboratory runs it, who orders it, who interprets the result, and what happens when it is abnormal.
- Numbers feel objective, which is precisely why marketing a result is treated as a claim about what that number means for the patient reading it.
- Reference ranges drawn so that almost everybody qualifies for treatment are the pattern a reviewer looks for in this category.
- Kits add operations that become findings: shipping, temperature, chain of custody, and a result arriving when nobody is on duty to act on it.

Testing has become standard in direct-to-consumer telehealth. A panel to qualify
a patient, a home kit to monitor progress, a device to track something the
treatment is meant to change. Each is a sensible clinical addition and each adds
a category of question to an application built around medicines.

## Four questions, per test

**Which laboratory performs it?** Named, with its certifications, and with the
relationship to your business stated. A brand that cannot name the lab behind
its own panel has the same gap as one that cannot name the pharmacy behind its
own preparation.

**Who orders it?** Ordering a laboratory test is generally a clinical act, which
makes it a licensure question in the patient's state. A model where the patient
buys a test with no clinician involved needs describing accurately rather than
implied to be clinician-led.

**Who interprets it, and against what?** A named clinician, or an algorithm, or
a reference range the brand chose. Where the brand sets its own thresholds for
what counts as low or optimal, that is a claim, and it belongs in the file
alongside the basis for it.

**What happens to an abnormal result?** Particularly one unrelated to the
treatment being sought. A model with no route for that is describing a
qualification step rather than a clinical service.

## The marketing problem specific to numbers

A test result feels objective, which makes claims built on it feel like facts.

The patterns that draw attention: presenting a result as a diagnosis, defining a
range as optimal without saying whose definition it is, promising that a
treatment will move a number, and implying that a number outside a chosen range
requires treatment.

That last one is the structural version, and it is the same problem as an intake
that always says yes. A testing model whose thresholds are drawn so that almost
everyone qualifies is describing a marketing funnel with a blood draw in it, and
[whether the prescribing decision is real](/blog/asynchronous-intake-and-the-clinical-encounter-under-review)
is the question underneath.

## Devices are a different regime again

A wearable, a monitor, a diagnostic kit or an applicator sold by a telehealth
brand carries its own regulatory classification, and that classification decides
what may be said about it.

The practical questions: what the device is classified as, who manufactures it,
whether your marketing describes it within what its classification supports, and
whether it is being sold or provided as part of a service. Brands that add a
device to a subscription frequently describe it in outcome language the device
itself has never been assessed for.

## Where the data goes

Test results and device data are health information, and the tracking discussion
that applies to intake pages applies with more force here.

A result page carrying an advertising pixel, a dashboard shared with an
analytics tool, a device integration passing readings to a third party: each is
a disclosure route, and each is visible to anybody reading your site the way
[the tracking on your intake pages](/blog/tracking-pixels-and-patient-data-on-a-telehealth-site)
describes.

## What a reviewer will want established

- The laboratory, its certifications, and the contractual relationship.
- Who orders tests and under what licensure, per state.
- Who interprets results, and the basis for the ranges used.
- The route for abnormal or incidental findings.
- The device classification and manufacturer for anything sold.
- What the marketing claims about the numbers, read against all of the above.

None of that is exotic and most of it exists somewhere in the business. What is
usually missing is that it exists in one place, which is the whole argument for
[assembling the file as a document](/blog/what-a-complete-legitscript-application-file-looks-like).

## The logistics nobody plans for

Testing adds physical operations to a business that may have had none, and the
operational gaps become compliance questions.

A kit has to reach the patient, be collected correctly, be returned within a
window and be traceable to the right person. Each of those steps can fail, and
the failure modes are patient-facing: a sample rejected by the laboratory, a
result attached to the wrong record, a kit that arrived after the treatment
decision was already made.

Have an answer for each. What happens when a sample is rejected, who tells the
patient and who pays for the replacement. How identity is verified so a result
belongs to the person it is recorded against. How long a result stays valid for
the purpose you use it for, since a panel from a year ago is not evidence about
a patient today.

That last one is worth stating on the site as well as in the file, because a
model that qualifies patients on stale results is qualifying them on
something else.

## The bundling trap

Testing is often bundled with treatment as a package, which merges two things a
reviewer would rather see separately: a clinical assessment and a product sale.

Where the test genuinely qualifies the patient, price and present it as part of
the assessment, and be clear that the assessment may end in a decline. Where it
is a monitoring add-on, present it as one. The version that reads badly is a
bundle in which paying for the test is functionally paying for the medicine,
because it describes a purchase with a clinical formality attached.

## The short version

Testing improves most telehealth models and it adds a licensure question, an
interpretation question and a claims question to the file. Answer all three in
writing before you file, and make sure the marketing describes what the numbers
actually mean rather than what they need to mean for the funnel to convert.

## Frequently asked questions

### Do I need to name the laboratory that runs my panels?

You need to be able to. A reviewer will want the laboratory, its certifications and its relationship to your business, in the same way they want the dispensing pharmacy named as an entity rather than as a brand.

### Can a patient order a test without a clinician involved?

Ordering a laboratory test is generally a clinical act, so it raises a licensure question in the patient's state. Whatever your model does, the website has to describe it accurately rather than implying clinician involvement that does not happen.

### Is it a problem to set our own reference ranges?

It is a claim, so it needs a basis you can state. Ranges drawn so that nearly every patient qualifies for treatment describe a funnel rather than an assessment, and that is visible from the marketing without anyone auditing the clinical logic.

## Disclaimer

LegitScript is a trademark of LegitScript LLC. VeriScripts is an independent application-preparation service. It is not affiliated with, endorsed by, or certified by LegitScript LLC, and claims no sponsorship or partnership with it. We prepare, submit, and manage the application; LegitScript alone decides whether certification is granted. "LegitScript" is used here only to name the certification these applications are for.