NCPI FHIR Implementation Guide
0.2.0 - ci-build
NCPI FHIR Implementation Guide - Local Development build (v0.2.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://nih-ncpi.github.io/ncpi-fhir-ig/ValueSet/nih-consent-codes | Version: 0.2.0 | |||
| Draft as of 2024-03-04 | Computable Name: NihConsentCodes | |||
List of Abbreviations and titles associated with core NIH Consent types
References
https://nih-ncpi.github.io/ncpi-fhir-ig/CodeSystem/nih-consent
Expansion based on codesystem NIH Consent Codes v0.2.0 (CodeSystem)
This value set contains 9 concepts.
| Code | System | Display |
| GRU | https://nih-ncpi.github.io/ncpi-fhir-ig/CodeSystem/nih-consent | General Research Use |
| HMB | https://nih-ncpi.github.io/ncpi-fhir-ig/CodeSystem/nih-consent | Health/Medical/Biomedical |
| DS | https://nih-ncpi.github.io/ncpi-fhir-ig/CodeSystem/nih-consent | Disease-Specific (Disease/Trait/Exposure) |
| IRB | https://nih-ncpi.github.io/ncpi-fhir-ig/CodeSystem/nih-consent | IRB approval required |
| PUB | https://nih-ncpi.github.io/ncpi-fhir-ig/CodeSystem/nih-consent | Publication required |
| COL | https://nih-ncpi.github.io/ncpi-fhir-ig/CodeSystem/nih-consent | Collaboration Required |
| NPU | https://nih-ncpi.github.io/ncpi-fhir-ig/CodeSystem/nih-consent | Not-for-profit use only |
| MDS | https://nih-ncpi.github.io/ncpi-fhir-ig/CodeSystem/nih-consent | Methods |
| GSO | https://nih-ncpi.github.io/ncpi-fhir-ig/CodeSystem/nih-consent | Genetic studies only |
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 |