Contract Management

Create rate simulation

Creates a local what-if rate simulation draft for an organization-owned payer configuration.

POSTNeeds publication reviewExternal or credentialedContract ManagementoperationId: createContractManagementSimulationhttps://dev-api.quickintell.com/api/v1/contract-management/simulations

Needs publication reviewExternal or credentialedRevenue integrity

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 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 revenue integrity contract generated for POST /api/v1/contract-management/simulations. 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 POST /api/v1/contract-management/simulations, 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	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

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.
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	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.

Contract Management public API.

Contract Management APIs expose organization-scoped insurance contract inventory and local revenue-integrity workflow controls for contract list, detail, create, and update operations; what-if rate simulation drafts; fee schedule validation/import; underpayment detection; dispute-letter request recording; assignment; and resolution. The bearer API key selects the organization. Public callers should not send `organizationId` as a tenant selector. Every referenced payer configuration, facility, contract, claim, underpayment case, assignee, fee schedule, rate schedule, simulation, activity, and audit row must resolve inside the authenticated organization. These endpoints manage QuickRCM local state and audit evidence. They do not call payer systems, prove payer acceptance, upload or return contract files, generate or transmit live dispute letters, post cash, adjudicate claims, update Electronic Health Record (EHR) billing resources, or guarantee external recovery. Use synthetic examples and keep names, notes, rate-change context, dispute text, and import data free of real protected health information (PHI), credentials, tokens, raw Electronic Data Interchange (EDI), payer portal payloads, S3 keys, and vendor responses.

What this endpoint does

Use case

Use this endpoint when an integration wants to stage proposed Current Procedural Terminology (CPT) rate changes for later Contract Management analysis or review.

Before calling

Authenticate with `contract-management:write`. Resolve the request `payerId` from the tenant's QuickRCM payer configuration records and prepare 1 to 1000 proposed rate-change rows.

Request and response behavior

Request guidance

`name`, `payerId`, and `rateChanges` are required. Each rate change requires `cptCode`, non-negative `currentRate`, and non-negative `proposedRate`. `cptCode` is capped at 20 characters. Despite the request field name, `payerId` is resolved by the current handler as a QuickRCM payer configuration id, not a clearinghouse payer id.

The public field is named `payerId`, but the handler resolves it through organization-owned payer configuration lookup.
`rateChanges` accepts 1 through 1000 rows.
Keep simulation names and code labels operational and free of patient identifiers.

Response semantics

A 201 response returns a local simulation record with status `CS_DRAFT`. `payerId` in the response is the stored QuickRCM payer configuration id and `payerName` is copied from that payer configuration. The public handler creates the draft and audit log only; it does not run the simulation, calculate final impact, contact a payer, or change contract rates. The implementation can return a not-found error for a missing payer configuration, but the current OpenAPI response map for this operation does not formally declare 404.

`status` is `CS_DRAFT` on creation.
`totalImpact` and `annualClaimVolume` can be null until a later simulation process populates them.
No payer system is called.

Errors and retries

Fix invalid rate-change arrays before retrying. Treat formally documented errors as 400, 401, 403, 429, and 500. If an implementation-observed not-found error occurs for the payer selector, resolve the tenant-local payer configuration id before retrying. After a timeout, inspect recent simulations before creating another draft.

400 can indicate missing name, invalid payerId shape, empty rateChanges, too many rows, negative rates, or excessive cptCode length.
Implementation-observed 404 can indicate the payer configuration is unavailable in the authenticated organization; update the OpenAPI response map before presenting that as a formal response code.
Do not retry blindly after timeouts because duplicate drafts are possible.

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

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
name	body	Yes	string	Human-readable local simulation name, capped at 255 characters.	Minimum length: 1. Maximum length: 255.
payerId	body	Yes	string	Endpoint-specific payer selector. In the current handler this is resolved as an organization-owned QuickRCM payer configuration identifier, not the nested `payer.payerId` external payer value from contract responses.	Minimum length: 1.
rateChanges	body	Yes	object[]	Array of proposed Current Procedural Terminology (CPT) rate changes. The public schema accepts 1 through 1000 entries.	OpenAPI does not declare additional validation metadata.
rateChanges[].cptCode	body	Yes	string	Current Procedural Terminology (CPT) or CPT-like procedure code for the proposed rate change, capped at 20 characters.	Minimum length: 1. Maximum length: 20.
rateChanges[].currentRate	body	Yes	number	Current non-negative rate value supplied by the caller for comparison.	Minimum value: 0.
rateChanges[].proposedRate	body	Yes	number	Proposed non-negative rate value supplied by the caller for simulation.	Minimum value: 0.

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.

{
  "name": "Example contract_management_simulation",
  "payerId": "87726",
  "rateChanges": [
    {
      "cptCode": "example-cptcode",
      "currentRate": 1.25,
      "proposedRate": 1.25
    }
  ]
}

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.

201

Rate simulation created.

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "id": "00000000-0000-4000-8000-000000000001",
    "organizationId": "00000000-0000-4000-8000-000000000001",
    "name": "Example contract_management_simulation",
    "payerId": "87726",
    "payerName": "Example contract_management_simulation",
    "status": "CS_DRAFT",
    "totalImpact": "example-totalimpact",
    "annualClaimVolume": 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 parameters.