more providers than the previous vendor
On a nationwide provider directory, we ran the same scrape the client's vendor had been running for months. We returned 79K more providers. The client had no mechanism to detect this. Nothing in the delivery indicated anything was missing.
A healthcare data company was receiving monthly provider data from their vendor for a nationwide directory. The vendor delivered consistently and on schedule. QA consisted of spot-checking a sample of records.
Nothing looked wrong. Nothing in the volume, the format, or the sampled records suggested anything was missing. There was no alert. No failed delivery. Just a gap, running silently every month.
On a state-based health plan directory, the vendor returned 49K providers including out-of-state ones. We returned 52K in-state providers. More relevant data, not just more data.
The 6.5% gap is not specific to one directory. Across similar state-based directories, we consistently return over 5% more in-state providers. The likely cause: differences in scrape traversal depth, handling of pagination, and how each vendor interprets scope from the same URL list.
Spot checks verify what is delivered. They cannot catch what is not there. The only way to find this gap is to run an independent comparison scrape, which is exactly what the Gap Audit does.
79K providers missing from the client's product every month, silently. Their customers were seeing an incomplete provider set. Neither party knew.
Want to know if your vendor is delivering everything the source contains?
Start a Gap Audit →