Denial Management

Reroute denial case

Moves one organization-owned denial case to another organization-owned Denial Management queue, updates queue counters when the queue changes, and records a local reroute activity.

PUTNeeds publication reviewLocal writeDenial ManagementoperationId: rerouteDenialCasehttps://dev-api.quickintell.com/api/v1/denial-management/cases/{denialCaseId}/route

Needs publication reviewLocal writeClaims and denials

Route status

Needs publication review

The endpoint contract is visible, but QuickRCM has not approved it yet for normal production API use.

Publication status

Needs publication review

Requires product, security/compliance, tenancy, side-effect, or module-owner approval before production public API use. 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 claims and denials contract generated for PUT /api/v1/denial-management/cases/{denialCaseId}/route. External use still depends on route classification, release evidence, and endpoint-specific side-effect approval.

What this does now

Shows the generated OpenAPI shape for PUT /api/v1/denial-management/cases/{denialCaseId}/route, but keeps the route out of ordinary production API positioning until review is complete.

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

Do not publish this endpoint as an ordinary developer API until its unresolved decisions are closed.

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

This endpoint needs explicit product, security/compliance, tenancy, or side-effect approval before publication.
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	Needs publication review 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.

Denial Management public API.

Denial Management APIs expose organization-scoped denial case read models, local denial workflow writes, remittance association, draft appeal creation, denial queue routing configuration, explicit case rerouting, and safe document-extraction validation. The bearer API key selects the organization. Public requests should not send `organizationId` as a tenant selector. Read endpoints accept Denial Management read or write scope; mutation endpoints require Denial Management write scope. Referenced denial cases, queues, queue rules, remittances, draft appeals, users, and optional case links must resolve inside the authenticated organization. These endpoints operate on QuickRCM local workflow state. They do not submit appeals to payers, run OCR or LLM extraction, upload files, parse ERA payloads, post payments, adjudicate claims, call clearinghouses, or guarantee denial recovery. Use synthetic examples and keep notes, rule metadata, letter HTML, filenames, and search/filter values free of real PHI, raw EDI, payer portal credentials, tokens, S3 keys, transcripts, and vendor payloads. Iteration 2 adds complete queue-rule action and condition field semantics, common response-field glossary coverage, and PHI-safe synthetic request/response examples for all 10 Denial Management operations.

What this endpoint does

Use case

Use this for manual reassignment, supervisor triage, escalation to a specialized queue, or an integration-driven queue move after a routing decision has already been made.

Before calling

Authenticate with `denial-management:write`. Resolve the denial case and destination queue from the same organization, and prepare an optional sanitized reason.

Request and response behavior

Request guidance

`queueId` is required and must reference a Denial Management queue in the authenticated organization. `reason` is optional and capped at 2000 characters. This endpoint does not evaluate routing rules; the caller supplies the destination queue.

Use queue IDs from listDenialQueueRules.
Keep `reason` concise and do not include raw payer payloads, credentials, or unnecessary PHI.
No owner assignment or status transition is declared in this endpoint.

Response semantics

A 200 response returns the denialCaseId, oldQueueId, newQueueId, and `meta.organizationId`. It confirms a local queue assignment change and activity record, not a payer workflow action.

`oldQueueId` may be null when the case did not have a queue.
Queue counters are adjusted only when the destination differs from the current queue.
The returned identifiers are local workflow state.

Errors and retries

A 404 can mean either the denial case or queue cannot be resolved inside the authenticated organization. After a timeout, re-read the case and queue counts before retrying to avoid confusing duplicate activity records.

404 can refer to either the case or destination queue.
400 can indicate missing queueId or an overlong reason.
Retry only after checking current case queue state.

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
denialCaseId	path	Yes	string	QuickRCM DenialCase 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
queueId	body	Yes	string	Required destination Denial Management queue identifier. It must belong to the authenticated organization.	Minimum length: 1.
reason	body	No	string	Optional sanitized local reroute note, capped at 2000 characters.	Maximum length: 2000.

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.

{
  "queueId": "00000000-0000-4000-8000-000000000001",
  "reason": "example-reason"
}

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

Denial case rerouted

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "denialCaseId": "00000000-0000-4000-8000-000000000001",
    "oldQueueId": "00000000-0000-4000-8000-000000000001",
    "newQueueId": "00000000-0000-4000-8000-000000000001"
  },
  "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