|
Set up internal global and
project specific dictionaries %tsetup(thesname = thesaurus name,
path = path location,
data = dataset name,
action = setup action,
key1 = key variable 1,
key2 = key variable 2,
key3 =
key variable 3);
|
Where |
Is Type... |
And represents... |
| thesaurus name | C | A unique name of the dictionary. For example:
- MedDRA version 8.1
- WHO Drug version 1.1
|
| path
location | C | The
physical file path location on the server where the dictionary will
be stored. |
| data | C | The SAS
dataset name that contains the dictionary information. This can
contain more than one dataset separated by spaces. |
|
action | C | Setup
action determines how the data will be updated. This includes:
- insert (default)
- update
- delete
|
| key1 | C | The
variable name of the first key. This is normally the verbatim
term for adverse event and drug name for drug dictionaries. |
| key2 | C | The
variable name of the second key. This is normally the preferred
adverse event term or drug name. |
| key3 | C | The
variable name of the third key. This is normally the adverse
event preferred term code or drug name ATC code. | Details
The %testup
registers the dictionary into a centralized database. The thesaurus
name must be unique since this is how it is selected. The key fields
are variables inside the specified dataset which contains the
dictionaries. Example %tsetup(thesname=MedDRA version 8.1, path=c:\thesaurus,
data=soc llt pt,
key1=llt_name,
key2=pt_name,
key3=pt_code); |
