Skip to main content
POST
Merge this chart into another

Authorizations

Authorization
string
header
required

Marketplace API key

Headers

idempotency-key
string
required

Required. A retry with the same key and body returns the same merge; never merges twice.

X-Organization-Id
string
required

Target clinic organization ID

Path Parameters

patientId
string
required

Body

application/json
intoPatientId
string
required

The surviving chart. Same organization and same EHR instance as the path patient.

Example:

"pat_c56103bcd39c46d39f3138dd2b5e05f6"

acknowledgeWarnings
boolean
default:false

Merge even though the EHR warned about the pair (e.g. differing first names), after staff confirmed both charts are the same person. Without it such a merge answers 409 merge_needs_confirmation. Blocks on either chart (balances, open bills) still refuse.

Response

Accepted — queued for background processing

code
string
required

Response code

Example:

"success"

data
object
required