report.object
AI agents for pharmacy, PBMs and medication workflows
Expert-reviewed from public records, platform data, primary sources, and private research beyond AI search. Use /api/v1/reports/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS/sample before purchase, then download PDF, JSON, or Markdown after checkout.
page.markdown
AI agents for pharmacy, PBMs and medication workflows.md
# AI agents for pharmacy, PBMs and medication workflows
Pharmacy and PBM AI should prove a drug-class access ledger: benefit rule, formulary evidence, prior-auth result, channel, patient cost, paid fill, continuation and safety escalation.
## Object
| field | value |
| ---------------- | ---------------------------------------------------- |
| report_id | RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS |
| schema_version | 2026-05-28 |
| last_updated_at | 2026-06-01 |
| category | AGENTS |
| sector | Pharmacy and benefits |
| region | GLOBAL |
| confidence_score | 0.84 |
| source_count | 29 |
| evidence_count | 29 |
## Endpoints
| action | endpoint |
| ------------ | ------------------------------------------------------------------------------- |
| summary | /api/v1/reports/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS |
| sample | /api/v1/reports/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS/sample |
| schema | /api/v1/reports/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS/schema |
| quote | /api/v1/reports/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS/quote |
| purchase | /checkout/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS?view=agent |
| versions | /api/v1/reports/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS/versions |
| changelog | /api/v1/reports/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS/changelog |
| monitor | /api/v1/monitors?report_id=RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS |
| mcp_resource | colophon://reports/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS/sample |
## Coverage
| field | value |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| category | AGENTS |
| sector | Pharmacy and benefits |
| region | GLOBAL |
| topics | pharmacy AI, PBM, medication prior authorization, formulary, specialty pharmacy, claims, adherence, dispensing, NCPDP, pharmacy benefit |
| source_classes | proposed_rule, agency_program, pharmacy_standard, regulatory_report, regulation, safety_reporting, network_docs, industry_report, pharmacy_provider_docs, agency_guidance, health_it_rule, draft_operating_rule, implementation_guide, peer_reviewed_study, industry_survey, vendor_directory |
| update_cadence | Weekly |
## Sample JSON
```json
{
"report_id": "RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS",
"slug": "ai-agents-pharmacy-pbms-medication-workflows",
"schema_version": "2026-05-28",
"title": "AI agents for pharmacy, PBMs and medication workflows",
"abstract": "Pharmacy and PBM AI should prove a drug-class access ledger: benefit rule, formulary evidence, prior-auth result, channel, patient cost, paid fill, continuation and safety escalation.",
"category": "AGENTS",
"sector": "Pharmacy and benefits",
"region": "GLOBAL",
"topics": [
"pharmacy AI",
"PBM",
"medication prior authorization",
"formulary",
"specialty pharmacy",
"claims",
"adherence",
"dispensing",
"NCPDP",
"pharmacy benefit"
],
"last_updated_at": "2026-06-01T00:00:00Z",
"source_count": 29,
"evidence_count": 29,
"confidence_score": 0.84,
"web_url": "/r/ai-agents-pharmacy-pbms-medication-workflows/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS",
"sample_endpoint": "/api/v1/reports/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS/sample",
"inventory_endpoint": "/api/v1/reports/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS/inventory",
"full_endpoint": "/api/v1/reports/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS/full",
"schema_endpoint": "/api/v1/reports/RPT_PHARMACY_BENEFITS_AI_AGENTS_MEDICATION_WORKFLOWS/schema",
"redaction": {
"status": "sample",
"paid_sections_redacted": true,
"preview_limits": [
"summary",
"table_of_contents",
"evidence_profile"
]
},
"coverage": {
"category": "AGENTS",
"sector": "Pharmacy and benefits",
"region": "GLOBAL",
"topics": [
"pharmacy AI",
"PBM",
"medication prior authorization",
"formulary",
"specialty pharmacy",
"claims",
"adherence",
"dispensing",
"NCPDP",
"pharmacy benefit"
],
"source_classes": [
"proposed_rule",
"agency_program",
"pharmacy_standard",
"regulatory_report",
"regulation",
"safety_reporting",
"network_docs",
"industry_report",
"pharmacy_provider_docs",
"agency_guidance",
"health_it_rule",
"draft_operating_rule",
"implementation_guide",
"peer_reviewed_study",
"industry_survey",
"vendor_directory"
]
},
"confidence": {
"overall_confidence": 0.84,
"source_quality": 0.86,
"source_recency": 0.88,
"source_density": 0.82,
"claim_verifiability": 0.84,
"geographic_coverage": 0.74,
"known_gaps": [
"Medication prior-authorization sources are U.S.-centric because CMS, NCPDP and PBM evidence dominate the public record.",
"PBM and specialty-pharmacy operating data is often proprietary, which limits public accepted-output economics.",
"Adherence and dispensing evidence varies sharply by pharmacy channel, patient group and drug class."
]
},
"document": {
"object": "report_document",
"schemaVersion": "2026-05-28",
"title": "AI agents for pharmacy, PBMs and medication workflows",
"subtitle": "Medication AI must prove benefit-to-fill outcomes across PA, formulary and pharmacy-channel work.",
"abstract": "Pharmacy and PBM AI should prove a drug-class access ledger: benefit rule, formulary evidence, prior-auth result, channel, patient cost, paid fill, continuation and safety escalation.",
"category": "AGENTS",
"sector": "Pharmacy and benefits",
"region": "GLOBAL",
"topics": [
"pharmacy AI",
"PBM",
"medication prior authorization",
"formulary",
"specialty pharmacy",
"claims",
"adherence",
"dispensing",
"NCPDP",
"pharmacy benefit"
],
"sources": [
{
"id": "S1",
"label": "CMS - 2026 Interoperability Standards and Prior Authorization for Drugs Proposed Rule",
"publisher": "CMS",
"sourceClass": "proposed_rule",
"accessedAt": "2026-06-01",
"status": "verified",
"access": "sample",
"originalUrl": "https://www.cms.gov/newsroom/fact-sheets/2026-cms-interoperability-standards-prior-authorization-drugs-proposed-rule",
"transformChain": [],
"provenanceNotes": "Use as workflow or timing evidence; verify final status and local applicability before relying on exact obligations.",
"url": "https://www.cms.gov/newsroom/fact-sheets/2026-cms-interoperability-standards-prior-authorization-drugs-proposed-rule"
},
{
"id": "S2",
"label": "CMS - Electronic prior authorization overview",
"publisher": "CMS",
"sourceClass": "agency_program",
"accessedAt": "2026-06-01",
"status": "verified",
"access": "sample",
"originalUrl": "https://www.cms.gov/epa",
"transformChain": [],
"url": "https://www.cms.gov/epa"
},
{
"id": "S3",
"label": "NCPDP - SCRIPT electronic prior authorization",
"publisher": "NCPDP",
"sourceClass": "pharmacy_standard",
"accessedAt": "2026-06-01",
"status": "verified",
"access": "sample",
"originalUrl": "https://www.ncpdp.org/NCPDP/media/pdf/NCPDP_SCRIPT_ePA_Standard.pdf",
"transformChain": [],
"url": "https://www.ncpdp.org/NCPDP/media/pdf/NCPDP_SCRIPT_ePA_Standard.pdf"
},
{
"id": "S4",
"label": "FTC - Pharmacy benefit managers interim staff report",
"publisher": "FTC",
"sourceClass": "regulatory_report",
"accessedAt": "2026-06-01",
"status": "verified",
"access": "sample",
"originalUrl": "https://www.ftc.gov/reports/pharmacy-benefit-managers-report",
"publicationDate": "2024-07-09",
"transformChain": [],
"url": "https://www.ftc.gov/reports/pharmacy-benefit-managers-report"
},
{
"id": "S11",
"label": "FTC - Specialty generic drugs and vertically integrated PBMs",
"publisher": "FTC",
"sourceClass": "regulatory_report",
"accessedAt": "2026-06-01",
"status": "verified",
"access": "sample",
"originalUrl": "https://www.ftc.gov/node/87180",
"publicationDate": "2025-01-14",
"transformChain": [],
"url": "https://www.ftc.gov/node/87180"
}
],
"evidence": [
{
"id": "E1",
"sourceId": "S1",
"claimIds": [
"C1",
"C2"
],
"summary": "CMS proposed extending prior-authorization API requirements to drugs covered under pharmacy benefits, with the comment period closing on 15 June 2026; medication PA could become a more structured transaction, response-time, denial, appeal and API-reporting workflow.",
"status": "monitor",
"confidence": 0.87,
"access": "sample"
},
{
"id": "E2",
"sourceId": "S2",
"claimIds": [
"C1",
"C2"
],
"summary": "CMS electronic prior-authorization resources link final and proposed rules and national standards relevant to drug authorization workflows.",
"status": "verified",
"confidence": 0.84,
"access": "sample"
},
{
"id": "E3",
"sourceId": "S3",
"claimIds": [
"C2"
],
"summary": "NCPDP SCRIPT ePA provides a standard structure for exchanging medication prior-authorization questions and responses.",
"status": "verified",
"confidence": 0.84,
"access": "sample"
},
{
"id": "E4",
"sourceId": "S4",
"claimIds": [],
"summary": "FTC's PBM report analyses pharmacy benefit manager concentration, affiliated pharmacies, specialty drug economics and patient-cost concerns, making pharmacy-channel steering a transparency issue for AI-assisted formulary and network work.",
"status": "verified",
"confidence": 0.85,
"access": "sample"
},
{
"id": "E11",
"sourceId": "S11",
"claimIds": [],
"summary": "FTC's January 2025 second interim PBM report says the Big 3 PBMs marked up 22% of analysed specialty generic drugs by more than 1,000% over estimated acquisition costs, generated more than $7.3 billion in affiliated-pharmacy dispensing revenue in excess of NADAC from 2017 to 2022, and increased affiliated-pharmacy revenue share for specialty drugs from 54% in 2016 to 68% in 2023. Report inference: AI touching formulary, exception or channel routing needs acquisition-cost, NADAC, affiliated-pharmacy, patient-cost and appeal evidence.",
"status": "verified",
"confidence": 0.88,
"access": "sample"
}
],
"claims": [
{
"id": "C1",
"statement": "Medication AI should be treated as its own market because the executive denominator is drug access yield: whether a request becomes a paid fill, transparent exception, continued therapy or safety escalation.",
"confidence": 0.86,
"evidenceIds": [
"E1",
"E2",
"E4"
],
"access": "sample"
},
{
"id": "C2",
"statement": "Drug prior-authorization agents need CMS and NCPDP transaction evidence plus outcome telemetry on denial reason, appeal, paid fill and abandonment; clean ePA alone is not the buying object.",
"confidence": 0.84,
"evidenceIds": [
"E1",
"E2",
"E3"
],
"access": "sample"
}
],
"colophon": {
"checkedAt": "2026-06-01",
"latestRevisionAt": "2026-06-01T00:00:00Z",
"reviewStandard": "expert_human_reviewed",
"kinetics": {
"speed": "fast",
"impact": 0.87,
"momentum": 0.89,
"businessImpact": "Medication AI depends on drug-class access proof: paid fills, exceptions, therapy continuation and safety escalation by benefit rule.",
"rateOfChange": "ePA standards, PBM scrutiny and drug prior-authorization policy work make benefit-to-fill evidence more specific.",
"from": "separate ePA, formulary, dispensing and adherence tools",
"toward": "drug-class access ledgers connecting benefit logic to fill, continuation and safety outcomes"
},
"watch": [
"15 June 2026: CMS drug prior-authorization proposal comment period closes; U.S. drug prior-authorization lanes may need revised API, response-clock and reporting assumptions before ePA rollout [E1]."
],
"gapAnalysis": "Drug-class and channel-level medication-workflow telemetry linking benefit rules, prior-authorization outcomes, paid-fill yield, abandonment, patient cost, pharmacist intervention, specialty continuation and safety escalation."
},
"body": {
"sections": [
{
"id": "executive-summary",
"title": "Executive summary",
"access": "sample",
"claimIds": [
"C1",
"C2"
],
"evidenceIds": [
"E1",
"E3",
"E11"
],
"blocks": [
{
"id": "executive-summary-narrative",
"evidenceIds": [
"E1",
"E3",
"E11"
],
"type": "section_narrative",
"lead": "Medication AI should be judged by therapy access, not transaction completion: paid fill, exception clarity, continuation and safety escalation by drug class.",
"body": [
"Judge electronic prior authorization and formulary logic by medication access. The proof object is a drug-class ledger that follows the request through benefit rule, patient cost and channel. Fill evidence belongs in the paid-fill field [E21]. Continuation belongs in specialty-support evidence [E10]. Safety escalation belongs in pharmacovigilance evidence [E7].",
"CMS and NCPDP can make drug authorization more structured [E1, E3], while FTC specialty-generic evidence raises the cost of opaque steering or affiliated-channel optimization [E11].",
"The trap is automation that clears a transaction but loses the therapy outcome. A medication can be approved and still fail through abandonment, high out-of-pocket cost, channel redirect, refill break or safety handoff. CMS and ONC guidance make the governance test more explicit: individual evidence, public criteria, bias controls, reviewer accountability and DSI risk management [E12, E13].",
"Start with high-cost, high-friction drug classes and require a benefit-to-fill scorecard before scaling formulary, PA, dispensing, specialty support or adherence agents. The scorecard should distinguish requirement discovery and documentation capture [E18, E19]. It should also separate PA exchange and attachment evidence [E17, E20]. Real-time benefit records need their own checks [E14]. Formulary and claim-response records need separate checks [E15, E16]."
],
"detail": [
"Make paid fill, denial or appeal reason, patient-cost exposure, channel redirect, continuation and pharmacist or safety action the required denominator.",
"Keep formulary and network steering inside human review until the buyer can see who benefited, who abandoned therapy and why."
]
},
{
"id": "board-decision-table",
"title": "The buying decision",
"evidenceIds": [
"E1",
"E3",
"E11"
],
"type": "table",
"columns": [
{
"key": "question",
"label": "Question",
"align": "left"
},
{
"key": "answer",
"label": "Answer",
"align": "left"
},
{
"key": "move",
"label": "Action",
"align": "left"
}
],
"rows": [
{
"question": "What is the object of approval?",
"answer": "A drug-class access ledger from benefit rule and PA result to paid fill, continuation and safety escalation.",
"move": "Approve only lanes that return patient-cost, appeal, fill, continuation and safety fields before expanding beyond transaction automation."
},
{
"question": "Which lane goes first?",
"answer": "High-cost or high-friction therapies where authorization, patient cost, pharmacy channel and continuation are measurable.",
"move": "Baseline clean ePA, denial yield, appeal yield, paid fill, abandonment, refill continuation and pharmacist intervention."
},
{
"question": "What remains blocked?",
"answer": "Opaque formulary steering, channel redirect or adherence automation without patient-cost, continuation and safety evidence.",
"move": "Separate benefit automation from pharmacy-channel incentives and safety reporting."
}
]
}
]
},
{
"id": "what-changed",
"title": "What changed",
"access": "sample",
"dek": "Public evidence is now structured enough to define private approval tests.",
"claimIds": [
"C1",
"C2"
],
"evidenceIds": [
"E1",
"E3",
"E11"
],
"blocks": [
{
"id": "what-changed-narrative",
"evidenceIds": [
"E1",
"E3",
"E11"
],
"type": "section_narrative",
"lead": "The trigger is the gap between faster medication transactions and provable therapy access: ePA structure, PBM scrutiny, patient-cost standards and algorithm-governance evidence now have to connect to fill outcomes, continuation and safety escalation. Fill outcome evidence belongs in the private eval [E21]. Continuation and safety evidence need specialty and FAERS controls [E10, E7].",
"body": [
"CMS and NCPDP can make drug ePA transactions faster and more structured [E1, E3]. The proof still comes from therapy access: formulary version, step therapy, patient cost and pharmacy channel. Fill outcomes need ePA-to-fill evidence [E21]. Refill continuation needs specialty workflow support [E10]. Pharmacist or safety action needs safety-reporting evidence [E7]. FTC PBM evidence makes hidden steering, affiliated-pharmacy routing and acquisition-cost opacity a commercial risk [E11].",
"Start with high-cost, high-friction drug classes and contract for a benefit-to-fill scorecard: PA status, denial or appeal reason, exception rationale, patient out-of-pocket exposure, pharmacy-channel redirect, paid-fill date, refill continuation, pharmacist intervention and safety escalation. Scale formulary or network optimization only when those fields are returned by drug class and channel, with individual-patient evidence and bias controls for coverage workflows [E12].",
"For high-risk workflows, the approval record has to connect source evidence, accepted output, reviewer action, exception path, outcome signal and retained audit record before volume or staffing claims matter."
]
},
{
"id": "trigger-table",
"title": "Triggers that change approval timing",
"evidenceIds": [
"E1",
"E3",
"E11"
],
"type": "table",
"columns": [
{
"key": "trigger",
"label": "Trigger",
"align": "left"
},
{
"key": "why_now",
"label": "Why it matters",
"align": "left"
},
{
"key": "buyer_action",
"label": "Decision use",
"align": "left"
}
],
"rows": [
{
"trigger": "CMS drug prior-auth proposal",
"why_now": "Medication authorization may move onto API-based requirements, response clocks and public usage evidence [E1].",
"buyer_action": "Demand transaction-to-fill instrumentation rather than ePA completion metrics alone."
},
{
"trigger": "NCPDP ePA standard",
"why_now": "Medication authorization has pharmacy-specific request and response structure [E3].",
"buyer_action": "Test by drug class, formulary version, real-time benefit, payer channel and fallback path [E14, E15]."
},
{
"trigger": "FTC PBM scrutiny",
"why_now": "Benefit design, specialty economics and pharmacy steering are under public policy pressure, with official specialty-generic markup evidence now available [E11].",
"buyer_action": "Require policy, acquisition-cost, conflict, channel, patient-cost and appeal evidence for optimization."
}
]
},
{
"id": "route-definition-callout",
"title": "Route definition",
"evidenceIds": [
"E3",
"E1"
],
"type": "callout",
"tone": "neutral",
"body": "Route means the approved path from work to accepted output: the source set, data boundary, model or vendor channel, tools, reviewer, evidence record and reapproval trigger that make an AI result usable."
}
]
},
{
"id": "decision-map",
"title": "Decision map",
"access": "sample",
"dek": "Workflow approval changes by authority, source boundary and proof burden.",
"claimIds": [
"C1",
"C2"
],
"evidenceIds": [
"E3",
"E1",
"E11"
],
"blocks": [
{
"id": "decision-map-narrative",
"evidenceIds": [
"E3",
"E1",
"E11"
],
"type": "section_narrative",
"lead": "The drug-class access ledger is the proof object: each medication request must resolve into a paid fill, transparent exception, continued therapy or safety escalation.",
"body": [
"The decision map should start with a drug-class access ledger with benefit rule, formulary version, PA result, pharmacy channel, patient cost, paid-fill status, continuation and safety escalation: what source record is read, what output is drafted, who approves it, where it is stored and what event forces reapproval.",
"A system can pass a low-risk support test and still fail production work: source evidence, accepted output, integration state, exception handling, reviewer burden and downstream rework have to hold together.",
"The useful vendor question is whether the system can make the named task inspectable, reversible and measurable inside the operating record."
]
},
{
"id": "route-selection-table",
"title": "Workflow selection",
"evidenceIds": [
"E3",
"E1",
"E11"
],
"type": "table",
"columns": [
{
"key": "route",
"label": "Workflow",
"align": "left"
},
{
"key": "accepted_output",
"label": "Accepted work",
"align": "left"
},
{
"key": "gate",
"label": "Approval gate",
"align": "left"
},
{
"key": "buyer_rule",
"label": "Approval rule",
"align": "left"
}
],
"rows": [
{
"route": "Drug-class access ledger",
"accepted_output": "Request-to-fill record with PA result, exception, pharmacy channel, patient cost, paid fill, refill continuation and escalation outcome [E21].",
"gate": "NDC or therapy class, benefit type, formulary version, policy source, reviewer action, evidence attachment and outcome timestamp [E14, E17].",
"buyer_rule": "Fund the ledger before funding broad autonomy."
},
{
"route": "Electronic drug prior authorization",
"accepted_output": "Medication PA request, response, denial reason, appeal trigger or approved exception tied to benefit and drug class [E3, E20].",
"gate": "NCPDP or payer channel, source policy and required evidence [E3], plus response-clock and fallback evidence where CMS drug-authorization rules apply [E1].",
"buyer_rule": "Require ePA to connect to fill and abandonment outcomes."
},
{
"route": "Formulary, exception and PBM steering",
"accepted_output": "Recommendation or exception rationale with policy source, patient-cost effect, pharmacy-channel impact and conflict evidence.",
"gate": "Formulary version, step-therapy rule, acquisition-cost/NADAC comparison, rebate or network conflict check, human review and appeal path [E11, E15].",
"buyer_rule": "Block optimization that hides steering, access or affiliated-pharmacy risk."
},
{
"route": "Specialty therapy start and continuation",
"accepted_output": "Benefits investigation, enrollment, first fill, refill continuation, patient-support task or abandonment reason [E10].",
"gate": "Patient consent, pharmacist review, specialty requirements, adverse-event escalation and support-contact evidence.",
"buyer_rule": "Measure therapy continuation and abandonment, not only staff minutes."
},
{
"route": "Dispensing, adherence and safety",
"accepted_output": "Refill intervention, counselling prompt, interaction alert, corrected claim or safety escalation.",
"gate": "Pharmacist action, medication history, patient communication, safety check and escalation log [E7, E10].",
"buyer_rule": "Keep dispensing and safety authority with licensed pharmacy staff."
}
]
},
{
"id": "workflow-authority-matrix",
"title": "Write authority changes the proof burden",
"caption": "Use the matrix to decide what proof is required before each workflow becomes accepted work.",
"evidenceIds": [
"E3",
"E1",
"E11"
],
"type": "visual_matrix",
"columns": [
"Source path",
"Reviewer gate",
"System action",
"Retest trigger"
],
"rows": [
{
"label": "Drug-class access ledger",
"note": "Request-to-fill record with PA result, exception, pharmacy channel, patient cost, paid fill, refill continuation and escalation outcome [E21].",
"cells": [
{
"label": "Source named",
"detail": "NDC or therapy class, benefit type, formulary version, policy source, reviewer action, evidence attachment and outcome timestamp [E14, E17].",
"tone": "info",
"strength": "medium"
},
{
"label": "Human gate",
"detail": "Fund the ledger before funding broad autonomy.",
"tone": "blocked",
"strength": "gate"
},
{
"label": "Accepted work",
"detail": "Request-to-fill record with PA result, exception, pharmacy channel, patient cost, paid fill, refill continuation and escalation outcome [E21].",
"tone": "success",
"strength": "high"
},
{
"label": "Reapproval",
"detail": "Retest when policy, workflow, model, data access or system write rights change.",
"tone": "warning",
"strength": "medium"
}
]
},
{
"label": "Electronic drug prior authorization",
"note": "Medication PA request, response, denial reason, appeal trigger or approved exception tied to benefit and drug class [E3, E20].",
"cells": [
{
"label": "Source named",
"detail": "NCPDP or payer channel, source policy and required evidence [E3], plus response-clock and fallback evidence where CMS drug-authorization rules apply [E1].",
"tone": "info",
"strength": "medium"
},
{
"label": "Human gate",
"detail": "Require ePA to connect to fill and abandonment outcomes.",
"tone": "blocked",
"strength": "gate"
},
{
"label": "Accepted work",
"detail": "Medication PA request, response, denial reason, appeal trigger or approved exception tied to benefit and drug class [E3, E20].",
"tone": "success",
"strength": "high"
},
{
"label": "Reapproval",
"detail": "Retest when policy, workflow, model, data access or system write rights change.",
"tone": "warning",
"strength": "medium"
}
]
},
{
"label": "Formulary, exception and PBM steering",
"note": "Recommendation or exception rationale with policy source, patient-cost effect, pharmacy-channel impact and conflict evidence.",
"cells": [
{
"label": "Source named",
"detail": "Formulary version, step-therapy rule, acquisition-cost/NADAC comparison, rebate or network conflict check, human review and appeal path [E11, E15].",
"tone": "info",
"strength": "medium"
},
{
"label": "Human gate",
"detail": "Block optimization that hides steering, access or affiliated-pharmacy risk.",
"tone": "blocked",
"strength": "gate"
},
{
"label": "Accepted work",
"detail": "Recommendation or exception rationale with policy source, patient-cost effect, pharmacy-channel impact and conflict evidence.",
"tone": "success",
"strength": "high"
},
{
"label": "Reapproval",
"detail": "Retest when policy, workflow, model, data access or system write rights change.",
"tone": "warning",
"strength": "medium"
}
]
},
{
"label": "Specialty therapy start and continuation",
"note": "Benefits investigation, enrollment, first fill, refill continuation, patient-support task or abandonment reason [E10].",
"cells": [
{
"label": "Source named",
"detail": "Patient consent, pharmacist review, specialty requirements, adverse-event escalation and support-contact evidence.",
"tone": "info",
"strength": "medium"
},
{
"label": "Human gate",
"detail": "Measure therapy continuation and abandonment, not only staff minutes.",
"tone": "blocked",
"strength": "gate"
},
{
"label": "Accepted work",
"detail": "Benefits investigation, enrollment, first fill, refill continuation, patient-support task or abandonment reason [E10].",
"tone": "success",
"strength": "high"
},
{
"label": "Reapproval",
"detail": "Retest when policy, workflow, model, data access or system write rights change.",
"tone": "warning",
"strength": "medium"
}
]
},
{
"label": "Dispensing, adherence and safety",
"note": "Refill intervention, counselling prompt, interaction alert, corrected claim or safety escalation.",
"cells": [
{
"label": "Source named",
"detail": "Pharmacist action, medication history, patient communication, safety check and escalation log [E7, E10].",
"tone": "info",
"strength": "medium"
},
{
"label": "Human gate",
"detail": "Keep dispensing and safety authority with licensed pharmacy staff.",
"tone": "blocked",
"strength": "gate"
},
{
"label": "Accepted work",
"detail": "Refill intervention, counselling prompt, interaction alert, corrected claim or safety escalation.",
"tone": "success",
"strength": "high"
},
{
"label": "Reapproval",
"detail": "Retest when policy, workflow, model, data access or system write rights change.",
"tone": "warning",
"strength": "medium"
}
]
}
],
"legend": [
{
"label": "Private eval can start here",
"tone": "success",
"strength": "high"
},
{
"label": "Requires named owner or reviewer",
"tone": "warning",
"strength": "medium"
},
{
"label": "Hard approval gate before scale",
"tone": "blocked",
"strength": "gate"
}
]
}
]
},
{
"id": "signature-proof",
"title": "Signature proof",
"access": "locked",
"dek": "The decisive proof is whether the workflow survives evidence, audit and rework.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "signature-proof-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "provider-workflow-landscape",
"title": "Provider lanes",
"access": "locked",
"dek": "Providers should be compared by workflow authority.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "provider-workflow-landscape-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "use-case-route-selection",
"title": "Workflow selection",
"access": "locked",
"dek": "Production starts with the lane where output can be accepted or rejected visibly.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "use-case-route-selection-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "evidence-and-benchmarks",
"title": "Evidence fit",
"access": "locked",
"dek": "Public evidence maps to local accepted work.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "evidence-and-benchmarks-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "private-eval-design",
"title": "Private eval design",
"access": "locked",
"dek": "Public evidence chooses the tests; local cases decide production.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "private-eval-design-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "risks-and-controls",
"title": "Risks and controls",
"access": "locked",
"dek": "The main risk is ungoverned action.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "risks-and-controls-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "operating-model",
"title": "Operating model",
"access": "locked",
"dek": "Production ownership crosses clinical, technical, compliance and finance teams.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "operating-model-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "economics",
"title": "Economics",
"access": "locked",
"dek": "Price the accepted work.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "economics-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "implementation-signals",
"title": "Public claim tests",
"access": "locked",
"dek": "Vendor pages seed diligence; local telemetry supplies operating proof.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "implementation-signals-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "vendor-directory",
"title": "Diligence directory",
"access": "locked",
"dek": "Representative vendors and platform RFI anchors to include in diligence.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "vendor-directory-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "recommended-next-steps",
"title": "Recommended next steps",
"access": "locked",
"dek": "A practical workflow can be approved in phases without pretending the whole market is ready.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "recommended-next-steps-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "known-unknowns",
"title": "Known unknowns",
"access": "locked",
"dek": "These gaps should shape diligence rather than delay all buying.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "known-unknowns-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "source-ledger",
"title": "Source ledger",
"access": "locked",
"dek": "Primary public sources and evidence rows behind the workflow analysis.",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "source-ledger-locked",
"title": "Locked section",
"evidenceIds": [],
"type": "callout",
"tone": "locked",
"body": "Purchase or subscribe to unlock this section."
}
]
},
{
"id": "glossary",
"title": "Glossary",
"access": "sample",
"claimIds": [],
"evidenceIds": [],
"blocks": [
{
"id": "glossary-table",
"title": "Terms used in this report",
"caption": "Definitions are reader aids, not separate evidence claims.",
"evidenceIds": [],
"type": "table",
"columns": [
{
"key": "term",
"label": "Term",
"align": "left"
},
{
"key": "meaning",
"label": "Plain meaning",
"align": "left"
}
],
"rows": [
{
"term": "Route",
"meaning": "The approved path from work to accepted output: source set, data boundary, model or vendor channel, tools, reviewer, evidence record and reapproval trigger."
},
{
"term": "API",
"meaning": "Application programming interface: a governed software connection used by an app or workflow to call a model or service."
}
]
}
]
}
]
}
},
"gap_analysis": "Drug-class and channel-level medication-workflow telemetry linking benefit rules, prior-authorization outcomes, paid-fill yield, abandonment, patient cost, pharmacist intervention, specialty continuation and safety escalation.",
"kinetics": {
"speed": "fast",
"impact": 0.87,
"momentum": 0.89,
"businessImpact": "Medication AI depends on drug-class access proof: paid fills, exceptions, therapy continuation and safety escalation by benefit rule.",
"rateOfChange": "ePA standards, PBM scrutiny and drug prior-authorization policy work make benefit-to-fill evidence more specific.",
"from": "separate ePA, formulary, dispensing and adherence tools",
"toward": "drug-class access ledgers connecting benefit logic to fill, continuation and safety outcomes"
},
"watch_signals": [
"15 June 2026: CMS drug prior-authorization proposal comment period closes; U.S. drug prior-authorization lanes may need revised API, response-clock and reporting assumptions before ePA rollout [E1]."
],
"sample_findings": [
"The proof object is the drug-class access ledger, not ePA automation: prove whether each request becomes a paid fill, transparent exception, continued therapy or safety escalation."
]
}
```