Operation-questionnaire-populate

Generates a QuestionnaireAnswers instance based on a specified Questionnaire, filling in answers to questions where possible based on information provided as part of the operation or already known by the server about the subject of the Questionnaire.

If the operation is not called at the instance level, one of the identifier or questionnaire 'in' parameters must be provided. (If called at the instance level, these parameters will be ignored.)

The response will contain a QuestionnaireAnswers instance based on the specified Questionnaire and/or an OperationOutcome resource with errors or warnings.

The QuestionnaireAnswers instance will be populated with an unanswered set of questions following the group and question structure of the specified Questionnaire. If content parameters were specified or the local parameter was set to true, some of the questions may have answers filled in as well. In the case of repeating questions or groups, typically only one repetition will be provided unless answer values exist that would support populating multiple repetitions.

Population of the QuestionnaireAnswers with appropriate data is dependent on the questions and/or groups in the Questionnaire having metadata that allows the server to recognize the questions. This might be through Questionnaire.group.question.code, through extensions such as the http://hl7.org/fhir/StructureDefinition/questionnaire-deReference extension or through us of the ConceptMap resource.

Regardless of the mechanism used to link the questions in a questionnaire to a "known" mapable concept, solutions using this operation should ensure that the details of the question and associated linkage element are sufficiently similar as to safely allow auto-population. I.e. the question text and context must be sufficiently the same, the value set for the question must fall within the value set for the mapped element, the data types must be the same or convertable, etc.

While it is theoretically possible for a QuestionnaireAnswers instance to be completely auto-populated and submitted without human review, the intention of this transaction is merely to reduce redundant data entry. A client SHOULD ensure that a human submitter has an opportunity to review the auto-populated answers to confirm correctness as well as to complete or expand on information provided by the auto-population process.

Complex form designs with conditional logic or tight constraints on cardinalities may be challenging to auto-populate. A server MAY choose to traverse the questionnaire as if it were a human respondant, answering only those questions that are enabled based on previously answered questions. However doing so may result in minimal population. Alternatively, systems may choose to populate all known answers, independent of dependencies and other constraints. This may cause questions to be answered that should not be answered. It will be up to the client to appropriately prune the final populated questionnaire once human review has taken place.

Invoking this operation with the ''content'' parameter may involve the disclosure of personally identifiable healthcare information to the system which is performing the population process. No such disclosures should be made unless the system on which the operation is being invoked is a "trusted" system and appropriate agreements are in place to protect the confidentiality of any information shared with that system.