artifact-version-policy-codes
type: CodeSystem
node role: treeRoot
id:
  v: artifact-version-policy-codes
text:
  status:
    v: generated
  div: Generated Narrative: CodeSystem artifact-version-policy-codes This case-sensitive code system http://terminology.hl7.org/CodeSystem/artifact-version-policy-codes defines the following codes: Code Display Definition metadata Metadata 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. strict Strict 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. loose Loose A versioning policy that indicates that only breaking changes require a change to the value of the version element of the artifact. package Package 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.
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
  value: code
    v: cds
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
  value: code
    v: trial-use
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
  value: integer
    v: 3
url:
  v: http://terminology.hl7.org/CodeSystem/artifact-version-policy-codes
version:
  v: 2.0.0
name:
  v: ArtifactVersionPolicyCodes
title:
  v: Artifact Version Policy Codes
status:
  v: active
experimental:
  v: false
date:
  v: 2025-10-13
publisher:
  v: HL7 International
contact:
  telecom:
    system:
      v: url
    value:
      v: http://hl7.org
  telecom:
    system:
      v: email
description:
  v: The versioning policy of an artifact (metadata, strict, loose, package)
copyright:
  v: 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
case sensitive:
  v: true
value set:
  v: http://terminology.hl7.org/ValueSet/artifact-version-policy
  link: http://terminology.hl7.org/ValueSet/artifact-version-policy
content:
  v: complete
concept:
  code:
    v: metadata
  display:
    v: Metadata
  definition:
    v: 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:
  code:
    v: strict
  display:
    v: Strict
  definition:
    v: 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:
  code:
    v: loose
  display:
    v: Loose
  definition:
    v: A versioning policy that indicates that only breaking changes require a change to the value of the version element of the artifact.
concept:
  code:
    v: package
  display:
    v: Package
  definition:
    v: 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.