The rule CT1023 - "Value for --SEV not found in (SEV) CT codelist" is enabled into config-send-3.0.xml for most of the domains, including CL (for CLSEV).
However, into the SENDIGv3.pdf standard the CLSEV variable is not controlled by any Terminology (SENDIGv3.pdf - page 70). Other --SEV variables (MASEV, MISEV) variables are controlled by the CL.C90000.SEV Terminology list.
Should rule CT1023 be disabled for CL, to reflect the SENDIGv3.pdf standard?
Or can we assume that the CDISC team missed to specify the Controlled Terminlogy list for CLSEV in their standard and therefor keep in config-send-3.0.xml the CT1023 validation rule for CLSEV?
Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.
The rule CT1023 - "Value for --SEV not found in (SEV) CT codelist" is enabled into config-send-3.0.xml for most of the domains, including CL (for CLSEV).
However, into the SENDIGv3.pdf standard the CLSEV variable is not controlled by any Terminology (SENDIGv3.pdf - page 70). Other --SEV variables (MASEV, MISEV) variables are controlled by the CL.C90000.SEV Terminology list.
Should rule CT1023 be disabled for CL, to reflect the SENDIGv3.pdf standard?
Or can we assume that the CDISC team missed to specify the Controlled Terminlogy list for CLSEV in their standard and therefor keep in config-send-3.0.xml the CT1023 validation rule for CLSEV?
Thanks!