Health insurance claims management software: built for a file with two different authors

J.D. Power's 2026 commercial health plan study found that only 30% of members describe their claims resolution as excellent, and that group scores 120 points higher on overall satisfaction than members who call the same experience merely great. Claims are one of the few moments a health plan actually touches a member's life directly, and most of that gap comes down to something structural, not attitudinal: a health claim usually has more than one author, and most claims software is built around the assumption that it has exactly one.

Two people, one file

A member submits a claim: an invoice and a prescription, sometimes a diagnosis code too. In most designs, that's treated as the whole submission, the same shape as a car claim or a property claim. But a health claim frequently can't actually be assessed until someone else weighs in too, a treating doctor or a hospital, confirming a diagnosis or describing a treatment in terms the insurer's own rules can evaluate.

That second party has no account with the insurer and no particular urgency to respond. The claim sits open because the file is genuinely incomplete, waiting on somebody who was never part of the relationship in the first place, through no fault of the member's. Software built around a single submitter treats this as an edge case to work around by hand: someone on the claims team has to notice the gap, figure out who to chase, and follow up by phone or email outside whatever system is tracking the claim itself.

The questionnaire that decides the outcome

The second structural difference is what happens once the documents are in. A meaningful share of health claims, especially anything involving incapacity or a treatment tier, get decided by a medical questionnaire assessed against the insurer's own scoring rules, well beyond a simple document check. One insurer we've seen work through this designed a questionnaire that computes a severity classification directly within the claim intake itself, using the insurer's own correspondence table between symptom and severity, so the claimant's session never depends on a live call to an internal rules engine partway through. The back-office system receives the computed result directly, already scored and ready to act on.

Done manually, that scoring step is exactly the kind of work that stays slow however careful the person doing it is, because someone has to hold a table in their head, or open it in a second window, for every single file.

What changes when this is handled well

The fix for the first problem isn't a general reminder system. It's treating the second party's contribution as its own tracked step inside the same case, with its own targeted request sent directly to whoever needs to respond, a doctor or a hospital, instead of an unstructured follow-up the member has to somehow arrange themselves. The case stays whole. The team can see exactly what's missing and from whom, instead of a claim that looks complete to the software and incomplete to everyone actually working it.

The fix for the second problem is building the scoring logic into the intake itself. The questionnaire's answers get evaluated against the insurer's own table as they're entered, and the computed classification, not just the raw responses, is what the back-office system receives. Nobody re-keys a severity score from a printed table, and nobody has to trust that two different reviewers would have scored the same answers the same way.

What good looks like in practice

A member submits a claim for a specialist treatment. The claim itself, submitted through a short form, triggers a separate, targeted request to the treating specialist's office for a supporting report, tracked as part of the same case rather than a side conversation. When the report arrives, it's read and matched to the claim automatically. The questionnaire the member completed at intake has already been scored against the plan's own severity table, so by the time a claims handler opens the file, the classification is already computed and sitting there, ready to act on.

Nobody spent the week calling a specialist's office to ask where the report was. The file was complete, and already scored, by the time it needed a person's judgment.

When to start

Health claims will keep having two authors regardless of what software a plan uses, and the questionnaire-to-classification step isn't going away either. What's optional is whether that structural reality gets handled by people working around gaps in the system by hand, or by a process built to expect it from the start.

The manual version was shaped around what a claims team could track by memory and follow-up calls. A well-run version is shaped around the fact that a health claim was never really a single-author document to begin with.

Penbox runs claims management on top of the systems you already use, including the parts of a claim that depend on someone outside the member relationship entirely. If you want the wider picture first, here is what case management means.