FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example CodeSystem/etsi-signature-type (JSON)

Vocabulary Work GroupMaturity Level: N/AStandards Status: Informative

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

Definition for Code SystemETSISignatureTypeCodes

{
  "resourceType" : "CodeSystem",
  "id" : "etsi-signature-type",
  "meta" : {
    "lastUpdated" : "2022-12-08T15:10:54.170+00:00"
  },
  "text" : {
    "status" : "generated",
    "div" : "<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>"
  },
  "url" : "http://uri.etsi.org/01903/v1.2.2",
  "identifier" : [{
    "system" : "urn:ietf:rfc:3986",
    "value" : "urn:oid:2.16.840.1.113883.4.642.4.1808"
  }],
  "version" : "5.0.0-cibuild",
  "name" : "ETSISignatureTypeCodes",
  "title" : "ETSI Signature Type Codes",
  "status" : "active",
  "experimental" : false,
  "publisher" : "ETSI",
  "description" : "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. ",
  "jurisdiction" : [{
    "coding" : [{
      "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
      "code" : "001",
      "display" : "World"
    }]
  }],
  "copyright" : "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" : true,
  "content" : "complete",
  "concept" : [{
    "code" : "ProofOfOrigin",
    "display" : "Proof of origin",
    "definition" : "indicates that the signer recognizes to have created, approved and sent the signed data object."
  },
  {
    "code" : "ProofOfReceipt",
    "display" : "Proof of receipt",
    "definition" : "indicates that signer recognizes to have received the content of the signed data object."
  },
  {
    "code" : "ProofOfDelivery",
    "display" : "Proof of delivery",
    "definition" : "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."
  },
  {
    "code" : "ProofOfSender",
    "display" : "Proof of sender",
    "definition" : "indicates that the entity providing that indication has sent the signed data object (but not necessarily created it)."
  },
  {
    "code" : "ProofOfapproval",
    "display" : "Proof of approval",
    "definition" : "indicates that the signer has approved the content of the signed data object."
  },
  {
    "code" : "ProofOfCreation",
    "display" : "Proof of creation",
    "definition" : "indicates that the signer has created the signed data object (but not necessarily approved, nor sent it)."
  }]
}

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.