Billing

Update billing encounter code

Updates an existing code on an editable Billing encounter and marks it human-reviewed.

PUTPublic reference baselineLocal writeBillingoperationId: updateBillingEncounterCodehttps://dev-api.quickintell.com/api/v1/billing/encounters/{encounterId}/codes/{codedEntryId}

Public reference baselineLocal writeBilling and claims

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

Local write

May mutate QuickRCM records. It does not prove live payer, EHR, clearinghouse, payment, or communication execution.

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 billing and claims contract generated for PUT /api/v1/billing/encounters/{encounterId}/codes/{codedEntryId}. 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/billing/encounters/{encounterId}/codes/{codedEntryId} contract as a local write 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	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

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

Billing public API.

Billing public API endpoints expose organization-scoped hospital billing encounters, coding review actions, physician query responses, batch imports, and Charge Description Master (CDM) maintenance. The surface is centered on `BillingEncounter` records and related review artifacts: code entries, POA indicators, DRG/E/M summaries, processing logs, physician queries, and CDM rate records. Tenant scope is resolved from the bearer API key. Read endpoints accept `billing:read` or `billing:write`; create, update, queue, finalize, code-edit, physician-response, and CDM mutation endpoints require `billing:write`. Callers should pass QuickRCM identifiers returned by prior reads, imports, or adjacent setup workflows; do not send organization IDs as an authority signal, raw EDI, payer portal credentials, transcripts, S3 keys, signed URLs, full vendor payloads, or unnecessary clinical narrative. The current Billing OpenAPI contract has detailed schemas for reads and queued workflows, but several mutation endpoints still use the generic mutation schema in generated OpenAPI while their handlers return concrete data. Client-facing docs should distinguish generated-schema guarantees from handler-observed runtime response fields, avoid promising unrelated Prisma columns as stable contract, and still recommend a follow-up read after queued workflows or state transitions when downstream processing is asynchronous.

What this endpoint does

Use case

Use this during coder review to correct code value, description, modifiers, principal flag, sequence, revenue code, units, diagnosis pointers, POA indicator, or human notes.

Before calling

Confirm the coded entry belongs to the requested encounter and tenant, and that the parent encounter is not FINALIZED or SUBMITTED.

Request and response behavior

Request guidance

Send only fields that should change. The schema does not require at least one business field, but every call marks the entry as HUMAN-assigned/human-reviewed in the handler.

The lookup scopes by `codedEntryId`, `encounterId`, and parent `billingEncounter.organizationId`.
`sequenceNumber` and `poaIndicator` can be set to null where the schema allows.
`humanNotes` is capped at 1000 characters.

Response semantics

HTTP 200 returns `success: true` with the serialized updated coded-entry record returned by Prisma. The generated OpenAPI schema is generic, so docs should not say the body is empty.

Runtime response contains the updated entry fields as serialized by the handler.
Because the generic OpenAPI mutation schema does not enumerate those fields, getBillingEncounter is the safest normalized read model.

Errors and retries

400 can mean attempting to modify a FINALIZED or SUBMITTED encounter. 404 means the code is missing or not tenant-scoped through the parent encounter. After timeout, read getBillingEncounter before retrying.

400 can mean attempting to modify a FINALIZED or SUBMITTED encounter. 404 means the code is missing or not tenant-scoped through the parent encounter. After timeout, read getBillingEncounter before retrying.

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
encounterId	path	Yes	string	Encounter identifier supplied as source context for a procedure, charge audit, or operating room log entry. Resolve organization ownership where QuickRCM identifiers are used.	Minimum length: 1. Financial value; preserve decimal precision and avoid real account details.
codedEntryId	path	Yes	string	Path identifier for the code entry being updated.	Minimum length: 1.

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
code	body	No	string	Procedure, revenue, Diagnosis-Related Group (DRG), or other local code on a contract rate schedule row.	Minimum length: 1. Maximum length: 32. Potential PHI; use synthetic examples and avoid logging raw values.
description	body	No	string	Human-readable description of the queue, workflow, or record. Avoid secrets and unnecessary PHI.	Minimum length: 1. Maximum length: 1000. Sensitive credential or storage-adjacent value; use placeholders only.
modifiers	body	No	string[]	Array of procedure modifiers on a claim line.	OpenAPI does not declare additional validation metadata.
isPrincipal	body	No	boolean	OpenAPI description is missing; publication gap.	OpenAPI does not declare additional validation metadata.
sequenceNumber	body	No	integer	OpenAPI description is missing; publication gap.	OpenAPI does not declare additional validation metadata.
revenueCode	body	No	string	Nullable institutional revenue code on a claim line.	Maximum length: 10.
units	body	No	integer	OpenAPI description is missing; publication gap.	OpenAPI does not declare additional validation metadata.
diagnosisPointers	body	No	integer[]	Optional diagnosis pointer list, maximum 12 positive integers.	Potential PHI; use synthetic examples and avoid logging raw values.
poaIndicator	body	No	Y \| N \| U \| W \| 1	OpenAPI description is missing; publication gap.	Enum values are declared in the Type column.
humanNotes	body	No	string	Optional reviewer note, maximum 1000 characters.	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.

{
  "code": "ERROR",
  "description": "Example billing_encounter_code note",
  "modifiers": [
    "example-modifiers"
  ],
  "isPrincipal": true,
  "sequenceNumber": 1,
  "revenueCode": "example-revenuecode",
  "units": 1,
  "diagnosisPointers": [
    1
  ]
}

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

Billing public API operation completed.

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {}
}

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.