Skip to main content
PATCH
Update a patient

Authorizations

Authorization
string
header
required

Marketplace API key

Headers

X-Organization-Id
string
required

Target clinic organization ID

Path Parameters

id
string
required

Patient ID

Body

application/json
firstName
string
Example:

"Jane"

middleName
string
Example:

"Marie"

lastName
string
Example:

"Doe"

dateOfBirth
string

YYYY-MM-DD

Example:

"1984-02-11"

sex
string
Example:

"FEMALE"

email
string
Example:

"jane@example.com"

phones
object[]

Contact points to write. Each is merged into the chart BY TYPE, so a submitted cell number never touches a stored home or work number. A phone-typed value must contain at least 7 digits or the request is rejected. NOTE: phone values are NOT covered by conflictPolicy — a submitted number replaces the stored number OF THE SAME TYPE. We hold one untyped 'preferred' number per chart, so a typed submission cannot be compared against it without rejecting the ordinary case of a patient confirming their mobile. An EMAIL_ADDRESS entry here writes the chart's single email field and IS covered by conflictPolicy.

address
object
conflictPolicy
enum<string>

What to do when a submitted value differs from the stored one. reject (default) fails the whole update and reports the conflicting fields; overwrite replaces them; skip keeps the stored value and applies the rest. Blank submitted values NEVER clear a populated EHR value under any policy — this is a public booking form writing to a clinical record, so silent overwrite is not the default. Applies to the named demographic fields and to an email sent via phones[]; see phones for why phone VALUES are exempt.

Available options:
reject,
overwrite,
skip
Example:

"reject"

Response

Success

code
string
required

Response code

Example:

"success"

data
object
required