Release 5 Draft Ballot

This page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot - 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 . Page versions: R5 R4B R4 R3 R2

4.4.1.378 Value Set http://hl7.org/fhir/ValueSet/signature-type

FHIR Infrastructure Work Group Maturity Level: 0Informative Use Context: Any

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/signature-type
Version:4.6.0
Name:SignatureTypeCodes
Title:Signature Type Codes
Definition:

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.

Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.3.63 (for OID based terminology systems)
Copyright:

This value set includes contents from ASTM and ETSI which hold their own copyright.

Source ResourceXML / JSON

This value set is used in the following places:

4.4.1.378.1 Content Logical Definition

This value set includes codes based on the following rules:

 

4.4.1.378.2 Expansion

This expansion generated 15 Apr 2021

This value set contains 24 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).
1.2.840.10065.1.12.1.1urn:iso-astm:E1762-95:2013Author's Signaturethe signature of the primary or sole author of a health information document. There can be only one primary author of a health information document.
1.2.840.10065.1.12.1.2urn:iso-astm:E1762-95:2013Coauthor's Signaturethe signature of a health information document coauthor. There can be multiple coauthors of a health information document.
1.2.840.10065.1.12.1.3urn:iso-astm:E1762-95:2013Co-participant's Signaturethe signature of an individual who is a participant in the health information document but is not an author or coauthor. (Example a surgeon who is required by institutional, regulatory, or legal rules to sign an operative report, but who was not involved in the authorship of that report.)
1.2.840.10065.1.12.1.4urn:iso-astm:E1762-95:2013Transcriptionist/Recorder Signaturethe signature of an individual who has transcribed a dictated document or recorded written text into a digital machine readable format.
1.2.840.10065.1.12.1.5urn:iso-astm:E1762-95:2013Verification Signaturea signature verifying the information contained in a document. (Example a physician is required to countersign a verbal order that has previously been recorded in the medical record by a registered nurse who has carried out the verbal order.)
1.2.840.10065.1.12.1.6urn:iso-astm:E1762-95:2013Validation Signaturea signature validating a health information document for inclusion in the patient record. (Example a medical student or resident is credentialed to perform history or physical examinations and to write progress notes. The attending physician signs the history and physical examination to validate the entry for inclusion in the patient's medical record.)
1.2.840.10065.1.12.1.7urn:iso-astm:E1762-95:2013Consent Signaturethe signature of an individual consenting to what is described in a health information document.
1.2.840.10065.1.12.1.8urn:iso-astm:E1762-95:2013Signature Witness Signaturethe signature of a witness to any other signature.
1.2.840.10065.1.12.1.9urn:iso-astm:E1762-95:2013Event Witness Signaturethe signature of a witness to an event. (Example the witness has observed a procedure and is attesting to this fact.)
1.2.840.10065.1.12.1.10urn:iso-astm:E1762-95:2013Identity Witness Signaturethe signature of an individual who has witnessed another individual who is known to them signing a document. (Example the identity witness is a notary public.)
1.2.840.10065.1.12.1.11urn:iso-astm:E1762-95:2013Consent Witness Signaturethe signature of an individual who has witnessed the health care provider counselling a patient.
1.2.840.10065.1.12.1.12urn:iso-astm:E1762-95:2013Interpreter Signaturethe signature of an individual who has translated health care information during an event or the obtaining of consent to a treatment.
1.2.840.10065.1.12.1.13urn:iso-astm:E1762-95:2013Review Signaturethe signature of a person, device, or algorithm that has reviewed or filtered data for inclusion into the patient record. ( Examples: (1) a medical records clerk who scans a document for inclusion in the medical record, enters header information, or catalogues and classifies the data, or a combination thereof; (2) a gateway that receives data from another computer system and interprets that data or changes its format, or both, before entering it into the patient record.)
1.2.840.10065.1.12.1.14urn:iso-astm:E1762-95:2013Source Signaturethe signature of an automated data source. (Examples: (1) the signature for an image that is generated by a device for inclusion in the patient record; (2) the signature for an ECG derived by an ECG system for inclusion in the patient record; (3) the data from a biomedical monitoring device or system that is for inclusion in the patient record.)
1.2.840.10065.1.12.1.15urn:iso-astm:E1762-95:2013Addendum Signaturethe signature on a new amended document of an individual who has corrected, edited, or amended an original health information document. An addendum signature can either be a signature type or a signature sub-type (see 8.1). Any document with an addendum signature shall have a companion document that is the original document with its original, unaltered content, and original signatures. The original document shall be referenced via an attribute in the new document, which contains, for example, the digest of the old document. Whether the original, unaltered, document is always displayed with the addended document is a local matter, but the original, unaltered, document must remain as part of the patient record and be retrievable on demand.
1.2.840.10065.1.12.1.16urn:iso-astm:E1762-95:2013Modification Signaturethe signature on an original document of an individual who has generated a new amended document. This (original) document shall reference the new document via an additional signature purpose. This is the inverse of an addendum signature and provides a pointer from the original to the amended document.
1.2.840.10065.1.12.1.17urn:iso-astm:E1762-95:2013Administrative (Error/Edit) Signaturethe signature of an individual who is certifying that the document is invalidated by an error(s), or is placed in the wrong chart. An administrative (error/edit) signature must include an addendum to the document and therefore shall have an addendum signature sub-type (see 8.1). This signature is reserved for the highest health information system administrative classification, since it is a statement that the entire document is invalidated by the error and that the document should no longer be used for patient care, although for legal reasons the document must remain part of the permanent patient record.
1.2.840.10065.1.12.1.18urn:iso-astm:E1762-95:2013Timestamp Signaturethe signature by an entity or device trusted to provide accurate timestamps. This timestamp might be provided, for example, in the signature time attribute.

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - 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