The client was losing enterprise hospital accounts because their legacy EHR lacked native e-prescribing capabilities.
Controlled Substance Prescribing for EHR Vendor
Yalantis developed a fully integrated e-prescription module with EPCS support, drug interaction checking, and real-time benefit verification, enabling the client to pass ONC certification and DEA audit on the first attempt and stop losing hospital contracts.
DEA and ONC compliance
Enterprise accounts lost after launch
Less time on refills and pharmacy calls
Be our next success story. Share details about your project and book a call with us to discuss your goals.
Certifications:
27001 2022 / 27001 2015 / 13485
Advanced IoT Core Delivery / Advanced RDS Delivery / Advanced Tier Delivery
From medical devices to industrial automation — we deliver complete enterprise solutions with regulatory compliance built-in. Everything under one roof.
Our offices
Poland
123 al. Jerozolimskie, Warsaw, 00-001
Ukraine
5 Dmytra Yavornytskoho Avenue, Dnipro, 49005
Cyprus
8 Athinon Street, Larnaca, 6023
Estonia
12 Parda, Tallinn, 10151
FAQ
-
What is EPCS and why does it require a higher level of security than standard e-prescribing?
EPCS (Electronic Prescribing of Controlled Substances) covers Schedule II–V drugs, including opioids. The DEA requires that every controlled substance prescription is signed with two-factor authentication and that prescribers undergo certified identity proofing before they can use EPCS. This is stricter than standard eRx because controlled substances carry higher abuse risk and legal consequences.
-
What authentication methods meet DEA requirements for EPCS signing?
The DEA requires authentication at NIST SP 800-63 Assurance Level. In practice, this means a FIDO2 hardware security key or a certified biometric credential bound to a verified identity. Simple phone biometrics (Face ID alone) do not meet the requirement unless they are part of a DEA-certified credentialing service that has completed the identity proofing process.
-
How did you embed a modern module into a legacy .NET monolith?
We used a micro-frontend architecture. The eRx module is a standalone .NET Core service with a React frontend that runs inside the existing application’s UI shell. It communicates with the legacy system through internal APIs for patient data and medication history but has its own deployment pipeline, database, and authentication layer. This approach avoids the risk of a full rewrite while delivering modern capabilities.
-
How fast is the drug interaction check?
Under one second. When a doctor enters a prescription, the system sends the drug, dosage, and the patient’s full medication history to First Databank’s engine. FDB returns all alerts (allergies, drug-drug interactions, therapeutic duplications, dosage warnings) in a single synchronous call. The prescription cannot proceed until the doctor acknowledges or overrides each alert.
-
What does Real-Time Benefit Check show the doctor?
Before finalizing a prescription, the system queries the patient’s insurance via Surescripts. The doctor sees whether the drug is covered, the expected copay amount, and cheaper therapeutic alternatives if available. This helps doctors prescribe medications patients can actually afford, which increases medication adherence.
-
How long did the project take from start to passing certification?
The partnership ran from 2020 to 2022. Development of the eRx module, integration with FDB and Surescripts, EPCS implementation, and preparation of all documentation for ONC and DEA certification was completed within this timeframe. Both certifications passed on the first submission.
Let’s set up a call
Leave your info and a few words about the project. We’ll review it and reach out to book a call.
Thank you for contacting us.
Keep an eye on your inbox. We’ll be in touch shortly
Meanwhile, you can explore our hottest case studies and read
client feedback on Clutch.
We are open for partnerships too
Check out our refferal program. Find out all benefits.