This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions
Clinical Decision Support Work Group | Maturity Level: 0 | Trial Use | Use Context: Any |
Official URL: http://hl7.org/fhir/ValueSet/related-artifact-type-expanded
|
Version: 6.0.0-ballot2 | |||
draft as of 2022-03-22 | Computable Name: RelatedArtifactTypeExpanded | |||
Flags: Immutable | OID: 2.16.840.1.113883.4.642.3.2975 |
This value set is used in the following places:
The type of relationship to the cited artifact.
Generated Narrative: ValueSet related-artifact-type-expanded
Last updated: 2024-11-15T18:37:49.495Z
Profile: Shareable ValueSet
http://hl7.org/fhir/related-artifact-type-expanded
This expansion generated 15 Nov 2024
Generated Narrative: ValueSet
Last updated: 2024-11-15T18:37:49.495Z
Profile: Shareable ValueSet
Expansion based on codesystem Related Artifact Type Expanded v6.0.0-ballot2 (CodeSystem)
This value set contains 2 concepts
Code | System | Display | Definition |
reprint | http://hl7.org/fhir/related-artifact-type-expanded | Reprint | A copy of the artifact in a publication with a different artifact identifier. |
reprint-of | http://hl7.org/fhir/related-artifact-type-expanded | Reprint Of | The original version of record for which the current artifact is a copy. |
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 |