TL;DR
- e-Prescribing software sends structured NCPDP SCRIPT messages over a network (Surescripts in the US) to the pharmacy: new, changed, cancelled and renewed prescriptions, fill status and medication history.
- In 2026 the must-haves add electronic prescribing of controlled substances (EPCS), checks of the state prescription drug monitoring program (PDMP), formulary and real-time benefit checks, and electronic prior authorization.
- EPCS puts duties on three parties: the prescriber (an identity-proofed two-factor credential), the practice (two-person access control) and the software provider (a third-party audit before use, then every two years or on any change).
- Three different “certifications” apply: Surescripts network certification, the Drug Enforcement Administration (DEA) EPCS audit, and certification by ONC (the federal health IT certification office) only if you certify an EHR.
- Two dates to plan around: January 1, 2027 (Medicare Part D benefit tools move to the Real-Time Prescription Benefit standard, RTPB, version 13) and January 1, 2028 (SCRIPT 2023011 only).
In most e-prescribing builds, most of the work lands on one kind of prescription: the controlled substance. That’s where the software, the prescriber, and the pharmacy network each have to prove something before the pharmacy sees a single field. The rest of this guide follows one controlled-substance prescription from the prescriber’s screen to the pharmacy, and picks up each requirement where it bites.
If you’re buying a tool for a practice, the feature list and the shortlist below are for you. If you’re building prescribing into your own product, our e-prescription software development page covers that work, and the “build” section near the end covers what you sign up for.
The volume tells you how settled the plumbing is. Surescripts reports 2.64 billion e-prescriptions filled in 2025 and 32.9 million RxChange transactions, citing its 2025 Annual Impact Report (March 2026).
What Is E-Prescribing Software, and How Does a Prescription Reach the Pharmacy?
e-Prescribing software lets a prescriber create, sign and send a prescription electronically to the patient’s pharmacy, then receive changes, renewal requests, cancellations and fill notices back. In the US it exchanges NCPDP SCRIPT messages (the National Council for Prescription Drug Programs standard) over a network, mostly Surescripts, and pulls medication history and coverage data into the prescribing screen.
The path has four hops. The prescriber builds the prescription in the EHR or a standalone eRx app. If the app embeds an eRx platform, the platform formats and routes it. The network delivers it to the pharmacy. The pharmacy sends messages back: a fill notice, a change request, a renewal request.
Medicare puts the format in regulation. For Part D drugs, 42 CFR 423.160(a)(3) requires the NCPDP SCRIPT standard “in all instances other than temporary/transient network transmission failures.” Computer-generated fax is allowed only during those failures, and HL7 messages are allowed only between a sender and recipient inside the same legal entity. So a prescription leaving your organization travels as SCRIPT.
What it replaces is plain enough: handwriting a pharmacist has to read, phone calls to clarify a dose, faxed renewal requests. What it adds is a stream of structured data the prescriber sees before signing. Hospitals use it too, at discharge; the difference between e-prescribing and in-house order entry is laid out in our eRx vs CPOE comparison of ambulatory and inpatient EHRs.
Which Features Does E-Prescribing Software Need in 2026?
The list has grown since “paper to electronic” was the whole pitch. Here is what a 2026 system has to do, the standard behind each feature, and who requires it.
Two rows in that table did not exist on most feature lists a few years ago: the real-time benefit check and electronic prior authorization. Both are now written into federal standards with dates attached, covered in the next sections. The six features most guides list (an easy interface, medication history, interaction alerts, EHR integration, automated refills, compliance) are still there. Each one now has a named standard behind it, which is what you can test during a demo.
For the wider set of modules an EHR carries around prescribing, see our guide to EHR capabilities.
What Does EPCS Require of the Software and the Prescriber?
Back to our controlled-substance prescription: before it can be signed, the rules below have to be met. Electronic prescribing of controlled substances (EPCS) is regulated by the Drug Enforcement Administration (DEA) in 21 CFR Part 1311. Five requirements carry most of the weight:
- Identity proofing. The prescriber gets a two-factor credential from a credential service provider approved by the General Services Administration to conduct identity proofing that meets “Assurance Level 3 or above as specified in NIST SP 800-63-1” (the regulation’s wording; NIST is the National Institute of Standards and Technology), or a digital certificate from a certification authority cross-certified with the Federal Bridge (§1311.105). The credential is issued over two channels, such as email and mail.
- Two-factor signing. To sign, the prescriber uses two of three factors: something they know, something they are (a biometric) or something they have (a hard token separate from the computer). A hard token meets at least FIPS 140-2 Security Level 1, the federal standard for cryptographic modules (§1311.115). A biometric subsystem operates at a false match rate of 0.001 or lower (§1311.116).
- Two-person access control. At each registered location, the registrant designates at least two people to manage access. At least one must be a DEA registrant with a two-factor credential. One person enters the permission; a second approves it with their own two-factor credential (§1311.125). Signing permission must be revoked on the date it’s discovered that a hard token or other authentication factor is lost, stolen or compromised, or that the prescriber’s DEA registration has expired without renewal or been terminated, revoked or suspended.
- A third-party audit of the application. The application provider has a third-party audit before the software is used for controlled substances, and again “whenever a functionality related to controlled substance prescription requirements is altered or every two years, whichever occurs first” (§1311.300). The auditor is “a person qualified to conduct a SysTrust, WebTrust, or SAS 70 audit” or “a Certified Information System Auditor” (the regulation’s wording). Certification by a DEA-approved certifying organization is the alternative.
- Records. The application keeps the audit trail and records Part 1311 requires.
These duties land on three different parties.
Medicare adds its own threshold. Under the Centers for Medicare & Medicaid Services’ CMS EPCS Program, a prescriber whose electronic rate for Schedule II-V Part D prescriptions is 70% or higher is compliant. Under 42 CFR 423.160(a)(5), compliance actions “will commence on or after January 1, 2023.” Prescribers with 100 or fewer qualifying prescriptions a year, those in a declared disaster area and those with a CMS-approved waiver are exempt.
CMS sends non-compliance notices by email or letter, and its page (updated October 22, 2026) says the measurement year 2026 requirement is the same as 2025, because the CY 2026 Physician Fee Schedule final rule made no EPCS changes. Prescriptions for patients in long-term care facilities start counting on January 1, 2028.
State EPCS mandates sit on top, and they vary: states differ in which prescriptions and which prescribers they cover, and the rules keep changing, so there is no single count worth quoting. CMS says its program is separate from state EPCS requirements. Your state board of pharmacy is the authoritative source; check it before go-live.
Psychiatry practices carry extra controlled-substance workflow on top of this, our psychiatry EHR and EPCS guide covers it.
How Do PDMP Checks Fit Into the Prescribing Screen?
Our prescription isn’t signed yet. First the prescriber should see the patient’s PDMP report: a prescription drug monitoring program (PDMP) is a state database of controlled-substance dispensing. A PDMP check is only useful if it happens before the prescriber signs. That’s why it belongs inside the prescribing screen.
Each state decides when a prescriber must check its PDMP and what counts as a check. That changes by state and over time, so the reliable source is the state program itself; PDMP TTAC’s state profiles are the usual starting point.
On the software side, ONC and the CDC ran an “Advancing PDMP and EHR Integration” project from 2018 to 2022, and ONC’s PDMP page (updated December 10, 2025) lists what it produced: a quick start guide, an integration taxonomy, and training, auditing, data-sharing agreement (MOU) and testing guidance. The taxonomy describes the options, which we summarize in four:
Medicare’s Merit-based Incentive Payment System (MIPS) counts both steps. In its 2026 Promoting Interoperability measures (CMS QPP measures data, 2026, read October 25, 2026), e-Prescribing (PI_EP_1) requires at least one permissible prescription sent electronically using certified EHR technology, with an exclusion for clinicians who write fewer than 100 permissible prescriptions, and Query of PDMP (PI_EP_2) requires, for at least one Schedule II opioid or Schedule III or IV drug e-prescribed with certified EHR technology, a PDMP query using data from that technology. CMS lists both as required. So the PDMP check is a reporting item for MIPS clinicians as well as a safety step.
The further down that list you go, the more likely the check happens every time. It also means more state-by-state integration work, because each state runs its own program and access rules.
What Are Real-Time Prescription Benefit Checks?
The next thing on the prescriber’s screen, before our prescription is signed, is the patient’s price.
Medicare already requires it on the plan side. Under 42 CFR 423.160(b)(5), Part D sponsors must offer at least one real-time benefit tool that integrates with at least one prescriber’s eRx system or EHR and shows “enrollee cost-sharing information, clinically appropriate formulary alternatives, when available, and the formulary status of each drug presented including any utilization management requirements.”
From January 1, 2027, that tool must use the NCPDP Real-Time Prescription Benefit standard version 13 (CMS e-prescribing page; final rule CMS-4205-F2, Federal Register 2024-12842, June 17, 2024). From the same date, formulary and benefit files must use Formulary and Benefit version 60.
ONC added the prescriber side. HTI-4 (effective October 1, 2025) created §170.315(b)(4): the software sends an RTPBRequest, receives patient-specific benefit, estimated cost and alternative products, and displays them to the user in readable form.
Which NCPDP SCRIPT Version Does Your System Need?
Two versions are legal today. Only one will be on January 1, 2028.
- Medicare Part D: either SCRIPT 2017071 or 2023011 may be used until January 1, 2028; from then, entities “must exclusively use NCPDP SCRIPT standard version 2023011” (CMS e-prescribing page; final rule CMS-4205-F2, Federal Register 2024-12842, effective July 17, 2024). The adoption of 2017071 in 45 CFR 170.205(b)(1) “expires on January 1, 2028.”
- ONC certification, §170.315(b)(3): either version through December 31, 2027; on and after January 1, 2028, SCRIPT 2023011 only. Optional transactions were removed from the criterion on October 1, 2025 (HTI-4 key dates).
Moving to 2023011 is more than a version bump. When a certified module uses it, nine electronic prior authorization transactions become required (PAInitiationRequest through PANotification), along with race and ethnicity data on several transactions and the diagnosis that is the reason for the prescription (§170.315(b)(3)). For ONC’s broader rule history, see our explainer on the HTI-1 final rule and ONC certification.
Build Secure e-Prescribing Workflows That Fit Your EHR and Clinical Needs.
Surescripts Certification, the EPCS Audit, and ONC Certification: What’s the Difference?
Our prescription only reaches the pharmacy because three different checks were passed earlier, by three different bodies. A product that prescribes usually needs two of them.
The two meet in practice. Surescripts states that “all e-prescribing applications sending controlled substance prescriptions are required to provide proof” that they “have successfully completed a third-party audit according to DEA requirements.”
Embedding a certified eRx platform doesn’t always cover your own screens. DoseSpot’s ONC certification page says API-only users “must complete a separate routing certification with Surescripts in order to handle the prescription workflow in their UI,” and a separate certification “to use EPCS in their UI.”
Whichever route you take, your product holds the certification. If your EHR runs on a certified platform, certifying your EHR built on it is a separate step: scope it from day one. Our USCDI v3 and certification guide covers the ONC side.
Which E-Prescribing Software Should You Shortlist? (As of October 2026)
If you’re buying, the shortlist splits by where the prescriber works: a standalone eRx app, an eRx platform embedded in another product, or the eRx module inside the EHR you already run. Every fact below is quoted from the vendor’s own page, read on October 25, 2026. Prices are each vendor’s own published entry price, or “not published.” Identity proofing for EPCS is quoted separately by each vendor; one on this list publishes it.
Two quick filters before the demos. Match the product to the setting first: a solo prescriber, a practice on an EHR and a digital-health product have different needs. Then confirm EPCS and PDMP support for every state you prescribe in. Practices that need a full EHR rather than a standalone eRx tool should start with our guide to the best EHR for private practice. Build costs for a custom system are in our EHR software cost guide.
How Does E-Prescribing Work in a Telehealth Visit?
If our prescription is written in a video visit, the software part is the same: the prescriber signs during the visit and the prescription goes out over the same SCRIPT path. The controlled-substance rules are what change.
As DEA’s December 2025 rule summarizes it, the Ryan Haight Act lets a practitioner prescribe controlled substances by telemedicine “only after conducting at least one in-person medical evaluation,” subject to certain exceptions. The fourth temporary extension (Federal Register, December 31, 2025) authorizes a DEA-registered practitioner to prescribe Schedule II-V controlled substances via telemedicine without a prior in-person evaluation, if its conditions are met, through December 31, 2026.
A permanent “special registration” for telemedicine was proposed on January 17, 2025 and had no final rule in the Federal Register as of October 25, 2026.
What Changes When You Build E-Prescribing Into Your Own Product?
The first decision is the route.
Why build at all, when DoseSpot and DrFirst already sell audited EPCS? Often you shouldn’t. Embedding is the faster route when its screens and workflow fit your product. Building your own screens on an embedded API, or connecting to Surescripts directly, makes sense when you need your own prescribing experience, your own EPCS flow, PDMP and benefit checks inside your workflow, or one prescribing layer across several products.
Either way, some things are yours: the EPCS audit if controlled substances are signed in your interface, the identity-proofing handoff to a credential service provider, PDMP integration for each state you serve, and a business associate agreement with every vendor that touches protected health information (PHI).
The build path we follow has five steps:
- Scope the prescribing workflows: who prescribes, which schedules, which states, which pharmacies.
- Pick the route: embedded platform or direct.
- Build and test the messages: new, change, cancel, renew, fill, history; then EPCS signing and PDMP.
- Certify: network certification, then the EPCS audit before any controlled-substance prescription goes live.
- Go live with a pharmacy test set, then watch change and cancel messages for the first weeks.
We integrate with Surescripts and DoseSpot for e-prescribing. We build to Surescripts’ and DEA’s requirements, and we build PDMP and real-time benefit checks into the prescribing screen. One example: a US wellness provider’s custom EHR with doctor and patient portals, where e-prescription is built directly into the platform alongside telemedicine. If prescribing is one module of a larger system, see our custom EHR development work.
What’s Changing Next for E-Prescribing? (As of October 2026)
| Date | What changes | Status | Source |
|---|---|---|---|
| October 1, 2025 | optional transactions removed from ONC (b)(3); (b)(4) RTPB criterion available | in effect | HTI-4 key dates |
| December 31, 2026 | DEA telemedicine flexibilities end unless extended or replaced | scheduled | FR 2025-24123 |
| January 1, 2027 | Part D real-time benefit tools must use RTPB version 13; Formulary and Benefit version 60 only | final rule | CMS e-prescribing page |
| December 31, 2027 | end of the SCRIPT 2017071 transition for ONC (b)(3) | final rule | 45 CFR 170.315(b)(3) |
| January 1, 2028 | SCRIPT 2023011 only for Part D and ONC; (b)(3) modules must also certify to (b)(4); (b)(4) joins the Base EHR definition | final rule | HTI-4 key dates; CMS |
| January 1, 2028 | long-term care prescriptions count toward the CMS EPCS 70% threshold | final rule | 42 CFR 423.160(a)(5) |
Three Checks Before You Sign a Contract or Start a Build
Go back to the controlled-substance prescription this guide started with. Before it reaches the pharmacy, three things have to be true. The prescriber signs with an identity-proofed second factor, inside software that has passed its DEA audit. The PDMP report and the patient’s cost were on screen before the signature. And the message is on a SCRIPT version that will still be accepted on January 1, 2028.
Ask every vendor to show all three in a demo, with your state selected. If you’re building, put the same three on the first sprint’s plan. Mindbowser builds e-prescribing into EHRs and digital-health products. If your product also needs data from Epic or other EHRs, ConnectHealth connects it over FHIR and HL7. For the security side of handling prescription data, our Guide to HIPAA Compliance eBook is a free download.








BLOGS
NEWSROOM
CASE STUDIES
WEBINARS
PODCASTS
ASSET HUB
EVENT CALENDAR 


















