Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Element NameChange Type
CodeSystem.UrlNew Code System (for HL7 created CS; externals have different rules; see HTA/Vocab guidance on changing URLs for external code systems)
CodeSystem.IdentifierNew Code System (if an OID or V2 mnemonic; externals have different rules see above)
CodeSystem.VersionN/A
CodeSystem.NameMajor?
CodeSystem.TitleMinor
CodeSystem.StatusMajor
CodeSystem.ExperimentalNot Currently In Use for UTG
CodeSystem.DateNot Currently In Use for UTG
CodeSystem.PublisherMinor
CodeSystem.ContactMinor
CodeSystem.DescriptionMinor ?   May be subjective if no change other than clarity or editorial corrections.

CodeSystem.UseContext

Not Currently In Use for UTG
CodeSystem.JurisdictionNot Currently In Use for UTG
CodeSystem.PurposeNot Currently In Use for UTG

CodeSystem.Copyright

Minor?   
CodeSystem.CaseSensitiveNot Widely Used in UTG (only two objects)
CodeSystem.ValueSetPro-forma in UTG, Cannot Change Value
CodeSystem.HierarchyMeaningMajor
CodeSystem.CompositionalNot Currently In Use for UTG
CodeSystem.VersionNeededNot Currently In Use for UTG - but under consideration for ballot-bound code systems
CodeSystem.ContentN/A (header element)       
CodeSystem.SupplementsNot Currently In Use for UTG
CodeSystem.CountNot Currently In Use for UTG
CodeSystem.Filter (and sub-elements)Not Currently In Use for UTG
CodeSystem.Property (including CodeSystem.Concept.Property.Code and .Value)

Major for Concept Status and defining property changes (like isSelectable), status changes (to/from Active to Retired, Active→Backwards Compatible,

Minor for non-defining property changes (like synonymCode), concept Status change of Active→Backwards-compatibility, addition of language translations of the text bits (print names, descriptions, etc.).  

 Not Not sure about Active→Deprecated?  or Deprecated→Backward Compatible).  ?   

CodeSystem.Concept (and all sub-elements)Major?   Add new concepts is always Major?   Note concepts never removed.   All changes to concepts by default are an increment of the major number.   Any proposed change could include a proposal to change the minor number instead if the change is asserted to be minor in the change proposal. 
concept.codecode never changed so N/A
concept.displayMajor?   if changed to one of the alternate already existing designations?  If fix to typo? Typos are minor.
concept.definitionMajor?   If correction of a typo?   Removal of spurious text erroneously inserted during import or during the old maintenance process?  (see Adding example?   Additional Discussion meta-value?  (see https://terminology.hl7.org/CodeSystem-v3-Confidentiality.html code 'V' ; see also  https://terminology.hl7.org/CodeSystem-v3-AcknowledgementDetailType.html )
concept.designation.MinorMajor?   If add language translation to a concept?   If correct error in translation?   Change designation.use?  All major.
concept.propertyMajor?  Minor?  changing vs. adding?   keeping same property but changing the type if erroneous?  is it different by property?   e.g. property 'synonym' added:  Major?  Minor?   property 'parent' added (add code to another hierarchy but leave it also where it currently is)
are there special or different rules about certain 'special' code systems, such ac UTG concept properties, or concept domains, or v2tables?special and/or extensive properties used only in these


...