In our operative note document we have a data element to record the decease of a patient during a surgical operation. At our first try, we modelled “time of death” as a single Element to make it fit into a particulare section on the document. However, it feels wrong as I think that the death of a patient is a concept on its own that will be reused in many scenarios and that might need further data elements. In the CKM, there is only the death data archetype (which is a CLUSTER in the Demographic Model) which is not feasible for our use-case.
Is there a reason why such a prominent concept as “death” has not been modeled as EHR archetype?
Anyway, I believe that probably is related to "full" archetypes vs
summary archetypes: There will be detailed archetypes for any given
documentable clinical practice (in this case, explaining everything
related to the death of a patient) and there will be other use cases
where this information is just needed as a quick summary (e.g. date of
death).
Thanks, Diego! How would these different kind of archetypes relate to each other? When querying the database, I'd like to make sure to find all data elements of the concept death by using the path of exactly one archetype.
