R5 Final QA

This page is part of the FHIR Specification (v5.0.0-draft-final: Final QA Preview for R5 - see ballot notes). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

4.3.2.24 CodeSystem http://uri.etsi.org/01903/v1.2.2

Terminology Infrastructure icon Work Group Maturity Level: 0Informative Use Context: Country: World
Official URL: http://uri.etsi.org/01903/v1.2.2 Version: 5.0.0-draft-final
active as of 2023-03-01 Computable Name: ETSISignatureTypeCodes
Flags: CaseSensitive, Complete OID: 2.16.840.1.113883.4.642.4.1808

This Code system is used in the following value sets:

  • ValueSet: Signature Type Codes (The 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. Examples include: author, transcriptionist/recorder, and witness.)

4.3.2.24.1 Definition

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.

4.3.2.24.2 Content

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

CodeDisplayDefinitionCopy
ProofOfOrigin Proof of originindicates that the signer recognizes to have created, approved and sent the signed data object.btn btn
ProofOfReceipt Proof of receiptindicates that signer recognizes to have received the content of the signed data object.btn btn
ProofOfDelivery Proof of deliveryindicates 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.btn btn
ProofOfSender Proof of senderindicates that the entity providing that indication has sent the signed data object (but not necessarily created it).btn btn
ProofOfapproval Proof of approvalindicates that the signer has approved the content of the signed data object.btn btn
ProofOfCreation Proof of creationindicates that the signer has created the signed data object (but not necessarily approved, nor sent it).btn btn

 

See the full registry of code systems defined as part of FHIR.

Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code