You were admitted because of fever.
The hospital record says this happened while your immune system is weakened.
Source: Admission note · synthetic
Not another pile of documents. One calm view of what happened, what changed, what is still pending, what happens next — with the original source always available.
Synthetic only. This demonstrates product and safety concepts, not clinical advice or a live patient portal.
The hospital record says this happened while your immune system is weakened.
The final identification is not ready yet. This is preliminary information, not a final result.
CareOS keeps pending, preliminary, corrected, unavailable and final information visibly different. An AI explanation may change the wording — never the underlying source state.
The patient helper may explain jargon, translate presentation, find a source or help prepare questions for the care team. It does not create a new clinical truth.
The laboratory is still testing which medicines the organism is sensitive to.
Microbiology laboratory releases the final result. The treating team reviews it after release.
If the source is down or a result is not finished, CareOS must never turn that into “nothing found.” Uncertainty remains visible until the source resolves it.
Not documented in this synthetic episode.
Documented as active therapy.
This reports what the hospital record currently documents. It is not an AI treatment recommendation.
The documented plan is to review the final result after the laboratory releases it.
Ask the treating team how you will receive the final result and who is responsible for follow-up.
Every important explanation should lead back to the original source, state and timestamp where the connected system exposes them.
A future family/proxy view should use explicit, revocable scopes. Who may see or share what remains governed by the connected health infrastructure and applicable policy.
Flagging does not silently overwrite the clinical record. It creates a visible review request with ownership and resolution state.
Our usability proof should test understanding, not page views.