EHR integration
EHR integration services: HL7 v2, FHIR R4 and SMART on FHIR, done properly.
Clarigo Infotech provides EHR integration services for healthcare software companies, clinics and digital health teams. Our HIPAA-trained team connects your app to EHR and EMR systems through HL7 v2 interfaces, FHIR R4 APIs and SMART on FHIR apps that launch inside the clinician's workflow, using integration engines where they help. We map the data, handle identity matching and errors, and test against sandbox and real interfaces before go-live. The same approach powers the HL7 and FHIR interoperability in our own Clarigo EHR, and you own every interface we build.
10+
Years of delivery
600+
Projects delivered
20+
Countries served
25-30
Days to a live MVP
Get a free consultation
Tell us what you need. A senior engineer replies within one working day.
What our EHR integration services cover
HL7 v2 interfaces
ADT, scheduling, orders and results messages over MLLP or SFTP, with mapping, acknowledgements and retry handling.
FHIR R4 APIs
Read and write Patient, Appointment, Encounter, Observation and other resources through the EHR's FHIR API.
SMART on FHIR apps
Apps that launch from inside the EHR with the right patient and user context, authorized through OAuth 2.0.
Integration engines
Build and maintain interfaces in engines such as Mirth Connect, or a lightweight custom service when that fits better.
Data mapping and matching
Code systems, units, patient matching and duplicate handling, agreed and documented field by field.
Monitoring and support
Alerts for failed or queued messages, replay tools and 24/7 support, because interfaces break when upstream systems change.
How we approach EHR integration
HL7 v2 or FHIR?
HL7 v2 is the long-standing messaging standard inside hospitals: pipe-delimited messages such as ADT for admissions and ORU for results, pushed as events happen. FHIR is the modern REST and JSON standard, better for apps that query data on demand. Most real projects use both: FHIR for app reads and writes, and HL7 v2 feeds where the EHR only sends events that way.
How SMART on FHIR works
SMART on FHIR lets an app launch inside the EHR. The EHR passes a launch context, the app requests scopes such as patient-level read access through OAuth 2.0, and the user's identity comes through OpenID Connect. The app then calls the FHIR API with that token. Each EHR vendor has its own registration and review steps before production access is granted.
US Core and real-world data
In the US, certified EHRs must offer standardized FHIR APIs, and US Core profiles define the expected fields. In practice, two EHRs can still fill those fields differently, leave optional data empty or support only some write operations. We test against each target EHR's sandbox and real data samples, and design the app to cope with missing or unexpected values without failing.
When an integration engine helps
An integration engine receives, transforms and routes messages between many systems, with queues, retries and monitoring built in. It earns its place when you connect several EHRs or hospital feeds. For one modern FHIR API, a small custom service is often simpler. Either way we log every message, protect PHI in transit and at rest, and alert on failures before staff notice missing data.
How it works
Week 1: discovery and PHI mapping
We map every place patient data is created, stored and sent, agree the minimum data each feature needs, and confirm BAAs with every vendor that will touch PHI.
Weeks 2-3: build and integrate
Senior engineers build in short sprints with access control, encryption and audit logging from day one, connect your EHR and other systems, and demo every week.
Week 4: test, security checks and launch
We test with realistic de-identified data, run security checks on access, logging and encryption, fix what they find, then deploy to your own HIPAA-eligible cloud account.
After launch: 24/7 support
The same team stays on with 24/7 support, monitoring, patching and new features, and keeps the security documentation up to date as the product changes.
See what we've built
Try it yourself, free
Free browser tools from our team. No sign-up needed.
Questions we hear most
Which EHRs can you integrate with?+
Most EHRs that offer FHIR APIs, HL7 v2 interfaces or a vendor API. The deciding factors are what the EHR supports, which access program it requires and what the clinic approves, so we confirm those in discovery before quoting.
What is the difference between HL7 and FHIR?+
Both are standards from HL7 International. HL7 v2 is event-based messaging widely used inside hospitals. FHIR is a newer REST API standard using JSON resources, better suited to apps. Many integrations use both.
How long does an EHR integration take?+
A read-only FHIR integration against an open sandbox can take a few weeks. Production access often depends on the EHR vendor's review and the clinic's approval, so we start those early and build against sandbox data meanwhile.
Do you build SMART on FHIR apps?+
Yes. We build apps that launch from inside the EHR with patient and user context, using OAuth 2.0 and OpenID Connect, and help with the vendor's registration and review process.
Is the integration HIPAA compliant?+
We build it to HIPAA expectations: encrypted connections, least-privilege scopes, audit logs and hosting under a BAA. Overall compliance also depends on your policies and your vendors' agreements, which we help you check.

