Payer Enrollment

Update payer enrollment application status

Applies a valid local status transition to an active payer enrollment application.

PUTPublic reference baselineExternal or credentialedPayer EnrollmentoperationId: updatePayerEnrollmentApplicationStatushttps://dev-api.quickintell.com/api/v1/payer-enrollment/applications/{applicationId}/status

Public reference baselineExternal or credentialedProvider and payer setup

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 E7 credential, webhook, and vendor trust 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

External or credentialed

May touch credentials, webhooks, SFTP, EHRs, payers, portals, clearinghouses, or other external systems.

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 provider and payer setup contract generated for PUT /api/v1/payer-enrollment/applications/{applicationId}/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/payer-enrollment/applications/{applicationId}/status contract as a external or credentialed 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.
External or credentialed behavior needs vendor trust, credential, webhook, and callback evidence before publication.

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.

Payer Enrollment public API.

Payer Enrollment APIs expose organization-scoped provider enrollment profiles, payer-specific enrollment applications, local enrollment status tracking, follow-up notes, deficiencies, assignment, and safe validation workflows for credentialing sync and bulk import. The bearer API key selects the organization. Public callers should not send `organizationId` as a tenant selector. Read endpoints require payer-enrollment read or write scope; mutation endpoints require payer-enrollment write scope. Referenced provider profiles, payer configurations, credentialing sessions, enrollment rows, deficiencies, applications, and assignees must resolve inside the authenticated organization. Provider identity fields include National Provider Identifier (NPI) values, Council for Affordable Quality Healthcare (CAQH) identifiers, Medicare identifiers, and other sensitive operational enrollment data. This public surface is intentionally conservative. Application, provider-profile, follow-up, deficiency, assignment, enrollment, status, and clone endpoints update local QuickRCM records only. `submitPayerEnrollmentApplication`, `simulateSyncPayerEnrollmentProfileFromCredentialing`, and `bulkImportPayerEnrollments` are validation or dry-run surfaces that return `SIMULATED_ONLY` metadata and do not submit to payer portals, write provider data from credentialing, or import rows. When an application method names Electronic Data Interchange (EDI) or the Provider Enrollment, Chain, and Ownership System (PECOS), it is local workflow metadata unless a future private workflow provides separate evidence. Keep examples synthetic and keep notes free of Protected Health Information (PHI), portal credentials, OAuth tokens, raw EDI, raw payer payloads, S3 keys, and vendor responses. Iteration 3 adds final materialization guidance for the reference pages: list responses are ordered by most recently updated application first, and simulated-only flows should show small synthetic examples that keep tenant selection implicit in the bearer API key.

What this endpoint does

Use case

Use this to move an application through QuickRCM's local enrollment workflow after staff review, payer feedback, or validated automation evidence.

Before calling

Read the current application status and confirm the requested `newStatus` is allowed from that state. Prepare an optional concise `note` for status history.

Request and response behavior

Request guidance

`newStatus` is required and must be one of the application status enum values. The handler enforces these transitions in addition to enum validation: DRAFT -> AUTO_FILLING, READY_FOR_REVIEW, PENDING_DOCUMENTS, WITHDRAWN; AUTO_FILLING -> READY_FOR_REVIEW, DRAFT; READY_FOR_REVIEW -> SUBMITTED, PENDING_DOCUMENTS, DRAFT, WITHDRAWN; PENDING_DOCUMENTS -> READY_FOR_REVIEW, SUBMITTED, WITHDRAWN; SUBMITTED -> ACKNOWLEDGED, IN_REVIEW, DEFICIENCY_RECEIVED, APPROVED, DENIED, WITHDRAWN; ACKNOWLEDGED -> IN_REVIEW, DEFICIENCY_RECEIVED, APPROVED, DENIED; IN_REVIEW -> DEFICIENCY_RECEIVED, APPROVED, DENIED; DEFICIENCY_RECEIVED -> DEFICIENCY_RESOLVED, DENIED, WITHDRAWN; DEFICIENCY_RESOLVED -> IN_REVIEW, APPROVED, DENIED; APPROVED -> EFFECTIVE, WITHDRAWN; EFFECTIVE -> EXPIRED, TERMINATED; EXPIRED -> DRAFT; TERMINATED -> DRAFT. DENIED and WITHDRAWN have no outbound transitions.

