Interoperability
The standards healthcare is built on
Interoperability is a small set of protocols, each doing a specific job. Pensieve speaks the ones hospitals already run on, and India’s EHR Standards name the same set.
One set, four jobs
Messaging, resources, imaging and instruments. Everything else on this page is a transport or a vocabulary.
HL7 v2 carries the events a hospital generates: an admission, an order, a result, a charge. FHIR R4 carries the same facts as addressable resources, which is what an exchange across an organisational boundary needs. DICOM carries the image and the worklist that produced it. ASTM carries what the bench instrument says.
Under all four sits a transport, and the transport is the same one every time: the on-prem orophin agent, one outbound mutually authenticated link, no inbound rule. A protocol is what Pensieve says; the bridge is where it is said from.
India’s EHR Standards (notified 2016, MoHFW) reference HL7 v2.8.2, FHIR, DICOM, and the SNOMED CT / LOINC / ICD terminology set. Attributed as the standard. Pensieve holds no certification against it.
The four protocol families, and how Pensieve uses each
| Family | What it is | How Pensieve uses it |
|---|---|---|
| HL7 v2 over MLLP | Pipe-delimited hospital messages (ADT, ORM / OMG, ORU, DFT, MDM, SIU) framed by MLLP over TCP/IP. The dominant hospital messaging standard. | orophin sends and receives HL7 v2 over MLLP, bidirectionally, through the bridge. |
| FHIR R4 | The REST / JSON, resource-based standard: Patient, Encounter, Observation, ServiceRequest, DiagnosticReport, Claim, Coverage. | Used for ABDM linkage and NHCX claim packaging; resources map to the governed record. Your data is exportable on FHIR R4. |
| DICOM | The imaging standard: C-STORE, C-FIND, C-MOVE, Modality Worklist, Storage Commitment. | orophin acts as a DICOM node; studies open in-app, inside the patient’s record. |
| ASTM E1381 / E1394 | The serial protocol most lab analysers speak, which an instrument manual calls LIS02. E1381 is the transport, E1394 the message content. | orophin’s ASTM adapter connects to analysers directly and posts each result against the order. |
India’s EHR Standards (notified 2016, MoHFW) reference HL7 v2.8.2, FHIR, DICOM, and the SNOMED CT / LOINC / ICD terminology set. Attributed as the standard. Pensieve holds no certification against it.
The register
Every standard and transport, at its own anchor
Sixteen entries. Each one names what it is and what Pensieve does with it, and each is linkable on its own.
- HL7 v2The dominant hospital messaging standard. orophin sends and receives ADT, ORM / OMG, ORU, DFT, MDM, and SIU. India’s EHR Standards name v2.8.2.
- FHIR R4Modern REST / JSON resources: Patient, Encounter, Observation, ServiceRequest, DiagnosticReport, Claim, Coverage. Pensieve speaks FHIR R4 for record exchange, ABDM linkage, and NHCX claims.
- DICOMThe imaging standard. orophin pushes the modality worklist, receives studies (C-STORE), answers Storage Commitment, and queries the archive (C-FIND / C-MOVE).
- ASTMThe serial protocol most analysers speak: E1381 transport, E1394 message content, the pair a bench calls LIS02. orophin’s ASTM adapter posts each result against the Forge order.
- MLLP transportThe TCP framing HL7 v2 rides on. A start block, the message, an end block and a carriage return, over a socket. orophin’s MLLP adapter is the transport under every HL7 v2 connection.
- CSV / flat fileThe fallback for a system with no live interface. orophin watches a drop folder for scheduled exports and reads each file once.
- DB polling / CDCRead-only polling of a legacy database or a view, where no messaging exists at all. orophin reads; it never writes back into someone else’s schema.
- mTLS WebSocket bridgeThe single outbound, mutually authenticated link orophin opens to the Pensieve backend. Both ends verify a certificate, nothing listens on the hospital side, and every row in this register rides it.
- SAML SSOEnterprise sign-in for a hospital with an existing SAML identity provider.
- OIDC SSOOpenID Connect sign-in for a hospital identity provider.
- ABDM (ABHA / HIE-CM)India’s national health-data rails: FHIR-R4 ABHA linkage and consent-driven sharing through the Health Information Exchange and Consent Manager.
- HFR / HPR registriesThe ABDM Health Facility Registry and Healthcare Professionals Registry. Facility and professional context is held in Nexus, beside orgs, sites, users and roles.
- NHCX claimsThe FHIR-based National Health Claims Exchange, built jointly by the National Health Authority and IRDAI. Vault packages pre-auth and claims to it.
- GST e-invoicing APIIndia’s e-invoicing rails. Vault produces GST-correct invoices for the Invoice Registration Portal, and each line carries its tax treatment from the moment the charge is captured.
- ICD-11 terminologyWHO diagnosis coding: the primary diagnosis coding surface in Atlas and at the medical-records desk.
- SNOMED / LOINC feedsClinical-term and laboratory / observation coding. An investigation resolves to LOINC and a clinical term to SNOMED CT, which is what makes two analysers comparable.
Exportable on the same standards
Because Pensieve reads these standards, it writes them too. Your data is exportable on HL7 v2, FHIR R4, and DICOM, the open standards the rest of healthcare already uses, and the export runs on the same governed outbound path as every other exchange. The exit is part of the design, documented here in the standards it uses.
Where a standard leaves a choice open, the choice is stated in data normalization: an investigation resolves to LOINC, a clinical term to SNOMED CT, and a diagnosis to ICD-11, so a value from an analyser and a value from a legacy laboratory system can be compared and trended against each other.