Add a Custom Field

PowerScribe One supports the use of Custom Fields to capture structured, site-specific, or workflow-driven data within radiology reports. Custom fields are configured by administrators in the Admin Portal and can be embedded in AutoText for use during report creation or added manually as metadata.

Prerequisites

  • Confirm that the AutoText you plan to use supports Custom Field workflows.
  • Verify that you have access to the required Custom Fields.
  • Custom Fields are created and managed by PowerScribe One administrators in the Admin Portal.

Using Custom Fields in a report

Insert a Custom Field value while dictating

  1. Launch a report using a template that contains Custom Fields. The Custom Field names appear in the Fields section of the left navigation pane.
  2. When prompted, dictate or select a value for the Custom Field and enter any required data. If configured by your PowerScribe One administrator, measurement values may populate automatically.
  3. Complete the report and continue with your normal workflow actions, such as signing the report.

Add Custom Field from the Procedure Data

  1. In the Report Editor, select Procedure Data from the right pane, then select Add Custom Field.
    The Custom Fields dialog box opens.
  2. Select a Custom Field to assign a value.
    • Some Custom Fields use Pick Lists.
    • Other Custom Fields require you to manually enter a value.
  3. (Optional) To narrow the list of Custom Fields applicable to your role, select the Filter by role checkbox in the lower-left corner of the dialog box.
    Custom Fields assigned by your administrator to specific procedure codes further refine the list to only relevant fields.
  4. Enter values for the Custom Fields that apply to your report.
    • You are not required to populate all Custom Fields.
    • Fields marked as required by the administrator are indicated by a blue visual indicator to the left of the field name.
  5. When finished, select OK.
  6. The entered Custom Field values are now associated with the order and the report.
    • If the Custom Fields are included as part of an AutoText, the values appear in the report body.
    • If not, the values are stored as metadata on the order and are not visible in the report body.

Troubleshooting and best practices

  • If a Custom Field does not appear in a report, verify that the field is correctly assigned to the AutoText.
  • Periodically review and update Custom Fields to align with evolving clinical or operational requirements.
  • Use practice scenarios or test reports to validate Custom Field behavior before deploying changes to production workflows.
  • Custom Fields can be managed across multiple sites and user accounts, supporting flexible and standardized workflows.