Release 5 Preview #1

This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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.14.477 Code System http://uri.etsi.org/01903/v1.2.2

Vocabulary

Work Group

Maturity Level: 0

Informative

Use Context: Any

This is a code system defined by the FHIR project.

Summary

Defining URL:

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

Version:

null

Name:

ETSISignatureTypeCodes

Title:

ETSI Signature Type Codes

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.

Committee:

??

OID:

(for OID based terminology systems)

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.

Source Resource

XML / JSON

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.14.477.1 Content

4.3.14.477.2 ETSI Signature Type Codes

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 Statement: 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.

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

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

Explanation of the columns that may appear on this page:

Level

A few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.

Source

The source of the definition of the code (when the value set draws in codes defined elsewhere)

Code

The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')

Display

The 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

Definition

An explanation of the meaning of the concept

Comments

Additional notes about how to use the code