FHIR © HL7.org  |  Server Home  |  XIG Home  |  XIG Stats  |  Server Source  |  FHIR  

FHIR IG Statistics: CodeSystem/etsi-signature-type

Packagehl7.fhir.uv.extensions.r4b
Resource TypeCodeSystem
Idetsi-signature-type
FHIR VersionR4B
Sourcehttp://hl7.org/fhir/extensions
URLhttp://uri.etsi.org/01903/v1.2.2
Version5.0.0
Statusactive
NameETSISignatureTypeCodes
TitleETSI Signature Type Codes
Realmuv
Authorityhl7
DescriptionThe 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.
CopyrightThese 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.
Contentcomplete

Resources that use this resource

No resources found


Resources that this resource uses

No resources found


Narrative

Note: links and images are rebased to the (stated) source

This code system http://uri.etsi.org/01903/v1.2.2 defines the following codes:

Code Display Definition
ProofOfOrigin Proof of origin indicates that the signer recognizes to have created, approved and sent the signed data object.
ProofOfReceipt Proof of receipt indicates that signer recognizes to have received the content of the signed data object.
ProofOfDelivery Proof of delivery 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.
ProofOfSender Proof of sender indicates that the entity providing that indication has sent the signed data object (but not necessarily created it).
ProofOfapproval Proof of approval indicates that the signer has approved the content of the signed data object.
ProofOfCreation Proof of creation indicates that the signer has created the signed data object (but not necessarily approved, nor sent it).

Source

{
  "resourceType": "CodeSystem",
  "id": "etsi-signature-type",
  "meta": {
    "lastUpdated": "2023-03-26T15:21:02.749+11:00"
  },
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/web-source",
      "valueUrl": "http://hl7.org/fhir/R5/codesystem-etsi-signature-type.html"
    }
  ],
  "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",
  "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)."
    }
  ]
}