DPC AI scribe 2026: subscription-free practice, long visits, member continuity, and the variable-cost stack

May 9, 2026 · 6 min read

Direct Primary Care physicians left the fee-for-service treadmill specifically to escape billing infrastructure: no insurance claims, no CPT coding under pressure, no RVU targets, no prior authorizations. Members pay a flat monthly fee ($60-150 typical), get unlimited visits, longer appointment slots (30-60 minutes is normal), and direct access to their physician via text or telehealth. The economics work because panel sizes are smaller (300-800 members vs the 2,000-2,500 of fee-for-service primary care) and the overhead is leaner.

This setup creates a peculiar tension with traditional AI scribe vendors. Subscription scribes at $200-300 per provider per month are designed for fee-for-service practices where billing-grade documentation drives revenue. DPC docs do not need HCC capture (no risk-adjusted contracts), do not need HEDIS measure surfacing (no value-based payor pressure), and do not need E/M coding optimization (no E/M codes billed). What they need is a long-visit narrative documentation pipeline, member-level continuity (scribes that remember the last 3-5 visits with this member), and a pricing structure that flexes with the variable panel (some weeks are slammed, some are quiet).

The 2026 DPC-aware AI scribe stack handles four things: long-visit documentation that captures depth without forcing fee-for-service templates, member-level continuity surfaced into each visit, asynchronous touchpoints (text / portal messages) folded into the chart, and the pay-as-you-go pricing that aligns with how DPC practices actually run.

The DPC visit profile

A typical DPC visit looks unlike fee-for-service primary care:

• 30-60 minute slots — vs 15-20 in FFS. More history, more counseling, more shared decision-making.
• Member context built up over time — physician knows the member's job, family, stressors, medications, lifestyle goals.
• Lifestyle and prevention-heavy — sleep, nutrition, exercise, mental health, financial stress are normal topics.
• Async touchpoints between visits — text questions, photos, refill requests, lab review, all needing chart capture.
• Procedures and POC labs in office — many DPC docs run their own CLIA-waived lab and basic procedures (skin biopsies, joint injections, IUDs) since cash pricing is transparent to members.
• Direct referrals to cash-pay specialists and imaging — member-aware cost transparency is part of the value.

Generic scribe templates produce notes that read like fee-for-service primary care chart-bait. DPC docs want narrative chart entries that read like a continuing relationship document, not a billing artifact.

The DPC system prompt

You are documenting a Direct Primary Care visit.

INPUT:
- Encounter audio transcript
- Member profile: age, occupation, household, prior visit narrative summaries (last 3-5)
- Active problems list (member-curated, not insurance-curated)
- Async touchpoints since last visit (text threads, portal messages, lab review)

OUTPUT a continuing relationship document:

1. Visit reason in member's words
2. Interval narrative since last touch (visit, text, lab, etc.)
3. Today's exam and findings (only what was actually examined)
4. Lab / imaging review (in-office POC and outside)
5. Discussion: shared decision-making content, options weighed, member preferences
6. Plan by problem (medication, procedure, monitoring, lifestyle, referral with cash-pay context if applicable)
7. Member education and coaching content
8. Continuity flag: anything from prior visits that should be revisited next time

DO NOT:
- Force CPT or E/M coding (DPC does not bill insurance)
- Pad ROS or exam beyond what was actually done
- Use risk-adjustment or HCC vocabulary
- Use HEDIS measure framing

DO:
- Preserve member voice in the narrative
- Note follow-up triggers (member is starting a new job in 3 weeks; reassess sleep)
- Capture cash-pay referral details (specialist name, expected price, any negotiated rate)
- Flag controlled-substance prescribing in line with DEA + state PMP requirements
- Maintain a running member-level summary that updates with each visit

Cite transcript. Use narrative voice over template voice.

Member-level continuity is the DPC superpower

Fee-for-service primary care optimizes for the visit. DPC optimizes for the member. A DPC scribe that only sees the current encounter underdelivers. A DPC scribe that has read the member's last five visits, the text thread from last week, and the lab from yesterday produces dramatically better notes — surfacing the kind of pattern recognition (sleep problem worsening over three visits, gradual weight gain after starting a new SSRI, recurring stress about job change) that DPC physicians built their practices to deliver. The DIY stack with a member-level context window is the practical way to deliver this; vendor scribes generally start each session cold.

Async touchpoints in the chart

DPC practices live and die by member texting and portal messaging. A member texts at 7am about a sore throat, the doc replies at 9am, the chart should reflect both. Most ambient scribes do not handle this; the doc ends up double-entering text content into the chart manually. A DPC-tuned pipeline includes a path for non-audio touchpoints — pasted text threads, portal messages, photos — into the visit summary or as standalone async-encounter entries. The infrastructure for this is straightforward (forward to a text-input pipeline that the same LLM summarizes) but vendor stacks rarely expose it.

The variable-cost economics

A DPC practice with 500 members at $90 per member per month grosses $540k annual collections. Visit volume varies wildly: a quiet week might have 20 visits, a flu week 60. Fixed-fee subscription scribes at $200-300 per provider per month do not feel expensive on paper but they take a constant bite even when visit volume is low. The math:

• Subscription scribe at $250/mo: $3,000/yr fixed, regardless of visits.
• Pay-as-you-go LessRec at $0.05/min: 30 visits/wk × 45 min average = ~22 hr/wk = ~$66/wk = ~$3,400/yr at high volume; ~$1,200/yr at low volume.

The variable-cost structure rewards DPC practices in slow seasons and is roughly cost-neutral in busy seasons. More importantly, it removes the friction of paying for unused capacity during travel weeks, parental leave, or member-panel rebalancing.

Vendor and DIY paths

Vendor ambient scribes (Suki, Heidi, DAX Copilot via EHR) work mechanically — they capture conversation. They are designed around fee-for-service templates that produce chart documents DPC docs find uncanny: too much ROS, too much E/M-code padding, too little narrative voice. The DIY stack — LessRec Whisper API + a DPC-tuned narrative system prompt + a lightweight EHR (Atlas.md, Hint, Elation, Spruce) — produces notes that feel like the practice. Build time is a weekend; the prompt iterates over the first month as your style stabilizes.

BAA chain

Practice + EHR (Atlas.md, Hint Health, Elation, Spruce, OpenEMR DPC mod) + transcription vendor + LLM vendor.

When to start

DPC physicians who left fee-for-service to escape billing infrastructure should not adopt a scribe that re-imports fee-for-service vocabulary. The DIY stack with a narrative system prompt and member-level continuity is the path that matches how DPC actually runs. The variable-cost pricing is a second-order benefit that aligns the scribe spend with the variable panel reality.