Appeals

Update appeal document status

Reviews, approves, or rejects an appeal supporting document.

PUTPublic reference baselineFile or artifactAppealsoperationId: updateAppealDocumentStatushttps://dev-api.quickintell.com/api/v1/appeals/documents/{documentId}/status

Public reference baselineFile or artifactClaims and denials

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 and E4 file and artifact governance 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

File or artifact

Touches documents, reports, transcripts, PDFs, EDI, or generated artifacts. Metadata is safer than raw content.

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/appeals/documents/{documentId}/status. 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/appeals/documents/{documentId}/status contract as a file or artifact 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	Potential file or artifact	Documents, PDFs, reports, transcripts, EDI, OCR, or generated artifacts need E4 classification before public examples.
Ownership and storage keys	Evidence required	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.
File and artifact examples must stay metadata-only until scanning, retention, ownership, and URL policy are approved.

Related platform rules

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

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.

Appeals public API.

Appeals APIs manage QuickRCM denial appeal records, supporting document workflows, peer-to-peer reviews, deadlines, reminders, analytics, and compliance tracking. All endpoints are scoped to the organization selected by the bearer API key; callers do not provide a public organization selector. Use these endpoints after a denial case, claim, supporting document, reminder, peer-to-peer review, compliance event, or compliance rule already exists in QuickRCM. Read endpoints accept `appeals:read` or `appeals:write`; write endpoints require `appeals:write`. The public API exposes local workflow state and sanitized metadata. It intentionally avoids returning raw payer payloads, PHI-heavy activity metadata, S3 object keys, raw EDI, transcripts, or vendor credentials. Electronic portal appeal submission is validate-only through the public API and returns a simulated validation response rather than transmitting a payer payload.

What this endpoint does

Use case

Use this after a document is uploaded and a reviewer needs to advance it through review state.

Before calling

Read the current document status and choose an allowed review status transition.

Request and response behavior

Request guidance

Pass `documentId` in the path and send required `status` plus optional `note`. Allowed request statuses are `REVIEWED`, `APPROVED`, and `REJECTED_REDO`.

Use `REJECTED_REDO` when the file must be corrected and uploaded again.
Keep review notes concise and avoid unnecessary PHI.

Response semantics

The response returns the updated local document. Request `note` is stored as review context; returned document metadata may include `reviewedAt` and `reviewNotes` when applicable.

Returned document metadata includes reviewedAt/reviewNotes when applicable.
Only document workflow state changes here.

Errors and retries

Treat invalid transitions as 400s. Re-read document state after 409 conflicts.

400 can mean an invalid transition.
409 means concurrent document status update conflict.

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
documentId	path	Yes	string	Tenant-scoped QuickRCM appeal supporting document identifier selected from the path.	Minimum length: 1. Tenant context is selected by the API key; do not treat this as a public tenant selector.

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
status	body	Yes	REVIEWED \| APPROVED \| REJECTED_REDO	Required document review status: REVIEWED, APPROVED, or REJECTED_REDO.	Enum values are declared in the Type column. File, artifact, or raw-payload adjacent; keep examples metadata-only.
note	body	No	string	Optional review note for the document status update. Keep concise and avoid unnecessary PHI.	Minimum length: 1. Maximum length: 2000. File, artifact, or raw-payload adjacent; keep examples metadata-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.

{
  "status": "REVIEWED",
  "note": "Example appeal_document_statu 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

Appeal document status updated

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "document": {
      "id": "00000000-0000-4000-8000-000000000001",
      "appealId": "00000000-0000-4000-8000-000000000001",
      "documentType": "APPEAL_LETTER",
      "documentName": "Example appeal_document_statu",
      "status": "REQUIRED",
      "fileId": "00000000-0000-4000-8000-000000000001",
      "dueDate": "2026-06-08T10:15:30Z",
      "uploadedAt": "2026-06-08T10:15:30Z",
      "reviewedAt": "2026-06-08T10:15:30Z",
      "reviewNotes": "Example appeal_document_statu note",
      "isRequired": true,
      "createdAt": "2026-06-08T10:15:30Z",
      "updatedAt": "2026-06-08T10:15:30Z",
      "file": {
        "id": "00000000-0000-4000-8000-000000000001",
        "filename": "Example appeal_document_statu",
        "mimeType": "example-mimetype",
        "sizeBytes": 1,
        "createdAt": "2026-06-08T10:15:30Z",
        "updatedAt": "2026-06-08T10:15:30Z"
      }
    }
  }
}

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