Sequoia Project Healthcare Directory Implementation Guide
0.0.10 - CI Build
Sequoia Project Healthcare Directory Implementation Guide - Local Development build (v0.0.10). See the Directory of published versions
Official URL: https://sequoiaproject.org/fhir/sphd/ValueSet/EndpointConnectionType | Version: 0.0.10 | |||
Active as of 2023-05-03 | Computable Name: EndpointConnectionType |
Codes used in Endpoint.connectionType
References
This value set includes codes based on the following rules:
https://sequoiaproject.org/fhir/sphd/CodeSystem/EndpointConnectionType
This value set contains 13 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 |
Ihe-xca-i | https://sequoiaproject.org/fhir/sphd/CodeSystem/EndpointConnectionType | IHE XCA-I | IHE Cross-Community Access for Imaging (XCA-I) - https://wiki.ihe.net/index.php/Cross-Community_Access_for_Imaging |
ihe-xcdr | https://sequoiaproject.org/fhir/sphd/CodeSystem/EndpointConnectionType | IHE XCDR | IHE Cross-Community Document Reliable Interchange (XCDR) - https://wiki.ihe.net/index.php/Cross-Community_Document_Reliable_Interchange_(XCDR) |
ihe-xds-i.b | https://sequoiaproject.org/fhir/sphd/CodeSystem/EndpointConnectionType | IHE XDS-I.b | IHE Cross-Enterprise Document Sharing for Imaging (XDS-I.b) - https://wiki.ihe.net/index.php/Cross-enterprise_Document_Sharing_for_Imaging |
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 |