HL7 Terminology (THO)
7.0.0 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 7.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

: Artifact Version Policy Codes - XML Representation

Page standards status: Trial-use Maturity Level: 3

Raw xml | Download


<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="artifact-version-policy-codes"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem artifact-version-policy-codes</b></p><a name="artifact-version-policy-codes"> </a><a name="hcartifact-version-policy-codes"> </a><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/artifact-version-policy-codes</code> defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">metadata<a name="artifact-version-policy-codes-metadata"> </a></td><td>Metadata</td><td><div><p>A versioning policy that allows non-substantive changes to the metadata elements of an artifact without requiring a change to the value of the version element.</p>
</div></td></tr><tr><td style="white-space:nowrap">strict<a name="artifact-version-policy-codes-strict"> </a></td><td>Strict</td><td><div><p>A versioning policy that indicates that any change to the content of an artifact, including non-substantive and metadata changes, requires a change to the value of the version element of the artifact.</p>
</div></td></tr><tr><td style="white-space:nowrap">loose<a name="artifact-version-policy-codes-loose"> </a></td><td>Loose</td><td><div><p>A versioning policy that indicates that only breaking changes require a change to the value of the version element of the artifact.</p>
</div></td></tr><tr><td style="white-space:nowrap">package<a name="artifact-version-policy-codes-package"> </a></td><td>Package</td><td><div><p>A versioning policy that indicates that version of the artifact is managed as the version of the package in which the artifact appears. This is a common versioning policy often used when artifacts are published as part of an implementation guide, and is important to consider as it indicates that there may be version changes <em>without</em> corresponding changes in the content of a particular artifact. For example, if an implementation guide includes questionnaires, new versions of that implementation guide may include new questionnaires, but not change existing ones, and in this case, with package-managed versions, the existing questionnaires that had no actual changes would still be published with a new version.</p>
</div></td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="cds"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="3"/>
  </extension>
  <url
       value="http://terminology.hl7.org/CodeSystem/artifact-version-policy-codes"/>
  <version value="2.0.0"/>
  <name value="ArtifactVersionPolicyCodes"/>
  <title value="Artifact Version Policy Codes"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2025-10-13"/>
  <publisher value="HL7 International"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://hl7.org"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="hq@HL7.org"/>
    </telecom>
  </contact>
  <description
               value="The versioning policy of an artifact (metadata, strict, loose, package)"/>
  <copyright
             value="This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html"/>
  <caseSensitive value="true"/>
  <valueSet
            value="http://terminology.hl7.org/ValueSet/artifact-version-policy"/>
  <content value="complete"/>
  <concept>
    <code value="metadata"/>
    <display value="Metadata"/>
    <definition
                value="A versioning policy that allows non-substantive changes to the metadata elements of an artifact without requiring a change to the value of the version element."/>
  </concept>
  <concept>
    <code value="strict"/>
    <display value="Strict"/>
    <definition
                value="A versioning policy that indicates that any change to the content of an artifact, including non-substantive and metadata changes, requires a change to the value of the version element of the artifact."/>
  </concept>
  <concept>
    <code value="loose"/>
    <display value="Loose"/>
    <definition
                value="A versioning policy that indicates that only breaking changes require a change to the value of the version element of the artifact."/>
  </concept>
  <concept>
    <code value="package"/>
    <display value="Package"/>
    <definition
                value="A versioning policy that indicates that version of the artifact is managed as the version of the package in which the artifact appears. This is a common versioning policy often used when artifacts are published as part of an implementation guide, and is important to consider as it indicates that there may be version changes _without_ corresponding changes in the content of a particular artifact. For example, if an implementation guide includes questionnaires, new versions of that implementation guide may include new questionnaires, but not change existing ones, and in this case, with package-managed versions, the existing questionnaires that had no actual changes would still be published with a new version."/>
  </concept>
</CodeSystem>