Release 4B Ballot #1

This page is part of the FHIR Specification v4.1.0: R4B Ballot. About the R4B version of FHIR. 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

4.3.14.209 Code System http://hl7.org/fhir/item-type

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

This is a code system defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/item-type
Version:4.1.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.4.445 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

  • ValueSet: QuestionnaireItemType (Distinguishes groups from questions and display text and indicates data type for questions.)

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

Properties

Code URL Description Type
notSelectable http://hl7.org/fhir/concept-properties#notSelectable Indicates that the code is abstract - only intended to be used as a selector for other concepts boolean

This code system http://hl7.org/fhir/item-type defines the following codes:

Lvl Code Display Definition
1 group Group An item with no direct answer but should have at least one child item.
1 display Display Text for display that will not capture an answer or have child items.
1 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).
2   boolean Boolean Question with a yes/no answer (valueBoolean).
2   decimal Decimal Question with is a real number answer (valueDecimal).
2   integer Integer Question with an integer answer (valueInteger).
2   date Date Question with a date answer (valueDate).
2   dateTime Date Time Question with a date and time answer (valueDateTime).
2   time Time Question with a time (hour:minute:second) answer independent of date. (valueTime).
2   string String Question with a short (few words to short sentence) free-text entry answer (valueString).
2   text Text Question with a long (potentially multi-paragraph) free-text entry answer (valueString).
2   url Url Question with a URL (website, FTP site, etc.) answer (valueUri).
2   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).
2   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).
2   attachment Attachment Question with binary content such as an image, PDF, etc. as an answer (valueAttachment).
2   reference Reference Question with a reference to another resource (practitioner, organization, etc.) as an answer (valueReference).
2   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 code systems 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. 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