Stream: implementers
Topic: Care Plan Phases
Martin Grundberg (Feb 08 2022 at 15:51):
We are about to represent standardized care plans (patient instances of them) for cancer in an overview.
From the healthcare professionals point of view it is very important to understand in which phase the plan is in. For cancer there are different deparmtents and different KPIs involved in the diagnostic phase (before a confirmed diagnosis and a decision to treat) than after the treatment starts. Hence, we have use cases like:
- See all patients on a cancer pathway undergoing diagnostics
- See all patients on a cancer pathway that have started treatment
There is a CarePlan.status, but that seems more oriented towards whether the plan is active or completed. We would like something like a CarePlan.phase.
We could see it being a codeableConcept with cardinality 0..1.
Any thoughts on how to solve this requirement? We can obviously always add an extension, but if that is the way, maybe we should add a jira ticket to add this to the CarePlan resource if others agree it belongs there?
Thoughts?
Jose Costa Teixeira (Feb 08 2022 at 16:22):
You can use a Task. Task supports business statuses which seems to be (related to) what you're looking for
Jose Costa Teixeira (Feb 08 2022 at 16:24):
This goes back to the early discussions on Task and some F2F (we were happy then and we didn't realize it) that if a Task represents "something that is to be done", then a Task can be divided by Task.
Jose Costa Teixeira (Feb 08 2022 at 16:25):
so I think I'd start looking at Task for that
Lloyd McKenzie (Feb 08 2022 at 17:48):
Actually, I would use CarePlan.category. The purpose of category is to allow grouping and filtering of plans that fall into the same 'bucket', and the notion of 'phase' seems like it would correspond to that.
Last updated: Apr 12 2022 at 19:14 UTC
