You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'd like to build a concept set for RA, but exclude juvenile concepts. This is proving hard to accomplish, as many juvenile RA ICD10CM codes are mapped to both a juvenile RA standard concept (4253901) and to a standard concept that conveys the location of the RA (e.g. elbow, shoulder, etc).
So in practice, though we exclude the juvenile RA standard concept, we still get the mapped juvenile ICD10CMs associated due to their other standard concept mapping. It appears either SNOMED needs to add some permutations of juvenile RA plus RA affected area, or we need to, via a SNOMED Extension.
Hi @alondhe - I picked a random ICD10CM code for juvenile RA + location and the location part is only mapped to Disorder of joint of ankle and/or foot. That one should work, right? Is that a model that we should try to align with?
Just curious (and not being a data scientist), while I agree that it could be nicer to have that sorted out in mapping, isn't there a way to exclude patients in the analysis explicitly that also have a juvenile RA?
Hello,
We'd like to build a concept set for RA, but exclude juvenile concepts. This is proving hard to accomplish, as many juvenile RA ICD10CM codes are mapped to both a juvenile RA standard concept (4253901) and to a standard concept that conveys the location of the RA (e.g. elbow, shoulder, etc).
So in practice, though we exclude the juvenile RA standard concept, we still get the mapped juvenile ICD10CMs associated due to their other standard concept mapping. It appears either SNOMED needs to add some permutations of juvenile RA plus RA affected area, or we need to, via a SNOMED Extension.
I am raising this issue here and Git.
Tagging @cgreich @mik-ohdsi
Thanks,
Ajit
The text was updated successfully, but these errors were encountered: