Reference table
Integration boundaries
Lists the kinds of integration that sit outside the catalogue, such as device streams and database polling, and the supported path that does the same work.
Pensieve does the work of several integrations familiar from other estates, such as a warehouse connector or a webhook, on the catalogue's routes or inside its tools. This page groups those integrations by area and names the route or tool that does each one's work.
Data platforms
A warehouse receives Pensieve's records through export, current figures are drawn in Falcon, and data from a hospital system arrives through orophin, the bridge.
| Outside the catalogue | Where the work is handled |
|---|---|
| A live connector for a data warehouse or BI tool | The hospital's users run the self-service export and load their warehouse from it, and analysis on current data runs in Falcon. |
| SQL, ODBC or JDBC access to Pensieve's data | Falcon reads through the governed read path under each reader's grants and each patient's consent, and its exports are de-identified by default. |
| A replication feed or change stream out of Pensieve | Records leave through the self-service export for the hospital to load, and outbound exchanges such as orders reach hospital systems, as programmatic access below sets out. |
| Polling a hospital system's database, or capturing its changes | The system sends HL7 v2 messages, FHIR resources or delimited files to the bridge, which carries each one to the integration engine. |
A system whose data sits only in its database reaches Pensieve once its rows are written as delimited files to a folder the bridge watches. The warehouse route is traced in analytics and data out, and every way a hospital system sends data in connection methods.
Devices and the bedside
Laboratory analysers connect to the bridge over ASTM, as laboratories and analysers describes. The rest of a ward's equipment is held as assets in Nexus Manager, and staff record what they observe through Glyph forms on the patient's record.
| Outside the catalogue | Where the work is handled |
|---|---|
| Data streams from bedside monitors, infusion pumps or wearables | Staff enter observations through Glyph forms, such as an observation set or a triage, and each device is held as a physical asset in Nexus Manager with its location and status. |
| Wristband printers, or barcode and wristband scanning | A dose is marked given only after the nurse at the bedside confirms the patient, drug, dose, route and time, and each record opens against one patient and their current visit. |
| Label printers | Documents such as forms, bills, receipts and discharge summaries print from the browser on the hospital's letterhead, and labels stay with the hospital's own printing. |
| Biometric or attendance devices | The duty roster in Nexus Manager records who is on shift, and staff sign in at a shared workstation with a PIN bound to that machine. |
An observation entered this way carries the name of the person who recorded it. The checks at a dose are set out in medication orders, and sign-in on a ward machine in shared workstations.
Programmatic access
A hospital or partner system exchanges data with Pensieve on a connection defined in Westron, which carries the system's identity and purpose of use and records each crossing. People work through Pensieve's own interfaces, under sessions issued to them alone.
| Outside the catalogue | Where the work is handled |
|---|---|
| General-purpose API keys, service accounts or OAuth client applications | A system joins as a registered connection in Westron and exchanges data on the routes its connection defines. |
| A person's session used by a script or another system | A system exchanges data on its own connection under its own identity, and each session belongs to the person who signed in. |
| Outbound webhooks, or subscriptions to Pensieve's events | Each hospital system receives the outbound exchanges its connection is mapped for through the governed outbound path: an order in HL7 v2 or FHIR, or a patient and encounter update as a FHIR transaction to the system of record. |
| An outside application built on Pensieve's interfaces | An app a hospital composes inside Pensieve works under the access of the person using it, through the same decision as every tool. |
Apps composed inside Pensieve are described in apps inherit access, and the route a change takes to a hospital system in outbound exchanges.
Message types and files
The bridge carries the HL7 v2 message types, FHIR resources and delimited files each connection names, and studies travel on an imaging path of their own. Scheduling and documents are work that Gate and Atlas already do inside Pensieve, and charges follow the site's billing mode in Vault.
| Outside the catalogue | Where the work is handled |
|---|---|
| HL7 v2 scheduling, document and financial message types | Gate books the appointment, Atlas attaches the document to the record, and at a site where Pensieve bills, Vault charges for each chargeable order as it is placed. |
| DICOM services such as C-STORE, C-FIND, C-MOVE and storage commitment | Studies move over DICOMweb: STOW-RS stores each one in the Pensieve imaging store, and QIDO-RS and WADO-RS find and fetch it for the viewer. |
| A spreadsheet workbook read as rows | A watched folder reads delimited text, so the sheet is saved in that form and each row passes through the connection's field mapping. |
The imaging path is followed in imaging, and the remaining edges of the interfaces, from HL7 v2 areas to FHIR releases and connection shapes, in outside the supported set.
Finance
Vault runs billing, payments and tax, and reaches outside finance services through a billing connector to the hospital's finance system, the Invoice Registration Portal and the payment gateway. Each of those routes runs on the hospital's own account, held by reference in the platform's secret store.
| Outside the catalogue | Where the work is handled |
|---|---|
| A general-ledger or voucher export to an accounting package | Where Vault bills and the hospital's finance system keeps the books, that system receives invoices and charges as FHIR R4 resources through a billing connector in Westron. |
| Payment links or UPI collect requests | Vault opens the gateway's hosted checkout against the invoice or deposit, and the patient completes the payment on that page. |
| A card machine connected to Pensieve | The cashier records each card-machine payment in Vault with the machine's approval reference. |
| Failover to a second payment gateway | Online collection runs through the one integrated gateway, and Vault keeps recording every counter method while that gateway is out of reach. |
The billing modes and the feed to a finance system are set out in tax and finance systems, and online collection in payments.
Every row names a route
Each entry above points to a route or a tool Pensieve already runs. An interface built on that route keeps its crossings under the same access decision and record as the rest of the integration.
Common confusions
What does a sender read when it sends an HL7 v2 type outside the supported set?
A rejection that names the reason, while the message itself is kept for review, as HL7 v2 sets out.
Which routes carry data out of Pensieve besides export?
Outbound exchanges carry orders, patient updates, claims, and invoices and charges to hospital systems and partners, and ABDM carries the records a patient consents to share. E-invoices go to the Invoice Registration Portal, online collections go to the payment gateway, and Raven carries messages to patients and staff. Each route keeps its own record of what it sent.
How is a new hospital system or partner added?
As a connection in Westron over one of the methods in connection methods. It is defined, mapped to the record and proven on a sandbox site before it carries live data, as proving an integration describes.
Read how the catalogue's routes fit together in the integration architecture.