Looking for a Verisys Alternative for OIG Exclusion Monitoring?

Fonteum vs Verisys

Federal exclusion data with field-level provenance

Ingest → provenance → deliver

Open federal data, priced for throughput — not for access

Enterprise exclusion-monitoring platforms are typically sold on per-seat or per-entity terms — frequently five-figure annual contracts — with the underlying federal lists held behind the subscription. Fonteum inverts the model: the OIG LEIE source records are federal public works under 17 U.S.C. § 105, so the /sanctions surface and the downloadable dataset are free, and the recurring fee maps only to the production layer on top of the open data.

Full tier detail — including FHIR R4 API scope, bulk-export throughput, and the methodology-versioning commitment — lives at /pricing.

Common questions

How does Fonteum monitor OIG LEIE exclusions?

Fonteum ingests the OIG HHS LEIE (List of Excluded Individuals and Entities) monthly CSV directly from oig.hhs.gov/exclusions/, on the same cadence the OIG publishes it. The current dataset contains 68,055+excluded individuals and entities. Every record carries the federal source citation written into the provenance layer — oig.hhs.gov LEIE · download date · Fonteum methodology version — along with the exclusion type, the statutory authority for the exclusion (such as 42 U.S.C. § 1320a-7(a) mandatory exclusions), and the effective date. The aggregate surface is public at /sanctions and the underlying dataset is freely downloadable; custom compliance exports — for example, exclusions cross-referenced to a specific provider network or scoped by specialty — are available via the pilot tier from $2,500/mo. Because the ingest mirrors the OIG's own monthly schedule, the screening record stays aligned with the federal source health plans are required to check against.

Does Fonteum replace a credentialing workflow platform like Verisys?

No — and it is important to be precise about the boundary. Verisys and comparable platforms provide automated credentialing workflow management: task queues, re-credentialing schedules, CAQH integration, primary-source license checks, and continuous monitoring orchestration. Fonteum provides the underlying federal data layer those workflows depend on, with field-level provenance: OIG LEIE exclusion flags (68,055+ records, monthly refresh), CMS NPPES NPI and taxonomy (6.8M+active providers), and CMS PECOS Medicare enrollment status — cross-referenced in one source-provenanced graph. Fonteum is the data tier, not the workflow tier. The right way to think about it: a credentialing team can drive its existing workflow platform with Fonteum's federally sourced, citable data via the FHIR R4 API, replacing or supplementing a vendor's proprietary exclusion list with the primary OIG file plus an auditable citation chain. Fonteum does not run the re-credentialing calendar; it makes the data feeding that calendar traceable to the federal record.

Can I download the OIG LEIE exclusion data directly from Fonteum?

Yes. The OIG LEIE dataset is available at /sanctions as a public research surface, and the underlying structured dataset is downloadable as CSV and JSON with no account required — the LEIE is a federal public work under 17 U.S.C. § 105, so Fonteum redistributes the provenance-tagged version openly. Every record traces to the OIG HHS LEIE file with the federal citation, the download date, and the methodology version. For production use cases that need more than the static file — bulk exports with custom cross-references such as NPI-matched exclusion flags scoped by specialty, geography, or an uploaded provider roster, or programmatic monthly delivery — the pilot tier provides scoped datasets and FHIR R4 API access from $2,500/mo. This open posture contrasts with per-seat or per-entity enterprise pricing, where the same federal exclusion list sits behind a five-figure annual contract.

Does Fonteum cross-reference OIG exclusions with NPI records?

Yes. Fonteum's source-provenance graph joins OIG LEIE exclusion records with CMS NPPES NPI data (6.8M+ active providers) and CMS PECOS Medicare enrollment status. The cross-reference is surfaced on provider profiles: an excluded provider shows the LEIE flag alongside their NPPES taxonomy, practice address, and PECOS enrollment indicator — each field carrying its own federal source citation and last-checked date. The join methodology, including how Fonteum handles name-and-identifier matching between the LEIE (which keys on individual and entity identifiers) and NPPES (which keys on NPI), is documented at /data-provenance, with match confidence preserved rather than collapsed. This matters because exclusion screening turns on correct identity resolution: a false match flags a clean provider, a missed match clears an excluded one. By keeping the provenance and match basis visible, Fonteum lets a compliance team see why a given NPI is or is not tied to an exclusion record, instead of trusting an opaque proprietary matcher.

Why does field-level provenance matter for exclusion screening audits?

CMS requires Medicare Advantage organizations and Medicaid managed-care plans to screen providers against the OIG LEIE monthly, and to be able to demonstrate that screening in an audit. The audit question is not merely 'did you check?' but 'against which version of the federal list, on what date, and can you show the record?' A platform that returns a proprietary clean/excluded verdict without surfacing the underlying OIG file, download date, and match basis leaves a gap in that audit trail. Fonteum closes it: every exclusion record carries the oig.hhs.gov LEIE citation, the monthly download date, the exclusion type and statutory authority, and the methodology version, all written to the provider_field_provenance layer. When an auditor asks for the basis of a screening decision, the answer is the federal record itself with its date stamp — not a vendor's derived list. That is the difference between defensible primary-source documentation and a black-box result.

