eRx software does two jobs a prescription draft cannot: it controls an authorized prescribing workflow and transmits prescription information electronically. Physicians comparing tools should test the route to the pharmacy, prescriber identity, controlled-substance controls, responses, cancellations, and chart reconciliation. A clean draft is only the starting artifact.
Before the demo
- A prescription draft is not proof of pharmacy transmission.
- Standalone eRx can work without replacing the current EHR.
- EPCS brings identity proofing, two-factor authentication, and access-control work.
- Patient Square claims prescription drafts, not a pharmacy network or EPCS capability.
Draw the boundary before comparing vendors
A physician says, “amoxicillin 500 milligrams, three times daily,” and software puts the words into a tidy card. That may save typing. It hasn’t prescribed anything.
Electronic prescribing adds the controlled act of sending prescription information through an electronic workflow governed by applicable standards. CMS maintains standards for Part D electronic prescribing and is transitioning covered transactions to NCPDP SCRIPT version 2023011 beginning January 1, 2028 (CMS e-prescribing standards). A screenshot with drug and dose fields doesn’t prove that path exists.
Use four labels during procurement:
| Output | What it proves | Evidence to request |
|---|---|---|
| Medication suggestion | The software proposed text | Source of the suggestion and clinician confirmation step |
| Prescription draft | The software prepared editable fields | Required review, edit history, and discard behavior |
| Electronic prescription | An authorized order can be transmitted | Named network or route, supported transactions, pharmacy response, audit trail |
| EPCS | Controlled substances can be prescribed electronically | DEA-compliant application evidence, identity proofing, two-factor authentication, logical access controls |
These aren’t maturity levels. A practice may want drafts but deliberately keep prescribing in its existing EHR. Trouble starts when a buyer treats one row as evidence for the next.
Standalone software is a real option
CMS’s 2026 EPCS setup guide says some e-prescribing programs connect with EHRs and others run as standalone software (CMS EPCS guide). That makes the first architecture choice straightforward: keep prescribing where it already works, add a standalone tool, or replace the broader record system.
Standalone eRx may suit a locum, a small practice whose record system lacks prescribing, or a group that cannot change the incumbent EHR this year. The extra login is not the only cost. Staff must reconcile the prescription record back into the chart, prevent duplicate patient profiles, manage departing prescribers, and define what happens during downtime.
An EHR-connected option can remove some hand entry, but “integrated” needs a noun and a verb. Which patient identity crosses, and does medication history return? Staff should find out whether pharmacy responses are visible, where cancellations land, and whether the signed prescription appears in the legal record. Ask the vendor to perform each action with a fictional patient.
EPCS turns setup into a control test
For controlled substances, CMS tells prescribers to use software that meets DEA requirements. Its current quick-reference guide names identity proofing, two-factor authentication, and logical access control among the setup steps (CMS EPCS guide). Those are operational controls, not checkbox copy.
Ask who completes identity proofing, who grants prescribing access, how the second factor works, how a lost factor is replaced, and how access is revoked when a prescriber leaves. Then test an unauthorized staff account. A demo that only shows the happy path hasn’t shown the control.
The practice also needs a local policy for downtime, failed transmissions, pharmacy changes, refill requests, and a prescription sent to the wrong destination. Software evidence does not replace the prescriber’s legal authority or the organization’s response process.
The prescription-draft review
AI can make the first artifact faster and still leave the higher-risk decisions with the clinician. Review the draft in a fixed order:
- Match the patient and encounter.
- Confirm the intended drug, strength, formulation, dose, route, frequency, duration, and quantity.
- Check allergies, interactions, contraindications, renal or hepatic considerations, and the current medication list in the approved clinical source.
- Confirm pharmacy, substitution instructions, refills, controlled-substance status, and the prescriber’s authority.
- Move the verified information through the actual eRx system, then confirm its final chart record.
The AI draft must not make any of those decisions. It can reflect what the clinician said. It cannot screen, reconcile, authorize, or transmit unless the vendor has separately demonstrated those functions and the organization has approved them.
Patient Square’s claim is deliberately smaller
Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.
The public Practice Copilot page says drug, dose, route, and frequency are pre-filled from the conversation and nothing sends without the clinician’s signature. Those words establish a draft and signature gate. They do not identify a Surescripts connection, EPCS evidence, controlled-substance routing, refill exchange, or electronic cancellation workflow. Under the product claims ceiling for this article, Patient Square remains on the prescription-draft side of the boundary.
That means a practice with working e-prescribing can leave it in place. Patient Square can draft the note and prescription text for review, while the verified eRx system remains the sending system. A buyer looking for a new prescribing network should evaluate a product that proves the third or fourth row in the boundary table.
The pricing page lists Practice Copilot plan scope. It isn’t evidence of a pharmacy connection. Put that distinction in the procurement record beside the transmission evidence.
A nine-action demo script
Use fictional patients and ask every shortlisted vendor to perform the same actions:
| Action | Passing evidence |
|---|---|
| Create a routine prescription | Correct fields, named prescriber, review before send |
| Change the pharmacy before sending | Destination changes without creating a duplicate order |
| Receive a pharmacy response | Response lands with an owner and audit trail |
| Cancel or replace an order | Old and new states stay visible |
| Process a refill request | Patient, drug, prescriber, and decision remain linked |
| Attempt EPCS | Verified control path, or a plain statement that EPCS is unsupported |
| Use an unauthorized account | Action is denied and logged |
| Lose connectivity | Downtime state is clear; no false “sent” status |
| Reconcile the chart | Final prescription record appears in the approved source of truth |
Price the labor around the software after the test. Count duplicate entry, identity administration, support calls, and failure cleanup. A low subscription can be expensive if two people reconstruct every prescription in the chart.
If your need is note and draft preparation,