This code system http://terminology.hl7.org/CodeSystem/endpoint-connection-type defines the following codes: Code Display Definition ihe-xcpd IHE XCPD IHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community_Patient_Discovery ihe-xca IHE XCA IHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access ihe-xdr IHE XDR IHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterprise_Document_Reliable_Interchange ihe-xds IHE XDS IHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing ihe-iid IHE IID IHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display dicom-wado-rs DICOM WADO-RS DICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html dicom-qido-rs DICOM QIDO-RS DICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html 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 dicom-wado-uri DICOM WADO-URI DICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html 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. 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. hl7v2-mllp HL7 v2 MLLP HL7v2 messages over an LLP TCP connection 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 direct-project Direct Project Direct Project information - http://wiki.directproject.org/
This is an example codesystem defined by the FHIR project, that could be used to represent possible connection type profile values.
IHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community_Patient_Discovery
IHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access
IHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterprise_Document_Reliable_Interchange
IHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing
IHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display
DICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html
DICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html
DICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.6.html
DICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html
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.
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 messages over an LLP TCP connection
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 information - http://wiki.directproject.org/