Search Results

A technical support role is all about running the OS reference implementation within a certain (cloud) infrastructure. As technical support specialist you know everything there is to know about the OS reference implementation: the APIs logging metrics securit...

We're all Documentation Specialists! Documentation is all about knowledge sharing. For it to be available we just have to make sure that we have a place to put it and we take the time to do it. There are three main locations where knowledge can be found: the N...

As a Nuts journalist, your role will be pivotal in shaping our online presence and public messaging. You will be responsible for crafting and curating engaging and tantalizing content that highlights our innovative work in healthcare technology. This role invo...

As a System Architect, your primary role will be to serve as a consultant, providing guidance and expertise to various parties involved in the implementation of Nuts technology. Your responsibilities will include: Document examples on how to incorporate Nuts ...

(nog te verplaatsen naar wiki) Project brief Werkafspraken inspiratie Kunnen we onze specificaties publiceren als een FHIR Implementation Guides?

Google doc

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

Nuts SSIBAC Een solution architectuur voor het implementeren van ABAC gebasseerd op attributen verkregen via SSI. Maakt gebruik van OpenID4VP, DIDs, VCs, FHIR en OPA. NOTE: vanwege limitaties van aanroepen OPA vanuit andere sources dan nginx en aanroep naar OP...

The configuration below show a minimal nuts.json 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 DB...

The first thing you need to do is create some public/private key material for your subjects. We use the term subjects for everything related to vendors, tenants, organizations and clients. Behind every subject there can be multiple DIDs (decentralized identifi...

After you created a subject with some DID documents, it's time to give meaning to these identifiers. Without Verifiable Credentials, DIDs are just useless identifiers. They receive meaning when another party issues credentials to one of those DIDs. Attestation...

Before another party can interact with you, they will first need to find your endpoints. The discovery service in the Nuts node can help you. The Nuts node can act as both server and client. From a use case definition you'll receive the following information/f...

You can find participants of a use case via their registered services. A use case defines the service identifier and which credentials are required through the presentation definition. Any constraint in the presentation definition with an identifier can also b...

After finding a service endpoint to interact with, it's time to request an access token. You can request one via your own Nuts node: POST /internal/auth/v2/my_subject_identifier/request-service-access-token { "authorization_server": "https://example.com/oau...

When a request comes in at your resource endpoint, an access token should be available in the HTTP Authorization header. You can validate the token by calling: POST /internal/auth/v2/accesstoken/introspect token=ciOiJSUzI1NiIsInR5cCI6Ikp Note: the content-ty...

When updating your node from V5 to V6, you can choose to disable/enable certain parts depending on your needs. The common paragraph describes the required configuration changes. Common Before you update, make a backup and check the diagnostics of your node. To...

It's possible to downgrade an v6.0.0 node back to v5.4.x. You'll also need to reset your configuration. The SQL database you configured for V6 can be removed. DID documents are still changed after the downgrade with the controller field removed.

When you upgrade from V5 to V6, your DID documents will be migrated to a SQL database. A new VDR V2 API has also been added. It's no longer possible to set a controller on a DID document. All DID Documents are self-controlled. It's also no longer possible to f...

Together with V6 comes a new understanding of how data exchange should be secured across organization boundaries. Some of the concept, promoted by Nuts in the past, are no longer viable or don't make any sense anymore. V6 supports alternatives or this wiki des...