PZP Volume 2a - Technical Agreements
This volume describes the technical side of the agreements to realize data availability for the use case Advance Care Planning. This volume provides the technical agreement needed for transmitting the data between parties. Technical agreements are made on
-
identifying health organizations
-
identifying vendors
-
identifying professionals
-
authenticating vendors & health organizations
-
authenticating professionals
-
localization
-
addressing
-
data request
Exchange pattern: indexed pull
Due to the nature of the use case, the exchange pattern is indexed pull. In short this means that fetching data globally consists of two steps: Localization
: Localising the data holders (via one or more indices) and then Data request
: actually reuqesting the data at each known data holder.
Identifying health organizations
The use case Advance Care Planning makes use of the generic technical agreement Identifying health organisations.
Identifying vendor organizations
The use case Advance Care Planning makes use of the generic technical agreement Identifying vendor organisations.
Identifying professionals
The use case Advance Care Planning makes use of the generic technical agreement Identifying professionals.
Authenticating health organisations
The use case Advance Care Planning makes use of the generic technical agreement Authenticating health organisations.
Authenticating vendor organizations
The use case Advance Care Planning makes use of the generic technical agreement Authenticating vendor organizations.
Authenticating professionals
The use case Advance Care Planning makes use of the generic technical agreement Authenticating professionals.
Localization
TOThe DOuse Jorrit:case BeschrijfAdvance verhaalCare lokalisatiePlanning viadoes CareTeamnot enmake optioneeluse of a generic technical agreement.
The use case Advance Care Planning uses the following technical agreements:
Lokaliseerbaar
Make maken:data localisable:
- MUST:
IedereEveryzorgorganisatiehealthcarehoudtorganisationzelfmaintainseenaCareTeamCareTeam-resourcebijpermetpatientdethatbijcontainshemallbekendeknownandereinvolvedzorgorganisatiesrelevant healthcare organizations - MUST: For testing purposes the facilitators of the test make sure that the NVI is filled
- SHOULD:
VoorVendortestthatzorgenwishwetoervoordodatso can register the CareTeams with the NVIeen(specifications)
Localise:
- MUST: Get URA’s from data holders from local CareTeam
- SHOULD:
Leveranciers- Send
datbsnwillen gaan de CareTeams aanmelden bij deto NVI - receice 1 or more URA's from data holders that host a CareTeam
- fetch at least 1 CareTeam-resource
die - Send
Addressing
Lokaliseren:The use case Advance Care Planning does not make use of a generic technical agreement. The use case Advance Care Planning uses the following technical agreements:
Publish addresses
- SHOULD:
StuurRegisterbsnatnaarNutsDiscoveryServiceNVIwith SHOULD:X509CredentialHaalandminimaalDiscoveryRegistrationCredential1containingCareTeamaopfhirBaseUrl-elemement.- MUST:
HaalPartiesURA’sthatuitchooseCareTeamnot to register at the NutsDiscoveryService themselves are registered at the NutsDiscoveryService via a hack - MUST: make sure you know the fhir base urls of other parties in some way (this can also be done via a local list)
Retrieve addresses
- MUST: make sure you know the fhir base urls of other parties in some way (this can also be done via a local list)
Authorization
The use case Advance Care Planning makes use of the generic technical agreement Authorizing incoming requests.
Legal basis: local explicit consent
The use case Advance Care Planning makes use of the generic technical agreement Local explicit consent.
Data request
In some contexts this is referred to as Pull
.
TO DO jorrit