Release 4

4.4.1.79 Value Set http://hl7.org/fhir/ValueSet/abstract-types

FHIR Infrastructure Work Group Maturity Level: NNormative (from v4.0.0) Use Context: Any

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/abstract-types
Version:4.0.1
Name:AbstractType
Title:AbstractType
Definition:

A list of the base types defined by this version of the FHIR specification - types that are defined, but for which only specializations actually are created.

Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.3.23 (for OID based terminology systems)
Source ResourceXML / JSON

This Value Set is normative - it is generated based on the information defined in this specification. The definition will remain fixed across versions, but the actual contents will change from version to version

This value set is not currently used

4.4.1.79.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.4.1.79.2 Expansion

This expansion generated 21 Jan 2021

This value set contains 2 concepts

Expansion based on http://hl7.org/fhir/abstract-types version 4.0.1

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

CodeDisplayDefinition
TypeTypeA place holder that means any kind of data type
AnyAnyA place holder that means any kind of resource

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
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). If the code is in italics, this indicates that the code is not selectable ('Abstract')
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