This bill directs the Secretary of Health and Human Services to update the National Action Plan for Adverse Drug Event (ADE) Prevention so it formally incorporates advances in pharmacogenomic science and testing, and to report to Congress on implementation within 180 days. It also requires HHS to issue guidance for a broad set of clinical professionals on the use of pharmacogenomic testing and to provide operational guidance for electronic health records and e-prescribing systems so pharmacogenomic information can trigger decision support and facilitate reporting to the FDA Adverse Event Reporting System (FAERS).
Why it matters: the measure aims to move pharmacogenomic findings from research into routine prescribing workflows—changing how EHRs surface test results, how clinicians are educated about gene–drug risks, and how post-market safety surveillance captures genetic associations. The practical effects will fall on EHR and e-prescribing vendors, clinical labs that perform genetic tests, health systems that deploy decision support, and regulators who must absorb and standardize genetic data into labeling and surveillance systems.
At a Glance
What It Does
The bill requires HHS to report to Congress within 180 days, convene the Federal Interagency Steering Committee to update the ADE National Action Plan to include drug–gene and multi‑drug–gene interactions, and issue guidance for clinicians and health IT. It directs updates to FAERS to accept EHR-submitted reports and add an optional flag for suspected drug–gene interactions, tasks the GAO to study including drug–gene information on labels, and mandates reports on EHR improvements to support pharmacogenomics and real‑world evidence.
Who It Affects
Health care providers (physicians, pharmacists, geneticists, advanced practice clinicians), health system administrators, medical schools, clinical laboratories performing pharmacogenomic tests, EHR and e-prescribing vendors, the FDA (FAERS), and standards bodies that enable lab/test interoperability.
Why It Matters
By linking pharmacogenomic testing to certification guidance and surveillance, the bill pushes vendors and health systems toward structured genetic data, routine decision support, and new reporting channels—raising technical, clinical, and compliance implications for workflow, liability, and data standards.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
Section 3 sets an immediate federal planning task: within 180 days HHS must report on how the existing National Action Plan for Adverse Drug Event Prevention is being implemented and convene the Federal Interagency Steering Committee to update that Plan. The update must specifically incorporate recent scientific advances around drug–gene interactions (including combinations of multiple drugs and genes), recognize how falling genetic test costs change deployment decisions, assess pharmacogenetic testing combined with clinical decision support as a prevention tool, and broaden adverse event monitoring to identify genetic associations.
Section 4 requires HHS to issue guidance aimed at a wide set of clinicians and educators—physicians, pharmacists, nurse practitioners, physician assistants, medical and laboratory geneticists, genetic counselors, and academic faculty—covering when pharmacogenomic testing can prevent adverse reactions, how to use drug‑gene and drug‑drug‑gene alerting systems, when to consult genetics specialists, and the importance of including pharmacogenomic information when reporting adverse events to the FDA. The guidance is educational and prescriptive in scope: it addresses both clinical decision-making and where genetic specialists fit into care pathways.Section 5 targets health information technology and surveillance.
It directs HHS to give practicable guidance to providers and leaders on how EHRs, e‑prescribing systems, and pharmacy benefit checks should behave—specifically, how systems might automatically surface recommendations that testing is appropriate before a medication order completes and how to show drug–gene and drug–drug–gene associations based on a patient’s medication and allergy lists and existing genetic test results. The bill requires routine (at least biannual) updates to alerting guidance to capture new drug labels and peer‑reviewed professional guidance, contains a rule of construction permitting immediate contraindication alerts based on pharmacogenomic results, and asks HHS to encourage EHRs that can submit ADE information directly to FAERS.On the surveillance and standards side, the bill orders FAERS updates so users can optionally flag suspected drug–gene or drug–drug–gene interactions and enables FAERS to accept reports directly from EHRs and provide patient-friendly mobile reporting channels; HHS must report on progress within one year.
The Comptroller General must study, within 180 days, how FDA could include and update drug–gene interaction information on drug labels and submit recommendations. Finally, HHS must report within 180 days on additional EHR improvements needed to develop pharmacogenomics real‑world evidence, including capture of which laboratory and which specific test produced results—an explicit nod to the need for richer lab/test metadata in EHRs.
The Five Things You Need to Know
HHS must report to Congress within 180 days on implementation of the National Action Plan for Adverse Drug Event Prevention and convene the Federal Interagency Steering Committee to update that Plan.
The Committee must evaluate drug–gene and multi‑drug–gene interactions, the preventive role of pharmacogenetic testing paired with clinical decision support, and expand ADE monitoring to identify genetic associations.
HHS must issue guidance for a broad set of clinical professionals and educators on when to use pharmacogenomic testing, how to consult genetics specialists, and how pharmacogenomics fits into comprehensive medication management.
The bill directs HHS to produce guidance for EHRs and e‑prescribing systems so alerts can indicate when testing is appropriate and to display drug–gene and drug–drug‑gene associations before an order completes; guidance must be updated at least biannually.
FAERS must be modernized to accept direct EHR submissions and an optional drug‑gene interaction flag, HHS must create patient‑friendly electronic reporting options within one year, and the GAO must study how FDA can add/update drug‑gene info on labels within 180 days.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Update National Action Plan and report to Congress
This section requires HHS to produce a 180‑day report to Congress on how the existing National Action Plan for ADE Prevention is progressing against its target outcomes, and to reconvene the Federal Interagency Steering Committee to update the Plan. Practically, this converts pharmacogenomics from a peripheral research topic into a named objective of federal ADE strategy and forces federal agencies to align on measurable implementation steps and surveillance priorities.
Guidance and education for clinical professionals
HHS must issue guidance tailored to clinicians, clinical leaders, medical educators, and genetics professionals on the clinical role of pharmacogenomic testing, the interpretation of results, when to consult genetic specialists, and how to report pharmacogenomic information in ADE reports to FDA. The provision places education and referral pathways squarely on the federal agenda, which will matter for continuing education, curricula in training programs, and institutional onboarding.
EHR and e‑prescribing behavior before order completion
The Secretary must provide guidance on how health IT should behave before a medication order is finalized, including automatic indications when testing is appropriate based on labeling or professional guidelines and visibility of drug‑gene and drug‑drug‑gene associations tied to a patient’s medication/allergy lists and test results. For vendors and implementers, this implies the need for structured data capture, mapping to authoritative sources (labels/guidelines), and workflow hooks that surface suggestions without blocking completion unless clinically indicated.
Biannual updates to alerting guidance and electronic ADE reporting
HHS must issue routine guidance on drug‑gene interaction alerting and update that guidance not less than every two years to reflect new or revised drug labels and published professional guidelines. Separately, HHS is to encourage development of EHR features that submit ADE reports directly to FAERS; FAERS itself must be updated to accept EHR submissions and add an optional selector for suspected drug‑gene or drug‑drug‑gene interactions, and HHS must work with stakeholders to create patient‑friendly electronic reporting options. These provisions operationalize surveillance pathways for genetic signals while setting a cadence for integrating new evidence into alerts.
GAO study on including drug‑gene interactions on drug labels
The Comptroller General must study and recommend how FDA can include and keep current drug‑gene interaction information on drug labels and submit those recommendations to congressional committees within 180 days. That study is a direct channel to influence FDA labeling practice, but it stops short of an immediate labeling mandate; instead it produces a blueprint for potential regulatory change.
Report on EHR improvements to support pharmacogenomics real‑world evidence
HHS must report within 180 days on further EHR enhancements needed to generate pharmacogenomics real‑world evidence, explicitly considering the need to capture information about the laboratory and the specific test used. This focuses attention on metadata—who ran the test, the assay used, and how results are encoded—an operational requirement for analytics and trustworthy RWE.
This bill is one of many.
Codify tracks hundreds of bills on Healthcare across all five countries.
Explore Healthcare in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Patients with actionable genetic variants — clearer guidance and EHR alerts can reduce prescribing of contraindicated drugs or prompt dose adjustments, lowering risk of preventable adverse drug events.
- Clinical pharmacists and pharmacogenomics specialists — the bill elevates their consultative role and creates more institutional demand for their services in medication management.
- EHR and clinical decision support vendors that adopt structured pharmacogenomic capabilities — they gain market differentiation as health systems seek compliant, analytics-ready solutions.
- Public health and FDA surveillance programs — FAERS enhancements and structured EHR reporting improve the capacity to detect genetic associations with adverse events and support evidence generation.
Who Bears the Cost
- EHR and e‑prescribing vendors — they must design, implement, and maintain new decision‑support flows, data fields for genetic test metadata, and interfaces that can submit ADEs to FAERS.
- Clinical laboratories and pathology/informatics teams — they will need to standardize result formatting and supply persistent test identifiers and metadata so EHRs can use results reliably.
- Health systems and smaller practices — they must absorb integration, workflow redesign, and clinician training costs, and may need to prioritize which genetic tests to support in routine care.
- HHS and federal agencies — producing reports, issuing guidance, updating FAERS, and coordinating the interagency committee will require staff time and possibly new technical investments without specified funding.
Key Issues
The Core Tension
The central tension is between accelerating the use of pharmacogenomic information to prevent adverse drug events and the practical, clinical, and technical burdens that acceleration imposes: improved safety requires standardized, high‑quality genetic data and well‑tuned decision support, but producing that infrastructure demands vendor effort, lab standardization, clinician training, and careful handling of imperfect evidence—trade-offs the bill signals but does not fully resolve.
The bill pushes several operational changes without specifying standards or funding. It asks for guidance and reports but stops short of prescriptive certification criteria, reimbursement changes, or required coverage of pharmacogenomic tests.
That leaves a gap between federal direction and on‑the‑ground implementation: vendors, labs, and health systems will need to interpret guidance into technical specifications (data models, vocabularies, APIs) without a single mandated standard. The requirement that EHRs indicate when testing is appropriate and display drug‑gene associations places pressure on clinical decision support design: too aggressive an alerting approach risks increased false positives and clinician alert fatigue; too conservative an approach reduces patient safety gains.
Data quality and provenance are central unresolved issues. The bill explicitly asks HHS to consider capturing lab and test metadata, but it does not require specific coding systems (LOINC, SNOMED CT, or FHIR profiles).
Without agreed identifiers for tests and laboratories, linking results across EHRs, labs, and FAERS will be brittle. Separately, adding a drug‑gene flag to FAERS and opening patient mobile reporting could improve capture of genetic signals but will also change signal‑to‑noise in postmarket data; surveillance teams must plan for increased volume, variable data quality, and potential confounding when tests differ in analytic validity.
Finally, the clinical evidence base for many gene–drug interactions varies. The bill directs biannual updating of alert guidance to reflect new drug labels and professional guidelines, but it does not set thresholds for when an alert should be mandatory versus advisory.
That ambiguity leaves liability and practice‑pattern tensions: some institutions will adopt conservative, interventionist policies while others will wait for stronger evidence or insurance coverage, potentially exacerbating care disparities.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.