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

FHIRcast fields in SMART on FHIR

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Considered for Future Use
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.1.0-ballot [deprecated]
    • Infrastructure & Messaging
    • STU
    • App launch scenarios and session discovery [deprecated]
    • Hide

      HL7 published FHIRcast's use of these top-level SMART app launch parameters well before SMART defined a fhirContext object alongside the access token. Even before FHIRcast, adding key/value pairs alongside the access token was common site-specific integration behavior. This practice is very, very widespread. 

      Also, note that none of these app launch paramters are in response to a requested launch/ scope.

      Further, most importantly, this change would break every FHIRcast integration in production. There doesn't seem sufficient justification for such a break.

       

      Marking as Considered for Future Use. This change is a breaking change to both the specification, and more importantly, every deployed FHIRcast implementation. We will log a Jira against the SMART spec to carve out support for the top-level context paramters used by FHIRcast and in production by implementers.

      Show
      HL7 published FHIRcast's use of these top-level SMART app launch parameters well before SMART defined a fhirContext object alongside the access token. Even before FHIRcast, adding key/value pairs alongside the access token was common site-specific integration behavior. This practice is very, very widespread.  Also, note that none of these app launch paramters are in response to a requested launch/ scope. Further, most importantly, this change would break every FHIRcast integration in production. There doesn't seem sufficient justification for such a break.   Marking as Considered for Future Use. This change is a breaking change to both the specification, and more importantly, every deployed FHIRcast implementation. We will log a Jira against the SMART spec to carve out support for the top-level context paramters used by FHIRcast and in production by implementers.
    • Bas van den Heuvel / Trent Nolin: 7-0-0

    Description

      If we follow the SMART on FHIR spec, we should not add such root level elements. We could use SMART on FHIR extensions or negotiate the key 'fhircast' for FHIRcast specific fields.

      E.g.
      "fhircast":

      { "hub.url" : "https://hub.example.com", "hub.topic": [ "2e5e1b95-5c7f-4884-b19a-0b058699318b", "fdb2f928-5546-4f52-87a0-0648e9ded065" ] }

      Ps. Is the topic repeated or does it return an array?

      Attachments

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: