The Operational Data Model (ODM) is a vendor-neutral, platform-independent data exchange format, intended primarily for interchange and archive archival of clinical study data pertaining to individual subjects, aggregated collections of subjects, and integrated research studies. The model includes the clinical data along with its associated metadata, administrative data, reference data, and audit information. All of the information that needs to be shared among different software systems during the setup, operation, analysis, submission or for long term retention as part of an archive is , and archiving of a study are included in the model.
This is version 1.3.2 Version 2.0 of the ODM. Section 2.5 5, Changes from Previous Versions provides , provides a summary of the new features. Detailed descriptions of the new features have been incorporated into the text of this document. ODM Version 1.3.2 has been designed to provide v2.0 breaks backward compatibility with previous versions of the model in most cases. In cases where backward compatibility has been impacted, it is due to clarifying the specification to more completely match the original intent of the standard.several ways noted in the Section 2.5 summary.
ODM v2.0 can be serialized as XML, JSON, or other formats. An ODM XML schema is currently Earlier versions of the model included a DTD. For version 1.2, both an XML Schema and a DTD were provided. Beginning with version 1.3.0 and going forward, only an XML Schema is available.
Clinical data management systems vary significantly in the information they store and the rules they enforce. The ODM model has been designed to represent a wide range of study information so as to be compatible with most existing clinical data management systems. Systems that do not have all of the features represented by the ODM model may still be ODM compatible as long as they comply with the conformity rules provided in the section on Section 2.3, System Conformity.
ODM has been designed to support extensions as documented in Section 2.4, ODM Extensions, and many organizations, in addition to CDISC, have created extensions to support requirements that extend beyond those documented in this specification.
ODM is the basis for the Define-XML and Dataset-JSON standard extensions used to represent tabular dataset metadata and data, respectively. These standard extensions target clinical research data, but may be used to represent any tabular dataset. Note that this ODM specification references subjects and subject data. A subject is defined as a participant in the study.
The ODM has been designed to be compliant with guidance and regulations published by the US Food & Drug Administration (FDA) for computer systems used in clinical studies. This document is intended to be both the formal specification of the ODM and a user guide for those involved in transferring or archiving of clinical data using the model.
...