1 Getting Started

This chapter introduces the basics of using Oracle Thesaurus Management System (TMS) and includes:

About Oracle Thesaurus Management System (TMS)

Pharmaceutical companies that develop new drugs are required to produce reports that document the effects of the drug. However, the data used to produce these reports, including information on health conditions and medications, can be hard to analyze because the terminology is inconsistent. Even when a company uses a dictionary of appropriate terms provided by an organization such as the World Health Organization, data collected during the study may be inconsistent with its terminology for a variety of reasons:

  • Medical personnel may use terminology different from that of the dictionary.

  • Companies may have developed new drugs since the dictionary's creation.

  • A study may require more precise terminology for a health condition than is available in the dictionary.

  • Medical personnel may misspell drug names or health conditions.

  • Data entry personnel may misinterpret or mistype the data.

TMS can transform this data into a consistent terminology that statisticians can analyze more easily.

TMS refers to an item of data initially entered or loaded into the system—drug or health condition information or other data item—as a verbatim term (VT). TMS maps verbatim terms to dictionary terms in a process called classification. TMS automatically classifies verbatim terms that directly match a dictionary term, and enables you to classify variant or misspelled terms manually. You can choose to have future occurrences of the same verbatim term automatically classified the same way, or you can choose to require manual classification, with the previous classification presented. You can also add terms to vendor-supplied dictionaries and modify your own terms at any time.

Usage Models

TMS serves as the single terminology repository for clinical studies, and can be made available to all applications used in studies. Particular applications, or external systems, are more or less compatible with TMS. Depending on the degree of compatibility, TMS can be installed in different degrees of integration with the external system(s).

The more fully TMS integrates with your clinical study application, the better it serves you. However, you can still benefit from TMS if your other software permits only partial integration, or even no integration.

Full Integration

Full integration requires the installation of TMS objects in the external system, a level of integration that is recommended if the external system is running in a stable global Oracle environment. In full integration, TMS maintains external data in both the tms_source_terms table and the tms_vt_omissions table.

A fully integrated system benefits from the full range of TMS functionality. It feeds source terms to TMS with contextual data you specify (such as Patient and Document Number) so that if you reclassify or declassify a term in TMS, TMS can send information about each affected source term back to the source data system.

In TMS, you run Autoclassification, manually classify remaining terms (omissions), assign Actions, and reclassify or declassify as necessary. You specify the information you want to derive from TMS for each source term, and TMS sends that data to the source data system associated with each source term.

Partial Integration

If full integration is not desirable—for example, if space is an issue—you may want to set up TMS with only partial integration to your external source data system. In partial integration, TMS maintains external data in the tms_vt_omissions table only. It does not store any data in the tms_source_terms table.

The external system feeds data to TMS, and TMS returns derived data and omissions. You can classify terms manually and perform all other functions within TMS. However, because the tms_source_terms table is not used, TMS has no external system information (such as patient ID or document number) associated with source terms and therefore cannot associate derived terms with source terms after the initial classification.

See "Partial Integration" for more information.

No Integration

Even if TMS has no knowledge of your external system, you can use TMS as a dictionary repository. You can use TMS to access, add, and modify dictionary terms. You can take advantage of TMS's flexible hierarchical dictionary structure and data validation. However, TMS functionality in this scenario is limited in the following ways:

  • TMS cannot receive terms directly from the external system, but you can load them or enter them manually in TMS.

  • TMS cannot handle omissions.

  • The external system must handle the impact of reclassification and de-classification on derived data.

  • High-level classification is not available.

Following is one scenario for using TMS with no integration to the external system:

  1. Check for matches between the external system's source data and the TMS repository.

  2. Load or create VTAs in TMS for verbatim terms in the external system that did not map to a term in the TMS repository.

The no-integration approach is recommended if the external system does not run on an Oracle database.

Dictionary Definition and Customization

