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

Clarify "EHR context" not actually tied to EHR.

    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

      The introduction to the App Launch page states:

      > The framework supports apps for use by clinicians, patients, and others via a PHR or Patient Portal or any FHIR system where a user can launch an app.

      We use the term "EHR" as a concrete and brief noun; generic terms like "host" can lead to confusion (e.g, does this refer to an HTTP server? And organization providing services?)

      To clarify in the overview, we can change "An app can launch from within an existing EHR or Patient Portal session" to say "An app can launch from within an existing session in an EHR, Patient Portal, or other FHIR system."

      Show
      The introduction to the App Launch page states: > The framework supports apps for use by clinicians, patients, and others via a PHR or Patient Portal or any FHIR system where a user can launch an app. We use the term "EHR" as a concrete and brief noun; generic terms like "host" can lead to confusion (e.g, does this refer to an HTTP server? And organization providing services?) To clarify in the overview, we can change "An app can launch from within an existing EHR or Patient Portal session" to say "An app can launch from within an existing session in an EHR, Patient Portal, or other FHIR system."
    • Josh Mandel/Rick Geimer: 17-0-0
    • Clarification
    • Non-substantive

    Description

      The "EHR launch" is broader than just EHR and patient portal use, and applies to any environment where the app is hosted within another application that provides the necessary context. For example, a PACS workstation could serve as a host. Conversely, "standalone launch" is not launch "from outside an EHR session" but, rather, launch in the absence of an existing context.

      For clarity, is EHR being used here to mean "the FHIR server," or is EHR being used to mean "the user-facing application"? If the latter, then that implies other applications cannot act as hosts; if the former, that is an unnecessarily narrow view and there may be non-EHR FHIR servers that implement this IG.

      Suggest broadening the definiton of this launch method to be more generic and not limited to the identified examples. Suggest renaming "EHR launch" throughout to "hosted launch." Suggest using more generic language and/or calling EHR out as only an example, in phrases such as "the EHR context. Suggest not defining "standalone launch" based on existance of an EHR. Review throughout IG.

      Existing Wording:

      An app can launch from within an existing EHR or Patient Portal session; this is known as an EHR launch. Alternatively, it can launch as a standalone app.

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

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: