Release 4 5 Preview #2
This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

4.4.1.440 4.4.1.470 Value Set http://hl7.org/fhir/ValueSet/item-type

FHIR Infrastructure Work Group   Maturity Level : 3 Trial Use Use Context : Any

This is a value set defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/ValueSet/item-type
Version: 4.0.1 4.4.0
Name: QuestionnaireItemType
Title: QuestionnaireItemType
Definition:

Distinguishes groups from questions and display text and indicates data type for questions.

Committee: FHIR Infrastructure Work Group
OID: 2.16.840.1.113883.4.642.3.444 (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 01 Nov 2019 04 Jun 2020


This value set contains 16 concepts

Expansion based on http://hl7.org/fhir/item-type version 4.0.1 QuestionnaireItemType v4.4.0 (CodeSystem)

All codes from system http://hl7.org/fhir/item-type
Lvl Code Display Definition
0 group Group An item with no direct answer but should have at least one child item.
0 display Display Text for display that will not capture an answer or have child items.
0 question Question An item that defines a specific answer to be captured, and which may have child items. (the answer provided in the QuestionnaireResponse should be of the defined datatype).
1    boolean Boolean Question with a yes/no answer (valueBoolean).
1    decimal Decimal Question with is a real number answer (valueDecimal).
1    integer Integer Question with an integer answer (valueInteger).
1    date Date Question with a date answer (valueDate).
1    dateTime Date Time Question with a date and time answer (valueDateTime).
1    time Time Question with a time (hour:minute:second) answer independent of date. (valueTime).
1    string String Question with a short (few words to short sentence) free-text entry answer (valueString).
1    text Text Question with a long (potentially multi-paragraph) free-text entry answer (valueString).
1    url Url Question with a URL (website, FTP site, etc.) answer (valueUri).
1    choice Choice Question with a Coding drawn from a list of possible answers (specified in either the answerOption property, or via the valueset referenced in the answerValueSet property) as an answer (valueCoding).
1    open-choice Open Choice Answer is a Coding drawn from a list of possible answers (as with the choice type) or a free-text entry in a string (valueCoding or valueString).
1    attachment Attachment Question with binary content such as an image, PDF, etc. as an answer (valueAttachment).
1    reference Reference Question with a reference to another resource (practitioner, organization, etc.) as an answer (valueReference).
1    quantity Quantity Question with a combination of a numeric value and unit, potentially with a comparator (<, >, etc.) as an answer. (valueQuantity) There is an extension 'http://hl7.org/fhir/StructureDefinition/questionnaire-unit' that can be used to define what unit should be captured (or the unit that has a ucum conversion from the provided unit).

 

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


Explanation of the columns that may appear on this page:

Lvl A 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
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). If the code is in italics, this indicates that the code is not selectable ('Abstract')
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