Jira |
---|
server | Issue Tracker (JIRA) |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
---|
key | ODM-54 |
---|
|
ODM v2.0 can be serialized as either XML or JSON.
...
- The ODM file must be a well-formed XML file. See the XML standard for details.
- The ODM file must conform to the XML Namespace standard. See the XML Namespace standard for details.
- The ODM file must contain only elements and attributes defined in the ODM standard schema or in a valid vendor extension schema, and must satisfy the rules about element nesting and the formats of attribute values and element bodies.
- The ODM file must contain a single (top-level) ODM element
- The ODM file must use the ODM v2.0 namespace, which is "http://www.cdisc.org/ns/odm/v2.0"
- The ODMVersion attribute on the top-level ODM element must be set to "2.0"
- The ODM file should begin with a prolog, or XML declaration, as this is considered a best practice
The XML schema for Version 2.0 of the ODM can be found at https://github.com/cdisc-org/DataExchange-ODM. The final version of this specification will be posted at https://www.cdisc.org/standards/data-exchange/odm.
...
Code Block |
---|
language | js |
---|
title | Example of ODM v2.0 JSON file |
---|
|
{
"clinicalDataODM": {
"studyOIDODMVersion": "cdisc2.com/CDISCPILOT010",
"metaDataVersionOIDFileOID": "MDV.MSGv2.0.SDTMIG.3.3.SDTM.1.7000-00-0000",
"itemGroupDataFileType": {"Transactional",
"IG.DM"Description": {
"Sample ItemData Extension",
"recordsAsOfDateTime": 18"2022-06-04T07:57:00",
"CreationDateTime": "2022-06-06T10:30:00",
"nameStudy": "DM",
{
"labelOID": "Demographicsxxx",
"itemsStudyName": "NIH [ ...
Chronic Low Back Pain example",
],"MetaDataVersion": {
"itemDataOID": [ ..."yyy",
]...
}
}
}
}
|