The short answer
CMS describes e-prescribing as electronically sending a prescription from the point of care directly to a pharmacy. For controlled substances, EPCS adds practitioner and application requirements under 21 CFR part 1311. Evaluate EPCS, ordinary e-prescribing, and PDMP access as separate workflows. Before deployment, verify the configured application, signing process, permissions, audit evidence, supported transactions and pharmacies, failure handling, downtime recovery, and rules applicable to each location and medication workflow.
What is e-prescribing integration?
E-prescribing integration connects prescribing functions in a behavioral health record with external prescription recipients. Depending on the configured product, a clinician may be able to create prescriptions and exchange supported new-prescription, change, cancellation, renewal, fill-status, medication-history, status, error, and verification messages; those are among the transactions identified in the ASTP/ONC electronic-prescribing criterion.
An integration may also present available medication and allergy data and support electronic routing to a selected pharmacy. Test data completeness, patient and pharmacy matching, alert behavior, transaction acceptance, rejected or failed messages, and reconciliation rather than assuming that a shared screen or certification establishes successful delivery or a complete medication record.
Why prescribing friction matters more in behavioral health
Prescribing workflows should account for medication continuity, patient safety, and program scope without assuming every behavioral health organization prescribes the same medications:
- Medication-specific workflows differ. Map prescribing, dispensing, administration, and documentation separately for each medication and care setting instead of assuming that all medications used in opioid-use-disorder treatment follow one process.
- Medication reconciliation needs explicit ownership. Record the source, status, and last reconciliation of each medication; multiple prescribers, pharmacies, and patient-reported use can leave gaps that decision support cannot resolve automatically.
- Transitions create handoffs. At admission, transfer, and discharge, identify who reconciles current medications, determines the status of existing orders, and handles new or renewal requests.
- Controlled substances need a distinct electronic workflow. Evaluate electronic controlled-substance prescriptions under 21 CFR part 1311. Separately, ASTP/ONC states that its general electronic-prescribing certification criterion does not require controlled-substance support.
Manual and electronic workflows have different risks. Evaluate transcription, routing, identity matching, alert design, overrides, unavailable pharmacies, outages, and reconciliation using the organization’s actual volume and error data.
What EPCS adds on top of standard e-prescribing
EPCS applies DEA requirements to applications and practitioner workflows used to create, review, sign, and transmit electronic prescriptions for controlled substances. For product evaluation, inspect these functions separately rather than treating EPCS as a single enabled setting:
- Credential onboarding. For individual practitioners, 21 CFR 1311.105 addresses obtaining a two-factor authentication credential and identity proofing. Ask the vendor to map the applicable onboarding route, responsible parties, credential replacement, and revocation process; do not equate a general EHR login with EPCS credentialing.
- Authentication at signing. The signing provisions in 21 CFR 1311.120(b)(5), (11), and (13) place two-factor authentication in the signing process, before subsequent transmission. Paragraph (b)(13) governs the conditions for using one authentication invocation in a multiple-prescription signing process; do not describe every prescription transmission as requiring a new authentication invocation.
- Readiness and logical access. 21 CFR 1311.120(b)(2) and (10) distinguish permissions for indicating readiness for signing, signing, and administering logical access controls from preparation of prescription data. During testing, confirm what each role can prepare, mark ready, sign, and administer.
- Audit evidence. Ask the vendor to demonstrate the auditable events, protected audit records, review workflow, retention, and export produced by the configured EPCS application, then map that evidence to the applicable provisions of 21 CFR 1311.120. A generic activity log does not establish the scope of EPCS audit evidence.
EPCS capability answers whether a configured workflow can handle an electronic controlled-substance prescription; it does not establish whether electronic transmission is required in a particular case. Evaluate the applicable medication, practitioner, patient and prescriber locations, pharmacy, payer or program, and current jurisdictional rules.
Standard e-prescribing vs. EPCS, side by side
| Dimension | Standard e-prescribing | EPCS |
|---|---|---|
| Federal source relevant to evaluation | For Medicare Part D, CMS identifies the adopted electronic-prescribing standards and transition dates, including the transition from NCPDP SCRIPT version 2017071 to version 2023011. Those Part D requirements are not a universal summary of every federal program, certification, transaction, or state rule. | DEA practitioner and application requirements in 21 CFR part 1311, considered alongside other rules applicable to the prescription. |
| Technology scope | The ASTP/ONC criterion addresses specified prescription transactions and expressly does not require controlled-substance support. | Electronic controlled-substance prescribing within the application’s supported and configured scope. |
| Prescriber setup to inspect | Organization, application, network, and program enrollment or credentialing applicable to the deployment. | The individual-practitioner credential and identity-proofing route described in 21 CFR 1311.105, where applicable, plus configured readiness, signing, and access-control roles under 21 CFR 1311.120. |
| Authentication at signing | Inspect the configured product and organizational policy. | Two-factor authentication is used in the signing process described by 21 CFR 1311.120(b)(5), (11), and (13); transmission follows signing, and the multiple-prescription process is conditional. |
| Failure visibility | Test status, error, rejection, and receipt behavior. ASTP/ONC notes that its certification criterion does not itself require an active alert when an electronic prescription fails. | In addition to failure visibility, test how the application preserves signing status, prevents duplicate transmission, and presents the next permitted action. |
| Evidence to request | Supported transaction list, validation results, routing logs, exception queues, and downtime procedure. | Configured role matrix, credential process, signing demonstration, audit evidence, independent audit or certification scope, routing logs, and downtime procedure. |
Where this fits with the rest of the record
Do not equate a consolidated medication view with a complete record. Ask where medication history originates, how identities and medications are matched, which updates return from pharmacies, how staff record patient-reported use, and who resolves conflicts during admission, transfer, and discharge.
Sunwave’s behavioral health EMR page describes prescriptions, medication orders, medication history, controlled and psychotropic substance workflows, and medication-assisted-treatment workflows. That product-page description does not establish the scope of a particular deployment. Ask Sunwave to identify the prescribing and EPCS services, supported jurisdictions and pharmacies, credential and signing workflow, access controls, audit evidence, downtime process, implementation dependencies, and contractual scope for the proposed configuration.
Test these scenarios during a vendor demonstration
- Rejected or uncertain transmission: Submit a non-production test, identify its status, locate the responsible queue, and show how staff avoid an accidental duplicate.
- Unavailable or mismatched pharmacy: Search for a representative pharmacy, confirm its identity and endpoint, and demonstrate the fallback and correction path.
- Role change: Remove or change a test user’s EPCS authority and show the effect on preparation, readiness for signing, signing, and access-control administration.
- Multiple prescriptions: Demonstrate the supported signing sequence, the prescriptions displayed, the practitioner’s selections, and when another authentication invocation is required.
- Downtime and recovery: Walk through an outage, an urgent prescription, restoration of service, reconciliation, and duplicate prevention.
- Audit and PDMP evidence: Export the records for a test prescription and separately show how a PDMP query, result, or exception is accessed and documented; prescription transmission alone is not evidence that a PDMP workflow occurred.
Sources
- eCFR — 21 CFR part 1311
- eCFR — 21 CFR 1311.105, individual-practitioner authentication credentials
- eCFR — 21 CFR 1311.120, electronic prescription application requirements
- CMS — Medicare electronic-prescribing standards
- ASTP/ONC — Electronic-prescribing certification test method
Sources reviewed September 9, 2026.
