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

Can Hub support single app or multiple app scopes?

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Considered - Question answered
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • OAuth2 authorization scopes [deprecated]
    • Hide

      FHIRcast is explicitly designed to enable multiple subscribers to a single topic. This is common and expected behavior. There is no theoretical limit to the number of subscribers for a single topic, but implementations may differ. 

      The commenter additionally asked this question in the comment thread of this Jira, and Bas answered it well – 

      >are there are recommendations on how to build FHIRCast servers –  one per EMR or one per physician session? 

      The specification leaves that aspect to implementers but does include some aspects allowing it to scale:

      1. When launching the applications using SMART on FHIR, the hub-URL is provided in the launch process this allows the use of multiple hubs and hub-servers.
      2. When setting-up a connection, a websocket URL is provided for the application to connect to. A full URL is provided allowing the websocket-service to be hosted by different servers within the same topic.

      As all messages are sent over the same websocket channel, there is a bottleneck in the amount of messages, the size of a message a topic can handle. As FHIRcast is mainly intended to be a channel for exchanging context-change events this is not seen as a big issue

      Show
      FHIRcast is explicitly designed to enable multiple subscribers to a single topic. This is common and expected behavior. There is no theoretical limit to the number of subscribers for a single topic, but implementations may differ.  The commenter additionally asked this question in the comment thread of this Jira, and Bas answered it well –  >are there are recommendations on how to build FHIRCast servers –  one per EMR or one per physician session?  The specification leaves that aspect to implementers but does include some aspects allowing it to scale: When launching the applications using SMART on FHIR, the hub-URL is provided in the launch process this allows the use of multiple hubs and hub-servers. When setting-up a connection, a websocket URL is provided for the application to connect to. A full URL is provided allowing the websocket-service to be hosted by different servers within the same topic. As all messages are sent over the same websocket channel, there is a bottleneck in the amount of messages, the size of a message a topic can handle. As FHIRcast is mainly intended to be a channel for exchanging context-change events this is not seen as a big issue

    Description

      Comment: Specify if Hub can support multiple or single app?

      Attachments

        Activity

          People

            Unassigned Unassigned
            Brian_Pech Brian Pech
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: