Skip to main content

Clinical State (CaseState): Core Concepts

Clinical Corvus maintains an explicit episode-level clinical state so the system can stay stable across interactions and remain audit-friendly.

Why This Matters​

Pure “chat history” approaches are fragile in clinical work:

  • Drift: important constraints are lost over multiple turns.
  • Ambiguity: unclear context leads to inconsistent summaries and plans.
  • Low auditability: it becomes hard to explain what changed and why.

An explicit clinical state helps make outputs consistent, reviewable, and traceable.

What The State Represents (Conceptually)​

  • Problem representation: a compact “one-liner” that anchors the case.
  • Differential: candidate diagnoses with supporting/contradicting evidence.
  • Plan: actions and monitoring items, written to be checkable.
  • Evidence ledger: references used to support key claims when evidence is requested.
  • Safety flags: gaps, contradictions, or areas of uncertainty that require clinician attention.

How It Evolves​

Instead of “rewriting the whole story” every time, the system records typed, incremental updates. This creates an audit trail that can be reviewed over time: what changed, who changed it (role-wise), and what prompted the change.