Motivation
This feature would connect vtk-js applications to the FHIRcast messaging infrastructure for advanced front-end integration. FHIRcast (https://fhircast.hl7.org/) is the standard replacing Epic’s file drop interface for integration with PACS and reporting systems. It provides a WebSub-like secure messaging infrastructure using a hub with websocket subscriptions.
There are a number of PACS and reporting applications supporting FHIRcast already and the feature would also facilitate participation in high-profile integration events such as the HIMSS “interoperability theater”, the RSNA “Radiology Reimagined” or the IHE Connectathon (Integrated Reporting Application profile).
The feature should support an example worklist client that can open and close studies in other applications with standard FHIRcast events.
In addition to connecting to FHIRcast, the client would also support cast hubs that provide expanded capabilities that are described in the Volview server feature request.
Here is a run-through of the proposed feature in progress:
https://examples-vtkjs.d2pxx3mhr69djy.amplifyapp.com/examples/CastClient.html
https://youtu.be/MUagLJ5HHG0
Detailed Description
The client would be part of the IO module. It would utilize the authentication server URL, hub URL, and subscription configuration to provide the following operations:
Authorize: Retrieves the token from the authentication server using OAuth 2.0 Client Credentials grant.
Subscribe: Establishes a websocket link to the hub for receiving information requests and events.
Publish: Distributes events to other connected applications.
Request: Obtains data from other applications via the hub.
It would provide an OnMessage callback where the application would receive messages from other applications and requests for information.
The client would support filtering hub heartbeats, message echos and automatically re-subscribes when the websocket connection is lost.
A feature request (Kitware/VolView#877) for the VolView repository would add the hub to the server feature for testing and development and cast client implementation.
Motivation
This feature would connect vtk-js applications to the FHIRcast messaging infrastructure for advanced front-end integration. FHIRcast (https://fhircast.hl7.org/) is the standard replacing Epic’s file drop interface for integration with PACS and reporting systems. It provides a WebSub-like secure messaging infrastructure using a hub with websocket subscriptions.
There are a number of PACS and reporting applications supporting FHIRcast already and the feature would also facilitate participation in high-profile integration events such as the HIMSS “interoperability theater”, the RSNA “Radiology Reimagined” or the IHE Connectathon (Integrated Reporting Application profile).
The feature should support an example worklist client that can open and close studies in other applications with standard FHIRcast events.
In addition to connecting to FHIRcast, the client would also support cast hubs that provide expanded capabilities that are described in the Volview server feature request.
Here is a run-through of the proposed feature in progress:
https://examples-vtkjs.d2pxx3mhr69djy.amplifyapp.com/examples/CastClient.html
https://youtu.be/MUagLJ5HHG0
Detailed Description
The client would be part of the IO module. It would utilize the authentication server URL, hub URL, and subscription configuration to provide the following operations:
Authorize: Retrieves the token from the authentication server using OAuth 2.0 Client Credentials grant.
Subscribe: Establishes a websocket link to the hub for receiving information requests and events.
Publish: Distributes events to other connected applications.
Request: Obtains data from other applications via the hub.
It would provide an OnMessage callback where the application would receive messages from other applications and requests for information.
The client would support filtering hub heartbeats, message echos and automatically re-subscribes when the websocket connection is lost.
A feature request (Kitware/VolView#877) for the VolView repository would add the hub to the server feature for testing and development and cast client implementation.