Loosen up the the cardinality of QuestionnaireResponse.contained element not to be mandatory

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • Structured Data Capture (SDC) (FHIR)
    • current
    • FHIR Infrastructure
    • Adaptive Questionnaire Response
    • Hide
      1. The Questionnaire reflects the specific pathway of the user through the instrument - what questions were asked and in what order, what answers were provided.
      2. Without the Questionnaire, you can't see what questions were asked but skipped or what answer the user got to choose from
      3. The design is that the system behaves as a black box and doesn't necessarily persist previous submissions.

      While there's nothing to stop systems from choosing to persist what's been received (if legal conditions, etc. allow that to occur), we don't think clients should have to handle this complexity.  The Questionnaire isn't going to be that heavy - typically there aren't more than 10 or so questions asked before the user is 'done' the QuestionnaireResponse.

      Show
      The Questionnaire reflects the specific pathway of the user through the instrument - what questions were asked and in what order, what answers were provided. Without the Questionnaire, you can't see what questions were asked but skipped or what answer the user got to choose from The design is that the system behaves as a black box and doesn't necessarily persist previous submissions. While there's nothing to stop systems from choosing to persist what's been received (if legal conditions, etc. allow that to occur), we don't think clients should have to handle this complexity.  The Questionnaire isn't going to be that heavy - typically there aren't more than 10 or so questions asked before the user is 'done' the QuestionnaireResponse.
    • Ana Kostadinovska/Paul Lynch: 11-0-0

      Having the QuestionnaireResponse.contained element mandatory, creates a burden for systems that are actually persisting the questions and responces being exchanged. The persumption taken here, that the invocation is stateless and that the server has no record of what's previously been asked or what answers have been given, comes at high costs for systems that are able to store the data. If we loosen up the cardinality of QuestionnaireResponse.contained element not to be mandatory, we would allow systems to choose whether to constantly exchange all questions and answers given, or have much simpler reource exchanged and persist the data locally.

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

              Created:
              Updated:
              Resolved: