Shared Care Planning (SCP) Implementation Guide - Local Development build (v0.2.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Transactions - Creating and responding to a Task

For adressing: make use of a (nation wide) database where you can find healthcareservices and or organizations that you are looking for. Tip: implement/use a Care Service Discovery that conforms to the IHE mCSD profile

For resolving a FHIR-endpoint for a specific healthcareservice/organization, multiple service discovery methods could be used (NUTS en/of GF Adressering)

To avoid losing data during update, actors MUST support the directives in transactional integrity and concurrency

[!IMPORTANT] This transaction will involve notification of the Task. Depending on the usecase, this might include sending/pushing PHI to other parties. The sending party must verify that the endpoint to which the data is sent, is under control of the intended recipient party.

Trigger Events

geen; handmatig?

Scope

Actor Roles

Interactions

Sequence diagram

Profiles

Task profile met verplichte referentie naar CarePlan in .BasedOn en request in .focus ??? Constraints zetten op referentie naar .owner (moet opgehaald kunnen worden door CPS). TODO: refer to used profiles (FHIR structure definitions generated on page 'Artifacts')