1 / 9

define.xml.v2 row-level metadata

define.xml.v2 row-level metadata. documentation and example Richard Senecal, Senior Principal Programmer NJ CDISC Users Group Merck/Summit, September 19, 2013. CDISC Define-XML Specification Version 2.0. Value Level Metadata sections. what is the context?.

brock
Download Presentation

define.xml.v2 row-level metadata

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. define.xml.v2row-level metadata documentation and example Richard Senecal, Senior Principal Programmer NJ CDISC Users Group Merck/Summit, September 19, 2013

  2. CDISC Define-XML Specification Version 2.0 Value Level Metadata sections | Presentation Title | Presenter Name | Date | Subject | Business Use Only

  3. what is the context? converting vertical files to horizontal vertical file horizontal file | Presentation Title | Presenter Name | Date | Subject | Business Use Only

  4. where does it live in define.xml? page 12 | Presentation Title | Presenter Name | Date | Subject | Business Use Only

  5. Codelists for VSTEST and VSTESTCD page 29 and IE DEMO vs.vstest and vs.vstestcd | Presentation Title | Presenter Name | Date | Subject | Business Use Only The VSTEST CodeList uses EnumeratedItems to store the list of possible values, as listed in the NCI/CDISC SDTM Controlled Terminology documents. The VSTESTCD CodeList uses CodeListItems to reflect the association with VSTEST items.

  6. define version 1 vs version 2 page 34 | Presentation Title | Presenter Name | Date | Subject | Business Use Only • define.v1 attached valuelist to –TESTCD and was assumed to describe the –ORRES only • define.v2 attaches valuelist to any variable: • --orres • --orresu • --stresc • --stresn • --stresu

  7. How the sections are chained together pages 35 - 40 | Presentation Title | Presenter Name | Date | Subject | Business Use Only • ItemGroupDef • has ItemRef for variables like VSORRES • ItemDef for VSORRES • has a def:ValueListRef pointing to a def:ValueListDef • def:ValueListDef • has ItemRefs for values of VSORRES (like DIABP) • in each ItemRef, there’s a def:WhereClauseRef • def:WhereClauseDef • has logic like: if VSTESTCD eq “DIABP”

  8. How the sections are chained together (cont...) pages 35 - 40 | Presentation Title | Presenter Name | Date | Subject | Business Use Only • ItemDef for the DIABP value in VSORRES • DataType="integer“ • Length="2“ • SASFieldName="DIABPOR“ • Description=Diastolic Blood Pressure (Orig U) • def:OriginType="CRF“ • def:PDFPageRefPageRefs="11“ • ...

  9. Thank You !

More Related