Change record: NCPDP SCRIPT 2023011 becomes the required e-prescribing version
The federally named SCRIPT 2023011 transition includes electronic prior-authorization transactions and becomes required January 1, 2028.
What changed
The federally named SCRIPT 2023011 transition includes electronic prior-authorization transactions and becomes required January 1, 2028.
This entry preserves the event separately from maintained provider and capability conclusions. A rule, announcement, release, enforcement record, or market transaction can be material before enough evidence exists to revise a company classification or comparison.
Operating consequence
Pharmacy ePA stakeholders need a version-specific migration, testing, and trading-partner readiness plan distinct from medical-service FHIR implementation.
Teams should identify which records, populations, systems, transactions, jurisdictions, products, or decisions fall within the change. Then assign an accountable owner, response date, evidence requirement, and disposition. Broad reassessment is not always necessary, but a material event deserves a documented decision.
Capabilities to revisit
Pharmacy Electronic Prior Authorization
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for pharmacy electronic prior authorization.
Benefit And Eligibility Context
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for benefit and eligibility context.
Audit Trail And Decision Provenance
Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for audit trail and decision provenance.
Questions for operating teams
- Which exact population and effective date does the source establish?
- Does the change alter authority, policy, content, workflow, integration, evidence, or only market positioning?
- What customer-controlled interpretation, configuration, or process remains outside a provider's responsibility?
- What test case would show whether the operational consequence has reached production?
- What record will close, defer, or supersede this review?
Evidence boundary
The source class is Official standards-body announcement. It establishes only the statements supported by the linked record and does not, by itself, establish implementation depth, market-wide availability, transaction-specific applicability, independent efficacy, or a universal buyer conclusion.