Allowed transitions are enforced by current status, not just by enum membership.
DENIED and WITHDRAWN are terminal in the current public handler; EXPIRED and TERMINATED can reopen only to DRAFT.
`note` is optional and capped at 1000 characters.
Use this for local workflow tracking; do not present it as external payer confirmation.

Response semantics

HTTP 200 returns the updated local application summary and `meta.organizationId`. A transition to APPROVED currently sets `effectiveDate` to the server timestamp. The response is local status state, not payer portal proof.

The response returns the updated application summary.
Status-history details are not exposed in the public response.
APPROVED currently also stamps `effectiveDate`.

Errors and retries

Treat 400 as invalid transition or invalid body. Treat 404 as missing, inactive, or wrong-organization application. After timeouts, re-read the application before retrying to avoid applying a stale transition.

400 can include an invalid transition message.
404 means the application was not found in active tenant scope.

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
applicationId	path	Yes	string	QuickRCM payer enrollment application identifier. It must belong to the organization selected by the bearer API key.	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
newStatus	body	Yes	DRAFT \| AUTO_FILLING \| READY_FOR_REVIEW \| PENDING_DOCUMENTS \| SUBMITTED \| ACKNOWLEDGED \| IN_REVIEW \| DEFICIENCY_RECEIVED \| DEFICIENCY_RESOLVED \| APPROVED \| EFFECTIVE \| DENIED \| WITHDRAWN \| EXPIRED \| TERMINATED	Required target local application status. It must be reachable from the current status according to the documented transition graph.	Enum values are declared in the Type column. File, artifact, or raw-payload adjacent; keep examples metadata-only.
note	body	No	string	Optional status-history note. Keep it concise and avoid sensitive 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.

{
  "newStatus": "DRAFT",
  "note": "Example payer_enrollment_application_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

Payer enrollment application status updated.

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "application": {
      "id": "00000000-0000-4000-8000-000000000001",
      "organizationId": "00000000-0000-4000-8000-000000000001",
      "providerId": "00000000-0000-4000-8000-000000000001",
      "provider": {
        "id": "00000000-0000-4000-8000-000000000001",
        "firstName": "John",
        "lastName": "Smith",
        "npi": "1234567893"
      },
      "payerConfigId": "00000000-0000-4000-8000-000000000001",
      "payerConfig": {
        "id": "00000000-0000-4000-8000-000000000001",
        "payerName": "Example payer_enrollment_application_statu",
        "payerId": "87726"
      },
      "applicationType": "INITIAL",
      "applicationMethod": "CAQH",
      "payerApplicationId": "00000000-0000-4000-8000-000000000001",
      "caqhProviderId": "00000000-0000-4000-8000-000000000001",
      "status": "DRAFT",
      "submissionDate": "2026-06-08T10:15:30Z",
      "acknowledgmentDate": "2026-06-08T10:15:30Z",
      "effectiveDate": "2026-06-08T10:15:30Z",
      "expirationDate": "2026-06-08T10:15:30Z",
      "nextFollowUpDate": "2026-06-08T10:15:30Z",
      "followUpCount": 1,
      "estimatedProcessingDays": 1,
      "assignedToId": "00000000-0000-4000-8000-000000000001",
      "formTemplateId": "00000000-0000-4000-8000-000000000001",
      "formTemplate": {
        "id": "00000000-0000-4000-8000-000000000001",
        "formName": "Example payer_enrollment_application_statu",
        "formVersion": "example-formversion"
      },
      "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 parameters.