Evidence before inference
ProviderFront methodology
How ProviderFront ingests, validates, versions, protects, compares, and explains public healthcare provider records.
Last updated July 20, 2026
Source acquisition and provenance
ProviderFront uses current Version 2 CMS NPPES full and incremental downloadable files for bulk history and the supported NPPES Read API version 2.1 for targeted freshness checks. Every accepted record retains the source batch, version, filename, checksum, import time, and validation result.
Downloads are resumable and checksum-verified. A source batch is quarantined if its format changes unexpectedly, required columns disappear, checksums fail, rejection rates exceed limits, or volume anomalies require review.
Temporal model
Type 1 and Type 2 records, legal and other names, reported taxonomies, practice locations, mailing addresses, and activation dates remain semantically separate. Complete snapshots receive a deterministic hash. ProviderFront compares a newly validated snapshot with its prior completed version and records field-level differences.
Public changes are never built from an incomplete download. The previously validated data stays in place until a new source batch passes validation in full.
Signal definitions
| Label | Rule | What it does not mean |
|---|---|---|
| Newly enumerated | Official enumeration date falls inside the documented 45-day window at observation. | Not proof a practice opened. |
| First observed | First complete ProviderFront batch containing the NPI. | Not the official enumeration date. |
| Recently updated | The official NPPES last-update date changed. | Not necessarily a new provider or location. |
| Practice location added | A normalized practice address was absent from the prior valid snapshot. | Not confirmation the location is operating. |
| Possible opening / move / expansion | At least two documented factors align, such as a recent Type 2 enumeration and a newly observed practice location. | Inference, not confirmation. |
Privacy before rendering
Field-level policy runs before public templates or payloads are created. Mailing addresses, endpoint details, personal contact data, license numbers, and EIN data are not public lead fields. Practice locations can be reduced to city and state or suppressed. Active suppression decisions persist across later imports.
Expiration and corrections
“New” labels expire automatically; deactivation, reactivation, and later source changes can retire a prior signal. Corrections and suppression reports enter a reviewed queue. A claim can add verified provider-submitted information only after identity verification and without overwriting source provenance.