At the end of last Tuesdays discussion, regarding some "a bit special" SEND rules, I promised to write something down about having additional functions/operations to retrieve information from the CDISC Library. Here it comes ...
I think it is unclear how "variable_library_metadata" works. I think only "core" works well at the moment. If there are other ones, then they are not well documented though ...
It think it is better to have specific functions, extending the current "library_xxx" ones. A few suggestions:
library_variable_has_associated_codelist
boolean: returns whether the variable has an associated codelist according to the CDISC Library
library_variable_associated_codelist_name
string: returns the name of the associated codelist according to the CDISC Library (e.g. "LBTESTCD")
library_variable_associated_codelist_code
string: returns the CDISC-NCI code of the associated codelist according to the CDISC Library
library_variable_associated_codelist_terms
array: returns the values of the associated codelist according to the CDISC Library
P.S. This requires the codelist version to be available / passed to the function
library_variable_codelist_extensible
boolean: returns whether the associated codelist (if any) is extensible according to the CDISC Library
library_variable_exists_in_IG
boolean: returns whether the variable is in the Implementation Guide (for the given domain) for the current standard and IG version according to the CDISC Library
library_variable_exists_in_model
boolean: returns whether the variable is in the underlying model for the current standard and IG version according to the CDISC Library.
P.S. I think this overlaps with the existing operator "get_parent_model_column_order"
Remark that the function names are purely first suggestions ...
We can also discuss next "office hours" on Tuesday.
At the end of last Tuesdays discussion, regarding some "a bit special" SEND rules, I promised to write something down about having additional functions/operations to retrieve information from the CDISC Library. Here it comes ...
I think it is unclear how "variable_library_metadata" works. I think only "core" works well at the moment. If there are other ones, then they are not well documented though ...
It think it is better to have specific functions, extending the current "library_xxx" ones. A few suggestions:
Remark that the function names are purely first suggestions ... We can also discuss next "office hours" on Tuesday.