Release 5 Ballot

This page is part of the FHIR Specification (v5.0.0-ballot: R5 Ballot - see ballot notes). 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

4.4.1.34 ValueSet http://hl7.org/fhir/ValueSet/artifact-contribution-type

Clinical Decision Support icon Work Group Maturity Level: 0Trial 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 icon 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:

4.4.1.34.1 Content Logical Definition

 

4.4.1.34.2 Expansion

This expansion generated 10 Sep 2022

This value set contains 14 concepts

Expansion based on ArtifactContributionType v5.0.0-ballot (CodeSystem)

CodeSystemDisplayDefinition
  conceptualizationhttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeConceptualization

Conceptualization (see https://jats4r.org/credit-taxonomy).

  data-curationhttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeData curation

Data curation (see https://jats4r.org/credit-taxonomy).

  formal-analysishttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeFormal analysis

Formal analysis (see https://jats4r.org/credit-taxonomy).

  funding-acquisitionhttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeFunding acquisition

Funding acquisition (see https://jats4r.org/credit-taxonomy).

  investigationhttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeInvestigation

Investigation (see https://jats4r.org/credit-taxonomy).

  methodologyhttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeMethodology

Methodology (see https://jats4r.org/credit-taxonomy).

  project-administrationhttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeProject administration

Project administration (see https://jats4r.org/credit-taxonomy).

  resourceshttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeResources

Resources (see https://jats4r.org/credit-taxonomy).

  softwarehttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeSoftware

Software (see https://jats4r.org/credit-taxonomy).

  supervisionhttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeSupervision

Supervision (see https://jats4r.org/credit-taxonomy).

  validationhttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeValidation

Validation (see https://jats4r.org/credit-taxonomy).

  visualizationhttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeVisualization

Visualization (see https://jats4r.org/credit-taxonomy).

  writing-original-drafthttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeWriting - original draft

Writing - original draft (see https://jats4r.org/credit-taxonomy).

  writing-review-editinghttp://terminology.hl7.org/CodeSystem/artifact-contribution-typeWriting - 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:

LvlA 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
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code