sub care plans

[joostholslag]

In my experience as a doctor and clinical modeller the care team depends on the topic of the care plan. So different topics lead to different care teams. e.g. a nurse can be involved in the diabetes care plan, but not in the depression care plan. So a care team membership because of involvement in diabetes care shall not lead to an authorisation for the depression related data. https://github.com/SanteonNL/shared-care-planning/blob/main/input/pagecontent/introduction.md implies there will be only one care team per patient. My solution was to model sub care plans (plan elements) as self standing artefacts, and have an 'overarching/main' care plan that indexes the relevant sub care plans for a given audience.

[bramwesselo]

Yeah, we more or less also ended up at your solution; the CarePlan as mentioned in SCP is an overarching 'network-careplan'; it will not contain every action for the patient as multiple organizations might have their own careplan (locally known as e.g. episode, DBC or any other condition/treatment related container-object) where actions are registered. Ideally, these local careplans are referring to the SCP-careplan.

Still, the SCP-Careplan should be some conditions. If diabetes and depression are related conditions, the SCP-careplan should refer both.

[joostholslag]

To me the main point is the care team may differ per condition. So if you want to deduce authorisations from a care plan with a care team, you must have a care plan with care team per condition.