Stream: implementers
Topic: DetectedIssue v/s Condition for representing certain events
Deepak Choudhary (Sep 29 2020 at 11:30):
For the following scenario as an example, is the DetectedIssue resource more appropriate than the Condition resource, or there's another better way of representing it per FHIR?
- An episode of Hypoglycemia (a condition) occurs due to the patient skipping a meal or high dose on insulin.
- This episode/event is supported by some symptoms like Hunger, Headache, etc. and by the Blood Glucose observation.
- Then the patient drinks a glass of juice - which resolves the event.
In essence we need to represent the Event, Evidence [Cause & Symptoms] and Resolution.
Now, as you can imagine this can be represented by the condition resource IF, we add the custom component of how it was resolved to it.
On the other hand, the DetectedIssue does already provide us the "mitigation" component, but the DetectedIssue code doesn't seem appropriate to capture such an event.
Lloyd McKenzie (Sep 29 2020 at 13:00):
DetectedIssue represents a warning about a potential contraindication. Condition is generally used for monitoring and tracking a long-term state. A single episode of hypoglycemia would typically be captured as Observation. However, if you're wanting to capture mitigating actions and resolution, you could also look to AdverseEvent.
Last updated: Apr 12 2022 at 19:14 UTC
