Is every element really needed? - SDC #6

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • Structured Data Capture (SDC) (FHIR)
    • STU3
    • FHIR Infrastructure
    • Questionnaire [deprecated]
    • Structured Data Capt
    • Hide

      Will move the constraints on usageContext into a separate profile using a combination of documentation and invariants to make the base profile easier to read.

      Will split the based Questionnaire profile into two - one focused on search and one focused on base capabilities. The base capabilities one will be the one inherited by everything. Base will include: url, version, subjectType, item (and everything under item)

      Will ensure that item.code and item.definition at least show up in the differential with comments about their use, but will not make them mustSupport here

      Will remove questionnaire-studyIdentifier extension as it's now covered by usageContext.

      Will make clear that for clients, the "search" elements are relevant to display to the user when searching to select a form and that there's no expectation to render 'search' elements or other metadata when displaying the rendered form to capture answers.

      When rendering forms, what metadata is displayed is up to the rendering tool (e.g. you can choose to display title, version, date, etc. but don't have to.)

      Will mark jurisdiction, approvalDate, lastReviewDate and effectivePeriod as optional

      Show
      Will move the constraints on usageContext into a separate profile using a combination of documentation and invariants to make the base profile easier to read. Will split the based Questionnaire profile into two - one focused on search and one focused on base capabilities. The base capabilities one will be the one inherited by everything. Base will include: url, version, subjectType, item (and everything under item) Will ensure that item.code and item.definition at least show up in the differential with comments about their use, but will not make them mustSupport here Will remove questionnaire-studyIdentifier extension as it's now covered by usageContext. Will make clear that for clients, the "search" elements are relevant to display to the user when searching to select a form and that there's no expectation to render 'search' elements or other metadata when displaying the rendered form to capture answers. When rendering forms, what metadata is displayed is up to the rendering tool (e.g. you can choose to display title, version, date, etc. but don't have to.) Will mark jurisdiction, approvalDate, lastReviewDate and effectivePeriod as optional
    • Clem McDonald/Eric Haas: 8-0-0
    • Clarification
    • Non-compatible

      Comment:

      Am I understanding correctly that this profile reqiures that every element in Questionnaire must be supported by the server? I assume this because of the long line of red "S" symbols down the differential table. Would be good to assert this in description. Also, is it really necessary to support every element? Some elements, such as "experimental", "code", "lastReviewDate" provide less value to a system that is storing the question to be displayed in a form... Can you imagine a system that would only display a Questionnaire form if it was last reviewed after a specific date? Fairly uncommon I would think.

      Summary:

      Is every element really needed?

            Assignee:
            Unassigned
            Reporter:
            Sean McIlvenna
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: