Clinical Form Management- Using {{value}} When Building a Form

What is a [value] | Where to put [value] | Field types | Recap

If you're building a custom form for clinical notes, this guide will walk you through one of the most important pieces: the {{value}} button. Don't let the technical-looking name intimidate you — it's simpler than it looks, and once you understand it, your forms will work exactly the way you want.

 Before you start:

We recommend reading the Best Practices for Building Custom Forms guide first. It's a great starting point that will help you get the most out of the clinical notes feature.

What is [value] and why does it matter?

Think of {{value}} as a placeholder. When you (or a provider) fill out a form field — like typing in a patient's symptoms or selecting a location — {{value}} is what tells the system to take that answer and drop it into the clinical note.

In short: no {{value}}, no note. The information gets entered into the form, but it won't show up in the generated note unless {{value}} is in the right place.


Where do I put [value]?

For each form field, you'll see a section called Generated Text. This is where you write the sentence or label that will appear in the note. You need to place [value] somewhere in that Generated Text so the system knows where to insert the answer.

Example: If you want the note to say "History of present illness: Patient presents with [what the provider typed]", you would write: History of present illness: Patient presents with {value}.

Each field only needs one {value} in its Generated Text section.

Which field types use [value]?

The following field types all work the same way — place one {value} in the Generated Text and the answer will flow right into the note:

 Short-Text Fields

This is a simple open text box where the provider types something in. Whatever they type will replace {value} in the note.

Before building your form, we recommend reviewing Best Practices for Building Custom Forms designed to help you make the most of the clinical notes feature.

Example generated text: History of present illness: Patient presents with {value}.

Single Select Fields

This field gives the provider a list of options to pick from — they can only choose one. The option they select will appear in the note wherever {value} is placed.

 Example generated text: Injection site: {value}


Multiple Select Fields

Similar to single select, but the provider can choose more than one option. All of their selections will be pulled into the note.

 Example generated text: Preparation of the area to be injected included {value}.


Fraction Fields

Fraction fields let providers enter a number out of a total — like a pain scale of 7/10. The {value} in the Generated Text will display both numbers together in the note.

 Example generated text: Patient describes pain as {value}.


Quick Recap

Here's all you need to remember: 

  • Every form field that needs to show up in the note must have {{value}} in its Generated Text section.
  • You only need one {{value}} per field.
  • This applies to short-text, single select, multiple select, and fraction fields.
  • Write a natural sentence in the Generated Text area and place {{value}} where the answer should go.

 Still have questions? Check out theBest Practices for Building Custom Forms guide or reach out to your support team.