|
Creates the Data Definition Clinical Domain
Documentation %datadef (datname=dataset name,
outdoc=output file name,
outtype=output file type,
fmtlib=format library,
link=link to derivation);
| Where | Is
Type... | And
represents... |
| dataset name | C | Name of the dataset to be
documented. This should be a valid dataset defined in the
data object. |
| inlib | LIBNAME | Library referencing the location of the Trialex data
object. |
| outdoc | C (optional) | The physical name of the new html file created
containing the documentation. This includes the path. If
this is not specified, the default location is the location where
the inlib libname is defined. For example:
dat_dataname.html
Note that the data name is replaced by the
name of the dataset. |
| outtype | C (optional) | The output file type. Valid values include:
|
| fmtlib | C (optional) | The two level name of the format library. By
default, the value is:
library.formats
|
| link | C (optional) | Link to program derivation option. This would
either create the link or do not create any hyperlinks. Valid
options are:
| Details
This generates the clinical domain
documentation according to the standards established by CDISC– Clinical Data
Interchange Standards Committee. For more
examples from CDISC, click here. The
following pieces of information are captured from the dataset:
- Data Set Name
- Variable Name
- Variable Label
- Variable Type
- Formats
- Origins (Source)
- Role
- Comments
Some metadata are inherent to the dataset and associated
format, but others are captured by tools such as %vardef. This tool will also create an index file named
dat_index.html which contains list of all the dataset for the current
studies. This index file contains hyperlinks to the detailed
documentation of each dataset. Example %datadef(datname=a_ae);%datadef(datname=demog,
outdoc=c:\myfolder\demog.html );
%datadef(datname=demog,
fmtlib=mylib.formats); |
