Systems
Medical devices & IoT
Device data on the record, with Sentinel watching the thresholds.
What this class of system is
These are the bedside monitors, pumps, ventilators, and ECG carts at the point of care.
orophin speaks HL7 v2 and device feeds. In: vitals and device data to the record. orophin, Atlas, and Sentinel consume 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
A monitor emits continuously, and a record wants only part of what it emits. The useful payload is a periodic observation set against a bed: heart rate, blood pressure, saturation, respiratory rate, temperature. A ventilator emits its settings and its measured parameters, a pump emits rate and volume, and an ECG cart emits a trace that is a DICOM object rather than a number.
What breaks here
A device knows a bed, and a record knows a patient. The bridge resolves one to the other through the bed and the visit in Nexus before anything reaches Atlas, so a reading is a reading on a person rather than a reading on a socket. Where that resolution fails, the reading is held. Sentinel then watches the thresholds on what did land, and hands delivery to Raven.
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.
- DICOMThe imaging standard. orophin pushes the modality worklist, receives studies (C-STORE), answers Storage Commitment, and queries the archive (C-FIND / C-MOVE).
- 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.
- 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.
Members
Systems in this class
4 entries on the register, each at its own anchor.
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.