Clinical Documentation

Physicians Spend 15 Hours a Week on Documentation. That's a Staffing Problem.

· 6 min read
The documentation burden on physicians — abstract concept

The American Medical Association has published physician workload surveys for years. One consistent finding: documentation takes somewhere between 13 and 16 hours per physician per week depending on specialty. The number gets cited regularly in healthcare tech circles. What gets discussed less often is what that number implies about how practices are staffed.

If a physician works 50 clinical hours per week and spends 15 of them on documentation, roughly 30% of total physician capacity is allocated to clerical record-keeping. That's not a charting preference problem or a typing speed problem. It's a workflow design problem, and it has a staffing cost attached to it that most practices have never made explicit.

What 15 Hours Actually Looks Like

The documentation burden isn't evenly distributed across the day. It clusters in two places: between appointments (the "pajama time" phenomenon of finishing notes after clinic ends, often at 9 or 10 PM), and during encounters themselves, when a physician is trying to maintain eye contact and clinical conversation while simultaneously entering data into an EHR.

For outpatient specialty practices on a 20-minute encounter slot, the EHR time pressure is particularly acute. A focused cardiology follow-up — reviewing a patient's rhythm strip, adjusting a medication, discussing a recent stress test — requires a SOAP note that documents the subjective report, the objective findings, the assessment with relevant ICD-10 codes, and the plan including any procedure orders, referrals, or prior auth triggers. Doing that in a 20-minute encounter while also talking to the patient is functionally impossible without either rushing the note or spending time after the encounter.

Most physicians do both: they take fragmentary notes during the encounter and complete the full chart entry after hours. The resulting documentation is clinically adequate — it captures what happened. But it's written under fatigue, and it often lacks the structured specificity that becomes important when a payer later scrutinizes the note to adjudicate a prior authorization.

The Staffing Math Most Practices Skip

Let's make the cost explicit. A physician billing at a mid-market outpatient rate in a specialty practice — say, a rheumatologist in a growing group practice in the greater Boston area — generates roughly $350 to $500 per clinic hour in reimbursable encounters. If 15 hours per week are spent on documentation that could in principle be automated or substantially accelerated, that's $5,250 to $7,500 per week in physician capacity allocated to non-clinical work.

That's not recoverable through billing, because those hours aren't patient care hours. They're overhead hours that happen to require a physician's credential to complete. The 15-hour number isn't just a physician satisfaction problem — it's a direct constraint on practice throughput and therefore practice revenue.

The standard response practices have used is to hire scribes. A full-time in-person medical scribe costs $35,000 to $55,000 per year depending on market. They solve the during-encounter documentation problem reasonably well when well-trained, but they don't solve after-hours note completion, they require training time, and they introduce HIPAA considerations around a third party present during every patient encounter. Many practices that tried in-person scribes at scale found the logistics difficult to sustain.

What Ambient Scribing Changes (and What It Doesn't)

Ambient clinical documentation — where a microphone captures the encounter and a language model produces a structured clinical note for physician review — addresses the real-time documentation pressure directly. The physician conducts the encounter as they normally would. The note is generated, structured as a SOAP format document with appropriate ICD-10 coding suggestions, and placed in the review queue before the next patient is called.

What this changes: the fragmented note-taking during the encounter stops. The after-hours note completion queue shrinks because notes are 80 to 90% complete by the time the physician reviews them, rather than beginning from a blank template. For a practice with a 15-physician group, that can translate to 30 to 50 hours per week of physician time that shifts from documentation to clinical activity — or simply to a sustainable end-of-day.

We are not saying ambient scribing eliminates physician documentation time entirely. Physicians still review and sign every note. For complex encounters — a new patient with multimorbidity, a difficult conversation about end-of-life preferences, a post-procedure note with unusual findings — physician editing remains substantial. What ambient scribing eliminates is the mechanical production of structured documentation for routine and follow-up visits, which represent the majority of outpatient encounters.

Why This Is a Staffing Problem, Not a Tool Problem

The framing matters because it changes how a practice leadership team thinks about the investment. Buying an ambient scribing subscription is not purchasing a software tool for physician convenience. It's making a staffing decision: replacing a category of documentation labor that currently consumes physician time with automated documentation that frees physician time for higher-value work.

At a 15-physician practice with average documentation load, the effective staffing freed is something like 2 to 3 full-time-equivalent positions worth of physician time per week. That can translate to 8 to 12 additional patient slots per week, reduction in physician overtime, lower burnout-related attrition, or a combination of all three. Any of those outcomes has a value that is straightforward to calculate and compare against the cost of the tooling.

The reason this calculation often doesn't happen is that documentation time is invisible as a cost line. It shows up as physician dissatisfaction, as burnout survey scores, as after-hours EHR activity logs — but it doesn't appear on a P&L as a separable expense that can be reduced. Making it visible requires framing it as a staffing allocation question, not a productivity or workflow preference question.

The Documentation Quality Dimension

There's a second consequence to the 15-hour documentation burden that rarely enters the staffing conversation: documentation quality under fatigue is lower than documentation quality produced in real time.

A note written at 10 PM for an encounter that happened at 2 PM relies on a physician's recall of a conversation that ended eight hours ago. Details that seemed important at the time may be less present. Specific patient-reported symptoms — the exact character of pain, the specific circumstances of a medication side effect, the treatment history that will matter if a PA is submitted — may be documented less precisely than they were discussed.

For prior authorization purposes, this matters significantly. A SOAP note where the assessment section specifically articulates why a standard therapy was tried and failed, in language that maps to the payer's step therapy criteria, is a stronger PA submission basis than a note that says "patient has not responded to methotrexate." The former is likely to pass automated PA review. The latter may require a peer-to-peer review call that takes an additional two business days.

Ambient documentation captures clinical reasoning in the moment. The physician's explanation of why a particular medication is appropriate, the specific clinical findings that support the assessment, the articulation of medical necessity — all of that is captured as it's spoken, not reconstructed hours later. That documentation quality difference has real downstream value in PA submission outcomes, which is why we've built Prioriq's ambient layer to feed directly into the PA workflow rather than treating documentation and prior auth as separate products.

A Realistic Starting Point

If your practice is evaluating ambient scribing, the most useful pilot design is specialty-specific. A cardiologist's documentation patterns differ from an orthopedic surgeon's differ from a rheumatologist's. The note structure, the typical ICD-10 codes, the procedure documentation patterns — all of these vary by specialty, and a general-purpose ambient scribe will produce better initial output in specialties where it's been more extensively trained.

Track documentation time per encounter before and after, not just physician satisfaction scores. Satisfaction improves reliably, but the business case depends on demonstrable time reduction. For a well-tuned ambient implementation on routine follow-up visits, post-encounter documentation time typically drops from 8 to 12 minutes per encounter to 2 to 4 minutes of review-and-sign. That's the number worth measuring.

Continue reading

All articles
Request Early Access