7 - Transfering Responsibility : Use Case diagram
Responsibility is registered on multiple levels in the Infrastructure.<br/>Changing responsibility is supported on some of the levels:<br/><b><br/></b><b>The EpisodeOfCare's careManagerOrganization</b> <br/>This is the Organization that has the formal responsibility for the Patient's care. It can change but it does not have any impact on the security for the underlying resources.<br/><br/><b>The EpisodeOfCare's team</b><br/>This team is for Practitioners with the rights to assign new CarePlans to the Patient's EpisodeOfCare.<br/>Examples include: Behandlingsansvarlig and Administrativt Personale<br/><br/>This team can be changed with the right permissions. The History of the responsibility is kept in EpisodeOfCare.teamHistory.<br/><b><br/></b><b>The Careplan's careTeam</b><br/>This operational team is for Practitioners with rights to monitor the execution and progress of the Patient's CarePlan. It is also for clinical practitioners who adjust plans and approve results for publishing.<br/>Examples include Sundhedsfaglig and Sundhedsfaglig monitoreringsansvarlig<br/><br/>Likewise, operational teams can include Practitioners with service and support roles.<br/><br/>CareTeam on CarePlans change. The history is kept CarePlan.ehealth-teamHistory<br/><b><br/></b><b>Non-transferable responsibility:</b><br/>The EpisodeOfCare.managingOrganization is the top level Organization that holds the data responsibility. It never changes. Setting a new data responsible for Patient resources, like CarePlans, requires creating a new Episode of Care.<br/>
Created: 28/01/2020 00.00.00
Modified: 19/03/2020 15.25.35
ID: {DEEA03EC-9BC6-4bdc-B522-955379473C0C}
Link to this Diagram