Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-28031

Will the creation of must-display necessarily lead to poor clinical user experience?

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • FHIR Data Segmentation for Privacy (FHIR)
    • 0.1 [deprecated]
    • Security
    • Artifacts Summary
    • Hide

      we don't intend to dictate UI display.

       

      will rephrase to: "a specific mark when [on any] rendering [of] the resource content in print or electronic user interfaces."

      separately, the name of the extension has also been changed to `display` to avoid this confusion.

      Show
      we don't intend to dictate UI display.   will rephrase to: "a specific mark when [ on any] rendering  [ of ] the resource content in print or electronic user interfaces." separately, the name of the extension has also been changed to `display` to avoid this confusion.
    • Mohammad Jafari/Kathleen Connor: 7-0-0
    • Clarification
    • Non-substantive

    Description

      In an EHR, patient data is aggregated, de-duplicated, represented in a variety of ways based upon the user's needs and workflows. For example, should must-display be shown to the patient? For a clinician view of a patient's medical timeline over a decade, should must-display be displayed? Please don't mandate UI. Doing so will necessarily, negatively impact clinical UX.

      Existing Wording:

      #implementation - The must-display extension to require the consumer to display a specific mark on any rendering of the resource in print or electronic user interfaces.

      Attachments

        Activity

          People

            Unassigned Unassigned
            Isaac.Vetter Isaac Vetter
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: