...
| Metadataspec |
|---|
| highlight | true |
|---|
| color | blue |
|---|
| keys | highlight |
|---|
|
| # | Functionality | Use case | Element | Attribute | Description of Functionality Change | Detailed Functionality (Specification) |
|---|
1
| Coding
|
| New |
| The Coding element references a symbol from a defined code system. It uses a code defined in a terminology system to associate semantics with a given term, codelist, variable, or group of variables. The presence of a Coding  ODM-6 Done element associates a meaning to its parent element.
| Coding
| 2
| Nested ItemGroupDef |
| Enhanced |
| Groups of ItemGroups or ItemsDefs, allowing nested structures that can represent a more diverse range of data structures. The revised ItemGroupDef element facilitates a number of new capabilities based on a more flexible re-use of groups of items; for instance, defining enhanced semantics when items share a common relationship or ODM-2 Under Team Review grouping common behaviors such as skip logic or pre-population. | ItemGroupDef | 3
| StudyEventGroupDef |
| New |
| Groups of StudyEventGroups or StudyEvents, allowing nesting ODM-3 Under Team Review of StudyEventGroups. StudyEventGroups are also used to define "study cells", i.e. crossings of epochs and arms. | StudyEventGroupDef
| 200
| CDISC 360 Support | New |
|
| Allows representation of ODM-7 Under Team Review biomedical concepts using new ODM v2.0 features such as nested ItemGroupDefs. | ParameterValue ItemGroupDef ItemDef CodeList CodeListItem EnumeratedItem Annotation Coding
| 100
| Study Design Model (SDM-XML) integration and enhancement | New |
|
| The many new study design model elements provide rigorous, machine-readable, interchangeable descriptions of study designs, including treatment plans, study design parameters, eligibility, and times and events. The new and updated study design elements permit various levels of detail in any representation of a clinical study’s design. | Protocol
| 200
| HL7 FHIR Interoperability
| New
|
|
| Provides the metadata needed to retrieve data from a FHIR resource to populate a variable referenced by an ItemRef. | Origin, Resource, Coding
| 300
| Traceability (Trace-XML Features) Support
| Enhanced
|
|
| Machine-readable end-to-end metadata traceability. | Origin
| 7
| Data Query Support
| New
| New
|
| Explicit support for data queries and the data query lifecycle. | Query
| 5
| MethodDef
|
| Enhanced
|
| Improved traceability and checking added with a method signature that defines zero or more input parameters and a return datatype(s). Support for external FormalExpression references that can point to a code library. | MethodDef FormalExpression
| 400
| Data Capture | Enhanced
|
|
| ODM Repeating ItemGroup based on a code list so that each term in the code list represents one or more questions on a CRF. Support for matrix style forms. | ItemGroupDef | 6
| TranslatedText |
| Enhanced
|
| TranslatedText supports alternative media-types so, for example, XHTML which can be used to enhance the display of the text. | TranslatedText
| 500
| Multi-lingual Support
| Enhanced
|
|
| Expanded use of TranslatedText to provide broader multi-lingual support. | TranslatedText
| 8
| AdminData |
| Enhanced
|
| Elements improved based on input from usage experience and updated for compatability with CTR-XML and SDM-XML. | AdminData
|
| Operational Datasets
| New
|
|
| Reference implementation that uses ODM v2.0 to represent datasets for the exchange of tabular raw data, such as an EDC vendor, CRO or service provider sending data to a sponsor as a tabular dataset. |
| 600
| JSON Serialization | New
|
|
| ODM v2.0 includes an updated version of Dataset-XML and a serialization optimized for JSON called Dataset-JSON | JSON representation for ODM
| 4
| Origin | Enhanced | New | Removed | ODM v2.0 includes an Origin element that replaces and enhances the Origin attribute in ODM 1.3.2. The Origin information on an ItemDef has also been moved to an ItemRef, so that an Item can have a different Origin depending on where it is used. | Origin |
|
|
|
|
| |
|
|
|
|
|
| |
|
|
|
|
|
| |
|
|
...
| Metadataspec |
|---|
| highlight | true |
|---|
| color | blue |
|---|
| keys | highlight |
|---|
|
| Functionality | Element | Attribute | Notes | Replacement Functionality |
|---|
FormDef | Deprecated |
|
| ItemGroupDef/@Type="Form"
| | Presentation | Deprecated |
| Presentation metadata can be added as an extension. |
| | ItemData[Type]: | Deprecated |
|
|
| | Certificate | Deprecated |
|
|
| | BasicDefinitions | Deprecated |
| An alternative method of associating units with measurement variables that better aligns with CDASH and SDTM has been implemented. | ItemRef/@UnitsItemOID
| Annotations (Container)
| Deprecated |
| The Annotations container was only allowed in conjunction with ItemData[Type].
| Annotation | | AuditRecords | Deprecated |
| The AuditRecords was only allowed in conjunction with ItemData[Type].
|
|
|
Future specifications
As ODM v.2.0 has a representation in XML as well as in JSON,
| Jira |
|---|
| showSummary | false |
|---|
| server | Issue Tracker (JIRA) |
|---|
| serverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
|---|
| key | ODM-4 |
|---|
|
a "format-neutral" path- and navigation language "
ODMPath" (based on
FHIRPath) is currently in development. This is "work in progress" and the current status (non-normative) can be found
here. As such, ODMPath is not part of the current specification.
...