Primary care / physician practices Operations Questions
The questions that recur in primary care share one shape: the payer's scorecard and the patient's experience drift apart quietly. Quality bonuses improve while satisfaction falls, front-desk verification errors predict denial write-offs two months out, and a departing provider takes 40 percent of the panel with them. The answers below ask whose definition of good the practice is optimizing.
-
Why do highest-need patients generate the most after-hours calls and least revenue per visit. Care model or payer mix?
Both, and they compound: complex patients need care management between visits (uncompensated
Activity), and fee-for-service pays per visit, not per coordination. The fix is structural, CCM billing, nurse triage protocols, panel complexity weighting, not working harder inside a model that prices the wrong unit.§1.1 InfrastructuralDecisions, §8.2, D3 NNVA
-
Quality-bonus metrics improve while satisfaction drifts down. Are we optimizing for the payer's definition of good?
Yes. Goodhart with a billing code: the payer's checklist (screenings, documentation) is measured and paid. The patient's experience (time, listening) is neither. You serve two principals with conflicting KPIs. Add experience measures to your own scorecard so the payer's do not run the practice alone.
§13 Goodhart, §1.3 BalancedScorecard, §6.3 SERVQUAL
-
Why does revenue per provider vary 35% with identical panels and payer mixes?
Coding intensity, visit-length norms, and same-day access behavior differ. With panels equalized, the variance is in how providers work the panel. Chart-audit coding levels first (usually the biggest factor), then schedule density. This is process variation, not patient variation.
§6.3 SPC special cause, §4.4 work measurement, §0.3 measuredBy
-
Does referral leakage to out-of-network specialists cost more downstream than the visit revenue protected?
For risk-bearing contracts, usually yes: leaked referrals lose downstream ancillary and follow-up revenue plus care coordination. Map referral flows and put a value on retention. Then build the in-network preference into the referral workflow (EHR defaults, care coordinator ownership).
§11.2 network design, §8.2 blueprint, §4.1
-
Did the nurse triage line cut visits by resolving issues or by adding friction. Can we tell?
Yes: resolved issues show stable outcomes with lower visit volume. Friction shows deferred visits reappearing as urgent care/ED visits later. Track downstream encounter data and complaint themes. Resolution is
VA. Friction isNVAwearing a costume. The downstream data distinguishes them.D3 VA/NVA, §8.2 blueprint, §6.3 SERVQUAL access
-
No-shows cluster by appointment type rather than patient. What does the schedule do to create them?
Long-lead appointment types (physicals booked 6 weeks out) decay in commitment. The schedule's own lead time manufactures the no-show. Shorten booking horizons for routine types, overbook strategically by type-specific no-show probability, and confirm at 48h.
§8.1 abandonment, §8.2 yield/overbooking, §2.1
-
Why does front-desk verification error rate predict denial write-offs two months later, and why is not it managed?
Because verification is an upstream
Activitywhose defects surface downstream as denials. Classic quality-at-source failure. It is unmanaged because the front desk and billing are siloed KPIs. Assign the denial cost back to the verification step and it becomes someone's number.§6.3 poka-yoke/at-source, A8 traceability, §6.2 internal failure
-
Panel keeps growing while same-week access worsens. At what size did we cross the line. Who was watching?
Nobody. Panel size is an ungoverned capacity decision. The line is where appointment demand rate exceeds slot supply (Little's Law: growing panel ÷ fixed slots = growing wait). Set a panel cap per provider tied to access KPIs, and make adding patients a deliberate capacity decision.
A1 Little's Law, §4.2 effective capacity, §8.1
-
When a provider leaves, why do 40% of patients leave the practice instead of transferring internally?
Because the relationship asset was personal, and your transfer process is administrative (a letter) instead of clinical (a warm handoff with the receiving provider meeting the panel). Patients treat the departure as a free choice point. Engineer the handoff like a referral, not a notice.
§13 relationship capital, §8.2 blueprint, §6.3 empathy
-
Are CCM billings a care model or a billing program. Would documentation survive an audit assuming the latter?
Stress-test it: sample CCM notes for actual care-management content (care plans, coordination calls, time logs) versus templated boilerplate. If the 20 monthly minutes are not traceable to real activities, it is a billing program with audit exposure. Build the workflow first. The billing follows the work.
§0.3 specifiedBy/governedBy, A8 traceability, §14 compliance
How these answers work
Each answer names the operational mechanism the question is circling, then states the directive that follows from the ontology in Part One of the book. Bracketed citations point to the ontology sections and axioms that produced the answer.
Related industries
- Chiropractic operations questions
- Dental practices operations questions
- Physical therapy clinics operations questions
- Urgent care clinics operations questions
- Mental health / counseling practices operations questions
Keep reading
Reading the question that matches your situation is not the same as correcting the structure underneath it. World Consulting Group works with operators on exactly the corrections this book describes.
Talk to World Consulting Group