Hi Jean,
If there are more than one Origin for the variable, you need to specify them using Value Level metadata.
See SDTM example in CDISC define.xml v2.0 standard package. QVAL variable in most SUPP-- domains has different Origin.
You need to define some condition (WhereClause) for each unique Origin. Sometimes a usage of additional variables like --SPID or --GRPID can be helpful.
Kind Regards,
Sergiy
Hi Sergiy,
Is there a way to keep multiple origins in variable level alone or in both variable level and value level?
It’s a lot more convenient to have multiple origins all together, especially for some important variables from main domains.
Kind Regards,
Lenny
Hi Lenny,
The only supported way of having multiple origins in Define-XML v2 is, like Sergiy mentioned, to have value level metadata. The Origin/@Type attribute only allows one value. Unfortunately, neither the XML schema nor OpenCDISC checks for this rule, or even for the allowed values. However, the specification is normative, and is clear about this. This will be fixed in the Define-XML v 2.1 schema.
In Define-XML clear interoperability and being machine readable is considered of higher importance than convenience.
In the Define-XML v2.1 development team we will further discuss origin metadata.
Would you be willing to further describe your use case? Do you have a variable that you can use to build the WhereClauseDef to distinguish multiple Origin/@Type values?
Regards,
Lex Jansen (CDISC Define-XML Development Team)
I’m curious about how to handle this situation as well. What happens if the origins cannot be distinguished by another variable? For instance, I have more than one origin for DSDECOD within single values of DSCAT. The only variable that I think might distinguish the origin is MODULE, however I’m not sure qualifying an Expected variable with a Supplemental variable is the right way to go. Any advice?
Cheers,
David.
David,
Thanks for the feedback.
I understand your concern. I agree that there would be situations where the documentation of multiple orgins would not be helped very much by introducing a non-standard variable, just for the sake of distinguishing multiple origins.
Let me take that to the Define-XML dev team.
Lex
Hi,
When the “CRF” was combined with other ORIGIN values (e.g. “eDT, CRF”), then link of CRF page(s) wasn’t developed correctly.
Is there any specific format in spec for the multiple “origin” metadata or is it a limitation of opencdisc-community to generate define.xml?
Thanks for your help in advance.