A growing number of UK telehealth brands are asking whether pharmacogenomic testing belongs in their prescribing pathway, usually after a patient asks for it directly or a partner lab pitches it as a differentiator. The honest answer is that it can add real value in a handful of medicine classes, but it also brings a diagnostic-device question, a consent question and a data-handling question that most platforms have not worked through yet.

What pharmacogenomic testing actually checks

Pharmacogenomic (or pharmacogenetic) testing looks at specific genes known to affect how a person metabolises certain drugs, most commonly variants in CYP2D6, CYP2C19, CYP2C9 and SLCO1B1. A cheek swab or saliva sample is enough; no blood draw is required, which is one reason it appeals to remote and telehealth models.

It is a different service to the routine blood panels many clinics already offer for cholesterol, thyroid function or vitamin levels (see our guide to adding a blood testing service). A pharmacogenomic result does not diagnose a condition. It describes how quickly or slowly someone is likely to metabolise a class of drug, which a prescriber then weighs alongside the normal clinical picture.

Where it fits in a UK telehealth pathway

The clearest use cases sit in a small number of drug classes: certain antidepressants processed through CYP2C19, some cardiovascular medicines including clopidogrel and statins, and a handful of specialist oncology and pain pathways where NHS services already use genotyping selectively. Outside those classes, the evidence for changing a prescribing decision is thinner, and a telehealth brand should be candid with patients about that rather than marketing testing as a universal upgrade.

Testing works best as an optional add-on inside an existing consultation pathway, not as a stand-alone product. The prescriber still needs a full history and, where appropriate, examination or safety-netting before any decision is made; prescriber discretion applies to how, or whether, a pharmacogenomic result changes the outcome. A test result that arrives without that context is close to useless.

The regulatory classification question

A genetic test used to inform a clinical decision is usually an in vitro diagnostic medical device (IVD) under UK medical device law, which the MHRA oversees. That matters for procurement: the kit and the laboratory process behind it need a valid UK conformity marking and a traceable chain from sample to report, not just a plausible-looking result PDF.

Genetic data also carries its own weight under UK GDPR. The ICO treats genetic data as a special category in its own right, alongside health data, which means the lawful basis and Article 9 condition for processing it need to be worked out before the first sample is collected, not after (our UK GDPR for telehealth piece covers the lawful-basis mechanics in more depth).

For clinics

Curious how PExpo could fit your workflow?

Key takeaway

Pharmacogenomic testing changes how a prescriber weighs a decision. It does not replace the consultation, the consent process, or the dispensing record that has to sit behind it.

Consent for a genetic test needs to cover more ground than consent for a standard blood test. Patients should understand what happens to the physical sample after analysis, how long the genetic result is retained, whether it could be re-interpreted for other medicines in future, and that a result can carry implications for blood relatives even though only one person was tested.

A consent process that holds up in practice tends to cover the same ground each time:

Choosing a lab partner

Most telehealth operators will not run their own genetic laboratory; they will contract one. UKAS accreditation is the baseline check, but it is worth going further: ask how the lab validates each assay, what its turnaround time actually looks like at volume rather than on a sales sheet, and how disputed or unclear results are escalated, and whether the lab has experience supporting UK prescribers rather than only direct-to-consumer customers.

The practical integration question is usually bigger than the clinical one. A report that lands as a static PDF in an inbox does not scale; a partner that can push structured results into the existing patient record through an API, in the same way other lab and dispensing integrations already do, is the difference between a pilot and a real service line, especially once volume moves past a handful of requests a week.

For white-label brands

Ready to talk to sales about launching?

A genetic result is evidence, not an instruction. Every telehealth operator we have seen get this right treats it exactly that way.

What prescribers actually do with results

Results are usually reported as a metaboliser status, poor, intermediate, normal, rapid or ultrarapid, for each gene tested. None of those categories tells a prescriber what to do on their own. They adjust the weight given to a starting dose, a drug choice within a class, or the intensity of monitoring, but the prescriber's clinical judgement and the patient's own history still lead the decision.

Where a result changes a prescribing decision, that reasoning should be documented in the same way any other clinical judgement is, and any resulting adverse reaction should still be reported and handled through the standard pharmacovigilance process (our adverse event management guide covers that workflow).

Where PExpo fits

PExpo does not manufacture or interpret genetic tests, and a white-label brand or clinic should be wary of any platform that blurs that line. What PExpo's regulated dispensing layer is built for is the part that comes after a result and a prescription decision: GPhC-governed dispensing, an auditable record connecting the test, the consultation and the medicine dispensed, and the same superintendent pharmacist oversight that applies to every other prescribing pathway on the platform, and the same escalation routes if something about a result looks wrong.

For a brand or clinic weighing whether pharmacogenomic testing belongs in their offering, the more useful question is usually not whether they can build this, but who already does the diagnostic-device and lab-accreditation part properly, so the team can focus on the consultation and the dispensing. That is the partnership model most operators land on, and it tends to be the faster route to a defensible launch as well as the safer one.

Pharmacogenomic testing is not a mass-market feature yet, and it does not need to be treated as one. Where it does add value, in a handful of well-evidenced drug classes, it belongs inside an existing consultation and dispensing pathway rather than bolted on as a novelty. Brands weighing this decision alongside other white-label platform choices, and clinics comparing it with more established clinic dispensing services, should start from the same place: get the regulatory and consent groundwork right before the marketing page goes live.

Frequently asked questions

Is pharmacogenomic testing the same as a genetic diagnostic test?

No. Pharmacogenomic testing looks at how a person's genes affect drug metabolism, not whether they have a disease or condition. It is used to inform dosing and drug choice within a small number of medicine classes, alongside a full clinical assessment, not as a diagnosis on its own.

Do UK telehealth clinics need special regulatory approval to offer pharmacogenomic testing?

The test kit and laboratory process typically need to meet UK in vitro diagnostic medical device requirements overseen by the MHRA, and genetic data processing needs its own lawful basis under UK GDPR because the ICO treats it as special category data. Most operators partner with an already-accredited laboratory rather than building this themselves.

Can a pharmacogenomic result override a prescriber's decision?

No. A result adds evidence about how a patient may metabolise a drug, but the prescriber still makes the final decision based on the full clinical picture, and prescriber discretion applies throughout. The result should be documented as part of that reasoning, not treated as an automatic instruction.