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

No appContext on stand-alone launch

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci DTR (FHIR)
    • 1.0.0 [deprecated]
    • Clinical Decision Support
    • Retrieval of Payer Resources [deprecated]
    • Hide

      Will update the spec to indicate that the resources corresponding to this context (if any) would be passed in the fhirContext element.  As part of configuration during app enablement process the app should also always ask for the launch/patient and the openId and fhirUser contexts.

      Show
      Will update the spec to indicate that the resources corresponding to this context (if any) would be passed in the fhirContext element.  As part of configuration during app enablement process the app should also always ask for the launch/patient and the openId and fhirUser contexts.
    • Bob Dieterle / Jeff Brown : 12-0-2
    • Correction
    • Compatible, substantive

    Description

      appContext is only passed when the launch is triggered by CDS Hooks.  Context information for stand-alone launch is driven by scope requests.  Guidance from the SMART community is that we should have a custom launch context request to solicit "current order(s) or DTR QuestionnareResponse(s) in the user's context - if any".  This context would have a custom URL - for example http://hl7.org/fhir/us/davinci-dtr/smart-app-launch-request.  

      The spec should indicate that the resources corresponding to this context (if any) would be passed in the fhirContext element.  As well, the app should also always ask for the launch/patient and the openId and fhirUser contexts.

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: