EHR IntegrationHealthcare Interoperability

ScriptSure eRx API: Integration Guide for EMRs (2026)

November 18, 202615 min readUpdated Nov 18, 2026
Written by
Jitendra Choudhary
Jitendra Choudhary

CTO & Co-Founder

CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

ScriptSure eRx API: Integration Guide for EMRs (2026)

ScriptSure is the e-prescribing product of D.A.W. Systems, Inc., usually written DAW Systems. DAW sells it to software platforms as an embedded module or an API, and to providers as a stand-alone app. There is no public API reference: DAW hands out documents and credentials with staging access, after contracting.

This guide is for a product lead at an EMR, telehealth or specialty software company who wants to add prescribing through ScriptSure. It is written for teams planning EHR and EMR integration work. It covers the integration models, how access works, what the integration covers, the published prices and timelines, and what DAW leaves unpublished. Two med spa EMRs, Aesthetic Record and Prospyr, already run ScriptSure inside their products. Their help centers show how it looks from the platform side. For a vendor with the same "documents after contract" model, see our MatrixCare integration guide. Last checked: Nov 18, 2026.

ScriptSure eRx API at a glance

Question Short answer
Who grants access? DAW Systems sales, at sales@dawsystems.com or (866) 755-1500 x1. Access opens in four steps that end in a contract and staging access.
Who signs? Every account signs a contract, generally for 12 months, and a business associate agreement with DAW. Each prescriber verifies identity with ID.me.
Are there public documents? No public API reference. Documents, credentials and support come with staging.
Which routes exist? Three models: Core (fully embedded), Advanced (hybrid) and Headless (API only).
What does it cost? Platform pricing is not published. Provider list price is $45 a month plus $65 a year for ID proofing, or $500 a year.
How long does it take? DAW says the embedded route can be integrated "in days" and a full native API build typically takes 4 to 6 weeks.
What is the biggest limit? No open sandbox, and staging has no production connectivity or live data.

What can you build on a ScriptSure integration?

Eight use cases follow. Each rests on a function DAW documents and points to a row in the table of what is possible (section 6). Build complexity and the build estimate are our own, and they count engineering time after staging access opens.

Eight use cases. Complexity is our own rating. Open a use case below for the detail.
1. Add e-prescribing to a specialty EMR
  • Who it is for: med spa, dental, hospice and behavioral health EMRs.
  • The value: providers prescribe from the chart without a second login, and the EMR does not build its own Surescripts link.
  • Build complexity: low.
  • How well it works: supported. DAW names EHRs, hospice, behavioral health, med spas and dentistry as the platforms it serves. Aesthetic Record documents that patient demographics and prescribing data flow "from patient charts to the virtual prescription pad". See row R1.
  • Typical build estimate: our estimate, 2 to 4 weeks on the embedded model.
2. Build your own prescribing screens on the API
  • Who it is for: EHR vendors and digital health products that want prescribing to look like the rest of their app.
  • The value: full control of the screens, with DAW handling the network, drug data and compliance underneath.
  • Build complexity: high.
  • How well it works: supported on the Headless model. DAW says "You build the UI, you control the experience, you send meds to ScriptSure's final approval surface". DAW rates this model slowest to market. See row R2.
  • Typical build estimate: our estimate, 6 to 10 weeks. DAW quotes 4 to 6 weeks.
3. Prescribe after a telehealth visit
  • Who it is for: telemedicine and virtual care platforms.
  • The value: the visit ends with a prescription sent to the patient's pharmacy, in the same product.
  • Build complexity: low to medium.
  • How well it works: DAW names telemedicine as a target market and says ScriptSure runs on any web-connected device, including tablets and smartphones. See rows R1 and R3.
  • Typical build estimate: our estimate, 3 to 5 weeks.
4. Send controlled-substance prescriptions (EPCS)
  • Who it is for: behavioral health, pain and weight-loss platforms.
  • The value: Schedule II to V drugs go out electronically, so the practice drops paper for them.
  • Build complexity: medium.
  • How well it works: supported. DAW lists EPCS for Schedules II to V and keeps the DEA certification with its own auditor. Each prescriber needs ID.me proofing and a second factor. Prospyr documents that supporting users "cannot send" controlled prescriptions directly. See row R4.
  • Typical build estimate: our estimate, 1 to 2 weeks on top of use case 2.1 or 2.2, most of it enrollment flow and testing.
5. Show the patient's drug cost while prescribing
  • Who it is for: primary care, specialty and telehealth platforms with insured patients.
  • The value: the provider sees cost and coverage before sending, so fewer scripts are abandoned at the pharmacy.
  • Build complexity: low on embedded, medium on headless.
  • How well it works: DAW lists real-time prescription benefit (RTPB) as included. See row R5.
  • Typical build estimate: our estimate, 1 to 2 weeks on headless. Included in the embedded screens.
6. Start a prior authorization from the prescription
  • Who it is for: specialty practices that prescribe drugs payers often gate.
  • The value: the prior authorization starts at the point of prescribing, and its status comes back to the platform.
  • Build complexity: medium.
  • How well it works: DAW sells ePA as its own product, FHIR-native, with notifications for "current status and payer determination". See row R6.
  • Typical build estimate: our estimate, 3 to 5 weeks.
7. Let an AI scribe draft the prescription for the provider to approve
  • Who it is for: AI documentation and clinical assistant platforms.
  • The value: the AI prepares the order, and the provider reviews and signs it without leaving the encounter.
  • Build complexity: medium to high.
  • How well it works: DAW describes this pattern, where providers "review, edit and authorize prescriptions before they are sent". See row R7.
  • Typical build estimate: our estimate, 4 to 8 weeks.
8. Bring prescription history back into the chart
  • Who it is for: any platform that keeps the medication list in its own record.
  • The value: the chart shows what was sent, so staff follow up without opening ScriptSure.
  • Build complexity: medium.
  • How well it works: DAW says prescription information "can then return to the platform", and tells teams to confirm which events the integration exposes. Prospyr documents that history arrives "via web hook" and can take a few minutes. Aesthetic Record stores a PDF record of each prescription. See row R8.
  • Typical build estimate: our estimate, 2 to 3 weeks.

The eight ScriptSure use cases compared

Use case Who it is for Build complexity Row
1. Add e-prescribing to a specialty EMR Med spa, dental, hospice, behavioral health EMRs Low R1
2. Build your own prescribing screens EHR vendors, digital health High R2
3. Prescribe after a telehealth visit Telemedicine platforms Low to medium R1
4. Send controlled-substance prescriptions Behavioral health, pain, weight loss Medium R4
5. Show drug cost while prescribing Primary care, specialty, telehealth Low to medium R5
6. Start a prior authorization Specialty practices Medium R6
7. AI draft, provider approves AI clinical platforms Medium to high R7
8. Bring prescription history back Any EMR Medium R8

How do you get access to the ScriptSure API?

You apply to DAW Systems sales, and access opens in four steps that end with a contract and a staging environment. There is no self-serve developer sign-up.

Four steps from first call to staging. No open sandbox.

The four steps DAW publishes

  1. Assess requirements and identify gaps. DAW reviews your environment, prescribing needs and technical requirements.
  2. Plan the implementation approach. You agree the integration model, scope and project plan together.
  3. Finalize the partnership. Contracting, with "the responsibilities, resources and timing needed to begin implementation".
  4. Begin the build. Your team gets "a staging environment, technical documentation and DAW support".

Who signs

All accounts sign a contract, "generally for 12 months", and a business associate agreement (BAA, the HIPAA contract for handling patient data) with DAW. On the clinical side, each prescriber goes through ID.me identity proofing before going live on the Surescripts network. For EPCS each prescriber also needs a two-factor token, an ID.me soft token or a hard token from a vendor such as Yubico.

What you do not need

DAW says your platform does not need its own Surescripts certification, because ScriptSure's certification covers the integration. It also says no separate EPCS auditor is typically required, while your organization stays responsible for its own workflows and policies.

What does ScriptSure access give you?

Staging first, with documents and credentials, and production after testing.

Environments

Stage What opens Source
Before contract Sales calls and the assessment. No sandbox.
Staging A dedicated staging environment, documents, credentials and DAW support. It stays available for the whole partnership.
Staging limits "Production connectivity and live patient or prescription data are not included."
Production Live Surescripts traffic to pharmacies, after prescribers are proofed.

The functions behind the integration

DAW lists these as part of every integration: Surescripts connectivity, EPCS for Schedules II to V, First Databank drug data with interaction and allergy checks, real-time prescription benefit, ePA from the prescribing workflow, state prescription monitoring program (PMP) checks, 12 months of medication history, compounds and order sets, and mobile web. Pharmacies can also send refill requests electronically for the provider to approve or change.

What are the ways to integrate with ScriptSure?

DAW offers three models that trade speed for control.

Speed against control, as DAW rates them.
Model What it is Speed to market Platform control Fits (our reading)
Core: Full Embedded ScriptSure's own prescribing screens inside your product, with your colors, fonts and branding. Fastest Low An EMR that wants prescribing live soon.
Advanced: Hybrid DAW calls it a "Flexible Blend" of embedded and API. Fast High A platform that wants its own entry screens and ScriptSure's final approval step.
Headless: API Only Your UI end to end, ScriptSure's engine underneath. Extended Maximum A product where prescribing must match the rest of the app.

DAW says both the embedded and the API paths carry "the same clinical capabilities and the same compliance coverage". Its certification disclosure also names REST APIs for custom data interfaces to third-party apps. HL7 v2 and FHIR for prescribing are not mentioned on any DAW page we read. FHIR appears only for the ePA product.

