Case File 01 · Healthcare
Returning clinician time with ambient documentation
Representative — regional health system
▸ ENGAGEMENT DETAILS
Representative scenario modeled on published industry benchmarks. Not a named client.
The Challenge
A representative regional health system runs inpatient, outpatient, and emergency services across multiple sites, and its clinicians carry a documentation load that pulls them away from patients.
Published time-motion research puts physicians at roughly 49% of the working day on EHR and desk work against about 27% in direct patient contact, with around 4.5 hours a day inside the record (Sinsky et al., AMA). Administrative work is among the most-cited drivers of burnout, and roughly 25% of US health spending is administrative (McKinsey).
In this scenario the same pressure shows up in two places: notes finished after hours, and intake documentation that varies between shifts. The constraint is not clinical judgement — it is the keystrokes around it.
Our Agent Solution
We deploy MedAgent — our healthcare agent system — as an ambient documentation workflow, with triage support as a secondary agent. It connects to the health system's EHR via FHIR to read the clinical context a note depends on, drafts the encounter note as the visit happens, and routes every draft back to the treating clinician for edit and signature. A triage-support agent structures intake against the health system's own ESI criteria and flags inconsistencies for a nurse to resolve. Nothing is filed and no severity is assigned without a clinician in the loop.
Ambient Documentation Agent
Drafts the encounter note from the consultation and structures it to the health system's own templates
Clinical Context Agent
Retrieves relevant history, medications, and results from the EHR via FHIR to ground the draft
Triage Support Agent
Structures intake against the health system's ESI criteria and flags inconsistencies for nurse review
Review & Handoff Agent
Routes every draft to the treating clinician for edit and signature, then generates the handoff summary
Implementation Timeline
A representative 12 weeks delivery path, from discovery to handover.
Discovery & Assessment
Mapped documentation and intake workflows, shadowed clinicians, audited EHR integration points and consent requirements
Weeks 1-2
Architecture & Design
Designed the agent pipeline, defined the review and escalation model, specified FHIR read/write scopes with the integration team
Weeks 3-4
Build & Evaluation
Built the agent system and tuned and evaluated it on the client's own historical corpus under a signed data agreement, validated against expert review
Weeks 5-9
Pilot & Iteration
Ran a limited-service pilot, measured note turnaround and clinician edit distance against the recorded baseline, refined templates and thresholds
Weeks 10-11
Handover & Rollout
Phased rollout with monitoring dashboards, alert thresholds, an operator runbook, and clinician training
Weeks 12
Target ranges — and today's baseline
Both sets of figures are drawn from published research, not from VelocityMind client results. Targets are the ranges this scenario is scoped against; baselines describe where the status quo sits. Actual results depend on your data, systems, and scope.
Less time on clinical documentation
Source · UW Health randomized trial, 2024-25 (~30 min per clinician per day)
30%
Of physicians reported higher satisfaction
Source · Permanente ambient documentation deployment, 7,260 physicians
82%
Where the baseline sits today
Published measurements of the problem, shown so the target ranges above can be read against something. These are not outcomes we delivered.
Of physician time is spent in the EHR today
Source · Sinsky et al., AMA time-motion study
49%
Of US health spending is administrative today
Source · McKinsey (~$1T, of which ~$265B is reducible)
25%
What ships — and what stays human
The artifacts you own at handover, and the decisions the agents never take.
▸ DELIVERABLES
What you receive
- Ambient documentation agents running in your environment, against your own note templates
- FHIR integration spec with the read and write scopes agreed with your EHR team
- Evaluation suite with a documented pre-deployment baseline for note turnaround and edit distance
- Clinician review workflow, escalation rules, and an operator runbook
- All source code in your repository, with the deployment owned by your team
▸ GUARDRAILS
What stays human
- Every note is reviewed and signed by the treating clinician before it enters the record.
- The triage agent structures and flags; a nurse assigns severity. The agent never sets an ESI score on its own.
- Diagnostic support is scoped as decision support only — published meta-analysis puts general GenAI diagnostic accuracy at roughly 52%, on par with non-experts and below experts.
- PHI stays inside the environment named in the data agreement. Model providers are selected with you, and your data is not used to train shared models.
Method and sources
This scenario is constructed, not reported. Every figure on this page traces to one of the published sources below.
Physicians spend ~49% of the day on EHR and desk work, ~4.5 hrs/day in the record
Sinsky et al., AMA time-motion study
~30 minutes per clinician per day saved on documentation with an ambient scribe
UW Health randomized controlled trial, 2024-25
82% of physicians reported higher satisfaction across 2.5M+ encounters
Permanente ambient documentation deployment (7,260 physicians)
~25% (~$1T) of US health spending is administrative
McKinsey
General GenAI diagnostic accuracy ~52% — below experts
Takita et al., npj Digital Medicine, 2025 (meta-analysis of 83 studies)
Ranges are published industry benchmarks. They describe what programs of this shape have achieved elsewhere, not a commitment for your environment — the range we would scope against for you is set after discovery.
A representative perspective
“Our physicians spend less time in the chart and more with patients, and intake is more consistent across shifts — with every note still reviewed by a clinician.”
▸ NEXT STEP
Run this against your own workflow
Send us one workflow, its monthly volume, and the systems it touches. We reply within one business day with a first read on whether an agent system is the right tool, the agent shape we would propose, and an engagement range.
No commitment. We reply within one business day.