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?

OIG publishes the LEIE monthly. Fonteum's production serving table held 68,055 rows from the May 8, 2026 source release when checked on July 12, so it may lag the current OIG file. Results identify OIG as the source and expose available record dates; users must confirm a match at oig.hhs.gov before acting.

Does Fonteum replace a credentialing workflow platform like Verisys?

No. Verisys and comparable products manage credentialing workflows. Fonteum exposes source-specific OIG LEIE, NPPES, and PECOS records. It links rows by NPI only when both sources publish that identifier; most LEIE rows require separate name-based screening. Fonteum does not turn an NPI record into a licensure or credentialing decision.

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. The downloadable dataset identifies the OIG HHS LEIE file and exposes available download-date and methodology metadata. 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 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, but only where the source supports the link. Fonteum makes an exact NPI cross-reference when an OIG LEIE or PECOS row publishes the same NPI as NPPES. Most LEIE rows lack NPI; name-and-identifier screening is handled separately with its match basis and limitations visible. An absent NPI match is not a clearance.

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. A Fonteum exclusion response exposes the OIG citation, download date, exclusion type, statutory authority, methodology, and match basis where populated; unavailable fields remain null. When an auditor asks for the basis of a screening decision, confirm the named federal record and its date stamp rather than relying on a vendor's derived verdict.

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 monthly. Fonteum's loaded serving table was checked at 68,055rows with a May 8, 2026 source date on July 12, so this surface may lag OIG's latest release. Treat the listed source date as the screening basis and confirm at OIG before acting.

What should a compliance team do when Fonteum's loaded LEIE date is older than OIG's current release?

Treat Fonteum's displayed source date as the boundary of the loaded evidence, not as a promise that the table matches the publisher's newest file. Record the date used for the screen, keep the returned OIG identifiers and match basis when present, and check the current LEIE at oig.hhs.gov before a consequential decision. If the current federal file differs, retain both the dated Fonteum response and the authoritative OIG result. A missing date, NPI, or provenance field should be recorded as unavailable, not filled from another provider or inferred from publisher cadence.

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; available records identify the OIG HHS LEIE and expose download-date and methodology metadata where populated.

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

Yes. Beyond the free static downloads, the pilot tier exposes 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. Supported Practitioner responses can carry an OIG exclusion signal and available federal-source metadata through meta.tag; fields may be absent. A credentialing or payer-integrity platform can pull exclusion status programmatically, reconcile it against its provider roster, and retain the source and date fields the response supplies. Other supported FHIR responses expose available NPPES taxonomy and PECOS enrollment fields.

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

For a compliance report or audit response, cite the OIG LEIE as the primary source. Use the download-date, exclusion-type, statutory-authority, and methodology fields returned with the Fonteum record when present; if a field is absent, mark it unavailable and confirm current status at OIG. The /data-provenance page documents the citation format and the join methodology used when an exclusion has an exact NPI cross-reference. This keeps the citation anchored to the federal file rather than an opaque intermediate verdict.

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.