EHR Archetype for Recording a patient's death

Birger Haarbrandt birger.haarbrandt at plri.de
Wed Feb 3 05:39:35 EST 2016


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.


Am 03.02.2016 um 11:35 schrieb Diego Boscá:
> I was going to point you there :)
>
> 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).
>
> 2016-02-03 11:25 GMT+01:00 Birger Haarbrandt <birger.haarbrandt at plri.de>:
>> Ah, sorry, never mind! Just found the recent thread (at first glance, I
>> didn't think that it would addresses this question)
>>
>> :)
>>
>> Birger
>>
>> Am 03.02.2016 um 11:18 schrieb Birger Haarbrandt:
>>
>> Hi there,
>>
>> 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?
>>
>> Regards,
>>
>> --
>> Birger Haarbrandt, M.Sc.
>>
>> Peter L. Reichertz Institut für Medizinische Informatik
>> Technische Universität Braunschweig und
>> Medizinische Hochschule Hannover
>> Mühlenpfordtstraße 23
>> D-38106 Braunschweig
>>
>> T +49 (0)531 391-2129
>> F +49 (0)531 391-9502
>> birger.haarbrandt at plri.de
>> http://www.plri.de
>>
>>
>>
>> --
>> Birger Haarbrandt, M.Sc.
>>
>> Peter L. Reichertz Institut für Medizinische Informatik
>> Technische Universität Braunschweig und
>> Medizinische Hochschule Hannover
>> Mühlenpfordtstraße 23
>> D-38106 Braunschweig
>>
>> T +49 (0)531 391-2129
>> F +49 (0)531 391-9502
>> birger.haarbrandt at plri.de
>> http://www.plri.de
>>
>>
>> _______________________________________________
>> openEHR-clinical mailing list
>> openEHR-clinical at lists.openehr.org
>> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org


-- 
*Birger Haarbrandt, M.Sc.*

Peter L. Reichertz Institut für Medizinische Informatik
Technische Universität Braunschweig und
Medizinische Hochschule Hannover
Mühlenpfordtstraße 23
D-38106 Braunschweig

T +49 (0)531 391-2129
F +49 (0)531 391-9502
birger.haarbrandt at plri.de
http://www.plri.de

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20160203/47991ff9/attachment-0002.html>


More information about the openEHR-clinical mailing list