FHIR Extensions Pack
5.2.0-ballot - 5.2.0 Ballot - September 2024) International flag

FHIR Extensions Pack, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 5.2.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-extensions/ and changes regularly. See the Directory of published versions

: Type Characteristic Codes System - XML Representation

Page standards status: Trial-use Maturity Level: 2

Raw xml | Download


<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="type-characteristics-code"/>
  <meta>
    <lastUpdated value="2023-01-31T07:07:38.434+11:00"/>
    <profile
             value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem type-characteristics-code</b></p><a name="type-characteristics-code"> </a><a name="hctype-characteristics-code"> </a><a name="type-characteristics-code-en-US"> </a><div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Last updated: 2023-01-31 07:07:38+1100</p><p style="margin-bottom: 0px">Profile: <a href="http://hl7.org/fhir/R5/shareablecodesystem.html">Shareable CodeSystem</a></p></div><p>This case-sensitive code system <code>http://hl7.org/fhir/type-characteristics-code</code> defines the following codes in a Is-A hierarchy:</p><table class="codes"><tr><td><b>Lvl</b></td><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td>1</td><td style="white-space:nowrap">has-target<a name="type-characteristics-code-has-target"> </a></td><td>Has Target</td><td>The type is reference to external content else where that can have a type. This is associated with the use of ElementDefinition.type.targetProfile</td></tr><tr><td>1</td><td style="white-space:nowrap">has-range<a name="type-characteristics-code-has-range"> </a></td><td>Has Range</td><td>The type has a value domain that is a range, and can be associated with allowable min/max values on it's ElementDefinitions</td></tr><tr><td>2</td><td style="white-space:nowrap">  is-continuous<a name="type-characteristics-code-is-continuous"> </a></td><td>Is Continuous</td><td>The type is a continuous distribution. These types have issues associated with precision and equality, and can have a specified number of max decimal places (via an extension)</td></tr><tr><td>1</td><td style="white-space:nowrap">has-length<a name="type-characteristics-code-has-length"> </a></td><td>Has Length</td><td>The type has variable length and be constrained by it's length. In principle, any type can be constrained by the number of characters to represent it, but this is not meaningful for numbers or attachments</td></tr><tr><td>1</td><td style="white-space:nowrap">has-size<a name="type-characteristics-code-has-size"> </a></td><td>Has Size</td><td>The type can be constrained by the number of bytes it takes to represent the content. This is usually applied to content that is compressed or interpreted, and there's no fixed relationship between the number of bytes of content, and the number of characters it represents</td></tr><tr><td>1</td><td style="white-space:nowrap">can-bind<a name="type-characteristics-code-can-bind"> </a></td><td>Can Bind</td><td>The type can be bound to a terminology. Note that a classic binding has system|version|code|display, but not all bindable types carry all four of these, and how they are bound varies, so an additional extension is required to enable tools to work with this content</td></tr><tr><td>1</td><td style="white-space:nowrap">has-units<a name="type-characteristics-code-has-units"> </a></td><td>Has Units</td><td>The content has units of measure (UCUM, by implication) and it may be useful to constrain the units by some valueset</td></tr><tr><td>1</td><td style="white-space:nowrap">do-translations<a name="type-characteristics-code-do-translations"> </a></td><td>Do Translations</td><td>The content is uncontrolled human readable text that may make sense to translate</td></tr><tr><td>1</td><td style="white-space:nowrap">can-be-target<a name="type-characteristics-code-can-be-target"> </a></td><td>Can Be Target</td><td>The content has an identify and can be persisted with an appropriate life cycle such that it can be the target of a reference from a resource or another logical model</td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="2"/>
  </extension>
  <url value="http://hl7.org/fhir/type-characteristics-code"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.4.642.4.1901"/>
  </identifier>
  <version value="5.2.0-ballot"/>
  <name value="TypeCharacteristicCodes"/>
  <title value="Type Characteristic Codes System"/>
  <status value="draft"/>
  <experimental value="false"/>
  <date value="2024-11-17T19:59:58+00:00"/>
  <publisher value="HL7 International / FHIR Infrastructure"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/fiwg"/>
    </telecom>
  </contact>
  <description value="Type Characteristic Codes"/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
    </coding>
  </jurisdiction>
  <caseSensitive value="true"/>
  <hierarchyMeaning value="is-a"/>
  <content value="complete"/>
  <concept>
    <code value="has-target"/>
    <display value="Has Target"/>
    <definition
                value="The type is reference to external content else where that can have a type. This is associated with the use of ElementDefinition.type.targetProfile"/>
  </concept>
  <concept>
    <code value="has-range"/>
    <display value="Has Range"/>
    <definition
                value="The type has a value domain that is a range, and can be associated with allowable min/max values on it's ElementDefinitions"/>
    <concept>
      <code value="is-continuous"/>
      <display value="Is Continuous"/>
      <definition
                  value="The type is a continuous distribution. These types have issues associated with precision and equality, and can have a specified number of max decimal places (via an extension)"/>
    </concept>
  </concept>
  <concept>
    <code value="has-length"/>
    <display value="Has Length"/>
    <definition
                value="The type has variable length and be constrained by it's length. In principle, any type can be constrained by the number of characters to represent it, but this is not meaningful for numbers or attachments"/>
  </concept>
  <concept>
    <code value="has-size"/>
    <display value="Has Size"/>
    <definition
                value="The type can be constrained by the number of bytes it takes to represent the content. This is usually applied to content that is compressed or interpreted, and there's no fixed relationship between the number of bytes of content, and the number of characters it represents"/>
  </concept>
  <concept>
    <code value="can-bind"/>
    <display value="Can Bind"/>
    <definition
                value="The type can be bound to a terminology. Note that a classic binding has system|version|code|display, but not all bindable types carry all four of these, and how they are bound varies, so an additional extension is required to enable tools to work with this content"/>
  </concept>
  <concept>
    <code value="has-units"/>
    <display value="Has Units"/>
    <definition
                value="The content has units of measure (UCUM, by implication) and it may be useful to constrain the units by some valueset"/>
  </concept>
  <concept>
    <code value="do-translations"/>
    <display value="Do Translations"/>
    <definition
                value="The content is uncontrolled human readable text that may make sense to translate"/>
  </concept>
  <concept>
    <code value="can-be-target"/>
    <display value="Can Be Target"/>
    <definition
                value="The content has an identify and can be persisted with an appropriate life cycle such that it can be the target of a reference from a resource or another logical model"/>
  </concept>
</CodeSystem>