Product overview
Clinical Corvus organizes clinical work into a simple cycle: context, deltas, plan, and review.
The product brings together information captured by the team, highlights relevant changes, prepares drafts, and supports evidence retrieval. None of these steps transfers the clinical decision to the system.
The core workflow
1. Context
The workspace brings together data associated with the patient and episode. The team can add text, PDFs, and documents already used in care.
2. Deltas
Monitor mode helps identify what changed since the last review, including new results, alerts, pending tasks, and changes in clinical state.
3. Plan
Plan mode organizes problems, goals, actions, and drafts. AI-generated items remain editable and require review before acceptance.
4. Evidence
When a decision needs support, Corvus can search sources, record which evidence was admitted or rejected, and declare when support is insufficient.
Main capabilities
| Capability | Output | Status |
|---|---|---|
| Rounds | Context, deltas, and a plan draft for review. | Limited beta |
| Handoff | Structured I-PASS draft. | Limited beta |
| Smart Clipboard | Structured extraction and conflict detection. | Limited beta |
| Evidence | Cited briefs and support states. | Limited beta |
| Workspace | Monitor, Plan, and contextual Corvus actions. | Limited beta |
| Academy | Educational exercises not intended for patient care. | Educational environment |
| Documents | Upload, indexing, and search when configured. | Configurable |
| Lab analysis | Deterministic analyzers for supported panels. | Supporting capability |
Current boundary
The beta distinguishes supported responses, responses requiring caution, and blocked requests. Missing context, weak evidence, and requests outside the support role should be visible to the user.
Read the Current product boundary and Validation and beta status for current limitations.