medOS AI
Unified Clinical Assistant
One chat/voice surface for any action
A single LLM function-calling loop drives reads, actions and form-fills: biomarker time-series queries, orders with a mandatory confirm gate, and registry-driven form filling — where the same form schema feeds the LLM and a human 'what can I say' palette.
K+ falling post-protocol — next draw due 16:00.
Draft order: BMP · 16:00 · bed 5B-2 — Confirm / Edit / Cancel
FORM-FILL via forms_registry · no autonomous writes · full RunnerStep audit
Capabilities
Three tool classes with distinct safety contracts: READ / ACTION / FORM-FILL
forms_registry schemas power both AI fill and human discoverability
Every write funnels into existing endpoints behind a confirm gate
Next-best-action nudges from empirical navigation patterns — abstain-first