This page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/data-types |
Name: | DataType |
Definition: | The type of an element - one of the FHIR data types. |
Committee: | FHIR Infrastructure Work Group |
OID: | 2.16.840.1.113883.4.642.2.data-types (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
This value set includes codes from the following code systems:
This expansion generated 11 Aug 2016
This value set contains 53 concepts
All codes from system http://hl7.org/fhir/data-types
Code | Display | Definition |
Address | Address | An 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 and which might not be valid for mail delivery. There are a variety of postal address formats defined around the world. |
Age | Age | A duration of time during which an organism (or a process) has existed. |
Annotation | Annotation | A text note which also contains information about who made the statement and when. |
Attachment | Attachment | For referring to data content defined in other formats. |
BackboneElement | BackboneElement | Base definition for all elements that are defined inside a resource - but not those in a data type. |
CodeableConcept | CodeableConcept | A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. |
Coding | Coding | A reference to a code defined by a terminology system. |
ContactDetail | ContactDetail | Specifies contact information for a person or organization. |
ContactPoint | ContactPoint | Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc. |
Contributor | Contributor | A contributor to the content of a knowledge asset, including authors, editors, reviewers, and endorsers. |
Count | Count | A 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. |
DataRequirement | DataRequirement | Describes a required data item for evaluation in terms of the type of data, and optional code- or date-based filters of the data. |
Distance | Distance | A length - a value with a unit that is a physical distance. |
Duration | Duration | A length of time. |
Element | Element | Base definition for all elements in a resource. |
ElementDefinition | ElementDefinition | Captures constraints on each element within the resource, profile, or extension. |
Extension | Extension | Optional Extensions Element - found in all resources. |
HumanName | HumanName | A human's name with the ability to identify parts and usage. |
Identifier | Identifier | A technical identifier - identifies some entity uniquely and unambiguously. |
Meta | Meta | The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. |
Money | Money | An amount of economic utility in some recognised currency. |
Narrative | Narrative | A human-readable formatted text, including images. |
ParameterDefinition | ParameterDefinition | The parameters to the module. This collection specifies both the input and output parameters. Input parameters are provided by the caller as part of the $evaluate operation. Output parameters are included in the GuidanceResponse. |
Period | Period | A time period defined by a start and end date and optionally time. |
Quantity | Quantity | A 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. |
Range | Range | A set of ordered Quantities defined by a low and high limit. |
Ratio | Ratio | A relationship of two Quantity values - expressed as a numerator and a denominator. |
Reference | Reference | A reference from one resource to another. |
RelatedResource | RelatedResource | Related resources such as additional documentation, justification, or bibliographic references. |
SampledData | SampledData | A series of measurements taken by a device, with upper and lower limits. There may be more than one dimension in the data. |
Signature | Signature | A digital signature along with supporting context. The signature may be electronic/cryptographic in nature, or a graphical image representing a hand-written signature, or a signature process. Different Signature approaches have different utilities. |
SimpleQuantity | SimpleQuantity | |
Timing | Timing | Specifies an event that may occur multiple times. Timing schedules are used to record when things are 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. |
TriggerDefinition | TriggerDefinition | A description of a triggering event. |
UsageContext | UsageContext | Specifies clinical metadata that can be used to retrieve, index and/or categorize the knowledge 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). |
base64Binary | base64Binary | A stream of bytes |
boolean | boolean | Value of "true" or "false" |
code | code | A 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 |
date | date | A date or partial date (e.g. just year or year + month). There is no time zone. The format is a union of the schema types gYear, gYearMonth and date. Dates SHALL be valid dates. |
dateTime | dateTime | A 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. |
decimal | decimal | A rational number with implicit precision |
id | id | Any 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. |
instant | instant | An instant in time - known at least to the second |
integer | integer | A whole number |
markdown | markdown | A string that may contain markdown syntax for optional processing by a mark down presentation engine |
oid | oid | An oid represented as a URI |
positiveInt | positiveInt | An integer with a value that is positive (e.g. >0) |
string | string | A sequence of Unicode characters |
time | time | A time during the day, with no date specified |
unsignedInt | unsignedInt | An integer with a value that is not negative (e.g. >= 0) |
uri | uri | String of characters used to identify a name or a resource |
uuid | uuid | A UUID, represented as a URI |
xhtml | XHTML | XHTML format, as defined by W3C, but restricted usage (mainly, no active content) |
See the full registry of value sets defined as part of FHIR.
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 |
Source | 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 |