Technical evaluators and IT leads assessing integration effort
Interoperability guide
On-Kare exchanges data with EHRs, labs and payers through standard formats. This page lists what is supported today and how a new connection gets built.
What is exchanged, and how
| System | Exchange |
|---|---|
| Electronic health records | Structured records via HL7 FHIR resources; the on-kare record stays the source of truth for encounters created in it |
| Laboratories | Structured result feeds matched to the patient and encounter automatically, flagged for review if unmatched |
| Payers | Eligibility checks and claim status queries against the payer's own interface |
| Messaging | Secure patient messaging through encrypted channels, no clinical free text sent unencrypted |
How a new connection gets built
- 01
1. Scope
We confirm the target system's supported version and the data fields you need to exchange.
- 02
2. Map
Fields are mapped to the equivalent on-kare record entries, with a named owner for any field that has no direct equivalent.
- 03
3. Test
The connection runs against a staging instance of the target system before touching production data.
- 04
4. Monitor
Unmatched or failed exchanges raise an alert to a named operations contact, not a silent drop.
Formats not on this list
A system that speaks neither HL7 FHIR nor a documented flat-file export is scoped case by case; this is stated up front rather than found during a pilot.
This page is part of a platform of 2,156 clinical and operational capabilities across 8 business domains.
Explore the catalogueContinue
On-Kare exchanges data with EHRs, labs and payers through standard formats. This page lists what is supported today and how a new connection gets built.