What is the difference between reactive and pre-emptive pharmacogenomic testing?

Reactive testing is ordered for a specific drug decision at the moment it arises, whereas pre-emptive testing genotypes a panel in advance and stores the results so they are available whenever a relevant drug is later considered.

Why is clinical decision support emphasized in implementation?

Because a stored genotype is only useful if the right interpretation reaches the prescriber at the right time; embedding alerts and recommendations in the electronic health record is how many programmes deliver that information at the point of care.

Pharmacogenomic Testing and Clinical Implementation

Pharmacogenomic testing measures a patient's genetic variants in genes relevant to drug response, and clinical implementation is the work of turning those results into usable information at the point of prescribing. This topic covers how pharmacogenomic tests are performed and reported, how results are translated into predicted phenotypes, and what is required to deliver that information reliably within health systems.

Definition

Pharmacogenomic testing is the laboratory determination of an individual's genotype for pharmacogenes; clinical implementation is the set of processes — interpretation, guideline mapping, decision support, and delivery — that make those results actionable in routine care.

Scope

The entry covers the molecular diagnostic methods used for pharmacogenomic testing, the distinction between reactive (single-gene, on-demand) and pre-emptive (panel, results stored ahead of need) testing, the translation of genotype to phenotype and clinical recommendation, and implementation infrastructure such as clinical decision support. It is a reference overview and does not direct testing or prescribing for individuals.

Core questions

How are pharmacogenomic variants measured and reported?
When is reactive testing preferable to pre-emptive panel testing?
How is a genotype translated into a phenotype and a prescribing recommendation?
What infrastructure is needed to deliver results at the point of care?

Key concepts

Genotyping versus sequencing assays
Targeted variant panels
Reactive versus pre-emptive (panel) testing
Genotype-to-phenotype translation tables
Clinical decision support integration
Result portability and reporting standards
Test validity and clinical utility

Mechanisms

Most pharmacogenomic tests interrogate a defined set of known variants by targeted genotyping, though broader sequencing is increasingly used; results are commonly reported as a diplotype and an inferred metabolizer or functional phenotype. Implementation links that phenotype to a peer-reviewed guideline recommendation and, in mature systems, surfaces it through electronic clinical decision support so the information reaches the prescriber when a relevant drug is ordered. Because a genotype is stable over a person's life, pre-emptive panel testing stores results for future use, whereas reactive testing addresses a single drug decision at the time it arises (Swen et al., 2011; Wang, McLeod & Weinshilboum, 2011).

Clinical relevance

Effective testing and implementation determine whether pharmacogenomic knowledge actually reaches the bedside, and understanding their requirements is central to clinical pharmacology and laboratory medicine. This entry describes how testing and implementation work as reference material; it is not a recommendation to test or to alter therapy for any particular patient.

Epidemiology

Because clinically relevant variants are common, pre-emptive panel testing typically yields at least one actionable result for the large majority of individuals tested, which is part of the rationale advanced for panel-based approaches; uptake and the availability of decision support nonetheless vary widely across health systems (Wang, McLeod & Weinshilboum, 2011).

Evidence & guidelines

Implementation is anchored by guideline-producing consortia — notably the Clinical Pharmacogenetics Implementation Consortium (CPIC) and the Dutch Pharmacogenetics Working Group (DPWG) — which translate genotype into graded prescribing recommendations, and by curated knowledge bases such as PharmGKB; regulators also incorporate pharmacogenomic information into drug labelling (Swen et al., 2011; Lee et al., 2022; Hicks et al., 2015).

History

Single-gene pharmacogenetic tests entered practice for selected drugs from the late twentieth century. The development of standardized genotype-to-phenotype guidelines by CPIC and DPWG, together with electronic health records and decision support, shifted attention from isolated tests toward systematic, often pre-emptive, implementation programmes in the 2010s.

Debates

Reactive single-gene testing versus pre-emptive panel testing: Pre-emptive panels offer immediate results when a drug is later prescribed but require infrastructure to store and re-surface results, while reactive testing is simpler per episode; the balance of cost, utility, and feasibility remains contested.
Demonstrating clinical utility: Critics note that analytic validity is well established for many assays but high-quality evidence that testing improves clinical outcomes is stronger for some gene-drug pairs than others, shaping disagreement over which tests warrant routine use.

Key figures

Jesse Swen
Kelly Caudle
Mary Relling
Teri Klein
Howard McLeod

Seminal works

swen-2011
hicks-2015
lee-2022

Frequently asked questions

What is the difference between reactive and pre-emptive pharmacogenomic testing?: Reactive testing is ordered for a specific drug decision at the moment it arises, whereas pre-emptive testing genotypes a panel in advance and stores the results so they are available whenever a relevant drug is later considered.
Why is clinical decision support emphasized in implementation?: Because a stored genotype is only useful if the right interpretation reaches the prescriber at the right time; embedding alerts and recommendations in the electronic health record is how many programmes deliver that information at the point of care.