Release 4B Ballot #1

This page is part of the FHIR Specification (v4.1.0: Release 4B Ballot #1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3

Codesystem-endpoint-connection-type.xml

Patient Administration Work GroupMaturity Level: N/AStandards Status: Informative

Raw XML (canonical form + also see XML Format Specification)

Definition for Code System EndpointConnectionType

<?xml version="1.0" encoding="UTF-8"?>

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="endpoint-connection-type"/> 
  <meta> 
    <lastUpdated value="2021-03-11T17:06:20.662+11:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> This code system http://terminology.hl7.org/CodeSystem/endpoint-connection-type defines
         the following codes:</p> 
      <table class="codes">
        <tr> 
          <td style="white-space:nowrap">
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">ihe-xcpd
            <a name="endpoint-connection-type-ihe-xcpd"> </a> 
          </td> 
          <td> IHE XCPD</td> 
          <td> IHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community
            _Patient_Discovery</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">ihe-xca
            <a name="endpoint-connection-type-ihe-xca"> </a> 
          </td> 
          <td> IHE XCA</td> 
          <td> IHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">ihe-xdr
            <a name="endpoint-connection-type-ihe-xdr"> </a> 
          </td> 
          <td> IHE XDR</td> 
          <td> IHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterpri
            se_Document_Reliable_Interchange</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">ihe-xds
            <a name="endpoint-connection-type-ihe-xds"> </a> 
          </td> 
          <td> IHE XDS</td> 
          <td> IHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Documen
            t_Sharing</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">ihe-iid
            <a name="endpoint-connection-type-ihe-iid"> </a> 
          </td> 
          <td> IHE IID</td> 
          <td> IHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">dicom-wado-rs
            <a name="endpoint-connection-type-dicom-wado-rs"> </a> 
          </td> 
          <td> DICOM WADO-RS</td> 
          <td> DICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/se
            ct_6.5.html</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">dicom-qido-rs
            <a name="endpoint-connection-type-dicom-qido-rs"> </a> 
          </td> 
          <td> DICOM QIDO-RS</td> 
          <td> DICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_
            6.7.html</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">dicom-stow-rs
            <a name="endpoint-connection-type-dicom-stow-rs"> </a> 
          </td> 
          <td> DICOM STOW-RS</td> 
          <td> DICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtm
            l/part18/sect_6.6.html</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">dicom-wado-uri
            <a name="endpoint-connection-type-dicom-wado-uri"> </a> 
          </td> 
          <td> DICOM WADO-URI</td> 
          <td> DICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">hl7-fhir-rest
            <a name="endpoint-connection-type-hl7-fhir-rest"> </a> 
          </td> 
          <td> HL7 FHIR</td> 
          <td> 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.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">hl7-fhir-msg
            <a name="endpoint-connection-type-hl7-fhir-msg"> </a> 
          </td> 
          <td> HL7 FHIR Messaging</td> 
          <td> 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.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">hl7v2-mllp
            <a name="endpoint-connection-type-hl7v2-mllp"> </a> 
          </td> 
          <td> HL7 v2 MLLP</td> 
          <td> HL7v2 messages over an LLP TCP connection</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">secure-email
            <a name="endpoint-connection-type-secure-email"> </a> 
          </td> 
          <td> Secure email</td> 
          <td> Email delivery using a digital certificate to encrypt the content using the public key,
             receiver must have the private key to decrypt the content</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">direct-project
            <a name="endpoint-connection-type-direct-project"> </a> 
          </td> 
          <td> Direct Project</td> 
          <td> Direct Project information - http://wiki.directproject.org/</td> 
        </tr> 
      </table> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="pa"/> 
  </extension> 
  <url value="http://terminology.hl7.org/CodeSystem/endpoint-connection-type"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.1.1140"/> 
  </identifier> 
  <version value="4.1.0"/> 
  <name value="EndpointConnectionType"/> 
  <status value="draft"/> 
  <experimental value="false"/> 
  <description value="This is an example codesystem defined by the FHIR project, that could be used to represent
   possible connection type profile values."/> 
  <caseSensitive value="true"/> 
  <content value="complete"/> 
  <concept> 
    <code value="ihe-xcpd"/> 
    <display value="IHE XCPD"/> 
    <definition value="IHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community
    _Patient_Discovery"/> 
  </concept> 
  <concept> 
    <code value="ihe-xca"/> 
    <display value="IHE XCA"/> 
    <definition value="IHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access"/> 
  </concept> 
  <concept> 
    <code value="ihe-xdr"/> 
    <display value="IHE XDR"/> 
    <definition value="IHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterpri
    se_Document_Reliable_Interchange"/> 
  </concept> 
  <concept> 
    <code value="ihe-xds"/> 
    <display value="IHE XDS"/> 
    <definition value="IHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Documen
    t_Sharing"/> 
  </concept> 
  <concept> 
    <code value="ihe-iid"/> 
    <display value="IHE IID"/> 
    <definition value="IHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display"/> 
  </concept> 
  <concept> 
    <code value="dicom-wado-rs"/> 
    <display value="DICOM WADO-RS"/> 
    <definition value="DICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/se
    ct_6.5.html"/> 
  </concept> 
  <concept> 
    <code value="dicom-qido-rs"/> 
    <display value="DICOM QIDO-RS"/> 
    <definition value="DICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_
    6.7.html"/> 
  </concept> 
  <concept> 
    <code value="dicom-stow-rs"/> 
    <display value="DICOM STOW-RS"/> 
    <definition value="DICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtm
    l/part18/sect_6.6.html"/> 
  </concept> 
  <concept> 
    <code value="dicom-wado-uri"/> 
    <display value="DICOM WADO-URI"/> 
    <definition value="DICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html"/> 
  </concept> 
  <concept> 
    <code value="hl7-fhir-rest"/> 
    <display value="HL7 FHIR"/> 
    <definition value="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> 
  <concept> 
    <code value="hl7-fhir-msg"/> 
    <display value="HL7 FHIR Messaging"/> 
    <definition value="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> 
  <concept> 
    <code value="hl7v2-mllp"/> 
    <display value="HL7 v2 MLLP"/> 
    <definition value="HL7v2 messages over an LLP TCP connection"/> 
  </concept> 
  <concept> 
    <code value="secure-email"/> 
    <display value="Secure email"/> 
    <definition value="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> 
  <concept> 
    <code value="direct-project"/> 
    <display value="Direct Project"/> 
    <definition value="Direct Project information - http://wiki.directproject.org/"/> 
  </concept> 
</CodeSystem>

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.