Back to playbooks

Module: Healthcare (Bills + Delays + Admin Drag)

Purpose: reduce the monthly squeeze by making care easier to use, easier to price, and less likely to turn into paperwork or debt.

This module is designed to be runnable by normal people in small weekly sprints.

What is happening (1-2 sentences)

Healthcare squeezes people through bills, denials, and time lost in the maze before care even starts.

The practical problem is not just cost. It is cost plus delay, confusion, and debt risk.

Why it is happening (mechanism, plain language)

The healthcare squeeze usually lives in one of three arenas:

A) hospital pricing and billing opacity
B) insurer prior-auth and denial churn
C) debt and collections after the fact

The common thread is simple: too much money and time get burned in the maze before they get to actual care.

What good looks like (principle)

A healthier local healthcare system has:

• clearer prices before and after care
• fewer delays from prior auth and billing churn
• charity care and debt protections that work before collections start
• less admin drag on clinicians, staff, and patients
• simple public metrics so people can tell whether anything is improving

Pick your arena first

Do not run the whole system at once. Pick one arena for one sprint.

Arena A: Hospital transparency and billing

Run this when prices are opaque, itemization is weak, or charity-care information is buried.

Arena B: Insurer prior auth and denials

Run this when delay is the harm and nobody can explain response times, denial rates, or overturn rates.

Arena C: Debt protections and collections

Run this when the bill is landing after the fact and the problem is collections, payment plans, or charity-care screening.

Default plays (recommended)

Default Play A: Charity care before collections

Run this when local hospitals are nonprofit, collections are active, and people learn about assistance too late.

One Ask (template): Require nonprofit hospitals to screen for charity care before collections activity begins, publish plain-language financial-assistance rules, and report quarterly on screening and collections volume.

Minimum components:

• plain-language charity-care eligibility rules
• screening before collections
• payment-plan standards
• quarterly public reporting

Why it wins: It is concrete, locally understandable, and reduces harm fast.

Default Play B: Prior-auth transparency

Run this when the squeeze shows up as delay, confusion, and repeated insurer fights.

One Ask (template): Publish prior-auth turnaround times, denial rates, and overturn rates by payer every quarter, with a named owner and response-time standard.

Minimum components:

• median turnaround time
• denial and overturn rates
• plain-language denial explanation rules
• escalation path when deadlines are missed

Why it wins: It turns a black box into something measurable.

Rule: if your group is small, run one play at a time. If you have allies, you can run hospital and insurer plays in parallel.

Definition of Done (every module sprint)

At the end of any Healthcare sprint, you should have:

1. One ask
2. One target map
3. One 1-page ask memo (250-400 words)
4. One 90-second testimony script
5. One scoreboard stub (3-5 metrics + data source)
6. One follow-up date
7. One public-record step if ignored

If you do not have #2, you are not doing healthcare civics yet. You are doing healthcare frustration.

Target map (who can say yes)

Local targets

• hospital CFO or revenue-cycle lead
• hospital patient-financial-services lead
• county or city health committee chair
• county public health or human services leadership
• major employer benefits office

State targets

• insurance regulator
• attorney general consumer protection office
• health department or state hospital regulator
• legislative health committee chair

Large buyers and civil society

• self-insured employers
• large union benefit plans
• patient advocates, legal aid, clinician groups

Receipts stubs (what to gather before you argue)

You only need a few items to build shared reality.

Hospital pricing / billing:

• hospital financial-assistance page
• billing and collections policy
• price-transparency page or file
• sample itemized bills or estimate tool screenshots

Prior auth / denial:

• denial stories turned into case files
• any published payer turnaround standards
• employer or plan complaint patterns
• regulator complaint or enforcement reports

Debt / collections:

• charity-care screening steps
• collections vendor relationship if visible
• payment-plan terms
• medical-debt protections in local or state law

Use a case-file approach when stories are doing too much work.

Escalation ladder (what to do when ignored)

Level 1 - direct ask

• email staff owner + elected sponsor with one-page memo

Level 2 - office hours

• ask: “Who owns implementation, and who can draft the reporting or policy language?”

Level 3 - public record

• 90-second testimony + written comment into meeting or board record

Level 4 - accountability move

• records request, regulator complaint, or audit ask

Level 5 - budget / rule change

• add reporting requirement, debt-protection rule, or enforcement capacity ask

Scoreboard (choose 3-5 metrics)

Pick a small set that matches your play.

If running Play A (charity care before collections)

• share of patients screened before collections
• number of accounts sent to collections
• median time from bill to collections
• payment-plan uptake and completion
• plain-language policy availability

If running Play B (prior-auth transparency)

• median prior-auth turnaround time
• denial rate
• overturn rate
• share of denials with plain-language explanation
• complaint volume or escalation count

If working general billing clarity

• price-transparency compliance
• share of itemized bills provided on request
• estimate tool usability for common services
• average time to resolve billing disputes

60-minute Healthcare Sprint (minimum viable)

If you only have an hour:

1. 10 min: pick Arena A, B, or C
2. 10 min: build your target map
3. 20 min: write the one-page ask memo + scoreboard stub
4. 10 min: send two emails
5. 10 min: schedule follow-up + log

Done. Repeat next week.

One Ask examples (ready to use)

• “Require nonprofit hospitals to screen for charity care before collections and publish quarterly screening and collections data.”
• “Publish prior-auth turnaround times, denial rates, and overturn rates by payer every quarter.”
• “Audit hospital price-transparency compliance locally and publish a simple scorecard by quarter.”
• “Create plain-language payment-plan standards and publish basic collections metrics.”

Bridge language (calm, non-tribal)

• “I am not asking for perfection. I am asking for fewer tollbooths between a patient and care.”
• “A delay can be a denial with better manners.”
• “If the price is real, it should be explainable before the bill lands.”
• “More spending should mean more care, not just more maze.”

Weekly cadence (how to keep it small and real)

• Week 1: pick the arena + send the ask
• Week 2: office hours or staff follow-up
• Week 3: public record step
• Week 4: follow-up for inclusion and reporting

Then repeat or pivot based on what moved.

Back to playbooks