In short
- If you deliver care and take part in CMS programs that require certified health IT, buy a certified EHR and build only the workflows it handles badly, as apps and services on its APIs.
- A fully custom EHR makes sense mainly when your care model does not fit any EHR's assumptions and you can carry certification, interoperability and security work for as long as the system runs.
- Most teams land in the middle: buy the system of record, then extend it with SMART on FHIR apps, CDS Hooks services and their own patient-facing products.
Buy a certified EHR if you deliver care and take part in CMS programs that require certified health IT, then build only the workflows it handles badly, on top of its APIs. A fully custom EHR beats Epic or Cerner mainly when your care model fits no EHR's assumptions and you can carry certification, interoperability and security work for as long as you run it.
This guide is for CTOs, product leads and clinic IT leaders weighing build vs buy for an EHR. The choice has more than two options, and the regulatory commitments that come with building are taken from ONC's and CMS's own pages.
Build vs buy EHR: what are the options?
The question usually arrives as two options, and there are at least five.
- Buy and use as delivered. Fastest, cheapest to start, and the vendor carries certification.
- Buy and configure. Templates, order sets, workflows and reports set up for your specialty, inside the vendor's tools.
- Buy and extend. Your own apps and services connected through the EHR's APIs: embedded SMART on FHIR apps, CDS Hooks decision support, data feeds, patient-facing products.
- Buy the record, build the engagement layer. The EHR stays the system of record, and you build the product patients and care teams use every day around it.
- Build the EHR. You own the system of record, its data model and everything the regulations attach to it.
If you started by asking “should we build an EHR?”, test the third and fourth options first. Jumping to the fifth without mapping the middle is the expensive mistake, because a custom system of record is the hardest of the five to walk back.
When should you buy an EHR?
- You deliver and bill for care and need scheduling, charting, orders, results, billing and a patient portal.
- You take part in CMS programs that require certified health IT. CMS's Promoting Interoperability programs require eligible hospitals, critical access hospitals and MIPS eligible clinicians to use certified EHR technology.
- Your workflows look like those of most practices in your specialty.
- You do not want to staff a team whose permanent job is keeping an EHR certified, secure and connected.
When you buy, you can still change workflows. The vendor carries the system of record and the regulatory baseline, and your effort goes into the parts that differentiate you.
What does certification have to do with build vs buy?
A lot. ONC describes its Health IT Certification Program as voluntary, but CMS's Promoting Interoperability programs continue to require certified health IT, and ONC notes that its use has expanded to other programs. Certified products are listed on ONC's Certified Health IT Product List (CHPL).
If you buy, the vendor carries certification. If you build and your customers or your own organization need certified technology, you take on the criteria yourself. Two examples show the scale:
- §170.315(g)(10), the standardized API: a FHIR R4 API for single patients and groups, using US Core, SMART App Launch and Bulk Data, with public documentation and a requirement to revoke an app's access within one hour when a patient asks.
- §170.315(b)(11), decision support interventions: support for evidence-based and predictive interventions, source attributes users can read, user feedback that can be exported, and risk management for predictive interventions.
Those are two of many criteria, and they move. ONC's (g)(10) page lists US Core STU 6.1.0 as the referenced version, approves later versions through its standards update process, and sets dates such as a November 15, 2027 surveillance compliance date for a US Core 8.0.1 errata. A custom EHR has to keep up with every one of these updates.
When does extending a bought EHR beat both?
When the system of record is fine and a specific workflow is not. Modern EHRs publish APIs for exactly this. Epic, for example, says it offers over 750 no-cost APIs and interfaces through open.epic. Standards make the extension portable across vendors:
- SMART App Launch lets your app open inside the EHR with the current patient in context, or launch on its own with the user signing in. SMART Backend Services covers system-to-system access with no user present.
- CDS Hooks lets the EHR call your service at set points in the workflow, such as when a chart opens or an order is signed, and show your advice as cards.
- FHIR APIs, required for certified EHRs under (g)(10), give you a predictable read baseline. Writes vary by vendor and by customer.
Good candidates for extension: specialty intake and assessment tools, remote patient monitoring, care management dashboards, patient engagement apps, decision support and analytics. Each one is a product you own, built on a record you do not have to maintain.
When does a custom EHR beat Epic or Cerner?
Rarely, but it does. The strongest cases share a few traits:
- Your care model does not fit EHR assumptions. Examples include care delivered mostly outside visits, longitudinal programs that are not organized around encounters, or a data model that is itself your product.
- Certification is not a requirement for you, or you are ready to certify and maintain certification as a product line.
- You have, or will fund, a permanent team for the system: engineering, security, clinical informatics and support.
- The workflow you need is your core business and a source of advantage, too important to configure around.
- Extending a bought EHR has been tried, or carefully scoped, and cannot deliver the workflow.
If fewer than three of these are true, extending is usually the better bet. If they are all true, building can be the right call, with the commitments listed below.
What does building an EHR commit you to?
- A system of record that must be available, auditable and correct for as long as you keep records.
- HIPAA security work: risk analysis, access control, audit logs, encryption, incident response and BAAs with every vendor that touches PHI.
- Interoperability with labs, pharmacies, payers, health information exchanges and other EHRs, usually a mix of FHIR and HL7 v2.
- Patient access APIs and the app ecosystem around them.
- If you certify: every applicable ONC criterion, its updates and its surveillance.
- Clinical safety: decision support you can explain, and a process for reporting and fixing errors.
- Migration in, if you are replacing a system, and a credible export path out.
Questions to answer before you decide
- Which CMS or payer programs do you or your customers take part in, and do they require certified health IT?
- Which three workflows does your current or candidate EHR handle badly, and could an app or service on its APIs fix them?
- What data do you need to read and write, and does the EHR's API support those writes?
- Who will own the system in five years: the team, the budget and the on-call rota?
- If you build, which ONC criteria apply, and who tracks their updates?
- What is your exit plan from whichever option you pick?
How to run the decision in practice
Write each workflow that worries you as one sentence: who does what, with which data, and what goes wrong today. Then mark each one as configure, extend or build. If almost everything lands on configure or extend, buy. If the build column holds the core of your business and the list above does not scare you, build, but start with the parts that differentiate you and integrate with an existing record for the rest while you grow.
Onix Systems has built software since 2000 and has 370+ engineers. We have shipped Epic and athenahealth integrations, we sign a BAA before touching PHI, and we run penetration tests before launch. If you are weighing build vs buy, talk to one of our engineers. Our 5-day free technical audit ends with a written report on which workflows to configure, extend or build.
Sources
- ONC (ASTP): About the ONC Health IT Certification Program
- CMS: Promoting Interoperability Programs
- ONC (ASTP): §170.315(g)(10) Standardized API for patient and population services
- ONC (ASTP): §170.315(b)(11) Decision support interventions
- open.epic: homepage (no-cost APIs and interfaces)
- HL7 SMART App Launch Implementation Guide
- HL7 CDS Hooks specification