This page is part of the FHIR Specification (v5.0.0-ballot: FHIR R5 Ballot Preview). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B
Clinical Decision Support Work Group | Maturity Level: 0 | Trial Use | Use Context: Not yet ready for Production use, Not yet ready for Production use |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/artifact-contribution-type |
Version: | 5.0.0-ballot |
Name: | ArtifactContributionType |
Title: | ArtifactContributionType |
Status: | draft |
Definition: | Citation contribution. |
Committee: | Clinical Decision Support Work Group |
OID: | 2.16.840.1.113883.4.642.3.2959 (for OID based terminology systems) |
Flags: | Experimental, Immutable |
This value set is used in the following places:
http://terminology.hl7.org/CodeSystem/artifact-contribution-type
This expansion generated 07 Sep 2022
This value set contains 14 concepts
Expansion based on ArtifactContributionType v5.0.0-ballot (CodeSystem)
Code | System | Display | Definition |
conceptualization | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Conceptualization | Conceptualization (see https://jats4r.org/credit-taxonomy). |
data-curation | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Data curation | Data curation (see https://jats4r.org/credit-taxonomy). |
formal-analysis | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Formal analysis | Formal analysis (see https://jats4r.org/credit-taxonomy). |
funding-acquisition | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Funding acquisition | Funding acquisition (see https://jats4r.org/credit-taxonomy). |
investigation | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Investigation | Investigation (see https://jats4r.org/credit-taxonomy). |
methodology | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Methodology | Methodology (see https://jats4r.org/credit-taxonomy). |
project-administration | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Project administration | Project administration (see https://jats4r.org/credit-taxonomy). |
resources | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Resources | Resources (see https://jats4r.org/credit-taxonomy). |
software | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Software | Software (see https://jats4r.org/credit-taxonomy). |
supervision | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Supervision | Supervision (see https://jats4r.org/credit-taxonomy). |
validation | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Validation | Validation (see https://jats4r.org/credit-taxonomy). |
visualization | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Visualization | Visualization (see https://jats4r.org/credit-taxonomy). |
writing-original-draft | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Writing - original draft | Writing - original draft (see https://jats4r.org/credit-taxonomy). |
writing-review-editing | http://terminology.hl7.org/CodeSystem/artifact-contribution-type | Writing - review & editing | Writing - review & editing (see https://jats4r.org/credit-taxonomy). |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
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). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
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 |