OHDSI Home | Forums | Wiki | Github

DataQualityDashboard checkNames parameter

Developers
#1

I need to run something like:

checkNames ← c(measurePersonCompleteness,
cdmField, isRequired, cdmDatatype,
isPrimaryKey, isForeignKey, fkDomain,
fkClass, isStandardValidConcept, measureValueCompleteness,
standardConceptRecordCompleteness, sourceConceptRecordCompleteness,
sourceValueCompleteness, plausibleValueLow, plausibleValueHigh,
plausibleTemporalAfter, plausibleDuringLife, plausibleValueLow, plausibleValueHigh, plausibleGender)

Is this ok? or should I use
checkNames ← c(“measurePersonCompleteness”,
“cdmField”, “isRequired”, “cdmDatatype”,
“isPrimaryKey”, “isForeignKey”, “fkDomain”,
“fkClass”, “isStandardValidConcept”, “measureValueCompleteness”,
“standardConceptRecordCompleteness”, “sourceConceptRecordCompleteness”,
“sourceValueCompleteness”, “plausibleValueLow”, “plausibleValueHigh”,
“plausibleTemporalAfter”, “plausibleDuringLife”, “plausibleValueLow”, “plausibleValueHigh”, “plausibleGender”)

I believe it is the second one but I need to be sure

#2

It is indeed the second, the checkNames are strings. All supported checks can be found here (human readable) and here (machine readable). We might want to think about implementing a getCheckNames function in a new version of DQD.

By the way, it seems you are listing all available checks. If you want to run all checks, you don’t need to provide the checkNames parameter at all when executing DQD.

t