Search Results

Google doc

Introduction This articles specifies version 2 of the Nuts-application-specification "eOverdracht" of which version 1.0 is published on: Leveranciersspecificatie. This article describes the necessary changes to version 1.0 to make eOverdracht work using did:we...

Een beschrijving van de GF lokalisatie

WIP! BZ: moeten we de drie verschillende momenten los uitwerken? Dus 1) inzage (bij spoed/ambu/OHCA bijv), 2) overdracht (bij veranderen van zorgorganisatie of lijn, bijv thuiszorg naar Hospice of oncoloog naar huisarts en wijkverpleging) of 3) samenwerking (...

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 Search ACP data source at NVI Token request Search ACP resources

De zorgtoepassing PZP gebruikt als content onderstaande zibs, FHIR-profielen en EHR-archetypen. Zorginformatiebouwstenen to do FHIR resources en queries Hieronder staan de endpoints die beschikbaar gesteld moeten worden door de partijen die optreden als bronho...

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