Help a patient check whether they qualify for hospital charity care, even after the bill has gone to collections, challenge billing errors and surprise bills, and answer a lawsuit over a medical bill.
Why it matters for peopleCharity care and corrected bills can erase medical debt before it reaches collections or court.
This page is the shared target for this situation. Any court, legal aid office, or builder working on it in their own region can take the vision, the blueprints, and the standards here instead of starting over, and set the parts that are local to them. The point is that the same work is not designed from scratch in every county.
Does this match how it goes where you are? Leave a note on this workflow.
A medical bill arrives after the care, sometimes from a provider the patient never chose and cannot recognize. Bills carry errors: a charge entered twice, a service that was never given, insurance applied to the wrong claim.
Nonprofit hospitals run financial assistance programs that can reduce or cancel a bill, and eligibility often reaches further up the income scale than people expect. The assistance is usually still available after the account has gone to a collector, and sometimes after a lawsuit is filed. A person who does not know the program exists pays what they do not owe, or gets sued for it.
A system here reads the bill against the insurer's explanation of benefits, checks the household against the hospital's own published assistance policy, and assembles the application. Where a case has already been filed, it says which deadline comes first.
A person compares a bill against an explanation of benefits they may never have received, works out whether the hospital has an assistance policy and whether they qualify, finds the application, and gathers the proof it asks for. If a collector has already sued, they are answering a lawsuit at the same time, on a deadline the court sets.
A good system reads the bill and the explanation of benefits together, flags charges that do not match, checks the household against the hospital's published assistance criteria, assembles the application with the proof it asks for, and says which deadline is nearest when a case has already been filed.
Who this serves: Patients facing medical bills they cannot pay, and the advocates, financial counselors, and hotline staff who help them.
Nothing in this package is written yet. The cohort takes the workflow on, writes the step-by-step agenda first so practitioners can argue with it, and the rest follows from what comes back. This page says plainly where each piece stands, and it changes as they exist.
Stage 1
What a good tool does at every step of this work, written so a practitioner can argue with it and a builder can build from it.
The work in order, with what a good tool does at each part, what it must never do, and one question for the practitioners who do this work. This is the first thing the cohort writes.
The same work written as a numbered specification, capability by capability, for a builder to build against and an evaluator to test against.
How the pieces fit together, and which decisions deterministic rules make rather than the model.
Stage 2
How a team checks whether what it has is good enough to rely on, and how it keeps checking once the tool is running.
The tests a tool has to pass on accuracy, safety, usability, and whether the organization can keep it running.
Who runs the tests, what a pass takes in staff time, and how the results get written up so somebody outside the team can read them.
The debt collection cohort is forming now. Members bring what they have seen in their own practice, argue about what a tool here has to do, and read the drafts as they are written.