Health Information Exchange
Health Information Exchange Platform
The right record, for the right patient, with their permission. BharathiExchange resolves identity across facilities, enforces consent on every request and serves a single longitudinal record — without forcing hospitals to hand over their databases.
Platform architecture
Five layers, one exchange
Data enters through standards-based gateways, is matched to the right person, checked against consent, enriched by AI and delivered to whoever is authorised to act on it.
Sources
Care & payer systems
- Hospital HIS / EMR
- LIS & RIS / PACS
- Pharmacies
- Insurers & TPAs
- Wearables & PHR apps
Integration gateway
Connect & translate
- HL7 v2 / MLLP engine
- FHIR REST & Subscriptions
- X12 EDI translator
- DICOMweb proxy
- SFTP / AS2 / API gateway
HIE core
Identity, consent & record
- Master Patient Index (EMPI)
- Provider & facility registry
- Consent manager
- Record locator & document registry
- FHIR clinical data repository
- Terminology server
Intelligence
AI services
- ML patient matching
- Clinical NLP
- Auto-coding
- Claim & denial analytics
- Data-quality scoring
Consumers
People who act
- Clinician longitudinal view
- Patient app & consent inbox
- Payer claim workflows
- Public-health dashboards
- Government Connect APIs
Core capabilities
What the HIE core does
Eight services that make interoperability trustworthy at national scale.
Master Patient Index
Links records across facilities using ABHA where present, and probabilistic plus ML matching where it is not. Duplicates go to a stewardship queue.
Consent manager
Purpose-bound, time-bound consent artefacts. Patients approve, revoke and audit access from their phone; every data pull checks consent first.
Record locator
Knows which facility holds which encounter, lab or discharge summary, so records can stay federated and still be found in seconds.
Clinical data repository
Normalised FHIR resources — Patient, Encounter, Observation, Condition, MedicationRequest, DiagnosticReport — for the longitudinal view.
Provider & facility directory
Verified clinicians and facilities, so every document carries a trusted author and origin, and routing finds the right endpoint.
Terminology services
SNOMED CT, LOINC, ICD-10 / ICD-11 and drug vocabularies, with local-to-standard code maps curated by AI and approved by coders.
Encounter notifications
Care teams subscribe to admissions, discharges and transfers, so follow-up happens within a day rather than at the next visit.
Surveillance feeds
De-identified, aggregated feeds for notifiable disease reporting, immunisation coverage and outbreak signals.
Patient matching
Two registrations, one person?
The EMPI weighs each field, then decides: link automatically, send to a human steward, or create a new identity. Move the threshold to see the decision change.
| Field | City Hospital | District Lab | Weight |
|---|---|---|---|
| Name | Lakshmi Narayanan | Laxmi Narayan | +4.1 |
| Date of birth | 14-03-1981 | 14-03-1981 | +6.8 |
| Sex | F | F | +0.9 |
| Mobile | 98xxxxx412 | 98xxxxx412 | +7.2 |
| PIN code | 560041 | 560076 | +0.6 |
| ABHA number | present | — | 0.0 |
Phonetic and nickname models treat "Lakshmi / Laxmi" as a strong partial agreement. Illustrative example data.
Match decision
Scores between the review floor (0.75) and the threshold go to data stewards.
Public health & Government Connect
Built to plug into India's digital health stack
Government Connect APIs link BharathiExchange to national identity, registry, insurance and programme systems — so eligibility, identity and reporting happen automatically, not by spreadsheet.
ABDM building blocks
ABHA linking, HIP/HIU flows, consent management and HPR/HFR registries, designed to align with ABDM specifications.
Insurance schemes
Beneficiary eligibility checks and FHIR claim exchange for government-funded and private insurance, including NHCX-style claim flows.
Programme reporting
Automated, de-identified indicators for immunisation, maternal and child health, NCD screening and disease surveillance programmes.
Policy dashboards
District-to-national views of utilisation, cost and outcomes for programme managers, built on the actuarial and AI layers.
Security & deployment
Sovereign by design
Health data stays in-country, encrypted everywhere and accessible only through audited, consented channels. Read more about security.
- Identity
- OAuth 2.0 / OpenID Connect, SMART on FHIR, mutual TLS between nodes
- Encryption
- TLS 1.3 in transit; AES-256 at rest with HSM-backed keys
- Audit
- Immutable audit trail for every read and write
- Hosting
- Government sovereign cloud, empanelled public cloud region, or on-premise
- Runtime
- Containerised microservices on Kubernetes, horizontally scalable
- Resilience
- Multi-zone active-active core with disaster-recovery site
FAQ · Health Information Exchange
Identity, consent and records.
5 common questions.
How do you match patients without a universal health ID?
The EMPI combines deterministic rules on strong identifiers with probabilistic and machine-learning scoring on names, date of birth, sex, phone and address. High scores link automatically; borderline scores go to a human data steward.
Who decides who can see a patient's record?
The patient. Every request for data is checked against a consent artefact that specifies purpose, requester, data types and time window. Patients can review and revoke consent from the app.
Which clinical data types are exchanged?
Encounters, diagnoses, lab results, imaging reports, prescriptions, immunisations, allergies, discharge summaries and other clinical documents, represented as FHIR R4 resources.
How are local hospital codes standardised?
The terminology server maps local codes to SNOMED CT, LOINC and ICD. AI proposes mappings; trained coders approve them before they go live.
Is every access logged?
Yes. Every read and write produces an immutable audit event recording who accessed what, when, and under which consent.
FAQ · Platform
How the pieces fit together.
4 common questions.
Is BharathiExchange a centralised or federated HIE?
Hybrid. A central index holds identities, consent and a record locator, while detailed records can stay at the source facility and be fetched on demand. Selected data can also be stored centrally in the FHIR repository where policy allows.
Do hospitals need to replace their existing HIS or EMR?
No. The integration gateway connects to what is already running — HL7 v2 feeds, FHIR APIs, database extracts, CSV or SFTP drops — and translates them into the platform's standard model.
Can it run in our own data centre?
Yes. The platform deploys on a government sovereign cloud, an empanelled public cloud region, or on-premise infrastructure, using the same containerised build.
What are Government Connect APIs?
Secure, documented APIs that link the exchange to national systems such as health ID, insurance scheme, provider and facility registries, so eligibility and identity checks happen automatically.
Ready to connect your organisation?
Request a demo and we’ll walk through BharathiExchange against your programme and real message flows.