Page History

Starting in Since ODM 1v1.3.0, there are two have been 2 forms of the ItemData element -- (the element used by the ODM for transmitting clinical data item values. These are the ): untyped and typed forms. The ItemData element, present in all previous ODM versions, is the form used for untyped data transmissions. The ItemData[TYPE] elements are the form used for typed data transmission.

The ODM schema for Version 1v1.3.2 includes the following ItemData[TYPE] elements:

...

All typed data value elements carry their data value as the as the element's PCDATA content. For example, an ItemDataInteger element would appear as:

<ItemDataInteger ItemOID="ID.114">100</ItemDataInteger>

Use of the ItemData[TYPE] element form permits the application receiving the ODM XML file to validate the ClinicalData when parsing the ODM file.

The ItemDataAny element is provided as an escape mechanism for transmitting clinical data values that do not have the correct DataType for the corresponding ItemDef. Receiving applications are not required to load the data values transmitted using ItemDataAny elements into the corresponding database field.

Typed and untyped data must not both be used within a single ODM file.

  <ItemDataString ItemOID="ID.115">
    <![CDATA[
	The five special characters that must normally be escaped are ' , " , < , > , &
	]]>
  </ItemDataString>

Systems that receive ODM clinical data files but do not normally support one 1 or more of the datatypes listed in this section should accept clinical data of the unsupported types as text. In cases where these systems transmit clinical data by generating a new ODM file with the unsupported type, the generated file must include the original datatype information.

...