IP Review

Unattributed Code Systems

http://unstats.un.org/unsd/methods/m49/m49.htm

Copyright Fragment

This fragment is available on index.html

No use of external IP

Copyright and Registered Trademark Uses

IG © 2024+ HL7 International / Terminology Infrastructure. Package hl7.xprod.uv.termfundamentals#0.1.0 based on FHIR 5.0.0. Generated 2026-01-27 Links: Table of Contents | QA Report ( src )
hl7.fhir.us.hai: Healthcare Associated Infection Implementation Guide ®© HL7 | CC0 ( src )
Clinical Document Architecture Release 2 (CDA R2) is one of the HL7 V3 family standards; however, CDA R2 uses Release 1 of the Data Types –Abstract specification, which does not include explicit references to Value Sets and versions in the CD (Concept Descriptor) or other coded data types. In particular for implementation guides where references to Value Sets are required, such as QRDA (HL7 Implementation Guide for CDA® Release 2: Quality Reporting Document Architecture – Category I27), it may be necessary to use a CDA extension in order to represent this data – for QRDA, this extension is the sdtc:valueSet attribute (note that there is no extension currently being used in QRDA to represent the value set version). ( src )
Terminology Fundamentals, published by HL7 International / Terminology Infrastructure. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/terminology-fundamentals-ig/ and changes regularly. See the Directory of published versions ( src )

External References

Type	Reference	Content
web	github.com	Terminology Fundamentals, published by HL7 International / Terminology Infrastructure. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/terminology-fundamentals-ig/ and changes regularly. See the Directory of published versions
web	confluence.ihtsdotools.org	SNOMED CT Expression Constraint Language (ECL)
web	en.wikipedia.org	Structured Query Language (SQL)
web	apelon.com	Apelon Terminology Query Language (TQL)
web	infocentral.infoway-inforoute.ca	Examples of a Code System Supplement include pCLOCD , but can also be as simple as frequency counts that describe usage statistics for concepts in a particular context. Because this supplemental information can be directly tied to individual concepts, Code System Supplements can be used as part of a Value Set Definition Content Expression to determine Value Set Expansion Code Set membership. Code System Supplements must have some sort of identifying information so that they may be uniquely identified and accessed and must identify the Code System to which they are associated.
web	www.rfc-editor.org	The intention is to use the IETF language tags preference referenced by the current RFC for BCP 47 .

Type

Reference

Content

web

github.com

Terminology Fundamentals, published by HL7 International / Terminology Infrastructure. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/terminology-fundamentals-ig/ and changes regularly. See the Directory of published versions

web

confluence.ihtsdotools.org

SNOMED CT Expression Constraint Language (ECL)

web

en.wikipedia.org

Structured Query Language (SQL)

web

apelon.com

Apelon Terminology Query Language (TQL)

web

infocentral.infoway-inforoute.ca

Examples of a Code System Supplement include pCLOCD , but can also be as simple as frequency counts that describe usage statistics for concepts in a particular context. Because this supplemental information can be directly tied to individual concepts, Code System Supplements can be used as part of a Value Set Definition Content Expression to determine Value Set Expansion Code Set membership. Code System Supplements must have some sort of identifying information so that they may be uniquely identified and accessed and must identify the Code System to which they are associated.

web

www.rfc-editor.org

The intention is to use the IETF language tags preference referenced by the current RFC for BCP 47 .

Internal Images

cld.png

vsdmodel.png

vstypes.png