Insurance Discovery

Dismiss discovered coverage

Marks a found discovery result as dismissed inside the authenticated organization.

PUTPublic reference baselineLocal writeInsurance DiscoveryoperationId: dismissInsuranceDiscoverySearchhttps://dev-api.quickintell.com/api/v1/insurance-discovery/searches/{searchId}/dismiss

Public reference baselineLocal writeEligibility and discovery

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 eligibility and discovery contract generated for PUT /api/v1/insurance-discovery/searches/{searchId}/dismiss. 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/insurance-discovery/searches/{searchId}/dismiss 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.

Insurance Discovery public API.

Insurance Discovery APIs expose organization-scoped workflows for finding possible hidden coverage for self-pay or uninsured patients, reviewing local discovery search records, starting simulated batch discovery, retrying failed searches in simulated mode, and verifying or dismissing discovered coverage. The bearer API key selects the organization. Public request bodies should not be documented as tenant selectors, and `organizationId` in responses is ownership/context metadata rather than a caller-controlled organization switch. Patient, search, and batch identifiers must resolve inside the authenticated organization. Search inputs can include patient demographics and optional sensitive matching fields. Treat names, dates of birth, addresses, ZIP codes, Social Security number (SSN) last four digits, payer member IDs, discovered group IDs, and match details as Protected Health Information (PHI) or sensitive insurance data where applicable. Examples must stay synthetic, and public docs should discourage logging search terms, raw vendor payloads, Electronic Health Record (EHR) responses, credentials, tokens, storage keys, and payer portal data. The public surface has mixed side-effect profiles. List and get endpoints read local QuickRCM Revenue Cycle Management (RCM) discovery records. `verifyDiscoveredCoverage` performs local database updates and is documented with `SAFE_WRITE_DB_ONLY` metadata. `startInsuranceDiscoveryBatch` and `retryInsuranceDiscoverySearch` require `simulateOnly: true` and return `SIMULATED_ONLY` metadata because those workflows can consume credits and call the simulated discovery vendor. Retry requests do not accept replacement demographics; current retry behavior reuses the failed search's stored first name, last name, date of birth, address, and ZIP code while not resubmitting stored SSN last-four. `runInsuranceDiscoverySearch` has no public `simulateOnly` flag; it can create a local PHI-bearing search record, consume discovery credits, and potentially transmit patient demographics to a discovery vendor, so document it with credit and privacy warnings. Verification should be described as a local QuickRCM coverage/account state update, not payer adjudication, eligibility verification, claim readiness, or EHR insurance write-back. Existing module docs state that direct EHR write-back is not wired from Insurance Discovery. Current public verification evidence supports creating a new local `PatientInsurance` record when discovered member data is available and storing that new identifier on the search; otherwise `patientInsuranceId` remains null. Downstream eligibility re-verification, claim use, payer configuration resolution, and optional EHR synchronization require separate workflows.

What this endpoint does

Use case

Use this when staff review determines that discovered coverage should not be linked or used, such as a likely false positive, stale coverage, or unrelated payer result.

Before calling

Retrieve the search and confirm it belongs to the tenant and is in a found state appropriate for dismissal. Prepare an optional concise `dismissReason` for audit context.

Request and response behavior

Request guidance

Pass non-empty `searchId` in the path. `dismissReason` is optional in the body, but when supplied it is trimmed and must be 1 to 1000 characters. Keep it operational and PHI-minimal; do not paste vendor payloads, EHR responses, credentials, or raw payer data.

`searchId` is the path selector.
`dismissReason` is optional but capped at 1000 characters.
Existing module docs state only `DISC_FOUND` searches can be dismissed in current operations.

Response semantics

HTTP 200 returns the updated local discovery search with dismissal fields populated. It does not notify a payer, update EHR coverage, reverse a claim, or adjudicate patient financial responsibility.

`status` should reflect dismissed local workflow state after success.
`dismissedAt` records the local dismissal timestamp.
`foundCoverage` may remain present for audit context, so treat the response as sensitive.

Errors and retries

Treat 404 as missing or wrong-tenant search context. If a timeout occurs, re-read the search before retrying because dismissal is a state transition.

400 can indicate an invalid body or invalid workflow transition.
404 can indicate the search is unavailable in the API key organization.
Do not retry state transitions blindly after client timeouts.

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
searchId	path	Yes	string	Non-empty Insurance Discovery search identifier in the path. It must belong to the API key organization.	Minimum length: 1. Sensitive credential or storage-adjacent value; use placeholders only.

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
dismissReason	body	No	string	Optional operator-facing reason for dismissing discovered coverage. Trimmed, 1 to 1000 characters when supplied, sanitized, and free of raw vendor payloads.	Minimum length: 1. Maximum length: 1000.

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.

{
  "dismissReason": "example-dismissreason"
}

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

Dismissed discovery search.

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "id": "00000000-0000-4000-8000-000000000001",
    "organizationId": "00000000-0000-4000-8000-000000000001",
    "patientId": "00000000-0000-4000-8000-000000000001",
    "batchId": "00000000-0000-4000-8000-000000000001",
    "status": "DISC_PENDING",
    "source": "DISC_SRC_EXPERIAN",
    "trigger": "DISC_TRIG_REGISTRATION",
    "foundCoverage": {
      "payerName": "Example dismiss_insurance_discovery_search",
      "memberId": "W123456789",
      "groupId": "00000000-0000-4000-8000-000000000001",
      "planType": "example-plantype",
      "coverageStart": "2026-06-08T10:15:30Z",
      "coverageEnd": "2026-06-08T10:15:30Z",
      "matchScore": "example-matchscore"
    },
    "eligibilityCheckId": "00000000-0000-4000-8000-000000000001",
    "patientInsuranceId": "00000000-0000-4000-8000-000000000001",
    "verifiedAt": "2026-06-08T10:15:30Z",
    "dismissedAt": "2026-06-08T10:15:30Z",
    "dismissReason": "example-dismissreason",
    "searchStartedAt": "2026-06-08T10:15:30Z",
    "searchCompletedAt": "2026-06-08T10:15:30Z",
    "createdAt": "2026-06-08T10:15:30Z",
    "updatedAt": "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.