Add a note to a Signals episode

Method	Path
POST	/v1/signals/alerts/:episodeId/notes

Shared authentication, project scope, and response conventions.

An alert note is a practitioner comment stored as a FHIR Communication. It does not edit the alert and is not sent to Signals. Ovok also makes these notes available through /v1/slim/notifications.

The note response has this shape:

Field	Meaning
id	Note resource id.
target.kind, target.id	The target is medical plus an episode id, or alert plus a raw-alert id.
patientId	Ovok Patient id, or null when unavailable.
text	Note text.
author.practitionerId, author.name	Author identity and display name; either may be null.
createdAt, updatedAt	Timestamps; either may be null.

Adds a note to an episode. Only a practitioner can write a note. The route author comes from the bearer token; do not send an author field.

Input or result	Details
Access policy	signals_alerts:update
Patient access	Read access to the episode's Patient; this note operation does not require Patient update.
Body	{ "text": "..." }; trimmed text must contain 1–2,000 characters.
Success	201 with the saved note.
403	Missing capability or caller is not a practitioner.
404	Episode is missing, outside the project, or its Patient is not readable.
422	text is empty or exceeds 2,000 characters.

curl --request POST \
  --url 'https://api.sandbox.ovok.com/v1/signals/alerts/0b6f8c1e-2a4d-4e7b-9c3f-1d5e8a7b6c4d/notes' \
  --header "Authorization: Bearer ${OVOK_TOKEN}" \
  --header 'Content-Type: application/json' \
  --data '{ "text": "Checked on the resident; resting." }'