A structured set of questions intended to guide the collection of answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the underlying questions. A structured set of questions intended to guide the collection of answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the underlying questions.

To support structured, hierarchical registration of data gathered using digital forms and other questionnaires. To support structured, hierarchical registration of data gathered using digital forms and other questionnaires.

An absolute URL that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this questionnaire is (or will be) published.

This records identifiers associated with this question set that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation). This records identifiers associated with this question set that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).

Need to allow connection to a wider workflow. Need to allow connection to a wider workflow.

The version number assigned by the publisher for business reasons. It may remain the same when the resource is updated. The version number assigned by the publisher for business reasons. It may remain the same when the resource is updated.

In some cases, separate resource instances might be created for each version (if an older version can be maintained once a new version exists). In some cases, separate resource instances might be created for each version (if an older version can be maintained once a new version exists).

The lifecycle status of the questionnaire as a whole. The lifecycle status of the questionnaire as a whole.

The date that this questionnaire was last changed. The date that this questionnaire was last changed.

Organization or person responsible for developing and maintaining the questionnaire. Organization or person responsible for developing and maintaining the questionnaire.

Conveys responsibility for the questions and their organization and also helps evaluate the questionnaire's "authority". Conveys responsibility for the questions and their organization and also helps evaluate the questionnaire's "authority".

Contact details to assist a user in finding and communicating with the publisher. Contact details to assist a user in finding and communicating with the publisher.

Identifies the types of subjects that can be the subject of the questionnaire. A code that identifies the questionnaire as falling into a particular group of like questionnaires; e.g. "Pediatric", "Admissions", "Research", "Demographic", "Opinion Survey", etc.

Allows discovery of questionnaires. Also allows organization of lists of questionnaires into groups for presentation.

If none are specified, then the subject is unlimited. The name or label associated with this questionnaire.

A collection of related questions (or further groupings of questions). Used for display, searching.

Need to be able to logically group answers to grouped questions. Identifies a how this question or group of questions is known in a particular terminology such as LOINC.

Allows linking of the complete Questionnaire resources to formal terminologies. It's common for "pannels" of questions to be identified by a code.

An identifier that is unique within the Questionnaire allowing linkage to the equivalent group in a QuestionnaireResponse resource. Identifies the types of subjects that can be the subject of the questionnaire.

If none are specified, then the subject is unlimited.

May be omitted if there is no expectation to link answers back to a questionnaire. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning. GUIDs or sequential numbers are appropriate here. The questions and groupings of questions that make up the questionnaire.

The human-readable name for this section of the questionnaire. An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource.

When including text for the questionnaire with the answers, sections may have a section header. Summary true QuestionnaireResponse does not require omitted items to be included and may have some items that repeat, so linkage based on position alone is not sufficient.

The title of the "root" group is the title for the questionnaire. May be omitted if there is no expectation to link answers back to a Questionnaire. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning. GUIDs or sequential numbers are appropriate here.

Identifies a how this group of questions is known in a particular terminology such as LOINC. Identifies a how this group of questions is known in a particular terminology such as LOINC.

Allows linking of groups of questions (and complete Questionnaire resources) to formal terminologies. Allows linking of groups of questions (and complete Questionnaire resources) to formal terminologies.

The code(s) for the "root" group apply to the questionnaire as a whole. The code(s) for the "root" group apply to the questionnaire as a whole.

Additional text for the group, used for display purposes. A short label for a particular group, question or set of display text within the questionnaire.

When including text for the questionnaire, each section may contain additional explanations are background text. Separating the label from the question text allows improved rendering. Also, instructions will often refer to specific prefixes, so there's a need for the questionnaire design to have control over what labels are used.

Common extensions are defined for more specialized types of display text. These are generally unique within a questionnaire, though this is not guaranteed. Some questionnaires may have multiple questions with the same label with logic to control which gets exposed.

Typically these won't be used for "text" items, though such use is not prohibited.

Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.

If true, indicates that the group must be present and have required questions within it answered. If false, the group may be skipped when answering the questionnaire. The name of a section, the text of a question or text content for a text item.

Whether the group may occur multiple times in the instance, containing multiple sets of answers. Identifies the type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.).

Defines the format in which the user is to be prompted for the answer.

Groups may be used to create set of (related) questions that can be repeated to give multiple answers to such a set. Additional constraints on the type of answer can be conveyed by extensions.

A sub-group within a group. The ordering of groups within this group is relevant. If present, indicates that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true.

Allows questionnaires to adapt based on answers to other questions; e.g. If physical gender is specified as a male, no need to capture pregnancy history. Also allows conditional display of instructions or groups of questions.

Reports can consist of complex nested groups. If multiple repetitions of this extension are present, the item should be enabled when the condition for any of the repetitions is true. I.e. Treat "enableWhen"s as being joined by an "or" clause.

If enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met.

Set of questions within this group. The order of questions within the group is relevant. The linkId for the question whose answer (or lack of answer) governs whether this item is enabled.

If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.

An identifier that is unique within the questionnaire allowing linkage to the equivalent group in a QuestionnaireResponse resource. If present, indicates that this item should be enabled only if the specified question is answered or not answered.

If answered=false and answer values are also provided, then they are treated as "or". I.e. "Enable if the question is unanswered or the answer is one of the specified values". If answered=true and answers are present, one of the specified answers must be met. (So there's little reason to specify answered=true if answers are present.).

Identifies a how this question is known in a particular terminology such as LOINC. If present, then the answer for the referenced question must match this answer for all components present in the enableWhen.answer.

Components not specified in the answer do not need to match. For example, if enableWhen specifies code + system for a Coding, it's ok if the answer has a "display" element.

The dataType of this element must be the same as the data type of the question being referenced.

The actual question as shown to the user to prompt them for an answer. If true, indicates that the item must be present in a "completed" QuestionnaireResponse. If false, the item may be skipped when answering the questionnaire.

If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element).

The expected format of the answer, e.g. the type of input (string, integer) or whether a (multiple) choice is expected. Whether the item may occur multiple times in the instance, containing multiple sets of answers.

Defines the format in which the user is to be prompted for the answer. Items may be used to create set of (related) questions that can be repeated to give multiple answers to such a set.

If true, indicates that the question must be answered and have required groups within it also present. If false, the question and any contained groups may be skipped when answering the questionnaire. If true, the value cannot be changed by a human respondent to the Questionnaire.

Allows certain information to be phrased (and rendered) as a question and an answer, while keeping users from changing it. May also be useful for preventing changes to pre-populated portions of a questionnaire, for calculated values, etc.

The value of readOnly elements can be established by asserting extensions for defaultValues, linkages that support pre-population and/or extensions that support calculation based on other answers.

If true, the question may have more than one answer. The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse.

Used for "check all that apply" types of questions or "list your top 3", etc. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data.

Reference to a value set containing a list of codes representing permitted answers for the question. Reference to a value set containing a list of codes representing permitted answers for the question.

LOINC defines many useful value sets for questionnaire response. See LOINC Answer Lists LOINC defines many useful value sets for questionnaire response. See LOINC Answer Lists .

For a "choice" question, identifies one of the permitted answers for the question.

For a "choice" question, identifies one of the permitted answers for the question. Identifies a specific answer that's allowed as the answer to a question.

The value that should be pre-populated when rendering the questionnaire for user input.

In some workflows, having defaults saves time.

Nested group, containing nested question for this question. The order of groups within the question is relevant. Allows text, questions and other groups to be nested beneath a question or group.

It is useful to have "sub-questions", questions which normally appear when certain answers are given and which collect additional details. Reports can consist of complex nested groups.