Search Results

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 id...

Within this volume the transactions that are used for the use case Advance Care Planing are described. Publish ACP data source to NVI Later. not in scope for September 2025 hackathon Search ACP data source at NVI Later. not in scope for September 2025 hackatho...

De zorgtoepassing PZP gebruikt als content onderstaande zibs, FHIR-profielen en EHR-archetypen. Dit artikel is een beknopte weergave van hoofdstuk 3.3 uit de Afsprakenset Proactieve Zorgplanning PZP Coalitie. De Afsprakenset Proactieve Zorgplanning PZP Coaliti...

Version 2025-07-04 Status draft Introduction This techincal agreements descibes how health organizations should be identified in the context of data exchanges. Agreements Decision Health organizations are identfied using URA-number (UZI-Register ...

Version 2025-07-04 Status draft Introduction This techincal agreements descibes how vendor organizations should be identified in the context of data exchanges. Agreements Decision Vendor organizations are identfied using KvK-number (Kamer van Koo...

Version 2025-07-04 Status draft Introduction This techincal agreements descibes how professionals should be identified in the context of data exchanges. Agreements Decision 1 Professionals are identfied using local employee number Rationale All ...

Version 2025-07-04 Status draft Introduction This technical agreement descibes how vendor organizations should be authenticated in the context of data exchanges. Agreements Decision Vendor organizations are authenticated on the network level usin...

Version 2025-07-04 Status draft Introduction This technical agreement descibes how health organizations should be authenticated in the context of data exchanges. Agreements Decision Health organizations are authenticated using a X509credential ba...

Version 2025-07-04 Status draft Introduction This technical agreement descibes how professionals should be authenticated in the context of data exchanges. Agreements Decision 1 Professionals are "authenticated" (it is probably better ot refer to ...

to do

to do

Version 2025-07-04 Status draft Introduction This technical agreement descibes how incoming requests must be authorized in the context of data exchanges. Agreements Decision 1 Authorization rules are technically defined using access policies writ...

Version 2025-07-04 Status draft Introduction This technical agreements descibes the needed technical agreements for the use of local explicit consent by data holders. Agreements Decision 1 Data holders are free to implement local explicit consent...

This document describes how to issue the X509Credential for a UZI server certificate, used to authenticate in several applications on Nuts/ use cases. Introduction Several applicatopns-on-nuts specify that care organizations are authenticated using a Verifiabl...

First, a new identity, with associated DID, needs to be created for the tuple (organization, environment). Log in to the organization’s Nuts Admin application. Click on “Identities”. Click on the plus sign on the right side. Enter the subject: it consists of ...

Using Nuts Admin application: Log in to the care organization’s Nuts Admin application. Click on “Identities”. Click on the wallet to load the credential into (there should be only one). Click on “Load Credential”. Enter/paste the credential in the input fiel...

Before another party can interact with you, they will first need to find your endpoints. The discovery service in the Nuts node helps you. Via Nuts admin to do Via API: POST /internal/discovery/v1/<servicedefinition-id>/<subject-id> { "registrationParameter...