Skip to main content
PATCH
Update an encounter

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Idempotency-Key
string

Optional. A unique value you choose for this request, such as a UUID. When sent, a retry with the same key returns the first answer instead of applying the change twice. See Retries and idempotency.

Minimum string length: 1

Path Parameters

clinic_id
string<uuid>
required
encounter_id
string<uuid>
required

Body

application/json

A change to a visit's details. It is accepted only while the draft the same key opened is still untouched: once a clinician has edited or signed the note the answer is 409 note_not_editable, and another party's visit is a 404. Only these four fields can change; no note text can be sent and nothing is signed, locked or finalized. The Idempotency-Key header is optional. Send JSON; a FHIR Encounter body is not accepted.

class
enum<string>
Available options:
ambulatory,
emergency,
inpatient,
virtual,
home_health
started_at
string<date-time>
ended_at
string<date-time>

Must not be before started_at.

reason
string
Required string length: 1 - 500

Response

OK.

data
object
required

A visit as documented in the clinic: a clinical note seen as a visit — the exposed-field allow-list, field by field. The id is the note's id, so the same visit reads under Notes. It carries the visit's status, dates, administrative reason and clinician only: no note text, title, diagnosis, plan, service, signature or billing is ever exposed here (clinical text is read through Notes). Every encounter is a consultation; triage, ward and appointment records are not encounters in this API. A visit opened through the API is a draft with review_status: pending until a clinician has reviewed it.

idempotent_replay
boolean

Present and true when this Idempotency-Key was already used and the original answer is returned.