Systems
HIS / HMIS
The system your front office already runs on. Bridged, and left running.
What this class of system is
A HIS / HMIS is the system your front office already runs registration, admission, and billing on.
orophin speaks HL7 v2 (ADT / DFT), and CSV or a REST API where that is what exists. In: demographics, admissions, and charges; out: orders where the system supports them. Gate, Atlas, Vault, and Forge consume and produce the data.
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
The traffic is admission, discharge and transfer. A registration produces an ADT^A04, an admission an A01, a transfer an A02, a discharge an A03, and a correction an A08 that has to be applied to a patient who already exists rather than creating a second one. Charges arrive as DFT^P03. Where the system has no interface engine at all, the same facts arrive as a nightly export in a drop folder, which orophin reads once and does not re-read.
What breaks here
The identifier. A legacy registration desk issues its own patient number, a scheme desk issues another, and the laboratory issues a third, so the same person is three people by the afternoon. Pensieve matches an inbound ADT to the entity it belongs to before the message lands, and an unmatched message stops at the bridge with the reason attached instead of quietly opening a duplicate record.
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.
Members
Systems in this class
8 entries on the register, each at its own anchor.
- Generic HIS via HL7HL7 v2 (ADT / DFT) over MLLP. In: demographics, admissions, and charges.
- Generic HIS via APIREST / FHIR R4, OIDC SSO. In/out: whatever the API exposes, through a configured adapter.
- Generic HIS via CSVCSV / flat-file drops. In: scheduled file exports watched from a drop folder.
- Insta HMSHL7 v2, CSV. In: demographics, admissions, and charges.
- BirlamedisoftHL7 v2, CSV, DB polling. In: demographics, admissions, and charges.
- MocDocREST / FHIR R4, HL7 v2. In: appointments and admissions.
- Napier HISHL7 v2, REST / FHIR R4, DB polling. In: demographics, admissions, and charges.
- KareXpertREST / FHIR R4, HL7 v2. In: demographics and admissions.
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.