Release 5 Draft Ballot

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


Vocabulary Work GroupMaturity Level: N/AStandards Status: Informative

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

Definition for Code System ETSISignatureTypeCodes

  "resourceType" : "CodeSystem",
  "id" : "etsi-signature-type",
  "meta" : {
    "lastUpdated" : "2022-05-17T15:24:24.905+00:00"
  "text" : {
    "status" : "generated",
    "div" : "<div>!-- Snipped for Brevity --></div>"
  "url" : "",
  "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. ",
  "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",
  "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.