Skip to main content

Current product boundary

Clinical Corvus provides reviewable support for clinical workflows. This page defines the beta scope and should be read with Validation and beta status.

Supported in the beta​

The product can support:

  • context and change summaries for rounds;
  • structured I-PASS drafts;
  • organization of problems, goals, and actions;
  • evidence retrieval with citations;
  • structured extraction through Smart Clipboard;
  • educational exercises in Academy;
  • deterministic analysis for supported laboratory panels.

“Supported” means a product workflow exists for the task. It does not mean proven clinical effectiveness, coverage of every case, or authorization for use without review.

Caution required​

The system should declare limits when patient context is incomplete, evidence is weak or indirect, a recommendation depends on an unavailable local protocol, required data is missing, or the execution path has limited traceability.

In those cases, the response may be partial, request more information, or decline to reach a conclusion.

Out of scope​

The beta must not issue an autonomous final diagnosis, approve or execute treatment, replace clinical judgment, conceal insufficient evidence, present educational content as patient-specific guidance, or claim certification or effectiveness that has not been demonstrated.

Clinical review​

The clinician must confirm identity, context, active problems, evidence, contraindications, and next steps before using an output. The interface can support that review, but it does not transfer responsibility to the system.

Beta promotion​

A release decision should consider pipeline-specific evaluations, clinical review of complete responses, replay of the surfaces showing context and uncertainty, state continuity, latency, availability, incidents, and operational support.

Internal benchmarks are engineering signals. They do not replace prospective validation in a clinical environment.