Reference table
Outside the supported set
Lists the protocols, message types and operations that sit outside current support, so the technology lead can plan around each one.
Pensieve interfaces cover a defined set of protocols, message types and operations, and a handful of neighbouring things sit outside that set because the work they stand for is handled elsewhere in the platform. This page lists each one and names where the equivalent is done, so the technology lead plans a connection around a clear edge.
Imaging on the message channel
Imaging does not travel on the message channel, which keeps the channel clear of large picture data. The hospital's imaging source sends each study over its own authenticated path direct to the Pensieve imaging store, and the message channel carries only the study reference.
| Outside the supported set | Where the work is handled |
|---|---|
| DICOM image bytes over the message channel | The imaging path carries the image bytes direct to the Pensieve imaging store. The message channel carries the study reference, and the image study viewer reads the study tied to its patient and order. |
HL7 v2 message types
The HL7 v2 interface handles results, patient and visit events, and orders with their responses. Scheduling, document and financial message types sit outside that set, because the platform holds each of those areas in a tool of its own.
| Outside the supported set | Where the work is handled |
|---|---|
| Scheduling message types | Appointments run in Gate, and due tasks run in Quest. |
| Document message types | Documents attach to the record in Atlas, and structured documents run through Glyph forms. |
| Financial message types | Charges, tariffs and claims run in Vault, which raises a charge when a chargeable order is placed. |
The full set of supported message types, with the direction each runs, sits in HL7 v2.
FHIR versions and resources
The FHIR interface conforms to R4 at version 4.0.1 and exposes a defined set of resources. A release other than R4, and a resource beyond the exposed set, sit outside the interface, and each maps to a path the platform already runs.
| Outside the supported set | Where the work is handled |
|---|---|
| A FHIR release other than R4 | The interface conforms to FHIR R4, version 4.0.1, and states that version on every exchange. |
| Imaging and medication resources | Imaging is read through the imaging path, and medication runs through Forge orders. |
| A search Pensieve starts on a timer | Inbound runs push-driven. A partner pushes a message, or an operator triggers a one-off search from the console. |
The exposed resources and the operations on each sit in FHIR.
Connection shapes
A connection reaches the platform in one shape: outward from the hospital, through the bridge's single path. A person's browser session and a direct inbound link sit outside that shape, and each resolves through the supported path instead.
| Outside the supported set | Where the work is handled |
|---|---|
| A person's FHIR app session | A FHIR connection authenticates as a system, so a machine-to-machine connection carries the exchange on its own identity. |
| A direct inbound link to the platform | Every connection reaches Pensieve outward through the bridge's single path, which the platform authenticates at the boundary. |
An edge is a redirection
Each row above names a supported path that does the same work. Planning a connection means choosing the supported path for the exchange, so an interface lands on the route the platform already runs.
Common confusions
How does imaging reach a clinician if it stays off the message channel?
Imaging travels its own route to the Pensieve imaging store, and the message channel carries the study reference. The image study viewer reads the study, tied to its patient and order, from any tool.
Where do charges go if financial messages sit outside HL7 v2?
Charges, tariffs and claims run in Vault. Vault raises a charge when a chargeable order is placed, so the financial work happens inside the platform rather than over an inbound message.
How does inbound FHIR arrive without a timed pull?
Inbound runs push-driven. A partner pushes a message across the boundary, or an operator triggers a one-off search from the console, so an exchange starts from the sender or the operator.
See which system holds the authoritative copy of each data type in system of record, and how Pensieve runs alongside an existing system in coexisting with an existing system.