n Narae
on

 

Hello,

 

I'm working on creating Define.xml for SDTM. In codelist, I know "Decoded value" should be used as the NCI Preferred Term of CT.

However, I want to change Decoded value text different to NCI Preferred Term.

 

CDISC Submission Value of Code(C49568) is CM and NCI Perferred Term is "Concomitant Medication Domain". However, SDTM domain label and CRF Page name in my study is "Concomitant/Prior Medications".

So I wrote decode value as "Comcomitant/Prior Medications" of Code(C49568).

In other case, NCI Preferred Term of NOT RECOVERED/NOT RESOLVED (C49494) is "Not Recovered from Adverse Event". But I collected "Not recovered/resolved" in CRF. So I wrote decode value as "Not recovered/resolved" 

 

I wonder if it's possible and what the best practice is for writting the decode value as either the NCI Preferred Term or the Display Term in CRF.

 

 

 

Forums: Define.xml

j Jozef
on May 9, 2024

Is there a specific reason why you want to do it? By changing the "decode", you are essentially changing the meaning of the coded value ...
BTW, I never assign subset-codelists to domains ("DOMAIN" variable) in SDTM. That doesn't make sense, as the "coded" and "decoded" value are already in the domain name and domain label. So why need to repeat it in a subset codelist that only contains 1 term?

For "NOT RECOVERED/NOT RESOLVED", this is published by CDISC as an "Enumerated Item", i.e. there is no decode (one could also say that code and decode are identical.

You say that "I know "Decoded value" should be used as the NCI Preferred Term of CT", but if you use the ODM files published by CDISC, you always immediately have what you need - no need at all for Excel. Best is to NOT use the Excel files at all. The same applies to constructing define.xml. There are much better tools that do not use Excel, the latter always leading to problems ("black box process").

CDISC-CT

IF you absolutely want to change the "decode", just open your define.xml in e.g. NotePad++, and change it there.

m MinJi
on May 9, 2024

Hi, 

First, please check which version of define.xml is generated. There is a define.xml guideline depending on the version.

And, the guideline will include answers to your questions.

 

Refer to the below:

According to the guidance of define.xml v2.1, 

 

1. About domain decoded values:

In cases where SAS Transport files are the transport format, the value provided in the ItemGroupDef element should match the dataset label provided in the SAS Transport file.

-> Because SDTM CM domain label "Concomitant/Prior Medications" is identical to decoded value as well as CDISC Synonym, you wrote it correctly. 

 

2. About variable decoded values:

The Decode values shown here are taken from the CDISC Synonym field in the CDISC Controlled Terminology publication. The implementation guides for some CDISC standards may recommend use of specific Decode values. In other cases, the choice of the decode is at the sponsor's discretion

->  Collected data in CRF ("Not recovered/resolved" ) is okay to be stated in decode value and it seems to be more specific.

 

I hope it helps you.

 

Best regards,

MinJi

j Jozef
on May 10, 2024

Just to get a few things straight here ...
The Define-xml guidance is mentioned, but ...
1. "In cases where SAS Transport files are the transport format ...".
This has nothing to do with code/decode. That section is about labels for the datasets (not domains), which go into ItemGroupDef/Description/TranslatedText. That is something completely different.
2. "The Decode values shown here are taken from the CDISC Synonym field ...".
That sentence is taken from an example. It is not guidance.

Want a demo?

Let’s Talk.

We're eager to share and ready to listen.

Cookie Policy

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.