Clinical context layer vs general-purpose AI assistant
A general-purpose AI assistant reasons over whatever is placed in its context window for the current conversation. A clinical context layer is the persistent model from which such a window could be drawn. It supplies maintained, scoped context; the assistant, or a clinician, still does the interpreting.
At a glance
| Aspect | Clinical context layer | General-purpose large language model assistant |
|---|---|---|
| What it is | Infrastructure that maintains contextual understanding for applications. | An application that reasons over the information it is given. |
| Memory of the patient | Persistent and cumulative, updated as events arrive. | Limited to the current window unless something else supplies more. |
| Source of context | A shared, continuously maintained model. | Whatever the user or application places in the window. |
| Safety framing | Proposes; a clinician decides, within human-authored boundaries. | Depends on how the application around it is designed. |
When to use which
A clinical context layer fits when
- Many applications and agents should share one understanding of a patient.
- Understanding must accumulate across encounters and signals.
- Human-authored concerns should govern what the system raises.
General-purpose large language model assistant fits when
- A one-off question needs a quick, general answer.
- The needed information can be placed in a single window.
- No persistence between conversations is required.
What each does not do
A clinical context layer
- It is not a chatbot and not a replacement for a model or for clinical judgment.
- It does not make a model's answers correct by itself.
General-purpose large language model assistant
- It does not maintain relationships between facts between conversations on its own.
- It does not know the clinical concerns that matter for a particular patient unless told.
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 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.
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