In short
- The fastest HIPAA-ready path to a startup's first EHR integration is to connect to the one EHR your first paying customer runs, start read-only on the standard FHIR APIs certified EHRs must offer, and add writes only after that customer sees the product working.
- Before PHI flows, a startup acting as a business associate needs a written BAA with its customer, BAAs with its own subcontractors that touch PHI, and the risk analysis the HIPAA Security Rule requires.
- Vendor developer programs, such as Epic's no-fee open.epic, and integration platforms both work for startups, and the choice depends on how many EHRs your first customers run.
A startup's first EHR integration should connect to one EHR, the one its first paying customer runs, using that EHR's standard FHIR APIs in read-only mode. Put the HIPAA basics in place before any PHI flows: a BAA with the customer, BAAs with your own vendors that touch PHI, and a documented risk analysis. Add writes and a second EHR only after the first customer is live.
This guide is for founders and early CTOs of digital health companies who need EHR data to sell, and who have more ambition than engineering budget.
Do you need to be HIPAA compliant before your first EHR connection?
Yes, if your product will create, receive, maintain or transmit electronic PHI for a covered entity such as a practice or health system. The Security Rule at 45 CFR 164.308(b)(1) lets a covered entity permit a business associate to do that only if it obtains satisfactory assurances that the business associate will protect the information, documented in a written agreement.
That agreement is the BAA. Under 45 CFR 164.504(e), it must set out the permitted uses and disclosures of PHI, require appropriate safeguards and Security Rule compliance for electronic PHI, require you to report uses or disclosures the contract does not allow, including breaches, and require that your subcontractors agree to the same restrictions. It also covers returning or destroying PHI at the end of the contract and lets the covered entity terminate if you materially violate it.
The subcontractor clause is easy to miss. Your cloud host, database service, error tracker, email provider and any AI service that sees PHI each need their own BAA with you, or they must never receive PHI. List them before you write the first line of integration code.
What does the HIPAA Security Rule expect from a small team?
The Security Rule scales to your size, but some items are required for everyone. Start with these two from 45 CFR 164.308.
- Risk analysis: an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of the electronic PHI you hold.
- Risk management: security measures sufficient to reduce those risks and vulnerabilities to a reasonable and appropriate level.
The technical safeguards at 45 CFR 164.312 give you the engineering checklist. Required items include unique user identification and an emergency access procedure. Automatic logoff and encryption are addressable specifications, which means you assess whether they are reasonable and appropriate and document the decision. The section also sets standards for integrity, for person or entity authentication, and for transmission security against unauthorized access to PHI sent over a network.
For a startup the practical version is short. Every user has their own login, nobody shares accounts, PHI is encrypted in transit and at rest, sessions time out, and you have written down why each choice fits your product. Write the risk analysis as a living document and update it when the architecture changes.
Which EHR should you integrate with first?
The one your first paying customer runs. A startup that builds a generic integration layer for five EHRs before it has a customer spends its runway on connections nobody uses. One live customer on one EHR teaches you more about data quality, approvals and support than any amount of sandbox work.
If your pipeline is spread across many EHRs, ask which customer will sign first and start there anyway. Keep your own data model in the middle so the second EHR maps into the same shape.
What does the cheapest useful first integration look like?
Read-only, on standard APIs. EHRs certified to ONC's §170.315(g)(10) criterion must offer FHIR R4 with US Core and SMART App Launch, with USCDI as the data set and documentation at a public link. That covers medications, problems, allergies, lab results and the other USCDI data most products need first.
Vendor programs for that floor can be inexpensive to start. Epic's open.epic, for example, lists no membership fee, with public APIs, a sandbox and data sharing playbooks. Its Vendor Services program costs $1,900 a year and adds private APIs and support from Epic representatives billed hourly, which most startups do not need for a first read-only integration.
Use SMART App Launch the way the guide describes. Discover the server's endpoints from its .well-known/smart-configuration, use PKCE with the S256 method, validate the state parameter, and keep tokens on your server where you can protect them.
Should a startup use an integration platform instead?
Sometimes. An integration platform gives you one API across many EHRs, which helps when your first customers run different systems and you need the same data from each. It also adds a vendor with access to PHI, so it needs a BAA, and its fees become part of every connection's cost.
- One EHR, deep workflow, or specific write-back: go direct to the vendor.
- Several EHRs, the same reads everywhere, a small team: consider a platform.
- Records from organizations you do not work with: look at national networks instead.
What will your first health system customer ask?
A startup gets the same security review as an established vendor. Prepare the answers before the first meeting.
- A data flow diagram showing what leaves the EHR, where it is stored, for how long, and who can see it.
- The list of APIs and scopes, with the feature that uses each one.
- Your subcontractors that touch PHI and the BAAs you have with them.
- Your encryption approach and key management.
- Your risk analysis and incident response plan, with named contacts.
- Penetration test results.
- How access is limited inside your product.
We sign a BAA before anyone on our team sees PHI, run a penetration test before launch, and scope access so each clinician sees only their own patients. Have your own answers on those three points ready in writing.
What mistakes cost startups the most?
- Building for many EHRs before the first customer is live.
- Sending PHI to a logging, analytics or AI service without a BAA.
- Requesting broad scopes. Ask only for what each feature needs, because every extra scope is a question in review.
- Promising write-back in the sales deck before confirming the API exists and the customer will enable it.
- Testing only in a vendor sandbox, which uses example data, and discovering the customer's configuration at go-live.
- Leaving credentials and keys in a contractor's account. Register developer accounts in your company's name.
When should a startup add write-back?
After the first customer is using the read-only product and asks for it. Writing into the chart changes what clinicians see and act on, so expect each write to get a closer review than the reads did, and each write is its own vendor API with its own rules. Adding them one at a time keeps each review small.
Pick the first write by its value to the customer, even when another write would be easier. A remote monitoring startup might start with filing readings, an intake startup with questionnaire answers. Design the failure path before the happy path: queue the write, retry transient errors, and show users when data has not reached the care team yet.
In what order should a startup do the work?
- 1. Sign the customer and confirm which EHR and version they run.
- 2. List the data each feature needs, marking reads and writes.
- 3. Sign BAAs with the customer and with every subcontractor that will touch PHI.
- 4. Write the risk analysis and fix what it finds.
- 5. Register with the EHR vendor's developer program and build read-only against its sandbox.
- 6. Test in the customer's non-production environment, then go live with a few users.
- 7. Add writes one at a time, then the second EHR.
Onix Systems has built software since 2000 and has more than 370 engineers. We have shipped Epic and athenahealth integrations, and for any vendor platform we work from the vendor's documentation and sandbox. If you are planning your first EHR integration, talk to one of our engineers. Our free five-day technical audit ends with a written report covering the route, the agreements and the order of work.
Sources
- 45 CFR 164.308: Administrative safeguards (Cornell LII)
- 45 CFR 164.504: Uses and disclosures, organizational requirements, business associate contracts (Cornell LII)
- 45 CFR 164.312: Technical safeguards (Cornell LII)
- ONC (ASTP): §170.315(g)(10) Standardized API for patient and population services
- open.epic: Developer Support (open.epic vs Vendor Services)
- HL7 SMART App Launch 2.2.0: App Launch