FHIR Cross-Version Extensions package for FHIR R4B from FHIR R4
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R4B from FHIR R4 - Version 0.0.1-snapshot-2. See the Directory of published versions

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

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

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

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 urn:iso-astm:E1762-95:2013 version 4.0.1
    CodeDisplayDefinition
    1.2.840.10065.1.12.1.1Author'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.3Co-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.5Verification 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.7Consent Signaturethe signature of an individual consenting to what is described in a health information document.
    1.2.840.10065.1.12.1.9Event 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.11Consent Witness Signaturethe signature of an individual who has witnessed the health care provider counselling a patient.
    1.2.840.10065.1.12.1.13Review 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.15Addendum 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.17Administrative (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.

 

Expansion

This value set expansion contains 9 concepts.

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

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