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

ValueSet: Cross-version VS for R5.SignatureTypeCodes for use in FHIR R4

Official URL: http://hl7.org/fhir/5.0/ValueSet/R5-signature-type-for-R4 Version: 0.0.1-snapshot-2
Standards status: Informative Maturity Level: 0 Computable Name: R5_signature_type_for_R4

This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/signature-type 5.0.0 for use in FHIR R4. Concepts not present here have direct equivalent mappings crossing all versions from R5 to R4.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

  • Include these codes as defined in http://uri.etsi.org/01903/v1.2.2 version 5.0.0
    CodeDisplayDefinition
    ProofOfOriginProof of originindicates that the signer recognizes to have created, approved and sent the signed data object.
    ProofOfReceiptProof of receiptindicates that signer recognizes to have received the content of the signed data object.
    ProofOfDeliveryProof 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.
    ProofOfSenderProof of senderindicates that the entity providing that indication has sent the signed data object (but not necessarily created it).
    ProofOfapprovalProof of approvalindicates that the signer has approved the content of the signed data object.
    ProofOfCreationProof of creationindicates that the signer has created the signed data object (but not necessarily approved, nor sent it).

 

Expansion

This value set expansion contains 6 concepts.

CodeSystemDisplayDefinition
  ProofOfOriginhttp://uri.etsi.org/01903/v1.2.2Proof of originindicates that the signer recognizes to have created, approved and sent the signed data object.
  ProofOfReceipthttp://uri.etsi.org/01903/v1.2.2Proof of receiptindicates that signer recognizes to have received the content of the signed data object.
  ProofOfDeliveryhttp://uri.etsi.org/01903/v1.2.2Proof 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.
  ProofOfSenderhttp://uri.etsi.org/01903/v1.2.2Proof of senderindicates that the entity providing that indication has sent the signed data object (but not necessarily created it).
  ProofOfapprovalhttp://uri.etsi.org/01903/v1.2.2Proof of approvalindicates that the signer has approved the content of the signed data object.
  ProofOfCreationhttp://uri.etsi.org/01903/v1.2.2Proof of creationindicates that the signer has created the signed data object (but not necessarily approved, nor sent it).

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. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System 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)
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