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

Change "need_patient_banner" to "patient_banner_provided"

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • SMART on FHIR (FHIR)
    • 2.0.0
    • FHIR Infrastructure
    • (NA)
    • Hide

      While there may be advantages to inverting this boolean flag, we have not encountered real-world challenges and this features has been widely implemented to the point where a breaking change is undesirable. However we can clarify the expectations by changing:

      > Boolean value indicating whether the app was launched in a UX context where a patient banner is required (when true) or not required (when false). An app receiving a value of false should not take up screen real estate displaying a patient banner.

      to say:

      > Boolean value indicating whether the app was launched in a UX context where a patient banner is required (when true) or may not be required (when false). An app receiving a value of false might not need to take up screen real estate displaying a patient banner.

      Show
      While there may be advantages to inverting this boolean flag, we have not encountered real-world challenges and this features has been widely implemented to the point where a breaking change is undesirable. However we can clarify the expectations by changing: > Boolean value indicating whether the app was launched in a UX context where a patient banner is required (when true) or not required (when false). An app receiving a value of false should not take up screen real estate displaying a patient banner. to say: > Boolean value indicating whether the app was launched in a UX context where a patient banner is required (when true) or may not be required (when false). An app receiving a value of false might not need to take up screen real estate displaying a patient banner.
    • Josh Mandel/Rick Geimer: 17-0-0
    • Clarification
    • Non-substantive

    Description

      The "polarity" of this parameter is reversed. It shouldn't be up to the host to determine whether the app needs to display a patient banner; that is a app decision. On the other hand, the host can provide information about whether the host displays a patient banner, and let the app make its own decision.

      Further the existing description of "An app receiveing a value of false should not take up screen real estate displaying a patient banner." is a patient safety and regulatory decision that should be made by individual vendors, not by the spec.

      Existing Wording:

      need_patient_banner true or false (boolean) Boolean value indicating whether the app was launched in a UX context where a patient banner is required (when true) or not required (when false). An app receiving a value of false should not take up screen real estate displaying a patient banner.

      (Comment 22 - imported by: Ron G. Parker)

      Attachments

        Activity

          People

            Unassigned Unassigned
            Rongparker Ron G. Parker
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: