Pharmacy Insight Report
Pharmacist perspectives on PGx confidence, education, software integration, workflow barriers and clinical authority.
Audience: Pharmacists
Countries: 6
Survey records: 197
-Hero findings
– Quick Read — Key Findings
The full report examines the gap between pharmacogenomic evidence, pharmacist confidence, software architecture, reimbursement and point-of-care implementation.
FDA maintains pharmacogenomic biomarker and pharmacogenetic association resources across many drug-gene relationships, while CPIC guidelines are designed to help clinicians use available genetic results to optimize drug therapy. The implementation challenge is therefore increasingly operational. The MDForLives data shows a profession with strong interest in PGx, but with inconsistent exposure, education and decision support at the point of dispensing.
Clinical context: FDA notes that pharmacogenomics can help identify responders and non-responders, avoid adverse events and optimize dose. CPIC focuses on how available genetic results should be used for drug therapy, not on whether a test should be ordered.
MDForLives captured perspectives from Pharmacists across United States, United Kingdom, Canada, Italy, France, Germany. The findings below focus on the operational and clinical patterns that stand out across the response data.
Most respondents have more than six years in practice, yet confidence interpreting complex PGx reports remains mixed.
What the pattern suggests: Experience in pharmacy practice does not automatically equal experience with genomic interpretation.
Why it matters: Upskilling needs to be targeted to applied gene-drug decisions, not assume that seniority closes the PGx competency gap.
Only a minority say pharmacy school gave them actionable or even adequate practical preparation.
What the pattern suggests: The implementation gap begins before workflow. Many pharmacists were trained when PGx was still treated as emerging science rather than routine therapeutic infrastructure.
Why it matters: Education needs case-based interpretation, phenotype translation and medication action pathways that resemble real practice.
More than half rarely or never encounter patient-specific PGx data in daily practice.
What the pattern suggests: Low exposure reinforces low confidence. Without repetition, PGx remains a reference exercise rather than a familiar clinical workflow.
Why it matters: Routine implementation needs enough test availability and system visibility for pharmacists to build pattern recognition and practice fluency.
Only about one in five respondents has automated gene-drug clinical decision support during verification or dispensing.
What the pattern suggests: PGx cannot scale if genetic information lives outside the medication workflow. Manual lookup turns every case into an extra cognitive and time burden.
Why it matters: The most valuable implementation layer may be interoperable clinical decision support that translates a stored result into an actionable medication recommendation.
No single operational barrier dominates, which suggests PGx implementation is a systems problem rather than one missing feature.
What the pattern suggests: Fixing only education or only software is unlikely to be enough. Each layer affects whether PGx can become routine.
Why it matters: Successful programs need a bundled implementation model covering result access, decision support, training, reimbursement and prescriber collaboration.
Support for ordering authority is strong, while oncology/immunology and psychiatry are the most selected areas for immediate protocol-driven PGx.
What the pattern suggests: The profession appears willing to accept more responsibility, but authority without workflow support could simply move more uncompensated complexity to pharmacists.
Why it matters: Scope expansion is most sustainable when access, decision support, training and reimbursement expand with it.
Respondents repeatedly ask for PGx results and actionable recommendations to appear inside the EHR or dispensing platform rather than in a separate portal.
Many comments ask for more education, standardized protocols and employer-supported upskilling.
Open feedback highlights the challenge of adding testing, interpretation, counselling and prescriber communication to already busy workflows.
Insurance coverage, testing availability and the economics of implementation appear alongside software as adoption constraints.
Several respondents call for universal formats, protocol order sets and interoperable storage rather than one-off local solutions.
Separate portals and manual lookups make genomics easy to miss during a busy dispensing workflow.
Education matters, but decision support can translate knowledge into consistent action at the moment it is needed.
Ordering rights have limited value if time, reimbursement and interoperable software remain unresolved.
The pattern is not resistance to precision medicine. Pharmacists are being asked to operationalize genomic decisions before many dispensing environments are built to support them. PGx becomes routine when the result, guideline logic and recommended action appear inside the same workflow where the medication is verified.
Direct answers to the questions healthcare professionals are most likely to ask about these findings.
