NCPDP SCRIPT
The e-prescribing messaging standard. NewRx, RxChange, RxCancel, RxRenewal, and medication history requests all flow through SCRIPT. It is the protocol the Surescripts network runs on.
Every healthcare app that touches prescriptions, pharmacy claims, or medication history runs through NCPDP.
The NCPDP SCRIPT standard drives every new prescription, refill, cancellation, and medication history exchange between your app and a pharmacy or prescriber system.
NCPDP Telecom handles pharmacy claim transactions to payers and PBMs.
Mindbowser builds the SCRIPT integration, directly to Surescripts or through DoseSpot, so your team ships the prescribing workflow while we handle the message layer.
#National Council for Prescription Drug Programs# publishes the messaging standards that underpin e-prescribing and pharmacy transactions across the US. Three matter for healthcare app integrations:
The e-prescribing messaging standard. NewRx, RxChange, RxCancel, RxRenewal, and medication history requests all flow through SCRIPT. It is the protocol the Surescripts network runs on.
The standard for real-time pharmacy billing and claims. When a pharmacy adjudicates a claim at the point of dispensing, Telecom is the protocol running underneath.
The 7-digit identifier assigned to each pharmacy in the network. Prescriber workflows need accurate NCPDP number routing to reach the correct dispensing location.
The NCPDP SCRIPT standard defines message format, transaction types, and acknowledgement behavior for electronic prescription exchange. Surescripts mandates SCRIPT compliance for any app connecting to its network which means most e-prescribing use cases require SCRIPT implementation before a single prescription can be sent. Key compliance requirements:
Surescripts publishes the SCRIPT version its network requires, and integrations move when it does.
SCRIPT messages are synchronous or asynchronous depending on type. NewRx and RxCancel are typically acknowledgement-based; MedHistory is request-response.
Every SCRIPT message requires a proper Status or Error response. Apps that don't handle acknowledgements correctly fail certification.
Electronic Prescribing for Controlled Substances adds identity-verification requirements on top of SCRIPT, separate from the message format. Mindbowser builds to DEA's EPCS requirements; the audit and certification belong to your product.
More on EPCS in psychiatry EHRs →Every pharmacy connected to the Surescripts network has a 7-digit NCPDP provider ID. This number identifies the dispensing location when a prescription message is routed a NewRx sent without a valid NCPDP number doesn't reach the right pharmacy. In practice, this creates two integration problems:
Prescribers have NPI numbers; pharmacies have NCPDP IDs. When a patient selects a pharmacy, your app needs to resolve that pharmacy's NCPDP number to route the prescription correctly. The integration resolves the pharmacy's NCPDP ID before the message is sent, so your app can pass the identifiers it already uses.
If your app lets patients pick a preferred pharmacy, it needs an NCPDP-indexed pharmacy directory. The integration uses the e-prescribing network's directory, so your team doesn't build its own lookup.
Collaborating with Industry Leaders for Smarter Healthcare
NCPDP (National Council for Prescription Drug Programs) is the standards body that publishes messaging protocols for e-prescribing and pharmacy billing in the US. The most widely used standard is NCPDP SCRIPT, which powers electronic prescription exchange across the Surescripts network.
National Council for Prescription Drug Programs the non-profit, ANSI-accredited organization that maintains e-prescribing and pharmacy claims standards used across the US healthcare system.
NCPDP is the standards body: it publishes the SCRIPT message format. Surescripts is the network: it runs the e-prescribing infrastructure connecting prescribers, pharmacies and PBMs. Surescripts uses NCPDP SCRIPT as its message protocol, so integrating with Surescripts means implementing SCRIPT.
The version Surescripts requires on its network, directly or through DoseSpot. When NCPDP and CMS adopt a new version, we plan the upgrade with you.
An NCPDP number is the 7-digit identifier assigned to each pharmacy in the Surescripts network. Prescriptions need a valid NCPDP number to route to the correct dispensing location. The integration Mindbowser builds resolves the NCPDP number before sending, so your app doesn't run its own directory lookup.
No. ConnectHealth, our integration product, has no NCPDP or Surescripts connection. Mindbowser builds e-prescribing integrations with Surescripts and DoseSpot. If you run ConnectHealth, it can carry the EHR side of the workflow, such as reading the patient's chart before a prescription is written.
Your product does. Mindbowser builds to Surescripts' and DEA's EPCS requirements; the certification and the EPCS audit belong to your product.
We don’t just deliver solutions we build partnerships that drive transformation. With a proven track record in healthcare technology, we understand the industry’s unique challenges and offer customized solutions to help you achieve breakthroughs.

From leading hospitals to digital-health companies, Mindbowser powers real-world healthcare transformation.
HIPAA-ready builds with controlled PHI access, secure environments, and disciplined engineering practices. Designed to reduce vendor risk and speed up onboarding.

Independent audit of security controls operating over time.

PHI safeguards built into access, environments, and release workflows.

Data handling built for modern privacy expectations.
Role-based access with controlled PHI exposure.
Code reviews, dependency checks, and security gates.
Secure integrations designed for traceability and reliability.
Partner with us to design, build, and scale digital solutions that drive better outcomes.
Global Tech Teams LLC, 525 Washington Blvd, Industrious at Newport Tower, Jersey City, NJ 07310, United States.
Let’s discuss your goals, workflows, and next steps in a focused consultation call.