I think it would be really helpful to add an Output Text Formatting setting to each custom template, because not every use case needs the same style of output.
For instance, a discharge instruction sheet should be easy for clients to read, with clear headings, short paragraphs, and simple bullet points. On the other hand, an AVImark medical note needs to be much more compact and structured so it can be quickly pasted into the medical record.
Having a dedicated formatting setting would let the template builder control things like:
Whether the output uses paragraphs or bullet points
The order and style of section headings
How concise or detailed the response should be
Use of bold text, numbering, or plain text
Formatting optimized for systems like AVImark
Spacing and line breaks
Whether the output is client-friendly or clinical/record-focused
This would keep prompts focused on what the AI should generate, while the formatting settings handle how it should look.
It would also make things much more consistent across a team or organization. Once a format is set up properly, users wouldn’t need to keep fixing formatting issues or rewriting instructions in every prompt—they could just rely on the template to handle it correctly every time.
Thanks for sharing this feedback.
The current Output Text Formatting setting is mainly global and focused on the copy/paste experience into different PIMS, such as choosing Rich Text, Plain Text, or Markdown depending on where the note will be pasted.
You’re right that there is a distinction between what the template should generate and how the output should be formatted. Today, template-specific structure and style can be controlled through custom templates, detail settings, and user instructions, including things like bullet points vs. paragraphs, section order, heading style, conciseness/detail level, spacing, and whether the output should be more client-friendly or medical-record focused.
That said, we can see how having these formatting preferences saved at the individual template level could make outputs more consistent across different use cases and teams, especially for workflows like client discharge instructions versus compact PIMS notes. We’ll keep this in mind as we continue improving template customization.