Replies: 1 comment 13 replies
-
|
Hi @lrasmus, I'm glad those scripts have been useful and that's totally fine. @artgoldberg and I and others have discussed strategies for diagnoses a bit and I think many have questions similar to this. My personal opinion is that users are >90% of the time going to be much more comfortable using and interpreting ICD{9|10} codes rather than SNOMED, given widespread use in EHRs and billing, etc. Given that there there are also far less ICD-10 codes than SNOMED, for example, it's also more compact and presumably easier to navigate than a SNOMED hierarchy, potentially. Given those assumptions, we haven't found a nice one-size-fits-all solution as different sites have different preferences and may populate their OMOP DBs differently, for example using SNOMED vs. ICD-10 for concept mapping, and populating the @lrasmus in your OMOP DB, how are you populating conditions? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Thanks so much for the excellent leaf-scripts for OMOP. I am sorry to ask for 'more, more, more', but before working on this myself I was wondering if anyone had created a Leaf Concept hierarchy for OMOP Conditions? Given that OMOP relies on SNOMED for conditions, I was curious in part of any SNOMED-based hierarchy for conditions is the best way to go, or if using an ICD-based hierarchy is better.
Happy to contribute back anything we create if a solution doesn't already exist.
Beta Was this translation helpful? Give feedback.
All reactions