Define custom terms

When you define a custom term, you create a new query or use an existing query to determine which cases meet the criteria for the term. When defining a new query, you have the option to save it to the Query Library. You can then use it to define custom terms for other data mining runs.

When you re-run a run, Oracle Empirica Signal uses the same custom terms in the run. However, you cannot switch run types. Thus, if you plan to use a custom term for different run types, make sure that you save the query you define for the custom term for the first run you set up. Then you can select that query as the custom term for the other run type(s).

1. In the left navigation pane, hover on the Data Analysis icon ( ), then click Data Mining Runs.
2. Click Create Run.
3. Select the type of run to create:
   • MGPS data mining run
   • Logistic regression data mining run
4. Select a data configuration.
5. Click Next.
6. Select your variables and check Define custom terms. For information about variable selection, see Select the variables.
7. Click Next.
8. Click Create Custom Term.
9. In the Name field, enter the name of the custom term.

   If a custom term name includes an invalid character, the application changes it automatically, and a message appears to inform you of the change. Invalid characters are replaced with a pound sign (#). Invalid characters for this field are:

   • Invalid filename characters: \, /, <, :, >, |, ?, *, ”, &, and null
   • Control characters
   • Non-ASCII characters
10. In the Item Variable field, select the variable to which the custom term will be assigned. Available variables are those that you selected as item variables for the MGPS data mining run, or as the Event or Drug variable in a logistic regression data mining run. A variable is not available if it is mapped via a data transformation or is associated in the data configuration with a hierarchy table (rather than a hierarchy account).
11. Choose one of the following:
    • To create a custom term by defining a new query, click Create Using Query Wizard. The Define Query page appears. You can save the new query to the Query Library so that you can re-use it for other runs.
    • To create a custom term based on an existing query, click Create from Existing Query. The Select Query from Library page appears. Subsequent changes to the query in the library will not affect the custom term.

    The screen refreshes and displays the query you created or selected in the Query field. If you click Edit Query, the Define Query page appears and you can change query variables, values, and logic.

    Note:

    If you saved the query to the library and then you edit it from this page, your changes are not saved to the library.
12. If the data configuration selected for an MGPS run specifies a drug or event hierarchy, you can select an existing term that has the primary path that you want to associate with the custom term. Next to Hierarchy Path, click Select <hierarchy> Term to view the hierarchy. If you select a term, the results table includes its hierarchy values for the custom term. If you do not select a term, the results table does not include hierarchy values for the custom term.

    The term that you select to indicate the primary path is always a PT (Preferred Term), even if the variable for which you are creating a custom term is a HLT, HLGT, or SOC. The option to specify a hierarchy path applies only to MGPS runs, and has no effect on logistic regression runs.

    To remove a previously specified hierarchy path click Clear Hierarchy Values. (Before changing a hierarchy path, you should clear the hierarchy path.)

    Note:

    Custom terms do not appear, and are not available for selection, from the hierarchy.
13. When you are satisfied with the custom term, click OK.

    The new custom term appears on the Define Custom Terms page.