You can start with one product and add others. DAW sells e-prescribing, ePA and prescription routing separately.

What is possible with a ScriptSure integration?

You can prescribe, run safety and cost checks, start prior authorization and get records back. Endpoint names are not public, so the table lists functions.

What goes out, what comes back.
Row Function Direction Source
R1 Create and send a prescription to any pharmacy, from embedded screens Platform to pharmacy
R2 Send a medication from your own UI to ScriptSure's final approval step Platform to ScriptSure
R3 Prescribe on any web-connected device, tablets and phones included Both
R4 EPCS for Schedules II to V, with ID.me proofing and two-factor signing Platform to pharmacy
R5 Real-time prescription benefit: drug cost at the point of prescribing Payer to provider
R6 Start ePA and receive status and payer determination Both
R7 Provider reviews, edits and authorizes a drafted prescription Platform to ScriptSure
R8 Prescription information back to the platform for records and follow-up ScriptSure to platform
R9 Drug interaction, allergy and dosing checks Inside ScriptSure
R10 Electronic refill requests from pharmacies Pharmacy to provider
R11 12 months of medication history and state PMP checks Into the prescribing screen

What is not possible with a ScriptSure integration?

You cannot test before you sign, and you cannot read the API before staging.

What to get in writing from DAW.
  • No open sandbox. DAW says it "does not provide a publicly accessible sandbox". The workaround is to ask for a staging timeline in the contract.
  • No live data in staging. Plan a production pilot with one practice before rollout.
  • No public list of events back to the platform. DAW tells teams to "establish which prescription events are available". Get that list in writing before you design follow-up screens.
  • A sent prescription is not a picked-up one. DAW states this, so do not mark medications as taken on a "sent" event.
  • Supporting users cannot send controlled drugs alone. Prospyr documents that a provider must approve them.
  • ONC certification covers ambulatory care only. Inpatient use needs a separate check with DAW.

What are the ScriptSure integration limits?

DAW publishes the functional limits below. It does not publish rate limits, quotas, a list of webhooks or an uptime contract.

Limit What DAW says Source
Sandbox None open. Staging after onboarding.
Staging data No production connectivity or live data.
Medication history 12 months.
Care setting ONC certification is for ambulatory care.
Browser Web app on web-connected devices, Chrome recommended.
Rate limits, quotas, webhooks, SLA Not published.
Downtime DAW states under 1 hour of unplanned downtime in 10 years. DAW's own figure.

How much does a ScriptSure integration cost?

DAW does not publish platform or API pricing. It asks larger organizations to contact sales. What it does publish is per-provider pricing and the types of fees.

List prices from DAW's own pages and one EMR partner.

Per-provider list prices

Source Price Source ID
Provider sign-up page $45 a month plus $65 a year for ID proofing, or $500 a year with ID proofing included
ONC certification disclosure $60 a month per provider, before discounts

Fee types in the certification disclosure

  • Each DEA-licensed user, or user with an NPI on their profile, incurs a charge.
  • EPCS carries additional fees, and a third party can charge for the two-factor token.
  • Document storage, custom reports and patient-data export carry fees.
  • Custom data interfaces to third-party apps are "typically a one-time fee", sometimes with maintenance fees.

What one EMR partner charges

Aesthetic Record publishes its own eRx prices per prescriber: EPCS $295 for 6 months or $505 a year, non-EPCS $235 for 6 months or $397 a year. These are Aesthetic Record's prices to its customers, not DAW's price to platforms.

Build it yourself instead?

DAW estimates that building your own Surescripts connection takes 12 to 18 months and upward of $500,000. That is DAW's figure, not a measured one.

How long does a ScriptSure integration take?

DAW quotes days for embedded and 4 to 6 weeks for a native API build. It does not publish the time from first call to staging.

Stage What DAW says Source
Sales to contract Not published.
Contract to staging Not published.
Embedded build "can be integrated in days"
White-label UI "days or weeks"
Full native API "typically take 4 to 6 weeks"
EPCS set-up for a practice "Typically less than a week"

How do you build a ScriptSure integration, step by step?

The order is commercial first, then staging, then prescriber enrollment and a production pilot.

The commercial path

  1. Email sales@dawsystems.com with your platform type, model choice and prescriber count.
  2. Go through DAW's assessment and planning steps, and get the integration model in writing.
  3. Sign the contract and the BAA.
  4. Receive staging access, documents and credentials.

The build

The headless model end to end.
  1. Map your patient, provider and location records to what ScriptSure needs. Prospyr's set-up asks for locations with address, phone and fax, and for each prescriber's NPI, state license and DEA number.
  2. Build the launch into ScriptSure (embedded) or the API calls to the final approval step (headless).
  3. Agree the events that come back and build the write-back to your chart.
  4. Test every exception in staging: missing data, failed sends, a controlled drug sent by a supporting user.

