This view acts on the QuestionnaireResponse resource to produce a table named "questionnaire_response_items".

The table contains the following columns:

Selection Rules:

Item	Coll	Type	Description
questionnaire_response_items		QuestionnaireResponse
questionnaire_response_items / Select
questionnaire_response_items / Select / id			getResourceKey() Unique questionnaire response identifier
questionnaire_response_items / Select / questionnaire			questionnaire Canonical URL of the questionnaire
questionnaire_response_items / Select / patient_id			subject.getReferenceKey(Patient) Patient identifier
questionnaire_response_items / Select / authored			authored Date and time the response was authored
questionnaire_response_items / Select
questionnaire_response_items / Select / item_link_id			linkId Unique identifier for this item within the questionnaire
questionnaire_response_items / Select / item_text			text Question text
questionnaire_response_items / Select / Select			for each answer, or null
questionnaire_response_items / Select / Select / answer_value_string			value.ofType(string) String answer value
questionnaire_response_items / Select / Select / answer_value_integer			value.ofType(integer) Integer answer value
questionnaire_response_items / Select / Select / answer_value_boolean			value.ofType(boolean) Boolean answer value
questionnaire_response_items / Select / Select / answer_value_date			value.ofType(date) Date answer value

This will result in a "questionnaire_response_items" table that looks like this:

Note how all items are flattened into a single table regardless of their nesting depth. The "demographics" and "conditions" items are group items (with no answer values), while items like "name", "dob", "diabetes", and "hypertension" are nested within those groups but appear as separate rows in the output. The "diabetes-type" item is nested under the answer to "diabetes" rather than under an item, and is reached through the answer.item path in repeat.