U.S. General Services Administration
SAM.gov Exclusions
SAM.gov carries the government-wide record of parties excluded from federal procurement and non-procurement programs. It is broader than the healthcare-specific LEIE, it is maintained by many agencies rather than one, and it is the list a federal contract most often means when it says “check exclusions”.
- How NPISignal reads it
- Official GSA API, queried live
- API version
- v4
- On this deployment
- Not configured
SAM screening is not configured here
Two lists, two scopes
How SAM differs from the OIG LEIE
| HHS-OIG LEIE | SAM.gov | |
|---|---|---|
| Maintained by | HHS Office of Inspector General | GSA, populated by many federal agencies |
| Scope | Federal healthcare programs specifically | Federal procurement and non-procurement, government-wide |
| Access | A downloadable file, republished monthly | An API and a web search, updated continuously |
| Carries an NPI | Sometimes — on a minority of records | No |
| Carries a date of birth | For most individuals | No |
| Typical healthcare relevance | Directly — this is the healthcare exclusion list | Vendors, contractors, and parties excluded reciprocally |
The practical consequence: a SAM-only match can rarely be confirmed on public data alone. Without a date of birth or an NPI on the SAM side, the strongest a name match usually gets is a possible one, and NPISignal labels it that way rather than manufacturing confidence it does not have.
What NPISignal reads, and what it refuses
Fields collected
Collected
- · Classification (individual, firm, vessel, special entity)
- · Exclusion name, or first and last name
- · Exclusion type and program
- · Excluding agency
- · UEI and CAGE code
- · Public address, city, state, ZIP, country
- · Activation and termination dates
- · Public comments and reference information
Deliberately not collected
- · Social Security numbers
- · Taxpayer identification numbers
- · Employer identification numbers
- · Dates of birth
There is no column for any of these anywhere in NPISignal. Where the API returns a field whose name resembles one, it is stripped before the response is stored for debugging — a future SAM release that starts returning one cannot introduce sensitive-data retention by accident.
Related