Shared Care Planning (SCP) Implementation Guide
0.2.0 - ci-build
Shared Care Planning (SCP) Implementation Guide, published by Santeon. This guide is not an authorized publication; it is the continuous build for version 0.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/santeonnl/shared-care-planning/ and changes regularly. See the Directory of published versions
Shared Care Planning (SCP) is about sharing healthcare data in the context of a patient's care plan. The care organizations involved in SCP participate with a role in SCP to share information between organizations as part of the treatment of the patient. The assumptions of the privacy model are:
Both the patient and practitioner need to give consent to the exchange of information. The consent of the patient should be requested by the practitioner and recorded in the health care system. Upon enrolling a patient for a use case of SCP, the practitioner provides consent by this action. SCP requires the health care professional to have an active user session where the health care professional is authenticated authorized to initiate such an action. The authentication and authorization credentials MUST be provided to the systems involved in the translation. See the section about trust form more details.
The access to data in SCP is limited based access policies that apply in the context of data access. The SCP authorization specification makes distinction access policies:
The SCP makes use of Verifiable Credentials (VCs) and Verifiable Presentations (VPs) as building blocks of Trust over IP to build a hierarchy of trust that creates the fundamentals for data exchange. The main principles are that:
The section on authentication describes this subject in more detail.
Shared Care Planning