---
type: "resource"
title: "QuestionnaireResponse"
resource: "QuestionnaireResponse"
---
# QuestionnaireResponse
## Introduction
## Scope and Usage
**QuestionnaireResponse** provides a complete or partial list of answers to a set of questions filled when responding to a questionnaire. The questions may be included directly or by reference to a [Questionnaire](questionnaire) resource that defines the questions as well as the constraints on the allowed answers. In some cases, both formal rules for editing the questionnaire (via link to [Questionnaire](questionnaire)) as well as sufficient local information to allow rendering of the questionnaire may be provided.
Each time a questionnaire is completed for a different subject or at a different time, a distinct QuestionnaireResponse is generated, though it may be possible for a previously entered set of answers to be edited or updated.
Questionnaire responses cover the need to communicate data originating from forms used in medical history examinations, research questionnaires and sometimes full clinical specialty records. In many systems this data is collected using user-defined screens and forms. Questionnaire responses record specifics about data capture - exactly what questions were asked, in what order, what answers were given, etc. Each of these questions is part of the Questionnaire, and as such the Questionnaire is a separately identifiable Resource, whereas the individual questions are not.
Examples of Questionnaires include:
- Past medical history (PMH)
- Family diseases
- Social history
- Research questionnaires and Case report forms (CRFs)
- Quality and evaluation forms
- Patient intake form (e.g. clipboard)
- Insurance claim form
**QuestionnaireResponse** resources can be validated against their corresponding [Questionnaire](questionnaire) to verify that required groups and questions are answered and that answers fit constraints in terms of cardinality, data type, etc.
## Boundaries and Relationships
The **QuestionnaireResponse** resource captures the responses to a questionnaire, while [Questionnaire](questionnaire) represents the definition of the questionnaire form, including what questions are asked, how they're organized and the constraints on the allowed answers.
While [Observation](observation), with its nested `component` structure, can create complex hierarchies of questions and answers, the focus is different. First, [Observation](observation) is used primarily for capturing data elements that are "true" observations - lab measurements, vital signs, social assessments, etc., while **QuestionnaireResponse** can be used to capture any types of data, including data that would typically map to other resources ([Procedure](procedure), [Patient](patient), [MedicationStatement](medicationstatement), etc.). Second, the focus of **QuestionnaireResponse** includes the specific phrasing and organization of the questions. All data must be explicitly captured as a question. With [Observation](observation), the focus is only on the meaning of the answer, not what question was asked (assuming a question was even asked at all). Additional information such as normal ranges, interpretation, date, etc., may also be captured.
## Background and Context
## Notes
## Notes
- QuestionnaireResponses can be authored by clinicians, patients, or patients' relatives (or even owners in the case of animals). Clinicians may author questionnaire responses, where the answers are provided by others on behalf of the patient. Additionally, information gathered on behalf of a patient may be about the patient's relatives (e.g. in family anamnesis). Therefore, QuestionnaireResponse makes a distinction between the author, the subject and the source of information.
- The QuestionnaireResponse's _encounter_ element can be used to link to the encounter when the questionnaire response was authored. This can be relevant since the encounter gives context to the answers and can be used to relate information in the QuestionnaireResponse to orders and observations that were done during the same Encounter.
- The QuestionnaireResponse's _language_ element can be used to indicate the language in which the patient completed the survey/questionnaire
- The order of questions within groups, groups within groups and groups within questions is relevant and must be retained for display and capture. The hierarchy of the items within the QuestionnaireResponse SHALL mirror the hierarchy of the items in the corresponding Questionnaire (if any).
- For use of QuestionnaireResponse.item.definition, see notes on [Questionnaire](questionnaire#definition)
- Because of the lack of explicit support for Questionnaires in [HL7 v3](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=186), [CDA](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7) Documents frequently used named sections with Observations to model questionnaires. Such use cases should now utilize the QuestionnaireResponse resource instead.
Refer to additional guidance provided in the [Questionnaire](questionnaire) resource dealing with the design of questionnaires.
### Links to Questionnaire
A `QuestionnaireResponse` may be stand-alone or may point to the definition of the questions in [Questionnaire](questionnaire). If the QuestionnaireResponse refers to a Questionnaire:
- 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 linkage between the questions and groups in the two resources is established using the `linkId` element
- LinkIds are unique across all items in a Questionnaire, but can sometimes appear multiple times within a QuestionnaireResponse if the corresponding item (or one of its ancestors) is allowed to repeat.
- When a QuestionnaireResponse references a Questionnaire, all the items in the questionnaire SHOULD be included in the QuestionnaireResponse if they are relevant to the interpretation of the answers, including items of type = `display`. When the QuestionnaireResponse is not yet marked as 'completed', this might also include items that are not [enabled](questionnaire-definitions#Questionnaire.item.enableWhen) based on what answers are currently present. However, once a QuestionnaireResponse is marked as "completed", the QuestionnaireResponse SHALL only include items that are 'enabled'. I.e. stuff that was perhaps answered through populate or user-action but subsequently got disabled due to other answers must not be included in a final QuestionnaireResponse.
The diagram above shows a Questionnaire with a hierarchy of group and question items, some marked as 'repeats'=true, and others false and with similar variation in 'required'=true and false. It also shows a hypothetical QuestionnaireResponse that is valid against that questionnaire with appropriate nesting of items and answers and linkIds showing the alignment between the Questionnaire and QuestionnaireResponse items.
### Validating QuestionnaireResponses
Rules imposed by a Questionnaire about expectations for answers are not expected to be met until a Questionnaire is deemed to be 'completed' (or 'amended'). For example, items that are marked as 'required' may be omitted, minimum numbers of answers might not be met, length requirement for answers, co-occurrence constraints, etc. might all be violated when the QuestionnaireResponse is still in the process of being completed. QuestionnaireResponses may be stored in this 'incomplete' state. Such QuestionnaireResponses might also include data for disabled questions, entries and text for non-answered questions, etc. However, once a QuestionnaireResponse is marked as 'completed' (including if it is subsequently changed to 'amended'), all requirements of the associated Questionnaire must be met, all non-answered question items must be removed, all non-enabled items must be removed, etc. (Display items MAY be retained. Certain extensions on the Questionnaire item may mandate that a display item needed for a human reviewer to interpret the QuestionnaireResponse be retained in a completed QuestionnaireResponse.)
### Nested Items
QuestioinnaireResponse has two different mechanisms to support nesting of items - `item.item` and `item.answer.item`. The former is used when nesting items within a 'group' and the latter is always used when nesting items within a question. This is because items nested within a question always nest within each _answer_ to the question. If the question allows multiple answers, each will have its own set of nested items.
### Security
QuestionnaireResponse resources can have answers with values of type Attachment. These attachments will typically be selected by the user answering the questionnaire and this selection may be done in an uncontrolled environment. Systems should ensure that the attachment is of the desired type and should take precautions before rendering or executing any attached content.
### Access Control
For most resources, the type of information that can be conveyed in the resource is determined by the resource, and the key attributes that determine the sensitivity level of the information are also known; e.g., drug, observation type, clinical trial randomization status, etc. However, for QuestionnaireResponse, the sensitivity of an instance is dependent on what type of Questionnaire it is associated with. And the data elements that determine that sensitivity could be the answers to any of the questions. This makes automatically enforcing access control rules more challenging. Designers should take these challenges into account and may need to place stricter access controls around QuestionnaireResponse to ensure that access to information is not granted improperly.
### Searching QuestionnaireResponses by answers
Until recently, there were no 'standard' SearchParameters defined to allow searching QuestionnaireResponse based on the answers within the response. A set of parameters have now been added. However, implementers using them should pay close attention to the following guidance:
- The meaning of answers in a QuestionnaireResponse is often contextual based on other answers within the form, making it very difficult (and potentially risky) to infer information from the inclusion of a QuestionnaireResponse in response to a search.
- When searching based on linkId, the search SHOULD also filter by the Questionnaire, and typically a specific version of the Questionnaire because linkIds can be re-used across forms and mean very different things.
- Searching for data in QuestionnaireResponses behaves in an opaque/proprietary way because Questionnaires are rarely standardized across organization. The best practice for making data accessible for search is therefore to [extract](https://hl7.org/fhir/uv/sdc/STU3/extraction.html) information from completed QuestionnaireResponses into other FHIR resources that are more standardized and can be better understood and searched for across organizations.
- Because of the complexity of indexing recursive data structures and the potential for large volumes of data elements, search parameters on linkId and answers might not be widely supported.
- Search on QuestionnaireResponses means that the server is often not aware of the 'meaning' of the data being searched or being returned. This makes applying access control policies, consent, etc. more difficult or even impossible.
### Profiling QuestionnaireResponses
It is possible to [profile](profiling) QuestionnaireResponse in the same way as any other resource. However, such profiling should not be used to constrain QuestionnaireResponse to only be able to capture the answers associated with a single type of form - that is what the [Questionnaire](questionnaire) resource is for. Profiling QuestionnaireResponse is appropriate when there's a need to enforce that certain metadata is always present, to indicate limitations on what types of answers can be handled, etc. - independent of what Questionnaire is being completed.
### FHIRPath Additions
When working with QuestionnaireResponses, there may be FHIRPath [expressions](metadatatypes#Expression) defined on the associated Questionnaire that will be evaluated in the context of the QuestionnaireResponse. The following additional guidance applies to using FHIRPath with QuestionnaireResponses:
- The `%resource` variable when it appears in expressions on elements in Questionnaire will be evaluated as the root of the QuestionnaireResponse.
- The `%context` variable will be set to the QuestionnaireResponse if the expression extension is defined on the Questionnaire root. Otherwise, it will be interpreted as the QuestionnaireResponse.item(s) whose linkId matches the linkId of the Questionnaire.item the expression extension was defined in. I.e. while the extensions and expressions are defined in the Questionnaire, they are evaluated in the context of the corresponding item(s) in the QuestionnaireResponse.
- All expressions that specify a 'name' can be accessed by other expressions appearing on the same item or any descendant item as though that name was part of context. The same is true for the 'name' element in the [launchContext extension](https://hl7.org/fhir/uv/sdc/STU3/StructureDefinition-sdc-questionnaire-launchContext.html). For example, a variable with the name 'score' could be accessed in FHIRPath or CQL using %score.
In addition, a couple of additional variables are defined for use with extensions evaluated in the context of a QuestionnaireResponse:
- `%questionnaire` corresponds to the Questionnaire resource resolved to by the QuestionnaireResponse.questionnaire element. It is in scope for all expressions defined in the Questionnaire.
- `%qitem` is defined as a shortcut to get to the Questionnaire.item that corresponds to the context QuestionnaireResponse.item (based on matching linkId). It is only valid for FHIRPath expressions defined within a Questionnaire item.
## StructureDefinition
### Elements (Simplified)
- **[QuestionnaireResponse](/questionnaireresponse-definitions#QuestionnaireResponse)** [0..*]: - A structured set of questions and their answers
- **[QuestionnaireResponse.identifier](/questionnaireresponse-definitions#QuestionnaireResponse.identifier)** [0..*]: [Identifier](/Identifier) Business identifier for this set of answers
- **[QuestionnaireResponse.basedOn](/questionnaireresponse-definitions#QuestionnaireResponse.basedOn)** [0..*]: [Reference(CarePlan](/Reference(CarePlan), [ServiceRequest)](/ServiceRequest)) Request fulfilled by this QuestionnaireResponse
- **[QuestionnaireResponse.partOf](/questionnaireresponse-definitions#QuestionnaireResponse.partOf)** [0..*]: [Reference(Observation](/Reference(Observation), [Procedure)](/Procedure)) Part of referenced event
- **[QuestionnaireResponse.questionnaire](/questionnaireresponse-definitions#QuestionnaireResponse.questionnaire)** [1..1]: [canonical](/canonical) Canonical URL of Questionnaire being answered
- **[QuestionnaireResponse.status](/questionnaireresponse-definitions#QuestionnaireResponse.status)** [1..1]: [code](/code) required:[questionnaire-answers-status](/valueset-questionnaire-answers-status) in-progress | completed | amended | entered-in-error | stopped
- **[QuestionnaireResponse.subject](/questionnaireresponse-definitions#QuestionnaireResponse.subject)** [0..1]: Reference([Resource](/Resource)) The subject of the questions
- **[QuestionnaireResponse.encounter](/questionnaireresponse-definitions#QuestionnaireResponse.encounter)** [0..1]: Reference([Encounter](/Encounter)) Encounter the questionnaire response is part of
- **[QuestionnaireResponse.authored](/questionnaireresponse-definitions#QuestionnaireResponse.authored)** [0..1]: [dateTime](/dateTime) Date the answers were gathered
- **[QuestionnaireResponse.author](/questionnaireresponse-definitions#QuestionnaireResponse.author)** [0..1]: [Reference(Device](/Reference(Device), [Practitioner](/Practitioner), [PractitionerRole](/PractitionerRole), [Patient](/Patient), [RelatedPerson](/RelatedPerson), [Organization](/Organization), [Group)](/Group)) The individual or device that received and recorded the answers
- **[QuestionnaireResponse.source](/questionnaireresponse-definitions#QuestionnaireResponse.source)** [0..1]: [Reference(Device](/Reference(Device), [Organization](/Organization), [Patient](/Patient), [Practitioner](/Practitioner), [PractitionerRole](/PractitionerRole), [RelatedPerson)](/RelatedPerson)) The individual or device that answered the questions
- **[QuestionnaireResponse.item](/questionnaireresponse-definitions#QuestionnaireResponse.item)** [0..*]: [BackboneElement](/BackboneElement) Groups and questions
- **[QuestionnaireResponse.item.linkId](/questionnaireresponse-definitions#QuestionnaireResponse.item.linkId)** [1..1]: [string](/string) Pointer to specific item from Questionnaire
- **[QuestionnaireResponse.item.definition](/questionnaireresponse-definitions#QuestionnaireResponse.item.definition)** [0..*]: [uri](/uri) ElementDefinition - details for the item
- **[QuestionnaireResponse.item.text](/questionnaireresponse-definitions#QuestionnaireResponse.item.text)** [0..1]: [string](/string) Name for group or question text
- **[QuestionnaireResponse.item.answer](/questionnaireresponse-definitions#QuestionnaireResponse.item.answer)** [0..*]: [BackboneElement](/BackboneElement) The response(s) to the question
- **[QuestionnaireResponse.item.answer.value[x]](/questionnaireresponse-definitions#QuestionnaireResponse.item.answer.value%5Bx%5D)** [1..1]: [boolean](/boolean), [decimal](/decimal), [integer](/integer), [date](/date), [dateTime](/dateTime), [time](/time), [string](/string), [uri](/uri), [Attachment](/Attachment), [Coding](/Coding), [SimpleQuantity](/SimpleQuantity), Reference([Resource](/Resource)) example:[questionnaire-answers](/valueset-questionnaire-answers) Single-valued answer to the question
- **[QuestionnaireResponse.item.answer.item](/questionnaireresponse-definitions#QuestionnaireResponse.item.answer.item)** [0..*]: - Child items of question
- **[QuestionnaireResponse.item.item](/questionnaireresponse-definitions#QuestionnaireResponse.item.item)** [0..*]: - Child items of group item
## Mappings
- [QuestionnaireResponse Mappings](/questionnaireresponse-mappings) — 36 mapping entries
## Implementation Guide
### implementationguide-QuestionnaireResponse-core.xml
```xml
```
## Resource Packs
### list-QuestionnaireResponse-packs.xml
```xml
-
```
## Search Parameters
- [author](/questionnaireresponse-search#author) — **reference** — The author of the questionnaire response — `QuestionnaireResponse.author`
- [authored](/questionnaireresponse-search#authored) — **date** — When the questionnaire response was last changed — `QuestionnaireResponse.authored`
- [based-on](/questionnaireresponse-search#based-on) — **reference** — Plan/proposal/order fulfilled by this questionnaire response — `QuestionnaireResponse.basedOn`
- [encounter](/questionnaireresponse-search#encounter) — **reference** — Encounter associated with the questionnaire response — `QuestionnaireResponse.encounter`
- [identifier](/questionnaireresponse-search#identifier) — **token** — The unique identifier for the questionnaire response — `QuestionnaireResponse.identifier`
- [part-of](/questionnaireresponse-search#part-of) — **reference** — Procedure or observation this questionnaire response was performed as a part of — `QuestionnaireResponse.partOf`
- [patient](/questionnaireresponse-search#patient) — **reference** — The patient that is the subject of the questionnaire response — `QuestionnaireResponse.subject.where(resolve() is Patient)`
- [questionnaire](/questionnaireresponse-search#questionnaire) — **reference** — The questionnaire the answers are provided for — `QuestionnaireResponse.questionnaire`
- [source](/questionnaireresponse-search#source) — **reference** — The individual providing the information reflected in the questionnaire response — `QuestionnaireResponse.source`
- [status](/questionnaireresponse-search#status) — **token** — The status of the questionnaire response — `QuestionnaireResponse.status`
- [subject](/questionnaireresponse-search#subject) — **reference** — The subject of the questionnaire response — `QuestionnaireResponse.subject`
- [item-subject](/questionnaireresponse-search#item-subject) — **reference** — Allows searching for QuestionnaireResponses by item value where the item has isSubject=true — `QuestionnaireResponse.repeat(item.combine(item.answer.item)).where(extension('http://hl7.org/fhir/StructureDefinition/questionnaireresponse-isSubject').exists()).answer.value.ofType(Reference)`
- [linkid](/questionnaireresponse-search#linkid) — **token** — Question linkIds found within the response — `QuestionnaireResponse.repeat(item.combine(item.answer.item)).linkId`
- [answer-concept](/questionnaireresponse-search#answer-concept) — **token** — Question answers of type coding or boolean found within the response. (Primarily for use as part of other composite search parameters.) Refer to [questionnaireresponse.html#searching](searching guidance) on the resource page for considerations on the use of this parameter. — `QuestionnaireResponse.repeat(item.combine(item.answer.item)).answer.value.ofType(boolean) | QuestionnaireResponse.repeat(item.combine(item.answer.item)).answer.value.ofType(Coding)`
- [answer-date](/questionnaireresponse-search#answer-date) — **date** — Question answers of type date or dateTime found within the response. (Primarily for use as part of other composite search parameters.) Refer to [questionnaireresponse.html#searching](searching guidance) on the resource page for considerations on the use of this parameter. — `QuestionnaireResponse.repeat(item.combine(item.answer.item)).answer.value.ofType(date) | QuestionnaireResponse.repeat(item.combine(item.answer.item)).answer.value.ofType(dateTime)`
- [answer-number](/questionnaireresponse-search#answer-number) — **number** — Question answers of type integer or decimal found within the response. (Primarily for use as part of other composite search parameters.) Refer to [questionnaireresponse.html#searching](searching guidance) on the resource page for considerations on the use of this parameter. — `QuestionnaireResponse.repeat(item.combine(item.answer.item)).answer.value.ofType(integer) | QuestionnaireResponse.repeat(item.combine(item.answer.item)).answer.value.ofType(decimal)`
- [answer-quantity](/questionnaireresponse-search#answer-quantity) — **quantity** — Question answers of type quantity found within the response. (Primarily for use as part of other composite search parameters.) Refer to [questionnaireresponse.html#searching](searching guidance) on the resource page for considerations on the use of this parameter. — `QuestionnaireResponse.repeat(item.combine(item.answer.item)).answer.value.ofType(Quantity)`
- [answer-reference](/questionnaireresponse-search#answer-reference) — **reference** — Question answers of type reference found within the response. (Primarily for use as part of other composite search parameters.) Refer to [questionnaireresponse.html#searching](searching guidance) on the resource page for considerations on the use of this parameter. — `QuestionnaireResponse.repeat(item.combine(item.answer.item)).answer.value.ofType(Reference)`
- [answer-string](/questionnaireresponse-search#answer-string) — **string** — Question answers of type string found within the response. (Primarily for use as part of other composite search parameters.) Refer to [questionnaireresponse.html#searching](searching guidance) on the resource page for considerations on the use of this parameter. — `QuestionnaireResponse.repeat(item.combine(item.answer.item)).answer.value.ofType(string)`
- [item-concept](/questionnaireresponse-search#item-concept) — **composite** — Question with items having the specified linkId and answers of type boolean or coding found within the response. (Primarily for use as part of other composite search parameters.) Refer to [questionnaireresponse.html#searching](searching guidance) on the resource page for considerations on the use of this parameter. — `QuestionnaireResponse`
- [item-date](/questionnaireresponse-search#item-date) — **composite** — Question with items having the specified linkId and answers of type date or dateTime found within the response. (Primarily for use as part of other composite search parameters.) Refer to [questionnaireresponse.html#searching](searching guidance) on the resource page for considerations on the use of this parameter. — `QuestionnaireResponse`
- [item-number](/questionnaireresponse-search#item-number) — **composite** — Question with items having the specified linkId and answers of type integer or decimal found within the response. (Primarily for use as part of other composite search parameters.) Refer to [questionnaireresponse.html#searching](searching guidance) on the resource page for considerations on the use of this parameter. — `QuestionnaireResponse`
- [item-quantity](/questionnaireresponse-search#item-quantity) — **composite** — Question with items having the specified linkId and answers of type quantity found within the response. (Primarily for use as part of other composite search parameters.) Refer to [questionnaireresponse.html#searching](searching guidance) on the resource page for considerations on the use of this parameter. — `QuestionnaireResponse`
- [item-reference](/questionnaireresponse-search#item-reference) — **composite** — Question with items having the specified linkId and answers of type reference found within the response. (Primarily for use as part of other composite search parameters.) Refer to [questionnaireresponse.html#searching](searching guidance) on the resource page for considerations on the use of this parameter. — `QuestionnaireResponse`
- [item-string](/questionnaireresponse-search#item-string) — **composite** — Question with items having the specified linkId and answers of type string found within the response. (Primarily for use as part of other composite search parameters.) Refer to [questionnaireresponse.html#searching](searching guidance) on the resource page for considerations on the use of this parameter. — `QuestionnaireResponse`
- [item-uri](/questionnaireresponse-search#item-uri) — **composite** — Question with items having the specified linkId and answers of type uri found within the response. (Primarily for use as part of other composite search parameters.) Refer to [questionnaireresponse.html#searching](searching guidance) on the resource page for considerations on the use of this parameter. — `QuestionnaireResponse`
[Full Search Parameters](/questionnaireresponse-search)
## Examples
- [3141](/questionnaireresponse-example-3141) — questionnaireresponse-example — General questionnaire response example
- [bb](/questionnaireresponse-example-bb) — questionnaireresponse-example-bluebook — Real-world NSW My Personal Health Record example
- [f201](/questionnaireresponse-example-f201) — questionnaireresponse-example-f201-lifelines — Real-world lifelines questionnaire response (fictively taken from the patient)
- [gcs](/questionnaireresponse-example-gcs) — questionnaireresponse-example-gcs — Glasgow Coma Score example answers
- [questionnaireresponse-example](/questionnaireresponse-example-questionnaireresponse-example) — questionnaireresponse-example
- [questionnaireresponse-example-bluebook](/questionnaireresponse-example-questionnaireresponse-example-bluebook) — questionnaireresponse-example-bluebook
- [questionnaireresponse-example-f201-lifelines](/questionnaireresponse-example-questionnaireresponse-example-f201-lifelines) — questionnaireresponse-example-f201-lifelines
- [questionnaireresponse-example-gcs](/questionnaireresponse-example-questionnaireresponse-example-gcs) — questionnaireresponse-example-gcs
- [questionnaireresponse-example-ussg-fht-answers](/questionnaireresponse-example-questionnaireresponse-example-ussg-fht-answers) — questionnaireresponse-example-ussg-fht-answers
- [questionnaireresponse-examples-header](/questionnaireresponse-example-questionnaireresponse-examples-header) — questionnaireresponse-examples-header
- [ussg-fht-answers](/questionnaireresponse-example-ussg-fht-answers) — questionnaireresponse-example-ussg-fht-answers — Example response to the SDC-LOINC USSG Family History questionnaire
[Full Examples](/questionnaireresponse-examples)
## Mapping Exceptions
### questionnaireresponse-event-mapping-exceptions.xml
### Divergent Elements
- **Event.identifier** → **QuestionnaireResponse.identifier**
- shortUnmatched | reason=Incorporates content from profile with context-specific wording | pattern=Business identifier for questionnaire response | resource=Business identifier for this set of answers
- commentsUnmatched | reason=Removed information not relevant to this resource | pattern=Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. | resource=Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)).
- **Event.basedOn** → **QuestionnaireResponse.basedOn**
- missingTypes | reason=This is a generic type and we use specific types | pattern=Reference(Request)
- extraTypes | reason=We use specific types rather than a generic type
- shortUnmatched | reason=Incorporates content from profile with context-specific wording | pattern=Fulfills plan, proposal or order | resource=Request fulfilled by this QuestionnaireResponse
- requirementsUnmatched | reason=Incorporates content from profile with context-specific wording | pattern=Allows tracing of authorization for the questionnaire response and tracking whether proposals/recommendations were acted upon. | resource=Supports traceability of responsibility for the questionnaire response and allows linkage of the response to the proposals/recommendations acted upon.
- **Event.partOf** → **QuestionnaireResponse.partOf**
- missingTypes | reason=This is a generic type and we use specific types | pattern=Reference(Event)
- extraTypes | reason=We use specific types rather than a generic type
- definitionUnmatched | reason=Incorporates content from profile with context-specific wording | pattern=A larger event of which this particular questionnaire response is a component or step. | resource=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.
- **Event.status** → **QuestionnaireResponse.status**
- shortUnmatched | reason=Codes differ for this resource | pattern=preparation | in-progress | not-done | suspended | aborted | completed | entered-in-error | unknown | resource=in-progress | completed | amended | entered-in-error | stopped
- commentsUnmatched | reason=Removed information not relevant to this resource | pattern=A nominal state-transition diagram can be found in the (Event pattern documentation
Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. | resource=Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.
- **Event.subject** → **QuestionnaireResponse.subject**
- missingTypes | reason=Unknown | pattern=Reference(Patient, Group)
- extraTypes | reason=With Questionnaire, anything can be a subject
- shortUnmatched | reason=Incorporates content from profile with context-specific wording | pattern=Individual service was done for/to | resource=The subject of the questions
- definitionUnmatched | reason=Incorporates content from profile with context-specific wording | pattern=The individual or set of individuals the action is being or was performed on. | resource=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.
- **Event.encounter** → **QuestionnaireResponse.encounter**
- commentsUnmatched | reason=Incorporates content from profile with context-specific wording | pattern=This will typically be the encounter the questionnaire response was created during, but some questionnaire responses may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission lab tests). | resource=This will typically be the encounter the questionnaire response was created during, but some questionnaire responses may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission forms). A questionnaire that was initiated during an encounter but not fully completed during the encounter would still generally be associated with the encounter.
- **Event.recorded** → **QuestionnaireResponse.authored**
- shortUnmatched | reason=Incorporates content from profile with context-specific wording | pattern=When questionnaire response was first captured in the subject's record | resource=Date the answers were gathered
- definitionUnmatched | reason=Incorporates content from profile with context-specific wording | pattern=The date the occurrence of the questionnaire response was first captured in the record - potentially significantly after the occurrence of the event. | resource=The date and/or time that this questionnaire response was last modified by the user - e.g. changing answers or revising status.
- commentsUnmatched | reason=Incorporates content from profile with context-specific wording | pattern=The recorded date indicates the date when the data was placed in the record maintained by the performing practitioner, or the date of disclosure by Patient or RelatedPerson, not a date of record transfer. If the record is transferred from one system to another (in paper or electronic form), it does not create a distinct recorded date. In most cases, performing practitioners will record on the same date the event occurred, but sometimes there are delays. If information is being relayed second-hand, the recorded date indicates when the system is first made aware of the data.
The recorded date is NOT intended to be the same as a database.createdTimestamp - that would be captured as part of resource.meta or possibly Provenance.
It is possible for the same event to be disclosed to different systems at different times. E.g. a patient might tell two different clinicians about a historical event at different visits. If the disclosure is from the patient rather than record transfer from clinician A to B, the recorded date would be the date each respective clinician put the data in their record. If the data flowed from clinician A to B, the recorded date would remain the recorded date as initially set in clinician A's system. | resource=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.
- **Event.performer.actor** → **QuestionnaireResponse.author**
- missingTypes | reason=The missing type(s) never apply in any context where this resource is used | pattern=Reference(CareTeam)
- extraTypes | reason=This should be in the pattern too
- shortUnmatched | reason=Incorporates content from profile with context-specific wording | pattern=Who performed questionnaire response | resource=The individual or device that received and recorded the answers
- definitionUnmatched | reason=Incorporates content from profile with context-specific wording | pattern=Indicates who or what performed the questionnaire response. | resource=The individual or device that received the answers to the questions in the QuestionnaireResponse and recorded them in the system.
### Unmapped Elements
- **Event.reported** — Not relevant for this resource
- **Event.reason** — Not relevant for this resource
- **Event.relevantHistory** — Not relevant for this resource
- **Event.code** — Implicit for this resource - 'Form was filled out'
- **Event.location** — Not relevant for this resource
- **Event.statusReason** — Not relevant for this resource
- **Event.performer.function** — Not relevant for this resource
- **Event.note** — Not relevant for this resource
- **Event.category** — Not relevant for this resource. If there was categorization, it would be on the Questionnaire
- **Event.occurrence** — Occurrence time is implicit in the questions and may vary for different questions
- **Event.product** — Not relevant for this resource
- **Event.performer** — Not relevant for this resource
### questionnaireresponse-fivews-mapping-exceptions.xml
### Unmapped Elements
- **FiveWs.what** — Not relevant for this resource
- **FiveWs.actor** — Not relevant for this resource
- **FiveWs.cause** — Not relevant for this resource
- **FiveWs.version** — Not relevant for this resource
- **FiveWs.witness** — Not relevant for this resource
- **FiveWs.class** — Not relevant for this resource
- **FiveWs.where** — Not relevant for this resource
- **FiveWs.init** — Not relevant for this resource
- **FiveWs.why** — Not relevant for this resource
- **FiveWs.who** — Not relevant for this resource
- **FiveWs.grade** — Not relevant for this resource
- **FiveWs.planned** — Not relevant for this resource
- **FiveWs.done** — Not relevant for this resource