FHIR Cross-Version Extensions package for FHIR R4B from FHIR R4
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R4B from FHIR R4 - Version 0.0.1-snapshot-2. See the Directory of published versions

ValueSet: Cross-version VS for R4.DataType for use in FHIR R4B

Official URL: http://hl7.org/fhir/4.0/ValueSet/R4-data-types-for-R4B Version: 0.0.1-snapshot-2
Standards status: Informative Maturity Level: 5 Computable Name: R4_data_types_for_R4B

This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/data-types 4.0.1 for use in FHIR R4B. Concepts not present here have direct equivalent mappings crossing all versions from R4 to R4B.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

  • Include these codes as defined in http://hl7.org/fhir/data-types version 4.0.1
    CodeDisplayDefinition
    AddressAddressAn address expressed using postal conventions (as opposed to GPS or other location definition formats). This data type may be used to convey addresses for use in delivering mail as well as for visiting locations which might not be valid for mail delivery. There are a variety of postal address formats defined around the world.
    AnnotationAnnotationA text note which also contains information about who made the statement and when.
    BackboneElementBackboneElementBase definition for all elements that are defined inside a resource - but not those in a data type.
    CodingCodingA reference to a code defined by a terminology system.
    ContactPointContactPointDetails for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.
    CountCountA measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies.
    DistanceDistanceA length - a value with a unit that is a physical distance.
    SubstanceAmountSubstanceAmount
    TimingTimingSpecifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.
    UsageContextUsageContextSpecifies clinical/business/etc. metadata that can be used to retrieve, index and/or categorize an artifact. This metadata can either be specific to the applicable population (e.g., age category, DRG) or the specific context of care (e.g., venue, care setting, provider of care).
    booleanbooleanValue of "true" or "false"
    codecodeA string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
    dateTimedateTimeA date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
    ididAny combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
    integerintegerA whole number

 

Expansion

This value set expansion contains 15 concepts.

CodeSystemDisplayDefinition
  Addresshttp://hl7.org/fhir/data-typesAddressAn address expressed using postal conventions (as opposed to GPS or other location definition formats). This data type may be used to convey addresses for use in delivering mail as well as for visiting locations which might not be valid for mail delivery. There are a variety of postal address formats defined around the world.
  Annotationhttp://hl7.org/fhir/data-typesAnnotationA text note which also contains information about who made the statement and when.
  BackboneElementhttp://hl7.org/fhir/data-typesBackboneElementBase definition for all elements that are defined inside a resource - but not those in a data type.
  Codinghttp://hl7.org/fhir/data-typesCodingA reference to a code defined by a terminology system.
  ContactPointhttp://hl7.org/fhir/data-typesContactPointDetails for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.
  Counthttp://hl7.org/fhir/data-typesCountA measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies.
  Distancehttp://hl7.org/fhir/data-typesDistanceA length - a value with a unit that is a physical distance.
  SubstanceAmounthttp://hl7.org/fhir/data-typesSubstanceAmount
  Timinghttp://hl7.org/fhir/data-typesTimingSpecifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.
  UsageContexthttp://hl7.org/fhir/data-typesUsageContextSpecifies clinical/business/etc. metadata that can be used to retrieve, index and/or categorize an artifact. This metadata can either be specific to the applicable population (e.g., age category, DRG) or the specific context of care (e.g., venue, care setting, provider of care).
  booleanhttp://hl7.org/fhir/data-typesbooleanValue of "true" or "false"
  codehttp://hl7.org/fhir/data-typescodeA string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
  dateTimehttp://hl7.org/fhir/data-typesdateTimeA date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
  idhttp://hl7.org/fhir/data-typesidAny combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
  integerhttp://hl7.org/fhir/data-typesintegerA whole number

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