Interoperability
Connect, don’t rip out.
Your lab analysers, imaging, pharmacy, and legacy HIS sit on your internal network and can’t be exposed to the internet. Pensieve reaches them through one small on-prem agent and one outbound connection, and speaks the protocols they already speak.
orophin is the bridge: a single agent you install on-premises, on a Windows PC or a Linux server. It speaks MLLP/HL7 v2, ASTM, DICOM, CSV drops, and database polling, and it opens one outbound, mutually authenticated (mTLS) connection to the Pensieve cloud. No inbound firewall holes are opened on your side.
One agent bridges many connections and keeps a durable local outbox, so a network outage does not lose messages. Westron, a tool inside Pensieve, is where your team configures and monitors each connection. The single governed outbound path is the one code path out to any external system. Connections cannot be opened ad hoc by a tool.
The protocol adapters are built and tested against real HL7 messages. HL7 v2, FHIR R4, and DICOM are supported directly, and your data is exportable on those same open standards, so there is no lock-in.
The bridge
One agent, one outbound connection, many machines
Explore
How the bridge works, page by page
- The orophin bridgeExpose no API to us. orophin is a small binary that sits inside your hospital and reaches out.
- No inbound firewall holesThe most common objection to cloud hospital software is that it will want to open ports into your network. Pensieve’s answer is that it never asks you to.
- The durable outboxHospital internet is not always reliable. The bridge is built to absorb the gaps.
- Data normalizationBridging systems is not only moving messages. It is making them agree. Pensieve maps incoming data to one governed reference layer.
- Interoperability governanceInteroperability is a security surface. Pensieve governs it the same way it governs everything else.
- ABDM readinessABDM is how India’s health records connect with consent. Pensieve is built to participate.
- The standards healthcare is built onThe sixteen standards and transports Pensieve speaks, each at its own anchor.
- The systems registerEvery system Pensieve is built to reach, with the protocol it speaks and the direction the data moves.
Message lifecycle
From a machine on the ward to the governed record
A machine emits
An analyser, an HIS, or an imaging modality produces a result, order, or ADT message on the hospital’s internal network.
orophin adapts
The matching protocol adapter (MLLP, ASTM, DICOM, CSV, or DB polling) receives the message and reads it.
Outbox, then out
It lands in the durable local outbox and delivers over one outbound mTLS WebSocket, surviving any network gap.
Into the record
The single governed outbound path applies governance and normalization, and the data becomes a governed value in the patient record.