Stream: Care Plan/Care Coordination
Topic: Is Detail Useful
Jay Lyle (Jan 29 2021 at 20:35):
Care Plan includes references to a variety of request activities, but it also has a “detail” structure for codes, reasons, performers, etc. that can be used if you have the data fields but not the resource.
Is that actually helpful? If you don’t have the ServiceRequest resource in your repository, but you do have a procedure code, is it much easier to put that in the backbone element than to instantiate a contained ServiceRequest?
Neither backbone nor contained resource can be identified or given provenance. It was suggested that you can’t search on a contained resource, but the Detail elements aren’t in the Search Parameters. Should Detail be removed so we can reduce the number of structures a recipient needs to understand?
Lloyd McKenzie (Jan 29 2021 at 21:33):
It was more a question of providing a minimum set of data that 'simple' systems could support without taking on the complexity of all of the full-blown resources. It's not really a question of external reference vs. internal - as you're correct that you can easily capture all of the request resources as contained if you need to.
Jay Lyle (Jan 31 2021 at 22:03):
That's my understanding, but the only property the "full blown" service request requires that is not required by Detail is intent. Which seems important.
Lloyd McKenzie (Jan 31 2021 at 22:07):
The detail within CarePlan would always have the same intent as the CarePlan itself.
Bryn Rhodes (Sep 08 2021 at 20:09):
For the projects I've been involved in, we never use detail, we always model activities with Request resources and the fulfilling Event resources.
Last updated: Apr 12 2022 at 19:14 UTC
