Revenue Integrity

Resolve a charge reconciliation item

Marks one organization-scoped charge reconciliation item as resolved with a resolution action and optional notes.

PUTNeeds publication reviewPayment or creditRevenue IntegrityoperationId: resolveRevenueIntegrityChargeReconciliationItemhttps://dev-api.quickintell.com/api/v1/revenue-integrity/charge-reconciliations/{sessionId}/items/{itemId}/resolve

Needs publication reviewPayment or creditRevenue 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 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

Payment or credit

May affect payments, credits, refunds, voids, or financial posting. Requires explicit product approval before publication.

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 PUT /api/v1/revenue-integrity/charge-reconciliations/{sessionId}/items/{itemId}/resolve. 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/revenue-integrity/charge-reconciliations/{sessionId}/items/{itemId}/resolve, 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.

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.

Revenue Integrity public API.

Revenue Integrity APIs expose organization-scoped controls for dashboard metrics, underpayment recovery case lists, charge reconciliation, charge lag reporting, charge capture audits, operating room reconciliation, coding validation, contract rate validation, implant recovery tracking, underpayment appeal tracking, recovery recording, contract setup, and manual underpayment checks. The bearer API key selects the organization. Public callers should not send an `organizationId` selector in these requests. Read endpoints accept `revenue-integrity:read` or `revenue-integrity:write`; write endpoints require `revenue-integrity:write`. Referenced claims, patients, facilities, billing encounters, payer configurations, contracts, charge reconciliation sessions, charge reconciliation items, and underpayment cases must belong to the authenticated organization. This public surface is conservative. Some endpoints create or update local Revenue Integrity records. Other endpoints return `202 Accepted` for queued, validated, or dry-run local workflows. Those responses do not mean QuickRCM made a direct payer call, contacted a payer portal, submitted an appeal externally, changed an Electronic Health Record (EHR), posted cash, adjudicated a claim, or received a payer decision. Use synthetic examples and keep notes, descriptions, invoice identifiers, source record identifiers, and appeal references free of unnecessary Protected Health Information (PHI), raw Electronic Data Interchange (EDI), raw Electronic Remittance Advice (ERA), payer payloads, transcripts, credentials, tokens, S3 keys, and payer portal secrets. Queued workflow controls are consistent across the public Revenue Integrity endpoints that expose them: `validateOnly` validates ownership and request shape without creating a queued workflow; `dryRun` simulates the workflow when `validateOnly` is false; otherwise the API records a queued local workflow request. `queueOnly: false` by itself is not a request for direct payer, clearinghouse, or EHR execution.

What this endpoint does

Use case

Use this endpoint after staff or an integration has reviewed a missing charge, extra charge, variance, or pending reconciliation item and decided the local resolution outcome.

Before calling

Authenticate with write scope. Use a `sessionId` and `itemId` obtained from QuickRCM for the same tenant. Confirm the item is still in a resolvable local status.

Request and response behavior

Request guidance

The body requires `resolutionAction`: CHARGE_ADDED, CHARGE_CORRECTED, CHARGE_REMOVED, or NO_ACTION. `resolutionNotes` is optional and capped at 2000 characters.

`sessionId` and `itemId` are both path selectors.
Only locally resolvable discrepancy or pending states should be resolved through this endpoint.
Keep `resolutionNotes` concise and free of raw clinical transcripts or payer payloads.

Response semantics

HTTP 200 returns the item id, status `RESOLVED`, mode `updated`, and `meta.organizationId`. This records local resolution metadata; it does not add charges to claims, submit corrected claims, or mutate Electronic Health Record charge records.

The response is local workflow state only.
`resolvedById` is derived from the public API actor internally and is not supplied by the caller.

Errors and retries

404 means the item/session pair was missing or outside the organization. 400 can mean the item status is not resolvable. Re-read item state after a timeout before retrying to avoid overwriting another user's resolution.

400 can indicate the item has already moved beyond a resolvable status.
404 can intentionally hide wrong-tenant items.

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
sessionId	path	Yes	string	Charge reconciliation session identifier from the path.	Minimum length: 1. Financial value; preserve decimal precision and avoid real account details.
itemId	path	Yes	string	Charge reconciliation item identifier from the path.	Minimum length: 1. Financial value; preserve decimal precision and avoid real account details.

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
resolutionAction	body	Yes	CHARGE_ADDED \| CHARGE_CORRECTED \| CHARGE_REMOVED \| NO_ACTION	Required local resolution action: CHARGE_ADDED, CHARGE_CORRECTED, CHARGE_REMOVED, or NO_ACTION.	Enum values are declared in the Type column. Financial value; preserve decimal precision and avoid real account details.
resolutionNotes	body	No	string	Optional local resolution note capped at 2000 characters. Avoid PHI and raw payer or EHR payloads.	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.

{
  "resolutionAction": "CHARGE_ADDED",
  "resolutionNotes": "Example revenue_integrity_charge_reconciliation_item 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

Charge reconciliation item resolved.

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "id": "00000000-0000-4000-8000-000000000001",
    "status": "active",
    "mode": "created"
  },
  "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.