This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

Endpoint Payload Type - XML Representation

(back to description)

Raw xml

Source view

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="endpoint-payload-type"/>
  <meta>
    <lastUpdated value="2020-04-09T17:10:28.568-04:00"/>
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
            
      <h2>Endpoint Payload Type</h2>
            
      <div>
              
        <p>This is an example value set defined by the FHIR project, that could be used to represent possible payload document types.</p>

            
      </div>
            
      <p>
              
        <b>Copyright Statement:</b> Some content from IHE® Copyright © 2015 IHE International, Inc.    This content is from the IHE Technical Frameworks and Supplements,    available for free download and use at http://www.ihe.net/Technical_Frameworks/
            
      </p>
            
      <p>This code system http://terminology.hl7.org/CodeSystem/endpoint-payload-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">any
                  
            <a name="endpoint-payload-type-any"> </a>
                
          </td>
                
          <td>Any</td>
                
          <td>Any payload type can be used with this endpoint, it is either a payload agnostic infrastructure (such as a storage repository), or some other type of endpoint where payload considerations are internally handled, and not available</td>
              
        </tr>
              
        <tr>
                
          <td style="white-space:nowrap">none
                  
            <a name="endpoint-payload-type-none"> </a>
                
          </td>
                
          <td>None</td>
                
          <td>This endpoint does not require any content to be sent; simply connecting to the endpoint is enough notification. This can be used as a 'ping' to wakeup a service to retrieve content, which could be to ensure security considerations are correctly handled</td>
              
        </tr>
            
      </table>
          
    </div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="pa"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="draft"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1"/>
  </extension>
  <url value="http://terminology.hl7.org/CodeSystem/endpoint-payload-type"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.4.642.1.1139"/>
  </identifier>
  <version value="4.2.0"/>
  <name value="EndpointPayloadType"/>
  <title value="Endpoint Payload Type"/>
  <status value="draft"/>
  <experimental value="false"/>
  <date value="2020-05-09T12:49:00-04:00"/>
  <publisher value="HL7 Patient Administration"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://hl7.org/fhir"/>
    </telecom>
  </contact>
  <description
               value="This is an example value set defined by the FHIR project, that could be used to represent possible payload document types."/>
  <copyright
             value="Some content from IHE® Copyright © 2015 IHE International, Inc.    This content is from the IHE Technical Frameworks and Supplements,    available for free download and use at http://www.ihe.net/Technical_Frameworks/"/>
  <caseSensitive value="true"/>
  <content value="complete"/>
  <concept>
    <code value="any"/>
    <display value="Any"/>
    <definition
                value="Any payload type can be used with this endpoint, it is either a payload agnostic infrastructure (such as a storage repository), or some other type of endpoint where payload considerations are internally handled, and not available"/>
  </concept>
  <concept>
    <code value="none"/>
    <display value="None"/>
    <definition
                value="This endpoint does not require any content to be sent; simply connecting to the endpoint is enough notification. This can be used as a &#39;ping&#39; to wakeup a service to retrieve content, which could be to ensure security considerations are correctly handled"/>
  </concept>
</CodeSystem>