$extract should perform data validation

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • Structured Data Capture (SDC) (FHIR)
    • current
    • FHIR Infrastructure
    • Questionnaire response extract to resource(s)
    • Hide

      We don't want to force validation as something that this operation must do because systems that can do extraction may not be well-suited to do validation.  However, we'll add the following language:

      "When invoking the $extract operation, care should be taken that the submitted QuestionnaireResponse is itself valid.  If not, the extract operation could fail (with appropriate OperationOutcomes) or, more problematic, might succeed but provide incorrect output."

      Show
      We don't want to force validation as something that this operation must do because systems that can do extraction may not be well-suited to do validation.  However, we'll add the following language: "When invoking the $extract operation, care should be taken that the submitted QuestionnaireResponse is itself valid.  If not, the extract operation could fail (with appropriate OperationOutcomes) or, more problematic, might succeed but provide incorrect output."
    • Ilya Beda/Paul Lynch: 11-0-0
    • Clarification
    • Non-substantive

      Extract usually require QuestionnaireResponse to be valid across multiple sophisticated validation rules. The extract process relies on correct and valid questionnaire data.

      My proposal is to perform validation for QuestionnaireResponse based on the Questionniare.item.required  attribute and http://hl7.org/fhir/R4/extension-questionnaire-constraint.html extension.

      I case of validation errors, $extract should return OperationOutcome with all validation error descriptions.

            Assignee:
            Unassigned
            Reporter:
            ilyabeda
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: