Release 5 Ballot

This page is part of the FHIR Specification (v5.0.0-ballot: R5 Ballot - see ballot notes). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

Example CodeSystem/type-characteristics-code (XML)

FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: Informative

Raw XML (canonical form + also see XML Format Specification)

Definition for Code SystemTypeCharacteristicCodes

<?xml version="1.0" encoding="UTF-8"?>

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="type-characteristics-code"/> 
  <meta> 
    <lastUpdated value="2022-09-10T04:52:37.223+10:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> This code system 
        <code> http://hl7.org/fhir/type-characteristics-code</code>  defines the following codes:
      </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|d
            isplay, 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> 
      </table> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/> 
  </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.0.0-ballot"/> 
  <name value="TypeCharacteristicCodes"/> 
  <title value="Type Characteristic Codes"/> 
  <status value="active"/> 
  <experimental value="false"/> 
  <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|d
    isplay, 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> 
</CodeSystem> 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.