Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document pharmacy electronic prior authorization while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
CMS-0062-P
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. 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.
NCPDP SCRIPT v2023011
SCRIPT is the core U.S. e-prescribing standard and includes transactions for electronic prior authorization and medication history. Version 2023011 adds required ePA transactions and other prescribing enhancements. Pharmacy ePA follows a distinct NCPDP transaction path from medical-service prior authorization. Buyers must confirm supported SCRIPT versions, network participants, attachments, renewals, and transition readiness.
Operating domains
Interoperability and transaction reliability
Risk that FHIR, X12, NCPDP, portal, fax, voice, identity, attachment, or legacy-system handoffs fail, lose meaning, duplicate work, or leave no reliable status and audit record.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should pharmacy electronic prior authorization produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?
Recent changes
NCPDP SCRIPT 2023011 becomes the required e-prescribing version — Pharmacy ePA stakeholders need a version-specific migration, testing, and trading-partner readiness plan distinct from medical-service FHIR implementation.
CMS releases CMS-0062-P for drug prior authorization and interoperability — Pharmacy ePA networks, payers, PBMs, EHRs, pharmacies, clearinghouses, and FHIR infrastructure providers need a scenario plan that preserves the distinction between current obligations and proposed changes.