OHDSI Home | Forums | Wiki | Github

Why no marital_status field in person table?

estimationmethods
patientprediction
atlas
cdm
vocabularies

(Akshay Kumar) #1

Hello Everyone,

I am trying to understand why the OMOP CDM person table doesn’t have a marital_status column?

Is it not really useful for observational research?


Using the CDM for Multiple Randomized Trials
(Christian Reich) #2

The PERSON table contains constant information about a person. ID, birthday, gender, race, that kind of thing. It’s not perfectly so, but that’s the model. While the spouses come and go, at least for some people. Information that is fluid like that goes into the OBSERVATION table. There you can store marital status no problem.


(Vojtech Huser) #3

Well, we could use the ONE AND ONLY marital standard concept.
See query here
https://athena.ohdsi.org/search-terms/terms?invalidReason=Valid&standardConcept=Standard&page=1&pageSize=15&query=marital+status&boosts

LOINC, SNOMED and ALL-OF-US

and phenx inside LOINC

Nice example of some syntax standardization but still no “deep standardization”. So we have OMOP as syntax but it still leaves room for a “semantic mess”.

Looking at value sets for LOINC (another PPI “duplication” here)

for SNOMED - no value sets defined.

for PhenX (not a very good set)

Looking more at SNOMED - going up from married to
https://athena.ohdsi.org/search-terms/terms/4076095 (e.g., engaged) (more granular)

The only way to decide a winner is by OHDS ConceptPrevalence network study. Let the collective vote and judgement of sites decide the winner.


t