Date

30 July 2014

Attendees

Goals

  • Metadata Curator's Assessments on CDISC CT Mappings

Discussion Items

TimeItemWhoNotes
 Mapping relationships
  • One-to-one; One-to-many; Many-to-one
 Questions (1) - (3) 
●Is there a rule for which column is the “nucleus” of a given CT mapping? The drawings above assumes the mappings evolve around C66741 for Vital Signs, and C71153 for ECG [Context: asset organization]
oNotes: Units technically apply to both TESTCD and TEST; therefore, the nucleus is a combination of both
●CDASH, SEND, SDTM all have EG and VS domains. Will mappings be unique to a particular standard? How about unique to one version of a standard? [Context: asset organization]
oNotes: CDASH is a direct absolute subset of SDTM. CDASH may not use all the test/test codes. There may be a chance CDASH further subset an SDTM CT. PoC will focus on SDTM for now.
●Will new mappings be always additive, i.e., will there be deprecations? Corrections? [Context: asset versioning]
oNotes: Code depreciation is possible, therefore CT Mappings will need to reflect that change. Add/modify/delete are all possibilities.
●Will mappings contain which codelist the codes belong? [Context: asset relationship]
oIt is a nice to have so we don’t need to “guess”; agreed to be explicit to facilitate imports
●Is it conceivable ECG will have units mappings like Vital Signs? If so, will mappings have names to differentiate multiple mappings? [Context: asset naming convention; asset organization]
oCan a domain have more than 1 CT mapping?’
§Notes: Not for PoC now; will wait and see if this scenario surfaces in the future
oWill there be one gigantic CT mapping for domain LB? In other words, will there be one for urinalysis, another for hematology, etc? Similarly, a set of ECG mappings for QT studies, another for holter monitoring, etc?
§Notes: The lab CT team will tackle one lab test at a time to sort out what units apply; therefore, still 1 CT mapping; the SHARE dev team is okay with a rolling spreadsheet with mappings
●From listening to the CT meeting on Friday, 2014-07-18:
oMethods for VS tests: Are the methods “extensible”? [Context: Mapping attributes]
§Notes: Doesn’t really apply. It all depends on the codelist themselves
oSME may benefit from being able to review the list on the METHOD codelist so that they can pick (check) codes that apply per test
§SHARE has this functionality; can demo
●Notes: Defer tool usability

Action Items