A structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the questionnaire being responded to.

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

The QuestionnaireResponse contains enough information about the questions asked and their organization that it can be interpreted somewhat independently from the Questionnaire it is based on. I.e. You don't need access to the Questionnaire in order to extract basic information from a QuestionnaireResponse.

A business identifier assigned to a particular completed (or partially completed) questionnaire.

Used for tracking, registration and other business purposes.

The order, proposal or plan that is fulfilled in whole or in part by this QuestionnaireResponse. For example, a ServiceRequest seeking an intake assessment or a decision support recommendation to assess for post-partum depression.

Supports traceability of responsibility for the action and allows linkage of an action to the recommendations acted upon.

A procedure or observation that this questionnaire was performed as part of the execution of. For example, the surgery a checklist was executed as part of.

Composition of questionnaire responses will be handled by the parent questionnaire having answers that reference the child questionnaire. For relationships to referrals, and other types of requests, use basedOn.

The Questionnaire that defines and organizes the questions for which answers are being provided.

Needed to allow editing of the questionnaire response in a manner that enforces the constraints of the original form.

If a QuestionnaireResponse references a Questionnaire, then the QuestionnaireResponse structure must be consistent with the Questionnaire (i.e. questions must be organized into the same groups, nested questions must still be nested, etc.).

The position of the questionnaire response within its overall lifecycle.

The information on Questionnaire resources may possibly be gathered during multiple sessions and altered after considered being finished.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

The subject of the questionnaire response. This could be a patient, organization, practitioner, device, etc. This is who/what the answers apply to, but is not necessarily the source of information.

Allows linking the answers to the individual the answers describe. May also affect access control.

If the Questionnaire declared a subjectType, the resource pointed to by this element must be an instance of one of the listed types.

The encounter or episode of care with primary association to the questionnaire response.

Provides context for the information that was captured. May also affect access control.

A questionnaire that was initiated during an encounter but not fully completed during the encounter would still generally be associated with the encounter.

The date and/or time that this set of answers were last changed.

Clinicians need to be able to check the date that the information in the questionnaire was collected, to derive the context of the answers.

May be different from the lastUpdateTime of the resource itself, because that reflects when the data was known to the server, not when the data was captured.

This element is optional to allow for systems that might not know the value, however it SHOULD be populated if possible.

Person who received the answers to the questions in the QuestionnaireResponse and recorded them in the system.

Need to know who interpreted the subject's answers to the questions in the questionnaire, and selected the appropriate options for answers.

Mapping a subject's answers to multiple choice options and determining what to put in the textual answer is a matter of interpretation. Authoring by device would indicate that some portion of the questionnaire had been auto-populated.

The person who answered the questions about the subject.

When answering questions about a subject that is minor, incapable of answering or an animal, another human source may answer the questions.

If not specified, no inference can be made about who provided the data.

A group or question item from the original questionnaire for which answers are provided.

Groups cannot have answers and therefore must nest directly within item. When dealing with questions, nesting must occur within each answer because some questions may have multiple answers (and the nesting occurs for each answer).

The item from the Questionnaire that corresponds to this item in the QuestionnaireResponse resource.

Items can repeat in the answers, so a direct 1..1 correspondence by position might not exist - requiring correspondence by identifier.

A reference to an ElementDefinition that provides the details for the item.

A common pattern is to define a set of data elements, and then build multiple different questionnaires for different circumstances to gather the data. This element provides traceability to the common definition.

The ElementDefinition must be in a StructureDefinition, and must have a fragment identifier that identifies the specific data element by its id (Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x].

There is no need for this element if the item pointed to by the linkId has a definition listed.

Text that is displayed above the contents of the group or as the text of the question being answered.

Allows the questionnaire response to be read without access to the questionnaire.

More specific subject this section's answers are about, details the subject given in QuestionnaireResponse.

Sometimes a group of answers is about a specific participant, artifact or piece of information in the patient's care or record, e.g. a specific Problem, RelatedPerson, Allergy etc.

The respondent's answer(s) to the question.

The value is nested because we cannot have a repeating structure that has variable type.

The answer (or one of the answers) provided by the respondent to the question.

Ability to retain a single-valued answer to a question.

More complex structures (Attachment, Resource and Quantity) will typically be limited to electronic forms that can expose an appropriate user interface to capture the components and enforce the constraints of a complex data type. Additional complex types can be introduced through extensions.

Nested groups and/or questions found within this particular answer.

It is useful to have "sub-questions", questions which normally appear when certain answers are given and which collect additional details.

Questions or sub-groups nested beneath a question or group.

Reports can consist of complex nested groups.