Skip to content

Systems

Lab analysers & instruments

Every result matched to the order that asked for it.

What this class of system is

These are the analysers and instruments on the laboratory bench, connected directly.

orophin’s ASTM and HL7 v2 adapters post each result against the order that asked for it. In: analyser results mapped to the ordering entry. Forge, orophin, Atlas, and Sentinel 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

A bench analyser speaks ASTM over a serial line or a socket: E1381 frames the transfer, E1394 carries the content, and the pair is what the instrument manual calls LIS02. The message is the instrument’s own vocabulary, with the instrument’s own test codes, its own units and its own reference ranges, which is why two analysers reporting the same analyte disagree about what to call it.

What breaks here

A local test code is a local test code. orophin’s adapter resolves each result to LOINC as it arrives, with the specimen type and the reference range attached, so a potassium from an ASTM bench and a potassium from a legacy LIS over HL7 land as the same governed value and can be trended against each other. Nothing is stored in the shape the instrument happened to send.

Members

Systems in this class

22 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.

Powerful. Responsible. Pensieve.

Get started