Overview

This section describes which tasks you can perform in the TMS Lite Browser, how it structures information in a Web browser window, and how to edit the list of dictionaries available for browsing.

For more information, see:

• Available Repository Data and Verbatim Terms
  
• Available External System Data
  
• Basic and Complex Searches
  

Available Repository Data and Verbatim Terms

This section describes which dictionaries you can search and browse in TMS Lite Browser windows.

For more information, see:

• User Roles
  
• Accessible Dictionaries
  
• Autoquerying Dictionaries
  
• Searching Across Dictionaries and Domains
  

User Roles

Any user with the RXCLIN_READ role can browse and search for dictionary data. Oracle Clinical users with the RXCLIN roles (such as RXCLIN_READ and RXCLIN_MOD) have access to dictionary data, but cannot search for source data without a TMS role. See Available External System Data.

Accessible Dictionaries

The TMS Lite Browser can display Repository data, including verbatim terms, for all of a database's active dictionaries that have the Accessible to Light Browser? option selected. If the dictionary is accessible and has a verbatim term level, you can use it to search for verbatim term data.

You can change the Accessible to Light Browser? setting for any dictionary by selecting that box for the dictionary in the Define Dictionaries window of TMS. You may want to leave this option deselected for dictionaries that you want to keep secure.

As long as a dictionary is accessible, you can browse or search it in the TMS Lite Browser. This includes base and virtual dictionaries, and strong and dynamic dictionaries. See Defining and Loading Dictionaries for an overview of the types of dictionaries you can define in TMS, and what characteristics distinguish them.

Autoquerying Dictionaries

When you autoquery a dictionary in the TMS Lite Browser, it displays all of the terms in the top level of that dictionary. Because only strong dictionaries contain top levels, autoquerying is only possible for this type of dictionary.

You can make a dictionary eligible for autoquery by selecting the Autoqueried in Light Browser? box for that dictionary in the Define Dictionaries window.

For instructions on autoquerying, see Browsing in the Terminology Data Tree Structure.

Searching Across Dictionaries and Domains

You can browse for Repository data within one domain (including the Global domain) or across all domains, and from a single dictionary or across all accessible dictionaries.

Available External System Data

Source data searches scan the data in one external system or all integrated systems for the source term that you enter. The TMS Lite Browser keeps external system data secure during these searches. If a record contains the source term for which you searched, but you do not have sufficient privileges to browse that record in the external system, the Browser will not allow you to view the record either.

The Source Data Search feature only appears in the TMS Lite Browser when:

• You log in as a user with one of the following TMS roles: TMS_CLASSIFY_PRIV, TMS_RECLASSIFY_PRIV, TMS_APPROVE_PRIV, or TMS_RESEARCH_PRIV. You may want to grant an external system user the TMS_RESEARCH_PRIV role if you prefer to deny them access to TMS, but grant them access to Source Data Searches in the TMS Lite Browser.

• You connect to a database in which TMS is fully integrated with an external system. Oracle Clinical and Oracle Adverse Event Reporting System are fully integrated automatically, but you can fully integrate with other external systems as well.

Basic and Complex Searches

All advanced search pages in the TMS Lite Browser include Use Context Search boxes, which control whether the browser performs a Basic or Context Search. The difference is significant: Basic Searches can use only two of the special character operators, which enable you to introduce fuzzy logic or language properties in your search.

The two allowable special characters in Basic Searches are the wildcards. The single character wildcard (an underscore: _) matches any single character when inserted in a query. The multi-character wildcard (a percent symbol: %) matches one or more characters.

In addition, the syntax for including wildcards is different in Basic and Context Searches. Assume you want to search for all dictionary terms that begin with the word "ankle" and end with the word "swelling." This search would yield three matches: "ankle swelling", "ankle really swelling" and "ankles are swelling."

Basic Search syntax follows standard SQL queries. Inserting a multi-character wildcard (%) directly between the starting and ending strings returns all three matches:

ankle%swelling

Context Searches treat multi-character wildcards differently. You must insert a space after the wildcard to retrieve the same results:

ankle% swelling