Know what changed. Know what got fixed.
An audit tells you what is wrong today. Monitoring tells you what arrived this week, what is still sitting there, and what your team has actually cleared.
Why a one-off audit does not hold
Marketplace (QHP) issuer files. A directory where half the findings are recent does not have a backlog problem, it has an inflow problem, and cleanup does not touch it. The inflow arrives a few records at a time and nothing in a normal directory process is reading the federal files that would catch it.
Three states, tracked over time
A federal file moved, and it now contradicts something you publish. Dated by the government, not by us.
We raised it before and it is still in the published directory. The age of a finding is the number that gets a plan's attention.
It is no longer in the file. We read the directory again and confirmed the change rather than taking anyone's word for it.
Every finding keeps its history, so a record that is corrected and then reappears is visible as exactly that rather than arriving as a fresh surprise.
Delivered where you already work
There is no portal you have to live in. The findings go where your provider-data process already is.
01 FILE
Scheduled and machine readable
The evidence file on a schedule, for batch ingestion into an existing provider-data workflow. Every row carries its source, the federal date and the gates it cleared.
02 API
Ask about one NPI, or a roster
Query findings, status and evidence from inside your own credentialing pipeline, at the point where a decision is being made.
03 WEBHOOK
Told when something changes
An event when a finding is created, changes state or resolves, so nothing depends on someone remembering to check.
Delivery is weekly, because the feed carries whatever has surfaced since the last one. Detection is only ever as fast as the federal file behind it, and those do not share a cadence. How often each source moves
Your queue on day one
Before any of this moves, it is worth seeing what an untouched queue looks like. This is the age profile of the cancelled-registration findings across every directory we read in August, measured from the federal event to the file we read it in.
A queue shaped like this is not a backlog someone is working through slowly. It is a backlog nobody is working, because nothing in the process raises it.
What moves, once it is moving
Every week the same directories are read again, and each finding lands in one of three states. These are the measures monitoring produces. We have run one sweep and have no subscribers, so each is named and empty rather than filled with something plausible.
| Measure | What it counts | Value |
|---|---|---|
| Open | Still in the published file | |
| New this week | A federal file moved and now contradicts you | |
| Resolved this week | Gone, and gone on the following read too | |
| Resolution rate | Share of what we raised that you cleared | |
| Median days to resolve | Raised to confirmed gone | |
| Oldest open | The one that has been there longest | |
| Recurrence | Cleared, then back again |
A dashboard of plausible numbers is easy to build and worth nothing. The first real value in any of these rows will be a customer's own. How these feed the Index