OIG Exclusion

Resolve OIG exclusion match

Records a human false-positive or confirmed-excluded decision for an organization-owned OIG exclusion check in a resolvable status.

PUTPublic reference baselineLocal writeOIG ExclusionoperationId: resolveOigExclusionMatchhttps://dev-api.quickintell.com/api/v1/oig-exclusion/checks/{checkId}/resolution

Public reference baselineLocal writeProvider and payer setup

Route status

Public reference baseline

Generated endpoint contract may be shown with caveats, but external publication still needs route registry and release evidence.

Publication status

Baseline reference only

Requires E6 route registry and E9 release evidence before external publication. Also requires E2 side-effect policy before production recipes, SDK inclusion, or try-out access.

Authentication

Bearer API key declared

OpenAPI declares bearer API-key security for this operation.

Tenant context

API-key organization

API-key organization context is authoritative; request organizationId is not a public tenant selector.

Side-effect summary

Local write

May mutate QuickRCM records. It does not prove live payer, EHR, clearinghouse, payment, or communication execution.

Source artifact

docs/openapi/openapi.json

OpenAPI 3.1.0; API 1.0.0.

When to use this endpoint

Use this page as an internal baseline for the provider and payer setup contract generated for PUT /api/v1/oig-exclusion/checks/{checkId}/resolution. External use still depends on route classification, release evidence, and endpoint-specific side-effect approval.

What this does now

Documents the generated PUT /api/v1/oig-exclusion/checks/{checkId}/resolution contract as a local write baseline endpoint.

What this does not do

Does not prove external GA readiness, SDK readiness, live production execution, or complete module behavior. Mutating behavior still needs side-effect and retry evidence.

Not public from this page

Live external side effects, file contents, credentials, webhooks, SDK promises, and production recipes are still gated.

Headers and tenancy

Current headers and tenant authority. Target headers stay labeled as future until OpenAPI and release evidence declare them.

Header	Required	Current status	Notes
Authorization	Yes	Current	Bearer <QUICKRCM_API_KEY>. OpenAPI security: bearerAuth.
Idempotency-Key	No	Target/future	Do not claim universal header support until E3 and OpenAPI metadata exist.
X-Request-Id	No	Target/future	Use for support correlation only after approved; not declared as a standard OpenAPI header today.

Required scopes

Unclassified until E6 route metadata exists; do not infer scopes from route names.

Wrong-org behavior

Tenant-safe 404, empty list, or 403 is endpoint-specific and remains an evidence gap until E1 is closed.

Actor and audit

No public actor, audit, or correlation contract is published from OpenAPI alone.

Idempotency and retries

Retry behavior is documented conservatively because universal idempotency headers are not declared.

Topic	Status	Guidance
Current idempotency	No idempotency mechanism is declared.	Do not retry blindly. Check resource, status, batch, or job state before repeating the request.
Universal header	Not declared	Do not document universal Idempotency-Key support until OpenAPI and E3 evidence declare it.
Conflict behavior	Unresolved	Same-key changed-payload, in-flight retry, fingerprint scope, and TTL behavior remain endpoint-specific evidence gaps.

Async jobs and polling

Queued work is accepted work, not proof of completed workflow execution.

Topic	Status	Guidance
Immediate response	No 202 response declared	OpenAPI does not declare HTTP 202 for this operation.
Polling and terminal states	Endpoint-specific	Use only operation-specific status endpoints visible in OpenAPI; generic job behavior, cancellation, retries, and retention are unresolved.
Later side effects	Not proven	Do not infer background execution beyond the documented response.

Files and artifacts

File-like routes need content-class, ownership, scanning, retention, and URL policy evidence before public recipes.

Topic	Status	Guidance
Content class	No file/artifact class inferred	OpenAPI text does not indicate file or artifact handling for this endpoint.
Ownership and storage keys	Not applicable unless a file field is present	Tenant ownership must be proven before retrieval or upload docs. Never expose storage keys as public identifiers.
URLs, scanning, and retention	Unresolved unless endpoint-specific evidence exists	Short-lived URLs, MIME limits, checksums, scanner status, retention, expiration, and legal hold behavior are not implied by OpenAPI examples.

