The patient's own wording is the part that must survive
Forms arrive with free-text boxes and are then retyped into the record. During that retyping, information is lost because the person summarizes as they go.
A well-organized structure helps the clinician read more quickly. The structuring is mechanical: what the patient reported, when the symptoms began, what the patient said about them, and the items they listed in the history and medication sections.
That is where the interpretation should end. Translating a described symptom into clinical terminology is an interpretive act with consequences. When a note presents the clinician's rephrasing as if it were the patient's own words, it misleads anyone who reads it.
The principle is to use direct quotation. The note arranges the text as written and retains the exact wording, so the clinician hears the patient's own words rather than a summary.
How the ActionFlow runs on the canvas
A Webhook trigger receives form submissions from your intake system. Those submissions already include free-text content.
A Filter node removes empty fields before any other processing. The entry then shows what was actually answered, not the structure of the form.
The Generate Object node arranges the content in the order your clinicians read it: reported concern, onset and duration, stated history, stated medication, and access needs. Each entry is a direct quotation of what the patient said.
The instruction is specific. When you reorganize information, quote it exactly. Never translate it into clinical language. Never infer what the patient said. For any section the form did not include, return an explicit empty.
A Validate node ensures that each filled section can be traced back to the submitted text. That is why an inferred entry does not enter the record.
If the patient has written in a language your clinicians do not understand, the Generate Text node translates. Both the original and the translation are kept, and the translation is clearly marked.
The HTTP Request node records the note in the record system. The Slack node informs the clinical team that it is ready. Nothing relating to clinical content is produced anywhere in this process.
Nodes this ActionFlow uses
- Webhook (Trigger): receives the intake submission from your form system.
- Filter (Data): removes unanswered fields so the note shows only the answers, not the form.
- Generate Object (AI Core): reorganizes into your sections with every entry quoted verbatim.
- Validate (Data): ensures that each filled section can be traced back to the original text.
- Generate Text (AI Core): translates only where needed, with both versions kept and marked.
- HTTP Request (Util): writes the administrative note into the record system.
- Slack (Communication): tells the clinical team the intake note is ready to read.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.