Systems
Custom hospital APIs
Whatever your endpoint offers, through a configured adapter on the one governed path.
What this class of system is
This is anything a hospital exposes over its own API, database, or file drop.
orophin speaks a REST or FHIR API, CSV, and DB polling. In/out: whatever the endpoint offers, through an adapter your team configures in Westron. The single governed outbound path keeps it on the one governed outbound path.
Everything above rides one path. The on-prem orophin agent speaks the protocol on the hospital's own network and opens a single outbound mutually authenticated link to the Pensieve backend. Your network team approves egress.
On the wire
What it emits, and what carries it
The traffic
Whatever the hospital wrote. In practice it is one of three shapes: a REST endpoint returning JSON, a view on a database that can be read but never written, or a folder someone drops a file into on a schedule. orophin has an adapter for each, and the adapter is configuration in Westron rather than a build.
What breaks here
An undocumented endpoint changes without telling anyone. The adapter validates every payload against a schema before it becomes a governed value, so a field that changed shape fails at the bridge with the message attached, and the failure is visible in Westron rather than discovered three weeks later in a report.
Protocols
The standards this class speaks
Each one is described in full on the standards register, at the anchor named here.
- 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.
- 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.
- 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.
- 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.
- 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.
Members
Systems in this class
11 entries on the register, each at its own anchor.
- Generic HIS via APIREST / FHIR R4, OIDC SSO. In/out: whatever the API exposes, through a configured adapter.
- Generic HL7 v2 feedHL7 v2 over MLLP. In/out: any HL7 v2 message the feed emits or accepts.
- Generic FHIR R4 serverFHIR R4, OIDC SSO. In/out: any FHIR R4 resource the server exposes.
- Generic HIS via CSVCSV / flat-file drops. In: scheduled file exports watched from a drop folder.
- Generic TPA via APIREST / FHIR R4, OIDC SSO. Out: pre-auth and claims. In: status.
- e-pharmacy APIREST / FHIR R4, OIDC SSO. Out: e-prescription. In: fulfilment status.
- Payment gateway (UPI)REST API (UPI), OIDC SSO. In: payment confirmation matched to the invoice.
- Bank reconciliation feedCSV / REST API. In: settlements matched to invoices.
- Dispensing-cabinet feedHL7 v2 / device feed. In: dispense events matched against the order.
- Corporate cashless portalREST / FHIR R4, OIDC SSO. Out: pre-auth and claims. In: approval.
- NDHM sandboxABDM sandbox. In/out: a test endpoint for exercising ABDM integration.
What a name in this register means
Compatibility only. Pensieve connects to systems in this class over the protocol they speak. Naming a system describes the connection Pensieve is built to make; it implies no partnership, no certification, and no existing deployment.