Cortex Engine

Two-layer AI analysis for chart QA that has to be reliable.

Cortex Engine does not ask a model to do everything. It combines deterministic clinical checks for facts we can prove with LLM analysis for the parts that require note-level judgment.

Input
Problem listLabsEncounter note
Deterministic
Rules for provable facts
  • I13.10 -> CKD stage gap
  • O24.819 -> demographic mismatch
LLM lanes
Models for judgment
  • E/M rationale
  • Audit risk
  • Broad review
Normalize

Provider-specific JSON shapes are converted into one canonical Cortex contract.

Filter

Policy drops unsafe, duplicated, or clinically unsupported model output before it reaches the HUD.

Coalesce

Overlapping findings merge into one card with distinct fix options preserved.

One HUD card per supported issue

The user sees specific, explainable fixes rather than raw model output or duplicate findings.

Layer 1

Deterministic analyses

Small rules catch facts we can prove from structured chart data. Same input, same output, no model drift.

  • Every mutually exclusive pair in the official ICD-10-CM Excludes1 table — 5,000+ payer denial rules, checked on every chart
  • CKD stage missing from I13.10
  • Demographic contradictions on active codes
  • Structured problem-list hygiene
Layer 2

LLM analysis lanes

Models handle contextual judgment: note support, E/M rationale, audit risk, and broader chart review.

  • Encounter-note support
  • E/M level and next action
  • Documentation gaps that need language judgment

Why not all LLM?

Because healthcare QA needs boring guarantees in the places where guarantees are possible. Models are valuable, but they should not be responsible for every obvious rule, every time.

Consistency

Rules catch the same CKD-stage or demographic mismatch every run.

Cost and speed

Cheap checks can stream first while model lanes continue in parallel.

Provider independence

If a model or provider changes behavior, proven checks still hold.

Safety boundaries

Normalization, policy, and coalescing prevent malformed or unsafe output from becoming UI.

Built for regression resistance, not demo-day luck.

Every layer has a narrow contract: rules, provider adapters, normalization, policy, coalescing, and HUD rendering. When a production failure appears, it becomes a fixture before it becomes tribal knowledge.

Provider contractsAnthropic + Cerebras
Regression fixturesModel drift cases
Safety eventsDrops + latency + errors
UI fixturesFragile HUD states