CDISC Procedure for CDISC ODM

PROC CDISC Statement for CDISC ODM

Specifies CDISC ODM as the model and references the physical location of the input or output ODM XML document.

Requirement:

Required for both importing and exporting.

PROC CDISC MODEL=ODM

READ=fileref |WRITE=fileref
<FORMATACTIVE= NO | YES >
<FORMATNOREPLACE= NO | YES>
<FORMATLIBRARY=libref>
<LANGUAGE=language-identifier> ;

Arguments

MODEL=ODM

specifies CDISC ODM as the model.

Requirement:	Required for both importing and exporting.
Interaction:	The model specification determines the syntax for the PROC CDISC statement and subsequent procedure statements. Specifying MODEL=ODM requires that you specify either the READ= or WRITE= argument and that the next statement must be the ODM statement.

READ=fileref

specifies the SAS fileref that is assigned to the input XML document.

Requirement:

Required for importing.

WRITE=fileref

specifies the SAS fileref that is assigned to the output XML document.

Requirement:

Required for exporting.

FORMATACTIVE=NO | YES

specifies whether the content in the CDISC ODM CodeList element, which includes instructions for transcoding display data in an XML document, is to be converted to PROC FORMAT style formats or SAS formats, and vice versa.

For both importing and exporting, FORMATACTIVE=NO causes formats to be ignored. This is the default.

For importing, FORMATACTIVE=YES does the following:

Converts CDISC ODM CodeList content to the corresponding SAS format, or creates PROC FORMAT style formats from the CodeList content.
Registers the SAS formats in the referenced variables.
Stores the created SAS formats in the SAS FORMAT library.

For exporting, FORMATACTIVE=YES converts SAS formats to the corresponding CDISC ODM CodeList content and variable references.

Default:	NO
Requirement:	Optional for both importing and exporting.
Interaction:	(Optional) If you specify FORMATACTIVE=YES, then you can specify FORMATNOREPLACE= and FORMATLIBRARY=.

FORMATNOREPLACE=NO | YES

specifies whether to replace existing SAS formats in the FORMAT catalog when an existing SAS format has the same name as a format that is being converted by PROC CDISC.

When FORMATNOREPLACE=NO, the procedure replaces existing SAS formats that have the same name. This is the default.

When FORMATNOREPLACE=YES, the procedure does not replace existing SAS formats that have the same name.

Default:	NO
Requirement:	Optional for importing.
Interaction:	Ignored unless FORMATACTIVE=YES.

FORMATLIBRARY=libref

specifies the assigned libref of an existing SAS library in which to create the FORMAT catalog, which is a permanent storage location for variable formats that are created by PROC CDISC.

Requirement:	Optional for importing.
Interaction:	Ignored unless FORMATACTIVE=YES.

LANGUAGE="language-identifier"

specifies a language identifier for the language tag attribute (xml:lang) in the ODM TranslatedText elements.

When importing, PROC CDISC locates the specified language identifier in the ODM TranslatedText element, and creates a SAS format by using the TranslatedText items with a matching language tag attribute. The created SAS format is then applied to the data that is imported from the XML document.
When exporting, PROC CDISC uses the specified language identifier as the language tag attribute value in the ODM TranslatedText element.

A language identifier, as defined in the XML specification, can be one of the following:

A two-letter language code as defined by ISO 639, "Codes for the representation of names of languages."
A language identifier that has been registered with the Internet Assigned Numbers Authority (IANA). The language identifier begins with the prefix i- or I-.
A language identifier that has been assigned by the user or agreed on between parties in private use. The language identifier begins with the prefix x- or X- to ensure that it does not conflict with names that are later standardized or registered with IANA.

Enclose the language identifier in single or double quotation marks.

Requirement:	Optional for both importing and exporting.
Featured in:	Example: Importing a CDISC ODM XML Document Using a Language Identifier

Top of Page