Open MelaniePhilofsky opened 1 year ago
Has a solution for this been discussed/fixed?
No, it needs a sponsor to take it through the Themis process found on the home page of this Git
Consensus recommendations from the Vocabulary WG that were collectively voted for (recording here):
Keep one race and ethnicity (if present) in race_concept_id and ethnicity_concept_id in PERSON table Keep all additional races and ethnicities and/or any longitudinal changes in OBSERVATION table. Provenance of the record can be captured through observation_type_concept_id. ETLers chose which race to put in OBSERVATION themselves and which date to used based on their knowledge of the data.
Vocabularies do not deduplicate races to allow greater flexibility given lack of consensus in terms. One can add other races and ethnicities to the OHDSI Vocabularies as long as they are not full duplicates of existing races.
No flavors of NULL are permitted, as usual. If race is unknown or not reported it is 0.
Tagging @cgreich to finalize the details.
Мakes sense to me. Let's build the vocabulary from the various national sources, and let's write up the Themis convention about the various scenarios (more than one race, mixed race, race changing over time).
For cases where there are >1 race or ethnicity, how do you pick which one is privileged and goes into the person table?
An alternative would be to not choose, and use 0.
The proposal gives the ETLer the authority to chose the race that goes to person/observation based on their unique expertise in local data.
Hello @clarkevans,
Themis needs to finalize the details, document the conventions and publish them. Let me put this topic on the Themis WG agenda. I'll announce it on the OHDSI forums and MS Teams.
From this forum post.