Artifact Version Policy Codes - HL7 Terminology (THO) v7.0.0

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

CodeSystem: Artifact Version Policy Codes

Official URL: http://terminology.hl7.org/CodeSystem/artifact-version-policy-codes			Version: 2.0.0
Standards status: Trial-use	Maturity Level: 3	Responsible: HL7 International	Computable Name: ArtifactVersionPolicyCodes
Copyright/Legal: 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

The versioning policy of an artifact (metadata, strict, loose, package)

This Code system is referenced in the content logical definition of the following value sets:

ArtifactVersionPolicy

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.