Pharmacy electronic prior authorization prepares for NCPDP SCRIPT 2023011
The federally named version becomes required January 1, 2028 and includes specific electronic prior-authorization transactions alongside broader e-prescribing changes.
Editorial figure by Prior Auth Monitor. Source context: National Council for Prescription Drug Programs.
Pharmacy ePA has its own standards path
Drug authorization cannot be evaluated solely through the medical-service FHIR workflow. Prescribers, EHRs, pharmacies, PBMs, health plans, and transaction networks use NCPDP standards for formulary, benefit, real-time benefit, prescribing, and ePA functions. The transition to SCRIPT 2023011 therefore has its own testing and trading-partner dependencies.
Buyers should request a supported-version matrix, transition plan, certification or test evidence where applicable, counterparty readiness, backward-compatibility approach, and the exact ePA transactions included in each product package.
Version readiness is not network reach
A vendor may support a standard version while having limited reach across PBMs, plans, EHRs, or pharmacies. Another may have broad network connectivity but require staged implementation for the newer version. Those are separate dimensions and should remain separate in comparison records.
The long runway to 2028 gives organizations time to test end-to-end workflows rather than accept a roadmap checkbox. It also creates a recurring standards-readiness beat for pharmacy ePA providers and their customers.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Prior Auth Monitor will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.