NCPDP SCRIPT Standard Version 2023011
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.
What the authority record establishes
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.
Required for applicable federal e-prescribing transactions beginning January 1, 2028 according to the cited NCPDP federal-rule summary
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
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.
Affected operating stages
- Medication Benefit Inquiry
- EPA Initiation
- Plan Question Set
- Clinical Response
- Determination
- Renewal
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.
Benefit And Eligibility Context
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 benefit and eligibility context.
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.
Authorization Status Tracking
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 status tracking.
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
- prescribers and EHR vendors
- pharmacies
- PBMs and health plans
- pharmacy ePA networks
- medication-access and life-sciences platforms
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.