Oh, I thought it was going to become a standard concept, so Colorado preemptively coded the discharged to morgue/expired records as such. Oops!
the new type_concept_id will cover @ericaVoss use case for CDM v5.*
V6 Death is problematic because there isn’t a type_concept_id associated with the Person.death_date in v6. If the death record lacks a cause of death, a Condition Occurrence record, there won’t be any type_concept_id associated with the death. Source provenance is an important aspect of the CDM.
! If you want to see it that way then indeed we should put in the Visit “morgue” as @Vojtech_Huser suggested. Followed by “Purgatory” and “Hell” or “Heaven”. We also need a one-day “Judgement Day” Visit.
But if we want to let these people rest in peace let’s not. The Visit has nothing to do with death. The fact that somebody died we already have - in the PERSON table. Why do you so badly want to repeat it?
It makes analysis easier especially if you want to know if they expired during a hospitalization rather then checking dates. I think discharged to “morgue” is a good compromise Again, I’m not saying that this replaces death in the person table or death table, but in addition. Plus, there would be a DQD check to confirm the information is aligned.
I am following this discussion from the sideline, two things as a suggestion:
should a dischargeto concept not belong in the CMS/place of service vocab or similar? a discharge status is more patient-centred, but would not fit in the same ‘domain’ as “other hospital” “nursing facility”, “hospice”, or indeed “morgue”, “coronar”, “funeral director/undertaker/mortician”.
as to the question of repeating: in v5 it seems that the death_type_concept_id column in the death table is sufficient to capture a hospital-recorded death, also if there is no death certificate or so available. However, in version6 there is no mechanism yet for representing information in an EHR that a person is dead without any further knowledge about cause of death and/or precise info about date and time etc.
Or is there? The CDM-documentation indicates that such a statement should be captured in the Observation table. A record with concept_id 434489 = dead and concept_type_id =32823 - EHR discharge record should work, right? Using the discharge date as the date of observation would generally fit very well with common EHR habits in point.
Which one? What’s the use case that forces us to record it that way?
Seriously, @Karthik? The entire OMOP CDM model relies on date relationships. The source data often don’t give us reliable cross-references. We don’t even know if procedures, drugs and devices belong to a visit explicitly in many cases. And now you want to have one special situation just for death, and only for one Visit (Inpatient)? How do you intend to make people familiar with that kind of a unique exception?
Look: I know where this is coming from. Folks in the EPIC EHR have a “discharge_disposition” field and want that field back with an entry “expired”, because they are used to it. That does not count as a use case. The clause “where death_date>=visit_start_date and death_date<=visit_end_date” is not too much to ask.
The Place of Service notion was retired a while ago. It is a crude mix of different things, and outside the USA with its quasi-standardization through the CMS it makes no sense. We now have Visit concept. They define the setting healthcare is delivered, who comes to whom in which environment, what is the level of service. Death is not a healthcare setting. It’s the opposite.
V6 has Person.death_datetime and the cause of Death can be recorded in the Condition_Occurrence table with a condition_type_concept_id = EHR record or Death Certificate, etc. and the condition_status = 32891, Cause of Death.
Your suggestion would work, but I believe the provenance should belong with the record in the CDM, as we do for all other clinical event records. Consistency or a convention to explain why we are not being consistent
FYI concept_id = 434489 has a domain_id = Condition, so this record would live in the Condition_Occurrence table.