Codesystem-endpoint-payload-type.xml

Definition for Code System Endpoint Payload Type

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="endpoint-payload-type"/> 
  <meta> 
    <lastUpdated value="2019-10-24T11:53:00+11: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://hl7.org/fhir/endpoint-payload-type defines the following codes:</p> 
      <table class="codes">
        <tr> 
          <td> 
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
        <tr> 
          <td> 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> 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-ballot-status">
    <valueString value="Informative"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="pa"/> 
  </extension> 
  <url value="http://hl7.org/fhir/endpoint-payload-type"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.1.490"/> 
  </identifier> 
  <version value="3.0.2"/> 
  <name value="Endpoint Payload Type"/> 
  <status value="draft"/> 
  <experimental value="true"/> 
  <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"/> 
  <valueSet value="http://hl7.org/fhir/ValueSet/endpoint-payload-type"/> 
  <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 'ping' to wakeup a service to retrieve content,
     which could be to ensure security considerations are correctly handled"/> 
  </concept> 
</CodeSystem>