Clinical context layer vs data warehouse
A data warehouse or data lake stores large volumes of data so it can be queried and analysed. A clinical context layer maintains what the facts mean in relation to one another for a patient, right now. A warehouse can be one of the sources a context layer draws on.
At a glance
| Aspect | Clinical context layer | Data warehouse or data lake |
|---|---|---|
| What it holds | Entities, relationships, interpretations and uncertainty, kept current for each patient. | Stored data, organised for querying and analysis. |
| How it changes | Updated event by event as new signals arrive. | Loaded and transformed on a schedule or by pipeline. |
| Main question answered | What does everything currently known mean for this patient now? | What does the data say when it is queried or analysed? |
| Role of uncertainty | Tentative and uncertain findings are kept as such. | Typically resolved during modelling and cleaning. |
When to use which
A clinical context layer fits when
- The goal is to see how a patient's facts relate, including tentative signals.
- Applications need scoped, up-to-date context rather than raw tables.
- Human concerns and constraints should shape what counts as significant.
Data warehouse or data lake fits when
- The goal is population-level reporting, analytics or model training.
- You need to store and query large volumes of structured data cheaply.
- The question is already well defined and answerable by a query.
What each does not do
A clinical context layer
- It is not a place to store everything for later analysis.
- It is not a system of record and does not replace one.
Data warehouse or data lake
- It does not maintain relationships and their changing significance by itself.
- It does not decide what is significant for an individual patient.
Status
Specified · Prototype next · Not in clinical use
Clinical Context AI (IMI) proposes; a clinician decides.
Last reviewed
Related reading
Clinical context layer vs retrieval-augmented generation
A clinical context layer maintains how facts relate to one another over time. Retrieval-augmented generation (RAG) finds fragments similar to a query and hands them to a model, which then has to work out the relationships on every call. The two are complementary, not interchangeable.
ComparisonClinical context layer vs EHR-embedded decision support
Decision support built into the electronic health record typically applies defined rules to recorded data at set points in a workflow. A clinical context layer maintains how facts, including signals outside the record, relate over time. It draws on the record and can feed insight back; it does not replace it.
DefinitionWhat is a clinical context layer?
The definition, what it is not, and how it works.
Want to go deeper?
Talk to the founders about where the context layer fits in your program.
Talk to the founders