Risk Adjustment

List risk adjustment jobs

Lists paginated risk adjustment jobs for the organization selected by the bearer API key, with optional status and patient filters.

GETPublic reference baselineRead-onlyRisk AdjustmentoperationId: listRiskAdjustmentJobshttps://dev-api.quickintell.com/api/v1/risk-adjustment/jobs

Public reference baselineRead-onlyPrior auth and clinical

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.

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

Read-only

Reads tenant-scoped data only unless the endpoint description explicitly states an external lookup.

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 prior auth and clinical contract generated for GET /api/v1/risk-adjustment/jobs. External use still depends on route classification, release evidence, and endpoint-specific side-effect approval.

What this does now

Documents the generated GET /api/v1/risk-adjustment/jobs contract as a read-only baseline endpoint.

What this does not do

Does not prove external GA readiness, SDK readiness, live production execution, or complete module behavior. Read behavior still needs release evidence before broad external publication.

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	Read request; no mutation idempotency contract needed.	Use ordinary safe-read retry behavior with rate-limit backoff.
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.

Related platform rules

Workflow Guide Route Status Tenant Context Errors Rate Limits PHI and Security Publication Readiness

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.

Risk Adjustment public API.

Risk Adjustment APIs expose organization-scoped job workflow controls for patient-document risk adjustment processing and human review of Hierarchical Condition Category (HCC) code results. HCC outputs contribute to Risk Adjustment Factor (RAF) score fields, but the bearer API key selects the organization; public callers should not send an `organizationId` selector in these requests. All referenced jobs, patients, files, appointments, and HCC code review targets must belong to the authenticated organization. The public surface is job-oriented and asynchronous. Create, bulk-create, and reprocess endpoints validate local QuickRCM references and either return validation output or queue local work; the OpenAPI descriptions state that public callers do not directly invoke optical character recognition (OCR) or artificial intelligence (AI) processing. Read endpoints return sanitized job summaries, HCC result summaries, and a limited patient-summary object. They do not expose raw document chunks, raw evidence text, clinical note text, transcripts, raw electronic health record (EHR) payloads, raw payer payloads, signed storage URLs, review notes, protected health information (PHI) beyond the minimum documented identifiers, or raw electronic data interchange (EDI) payloads. These endpoints do not submit diagnoses to the Centers for Medicare & Medicaid Services (CMS), send Risk Adjustment Processing System (RAPS) files, send Encounter Data Processing System (EDPS) files, adjudicate claims, update a payer portal, write back to an EHR, or certify final RAF/HCC accuracy. Use `reviewRiskAdjustmentHccCode` only to record a human decision for one HCC code. Treat `finalizedRafScore` and review fields as downstream workflow inputs only when the job state actually includes them and required review has completed. Diagnosis code fields use International Classification of Diseases, 10th Revision (ICD-10) code values where the response schema names them.

What this endpoint does

Use case

Use this endpoint to monitor queued, processing, completed, failed, cancelled, or partially failed risk adjustment jobs or to populate a tenant-scoped worklist.

Before calling

Authenticate with a public API key that has `risk-adjustment:read` or `risk-adjustment:write`. Choose pagination before polling; `page` is one-based and `pageSize` is capped at 100. Use `patientId` only when it is a QuickRCM patient identifier from the authenticated organization.

Request and response behavior

Request guidance

Send query parameters only. `page` defaults to 1 and accepts 1 through 10000. `pageSize` defaults to 25 and accepts 1 through 100. `status` must be one of the documented risk adjustment job status enum values. Do not send `organizationId`; tenant context comes from the bearer API key.

`status` filters by processing lifecycle values such as `PENDING`, `TIER1_PROCESSING`, `COMPLETED`, `FAILED`, `CANCELLED`, and `PARTIAL_FAILURE`.
`patientId` is a QuickRCM patient identifier, not a demographics search field.
Use smaller pages for active polling to reduce repeated exposure of patient-linked job metadata.

Response semantics

HTTP 200 returns `data.jobs`, `total`, `page`, `pageSize`, `totalPages`, and `meta.organizationId`. Each job summary includes local identifiers, lifecycle status, progress/counter fields, RAF score fields, cost fields, review booleans, and lifecycle timestamps. The list response does not include HCC code arrays, patient summaries, raw evidence text, or document chunks.

`progress` is bounded from 0 through 100.
`rafScore` and `finalizedRafScore` can be null depending on processing and review state.
`organizationId` appears in resource rows and metadata as response context, not as a public request selector.

Errors and retries

Treat 400 as invalid pagination or filter input, 401/403 as credential or tenant authorization failures, 429 as a backoff signal, and 500 as retryable only with bounded retry logic. 402, 404, and 409 are declared common responses in the generated OpenAPI contract, but this read endpoint should not be described as a normal credit-consuming or duplicate-conflict workflow. Empty result sets should be documented as HTTP 200 with an empty `jobs` array.

400 can indicate out-of-range `page` or `pageSize` or an unsupported status enum.
404 is declared for tenant-scoped resources but should not be used for normal empty result pages.
429 should be retried with scheduled or exponential backoff.

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

This endpoint does not define path parameters.

Query parameters

Name	Location	Required	Type	Description	Validation and safety notes
page	query	No	integer	One-based result page to return. Defaults to 1 and is capped at 10000.	Minimum value: 1. Maximum value: 10000. Default: 1.
pageSize	query	No	integer	Number of jobs per page. Defaults to 25 and is capped at 100.	Minimum value: 1. Maximum value: 100. Default: 25.
status	query	No	PENDING \| INGESTING \| CHUNKING \| TIER1_PROCESSING \| ROUTING \| TIER2_PROCESSING \| AGGREGATING \| COMPLETED \| FAILED \| CANCELLED \| PARTIAL_FAILURE	Optional risk adjustment processing status filter.	Enum values are declared in the Type column.
patientId	query	No	string	Optional QuickRCM patient identifier used to filter jobs within the authenticated organization.	Minimum length: 1. Potential PHI; use synthetic examples and avoid logging raw values.

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.

This endpoint does not define a JSON request body.

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.

No request example is declared.

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

Risk adjustment jobs for the authenticated organization.

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "jobs": [
      {
        "id": "00000000-0000-4000-8000-000000000001",
        "organizationId": "00000000-0000-4000-8000-000000000001",
        "patientId": "00000000-0000-4000-8000-000000000001",
        "fileId": "00000000-0000-4000-8000-000000000001",
        "appointmentId": "00000000-0000-4000-8000-000000000001",
        "status": "PENDING",
        "currentStage": "example-currentstage",
        "progress": 1,
        "totalPages": 1,
        "totalChunks": 1,
        "relevantChunks": 1,
        "tier1AcceptedChunks": 1,
        "tier2EscalatedChunks": 1,
        "discardedChunks": 1,
        "totalConditions": 1,
        "confirmedHccCodes": 1,
        "rafScore": 1.25,
        "totalCostUsd": 1,
        "creditsCost": 1,
        "requiresHumanReview": true,
        "humanReviewCompleted": true,
        "finalizedRafScore": 1.25,
        "startedAt": "2026-06-08T10:15:30Z",
        "completedAt": "2026-06-08T10:15:30Z",
        "createdAt": "2026-06-08T10:15:30Z",
        "updatedAt": "2026-06-08T10:15:30Z"
      }
    ],
    "total": 1,
    "page": 1,
    "pageSize": 1,
    "totalPages": 1
  },
  "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.