SUPPQUAL – Where’s My Mommy? Sandra VanPelt Nguyen Midwest CDISC Users Group May 2012

Abstract When using CDISC standards, there may be situations in which a field has been collected on a CRF or included in a vendor data transfer which seems to be clinically relevant but is not “topic” data belonging in a standard or custom SDTM domain (any of the three general observation classes). Since non-standard variables cannot be added to SDTM domains, this data typically gets mapped to a SUPPQUAL (Supplemental Qualifiers) dataset, but what do we do when there is not an obvious “parent” record corresponding to this data within one of the SDTM domains? This presentation will provide a set of guidelines to use to determine how best to handle these situations.

Discussion Topics ► Introduction/Background ► Guidelines ► Examples © All rights reserved.3

Intro to Supplemental Qualifiers (SUPPQUAL) ► CDISC SDTM organizes data in domains (datasets) based on topic ► Topics are divided amongst 3 general domain classes - Interventions, Events, Findings ► Topics which do not fall into a reserved SDTM domain but fit into a general domain class may go into custom domains ► Variables cannot be added to domains with exception of certain timing, identifier and qualifier variables allowable within the general domain class ► SDTM allows for the inclusion of additional variables using the Supplemental Qualifiers special-purpose domain

Intro to Supplemental Qualifiers (SUPPQUAL) ► SUPPQUAL is used to capture non-standard variables and their association to parent records in general observation class datasets or DM (demographics) ► QNAM (qualifier variable name) and QLABEL (qualifier variable label) are used to describe the particular qualifier ► Variables IDVAR (identifying variable) and IDVARVAL (identifying variable value) provide the linkage between records (qualifier child to observation(s) parent) by identifying the variable to join on and the variable value of the specific record(s) which are related ► SUPPQUAL is typically split as SUPP--, with the suffix based on the related domain’s code, e.g. SUPPAE for qualifiers related to the AE domain

SUPPQUAL Example © All rights reserved.6 CMTRTReported Name of Drug, Med, or Therapy CMCATCategory for Medication CMINDCIndication CMDOSEDose per Administration CMDOSTXTDose Description CMDOSUDose Units CMSTDTCStart Date/Time of Medication CMENDTCEnd Date/Time of Medication CMLOCLocation of Dose Administration CMTRT CMSTDTC CMENDTC CMLOC CMDOSE/CMDOSTXT CMDOSU

SUPPQUAL Example: Parent-Child Relationship USUBJIDCMSEQCMTRTCMDOSECMDOSUCMLOCCMSTDTCCMENDTC ABC PALLIATIVE RADIATION68GyPROSTATE CM: SUPPCM: USUBJIDRDOMAINIDVARIDVARVALQNAMQLABELQVAL ABC CMCMSEQ1REASDISCReason for DiscontinuationCompleted therapy

SUPPQUAL Example: No Parent USUBJIDCMSEQCMTRTCMDOSECMDOSUCMLOCCMSTDTCCMENDTC ABC PALLIATIVE RADIATION68GyPROSTATE ABC PALLIATIVE RADIATION72GyPROSTATE CM: SUPPCM: USUBJIDRDOMAINIDVARIDVARVALQNAMQLABELQVAL ABC CMCMSEQ2REASDISCReason for DiscontinuationCompleted therapy NO MATCH ON USUBJID, CMSEQ SD0078: Referenced record not found

SUPPQUAL Example: No Parent SUPPCM: USUBJIDRDOMAINIDVARIDVARVALQNAMQLABELQVAL ABC CMREASDISCReason for DiscontinuationCompleted therapy What to do when you do not know what to use for IDVAR/IDVARVAL?

Sample CRF

Mapping Guidelines 1. Does the data belong in a general observation class domain? 2. Is there a not-so-obvious parent? 3. Is the data actually needed? 4. Time to get creative

Applying the Guidelines – Example 1 (1) Does the data belong in a general observation class domain? (2) Is there a not-so- obvious parent? (3) Is the data actually needed? Time to get creative!

Applying the Guidelines – Example 1

Applying the Guidelines – Example 2 (1) Does the data belong in a general observation class domain?

Applying the Guidelines – Example 2

Applying the Guidelines – Example 3 (1) Does the data belong in a general observation class domain? (2) Is there a not-so- obvious parent?

Applying the Guidelines – Example 3

Applying the Guidelines – Example 4 (2) Is there a not-so- obvious parent? (1) Does the data belong in a general observation class domain?

Applying the Guidelines – Example 5 (2) Is there a not-so- obvious parent? (1) Does the data belong in a general observation class domain? (3) Is the data actually needed?

Applying the Guidelines – Example 5

Applying the Guidelines – Example 6 (3) Is the data actually needed? Time to get creative! (1) Does the data belong in a general observation class domain? (2) Is there a not-so- obvious parent?

Applying the Guidelines – Example 6

Conclusion ► Be on the lookout for possible “lost children” when annotating and creating mapping specifications. ► Be mindful of the intent and relevance of the data. ► Consider how/if the information will be used for review or analysis. ► Determine the best fit within the SDTM standard.

© All rights reserved. 24 Thank you Sandra VanPelt Nguyen