Page tree
Skip to end of metadata
Go to start of metadata

All Ballot-bound Terminology Content must go through the Ballot process and not the Unified Terminology Governance Process. Terminology artifacts that are Ballot-bound can be found in the areas below. 

FHIR

All Internal FHIR Code Systems and all FHIR Value Sets are Ballot-bound.  These can be easily recognized as their Canonical URL values all begin with "http://hl7.org/fhir".   These are not maintained through the UTG system but are maintained within the FHIR ecosystem.

See http://build.fhir.org/terminologies-systems.html in the 'Value Sets' tab for all Ballot-bound FHIR Value Sets.

See http://build.fhir.org/terminologies-systems.html, select the 'Code Systems' tab, and then select the 'Internal (FHIR)' subtab further down the page for all Ballot-bound FHIR Code Systems. 


V2

All of the v2 tables have been subject to Harmonization in past years, but a subset of them are directly tied to model structures in the V2 Standard.   As such they are version-dependent, and cannot be modified through community consensus process without new or changed model structures also being balloted.   These include:

 v2-0003 Event Type

v2-0076 messageType

v2-0125 Value Type

v2-0354 messageStructure

v2-0440 Data Types

Potentially additional ones are awaiting agreement with the V2 group.

V3

All of the v3 code systems and value sets have been subject to Harmonization in past years, including those that have been declared 'structural'.   However there are a small number of additional code systems/value sets that are schema-bound, ie their content is enumerated in XSD schemas and are part of the v3 processing infrastructure. They are generally not part of the published coremif content but are required for v3 infrastructure. Some of these may be found in the published terminology.hl7.org content for browsable convenience. These are not generally subject to UTG process maintenance as they are tied into the V3 base datatype schemas; any change for these must be coordinated with an update and republication of the V3 coremif base schemas. These include:

AddressPartType

CalendarCycle

Code

CodingRationale

Compression

Decimal

EntityNamePartQualifier

EntityNamePartType

EntityNameUse

IdentifierReliability

IdentifierScope

IntegrityCheckAlgorithm

NullFlavor

PostalAddressUse

set_Code

set_CodingRationale

set_EntityNamePartQualifier

set_EntityNameUse

set_IDREF

set_PostalAddressUse

set_TelecommunicationAddressUse

set_TelecommunicationCapability

StrucDoc.Align

StrucDoc.CellScope

StrucDoc.Frame

StrucDoc.Length

StrucDoc.ListType

StrucDoc.Revised

StrucDoc.Rules

StrucDoc.VAlign

TelecommunicationAddressUse

TelecommunicationCapability

TimingEvent

Uid

UncertaintyType

UpdateMode

Uri

XmlID

XmlIDREF

  • No labels