Form Configuration in Coder Tools


Coder Tools > Study Settings includes a Form Configuration section, which lists the Forms collecting coding data within the selected Study. From here, you can assign Synonym Lists and Do Not Autocode Lists to a Form, enable dictionary-specific fields, and upversion to a new dictionary release.

Accessing Coder Tools

To access the Coder Tools administration area, click the Tools tab in the primary navigation bar, and then click Coder Tools.

Access Coder Tools from the Tools Tab

Once in Coder Tools, you can click the sub-tabs to navigate to different areas within.

Assign a Synonym List to a Form

Before Vault can use a Synonym List for autocoding, and before coders can request to add new Synonyms, you must first assign a Synonym List to a coding Form.

To assign a Synonym List to a Form:

  1. Locate the Form you want to edit in Coder Tools > Study Settings > Form Configuration.
  2. Hover over the Form to display the Actions menu.
  3. Select Edit. Edit action

  4. In the Edit Form dialog, select a Synonym List.
  5. Click Save.
  6. Vault assigns the Synonym List to the Form. Vault now uses this Synonym List to inform autocoding on this Form.

You can edit the Synonym List assignment later.

Assign a Do Not Autocode List to a Form

Before Vault can use a Do Not Autocode List for autocoding, you must first assign a Do Not Autocode List to a coding Form.

To assign a Do Not Autocode List to a Form:

  1. Locate the Form you want to edit in Coder Tools > Study Settings > Form Configuration.
  2. Hover over the Form to display the Actions menu.
  3. Select Edit. Edit action

  4. In the Edit Form dialog, select a Do Not Autocode List. Select a Stop List

  5. Click Save.
  6. Vault assigns the Do Not Autocode List to the Form. Vault now uses this Do Not Autocode List to inform autocoding on this Form.

You can edit the Do Not Autocode List assignment later. Note that if you edit the assigned list, all coded Forms are reset to the Uncoded status.

Upversion a Form

Once a new WHODrug or MedDRA dictionary release is available, you can upversion a Form and the form’s assigned Synonym List to reference that new dictionary version. Upversioning a Form itself and the Synonym List that the Form uses are separate actions, but both are required to update the Form.

See Upversioning to a New Dictionary Release for details.

WHODrug Coding Fields

If a WHODrug form is configured to collect values for Indication and Route, you can configure the Form to display those values and use them to inform Code Request groupings.

Indication and Route are configured individually. You can select one, both, or neither of these fields.
Enabled (Selected)
  • Coder displays the a column for the coding field in the Code Request Listing page.
  • Vault stores the coding field in a Synonym and uses the property to inform autocoding from that Synonym List.
  • The coding field informs how Vault groups Code Requests in Grouped mode.
Disabled (Not selected)
  • Vault does not display a column for the coding field in the Code Request Listing page.
  • Vault does not store the coding field in Synonyms.
  • The coding field does not inform how Vault groups Code Requests in Grouped mode.

To enable WHODrug coding fields:

  1. Navigate to Coder Tools > Study Settings.
  2. Use the Study Selector to select your Study:
    • Type your study’s Name in the Search Studies field.
    • Click your Study to select it. Study Selector
  3. Locate the Form you want to update in the Form Configuration section.
  4. Hover over the Form to display the Actions menu.
  5. From the Actions menu, select Edit. Vault opens the Edit Form dialog.
    Edit action

  6. Select the Indication and Route checkboxes. Coding Fields checkboxes

  7. Click Save.

Enabling SAE Prioritization for MedDRA Forms

If a MedDRA form collects a Seriousness value, you can configure the form to display the collected Seriousness property during manual coding by enabling SAE (Serious Adverse Event) prioritization. Displaying the Seriousness of an adverse event allows coders to easily identify seriousness adverse events and prioritize them for coding.

Enabled (Selected) Vault displays a Seriousness column in the Code Request Listing page. The Seriousness value also informs how Vault groups Code Requests in Grouped mode.
Disabled (Not selected) Vault does not display the Seriousness column, and Seriousness does not inform the grouping of Code Requests.

To enable SAE prioritization for a Form:

  1. Navigate to Coder Tools > Study Settings.
  2. Use the Study Selector to select your Study:
    • Type your study’s Name in the Search Studies field.
    • Click your Study to select it. Study Selector
  3. Locate the Form you want to update in the Form Configuration section.
  4. Hover over the Form to display the Actions menu.
  5. From the Actions menu, select Edit. Vault opens the Edit Form dialog.
    Edit action

  6. Select the Enable SAE Prioritization checkbox. Enable SAE Prioritization checkbox

  7. Click Save.

To disable SAE prioritization for a Form, edit the Form and clear the Enable SAE Prioritization checkbox.

Which permissions control your access depends on when your vault was created. If your vault uses the Role by Study feature, see the first section, Role by Study Permissions. If your vault does not use the CDMS Role by Study feature, see the second section, Profile Permissions.

Role by Study Permissions

Users with the standard CDMS Clinical Coder Administrator application role can perform the actions described above by default. If your vault uses custom Application Roles, your role must have the following permissions:

Type Permission Label Controls
Functional Permission Coder Tools Tab

Ability to access the Coder Tools tab

Functional Permission Manage Coder Study Settings

Ability to edit Study Settings in Coder Tools

Learn more about Study Roles.

Profile Permissions

Users with the standard Vault Owner security profile can perform the actions described above by default.