eRx & EPCS

Electronic prescribing is the backbone of the ambulatory medication workflow — and the gap between "can e-prescribe" and "can e-prescribe controlled substances" is the difference between a convenient feature and a regulatory mandate. The eRx & EPCS module connects the prescriber to >95% of US pharmacies through the Surescripts network for routine prescriptions, renewal workflows, and real-time pharmacy-benefit cost checks, and wraps controlled-substance prescribing in the DEA-mandated two-factor EPCS envelope (IAL2 identity proofing, AAL2 MFA, FIPS 140-2 digital signature). Because REV.health is a single platform spanning all of a patient's care relationships, the medication history accumulates longitudinally across every prescribing org, giving the DUR engine a more comprehensive view than any single EHR could offer.

Key Capabilities

Persona Connections

Three personas interact with eRx & EPCS daily. The Doctor signs every Rx and needs EPCS two-factor for controlled substances. The Patient requests refills and views medication cost transparency. The MA processes renewal requests and reconciles medication lists under standing orders.

Technical Highlights

AreaStandard / ProtocolDetail
Message format NCPDP SCRIPT 2017071 NewRx, RxRenewal, RxChange, CancelRx, FillStatus, RTPB, ePA — all via Surescripts-certified connector
EPCS compliance DEA 21 CFR 1311 IAL2 identity proofing (ID.me), AAL2 two-factor, FIPS 140-2 HSM digital signature, Drummond third-party app certification
DEA integration DEA number verification DEA registration validity and Schedule authority checked at sign time; EPCS token enrollment per (Provider, Org) pair stored in ControlledSubstanceAuth
Network routing Surescripts ~95% of US dispensing pharmacies. REV.health certifies directly; DrFirst contracted as standby. Message audit with 7-year encrypted retention
PDMP gateway Bamboo Health / LogiCoy State-by-state API; mandate-aware query enforcement blocks Rx when state law requires an unsatisfied PDMP check
Coding vocabulary RxNorm / NDC RxCUI or NDC on every Prescription row; structured SIG to SCRIPT fields; MHX feed populates longitudinal medication list
CDS invocation CDS Hooks 2.0 DUR engine (DDI, drug-allergy, drug-condition, dose-range) invoked at orders-sign hook; rules authored and versioned in Coding / CDS module

Phase Roadmap

Phase 1 — Foundation
  • Basic e-prescribing via Surescripts NewRx and CancelRx
  • Manual Rx for controlled substances (phone/fax to pharmacy)
  • Simple pharmacy search by name or NCPDP ID
  • RxRenewal/RxChange inbound inbasket (approve/deny)
  • Medication History (MHX) import on chart open
Phase 2 — EPCS & Formulary
  • EPCS two-factor signing for Schedule II–V (IAL2 + AAL2 + FIPS 140-2)
  • RTPB real-time pharmacy-benefit cost at prescribing
  • Formulary check with on-formulary alternatives
  • PDMP query integration with mandate-aware enforcement
  • ePA via Surescripts for pharmacy-benefit prior authorization
  • DUR engine invocation via CDS Hooks at orders-sign
Phase 3 — Advanced Workflows
  • Compound Rx support (Surescripts Compound message type, ingredient-level NDC)
  • RxTransfer (transfer prescriptions between pharmacies)
  • EPCS soft-token option via mobile authenticator app
  • Prescription tracking dashboard with fill-status notifications
  • Automated refill-authorization rules under standing orders
  • NarxCare score integration in PDMP response

Cross-Module Connections

Try This in the Demo

Developer Reference — Entity schemas (Prescription, ControlledSubstanceAuth, PdmpQuery, FormularyCheck), EPCS auth flow, NCPDP message model, and functional/non-functional requirements: eRx & EPCS Dev Spec →