Is Fonteum's data free, and what does the pilot tier add?

The /sanctions OIG LEIE surface and the underlying research dataset are free to access and cite, as are Fonteum's other federal datasets at /research — no account, no API key for the static files. This is possible because the source records are federal public works. The paid pilot tier ($2,500–$5,000/mo) is for teams that need production capabilities on top of the open data: custom export scoping (exclusions matched to your provider roster, or cross-referenced with NPPES taxonomy and PECOS enrollment), FHIR R4 US Core 6.1.0 API access with SMART Backend Services auth for system-to-system integration, HL7 bulk $export for large pulls, methodology-versioning commitments so your pipeline is pinned to a stable schema, and a 30-day no-penalty exit. The pricing model is deliberately inverted from the enterprise norm: the federal data is open, and you pay only for scoping, throughput, and integration support.

How often is the OIG LEIE updated on Fonteum?

The OIG publishes the LEIE as a monthly full database replacement plus monthly supplement files listing the additions and reinstatements since the prior release. Fonteum ingests the full file on the OIG's monthly cadence, so the /sanctions surface and the downloadable dataset track the federal source within that publication window. Each ingest is stamped with its download date in the provenance layer, so a record always carries the date of the federal file it came from — not a vague 'recently updated' label. The current dataset holds 68,055+excluded individuals and entities. Because exclusion-screening obligations under CMS guidance run monthly, aligning the ingest to the OIG's own monthly release keeps the screening basis aligned with the list health plans are required to check against.

How is the OIG LEIE different from SAM.gov exclusions?

The OIG LEIE (List of Excluded Individuals and Entities) and the SAM.gov exclusions list are two distinct federal sources. The OIG LEIE is maintained by the HHS Office of Inspector General and identifies individuals and entities excluded from participation in federal health-care programs under sections 1128 and 1156 of the Social Security Act. SAM.gov's exclusions cover a broader federal procurement and award context across agencies. Fonteum's /sanctions surface is sourced specifically from the OIG LEIE — the list directly relevant to health-care program participation and the one CMS expects Medicare Advantage and Medicaid managed-care plans to screen against monthly. Fonteum is explicit about that scope rather than blending two lists with different statutory bases into one undifferentiated verdict; the source citation on every record states that it is the OIG HHS LEIE, with its download date and methodology version.

Can Fonteum's exclusion data integrate with our credentialing system via API?

Yes. Beyond the free static downloads, the pilot tier exposes the exclusion data through a FHIR R4 US Core 6.1.0 API with SMART Backend Services authentication for system-to-system integration, and an HL7 bulk $export endpoint for large roster pulls. The OIG exclusion signal is carried on the Practitioner resource through meta.tag provenance, so an integrating system receives both the flag and its federal source citation in the same payload. This lets a credentialing or payer-integrity platform pull exclusion status programmatically on a schedule, reconcile it against its own provider roster, and retain the source citation and download date for its audit trail — rather than copying a derived clean-or-excluded verdict with no traceable basis. The same FHIR resources expose NPPES taxonomy and PECOS enrollment, so a single integration can carry identity, enrollment, and exclusion signal together.

How do I cite Fonteum's OIG exclusion data in a compliance report?

Every Fonteum exclusion record is designed to be cited the way a primary federal source is cited. The provenance layer carries the originating dataset (OIG HHS LEIE), the download date of the specific monthly file, the exclusion type and statutory authority, and the Fonteum methodology version under which the record was processed. For a compliance report or audit response, cite the OIG LEIE as the primary source with the download date Fonteum records, and reference the methodology version so the processing step is reproducible. The /data-provenance page documents the full citation format and the join methodology used when an exclusion is cross-referenced to an NPI. Because the chain is explicit end to end, the citation points an auditor back to the federal file itself, not to an opaque intermediate product — which is exactly what a defensible screening record requires.

How does Fonteum's pricing compare to enterprise exclusion-monitoring contracts?

Enterprise exclusion-monitoring and provider-data platforms are typically sold on per-seat or per-entity terms, often as five-figure annual contracts with the underlying federal lists locked behind the subscription. Fonteum inverts that: the OIG LEIE surface at /sanctions and the downloadable dataset are free, because the source records are federal public works under 17 U.S.C. § 105. The paid pilot tier ($2,500–$5,000/mo) covers only the production layer on top of the open data — custom export scoping, FHIR R4 API and HL7 bulk $export throughput, methodology-versioning commitments, and integration support — with a 30-day no-penalty exit. The practical result is that evaluation, citation, and one-off research use cost nothing, and the recurring fee maps to throughput and integration rather than to access to data that is, at its source, public. See /pricing for current tier detail.

Explore the OIG exclusion data.

The /sanctions surface and OIG LEIE research dataset are free. For custom compliance exports, request access.

• /sanctions → OIG LEIE exclusion aggregate surface — 68,055+ excluded providers.
• /sources → OIG LEIE source family documentation — tier, refresh cadence, redistribution posture.
• /data-provenance → How OIG LEIE, NPPES, and PECOS cross-references are provenanced.
• /use-cases/payer-credentialing → Provider credentialing data for health plan compliance teams.