STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). 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

4.3.1.data-types Value Set http://hl7.org/fhir/ValueSet/data-types

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 ResourceXML / JSON

This value set is used in the following places:

  • This value set is the designated 'entire code system' value set for DataType

This value set includes codes from the following code systems:

 

This expansion generated 06 Dec 2016


This value set contains 54 concepts

Expansion based on http://hl7.org/fhir/data-types version 1.8.0

All codes from system http://hl7.org/fhir/data-types

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 and which might not be valid for mail delivery. There are a variety of postal address formats defined around the world.
AgeAgeA duration of time during which an organism (or a process) has existed.
AnnotationAnnotationA text note which also contains information about who made the statement and when.
AttachmentAttachmentFor referring to data content defined in other formats.
BackboneElementBackboneElementBase definition for all elements that are defined inside a resource - but not those in a data type.
CodeableConceptCodeableConceptA concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
CodingCodingA reference to a code defined by a terminology system.
ContactDetailContactDetailSpecifies contact information for a person or organization.
ContactPointContactPointDetails for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc.
ContributorContributorA contributor to the content of a knowledge asset, including authors, editors, reviewers, and endorsers.
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.
DataRequirementDataRequirementDescribes a required data item for evaluation in terms of the type of data, and optional code- or date-based filters of the data.
DistanceDistanceA length - a value with a unit that is a physical distance.
DosageInstructionDosageInstructionIndicates how the medication is to be used by the patient.
DurationDurationA length of time.
ElementElementBase definition for all elements in a resource.
ElementDefinitionElementDefinitionCaptures constraints on each element within the resource, profile, or extension.
ExtensionExtensionOptional Extensions Element - found in all resources.
HumanNameHumanNameA human's name with the ability to identify parts and usage.
IdentifierIdentifierA technical identifier - identifies some entity uniquely and unambiguously.
MetaMetaThe 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.
MoneyMoneyAn amount of economic utility in some recognised currency.
NarrativeNarrativeA human-readable formatted text, including images.
ParameterDefinitionParameterDefinitionThe 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.
PeriodPeriodA time period defined by a start and end date and optionally time.
QuantityQuantityA 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.
RangeRangeA set of ordered Quantities defined by a low and high limit.
RatioRatioA relationship of two Quantity values - expressed as a numerator and a denominator.
ReferenceReferenceA reference from one resource to another.
RelatedArtifactRelatedArtifactRelated artifacts such as additional documentation, justification, or bibliographic references.
SampledDataSampledDataA series of measurements taken by a device, with upper and lower limits. There may be more than one dimension in the data.
SignatureSignatureA 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.
SimpleQuantitySimpleQuantity
TimingTimingSpecifies 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.
TriggerDefinitionTriggerDefinitionA description of a triggering event.
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).
base64Binarybase64BinaryA stream of bytes
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
datedateA 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.
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.
decimaldecimalA rational number with implicit precision
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.
instantinstantAn instant in time - known at least to the second
integerintegerA whole number
markdownmarkdownA string that may contain markdown syntax for optional processing by a mark down presentation engine
oidoidAn oid represented as a URI
positiveIntpositiveIntAn integer with a value that is positive (e.g. >0)
stringstringA sequence of Unicode characters
timetimeA time during the day, with no date specified
unsignedIntunsignedIntAn integer with a value that is not negative (e.g. >= 0)
uriuriString of characters used to identify a name or a resource
uuiduuidA UUID, represented as a URI
xhtmlXHTMLXHTML 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:

LevelA 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
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance)
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code