Details
-
Change Request
-
Resolution: Not Persuasive with Modification
-
Highest
-
SMART on FHIR (FHIR)
-
2.0.0
-
FHIR Infrastructure
-
(NA)
-
-
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
Issue Links
- is voted on by
-
BALLOT-46624 Affirmative - Ron G. Parker : 2023-Jan-HL7 FHIR IG SMART APP LAUNCH R2 STU
- Closed
-
BALLOT-47255 Affirmative - Joan Harper : 2023-Jan-HL7 FHIR IG SMART APP LAUNCH R2 STU
- Closed
-
BALLOT-47368 Affirmative - Elliot Silver : 2023-Jan-HL7 FHIR IG SMART APP LAUNCH R2 STU
- Closed
-
BALLOT-47408 Affirmative - Ken Sinn : 2023-Jan-HL7 FHIR IG SMART APP LAUNCH R2 STU
- Closed
-
BALLOT-47447 Affirmative - Harsh Sharma : 2023-Jan-HL7 FHIR IG SMART APP LAUNCH R2 STU
- Closed