Definition for Code SystemETSISignatureTypeCodes

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

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="etsi-signature-type"/> 
  <meta> 
    <lastUpdated value="2022-09-10T04:52:37.223+10:00"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> This code system 
        <code> http://uri.etsi.org/01903/v1.2.2</code>  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">ProofOfOrigin
            <a name="etsi-signature-type-ProofOfOrigin"> </a> 
          </td> 
          <td> Proof of origin</td> 
          <td> indicates that the signer recognizes to have created, approved and sent the signed
             data object.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">ProofOfReceipt
            <a name="etsi-signature-type-ProofOfReceipt"> </a> 
          </td> 
          <td> Proof of receipt</td> 
          <td> indicates that signer recognizes to have received the content of the signed data
             object.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">ProofOfDelivery
            <a name="etsi-signature-type-ProofOfDelivery"> </a> 
          </td> 
          <td> Proof of delivery</td> 
          <td> indicates that the TSP providing that indication has delivered a signed data object
             in a local store accessible to the recipient of the signed data object.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">ProofOfSender
            <a name="etsi-signature-type-ProofOfSender"> </a> 
          </td> 
          <td> Proof of sender</td> 
          <td> indicates that the entity providing that indication has sent the signed data object
             (but not necessarily created it).</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">ProofOfapproval
            <a name="etsi-signature-type-ProofOfapproval"> </a> 
          </td> 
          <td> Proof of approval</td> 
          <td> indicates that the signer has approved the content of the signed data object.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">ProofOfCreation
            <a name="etsi-signature-type-ProofOfCreation"> </a> 
          </td> 
          <td> Proof of creation</td> 
          <td> indicates that the signer has created the signed data object (but not necessarily
             approved, nor sent it).</td> 
        </tr> 
      </table> 
    </div> 
  </text> 
  <url value="http://uri.etsi.org/01903/v1.2.2"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.4.1808"/> 
  </identifier> 
  <name value="ETSISignatureTypeCodes"/> 
  <title value="ETSI Signature Type Codes"/> 
  <status value="active"/> 
  <experimental value="false"/> 
  <publisher value="ETSI"/> 
  <description value="The ETSI TS 101 733 V2.2.1 (2013-04) - Electronic Signatures and Infrastructures
   (ESI) - defines a set of Commitment Types (Purpose of Signature). ETSI TS 101 903
   V1.2.2 defines vocabulary identifiers for these Commitment Types. Digital Signature
   Purposes, an indication of the reason an entity signs a document. This is included
   in the signed information and can be used when determining accountability for various
   actions concerning the document. "/> 
  <copyright value="These codes are excerpted from ETSI Standard for Digital Signatures and XAdES,
   Copyright by ETSI International. Copies of this standard are available through
   the ETSI Web Site at www.etsi.org."/> 
  <caseSensitive value="true"/> 
  <content value="complete"/> 
  <concept> 
    <code value="ProofOfOrigin"/> 
    <display value="Proof of origin"/> 
    <definition value="indicates that the signer recognizes to have created, approved and sent the signed
     data object."/> 
  </concept> 
  <concept> 
    <code value="ProofOfReceipt"/> 
    <display value="Proof of receipt"/> 
    <definition value="indicates that signer recognizes to have received the content of the signed data
     object."/> 
  </concept> 
  <concept> 
    <code value="ProofOfDelivery"/> 
    <display value="Proof of delivery"/> 
    <definition value="indicates that the TSP providing that indication has delivered a signed data object
     in a local store accessible to the recipient of the signed data object."/> 
  </concept> 
  <concept> 
    <code value="ProofOfSender"/> 
    <display value="Proof of sender"/> 
    <definition value="indicates that the entity providing that indication has sent the signed data object
     (but not necessarily created it)."/> 
  </concept> 
  <concept> 
    <code value="ProofOfapproval"/> 
    <display value="Proof of approval"/> 
    <definition value="indicates that the signer has approved the content of the signed data object."/> 
  </concept> 
  <concept> 
    <code value="ProofOfCreation"/> 
    <display value="Proof of creation"/> 
    <definition value="indicates that the signer has created the signed data object (but not necessarily
     approved, nor sent it)."/> 
  </concept> 
</CodeSystem>