Free · ten questions · no email
Your LIS knows the test was run. Your billing system knows what was claimed. The clearinghouse knows what was accepted. The remittance knows what was paid. Each one is individually fine. Almost nobody reconciles across all four, and that is where the money goes.
This asks about ten specific seams. It gives you a prioritized focus list, not a dollar figure. If you want the dollars, the calculator does that job. Nothing is sent anywhere.
How to answer
A leak you know about is a decision. A leak you cannot see is a liability, because you cannot size it, staff against it, or tell anyone whether it is getting worse. Most organizations have more of the second kind than the first.
So answer honestly rather than optimistically. The output ranks what you cannot see above what you can, because that is the order in which they are worth fixing.
{{ progressLabel }}
{{ q.num }}
{{ q.text }}
{{ q.why }}
Your result
{{ bandBody }}
Start here. You cannot see these
{{ item.text }}
{{ item.action }}
Then these: known and untracked
{{ item.text }}
{{ item.action }}
{{ closing }}
What this is not
It is not an audit
It is ten questions answered from memory. A real audit looks at your data and produces numbers. This produces an ordered list of where to look, which is a genuinely different and cheaper thing.
It gives you no dollar figure, on purpose
Any number we produced from ten yes-or-no answers would be invented, and you would reasonably stop trusting the rest of it. Sizing a leak requires your actual data.
Some of these are fine to leave alone
A leak that costs less to tolerate than to close should be tolerated deliberately. The point of naming it is that the decision becomes conscious rather than accidental.
Nothing here is sent to us
No email, no submission, no analytics on your answers. The result exists in your browser and disappears when you close the tab. Our privacy page.
Related
Five minutes
ROI calculator
The dollars this deliberately does not give you, with every assumption visible and adjustable.
Run it →Service
Denial management
Several of these leaks are denials nobody worked. This is how the recurring ones get closed upstream.
See the service →Sector
For diagnostics labs
Why lab billing leaks differently, and why the fix usually starts at intake rather than at the claim.
Read it →