Publication warnings

Universal Idempotency-Key header support is not declared; retry only after checking endpoint-specific state.

Related platform rules

Workflow Guide Route Status Tenant Context Errors Rate Limits PHI and Security Publication Readiness Side-Effect Modes Idempotency

Evidence

Evidence	Status	Caveat
OpenAPI artifact	docs/openapi/openapi.json; OpenAPI 3.1.0; API 1.0.0.	Generated baseline contract only.
Route registry	Public reference baseline from documentation classification overlay.	E6 route registry evidence is still required before external publication.
Example validation	Generated examples are internal baseline aids.	No external publication claim; examples must pass no-PHI/no-secret/no-raw-payload/no-storage-key checks.
Last reviewed	Implementation run 20260619T-docs-impl; source boardroom packet 20260619T064820Z.	Refresh this evidence for release workspaces.
Release evidence	E9 required.	No SDK readiness, production readiness, or expanded external docs claim from this endpoint page.

OIG Exclusion public API.

OIG Exclusion APIs expose organization-scoped exclusion-check records for Office of Inspector General (OIG) screening against List of Excluded Individuals/Entities (LEIE) and System for Award Management (SAM.gov) summary data. The bearer API key selects the authenticated organization; public request bodies should not be documented as tenant selectors. The current public surface is intentionally conservative. organizationId`. The create endpoint accepts provider checks with a legal display name, `checkType: PROVIDER`, a 10-digit NPI, and a two-uppercase-letter state code; successful calls can return a recent existing check because the runtime deduplicates matching checks within the recent-check window. The bulk endpoint is dry-run only and returns `SIMULATED_ONLY` counts plus latest-run metadata without calling LEIE or SAM sources. The resolution endpoint records a human false-positive or confirmed-excluded decision for resolvable local checks, and a confirmed-excluded decision can attempt internal organization-scoped follow-up. Do not describe public responses as raw federal-source exports, external EHR write-back, payer notification, or guaranteed claim holds.

What this endpoint does

Use case

Use this endpoint after an authorized human reviewer has compared the local match summary against approved compliance evidence and decided whether the match is false positive or confirmed excluded.

Before calling

Authenticate with `oig-exclusion:write` scope. Retrieve the check first, confirm it belongs to the authenticated organization, and confirm its status is `EXC_MATCH_FOUND` or `EXC_REVIEW_NEEDED`. Keep review notes concise and free of raw source payloads, credentials, DOB, SSN, or unnecessary sensitive identifiers.

Request and response behavior

Request guidance

`checkId` is a required path parameter. `resolution` is required and must be `FALSE_POSITIVE` or `CONFIRMED_EXCLUDED`. `notes` is optional, must be non-empty when supplied, and is capped at 4000 characters.

`resolution` must be `FALSE_POSITIVE` or `CONFIRMED_EXCLUDED`.
Only checks currently in `EXC_MATCH_FOUND` or `EXC_REVIEW_NEEDED` status are resolvable.
`notes` should summarize the decision rationale without raw LEIE/SAM.gov rows, secrets, DOB, SSN, or unrelated PHI.
Use this endpoint only after human review; it is not a source-list search endpoint.

Response semantics

A 200 response returns the resolved sanitized check in `data.check` plus `meta.organizationId`. False-positive resolution changes the local status to `EXC_FALSE_POSITIVE`; confirmed-excluded resolution changes it to `EXC_CONFIRMED_EXCLUDED` and can attempt internal organization-scoped follow-up such as audit logging, admin notification, credentialing flags, or claim-hold attempts where those models support it. The public response itself is not proof that external EHR write-back, payer notification, or claim holds completed.

The response returns the local check record after resolution.
`reviewedBy` and `reviewedAt` may be populated by the server when the resolution is recorded.
`status` changes to `EXC_FALSE_POSITIVE` for false-positive resolution or `EXC_CONFIRMED_EXCLUDED` for confirmed-excluded resolution.
`matchSummary`, `leie`, and `sam` remain structured summaries on the returned check; the public response does not expose raw source-list evidence or reviewer notes.
Confirmed-excluded resolution can trigger internal follow-up attempts, but the response should not be documented as proof of completed claims, credentialing, payer, or external EHR side effects.
The public check serializer returns `reviewedBy` and `reviewedAt`, but not raw reviewer notes.

Errors and retries

Treat 404 as missing or wrong-organization `checkId`. Treat 400 as invalid request body or a non-resolvable current status; only `EXC_MATCH_FOUND` and `EXC_REVIEW_NEEDED` checks can be resolved. After a timeout, fetch the check before submitting another resolution to avoid duplicate or conflicting review notes.

400 can indicate an unsupported resolution value, invalid notes length, or a check status other than `EXC_MATCH_FOUND` or `EXC_REVIEW_NEEDED`.
404 means the check is not available in the authenticated organization.
403 means the caller lacks authorization for the organization context or write scope.

Template boundary before examples

The route class, authentication state, tenancy rule, side-effect mode, idempotency status, async behavior, file policy, warnings, links, and evidence above are part of the endpoint contract. Treat generated examples below as internal baseline aids until release evidence closes.

Path parameters

Name	Location	Required	Type	Description	Validation and safety notes
checkId	path	Yes	string	Identifier of the local OIG exclusion check to resolve.	Minimum length: 1.

Query parameters

This endpoint does not define query parameters.

OpenAPI-declared header parameters

Standard platform header guidance appears in the governance panel. This table only lists operation-specific headers declared in OpenAPI.

This endpoint does not define operation-specific header parameters.

Request body

JSON fields from the generated OpenAPI schema with pilot enrichment applied where available. Nested object fields are shown with dotted paths.

Name	Location	Required	Type	Description	Validation and safety notes
resolution	body	Yes	FALSE_POSITIVE \| CONFIRMED_EXCLUDED	Human review outcome: `FALSE_POSITIVE` or `CONFIRMED_EXCLUDED`.	Enum values are declared in the Type column.
notes	body	No	string	Optional reviewer notes, capped at 4000 characters. Keep notes sanitized and avoid raw source data, DOB, SSN, secrets, and unrelated PHI.	Minimum length: 1. Maximum length: 4000. Sensitive credential or storage-adjacent value; use placeholders only.

Generated request example

Generated examples are baseline contract aids only. They are not external publication evidence and must not include real PHI, credentials, raw vendor payloads, raw EDI, transcripts, storage keys, or signed URLs.

{
  "resolution": "FALSE_POSITIVE",
  "notes": "Example oig_exclusion_match note"
}

Successful responses

Generated response examples show the baseline OpenAPI contract. Tenant identifier echo, PHI redaction, pagination, money, date/time, and enum semantics remain endpoint-specific publication checks.

200

Resolved OIG exclusion check for the authenticated organization.

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "check": {
      "id": "00000000-0000-4000-8000-000000000001",
      "organizationId": "00000000-0000-4000-8000-000000000001",
      "checkType": "PROVIDER",
      "entityName": "Example oig_exclusion_match",
      "npi": "1234567893",
      "userId": "00000000-0000-4000-8000-000000000001",
      "providerId": "00000000-0000-4000-8000-000000000001",
      "status": "EXC_CLEAR",
      "matchSummary": {
        "leieMatch": true,
        "samMatch": true,
        "matchScore": 1.25
      },
      "leie": {
        "exclusionType": "example-exclusiontype",
        "exclusionDate": "2026-06-08T10:15:30Z",
        "reinstatementDate": "2026-06-08T10:15:30Z",
        "state": "example-state",
        "specialty": "example-specialty"
      },
      "sam": {
        "exclusionType": "example-exclusiontype",
        "exclusionDate": "2026-06-08T10:15:30Z"
      },
      "reviewedBy": "example-reviewedby",
      "reviewedAt": "2026-06-08T10:15:30Z",
      "checkedAt": "2026-06-08T10:15:30Z"
    }
  },
  "meta": {
    "organizationId": "00000000-0000-4000-8000-000000000001"
  }
}

Error responses

Errors must remain sanitized. Do not include raw payer, EHR, SFTP, SMTP, Stripe, LLM/OCR, browser automation, file, transcript, EDI, worker, or vendor payloads.

400

Invalid request.