This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://terminology.hl7.org/ValueSet/consent-scope |
Version: | 4.1.0 |
Name: | ConsentScopeCodes |
Status: | draft |
Title: | Consent Scope Codes |
Definition: | This value set includes the four Consent scope codes. |
Publisher: | CBCC |
Committee: | Community Based Collaborative Care |
OID: | 2.16.840.1.113883.4.642.3.761 (for OID based terminology systems) |
Maturity: | 2 |
Source Resource: | XML / JSON / Turtle |
References
This value set is not used
http://terminology.hl7.org/CodeSystem/consentscope
This value set contains 3 concepts
Expansion based on Consent Scope Codes v4.2.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/consentscope
Code | Display | Definition |
research | Research | Consent to participate in research protocol and information sharing required |
patient-privacy | Privacy Consent | Agreement to collect, access, use or disclose (share) information |
treatment | Treatment | Consent to undergo a specific treatment |
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 |
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) |
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 |
History
Date | Action | Author | Custodian | Comment |
2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |