Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R2-contract-signer-type-for-R4 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R2ContractSignerTypeForR4 | ||
| This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/contract-signer-type | 1.0.2 for use in FHIR R4 that is appropriate for use but unavailable in http://hl7.org/fhir/ValueSet/contract-signer-type|4.0.1. |
This value set is part of the cross-version definitions generated to enable use of the
value set http://hl7.org/fhir/ValueSet/contract-signer-type|1.0.2 as defined in FHIR DSTU2
in FHIR R4.
The source value set is bound to the following FHIR DSTU2 elements:
Contract.signer.type as PreferredAcross FHIR versions, the value set has been mapped as:
http://hl7.org/fhir/ValueSet/contract-signer-type|1.0.2http://hl7.org/fhir/ValueSet/contract-signer-type|3.0.2http://hl7.org/fhir/ValueSet/contract-signer-type|4.0.1Note that all concepts are included in this cross-version definition because no concepts have compatible representations
Following are the generation technical comments: All concepts in the comparison are listed as identical. The source value set has fewer active concepts (17) than the target (48), so the source is narrower than the target. All concepts in the comparison are have code literals listed as identical. The source and target value sets have the same number of active concepts (48).
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://hl7.org/fhir/contractsignertypecodes version 📍1.0.2| Code | Display | Definition |
| 1.2.840.10065.1.12.1.1 | AuthorID | 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.10 | Identity-Witness | 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 | Consent-Witness | the signature of an individual who has witnessed the health care provider counselling a patient. |
| 1.2.840.10065.1.12.1.12 | Interpreter | 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 | Review | 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 | Source | 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 | Addendum | 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 | Administrative | 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 | Timestamp | 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.2 | Co-AuthorID | 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 | Co-Participated | 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 | Transcriptionist | 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 | Verification | 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 | Validation | 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 | Consent | the signature of an individual consenting to what is described in a health information document. |
| 1.2.840.10065.1.12.1.8 | Witness | the signature of a witness to any other signature. |
| 1.2.840.10065.1.12.1.9 | Event-Witness | the signature of a witness to an event. (Example the witness has observed a procedure and is attesting to this fact.) |
This value set expansion contains 17 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.1 | AuthorID | 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. | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.10 | Identity-Witness | 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.) | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.11 | Consent-Witness | the signature of an individual who has witnessed the health care provider counselling a patient. | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.12 | Interpreter | the signature of an individual who has translated health care information during an event or the obtaining of consent to a treatment. | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.13 | Review | 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.) | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.14 | Source | 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.) | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.15 | Addendum | 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. | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.16 | Administrative | 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. | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.17 | Timestamp | 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. | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.2 | Co-AuthorID | the signature of a health information document coauthor. There can be multiple coauthors of a health information document. | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.3 | Co-Participated | 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.) | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.4 | Transcriptionist | the signature of an individual who has transcribed a dictated document or recorded written text into a digital machine readable format. | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.5 | Verification | 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.) | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.6 | Validation | 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.) | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.7 | Consent | the signature of an individual consenting to what is described in a health information document. | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.8 | Witness | the signature of a witness to any other signature. | ||
http://hl7.org/fhir/contractsignertypecodes | 1.0.2 | 1.2.840.10065.1.12.1.9 | Event-Witness | the signature of a witness to an event. (Example the witness has observed a procedure and is attesting to this fact.) |
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 |