Add use case to description of optionalDisplay extension

XMLWordPrintableJSON

    • Type: Technical Correction
    • Resolution: Persuasive
    • Priority: High
    • Structured Data Capture (SDC) (FHIR)
    • current
    • FHIR Infrastructure
    • (NA)
    • 12.33.1
    • Hide

      Will add clarifying text to better explain the use-case for this field, perhaps with an example or two.  Will also look at adding an explicit section in SDC that talks about deriving forms - what can be done and what can't and how this extension would play into that use-case.  If there isn't time to get that done in this release, we'll create a new tracker to ensure it happens in the next release.

      Show
      Will add clarifying text to better explain the use-case for this field, perhaps with an example or two.  Will also look at adding an explicit section in SDC that talks about deriving forms - what can be done and what can't and how this extension would play into that use-case.  If there isn't time to get that done in this release, we'll create a new tracker to ensure it happens in the next release.
    • Correction

      See https://chat.fhir.org/#narrow/stream/179255-questionnaire/topic/.22optional.20display.22.20extension.3F/near/203388062

      The description for the optionalDisplay extension could benefit from the use case Lloyd mentions. Also, the in the current description, the text, "or the individual encoding the form for data capture) can choose to omit the item from display to the user" is hard to understand, because presumably the "individual encoding the form" is the one who has put the optionalDisplay extension on the item, and not the thing/person deciding whether to display it.

            Assignee:
            Lloyd McKenzie
            Reporter:
            Paul Lynch
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: