FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions

CodeSystem: ETSI Signature Type Codes

Official URL: http://uri.etsi.org/01903/v1.2.2 Version: 5.0.0
Standards status: Informative Maturity Level: 0 Computable Name: ETSISignatureTypeCodes

Copyright/Legal: 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.

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.

This Code system is referenced in the content logical definition of the following value sets:

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

CodeDisplayDefinition
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).