FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions
| Official URL: http://hl7.org/fhir/5.0/ValueSet/R5-consent-category-for-R4 | Version: 0.0.1-snapshot-2 | |||
| Standards status: Informative | Maturity Level: 1 | Responsible: Community Based Collaborative Care | Computable Name: R5_consent_category_for_R4 | |
| This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/consent-category | 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)
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/consentscopehttp://terminology.hl7.org/CodeSystem/consentcategorycodeshttp://loinc.org
| Code | Display |
| 59284-0 | Patient Consent |
| 57016-8 | Privacy policy acknowledgement Document |
| 57017-6 | Privacy policy Organization Document |
| 64292-6 | Release of information consent |
Expansion from tx.fhir.org based on:
This value set contains 27 concepts
| Code | System | Display | Definition |
| adr | http://terminology.hl7.org/CodeSystem/consentscope | Advanced Care Directive | Actions to be taken if they are no longer able to make decisions for themselves |
| research | http://terminology.hl7.org/CodeSystem/consentscope | Research | Consent to participate in research protocol and information sharing required |
| patient-privacy | http://terminology.hl7.org/CodeSystem/consentscope | Privacy Consent | Agreement to collect, access, use or disclose (share) information |
| treatment | http://terminology.hl7.org/CodeSystem/consentscope | Treatment | Consent to undergo a specific treatment |
| acd | http://terminology.hl7.org/CodeSystem/consentcategorycodes | Advance Directive | Any instructions, written or given verbally by a patient in anticipation of potential need for medical treatment. |
| dnr | http://terminology.hl7.org/CodeSystem/consentcategorycodes | Do Not Resuscitate | A legal document, signed by both the patient and their provider, stating a desire not to have CPR initiated in case of a cardiac event. |
| emrgonly | http://terminology.hl7.org/CodeSystem/consentcategorycodes | Emergency Only Disclosure | Opt-in to disclosure of health information for emergency only consent directive. Comment: This general consent directive specifically limits disclosure of health information for purpose of emergency treatment. Additional parameters may further limit the disclosure to specific users, roles, duration, types of information, and impose uses obligations. |
| hcd | http://terminology.hl7.org/CodeSystem/consentcategorycodes | Health Care Directive | Patient authored document communicating to patient's health care provider(s) instructions about the patient's goals, preferences, and priorities if the patient is diagnosed as being terminally ill and in a persistent vegetative state, is in a permanently unconscious condition or is otherwise unable to communicate thoe instructions. |
| npp | http://terminology.hl7.org/CodeSystem/consentcategorycodes | Notice of Privacy Practices | Acknowledgement of custodian notice of privacy practices. Usage Notes: This type of consent directive acknowledges a custodian's notice of privacy practices including its permitted collection, access, use and disclosure of health information to users and for purposes of use specified. |
| polst | http://terminology.hl7.org/CodeSystem/consentcategorycodes | POLST | The Physician Order for Life-Sustaining Treatment form records a person's health care wishes for end of life emergency treatment and translates them into an order by the physician. It must be reviewed and signed by both the patient and the physician, Advanced Registered Nurse Practitioner or Physician Assistant. |
| research | http://terminology.hl7.org/CodeSystem/consentcategorycodes | Research Information Access | Consent to have healthcare information in an electronic health record accessed for research purposes. |
| rsdid | http://terminology.hl7.org/CodeSystem/consentcategorycodes | De-identified Information Access | Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes, but without consent to re-identify the information under any circumstance. |
| rsreid | http://terminology.hl7.org/CodeSystem/consentcategorycodes | Re-identifiable Information Access | Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes re-identified under specific circumstances outlined in the consent. |
| _ActConsentType | http://terminology.hl7.org/CodeSystem/v3-ActCode | ActConsentType | Definition: The type of consent directive, e.g., to consent or dissent to collect, access, or use in specific ways within an EHRS or for health information exchange; or to disclose health information for purposes such as research. |
| ICOL | http://terminology.hl7.org/CodeSystem/v3-ActCode | information collection | Definition: Consent to have healthcare information collected in an electronic health record. This entails that the information may be used in analysis, modified, updated. |
| IDSCL | http://terminology.hl7.org/CodeSystem/v3-ActCode | information disclosure | Definition: Consent to have collected healthcare information disclosed. |
| INFA | http://terminology.hl7.org/CodeSystem/v3-ActCode | information access | Definition: Consent to access healthcare information. |
| INFAO | http://terminology.hl7.org/CodeSystem/v3-ActCode | access only | Definition: Consent to access or "read" only, which entails that the information is not to be copied, screen printed, saved, emailed, stored, re-disclosed or altered in any way. This level ensures that data which is masked or to which access is restricted will not be. Example: Opened and then emailed or screen printed for use outside of the consent directive purpose. |
| INFASO | http://terminology.hl7.org/CodeSystem/v3-ActCode | access and save only | Definition: Consent to access and save only, which entails that access to the saved copy will remain locked. |
| IRDSCL | http://terminology.hl7.org/CodeSystem/v3-ActCode | information redisclosure | Definition: Information re-disclosed without the patient's consent. |
| RESEARCH | http://terminology.hl7.org/CodeSystem/v3-ActCode | research information access | Definition: Consent to have healthcare information in an electronic health record accessed for research purposes. |
| RSDID | http://terminology.hl7.org/CodeSystem/v3-ActCode | de-identified information access | Definition: Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes, but without consent to re-identify the information under any circumstance. |
| RSREID | http://terminology.hl7.org/CodeSystem/v3-ActCode | re-identifiable information access | Definition: Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes re-identified under specific circumstances outlined in the consent. Example:: Where there is a need to inform the subject of potential health issues. |
| 59284-0 | http://loinc.org | Consent Document | |
| 57016-8 | http://loinc.org | Privacy policy acknowledgment Document | |
| 57017-6 | http://loinc.org | Privacy policy Organization Document | |
| 64292-6 | http://loinc.org | Release of information consent Document |
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 |