This page is part of the National Directory of Healthcare Providers and Services (NDH) Implementation Guide (v1.0.0-ballot: STU1 Ballot 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/us/ndh/ValueSet/EndpointConnectionTypeVS | Version: 1.0.0-ballot | |||
Active as of 2023-07-30 | Computable Name: EndpointConnectionTypeVS |
Endpoint Connection Types
References
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/endpoint-connection-type
http://hl7.org/fhir/us/ndh/CodeSystem/EndpointConnectionTypeCS
This value set contains 20 concepts
Expansion based on:
Code | System | Display | Definition |
dicom-wado-rs | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | DICOM WADO-RS | DICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html |
dicom-qido-rs | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | DICOM QIDO-RS | DICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html |
dicom-stow-rs | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | DICOM STOW-RS | DICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.6.html |
dicom-wado-uri | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | DICOM WADO-URI | DICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html |
hl7-fhir-rest | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | 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. |
hl7-fhir-msg | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | 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. |
hl7v2-mllp | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | HL7 v2 MLLP | HL7v2 messages over an LLP TCP connection |
secure-email | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | 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 |
direct-project | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | Direct Project | Direct Project information - http://wiki.directproject.org/ |
cds-hooks-service | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | 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 |
hl7-fhir-opn | http://hl7.org/fhir/us/ndh/CodeSystem/EndpointConnectionTypeCS | HL7 FHIR Operation | Interact with a FHIR server interface using FHIR's RESTful interface using an operation other than messaging. For details on its version/capabilities you should connect the value in Endpoint.address and retrieve the FHIR CapabilityStatement. |
rest-non-fhir | http://hl7.org/fhir/us/ndh/CodeSystem/EndpointConnectionTypeCS | REST (not FHIR) | Interact with a server using HTTP/REST but not FHIR. Should be used for web portals. |
ihe-xcpd | http://hl7.org/fhir/us/ndh/CodeSystem/EndpointConnectionTypeCS | IHE XCPD | IHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community_Patient_Discovery |
ihe-xca | http://hl7.org/fhir/us/ndh/CodeSystem/EndpointConnectionTypeCS | IHE XCA | IHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access |
ihe-xdr | http://hl7.org/fhir/us/ndh/CodeSystem/EndpointConnectionTypeCS | IHE XDR | IHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterprise_Document_Reliable_Interchange |
ihe-xds | http://hl7.org/fhir/us/ndh/CodeSystem/EndpointConnectionTypeCS | IHE XDS | IHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing |
ihe-iid | http://hl7.org/fhir/us/ndh/CodeSystem/EndpointConnectionTypeCS | IHE IID | IHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display |
ihe-pdq | http://hl7.org/fhir/us/ndh/CodeSystem/EndpointConnectionTypeCS | IHE PDQ | IHE Patient Demographics Query (PDQ) - http://wiki.ihe.net/index.php/Patient_Demographics_Query |
ihe-pix | http://hl7.org/fhir/us/ndh/CodeSystem/EndpointConnectionTypeCS | IHE PIX | IHE Patient Identity Feed (PIX) - http://wiki.ihe.net/index.php/Patient_Identity_Feed |
ihe-mhd | http://hl7.org/fhir/us/ndh/CodeSystem/EndpointConnectionTypeCS | IHE MHD | IHE Mobile Healthcare (MHD) - http://wiki.ihe.net/index.php/Mobile_Healthcare |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |