Clinical Manager
An agent for the operational layer of a clinical team: what is late, what is unsigned, what is about to be missed, and the next action for each, drafted and routed for approval.
Specification.
What it reads, what it may write, what it must pass, and how a change to it is judged.
| Domain | Clinical operations |
|---|---|
| Status | Production |
| Trigger | Schedule and change events from the systems of record |
| Reads | Schedules, orders, documentation and staffing, scoped per role |
| Writes | Drafts only. Every outbound action passes the approval gate |
| Gate | Role-scoped approval, bound to the exact payload |
| Models | Routed per step through the gateway; structured outputs |
| Evals | Ranking and drafting suites, run in CI on every change |
What it does.
Ranks the day's clinical work by risk, drafts the follow-ups, and routes each one to the clinician who owns it for approval.
Risk-ranked worklist
Overdue tasks, unsigned orders and incomplete documentation merged into one queue and ordered by consequence, not by arrival time.
Drafted follow-ups
Clinician reminders, physician-office requests and shift handoffs generated as structured drafts, each tied to the record that caused it.
Coverage matching
Appointments at risk of being missed matched to available clinicians on skill, credentials and availability, proposed as a reassignment.
Daily brief
A deterministic morning summary for the clinical lead: what changed, what is at risk, and the ordered actions.
The rules it holds.
The same six invariants hold for every AgencyAI system.
- INV-01
Least privilege
Every connector is scoped to the fields one job needs. No agent holds a credential broader than its task.
- INV-02
Typed boundaries
Tool inputs and model outputs are validated against schemas at every boundary. Invalid output is a failed step, never a guess.
- INV-03
Idempotent effects
Every side-effecting call carries an idempotency key. Runs are resumable state machines; a retry cannot double-send.
- INV-04
Gated consequences
Actions are classed by consequence. Anything that leaves the system needs a role-scoped approval bound to the exact payload.
- INV-05
Append-only record
Inputs, tool calls, model calls, outputs and approvals are written to an append-only audit log, reviewable per run.
- INV-06
Evals gate merges
Prompt, model and tool changes run the eval suites in CI. A regression blocks the merge like a failing unit test.
The books are closed.
We work with a few enterprise companies at a time. If you have a project and want to know whether an opening comes up, write to us. You will get a straight answer either way.