Thanks to @Ajit_Londhe’s fix, I was able to run the DQ Dashboard on our CDM instance. One of the first things I noticed was that the plausibleGender checks flagged a pretty substantial error:
For a CONCEPT_ID 197605 (Inflammatory disorder of male genital organ), the number and percent of records associated with patients with an implausible gender (correct gender = Male). (Threshold=5%).
In investigating a bit further, I found that these were mostly source records with an ICD-9 code of 616.9 (Unspecified inflammatory disease of cervix, vagina, and vulva). In ETLing our old ICD-9 data into the CDM, we use the mappings in CONCEPT_RELATIONSHIP, which, it seems, is what threw this issue, as 616.9 maps to the SNOMED code referenced in the DQ check error message:
select * from FULL_OMOP.dbo.CONCEPT_RELATIONSHIP cr join FULL_OMOP.dbo.CONCEPT c on c.concept_id = cr.concept_id_1 where concept_id_2 = '197605'
@Dymshyts and other Athena folks, is this mapping functioning as intended? Any thoughts on how to preserve the gender-specific nature of these ICD-9 codes and avoid throwing DQ errors?