A medication code may sit where CMTRTCD now belongs

Rule

VAR-031

Category

Variables added

Basis

Confirmed Traceable to the published specification text cited below.

Detectability

Define-XML heuristic The Define-XML indicates this, but does not prove it. Treat the finding as a prompt to check, not as a verdict.

Finding type

Opportunity

Applies to

SDTMIG 3.2, 3.3, 3.4

What changes in v4.0

v4.0 adds CMTRTCD (Standardized Medication Code, Char, Permissible) to Concomitant/Prior Medications, and Appendix E describes --TRTCD as "the variable for the code associated with --DECOD". Before v4.0 the WHODrug code that pairs with CMDECOD had no standard column, and sponsors who kept it commonly kept it as a supplemental qualifier. This study's Define-XML declares a QLABEL naming a drug, ATC or medication code, and this CM dataset declares no CMTRTCD, so the content CMTRTCD was added for appears to exist in the structure v4.0 is decommissioning.

What to do about it

Optional. If the supplemental qualifier holds the code associated with CMDECOD, CMTRTCD is where v4.0 puts it, and the move is cheaper as part of the SUPP-to-NS conversion than as a separate exercise later. Confirm which dictionary and version the code came from while you are there — that belongs in the Define-XML external codelist metadata rather than in the variable. If the QNAM holds something else, a local formulary code or a sponsor identifier, leave it where it is: a name match is not a mapping.

What the scan can and cannot see

A QLABEL naming a drug, ATC or medication code is a proxy for what the supplemental dataset holds. It may name something else entirely, and a declared QNAM is not a populated one. Both caveats are why this is heuristic rather than conclusive.