Clone and edit existing AutoText

Completed

Clone and modify an existing AutoText in PowerScribe One to efficiently create personalized report templates without starting from scratch.

Why clone AutoText?

Cloning uses an existing AutoText as a starting point while preserving its structure, default content, fields, and formatting. This approach reduces build time and supports consistency across reporting workflows.

Cloning and editing

Action	What it does	Use it when
Cloning	Creates a new AutoText based on an existing personal, site, or other user's AutoText.	You need a variation of a template. You want to preserve the original AutoText. You're adapting content from another user or site.
Editing	Modifies an existing AutoText.	You want to edit the content of an existing AutoText. The change should apply to all users of that AutoText. You're correcting or improving a shared standard.

AutoText structure and dependencies

AutoTexts can include:

• Text fields, Pick Lists, and merge fields.
• Nested AutoTexts, where modules are referenced within templates.
• Procedure code associations and default behavior.

Because other templates can reference modules, changes to a shared AutoText can affect multiple workflows. Use the **AutoText Preview pane to review references and change history and assess downstream effects.

Procedural guidance

Clone an existing AutoText

1. In the AutoText Manager, search for and select one or more AutoTexts.

   To select an AutoText, select the checkbox to the left of its name.

2. Select Clone above the column header.

3. In the Clone AutoText dialog box, confirm the number of AutoText to clone.

4. Select Yes to proceed.

5. If prompted, choose whether to keep or remove the default attribute.

6. In the success dialog box, review the confirmation message and select Ok.

The cloned AutoText opens in the AutoText Editor.

Tip

If you clone an AutoText that shares a name with an existing AutoText, the cloned AutoText gets a numerical extension.

Edit an existing or cloned AutoText

1. Open the AutoText that you want to modify in the AutoText Editor.
2. Review the lower pane search results, which remain available while you edit. Resize the pane by dragging its upper edge, or collapse it by using the down arrow.
3. Select an existing field to open the corresponding Text Field, Pick List, or Merge Field settings.
4. Update the content, formatting, or field settings as needed.
5. To add new content, press Enter to create a new line or paragraph, type a section heading, and then select Text Field, Pick List, Merge Field, or Table.
6. Apply formatting to selected text by using the options in the Formatting ribbon.
7. To open AutoText Settings, select the Settings icon. If a text field or Pick List is currently being edited, select X to close it first.

Changes are saved as you work.

Best practices for cloning and editing

• Clone before making major changes to shared templates.
• Use clear naming to distinguish original and modified versions, such as CT abdomen normal update.
• Review and update default values as needed.
• Remove or update outdated fields when cloning older templates.
• Test AutoText in a report to validate insertion and field behavior.
• Use copy and paste when appropriate, noting that pasted content retains field settings.

Applied scenario

You frequently use a shared chest CT template, but a new protocol requires more structured findings.

Instead of modifying the shared template, you:

1. Clone the existing CT chest standard AutoText.
2. Rename it CT chest extended protocol.
3. Add new structured fields for more findings.
4. Update procedure code associations for the new protocol.

This approach preserves the original template while enabling a tailored workflow for specific clinical use cases.

Accessibility and usability notes

• Use descriptive names to distinguish cloned templates from originals.
• Keep field labels clear to support consistent data entry.
• Avoid unnecessary duplication and reuse structured elements where possible.
• Ensure formatting supports readability for long reports.
• Review nested AutoTexts to avoid confusion or unintended duplication.
• Validate templates after editing to reduce downstream reporting errors.