From published directory to verified resolution.
Eight stages, none of which need anything from your systems. We read what you already publish, the way a regulator or a member would read it.
01 INGEST
Read what you publish
Directory files are discovered and read from the channel they are already published in. Nothing is requested from you.
02 NORMALISE
Resolve records to NPIs
Rows become records keyed on NPI, across individual clinicians, facilities and groups alike.
03 COMPARE
Join against federal sources
Every record is checked against NPPES and the HHS-OIG exclusion list.
04 CONTROL
Apply the gates
The federal event must pre-date your published file, and be more than 90 days old. Anything else is dropped.
05 EVIDENCE
Keep the trail
Source, federal date, the file we read and its last-modified date, and which gates were cleared.
06 MONITOR
Read it again
Later sweeps sort findings into new, persistent and resolved, and keep each one's history.
07 DELIVER
Into your workflow
Scheduled file, API or webhook, whichever your provider-data process already uses.
08 RESOLVE
Confirm the correction
When the published record changes, we see it in the file and close the finding against evidence.
Every rule you are held to, and what covers it
Nine obligations across four federal instruments. Solid means a check runs at national scale today. Outline means it is built and not yet running nationally, and we would rather label that than let a table imply otherwise.
| What the rule requires | Where it comes from | What covers it |
|---|---|---|
| Nobody barred from billing is listed in-network | OIG LEIE · 42 CFR 438.214 | Federal check |
| No cancelled NPI registration is still listed | NPPES | Federal check |
| The directory is actually published, and current | CMS-9115-F · 45 CFR 156.230 | Publication watch |
| They practise where you say they practise | CMS deficiency · weight 3 | Research agent |
| The phone number reaches them | CMS deficiency · weight 3 | Voice agent |
| The panel is open if you say it is open | CCIIO field | Email and voice |
| Address and suite match the registry | CMS deficiency · weight 2, 1 | Federal check |
| Every change is verified within 90 days | REAL Act · PY2028 | Monitoring |
| An officer can sign for all of it | CMS-4208-F2 · 1 Sep 2026 | The evidence file |
The first two are asserted outright, because cancelling a registration and adding someone to an exclusion list are federal acts rather than opinions. The rest are corroborated leads until verification settles them. What a finding is, and what it is not
The weekly loop, and who decides
The stages above run as one weekly pass over every published directory. Agents operate the pass: they read the files, retry what failed, load the results, and draft the analysis of what moved. What they cannot do is change the method or publish.
- Every run is checked before anything reads it. A run must pass its validation checks; one that fails is held, and a held run is invisible to this site and the API.
- The review is written down. Each week's movement is attributed to its causes and reviewed against the stored evidence, and the review itself is recorded alongside the run.
- Publication is a human decision. No run reaches this site or the API until a person signs it off. The publish step runs only when a person runs it, deliberately.
Open methods. Continuous machine operation. Human-governed publication. The method and the API serve exactly the published runs.
When federal data is not enough
Four of those nine cannot be settled from any registry. Whether someone still practises at an address, whether the number reaches them, whether the panel is open: these need evidence gathered rather than looked up.
That is what the verification ladder does, and it runs upstream of everything above rather than being a separate thing to buy. How autonomous verification works