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

ValueSet: Type Characteristic Codes Value Set

Official URL: http://hl7.org/fhir/ValueSet/type-characteristics-code Version: 5.2.0-ballot
Standards status: Trial-use Maturity Level: 2 Computable Name: TypeCharacteristicCodes
Other Identifiers: OID:2.16.840.1.113883.4.642.3.2986

Description Needed Here

References

Changes since version 1.0.0:

  • The resource metadata has changed (title)

    • Logical Definition (CLD)

    Generated Narrative: ValueSet type-characteristics-code

    Last updated: 2023-01-31 07:07:38+1100

    Profile: Shareable ValueSet

     

    Expansion

    Generated Narrative: ValueSet

    Last updated: 2023-01-31 07:07:38+1100

    Profile: Shareable ValueSet

    Expansion based on codesystem Type Characteristic Codes System v5.2.0-ballot (CodeSystem)

    This value set contains 9 concepts

    LevelCodeSystemDisplayDefinition
    1  has-targethttp://hl7.org/fhir/type-characteristics-codeHas Target

    The type is reference to external content else where that can have a type. This is associated with the use of ElementDefinition.type.targetProfile

    1  has-rangehttp://hl7.org/fhir/type-characteristics-codeHas Range

    The type has a value domain that is a range, and can be associated with allowable min/max values on it's ElementDefinitions

    2    is-continuoushttp://hl7.org/fhir/type-characteristics-codeIs Continuous

    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)

    1  has-lengthhttp://hl7.org/fhir/type-characteristics-codeHas Length

    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

    1  has-sizehttp://hl7.org/fhir/type-characteristics-codeHas Size

    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

    1  can-bindhttp://hl7.org/fhir/type-characteristics-codeCan Bind

    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

    1  has-unitshttp://hl7.org/fhir/type-characteristics-codeHas Units

    The content has units of measure (UCUM, by implication) and it may be useful to constrain the units by some valueset

    1  do-translationshttp://hl7.org/fhir/type-characteristics-codeDo Translations

    The content is uncontrolled human readable text that may make sense to translate

    1  can-be-targethttp://hl7.org/fhir/type-characteristics-codeCan Be Target

    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

    Explanation of the columns that may appear on this page:

    Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
    System The source of the definition of the code (when the value set draws in codes defined elsewhere)
    Code The code (used as the code in the resource instance)
    Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
    Definition An explanation of the meaning of the concept
    Comments Additional notes about how to use the code