Prescriber enrollment and go-live

Enrollment steps. DAW publishes no time for them.
  1. Each prescriber completes ID.me proofing.
  2. EPCS prescribers add a two-factor token. Aesthetic Record documents that adding a DEA number in ScriptSure auto-enrolls EPCS.
  3. Go live with one practice, then roll out.

Which ScriptSure quirks should you know?

These come from DAW's own pages and from the two EMR partners' help centers.

DAW's pages give two provider prices

The sign-up page says $45 a month, and the certification disclosure says $60 a month retail. Ask which applies to your users.

EPCS fees are stated both ways

The disclosure lists additional EPCS fees, and a DAW blog says EPCS is "included at no extra cost". Get it in the contract.

Award and age figures vary

DAW's pages give different counts for its Surescripts awards and its years in business. If your buyers care about these figures, ask DAW for the current ones.

Headless is the slow path

DAW rates API Only as "Extended" for speed to market.

Leavers stay in eRx

Aesthetic Record documents that removing a person from its EMR "will not remove them from eRX". Build an offboarding step that inactivates the prescriber in ScriptSure too.

History is not instant

Prospyr documents that sent prescriptions can take a few minutes to appear: "It may take a few minutes to appear via web hook." Show a pending state.

Email clashes

Prospyr documents a workaround for a prescriber email already used in ScriptSure: add +1 before the @.

Cancelling goes through the EMR

Users who get ScriptSure through an EMR cancel through the EMR's support, not DAW's billing page.

What should you check before you sign with DAW Systems?

Get the unpublished parts in writing: platform pricing, staging timing, the event list and support terms.

Security and compliance, as DAW states them

DAW lists HTI-4, Surescripts, DEA and EPCS, HIPAA, SOC 2 and DirectTrust, and NCPDP 2023 standards. Its ONC certificate is 15.04.04.2919.Scri.03.02.0.231102 for ScriptSure Cloud v3.0, certified Nov 2, 2023. It moved to NCPDP SCRIPT 2023011 in January 2025. Ask for the SOC 2 report itself. The pages describe the program but do not attach the report.

Testing

Staging has no live data, so plan a pilot practice in production. Test exceptions as well as the happy path, which DAW also advises.

Support

DAW support runs Monday to Friday, 9 a.m. to 6 p.m. ET. Agree who answers provider calls: your support team or DAW's.

Questions to ask DAW before you sign

  1. What does the platform license cost, per prescriber or per transaction, and are EPCS and ePA included?
  2. How long from signature to staging access?
  3. Which prescription events come back to our platform, and by which mechanism?
  4. What are the rate limits and the uptime commitment?
  5. Who supports providers after go-live, and how are outages announced?
  6. Can we see the SOC 2 report?
  7. What does a move from embedded to headless later involve?
  8. When a prescriber leaves our platform, how is the ScriptSure account inactivated?

What is the next step for a ScriptSure integration?

A short scoping call settles the model, the build and the questions for the DAW sales call.

For the standard underneath every ScriptSure prescription, see our NCPDP SCRIPT standard guide. For ScriptSure inside med spa EMRs, see the Aesthetic Record integration guide and the Prospyr integration guide. For prescription data inside Veradigm EHR, see our Allscripts and Veradigm integration guide.

Ready to scale?

Talk to our healthcare engineering team about building, integrating, and shipping faster.

Frequently Asked Questions

Who makes ScriptSure?

D.A.W. Systems, Inc., known as DAW Systems. The first version of ScriptSure dates from 1985.

Does ScriptSure have a public API?

No public API reference is published. DAW provides documents and credentials with staging access, after contracting.

Does ScriptSure have a sandbox?

No open sandbox. DAW gives a dedicated staging environment once onboarding begins, without live data or production connectivity.

What are the ScriptSure integration models?

Core (fully embedded), Advanced (hybrid) and Headless (API only).

Do we need our own Surescripts certification to use ScriptSure?

DAW says no. Its certification covers the integration.

Does ScriptSure support EPCS?

Yes, for Schedules II to V. Each prescriber needs ID.me proofing and a two-factor token.

How much does ScriptSure cost?

Platform pricing is not published. Provider list price is $45 a month plus $65 a year for ID proofing, or $500 a year, on the sign-up page. The certification disclosure says $60 a month.

How long does a ScriptSure integration take?

DAW says days for the embedded model and typically 4 to 6 weeks for a full native API build.

Does ScriptSure support electronic prior authorization?

Yes. DAW sells ePA as a FHIR-native product with status and payer determination notifications.

Which EMRs use ScriptSure?

Aesthetic Record and Prospyr document ScriptSure in their help centers, and DAW's home page shows Boulevard, PDCRx and PracticeQ.
Share