This fragment is not visible to the reader
| Type | Reference | Content |
|---|---|---|
| web | github.com | Netherlands - Generic Functions for data exchange Implementation Guide, published by Nuts. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/nuts-foundation/nl-generic-functions-ig/ and changes regularly. See the Directory of published versions |
| web | www.nuts.nl |
IG © 2024+ Nuts
. Package fhir.nl.generic-functions-ig#0.1.0 based on FHIR 4.0.1
. Generated 2025-09-03
Links: Table of Contents | QA Report |
| web | github.com | Open issues are discussed/located on the Github repository |
| web | github.com | Date: 2025-07-24, Source code |
| web | santeonnl.github.io | An important consideration was that the Shared Care Planning initiative already uses CarePlan and CareTeam resources to manage the care network of a patient. Since NVI has a different goal and scope, using different resources would avoid semantic conflicts by not overloading the same entities (CarePlan and CareTeam) with different meanings in different contexts. For instance, SCP chooses to have one single CarePlan/CareTeam resource and add the Organizations as members. The SCP also manages Tasks, which NVI will never support. |
| web | github.com | For implementing NVI (Network of Involved Care Providers - see detailed description ), we have chosen to use a simple JSON-based REST API instead of FHIR resources. This decision was made to simplify the implementation and reduce complexity while still meeting the core requirements of tracking which organizations have data about a patient in specific care contexts. |
| web | editor.swagger.io | The NVI API is defined using OpenAPI 3.0.2 specification (you may render this using swagger.editor.html ). The API provides a straightforward interface for managing the network of involved care providers using standard REST operations. |