Best practices: Optimizing templates for Omni AI features

Rad AI Reporting’s Omni AI features work best when templates are optimized to take full advantage of their capabilities

Read on for tips to help you optimize your templates for Omni Report, Omni Impression, and Omni Unchanged.

💡 To learn more about how to create and manage templates, visit our templates and macros Help Center article.

In this article: 

• Overview
  • Key terms
• Structure
  • 1) Keep templates as simple as possible
  • 2) Add an impression zone
  • 3) Place findings on a separate line from headers
  • 4) Pair single field prefixes with single fields on the same line
• Fields
  • 5) Make field names specific
• Default text values
  • 6) Make default text values specific
  • 7) Keep default text concise and resilient
  • 8) Avoid duplicate default text values across fields
• Picklists
  • 9) Use picklists for single findings only
  • 10) Avoid using nested picklists
  • 11) Enter labels and values for all picklist options
• Troubleshooting

Overview

In traditional reporting software, radiologists navigate through a template field by field, inserting findings as they go. With Rad AI Reporting, you can simply dictate your findings into the Omni Box and say "Omni Report". Omni Box will then use AI to place each finding in the correct field—so you no longer need to move from one field to the next with hotkeys or voice commands. 

To ensure accurate placement, configure your report templates in advance so the system knows which fields should receive Omni Box findings and which sections should remain unchanged. For best results, set up your templates in a way that supports the AI. Read on to learn how.

Key terms

Scroll down for key template terms and definitions, or watch this video:

The following table displays definitions for key terms related to the creation and management of templates. To access the template editor, select Templates from the main navigation menu.

	Term	Definition	Notes
1	Default text value	The pre-filled text that automatically appears in a template field when the report is created, serving as a starting point that you can keep, edit, or replace. It’s often a 'default normal statement' (e.g., "Unremarkable").	Click a field to view its properties on the right-hand side, where you can edit the name of the default text value.  The Field name also appears in the "Outline" view in the report workbench.
3	Field	A type of template element that prompts you to enter information (e.g., specific findings) into the report. There are three types of fields:  Text fields prompt you to type a value into the report. Data and formula fields automatically populate the report with information that’s available to Reporting.	All types of fields can have a field name and a default text value. Learn more about fields.
3	Field name	The name of a field, used by the AI to map Omni Box findings to the correct location in the template.	Click a field to view its properties on the right-hand side, where you can edit the field name.  The Field name also appears in the "Outline" view in the report workbench.
4	Field prefix	The descriptive text that appears to the left of a template element—such as a field—to indicate what should go there. Usually followed by a colon. The field prefix is considered by the AI.	Examples: “Spleen”, “Liver/Gallbladder”, “Bowel”, “Pancreas”
5	Embedded template	A template that is inserted into another template as a linked component. It can only be edited at its source, and changes apply everywhere it is embedded.	Learn more about embedding templates
6	Header	A title or section label in a template that typically appears at the top of a content block to organize and introduce the information that follows. The AI does not use this to determine where to locate findings from the Omni Box	Examples: “History”, “Technique”, “Comparison”, “Findings”, “Impression”
7	Impression zone	A designated area in a template where Omni generates the impression, protecting content (e.g., fields, picklists, notes) outside that zone from being overwritten.	Learn more about setting impression zones.
8	Observation	Pre-configured fields that can only be edited by administrators	Learn more about configuring observations.
9	Omni Box findings	The text that you dictate into the Omni Box. When you start an Omni Report or use the Omni Unchanged command, the AI will automatically assign findings to the correct fields in the template.	Learn more about Omni AI.
10	Picklist	A type of field that allows you to select one option from a predefined list of choices, rather than entering free text. Picklists standardize input and streamline workflows by presenting a set of selectable options from a menu.	Example:  For “Liver/Gallbladder”, the picklist options are: 1: Normal  2: Fatty 3: Gallstones

Structure

1) Keep templates as simple as possible

Best practice for Omni Report and Omni Unchanged

As the number of available fields, picklists, or assignment options in the template increases, so does the risk of the AI placing findings in the wrong location.
 

Recommendation

✅ Use the simplest possible template structure and verify that all findings are transferred to the correct fields.

 

2) Add an impression zone

Best practice for Omni Report, Omni Impression, and Omni Unchanged

An impression zone tells Omni exactly where to generate an impression. By default, Omni Impression, Omni Report, and Omni Unchanged overwrite any content under the Impression header such as notes, picklists (e.g., BI-RADS, TI-RADS, Lung-RADS, LI-RADS, Fleischner, Bosniak, etc.), and fields—including those with potentially critical outbound messages to other software (e.g., MQSA management tools). 
 

Recommendation

✅ To preserve default statements and fields when using AI, set a clearly defined impression zone right under the Impression header so the AI knows where to start generating the impression and which content to leave unchanged. 

All content under the Impression header will be retained when Omni is run, even if the impression spans multiple lines. Learn more about setting an impression zone.



 

3) Place findings on a separate line from headers

Best practice for Omni Report and Omni Unchanged

The AI doesn’t take headers into account and may struggle to map findings to fields located right next to headers. For best results, headers should exist on a separate line by themselves, with any related findings listed below.
 

Recommendation 

✅ Place picklists and findings on their own lines beneath the section header.

Example:

FINDINGS: 

Tubes/lines: | None |

4) Pair single field prefixes with single fields on the same line

Best practice for Omni Report and Omni Unchanged

