Clinical Assessment
Patient assessment
Agent convergence
De-escalate empirical regimen
Governance
The UI never promotes a clinical recommendation. It displays the backend governance decision, violations, warnings, and knowledge-base provenance.
Fail closed
Blocked antibiotic outputs do not cross the governance boundary.
Immutable KB
Guideline versions are published as new versions; existing versions are never overwritten.
Human approval
Guideline surveillance creates pending review records rather than activating changes.
Audit trail
Case assessment and governance events are recorded for traceability.
Decision boundary
| Control | PASS | WARNING | BLOCK |
|---|---|---|---|
| Antibiotic response | Allowed | Allowed with warning | Not exposed |
| Guideline update | — | Pending review | Not activated |
| Missing critical input | — | Flag | Escalate / no silent guess |
| Provenance | Versioned | Review required | Unverified source blocked |
Recent governance decisions
Memory & Clinical Analytics
Only aggregate, de-identified metrics are displayed here. Patient identifiers are not rendered in the analytics dashboard.
System memory
The four numbers above come from this raw aggregate — kept here as the audit source, not for reading directly.
View raw JSON (audit / developer)
Loading analytics…
Outbreak & device-association flags
Statistical co-occurrence flags for infection-control / epidemiologist review — never a causal diagnosis, and not scoped by ward or unit. Requires a culture organism recorded via the De-escalate form to appear.
Insights briefing
The narrative below can only describe numbers already computed in the statistics panel — it never adds a fact, count, or cause that isn't already there.
View full statistics (audit / developer)
Five-agent architecture
Independent agents converge through a governed channel — the same design carried through from the login screen. The system is designed around provenance, deterministic clinical rules, controlled memory, and explicit physician authority.
Antibiotic guidelines
Pending guideline changes require reviewer approval before they can become the active knowledge base — nothing activates automatically. Source acquisition currently requires a licensed feed to be wired in per config/source_registry.json; until then this page reflects whatever reviews exist and lets you exercise approve/reject manually.