Interoperability

One agent. One outbound connection. Every machine you own.

Expose no API to us. orophin is a small binary that sits inside your hospital and reaches out.

Speaks: MLLP/HL7 v2, ASTM, DICOM, CSV, DB polling
Connection: One outbound mTLS WebSocket
Runs: On-prem (Windows PC or Linux server)

What orophin is

orophin is a single TypeScript Node binary installed on a Windows PC or a Linux server inside the hospital. One agent per hospital bridges many connections at once.

No port is opened and no API is published. It sits on your internal network, next to the machines it talks to, and reaches out to Pensieve, never the other way around.

Inside the agent

Adapters, a durable outbox, one link out

DIAGRAMorophin agent internals: protocol adapters (MLLP/ASTM/DICOM/CSV/DB) into a local durable outbox into a single outbound mTLS WebSocket to the Pensieve backendDIAGRAM, 16/9

orophin internals: protocol adapters (MLLP, ASTM, DICOM, CSV, DB polling) feed a local durable outbox, which delivers over a single mutually authenticated WebSocket to the Pensieve backend.

How the bridge works

How it connectsOne outbound, mutually authenticated (mTLS) WebSocket to the Pensieve backend. Both ends verify each other’s certificate. Nothing on the hospital side is exposed to the internet.
What it speaksMLLP/HL7 v2, ASTM (lab analysers), DICOM (imaging), CSV drops, and database polling, the protocols the machines already use.
What it connectsHIS, EMR, EHR, LIS (lab), PIS (pharmacy), RIS-PACS (imaging), billing systems, and custom hospital APIs.
The durable outboxA persistent on-disk queue holds messages from your machines through a network outage, so nothing is lost when the line drops.
One governed path outEvery outbound connection routes through the single governed outbound path. No tool opens a connection on its own.
Configured in WestronWestron, a tool inside Pensieve, is where your team defines and monitors each connection the agent carries.

Built, tested, demoable

The adapters (MLLP, ASTM, CSV), the durable outbox, and the backend link are built and tested against real HL7 messages. Our hospital partners run under NDA, so we do not publish their names. Get started and see orophin move live data on workflows like yours.