Stream: implementers
Topic: Condition end without abatement
Kirstine Rosenbeck Gøeg (Jun 08 2020 at 11:27):
I am trying to design Conditions in a way, so that they only "appear"/"are active", when they are actually a problem, that some organization is responsible for. When a condition is no longer a problem for the patient, the Condition resource states that I may set an abatement-date or set the status to one of codes that signify that the Condition is inactive.
However, what to do when the Condition is no longer handled in my organisation? E.g. I send a ServiceRequest to someone else to handle the condition, and then I want to "end it" in my record system - not because it is better, but because I do not want it to appear as an active problem in my organisational context.
I do realize, that it does not necessarily makes sense from a patient record perspective to "end" the condition, because it is actually probably still there, and at least, the last version was correct at the time of registration. My problem is that I don't have a way to distinguish "problems that my organisation is responsible for" from "problems that my organisation is not responsible for (any more)". Suggestions?
I could search for conditions that are used as "reasons" for my organsations active CarePlans, but I would prefer a solution that was not dependent on other resources.
Lloyd McKenzie (Jun 08 2020 at 14:31):
The intention is that this is managed by the List resource. Each organization (or even each practitioner) can have their own problem List. The gynecologist doesn't necessarily care about your dental issues and your psychiatrist doesn't necessarily care about your podiatry issues. The List resource provides a filtered view of all of the Conditions that are 'relevant' for that organization/practitioner. (The fact something is no longer 'active' wouldn't necessarily cause it to be dropped from the 'concern' list.)
Last updated: Apr 12 2022 at 19:14 UTC
