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

introduction of fhirContext breaks a significant number of production integrations

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • SMART on FHIR (FHIR)
    • 2.0.0
    • FHIR Infrastructure
    • App Launch: Scopes and Launch Context
    • Hide

      Based on FHIR-35801 we have a set of improvements to fhirContext in place for a technical correction. In any case, the addition of fhirContext does not prevent the use of other properties to convey context to SMART Apps. To prevent naming conflicts,  No change needed"

      As part of the same technical correction defined in FHIR-35801, we clarify the "if required" clause from https://hl7.org/fhir/smart-app-launch/scopes-and-launch-context.html#standalone-apps:

      > This list can be extended by any SMART EHR if additional context is required.

      To:

      >This list can be extended by any SMART EHR to support additional context.

      Show
      Based on  FHIR-35801 we have a set of improvements to fhirContext in place for a technical correction. In any case, the addition of fhirContext does not prevent the use of other properties to convey context to SMART Apps. To prevent naming conflicts,  No change needed" As part of the same technical correction defined in  FHIR-35801 , we clarify the "if required" clause from https://hl7.org/fhir/smart-app-launch/scopes-and-launch-context.html#standalone-apps: > This list can be extended by any SMART EHR if additional context is required. To: >This list can be extended by any SMART EHR to support additional context.
    • Rick Geimer / Michael Donnelly: 16-0-1
    • Clarification
    • Non-substantive

    Description

      Most of our provider-facing EHR launched SMART app integrations and many patient-facing EHR launched SMART app integrations use SMART context parameters as described in SMART v1.0. 

      The introduction of fhirContext as described:

      > any contextual resource types (other than Patient and Encounter) that were requested by a launch scope will appear in [fhirContext]. 

      Effectively requires that no additional contextual parameters be included alongside the access token; thereby breaking compatibility not just with SMART v1.0, but more importantly with thousands (at least) of production integrations. 

      My apologies for the late objection to a resolved discussion.

      Attachments

        Activity

          People

            michael_donnelly Michael Donnelly
            Isaac.Vetter Isaac Vetter
            Isaac Vetter
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: