Most commonly, a user-defined message that Oracle Thesaurus Management System (TMS) returns to the external system; see answerable action and Unanswerable Action. In addition, Internal Actions are used for approving external action assignments or for internal communication.
The manner in which TMS assigns an Action; a answerable action is assigned at the first instance of an omission but not in subsequent appearances of an omission, a Unanswerable Action is assigned at every instance of the specified omission, and a discrepancy message is assigned to a specific TMS omission and applies to that verbatim term occurrence only.
A group of terms that TMS will activate during the same batch job. The group is defined in the Define Activation Groups window, and used during loading, updating, and modifying dictionaries.
A message that a user applies to an unprocessable verbatim term requesting a change to the term in the external source data system. TMS sends the action with the verbatim term to the external system. A user in the external system can either change the term as requested or send a message back to TMS that is visible in TMS.
Autocoding: the process of searching for exact matches to each new verbatim term occurrence (source term) among both VTAs and dictionary terms in the current domain.
A configuration for the TMS Lite Browser that enables users to connect without specifying a user name and password.
A dictionary to which you can add, modify, or delete terms and unapproved VTAs (unlike a virtual dictionary). Base dictionaries are useful for studies that require the most up-to-date dictionary information.
When a verbatim term matches a verbatim term previously classified with a Nonapproved VTA, TMS proposes the dictionary term linked by the Nonapproved VTA as the Candidate Term. If another occurrence of the verbatim term occurs in the same domain, TMS allows the user only to accept or reject the Candidate Term. If another occurrence of the verbatim term occurs in a different domain, the user can accept the Candidate Term or manually classify the verbatim term to a different dictionary term. If the verbatim term is linked to different dictionary terms in different domains, and the supplied and predefined domain match search object is linked to the dictionary, TMS presents the Candidate Terms that exist in other domains.
A characteristic of a relation between two dictionary levels; determines the maximum number of terms (one or many) in a level to which a term in another level may be linked. In TMS this characteristic is represented in the tree structure by the line between related levels: a single line symbolizes Single Cardinality and a branched line symbolizes Many Cardinality.
The process of assigning a VTA to a verbatim term. Depending on the verbatim term, the definitions in the dictionary domain, and the type of searches selected for the dictionary, TMS may accomplish classification automatically or may return an omission requiring user input. Only users with the TMS role tms_classify_priv may perform classification.
The dictionary level defined as the level in which TMS should search for matches to verbatim terms; verbatim term code level.
A relationship that you must define between two dictionaries before you can create relations from a term in one dictionary to a term in the other.
Deletion of a verbatim term assignment. Declassifying a source term creates an omission.
A series of related levels defined as derivable that begins at the classification level and includes all levels from which you want to derive terms. There must be one and only one path from the verbatim term level to derivable levels. Defining levels as derivable makes them part of the derivation path. To actually derive values from derivable levels, you must also define them as reportable.
The data collection unit set up in the external system to receive the term or other value TMS returns to the external system after classification.
A set of terms and relations; usually including a vendor-supplied (external) dictionary as its core, plus user-defined company and domain terms.
Terms and relations associated with a particular dictionary, including external terms supplied by a vendor and user-defined company and domain terms.
An external, company, or domain term associated with a particular dictionary, such as MedDRA or WHO-Drug.
dictionary term display procedure
A user-defined procedure used in omission management to show a different term in the derivation path than the classification level term. Selected on a dictionary-wide basis.
In Oracle Clinical or other external systems, an entry into the Discrepancy Management System created by Batch Validation when (in the case of thesaurus discrepancies) a verbatim term does not match a dictionary term or an Approved VTA; if the appropriate flag is set in the external system, requires resolution in TMS. See also omission.
An Action that you create and assign to a single occurrence of a verbatim term, sent one time only to the external system.
In TMS, a logical group of data assigned for use in a particular study or other work unit, including external dictionaries, company and domain terms, and VTAs.
The link between an Oracle Clinical study or project and the TMS dictionary and domain it uses for reference.
A relation defined by the user and available only within the domain in which it was created.
A term defined by the user and available only within the domain in which it was created.
A dictionary in which the terms do not belong to specified dictionary levels. In TMS, named relations define the linking between terms in dynamic dictionaries.
A vendor-supplied dictionary; a dictionary maintained and released by an organization external to the TMS customer company.
An application that is using TMS as its dictionary repository; for example, Oracle Clinical.
The primary language in which a study or project is conducted. When you specify Translation Derivation Links between dictionaries, you must choose which dictionary is in the global language and which is in the local language.
A browser-based tool for viewing and searching for TMS Repository data and source data in a read-only format.
Sets of columns that you can use in the TMS Lite Browser to customize which data is presented in the results for terminology and verbatim term searches. HTML layouts are dictionary-specific.
An indication omission that has been classified; a high-level classification based on the indication for which a drug was taken.
Different instances of the same dictionary coding-level term may be classified to different high level terms based on the indication for which the drug was taken by a patient. In this case, multiple high-level terms are related to a single lower-level dictionary term with no primary path defined. TMS cannot derive the high-level term and creates an indication omission. After a user manually classifies the indication omission, TMS derives all current and future occurrences of the same term for the same verbatim term/indication combination.
Data structures that provide more information about one term, relation, VTA, or dictionary as a whole, in the database.
Database-wide definitions for the Data Type, Attribute Type, and other properties of an Informative Note. All Informative Notes are based upon an Informative Note Attribute definition.
An Action that is assigned to a verbatim term for the purpose of approving the assignment of the associated base Answerable Action to the same verbatim term. When the Internal Action is approved, TMS sends the base Answerable Action, with any text modifications made by the approver, to the external system. Internal Actions can also be used to communicate internally with other TMS users.
(LOV, <LIST> function) A list of acceptable values for a field, populated by the system into a list or a shortcut window. Access the LOV by clicking on the arrow of the list, an ellipsis (…) button, or by pressing F9 while your cursor is in the field.
The secondary language in which a study or project is conducted. When you specify Translation Derivation Links between dictionaries, you must choose which dictionary is in the global language and which is in the local language.
See list of values.
View that provides indirect access to table data by storing the results of a query in a separate schema object. Unlike an ordinary view, which does not take up any storage space or contain any data, a materialized view contains the rows resulting from a query against one or more base tables or views. A materialized view can be stored in the same database as its base table(s) or in a different database.
more information on materialized views is available in the Oracle9i Database Concepts manual (part number A96524).
A verbatim term assignment that maps an incorrectly spelled verbatim term to an appropriate dictionary term.
A type of relation that defines the connection between terms. Named relations are defined on an installation-wide basis, and are used primarily in weak dictionaries.
A VTA, or classification of a verbatim term to a dictionary term, that has been created but not approved. The VTA must be manually applied to subsequent occurrences of the same verbatim term in the same domain. During manual classification, the system proposes the dictionary term as a candidate term.
A single instance of a verbatim term from the external system; for example, a response of a particular patient at a particular visit.
A verbatim term without a link to a dictionary term; if the appropriate flag is set in the external system, requires resolution by TMS. See also discrepancy.
In Oracle Clinical, the question that collects the response, or verbatim term, sent to TMS for classification.
Pre-dictionary tables; TMS tables that hold terms and relations awaiting activation, and terms and relations that have failed activation.
Data in the predict tables; terms and relations awaiting activation, and terms and relations that have failed activation.
Defines which single term is considered the predominant relation in a higher dictionary level where more than one term may be related to a single term in a lower level; defines the one term in the multiple-term level that should be derived or used for derivation farther up in the dictionary hierarchy.
Defines the derivation path between terms across any number of defined relations. Primary Path Links enable you to specify a Primary Path between a top level term and the coding-level terms without defining a series of Primary Links or Paths to bridge the levels in between.
In Oracle Clinical, defines the data derived from TMS to Oracle Clinical and associates a parent question with one or more derived questions.
Changing a verbatim term assignment so that the verbatim term relates to a different dictionary term.
The unique label that TMS applies to a particular build, or activation, of a dictionary. The Release Label consists of the Release Label Prefix followed by the build number.
A dictionary level whose terms can be reported to the external system as derived terms. You can report a level's terms only if the level's relation with its child is derivable and the external system is set up to call for derived terms.
Set of algorithms used to search the TMS Repository in order to find matches for verbatim terms during Autoclassification, to find Candidate Terms during manual classification, or to find Repository terms in the Extended Search window.
A term collected in an external system and sent to TMS for classification. A single occurrence of a verbatim term. In Oracle Clinical, a question response.
Tables that hold data from vendor-supplied ASCII files before it is loaded into the preliminary tables.
A connection between two dictionaries with the same data and dictionary structure, which enables you, given a term in one dictionary, to find the corresponding record in the other. These links serve to translate dictionary data in studies being conducted in two different languages.
A message that a user applies to an unprocessable verbatim term. TMS sends the action with the verbatim term to the external system. Any messages sent by a user in the external system to TMS are not visible in TMS.
The set of profiles that have been assigned to a TMS user, and the hierarchy of Search Orders that enable TMS to determine which profiles to use for defining default values.
Free-form text initially entered or loaded into the external system; source term; external system question response.
verbatim term assignment (VTA)
The mapping between a verbatim term and a dictionary term in a dictionary whose classification level contains unique terms. VTAs can be created either by TMS during Autoclassification, if a direct match or Approved VTA exists, or by a user during manual classification.
verbatim term individual (VTI)
The mapping between a verbatim term and a dictionary term in a dictionary whose classification level contains non-unique terms, created either by TMS during Autoclassification, if a VTI exists for a verbatim term with the same auxiliary information, or by a user during manual classification.
A dictionary containing all the terms and assignments for a base dictionary at a specified point in time, the cut-off date. Virtual dictionaries enable you to continue coding verbatim terms for a clinical study against one version of a dictionary while the base dictionary changes.
A TMS dictionary that contains one or more dynamic dictionaries. Each level of a weak dictionary folder can be a fully defined dictionary.
The external system unit used in data exchange with TMS. If the external system is Oracle Clinical, an X Area corresponds to a clinical study, identified by the clinical study ID. For other external systems, the X Area should be a unique number that defines the external system batch processing unit.