TMS supports the inclusion of any number of dictionaries in its repository. You can use dictionaries supplied by a vendor such as WHO (an external dictionary) and/or convert a legacy company dictionary. You can customize external dictionaries by adding company terms. You can customize dictionaries in multiple ways, all available simultaneously, by using TMS domains.

Flexible Definition

You can create a dictionary in which terms inherit the relations of the levels to which they belong, or one in which you store all the terms on a single level and use the relation itself to define the connection between the terms. For dictionaries with multiple levels, you can define any number of levels in a given dictionary; you can group levels, and you can create a hierarchy of any shape or degree of complexity. You define both ends of the relation between each pair of related levels, specifying:

  • whether the relation is optional in each direction, and in some cases, whether the relation is mandatory in each direction

  • whether a single term in one level can map to more than one term in the other level, in each direction

  • whether the parent-level end of the relation can have multiple links, whether a term in the child level must have a Primary Link to a single term in the parent level

  • the currency of viewable data. Base dictionaries contain all dictionary information that is currently not expired in the TMS repository, while virtual dictionaries can represent the state of a dictionary at a particular point in time.

See Chapter 6, "Defining and Loading Dictionaries" for more information.

TMS automatically performs validation to ensure that links between terms do not violate the level relations you have defined.

Customization

You can add company terms to external dictionaries if, for example, you need to use the name of a new drug that is not included in the external dictionary.

If you need several more specific terms instead of one more general term provided by the dictionary, you can mark the external dictionary term as Unapproved to ensure that it is not used for classification, forcing the use of the more specific company terms instead.

Different studies or projects may have different terminology needs. TMS addresses this issue with the concept of user-defined TMS domains. You associate external dictionaries with TMS domains and customize them differently in each domain, creating TMS domain-specific terms and relations. See Chapter 6, "Defining and Loading Dictionaries" for more information on defining and using domains in TMS.

The API

TMS includes PL/SQL packages to accomplish all TMS tasks, providing the ability to interface with many external applications. Your external system calls these packages instead of manipulating the database directly, thus avoiding database corruption. The API is documented in the Oracle Thesaurus Management System Technical Reference Manual. Contact Oracle Support to receive a copy.

The following table shows a subset of the API packages, and the purpose of each one.

Table 1-1 Sample API Packages and Their Purpose

Package Purpose

tms_user_classification

Creates accepted or misspelled verbatim term assignments (VTAs), which map the corresponding correct or misspelled verbatim terms to dictionary terms.

tms_user_action

Enables you to specify comments for unclassified VTs, which can be propagated to the external system's discrepancy management system.

tms_user_reclassification

Reclassifies VT to another dictionary term or declassifies the VT.

tms_user_fullautocode

In fully integrated external systems, this package matches a new or updated verbatim term with a dictionary term, and returns values.

tms_user_autocode

In partially integrated external systems, this package matches a new or updated verbatim term with a dictionary term.


Basics of Using TMS

The following sections describe the interface and cover common features in TMS, including:

Launching the Application

TMS runs in a Java-based window that you initiate from the launch page. To start a session:

  1. Open a browser window and connect to the following URL:

    http://server.domain/path_variable/launch.htm

    where server.domain is the TMS application server and path_variable is the configuration variable that you set during the TMS front end installation; for example, opa52. (See the Oracle Thesaurus Management System Installation Guide.)

    Your browser window loads the Oracle Health Sciences Applications launch page.

  2. Click Login. The browser launches two windows: an Oracle Developer Forms Runtime window, and a small browser window containing the warning not to close the window.

  3. In the Forms Runtime window, enter your user name, password, and the TMS database to which you want to connect, then click OK. If you have an account on the selected database and have entered the correct password, the Forms Runtime window displays the TMS Navigator window.

Note for Internet Explorer Users:

Do not open another Thesaurus Management System session from this session. To start another Thesaurus Management System session, open it from the Windows Start menu or from the Internet Explorer desktop icon. If you instead start a new session by selecting New from the File menu or by using the shortcut combination Ctrl+N, the new session may be unstable and unpredictable.

Getting Started with Your Oracle Health Sciences SSO Account

Your organization will create an Oracle Health Sciences SSO account for you. With this account, you can access any Oracle Health Sciences SSO-enabled application owned by your company and to which you are authorized, including TMS.

After your account is created, you receive three email messages, which contain:

  • Your account name, which you can use to log in to Oracle Identity Self Service, the TMS Lite Browser, and other Oracle Health Sciences SSO-enabled applications.

  • A temporary password for your account and a link to Oracle Identity Self Service where you can manage your account.

  • Your DB Login Name for the account, which you can use together with the Oracle Health Sciences SSO account password to log in to TMS.

Save the link to Oracle Identity Self Service so that you can access it whenever you need to manage your account settings. Do not save it in your browser by bookmarking the address where the link redirects, but by right-clicking on the link in the email message and choosing to copy the underlying link address.

Initial Setup

After you receive the messages containing your account name and temporary password, click the link to Oracle Identity Self Service to set up your account.

When you log in to your Oracle Health Sciences SSO account for the first time, you must reset your account password and define challenge questions for your account. Challenge questions are security questions that you must answer to verify your identity when you use the Reset Password link from the Oracle Health Sciences SSO login page.

Assistance with Your Account

Your organization's delegated administrator manages user accounts for all your company's Oracle Health Sciences applications that are SSO-enabled, including TMS. Contact your organization's delegated administrator for assistance related to your Oracle Health Sciences SSO account if:

  • Your account is locked because you entered the wrong password too many times.

  • You need help resetting your account password.

  • You need help updating account information, such as first or last name, email address, or user name.

  • You require additional privileges or encounter access issues.

Changing Your Database Password

This section describes how to change your own password in the TMS database. You can only change your password for the database to which you are connected; you must repeat these steps for every database in which you want to update your password.

There are three methods of changing your password, depending on your privileges and on whether Oracle Clinical is integrated with TMS:

If You Have Administrator Privileges in This Database

If you have privileges equivalent to the SYSTEM user in this database, you can change your own password (and update the passwords of other users in the database) from a SQL*Plus prompt. This process is an administrator-level activity, so see "Changing a User's Password".

If Oracle Clinical Is Not Installed in This Database

If you are running TMS in a standalone configuration, follow the procedure in this section to update your database password.

  1. From the TMS main window, select File, then choose Change DB Password. The Change Password for User_Name window opens (Figure 1-1).

    Figure 1-1 Change Password Window

    Description of Figure 1-1 follows
    Description of ''Figure 1-1 Change Password Window''

  2. Enter your old password, then enter and confirm your new password.

  3. Click Change Password. The system validates your old and new password entries. The system returns "Password changed" if all entries are correct, or a descriptive error message if the old password is incorrect or the two new password entries do not match.

    If you click Cancel, the system retains your old database password and closes the Change Password window.

If Your Database is Integrated With Oracle Clinical

