endpoint-connection-type
type: CodeSystem
node role: treeRoot
id:
  v: endpoint-connection-type
text:
  status:
    v: generated
  div: 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…
extension:
  extension:
    url:
      v: packageId
    value: id
      v: hl7.fhir.uv.xver-r4b.r4
  extension:
    url:
      v: version
    value: string
      v: 0.0.1-snapshot-2
  url:
    v: http://hl7.org/fhir/StructureDefinition/package-source
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
  value: code
    v: pa
url:
  v: http://terminology.hl7.org/CodeSystem/endpoint-connection-type
version:
  v: 4.3.0
name:
  v: EndpointConnectionType
status:
  v: draft
experimental:
  v: false
date:
  v: 2025-09-13T16:38:45-04:00
publisher:
  v: Patient Administration
contact:
  name:
    v: Patient Administration
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/pafm
description:
  v: This is an example codesystem defined by the FHIR project, that could be used to represent possible connection type profile values.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
    code:
      v: 001
    display:
      v: World
case sensitive:
  v: true
content:
  v: complete
concept:
  code:
    v: ihe-xcpd
  display:
    v: IHE XCPD
  definition:
    v: IHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community_Patient_Discovery
concept:
  code:
    v: ihe-xca
  display:
    v: IHE XCA
  definition:
    v: IHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access
concept:
  code:
    v: ihe-xdr
  display:
    v: IHE XDR
  definition:
    v: IHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterprise_Document_Reliable_Interchange
concept:
  code:
    v: ihe-xds
  display:
    v: IHE XDS
  definition:
    v: IHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing
concept:
  code:
    v: ihe-iid
  display:
    v: IHE IID
  definition:
    v: IHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display
concept:
  code:
    v: dicom-wado-rs
  display:
    v: DICOM WADO-RS
  definition:
    v: DICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html
concept:
  code:
    v: dicom-qido-rs
  display:
    v: DICOM QIDO-RS
  definition:
    v: DICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html
concept:
  code:
    v: dicom-stow-rs
  display:
    v: DICOM STOW-RS
  definition:
    v: DICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.6.html
concept:
  code:
    v: dicom-wado-uri
  display:
    v: DICOM WADO-URI
  definition:
    v: DICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html
concept:
  code:
    v: hl7-fhir-rest
  display:
    v: HL7 FHIR
  definition:
    v: 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.
concept:
  code:
    v: hl7-fhir-msg
  display:
    v: HL7 FHIR Messaging
  definition:
    v: 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.
concept:
  code:
    v: hl7v2-mllp
  display:
    v: HL7 v2 MLLP
  definition:
    v: HL7v2 messages over an LLP TCP connection
concept:
  code:
    v: secure-email
  display:
    v: Secure email
  definition:
    v: Email delivery using a digital certificate to encrypt the content using the public key, receiver must have the private key to decrypt the content
concept:
  code:
    v: direct-project
  display:
    v: Direct Project
  definition:
    v: Direct Project information - http://wiki.directproject.org/