An OIG notice of intent is not an active exclusion

Model the notice and the exclusion as different records

The direct answer is to preserve process status without relabeling a notice as a current exclusion. A Notice of Intent record should identify the person or entity, identifiers, issuing authority, legal basis, notice date, delivery and receipt, response window, case owner, materials submitted, pending questions, confidentiality and access controls, and next action. It should not automatically populate the field used to represent an active LEIE exclusion.

The exclusion record should retain the authoritative source, query or file version, exact matching inputs, returned identifiers, exclusion type and authority, effective date, stated period, waiver or reinstatement evidence where applicable, verification time, reviewer, and downstream decisions. Link related notice, decision, appeal, and reinstatement events while keeping their states distinct. That structure allows a team to act on a pending process according to policy without misrepresenting the final authority status.

Separate case handling from operational screening

OIG says it considers material supplied by a Notice of Intent recipient before making its decision. Case-management access therefore can require tighter controls than routine screening. Retain the source and purpose for allegations, convictions, licensing actions, correspondence, submissions, deadlines, counsel review, and authorized disposition. Do not expose a pending notice as a public or broad workforce label merely because the credentialing system can display it.

Operational screening should continue to use maintained current-exclusion evidence and a documented matching process. A name-only candidate, no-result search, stale downloaded file, source outage, or pending notice is not a confirmed current exclusion or a clean result. Preserve date of birth or other permitted identifiers, name variants, entity identifiers, state and profession context, candidate matches, resolution evidence, reviewer, and unresolved status. Route ambiguity instead of forcing it into included or clear.

Map each status to its own authorized response

The authority page says the primary effect of exclusion is that federal health care programs will not pay for items or services furnished, ordered, or prescribed by an excluded individual or entity. That consequence belongs to established exclusion status and its effective period; it should not be imported wholesale into the notice or investigation phase. Organizations still need policy and legal review for interim risk controls, due process, workforce actions, scheduling, credentialing, contracting, billing, repayment, disclosure, and notification.

Record the evidence, policy version, decision authority, action, affected role and locations, effective time, communication, appeal or correction path, and later reversal for each response. Keep employment, medical-staff appointment, privilege, payer enrollment, roster inclusion, network participation, claim editing, and payment decisions separate. The same exclusion evidence can be relevant to several workflows without giving one system or reviewer authority over all of them.

Test a notice that never becomes an exclusion

Use a controlled scenario with a same-name LEIE candidate, an individual who receives a Notice of Intent, timely submits material, is not ultimately excluded, and later appears in an unrelated state action. Add a source outage and a downloaded LEIE file that becomes stale during review. Confirm that the notice triggers the organization's authorized interim workflow, never masquerades as an active federal exclusion, the final disposition is preserved, each source remains distinct, and downstream systems receive corrections with acknowledgements.

HHS-OIG's official page supports the attributed LEIE, mandatory and permissive authority, exclusion effect, notice, decision, and appeal-process statements. It does not establish the identity or status of a particular person or entity, a match, pending case, final exclusion, effective period, appeal, reinstatement, employment action, credentialing decision, claim, payment, compliance conclusion, or outcome. OIG and other authorities, medical-staff, credentialing, human-resources, compliance, billing, privacy, security, legal, and clinical owners retain their responsibilities.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Credentialing Current will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.