FHIR Chat · How to capture deceased reason · implementers

Stream: implementers

Topic: How to capture deceased reason


view this post on Zulip Stuart Cox (Feb 19 2021 at 00:30):

What is the best and/or most widely adopted way to record the date and reason code for a patient's death or cause of death in FHIR R4? Obviously we have Patient.deceased[x], but waht about the reason for death. Condition? AdverseEvent?

I found a link that referred to condition-outcome extension, but was wondering if there is a more standard way to record it that would not require an extension. Any JSON examples would be helpful as well.

view this post on Zulip Stuart Cox (Feb 19 2021 at 00:51):

Also found a cause of death profile ballot. But again, looking for most widely adopted way to record this.

https://trifolia-fhir.lantanagroup.com/igs/lantana_hapi_r4/vrdr/StructureDefinition-VRDR-Cause-Of-Death-Condition.html

view this post on Zulip Lloyd McKenzie (Feb 19 2021 at 01:00):

Cause of death would typically be an Observation. It's an assertion made at a particular point in time by a particular individual. (It's possible different assertions might be made at different times or by different people.)

view this post on Zulip Stuart Cox (Feb 19 2021 at 14:20):

Thank you @Lloyd McKenzie. Makes sense, and like that no special extensions or profiles are needed.

view this post on Zulip Lin Zhang (Feb 19 2021 at 15:57):

Just for a joke:
Observation looks like a powerful extension-killer:big_smile:

view this post on Zulip René Spronk (Feb 19 2021 at 15:58):

Was that an observation ? ;-)


Last updated: Apr 12 2022 at 19:14 UTC