CMS Interoperability Standards and Prior Authorization for Drugs Proposed Rule
The proposal would extend many electronic prior authorization, decision-time, transparency, API, and reporting policies to drugs and would adopt or update FHIR-based standards and implementation specifications for prior authorization transactions. The proposals are not final policy.
What the authority record establishes
The proposal would extend many electronic prior authorization, decision-time, transparency, API, and reporting policies to drugs and would adopt or update FHIR-based standards and implementation specifications for prior authorization transactions. The proposals are not final policy.
Not binding unless and until provisions are finalized with applicable compliance dates
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
It could materially reduce the current boundary between medical-service and drug prior authorization regulation while changing standards, response times, and metrics. Buyers must plan for the possibility without treating proposed provisions as current obligations.
Affected operating stages
- Drug Requirement Discovery
- Documentation Exchange
- Request Submission
- Determination
- Denial And Appeal Transparency
- Public Metrics Reporting
Capabilities to examine
Authorization Requirement Discovery
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for authorization requirement discovery.
Clinical Documentation Assembly
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for clinical documentation assembly.
Medical-Service Electronic Submission
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for medical-service electronic submission.
Denial Reason And Correspondence
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for denial reason and correspondence.
Metrics And Turnaround Reporting
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for metrics and turnaround reporting.
FHIR CRD, DTR, And PAS Interoperability
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for FHIR CRD, DTR, and PAS interoperability.
Pharmacy Electronic Prior Authorization
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for pharmacy electronic prior authorization.
Audit Trail And Decision Provenance
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for audit trail and decision provenance.
Affected buyer audiences
- health plans and PBMs
- providers, pharmacies, and EHR vendors
- pharmacy and medical-benefit ePA networks
- clearinghouses and FHIR infrastructure providers
- compliance and policy teams
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
Prior Auth Monitor does not provide patient-specific medical advice, determine coverage, authorize care, or establish final payment. Its records support organizational research and operating review.