This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
FHIR Infrastructure Work Group | Maturity Level: 0 | Informative | Use Context: Country: World, Not Intended for Production use |
Official URL: http://hl7.org/fhir/ValueSet/signature-type
|
Version: 5.0.0 | |||
draft as of 2023-03-26 | Computable Name: SignatureTypeCodes | |||
Flags: Experimental | OID: 1.2.840.10065.1.12 |
This value set is used in the following places:
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.
This value set includes codes based on the following rules:
http://uri.etsi.org/01903/v1.2.2
urn:iso-astm:E1762-95:2013
This expansion generated 26 Mar 2023
This value set contains 24 concepts
Expansion based on:
Code | System | Display | Definition |
ProofOfOrigin | http://uri.etsi.org/01903/v1.2.2 | Proof of origin | indicates that the signer recognizes to have created, approved and sent the signed data object. |
ProofOfReceipt | http://uri.etsi.org/01903/v1.2.2 | Proof of receipt | indicates that signer recognizes to have received the content of the signed data object. |
ProofOfDelivery | http://uri.etsi.org/01903/v1.2.2 | 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 | http://uri.etsi.org/01903/v1.2.2 | Proof of sender | indicates that the entity providing that indication has sent the signed data object (but not necessarily created it). |
ProofOfapproval | http://uri.etsi.org/01903/v1.2.2 | Proof of approval | indicates that the signer has approved the content of the signed data object. |
ProofOfCreation | http://uri.etsi.org/01903/v1.2.2 | Proof of creation | indicates that the signer has created the signed data object (but not necessarily approved, nor sent it). |
1.2.840.10065.1.12.1.1 | urn:iso-astm:E1762-95:2013 | Author's Signature | the 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.2 | urn:iso-astm:E1762-95:2013 | Coauthor's Signature | the signature of a health information document coauthor. There can be multiple coauthors of a health information document. |
1.2.840.10065.1.12.1.3 | urn:iso-astm:E1762-95:2013 | Co-participant's Signature | the 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.4 | urn:iso-astm:E1762-95:2013 | Transcriptionist/Recorder Signature | the 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.5 | urn:iso-astm:E1762-95:2013 | Verification Signature | a 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.6 | urn:iso-astm:E1762-95:2013 | Validation Signature | a 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.7 | urn:iso-astm:E1762-95:2013 | Consent Signature | the signature of an individual consenting to what is described in a health information document. |
1.2.840.10065.1.12.1.8 | urn:iso-astm:E1762-95:2013 | Signature Witness Signature | the signature of a witness to any other signature. |
1.2.840.10065.1.12.1.9 | urn:iso-astm:E1762-95:2013 | Event Witness Signature | the 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.10 | urn:iso-astm:E1762-95:2013 | Identity Witness Signature | the 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.11 | urn:iso-astm:E1762-95:2013 | Consent Witness Signature | the signature of an individual who has witnessed the health care provider counselling a patient. |
1.2.840.10065.1.12.1.12 | urn:iso-astm:E1762-95:2013 | Interpreter Signature | the 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.13 | urn:iso-astm:E1762-95:2013 | Review Signature | the 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.14 | urn:iso-astm:E1762-95:2013 | Source Signature | the 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.15 | urn:iso-astm:E1762-95:2013 | Addendum Signature | the 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.16 | urn:iso-astm:E1762-95:2013 | Modification Signature | the 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.17 | urn:iso-astm:E1762-95:2013 | Administrative (Error/Edit) Signature | the 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.18 | urn:iso-astm:E1762-95:2013 | Timestamp Signature | the 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:
Lvl | A 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 |
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 |