Prevention

Acknowledge prevention alert

Acknowledges an organization-owned prevention alert or dismisses it when `dismiss` is true.

PUTPublic reference baselineLocal writePreventionoperationId: acknowledgePreventionAlerthttps://dev-api.quickintell.com/api/v1/prevention/alerts/{alertId}

Public reference baselineLocal writeAgent Builder and Prevention

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 agent builder and prevention contract generated for PUT /api/v1/prevention/alerts/{alertId}. 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/prevention/alerts/{alertId} 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	Not indicated by OpenAPI	No generic polling contract is published from this page.
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.

Prevention public API.

Prevention APIs expose organization-scoped public endpoints for claim pre-submission scrub queueing, denial-risk prediction queueing, prevention alert review, finding resolution, controlled auto-fix preview/application/revert, prevention rule lifecycle management, prediction feedback, provider education workflow, and learned payer-rule promotion. The bearer API key selects the organization. Public callers should not send an `organizationId` selector. List and detail reads accept Prevention read or write scope; every mutation requires Prevention write scope. Referenced claims, claim lines, findings, predictions, rules, alerts, payer profiles, providers, education records, and auto-fix runs must belong to the authenticated organization. organizationId`; generated schema leaves `data` open-ended for several workflow endpoints, so endpoint examples should be treated as illustrative current handler behavior while the stable top-level envelope remains consistent. Alert list/detail and alert acknowledge endpoints return explicit alert objects. Public scrub, batch scrub, prediction, and education generation endpoints are safe local workflows: `validateOnly` returns validation-only output, `dryRun` simulates without queueing, and `queueOnly` creates or reuses local work items where the handler supports queueing. These endpoints do not return payer acceptances, raw electronic data interchange (EDI), raw payer payloads, live large language model (LLM) output, or external dispatch evidence. Use only synthetic examples in public documentation. Alert and education text can contain operational context, so examples and guidance should avoid real protected health information (PHI), credentials, tokens, raw EDI, transcripts, S3 keys, payer portal credentials, vendor payloads, or patient demographic details. Safe-workflow request bodies may accept unknown passthrough properties at validation time, but those properties are not part of the public API contract. Do not use extra properties to send protected health information (PHI), raw claim payloads, raw electronic data interchange (EDI), vendor payloads, credentials, tokens, or payer portal details.

What this endpoint does

Use case

Use this endpoint for the lightweight alert update path when a reviewer has seen the alert, recorded a short action, or wants to dismiss it from the active alert queue.

Before calling

Authenticate with Prevention write scope and load the alert from the same organization. Decide whether this is an acknowledgment or dismissal because `dismiss: true` changes the update path.

Request and response behavior

Request guidance

Send `actionTaken` for an acknowledgment. Send `dismiss: true` with optional `dismissReason` for dismissal. The source request schema accepts optional `resolutionCode`; current handler persists it on the dismiss path and defaults dismissal resolution to `DISMISSED` when omitted.

`actionTaken` and `dismissReason` are capped at 1000 characters.
`dismiss` defaults to false.
`resolutionCode` is optional and capped at 100 characters.
Keep action text free of unnecessary protected health information (PHI), raw payer payloads, credentials, and electronic data interchange (EDI).

Response semantics

HTTP 200 returns the updated `data.alert` object. The update is local QuickRCM workflow state; it does not alter the claim or send payer communications.

Acknowledgment sets acted-upon state in local alert workflow.
Dismissal sets dismissed state, stores the optional dismissal reason, sets `dismissedAt`, and stores `resolutionCode` or default `DISMISSED`.

Errors and retries

Fix 400 validation errors before retrying. Treat 404 as missing or wrong-tenant alert. If a retry follows a network timeout, re-read the alert first because the previous update may have completed.

403 means the API key lacks Prevention write scope.
404 means the alert was not found in the authenticated organization.

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
alertId	path	Yes	string	QuickRCM prevention alert identifier in the path.	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
actionTaken	body	No	string	Short staff or system action note for an acknowledgment. Avoid patient details and secrets.	Minimum length: 1. Maximum length: 1000. Sensitive credential or storage-adjacent value; use placeholders only.
dismiss	body	No	boolean	When true, the handler dismisses the alert instead of recording an acknowledgment.	Default: false. File, artifact, or raw-payload adjacent; keep examples metadata-only.
dismissReason	body	No	string	Optional dismissal rationale, capped at 1000 characters.	Minimum length: 1. Maximum length: 1000.
resolutionCode	body	No	string	Optional local resolution code accepted by the source schema. Current handler stores it when `dismiss` is true; use the action endpoint when completing an alert with an `ACTION_TAKEN` style code.	Minimum length: 1. Maximum length: 100.

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.

{
  "actionTaken": "example-actiontaken",
  "dismiss": false,
  "dismissReason": "example-dismissreason",
  "resolutionCode": "example-resolutioncode"
}

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

Prevention alert updated

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "alert": {
      "id": "00000000-0000-4000-8000-000000000001",
      "organizationId": "00000000-0000-4000-8000-000000000001",
      "claimId": "00000000-0000-4000-8000-000000000001",
      "claimLineId": "00000000-0000-4000-8000-000000000001",
      "userId": "00000000-0000-4000-8000-000000000001",
      "alertType": "example-alerttype",
      "triggerSource": "example-triggersource",
      "severity": "LOW",
      "status": "ACTIVE",
      "title": "Example acknowledge_prevention_alert",
      "message": "Request failed",
      "suggestedAction": "example-suggestedaction",
      "estimatedRiskAmount": "example-estimatedriskamount",
      "historicalDenialRate": "example-historicaldenialrate",
      "wasActedUpon": true,
      "actionTaken": "example-actiontaken",
      "wasDismissed": true,
      "dismissReason": "example-dismissreason",
      "acknowledgedAt": "2026-06-08T10:15:30Z",
      "dismissedAt": "2026-06-08T10:15:30Z",
      "resolvedAt": "2026-06-08T10:15:30Z",
      "ownerUserId": "00000000-0000-4000-8000-000000000001",
      "dueAt": "2026-06-08T10:15:30Z",
      "resolutionCode": "example-resolutioncode",
      "createdAt": "2026-06-08T10:15:30Z",
      "claim": {
        "id": "00000000-0000-4000-8000-000000000001",
        "status": "active",
        "claimControlNumber": "example-claimcontrolnumber",
        "payer": {
          "id": "00000000-0000-4000-8000-000000000001",
          "payerId": "87726",
          "name": "Example acknowledge_prevention_alert"
        }
      }
    }
  }
}

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