Skip to content

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.

DIAGRAMOne orophin agent inside the hospital opening a single outbound mTLS connection to the Pensieve cloud, no inbound arrowsDIAGRAM, 4/3

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

DIAGRAMArchitecture: hospital network (HIS/LIS/PACS/PIS/analysers/devices) into one orophin agent (durable outbox) into a single outbound mTLS WebSocket into the Pensieve backend on the single governed outbound path; Westron console overlayDIAGRAM, 16/9
Hospital network (HIS, LIS, PACS, PIS, analysers, devices) reaches one orophin agent with a durable outbox, which opens a single outbound mTLS WebSocket to the Pensieve backend on the single governed outbound path, with the Westron console over the top.

Message lifecycle

From a machine on the ward to the governed record

  1. A machine emits

    An analyser, an HIS, or an imaging modality produces a result, order, or ADT message on the hospital’s internal network.

  2. orophin adapts

    The matching protocol adapter (MLLP, ASTM, DICOM, CSV, or DB polling) receives the message and reads it.

  3. Outbox, then out

    It lands in the durable local outbox and delivers over one outbound mTLS WebSocket, surviving any network gap.

  4. Into the record

    The single governed outbound path applies governance and normalization, and the data becomes a governed value in the patient record.

Powerful. Responsible. Pensieve.

Get started