Skip to content

Systems

RIS / PACS (imaging)

One order drives the worklist; the study lands in the record.

What this class of system is

A RIS / PACS runs radiology scheduling and stores images and reports.

orophin speaks DICOM (MWL, C-STORE, C-FIND / C-MOVE) and receives HL7 ORU reports. Out: modality worklist; in: studies and reports, viewed inside the record. Forge, orophin, and Atlas 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

The worklist is the whole argument. orophin answers Modality Worklist so the technologist selects the patient rather than typing the name, which is where the mismatched study comes from. Studies arrive by C-STORE and are acknowledged with Storage Commitment, so the archive knows the transfer completed. Priors are pulled with C-FIND and C-MOVE. The radiologist’s report returns separately as an HL7 ORU.

What breaks here

An archive that answers a query and refuses a retrieve, and a modality that will not take a worklist at all. Both are ordinary. Where a worklist is available, one order drives the modality and the study lands against it; where it is not, the study is matched on the accession and the demographics, and a study that matches neither is held rather than filed under a guess.

Members

Systems in this class

18 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