Skip to main content

Dual-Stream Architecture

To handle messy input (text, tables, PDFs) without giving up structure, Clinical Corvus separates two streams at ingestion:

  • Narrative stream: synthesis and clinical drafts
  • Signal stream: quantitative values requiring consistency and validation

Why separate​

Clinical text requires interpretation and review. Critical numbers (labs, vitals) require consistency. Mixing both in one process creates the risk that narrative replacements overwrite structured values without the clinician noticing.

How it works​

At ingestion:

  1. The system prioritizes structure preservation (tables, headers, sections)
  2. OCR is used as fallback when direct structuring isn't possible
  3. Narrative stream goes to synthesis and drafting
  4. Signal stream goes to validation and extraction

The workspace output integrates both streams, but they are processed separately to prevent one from polluting the other.

Visualization​

Implication for bounded support​

Stream separation reduces the risk that narrative synthesis silently replaces a structured value. Paths that implement signal validation must preserve that result through the interface. Coverage is not uniform across every surface, so critical values still require clinical verification.