Omni compares your dictated findings with template content and uses the field name and the default text value to determine where to place each finding in the template. For this reason, Omni Report and Omni Unchanged work best when prefixes are followed by single, relevant fields that have a default text value.
 

Recommendation

✅ Keep the field on the same line as its prefix to prevent the AI from potentially removing the prefix.

Structure prefixes and fields like this:

Biliary: | Unremarkable |

💡 You can substitute "Unremarkable" with your preferred default language.

Fields

5) Make field names specific

Best practice for Omni Report and Omni Unchanged

Field names are used by the AI to map Omni Box findings to the expected field. Omni works best if the field provides appropriate context. Unnamed fields, generic field names (e.g., "1", "2", "3"), and field names that are unrelated to the template’s content may result in findings being inserted into the wrong fields.
 

Recommendation

✅ Give every field in your template a name that is specific and provides context to the AI. For example, you can name fields based on anatomy (e.g., “Gallbladder”) or pathology (e.g., “Ovarian cysts”). Learn how to edit field names.

Default text values

6) Make default text values specific

Best practice for Omni Report and Omni Unchanged

Entering default text values and making them specific is essential because it helps the AI accurately map dictated findings to the correct fields and prevents findings from being omitted or inserted in a different place (e.g., an "Additional findings" section).
 

Recommendation

✅ For the "Coronary artery calcifications" field, use a default text value such as: "There are no coronary artery calcifications."

❌ Avoid leaving the default text value blank. If blank, the AI can’t determine the appropriate field for the finding “Mild coronary arterial calcifications are noted”. It may generate an "Additional findings" section and place the finding there instead.

7) Keep default text concise and resilient

Best practice for Omni Report and Omni Unchanged

Default text can include one or multiple 'normal' statements per field. That said, shorter defaults are more robust: as more normal statements are bundled together, there’s a higher chance that one line may be dropped or rewritten when a new finding is inserted.

Example:

• Default: No hydronephrosis, calculus, or enhancing mass.
• Finding: 3 mm right UPJ calculus.
• Possible Output: Kidneys: 3 mm right UPJ calculus. No enhancing mass. (“No hydronephrosis” omitted.)
   

Recommendation

✅ For the most consistent results, use one key default statement per field when possible.

If you prefer multiple default statements, that’s supported—just review that default normal language persists after AI insertion.

8) Avoid duplicate default text values across fields

Best practice for Omni Report and Omni Unchanged

Using the same specific default text value in multiple fields can cause inconsistencies.

Example: No free fluid in both the Peritoneal and Pelvis fields may result in one field keeping the default text value and the other replacing it with a finding.
 

Recommendation

✅ Assign each specific default text value to only one field. General terms such as Unremarkable or Normal may be used across multiple fields without issue.

Picklists

9) Use picklists for single findings only

Best practice for Omni Report and Omni Unchanged

Picklists work best when you expect to capture one discrete finding (e.g., Normal, Mild, Severe, Present/Absent). Omni AI does not “select” multiple picklist options. Instead, Omni treats picklists like a text destination and typically inserts one finding based on the field prefix and picklist option value.

If multiple findings are dictated for the same category, Omni may place only one finding into the picklist and redirect the remaining statements to an “Additional findings” section.

Example: 

In the template, the “Liver:” field prefix is followed by a single picklist:

Liver: | ▼ | 

The user filling in the template dictates multiple liver findings (e.g., nodules + diffuse low density). Omni AI will typically place one liver statement in the picklist field, and the rest may appear in the “Additional findings” section.
 

Recommendation

✅  Choose the appropriate element, based on the number of findings you expect to capture:

• Use a picklist when you expect one finding per field prefix. Keep each picklist option limited to one finding (don’t bundle multiple statements into one option).
• Use a text field when you may need to display more than one finding under the same field prefix.
   

10) Avoid using nested picklists

Best practice for Omni Report and Omni Unchanged

Currently, Omni Report’s AI doesn’t recognize nested picklist options (i.e. picklists that have options within options), so it won’t place Omni Box findings into nested fields.
 

Recommendation

✅ Avoid using nested picklists when designing templates. Instead, use simple, single-level picklists or replace them with clearly labeled text fields so the system can more reliably interpret and map dictated findings.

11) Enter labels and values for all picklist options

Best practice for Omni Report and Omni Unchanged

If a picklist option doesn’t include at least one character in its value field, the option won’t display any labels or function when selected. Empty values can make it harder for the AI to determine where to place findings.
 

Recommendation

✅ Ensure each picklist option includes at least one character in its value field.
 

Troubleshooting

When using my template, Omni AI created an 'Additional findings' section. How do I avoid this?

• Make the field names and default text values more specific.
   
  • Example: Within the CT abdomen template, the AI can’t determine the appropriate field for the finding “Mild coronary arterial calcifications are noted,” so it generates an “Additional findings” section and places the finding there instead.
     
  • Solution: Change the field name “Lower chest” to “Lower chest and coronary calcifications”.
     
• Insert a field with a name—but without a default text value or field prefix—to create a placeholder for dictated-only findings.
   
  • Example: The AI can’t determine the appropriate field for the finding "Hiatal hernia", so it generates an “Additional findings” section and places the finding there instead.
     
  • Solution: Add a dedicated field for dictated hiatal hernia statements. This field will only appear in the report if a hiatal hernia is present, ensuring the finding is placed in the preferred section.