Replies: 1 comment 1 reply
-
You're right - we can do better here. Condition.category is only set when US Core is enabled (which it is by default) but we always set it to "encounter-diagnosis". That's fine for most of the Conditions in Synthea, but for these SDoH type conditions there are more appropriate options. From the US Core IG perspective, these could be “problem-list-item” or “health-concern” as you note, or from the SDOH Clinical Care (ie, Gravity) perspective these could fall into one of their categories: Because category is 0..* we could even use multiple at a time. Things get a little tricky as we try to support different versions of US Core but we can definitely improve this. |
Beta Was this translation helpful? Give feedback.
-
I am looking at some recent data I generated with Synthea and noticing that a high percentage of Conditions generated seems to be SDOH-related.
These all have Condition.category = encounter-diagnosis.
Primary question:
Should these use a different Condition category (problem-list-item, health-concern, or one of the SDOH profile values) ?
Secondary question:
Is it realistic to have so much of this data? I generated 20k patients, and around 50% of the Conditions generated are not what OMOP/OHDSI consider to be in the SNOMED "condition" domain. I'd agree these factors are important, but it surprised me to see so much of it.
Here is a listing of all the generated condition codes for one sample patient to illustrate the prevalence of these:
Beta Was this translation helpful? Give feedback.
All reactions