rendering-stylesensitive should include alternate content

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: High
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Datatypes
    • Hide

      1. Change the context of rendering-styleSensitive to be only Resource (not element)

      2. Change the description to the following:

      Indicates that the style extensions (style, markdown and xhtml) in this resource instance are essential to the interpretation of the instance and that systems that are not capable of rendering using those extensions should not be used to render the resource.

      Comment:

      If set to true, all systems that claim to support this extension and that render elements from the resource SHALL either render the content as required by the style extensions ([style], [xhtml] and [markdown]) or shall indicate to the user that the resource (or specific elements in the resource) cannot be appropriately rendered by the system.

      3. Will add an additional comment to the SDC usage of this extension:

      Systems that do not support the [style], [markdown] and [xhtml] extensions present in the instance SHALL NOT render the form to collect data.

      4. Will ensure that styleSensitive appears in the SDC profiles for ValueSet and CodeSystem too.

      5. Will add "Dragon" usage note to the IG around ValueSet indicating that extensions present in the CodeSystem (ordinal, styles, etc.) need to flow into the ValueSet during the expansion process.

      Show
      1. Change the context of rendering-styleSensitive to be only Resource (not element) 2. Change the description to the following: Indicates that the style extensions ( style , markdown and xhtml ) in this resource instance are essential to the interpretation of the instance and that systems that are not capable of rendering using those extensions should not be used to render the resource. Comment : If set to true, all systems that claim to support this extension and that render elements from the resource SHALL either render the content as required by the style extensions ( [style] , [xhtml] and [markdown] ) or shall indicate to the user that the resource (or specific elements in the resource) cannot be appropriately rendered by the system. 3. Will add an additional comment to the SDC usage of this extension: Systems that do not support the [style] , [markdown] and [xhtml] extensions present in the instance SHALL NOT render the form to collect data. 4. Will ensure that styleSensitive appears in the SDC profiles for ValueSet and CodeSystem too. 5. Will add "Dragon" usage note to the IG around ValueSet indicating that extensions present in the CodeSystem (ordinal, styles, etc.) need to flow into the ValueSet during the expansion process.
    • Brian Postlethwaite/Nagesh Bashyam: 6-0-0
    • Correction
    • Non-compatible
    • STU3

      In thinking about how one might use rendering-styleSensitive* *in an SDC Questionnaire, it is hard to imagine cases where an author would either want a style block of text, or none at all. I think it would be much more likely that if a Questionnaire designer had concerns about the readability of a styled block of text, they would want to provide a second version that is not styled. However, the Questionnaire can't simply contain the unstyled text as a separate item, because then if styling were supported, both the styled and the unstyled version would be displayed. To avoid that problem, the rendering-styleSensitive extension can contain the unstyled version to use if the styled version could not be displayed properly.

      I am filing this on FHIR Core, because the extension is there and the change I am proposing is on that extension, but my particular concern is its inclusion in SDC Questionnaire.

            Assignee:
            Unassigned
            Reporter:
            Paul Lynch
            Paul Lynch
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: