Written and maintained by CASRAI Editorial Board
Last updated
The NCPDP SCRIPT Standard—developed and maintained by the ANSI-accredited National Council for Prescription Drug Programs (NCPDP)—is the mandated national electronic data interchange (healthcare EDI) standard used by Electronic Health Records (EHRs), standalone e-prescribing systems, health information networks (such as Surescripts), retail and specialty pharmacies, and Pharmacy Benefit Managers (PBMs) to transmit outpatient prescriptions, medication history, and electronic prior authorization (ePA) messages across the United States. Under Centers for Medicare & Medicaid Services (CMS) Medicare Part D regulations (42 CFR § 423.160) and Office of the National Coordinator for Health IT (ONC / ASTP) certification criteria (45 CFR § 170.315(b)(3)), certified EHR modules must implement the NCPDP SCRIPT Standard alongside standardized clinical drug vocabularies (RxNorm and NDC).
What Is the NCPDP SCRIPT Standard? Core Transaction Architecture
While the NCPDP Telecommunication Standard (such as Version D.0 and F6) governs real-time pharmacy-to-PBM claim billing and adjudication at the pharmacy counter, the NCPDP SCRIPT Standard governs clinical prescriber-to-pharmacy and prescriber-to-payer workflows. Modern SCRIPT implementations use an extensible XML (and JSON-compatible) schema organized into seven major transaction families:
| Transaction Family | NCPDP SCRIPT Message Names | Direction & Clinical Workflow Function |
|---|---|---|
| New Prescription & Cancellation | NewRx, NewRxRequest, NewRxResponseDenied, CancelRx, CancelRxResponse |
Prescriber → Pharmacy: Transmits a newly signed outpatient prescription (carrying RxNorm code, NDC, structured Sig directions, quantity, days’ supply, refills, and DEA EPCS digital signature) or instructs the pharmacy to cancel a previously sent order (`CancelRx`) so discontinued drugs are not dispensed. |
| Prescription Renewal (Refills) | RxRenewalRequest, RxRenewalResponse |
Pharmacy ↔ Prescriber: When an active prescription runs out of authorized refills, the pharmacy sends RxRenewalRequest to the EHR; the clinician approves, modifies, or denies the renewal via RxRenewalResponse. |
| Therapeutic / Prior Auth Change | RxChangeRequest, RxChangeResponse |
Pharmacy ↔ Prescriber: Initiated by the pharmacist to request a therapeutic substitution (e.g., switching to a formulary-covered alternative), generic substitution, dosage form adjustment, or prior authorization confirmation. |
| Dispense Fill Status | RxFill, RxFillIndicatorChange |
Pharmacy → Prescriber: Notifies the prescribing EHR whether the patient picked up the medication (Dispensed), partially filled it (Partially Dispensed), failed to pick it up (Not Dispensed), or transferred the prescription to another pharmacy—providing objective primary medication adherence data. |
| Medication History | RxHistoryRequest, RxHistoryResponse |
Prescriber ↔ PBM / Pharmacy Hub: Queries 12–24 months of adjudicated PBM pharmacy claims and pharmacy dispense records during emergency department triage or outpatient medication reconciliation. |
| Electronic Prior Authorization (ePA) | PAInitiationRequest, PAInitiationResponse, PARequest, PAResponse, PACancelRequest, PAAppealRequest |
Prescriber ↔ Payer / PBM: Fetches dynamic payer-specific clinical question sets (PAInitiationResponse), submits structured clinical criteria and lab attachments (PARequest), and returns real-time approval, denial, or step therapy exception determinations (PAResponse). |
| Long-Term Care (LTC) & Transfers | Resupply, Recertification, RxTransferRequest, RxTransferResponse, Census |
Facility ↔ Prescriber ↔ Pharmacy: Coordinates skilled nursing facility patient admissions/discharges (`Census`), nurse-requested medication resupplies, and pharmacy-to-pharmacy electronic prescription transfers. |
NCPDP SCRIPT Standard Version 2017071 vs. Version 2023011
Beginning January 1, 2020, CMS mandated NCPDP SCRIPT Standard Version 2017071 across Medicare Part D (retiring the legacy v10.6 standard). In June 2024, CMS and ONC finalized a regulatory update adopting NCPDP SCRIPT Standard Version 2023011—establishing a multi-year transition period during which both versions are permitted before Version 2023011 becomes the exclusive mandatory standard on January 1, 2028.
| Capability / Schema Domain | NCPDP SCRIPT v2017071 (Legacy Baseline) | NCPDP SCRIPT v2023011 (Mandated by Jan 1, 2028) |
|---|---|---|
| Controlled Substance Transfers (EPCS) | Limited electronic transfer support for Schedule II–V controlled substances between retail pharmacies. | Full structured RxTransfer transaction workflow aligned with the 2023 DEA Final Rule (21 CFR § 1306.08) allowing one-time electronic transfer of unfilled Schedule II–V prescriptions between retail pharmacies. |
| Three-Way Long-Term Care (LTC) Routing | Primarily bilateral (Prescriber ↔ Pharmacy) messaging, requiring manual workarounds for skilled nursing facilities. | Native three-way multi-party transaction routing connecting the Prescriber, Long-Term Care Facility EHR, and LTC Pharmacy simultaneously. |
| REMS (Risk Evaluation & Mitigation Strategies) | Requires out-of-band portal checks or separate fax/phone verification for FDA REMS-restricted drugs. | Expanded observation, laboratory, and patient-counseling elements within SCRIPT and ePA transactions to verify FDA REMS compliance inline. |
| Structured Sig & Patient Demographics | Introduced structured Sig segments, veterinarian prescribing, and diabetic supply qualifiers. |
Redesigned compound/product groupings, expanded patient gender identity, pronouns, preferred language, and Social Determinants of Health (SDOH) elements aligned with USCDI. |
When transmitting Schedule II–V controlled substances, NCPDP SCRIPT works in tandem with U.S. Drug Enforcement Administration (DEA) Electronic Prescriptions for Controlled Substances (EPCS, 21 CFR Part 1311) and the Ryan Haight Act—requiring NIST SP 800-63-3 Identity Assurance Level 2 (IAL2) prescriber credentialing, FIPS 140-2/140-3 two-factor authentication (2FA) at the moment of signing, and third-party certification of both the EHR and pharmacy software.
Real-Time Benefit Check (RTBC) / Real-Time Prescription Benefit (RTPB) Explained
Since January 1, 2021, section 2003 of the SUPPORT Act and CMS regulations at 42 CFR § 423.160(b)(7) have required every Medicare Part D plan sponsor to implement a Real-Time Benefit Tool (RTBT)—commonly referred to in clinical EHRs as a Real-Time Benefit Check (RTBC) or Real-Time Prescription Benefit (RTPB)—integrated with at least one prescriber EHR system. In 2024, CMS finalized adoption of the NCPDP Real-Time Prescription Benefit (RTPB) Standard Version 13 as the national transaction standard:
- Point-of-Care Trigger Before Signing: As soon as a clinician selects a medication, strength, quantity, and pharmacy in the EHR order composer—before transmitting the
NewRxmessage—the EHR fires a synchronous RTPB request to the patient’s PBM. - Patient-Specific Out-of-Pocket Cost & Formulary Status: Within 2–3 seconds, the PBM returns the patient’s exact copay or coinsurance amount at that specific retail or mail-order pharmacy, accounting for the patient’s current deductible accumulator and coverage phase.
- Coverage Restrictions & Therapeutic Alternatives: If the selected drug is non-formulary or subject to Prior Authorization, Step Therapy, or Quantity Limits, the RTPB response flags the restriction immediately in the EHR order window and presents up to several formulary-covered therapeutic alternatives along with their exact patient out-of-pocket costs—allowing the prescriber either to switch to an affordable covered alternative on the spot or click directly into the NCPDP SCRIPT
PAInitiationRequestworkflow.
How Is the NCPDP SCRIPT Standard Used in Clinical Research and Pragmatic Trials?
In pharmacoepidemiology, health services research, and pragmatic clinical trials, NCPDP SCRIPT transactions provide critical real-world data (RWD) that cannot be captured from adjudicated insurance claims alone:
- Measuring Primary Medication Non-Adherence (PMN): Traditional PBM claims databases (NCPDP Telecommunication D.0) only record prescriptions that were actually dispensed and paid for, leaving investigators blind to prescriptions that were ordered by a physician but never picked up by the patient. By linking EHR-originated NCPDP SCRIPT
NewRxorders with pharmacy-returnedRxFill(Not Dispensed) andCancelRxmessages, researchers quantify primary non-adherence and abandonment driven by high out-of-pocket copays. - Evaluating RTBC & ePA Clinical Decision Support Trials: Pragmatic cluster-randomized trials embedded in Epic and Oracle Health use RTPB and NCPDP SCRIPT ePA logs to measure whether displaying real-time out-of-pocket cost alerts at the point of prescribing reduces prescription abandonment and accelerates time-to-therapy for specialty oncology, rheumatology, and cardiometabolic medications.
Frequently Asked Questions
What is the NCPDP SCRIPT Standard?
The NCPDP SCRIPT Standard is the ANSI-accredited national electronic prescribing standard maintained by the National Council for Prescription Drug Programs (NCPDP) and mandated by CMS (42 CFR § 423.160) and ONC (45 CFR § 170.315(b)(3)). It defines the XML/JSON message schemas used by EHRs, pharmacies, and PBMs to exchange new prescriptions (NewRx), refills (RxRenewal), therapeutic changes (RxChange), cancellations (CancelRx), fill statuses (RxFill), medication histories, and electronic prior authorizations (ePA).
How is the NCPDP SCRIPT Standard used in clinical research and healthcare?
In clinical practice and health informatics research, the NCPDP SCRIPT Standard (transitioning from v2017071 to v2023011 by January 1, 2028) powers paperless outpatient and controlled-substance e-prescribing (EPCS), automates point-of-care Electronic Prior Authorization (ePA), pairs with Real-Time Prescription Benefit (RTPB / RTBC) tools to surface patient out-of-pocket costs before an order is signed, and enables researchers to measure primary medication non-adherence by linking NewRx orders to RxFill dispense confirmations.
