Stream: Care Plan/Care Coordination
Topic: CarePlan activity detail - kind
Petter Wolff (Nov 30 2020 at 10:07):
Why does CarePlan.activity.detail.kind have a Required valueset, a valueset that contains the very generic 'Task' alongside the quite more specific 'VisionPrescription', for example? I can understand if you want to restrict ActivityDefinition.kind (which by the way has similarities, but seems to have been more curated by actual needs from the community) to be able to run $apply in a somewhat standardized way (but even then, it should probably be better to use Extensible instead?). But for a CarePlan, to even try to restrict the various 'kinds' of activities that can be tracked in a plan (or having the guts to deem oneself able to make a perfect choice)...? Not sure about the logic there, to say nothing about the random-looking selection of codes.
Lloyd McKenzie (Nov 30 2020 at 18:27):
The list of codes are the list of possible FHIR resources
Petter Wolff (Dec 03 2020 at 10:35):
Thanks Lloyd - which kind of use case is envisioned where 'kind' is used to describe inline (i.e. CarePlan.detail) attributes of the activity, in the form of a resource?
I also think it seems limiting for the use of the quite generic term 'kind'. The term should specify better the intended use, no?
Lloyd McKenzie (Dec 03 2020 at 15:45):
@Bryn Rhodes
Bryn Rhodes (Dec 08 2020 at 14:50):
If you need something more than can be specified with the inline information in the detail element, you would use the reference to the resource, rather than specifying it inline in the CarePlan at all.
Last updated: Apr 12 2022 at 19:14 UTC
