Clinical note
Turn collected answers into a readable, structured summary that can be exchanged over the API, instead of making staff read raw form responses.
A clinical note formats data a care flow has collected into something a human can read, so clinical staff don't have to page through raw survey responses.
Clinical notes can be exchanged over the API, so the note can land in another system.
A note holds narratives plus context
- Narratives. Sections grouping content together, such as Anamnesis, patient-reported outcomes, or Follow-up, which can end up in separate fields elsewhere.
- Context. Metadata describing the note, such as a title or description.
Every narrative needs a key, a title and content
- Key. An identifier, unique within this clinical note action. The same key can be reused elsewhere in the care flow.
- Title. A description of the content.
- Content. The text to display, built with variables so it fills in per patient.
Split narratives the way the receiving system or the reading clinician expects, since a narrative is the unit that gets mapped onward.
Next steps
Next: Checklist for a different kind of structured action.
Use variables in your actions
Insert care flow data into messages, clinical notes and API calls with the slash command, so one action adapts to each patient.
Checklist
Give a care team member or patient a list of tasks to tick off inside a care flow, with a separate checklist per stakeholder if needed.