You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: PW44_2026_GranCanaria/Projects/CastAStandardForRealTimeFrontEndIntegrationOfHealthcareApplication/README.md
+55-44Lines changed: 55 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,49 +74,6 @@ Cast is a client to client protocol. Client to client protocols differ because t
74
74
Cast serves as an umbrella standard that encompasses specialized variants such as FHIRCast (for FHIR context management), DICOMCast (for DICOM data exchange), NAVICast (for surgical navigation), and other domain-specific implementations. All variants share the same core infrastructure while defining specialized event types for their domains (see [Cast Ecosystem](#cast-ecosystem) below).
75
75
76
76
77
-
### Background
78
-
79
-
Healthcare environments sometimes involve multiple specialized applications working together to support clinical workflows. These applications need to communicate and coordinate in real-time, sharing events such as user interactions, data exchanges, state changes, and workflow transitions. A typical scenario is radiology reporting where a worklist, viewer, reporting and EMR integrate to produce the diagnostic report. This workflow is defined in the IHE Integrated Reporting Applications profile.
80
-
81
-
FHIRcast provides a solid foundation for FHIR-based context management, focusing specifically on synchronizing FHIR resource context across applications. However, the healthcare ecosystem includes many non-FHIR data formats, such as DICOM, openEHR and use cases that extend beyond context management such has navigation controllers, VR controllsers, joysticks and footswitches. Cast addresses this by providing a flexible, extensible framework that supports:
-**Data Exchange Events**: FHIR, DICOM data synchronization (potentially called DICOMCast), HL7 V2 messages, proprietary formats
85
-
-**Workflow Events**: Task assignments, status updates, notifications
86
-
-**Any Custom Event Types**: Domain-specific events defined by applications
87
-
88
-
Cast supports **bi-directional WebSocket communication**. This enables low-latency, "gaming style" interactions where applications can exchange events in real-time with minimal delay, supporting use cases such as collaborative viewing, synchronized navigation, and interventional workflows that require immediate feedback and coordination.
89
-
90
-
Cast also supports **collaborative multi-user workflows** through the hub's ability to group users together within sessions. The hub can coordinate multiple users, allowing them to share events and synchronize their applications in real-time. This enables scenarios such as tumor board meetings, where multiple radiologists and clinicians can simultaneously view and interact with the same DICOM study, with measurements, annotations, and navigation synchronized across all participants own viewers.
91
-
92
-
93
-
The hub-based architecture provides **flexible integration** because applications do not need to connect directly to each other—they only need to reach the hub. This enables applications running on different platforms and locations to seamlessly participate in the same workflow. For example, a 3D Slicer application running on trame in the cloud can communicate with a mobile device application, a web-based viewer, or local camera control , all through the hub without requiring direct network connections between them.
94
-
95
-
### Cast Ecosystem
96
-
97
-
Cast serves as an umbrella standard that encompasses specialized "Cast" variants for different healthcare domains and use cases:
@@ -128,7 +85,17 @@ Cast serves as an umbrella standard that encompasses specialized "Cast" variants
128
85
If there are specific steps that you could not complete then you can describe them here, too. -->
129
86
130
87
131
-
1. Describe specific steps you **have actually done**.
88
+
1. Getting started:
89
+
- Open the OHIF client and note your user name in the top right corner. See note on mock authentication and standalone applicaton below.
90
+
- In the sprocket icon, open the Cast admin portal. Note the subscribtion for your subscriber (application) and the topic matching your user.
91
+
- In the sprokect icon, open the Cast test client. The test client will have the topic prefilled with you user.
92
+
- Click the Subscribe button. The subscription will appear in the admin portal.
93
+
- Click the Publish button. The imagingstudy-open event will cause the OHIF client to open the study in the message.
94
+
- Change the event to imagingstudy-close and Publish. The OHIF client will close the study.
95
+
96
+
- Open a second OHIF client on the same computer or on a tablet. It will show up in the admin portal with its user.
97
+
- Open the conference portal in the sproket icon. Choose a title and choose both the PC and tablet user.
98
+
- Check that all three clients receive and send imaging-study open/close messages.
132
99
133
100
134
101
@@ -185,6 +152,50 @@ _No response_
185
152
186
153
# Background and References
187
154
155
+
## Background
156
+
157
+
Healthcare environments sometimes involve multiple specialized applications working together to support clinical workflows. These applications need to communicate and coordinate in real-time, sharing events such as user interactions, data exchanges, state changes, and workflow transitions. A typical scenario is radiology reporting where a worklist, viewer, reporting and EMR integrate to produce the diagnostic report. This workflow is defined in the IHE Integrated Reporting Applications profile.
158
+
159
+
FHIRcast provides a solid foundation for FHIR-based context management, focusing specifically on synchronizing FHIR resource context across applications. However, the healthcare ecosystem includes many non-FHIR data formats, such as DICOM, openEHR and use cases that extend beyond context management such has navigation controllers, VR controllsers, joysticks and footswitches. Cast addresses this by providing a flexible, extensible framework that supports:
-**Data Exchange Events**: FHIR, DICOM data synchronization (potentially called DICOMCast), HL7 V2 messages, proprietary formats
163
+
-**Workflow Events**: Task assignments, status updates, notifications
164
+
-**Any Custom Event Types**: Domain-specific events defined by applications
165
+
166
+
Cast supports **bi-directional WebSocket communication**. This enables low-latency, "gaming style" interactions where applications can exchange events in real-time with minimal delay, supporting use cases such as collaborative viewing, synchronized navigation, and interventional workflows that require immediate feedback and coordination.
167
+
168
+
Cast also supports **collaborative multi-user workflows** through the hub's ability to group users together within sessions. The hub can coordinate multiple users, allowing them to share events and synchronize their applications in real-time. This enables scenarios such as tumor board meetings, where multiple radiologists and clinicians can simultaneously view and interact with the same DICOM study, with measurements, annotations, and navigation synchronized across all participants own viewers.
169
+
170
+
171
+
The hub-based architecture provides **flexible integration** because applications do not need to connect directly to each other—they only need to reach the hub. This enables applications running on different platforms and locations to seamlessly participate in the same workflow. For example, a 3D Slicer application running on trame in the cloud can communicate with a mobile device application, a web-based viewer, or local camera control , all through the hub without requiring direct network connections between them.
172
+
173
+
### Cast Ecosystem
174
+
175
+
Cast serves as an umbrella standard that encompasses specialized "Cast" variants for different healthcare domains and use cases:
0 commit comments