Skip to main content
Advanced Search
Search Terms
Content Type

Exact Matches
Tag Searches
Date Options
Updated after
Updated before
Created after
Created before

Search Results

142 total results found

Bouwblok service discovery

Actiz architectuurwerkgroep

Resultaat van een eerste schets sessie: Inventarisatie van rollen, processen, systemen en transacties. Rollen Zorgtoepassingdeelnemer De deelnemer is in het algemeen is het de rechtspersoon die verantwoordelijk is voor het naleven van de afspraken van de zorgt...

OAuth2 Scopes and Presentation Definition Mapping

Designing a Nuts Use Case Authorization

Scope design When designing a system that uses OAuth2, you have to decide how scopes map to resources that the client will attempt to access. "Resource access" is typically a specific REST-style HTTP operation on a specific URL, e.g. POST /products/staplers/1...

OAuth2 Flows and Wallets

Designing a Nuts Use Case Authorization

Nuts supports a custom OAuth2 flow for acquiring an access token: the service-to-service flow. Service-to-Service flow Credentials that are presented during this flow are subject to legal organizations (e.g. registered care organizations). This flow uses a cus...

AuthN using Verifiable Credentials

Designing a Nuts Use Case Authorization

To successfully negotiate an OAuth2 access token, the token issuer (OAuth2 Authorization Server) will ask the client to present Verifiable Credentials. Nuts uses DIF Presentation Exchange for requesting and presenting credentials during authentication. It's us...

Credential Trust

Designing a Nuts Use Case Authorization

Authentication on Nuts heavily depends on trusted credential issuers: any attribute, relevant to the security model of the use case should be verifiable. E.g., if a party claims to be a care organization, it should be able to present a Verifiable Credential to...

Service Discovery

Designing a Nuts Use Case

A party often exchanges data through its API endpoints. If a client only has the party's name or identifier, it needs to find the API endpoints. Service Discovery via the Nuts node let clients find involved parties and additional information, like API endpoint...

Toegangscontrole met Verifiable Credentials

Solution Architecture

Een solution architectuur voor het implementeren van ABAC gebaseerd op attributen verkregen via SSI. Maakt gebruik van OpenID4VP, DIDs, VCs, FHIR en OPA. Introductie Voor succesvolle gegevens uitwisseling in de zorg zijn een heel aantal (technische) stappen no...

Lokalisatie in netwerkzorg hoogover

Lokalisatie

Status: concept. Deze pagina wordt momenteel niet verder uitgewerkt of gebruikt. Zie voor lokalisatie de generieke functie Lokalisatie van het Ministerie van VWS. Context Binnen netwerkzorg is vaak bekend wie de andere behandelaren zijn. Dit kan worden geïnven...

Notified Pull gebaseerd op FHIR subscriptions

Communicatiepatronen

Achtergrond Het Notified Pull (NP) communicatiepatroon stelt een initiatiefnemer in staat gegevens gericht aan te bieden aan een raadpleger. De raadpleger wordt hiervan op de hoogte gebracht via een notificatie. De Pull operatie kan meerdere keren worden uitge...

Zorginzage V6 hackathon spec

Samenwerken Huisarts en Thuiszorg

Status: historical. Hackathon spec from 2024, replaced by Zorgtoepassing: HA-VVT inzage dossier v1.1. This document is in DRAFT Purpose The purpose of the hackathon is to demonstrate a simple implementation of Nuts Zorginzage in Nuts V6. The present Nuts Zorgi...

Access Policy

Designing a Nuts Use Case Authorization

Anti-patterns Bad: "Clients can update the FHIR resource at /Task/ using an HTTP PUT, but only the status field. HTTP PUT is a replace operation, which requires the Policy Decision Point to verify whether delta of the update only updates the status field, whic...

Install the use case's configuration files

Implementing a Nuts v2 Use Case Configure the node for a use case

A use case gives you two kinds of configuration files. Your Nuts node needs both, for every use case you join. File What it tells your node Directory setting Discovery Service definition Where the use case's Discovery Service is, and which credentials a care o...

Request an access token

Implementing a Nuts v2 Use Case Outbound: querying another party

To query another care organization's API, you need an access token from that organization's authorization server. Your Nuts node requests it for you: it shows the authorization server the credentials the use case requires. Before you start You found the other ...

V6 configuration without V5 features

Cookbook

The configuration below shows a minimal nuts.yaml config file: did:nuts disabled, did:web enabled discovery refresh of 1 minute for faster discovery during development default mappings for discovery and policy files (mounts required) SQLite will be used as D...

Obtaining credentials

Implementing a Nuts v2 Use Case Set up a care organization

Some use cases require credentials besides the X509Credential. Check the use case's Discovery Service and policy definitions to see which credentials you need. Credential types are defined in the credential catalog. 360-graden-clientbeeld No other credentials ...

Validate the access token

Implementing a Nuts v2 Use Case Inbound: handling queries

When another care organization queries your FHIR API (or other data API), the request carries an access token your Nuts node issued. Your API (or the API gateway in front of it) must check that token on every request, then decide whether to allow the query. Th...

UZI certificates as a source of identity

Authenticatie

UZI certificates from CIBG can back Verifiable Credentials. The credential is signed with the UZI private key, and its issuer is a did:x509 DID derived from the certificate. This reuses CIBG's identity checks instead of setting up new issuers. It breaks a chi...

Notulen bijeenkomsten

Samenwerken Huisarts en Thuiszorg

Google doc