CSV screening
Batch NPI and OIG screening
Upload up to 500 rows. Results separate exact identifier checks from possible name or business matches, so reviewers can scan risk without losing source context.
Provider exclusion screening
Identifier-first checks before name review
Last verified: 2026-06-04. date_retrieved: 2026-06-04. The CSV workflow separates exact identifier checks from possible name or business matches so reviewers can keep official source context attached to each row.
| Signal | How it is used | Review note |
|---|---|---|
| NPI | Checks exact provider or organization identifiers against NPI Registry context. | NPI data identifies the record; it does not verify licensure or credentialing. |
| OIG LEIE | Marks exact NPI matches separately from possible name, business, state, or ZIP matches. | Possible matches require manual verification against OIG before action. |
| CLIA number | Looks up imported CMS clinical laboratory rows when a clia_number column is present. | Use CMS QCOR or the CMS registry for current certificate context. |
Input quality checklist
Fields to collect before provider exclusion screening
Last verified: 2026-06-04. date_retrieved: 2026-06-04. Stronger identifiers reduce false positives in healthcare sanctions screening, but official-source verification is still required before employment, payment, enrollment, or contracting action.
| Input quality | CSV fields | How reviewers should use it | Official source anchor |
|---|---|---|---|
| Exact public identifier | npi, clia_number | Use exact NPI and CLIA values first so a row is anchored to a public registry record before name matching. NPI numbers identify providers; they do not validate licensure or credentialing. | |
| OIG verification identifier | not stored in CSV | Use SourceCheckHealth to triage possible LEIE matches, then verify specific individuals or entities in OIG's online search with SSN or EIN when the official workflow requires it. | OIG LEIE instructions |
| Name and location context | first_name, last_name, organization_name, city, state, zip | Treat name, business, and location matches as review context. They can explain why a possible match appeared, but they are not enough for a final provider exclusion decision. | OIG search tips |
| Source freshness | reviewed_at, source_note | Record when the row was reviewed and compare it with the current source status. OIG refreshes LEIE information monthly, NPPES publishes monthly and weekly files, and CLIA status should be checked in CMS registry tools when certificate currency matters. |
Supported CSV columns
Keep the file simple: one row per entity, with identifiers first when available.
| Column | Use |
|---|---|
| npi | Exact NPI Registry lookup and exact OIG NPI match |
| first_name, last_name | Person match context for OIG matching |
| organization_name, business_name | Organization/business match context |
| city, state, zip | Location fields used for match confidence |
| clia_number | Exact lookup against imported CMS CLIA lab records, with QCOR linked for verification |
FAQ
Practical notes
How many rows can I screen in the MVP?
The MVP accepts up to 500 rows per upload to keep processing predictable.
What does healthcare sanctions screening cover here?
The CSV workflow checks NPI identity context, OIG LEIE exact and possible matches, and CLIA lab rows when a CLIA number is supplied. Reviewers should verify relevant records against the official source before acting.
Can provider exclusion screening make a final hiring or credentialing decision?
No. It is a screening aid for public-source review. It does not provide legal clearance, complete credentialing, licensure verification, or a final hiring decision.
Which CSV columns improve match confidence?
Exact identifiers such as npi and clia_number are strongest. Names, business names, city, state, and ZIP help reviewers interpret possible matches but should not be treated as final by themselves.
What identifiers should I collect before provider exclusion screening?
Collect exact public identifiers first, especially NPI and CLIA number when available, then names and location fields for possible-match context. OIG identity verification may still require the official online search workflow, including SSN or EIN verification for specific matches.