Wiring every system to every other system stops working around connection ten.
Each new link is quick on its own. Together they become something nobody fully understands, and nobody wants to touch.
What happens to a message, start to finish.
A request, an event, a file or a reading from a machine — from a source that is allowed to send it.
Who sent it, is it the right shape, are the required fields there, and have we seen it already.
The receiving system wants the data its own way, so we reshape it and add what it needs.
It goes to whichever systems should get it, and we wait for each one to confirm it arrived.
Everything is logged. If a delivery fails it retries, and you can re-send it once the far end is back.
Three ways to connect. Each suits a different job.
APIs
One system asks, another answers, right now. Best when someone is waiting for the reply.
Events
One system announces that something happened. Anything that cares picks it up in its own time.
Adapters
For older systems that will never speak a modern format. We translate on their behalf.
Readings from the bedside, in the notes automatically.
A reading arrives knowing which patient, which bed, which machine and exactly when — so nobody has to copy it across by hand.
It speaks the formats your clinical systems already use.
HL7, FHIR and DICOM are supported directly, so a result means the same thing on both sides of a connection.
The messaging format most hospital systems already speak.
The newer standard, for systems built to share data over the web.
Imaging — scans, studies and the workflow radiology runs on.
Orders out, results back, and an alert when a result cannot wait.
Keeping one patient as one patient, even when records get merged.
What happened clinically reaching the teams who bill and plan for it.