If you are connected to a database that is integrated with Oracle Clinical, you can change your own password either by selecting Options, then Change DB Password from the Navigator window or from the Change Database Password window in Oracle Clinical (From Oracle Clinical's Admin menu, select Users, then Database Password). However, once you launch the Change Database Password window, the system deactivates the Change DB Password selection under the File menu for the rest of your session.

Note:

When you use the Oracle Clinical Change Database Password window to change your password in an integrated database, the system disables TMS windows for the rest of your session. You must exit and reenter TMS before you can open any windows.

Using TMS Windows

All TMS windows, except those used for creating reports and other batch jobs, provide the same set of icons, keystrokes, and menu options to perform common functions. Windows used for reports and batch jobs provide another set. Appendix C, "GUI Quick Reference" contains a complete set of icons, keystrokes, and menu options for functions in both types of windows.

This section contains additional information on the following tasks in the GUI.

Understanding Color Indicators

TMS conveys some information using color cues.

Table 1-2 Color Indicators in the User Interface

Function Color Displayed What is Colored

Current record

Blue

Area to left of record

Query mode

Light blue

Field background

Mandatory field (batch jobs and reports)

Red

Text in field

Drill-down information available

Blue

Text in field

Read-only information

Gray

Field background


Changing the Display

You can change the way data is displayed by selecting single- or multi-record display. You can change which data is displayed by using the tree structure and querying. See "Using the Tree Structure" and "Querying in Windows".

Single/Multi-record Display Option

In general, the single-record display is more useful when you are modifying data because it allows you to see all the information for a record at once, without scrolling. The multi-record display is useful when you are querying; you can scroll up and down to quickly see all the records retrieved, and scroll across to see the complete information for each record.

Sort Order

You can sort records on any active column label (column labels that appear three-dimensional, with the column heading in boldface). Click once to sort on a column in ascending order. Click again to sort in descending order. Click a third time to return to the default unsorted state. A sort icon appears in the label after you use it to sort. The system sorts numbers by the first digits, no matter how many digits the number contains, so that 12345 comes before 543 in ascending order.

Using the Tree Structure

The tree structure that appears on the left of many windows serves different purposes depending on the window, but its behavior is consistent throughout TMS:

  • Nodes, or branches, of the tree structure expand and collapse when you click the boxed + or - icons in the tree structure, use the +, -, ++, or -- icons in the toolbar, or use the menu options in the Navigation menu.

  • The system populates the right side of the window according to what you highlight in the tree structure.

  • The display of the tree structure changes according to changes you make on the right side of the window.

  • In some windows you highlight a level in the tree structure and execute a query in the current-level block (usually the middle text block on the right side of the screen) to display data.

  • When a tree structure node is the active field, dotted white lines appear along the top and bottom of the blue background, highlighting it. When no dotted white lines are displayed in the highlighted node, the active field is on the right side of the window.

The system uses the tree structure for two purposes: the menu and dictionary hierarchy.

The Navigator

When you first open TMS, the Navigator window opens. This window displays the main menu tree and, if you have it installed, Oracle Clinical as well. Each item under the TMS node represents a TMS subsystem; for example, from the Repository Maintenance menu you can open windows for updating term and relation data in the TMS repository. See Figure 1-2 for an overview of the menus that appear in the Navigator.

In some cases the objects you create also appear in the navigator tree: dictionaries, levels, and Activation Groups that you have already defined appear in the tree structure; if you click them, the system displays the definition you created. To create a new object, highlight the menu option above it in the tree structure and select Insert Record.

To open a window or run a batch job or report, click either the icon or the text.

The menu items in the navigator are covered in TMS documentation as follows:

  • Favorites. Save shortcuts for commonly used windows in the Favorites menu. See "Using the Favorites Menu".

  • Oracle Clinical. If you integrate TMS with Oracle Clinical, the OCL menu options appear above the TMS node. See Chapter 4 for TMS/Oracle Clinical integration information.

  • Define Dictionaries and Domains. Define base and virtual dictionaries from the Define Dictionaries window, and link dictionaries together. The Define Domains window allows you to create domains and assign dictionaries to them. See Chapter 6.

  • Defining External System Integration. Chapter 4 covers integration with Oracle Clinical. Chapter 5 covers integrating with external systems other than Oracle Clinical, including Disconnected System Integration.

  • Other Definitional Tasks. Chapter 7 explains the other Definition windows, where you define elements for use in assigning VTs, attributes of the external systems with which TMS exchanges data, and reference codelists.

  • Security and Administration. Chapter 3 covers reference codelists, other settings, and security.

  • Repository Maintenance. Chapter 12 describes how you can modify data in the TMS repository within a single dictionary or between multiple dictionaries, and how to view dictionary loading error logs.

  • Dictionary Upgrade. Chapter 8 describes how to use TMS features to control the impact of upgrading to a new version of a vendor-supplied dictionary on your repository.

  • Verbatim Term Assignment Maintenance. The windows and jobs under VTA Maintenance enable you to promote and demote VTAs, maintain Actions, reclassify verbatim terms, perform High-Level Reclassification, and copy domains. You can also run reports about VTA data, such as the Nonapproved VTAs Report, the Classification to a New Domain Report, and the three Classification Changes reports. See Chapter 11.

  • Task Allocation. Chapter 9 describes how to set up task allocation and how to allocate tasks—approving actions and VTAs and classifying omissions—to users.

  • Omission Management. Chapter 10 describes how to classify VT Omissions, approve VTAs, and run Omission-related reports.

  • Disconnected System Integration Maintenance (DSI). Chapter 5 describes how to use DSI to exchange information with disconnected systems.

  • Repository. Users without data modification privileges may still view repository data using the windows under the Repository node. These selections are covered in Chapter 13.

  • Translation Reports help you identify which term and relation data are not consistent between two dictionaries in a Translation Derivation Link. For background on translation derivation, see "Defining a Translation Derivation Link". For specific information on the three translation reports, see "Translation Reports to Identify Inconsistent Data".

TMS Lite Browser. Chapter 14 describes how to use the TMS Lite Browser, which has a separate login and user interface.

Dictionary Hierarchy Tree Structure

Dictionary levels, and the relations between them, are displayed in many windows through the tree structure (Figure 1-3, "Hierarchical Structure in the Maintain Repository Data Window").

Figure 1-3 Hierarchical Structure in the Maintain Repository Data Window

Description of Figure 1-3 follows
Description of ''Figure 1-3 Hierarchical Structure in the Maintain Repository Data Window''

Using the Tree Structure to See Data

The Maintain Repository Data window includes a dictionary's tree structure on the left side and three blocks on the right. To view data in the blocks of fields, highlight a level in the tree structure and then execute a query on the right. TMS displays terms that you queried for in the level you highlighted. After TMS populates the text block(s), you can highlight a different level in the tree structure and TMS will make that level the current level, with only terms related to the former current term displayed.

Understanding Multiple Displays of One Level

In order to show all relations between levels, sometimes TMS displays a level more than once. For example, levels within a group are shown once within the group level, with the relation between the group level and the level above it displayed, and once with the relation between the top sublevel and the level above it displayed. Similarly, if a level has more than one parent level, it is displayed once for each parent. All its child, grandchild, and other levels also appear below it each time.

In the sample WHODrug dictionary shown in Figure 1-3, "Hierarchical Structure in the Maintain Repository Data Window", the Source of Drug level is shown twice in the Verbatim Term Classification Group level. TMS does this because Source of Drug has two parent levels: the Drug Constituents level and the Preferred Name level, and because it is also linked to the ATC group.

In the tree structure, select the level display that you prefer. Some levels may be displayed twice or more because they have a relation to more than one parent level. To see terms in a parent level as well as the current level, you choose the display of the current level that is linked to the parent level you want to see.

Understanding Tree Structure Icons

TMS uses small icons to convey information about the hierarchy:

Table 1-3 Tree Structure Icons

Icon Information

VT

Indicates that TMS has created this level to hold verbatim terms and their VTAs.

p

Indicates that a Primary Link is required in a parent level where many cardinality is allowed; that is, more than one term in the parent level can be linked to a single term in the child level, and one of them must be designated as the Primary Link.

pp

Indicates that a Primary Path Link is required in a parent level where many cardinality is allowed.

Group level icon

Indicates that this level is a group level. Levels within the group (except for the topmost level) are displayed with their end of the relation shown in red. They appear on the same branch in the tree structure.

__

Mandatory relation; terms in the related level must have a relation to a term in the level with a solid relation line.

- -

Optional relation; terms in the related level may or may not have a relation to a term in the level with a dotted relation line.

Many cardinality icon

Many cardinality relation; terms in the related level may be related to more than one term in the level with a branched (crow's foot) relation line.

__

Single cardinality relation; terms in the related level may not be related to more than one term in the level with a single relation line.


To refresh the tree structure display, select Navigate, then choose Refresh Tree.

Changing the Sort Order

Many windows enable you to sort records by clicking one of the column headings. Click an active column head—one that looks like a button, and displays the column heading in boldface—once to indicate that you want to sort on it (alphabetically for character fields, numerically for numeric fields). Click again to sort in the opposite order.

Note:

TMS sorts numbers by the first digits, no matter how many digits the number contains, so that 12345 comes before 543 in ascending order.

Options Menu

The options included in the Options menu change for each window. Common selections under the Options menu include Change Domain, Filter, and Informative Notes. Any tasks you can perform using a button are also available in the Options menu and keystroke combinations. See Appendix C for a complete list of keyboard shortcuts.

Showing the Environment

TMS displays the current TMS version number and the current database in the title bar. Select Help, then Show Environment to display the following information:

  • User and Instance

  • Current Window Name, Module, Block, and Field

Selecting Multiple Records

Several windows in TMS enable you to select more than one record using the standard Windows behavior of Shift+Click for adjacent records and Ctrl+Click for separated records. The windows are High-Level Reclassification, Demote VTAs, and the Assign/Revoke Role subwindow of Define Users.

Changing the Database Connection

Under some conditions, you can change the database to which you are connected without logging out by selecting the Connect option from the File menu. If your database is integrated with Oracle Clinical, however, TMS disables this feature upon your first visit to an Oracle Clinical window.

Printing the Contents of a TMS Window

You can print a hard copy of any window in TMS by selecting File, then Print from the TMS menu bar. The generated printout displays the TMS window as it appears on your screen, showing the data that appears in the TMS interface for that window.

Note:

The other menu bar option, selecting File and then Print Contents, has no effect in TMS.

Querying in Windows

TMS follows standard Oracle querying procedures in every window of the user interface. In addition, in many TMS windows you can take advantage of the advanced text retrieval capabilities of Oracle's interMedia Text software (formerly known as the Context Server Cartridge), which is integrated into the RDBMS in an Oracle9i platform.

About Query Mode

You are in Query mode when you have entered but not yet successfully executed or canceled a query. When you are in Query mode:

  • TMS changes the background color for all fields in the block to light blue.

  • You cannot change the Query Type (Standard or Context).

  • You cannot modify data in any window.

  • You cannot select another level in the tree structure.

  • You cannot change domains.

To end Query mode, either execute or cancel the query. If you execute the query and no records are retrieved, TMS stays in Query mode. If the query does retrieve records, TMS displays the records and exits Query mode.

Starting a Query
  1. Do one of the following:

    • Press F7.

    • Choose Query, then select Open Query.

    • Click the Open Query icon (see Appendix C).

  2. Enter the alphanumeric text you want TMS to search for. You can always enter a standard Oracle query. If there is a Query list in the TMS window where you are working, you can choose to enter either a Standard Oracle query or a Context query, which requires the interMedia Text software.

Entering a Standard Query

Standard Oracle queries recognize the following:

Wildcards There are two wildcards that standard Oracle queries recognize:

The underscore (_) character is a single character wildcard, which can represent exactly one character in your search. Thus, the query no_e returns records with Nose and Note, but not Noise.

The percent sign (%) is a multi-character wildcard, which can match one or more characters in your search, or even none. A query on %bite% in the Term field would retrieve the terms Human Bite, Bite, and Bite on Nose.

No Text To retrieve all possible data, enter no parameters.

Entering a Context Query

Context queries use the interMedia Text software, which enables more flexible searches of TMS terms and relations. The Browse Repository Data window and the advanced search pages in the TMS Lite Browser allow you to switch between standard and context queries; see Chapter 14, "Using the TMS Lite Browser"

The Context Server Index is language-specific and configured for English language searches by default. You can change the language preference for the index by running the tmscincontextinx.sql script. See "Enabling Context Searches for Non-English Dictionaries".

The following table lists four types of operators that context queries use to expand or change the scope of a search.

Table 1-4

Name Operator Function Example

Fuzzy

?

Finds words with a similar form; checks for common spelling, keyboard, and OCR errors.

?aspirin finds aspirin, ascriptin, and aspellin

Stem

$

Finds words with the same linguistic stem (root).

$crush finds crush, crushed, and crushing

Soundex

!

Finds words that sound similar.

!hair finds hair and air

About

( )

Finds terms that contain concepts that are related to your query parameter.

(car) finds car, auto, and automobile


Note:

Two attributes are available to make fuzzy searches more precise. You can set fuzzy_numresults to n where n is the maximum number of results you want. You can also set fuzzy_score to a number between 1 and 80 to retrieve only terms that score n in nearness to the original term.

Because context queries are driven by the interMedia text software, you may require a different syntax for these searches than in the rest of the TMS user interface. For example, TMS forms and interMedia handle hyphenated terms differently. When you enter a query for a term such as 'musculo-skeletal system' in a TMS form, TMS returns all of the terms that contain that text. The interMedia text option, however, treats the hyphen character ('-') as an operator between two terms in a search. To search for the same term in the TMS Lite Browser, you must precede the hyphen with a slash ('\'). The search becomes:

musculo\-skeletal system

For more information on using special characters in context searches, see the Oracle interMedia User's Guide and Reference (part number A88786).

Counting the Number of Records Your Query Retrieves

Do one of the following:

TMS displays the count at the bottom of the window.

Executing the Query

Do one of the following:

To execute the same query again, press F7 F7 F8, in sequence.

Cancelling the Query

Do one of the following:

Using the Favorites Menu

You can add shortcuts to the TMS Navigator window for quicker access to commonly used forms and jobs. TMS displays these shortcuts under the Favorites node, at the top of the Navigator menu tree.

Favorites are private and database-specific: your choices appear only when you are logged into this TMS database.

Adding Shortcuts

To add a shortcut to the Favorites menu:

  1. Select File, then Save as Favorite. TMS prompts you to select a form or batch job.

  2. Click OK, and click the form or job you want to add to the Favorites. The Save as Favorite window appears.

    Description of save_favorite.gif follows
    Description of the illustration ''save_favorite.gif''

  3. Enter a name for the shortcut, and click OK.

  4. In the Favorites menu, click the selection under which you want the new shortcut to appear. To save the new shortcut at the top of the Favorites, or if this is the first shortcut for this system, click the Favorites node itself.

    TMS saves the new shortcut under the Favorites node in the navigator tree.

Removing Shortcuts

To remove a shortcut from the Favorites menu:

  1. Select File, then choose Delete Favorite. TMS prompts you to select a form or batch job to remove from the Favorites menu.

  2. Click OK, and click the Favorites shortcut you want to remove. TMS prompts you to confirm this deletion.

  3. Click OK to delete the shortcut. TMS removes this Favorite from the navigator tree.

Getting Help

For additional information about TMS, see:

Online Help

TMS contains online help for every field and window except batch jobs.

To launch online help:

  1. Place your cursor in the field for which you want help; if you wish to read online help for the entire window, the cursor can be placed in any field.

    Note:

    The cursor must be active in a field; you must actually click in a field or enter text. It is not enough to have the window open; you will see help for the last window in which you were active.
  2. Click the question mark icon at the right of the toolbar, press F1, or select Help, and then choose Help from the menu. TMS displays the field help pop-up box for the field your cursor is in. Figure 1-4 shows the help box for the Short Name field in the Define Dictionaries window.

    Figure 1-4 Field Help for Short Name Field in Define Dictionaries

    Description of Figure 1-4 follows
    Description of ''Figure 1-4 Field Help for Short Name Field in Define Dictionaries''

  3. If this help is sufficient, click OK to close the window. If you want help for the window in general, click More in the field help pop-up box. A new browser window opens and loads the appropriate topic in a help file. You can scroll along the file or use hot links to navigate to other topics.

    You can also write your own company-specific online help and access it through the Custom Help button in the field help window.

Oracle Help Center

The latest product documentation is available on the Oracle Help Center at http://docs.oracle.com/health-sciences/tms-521/index.html.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.