Patient timeline
Encounters, observations, results and documents resolve from one request instead of a record-summary service.
- SQL
A clinical question answered from the record, not from a summary of it.
Where it starts
Encounters and observations
Visits, measurements, vitals and administered care. It is the first of 4 workloads running in Healthcare.
The question it raises
Patient timeline
Encounters, observations, results and documents resolve from one request instead of a record-summary service.
Why one question is hard
From Register to Review
Healthcare data moves through 5 stages — Register → Encounter → Order → Document → Review. The shapes in play are SQL, JSON / documents, Time series, Objects, Events, and answering one question means reading across all of them.
What PLOMID contributes
Clinical systems are judged on traceability. These are the parts of the layer that carry it.
- Documents beside rows Fields that keep changing shape stay queryable instead of being exported into a separate document store.
- One data layer Rows, documents and time-ordered events live in one system, so a question is asked once instead of once per store.
- Snapshot reads under continuous writes Readers and writers do not block each other, which is what makes a telemetry feed and an application share one system.