Motivation
This request relates to this vtk-js request: Kitware/vtk-js#3507.
It would be supported by two PRs:
PR #1 - Cast client:
The client PR would implements the vtk-js cast client in the VolView IO module and adds CastModule.vue to the ModulePanel.vue component.
PR #2 - Hub:
The 3D slicer cast_api.py script would be replicated to the VolView server folder. An additional server script would deliver the volview remote server and the hub endpoints on the same port.
The hub provides a test mock auth endpoint that provides a user id and auth code. A “single-user” mode is available for stand-alone applications that do not use authentication. In addition to FHIRcast events, the cast hub allows the following:
- Data formats other than FHIR, such as DICOM, PNG, NIFTi, openEHR, OpenIGTLink, nrrd,
- Query applications for information, such as worklist context, report content, DICOM instance, DICOM tag, JPEG/PNG screenshots, scene views, etc.
- Group topics for multi-user workflows, such as tumor boards or interventional procedures.
- Support three additional event level data: subscriber product name, version and IHE actor role.

Motivation
This request relates to this vtk-js request: Kitware/vtk-js#3507.
It would be supported by two PRs:
PR #1 - Cast client:
The client PR would implements the vtk-js cast client in the VolView IO module and adds CastModule.vue to the ModulePanel.vue component.
PR #2 - Hub:
The 3D slicer cast_api.py script would be replicated to the VolView server folder. An additional server script would deliver the volview remote server and the hub endpoints on the same port.
The hub provides a test mock auth endpoint that provides a user id and auth code. A “single-user” mode is available for stand-alone applications that do not use authentication. In addition to FHIRcast events, the cast hub allows the following: