Netherlands - Generic Functions for data exchange Implementation Guide
0.10.0 - ci-build
Netherlands - Generic Functions for data exchange Implementation Guide
0.10.0 - ci-build
Netherlands - Generic Functions for data exchange Implementation Guide - Local Development build (v0.10.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: http://minvws.github.io/generiekefuncties-docs/ValueSet/nl-gf-connection-types-vs | Version: 0.10.0 | ||||
| Active as of 2026-07-15 | Computable Name: NlGfConnectionTypesVS | ||||
Authorization and endpoint connection type codes supported by NL Generic Functions.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
This value set includes codes based on the following rules:
http://minvws.github.io/generiekefuncties-docs/CodeSystem/nl-gf-authorization-server-cs version 📦0.10.0http://vzvz.nl/fhir/CodeSystem/koppeltaal-endpoint-connection-type version 📦0.10.0
| Code | Display | Definition |
| hti-smart-on-fhir | HTI SMART on FHIR | Endpoint uses the HTI SMART on FHIR connection type. |
Expansion performed internally based on:
This value set contains 19 concepts
| System | Code | Display (en) | Definition | status | JSON | XML |
http://minvws.github.io/generiekefuncties-docs/CodeSystem/nl-gf-authorization-server-cs | oauth2 | OAuth 2.0 | Endpoint uses OAuth 2.0 authorization framework. | |||
http://minvws.github.io/generiekefuncties-docs/CodeSystem/nl-gf-authorization-server-cs | oauth2-fapi2 | OAuth 2.0 FAPI 2 | Endpoint uses OAuth 2.0 with Financial-grade API (FAPI) 2 security profile requirements. | |||
http://minvws.github.io/generiekefuncties-docs/CodeSystem/nl-gf-authorization-server-cs | oauth-nuts | OAuth 2.0 NUTS | Endpoint uses OAuth 2.0 with NUTS-based trust and authentication profile constraints. | |||
http://vzvz.nl/fhir/CodeSystem/koppeltaal-endpoint-connection-type | hti-smart-on-fhir | HTI SMART on FHIR | Endpoint uses the HTI SMART on FHIR connection type. | |||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | dicom-wado-rs | DICOM WADO-RS | DICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html | |||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | dicom-qido-rs | DICOM QIDO-RS | DICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html | |||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | dicom-stow-rs | DICOM STOW-RS | DICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.6.html | |||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | dicom-wado-uri | DICOM WADO-URI | DICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html | |||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | hl7-fhir-rest | HL7 FHIR | Interact with the server interface using FHIR's RESTful interface. For details on its version/capabilities you should connect the value in Endpoint.address and retrieve the FHIR CapabilityStatement. | |||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | hl7-fhir-msg | HL7 FHIR Messaging | Use the servers FHIR Messaging interface. Details can be found on the messaging.html page in the FHIR Specification. The FHIR server's base address is specified in the Endpoint.address property. | |||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | hl7v2-mllp | HL7 v2 MLLP | HL7v2 messages over an LLP TCP connection | |||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | secure-email | Secure email | Email delivery using a digital certificate to encrypt the content using the public key, receiver must have the private key to decrypt the content | |||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | direct-project | Direct Project | Direct Project information - http://wiki.directproject.org/ | |||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | cds-hooks-service | CDS Hooks Service | A CDS Hooks Service connection. The address will be the base URL of the service as described in the CDS specification https://cds-hooks.hl7.org | |||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | ihe-xcpd | IHE XCPD | IHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community_Patient_Discovery | deprecated | ||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | ihe-xca | IHE XCA | IHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access | deprecated | ||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | ihe-xdr | IHE XDR | IHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterprise_Document_Reliable_Interchange | deprecated | ||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | ihe-xds | IHE XDS | IHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing | deprecated | ||
http://terminology.hl7.org/CodeSystem/endpoint-connection-type | ihe-iid | IHE IID | IHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display | deprecated |