Integrated Reporting Applications
1.0.0 - Trial-Implementation
This page is part of the Integrated Reporting Applications (v1.0.0: Publication) based on FHIR v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions
This transaction is used to connect to a notification channel to receive synchronization events.
Table 2:4.147.2-1: Actor Roles
Role | Description | Actor(s) |
---|---|---|
Subscriber | Initiate a websocket notification channel request | Image Display Report Creator Worklist Client Evidence Creator Stateless Evidence Creator Watcher |
Manager | Establish a websocket notification channel and manage connection | Hub |
FHIRcast: Subscribing to Events
Websocket: IETF RFC 6455
Figure 2:4.147.4-1: Interaction Diagram
The Subscriber sends a websocket connection request to the Manager.
The Subscriber shall support sending such messages to more than one Manager. The Manager shall support handling such messages from more than one Subscriber.
The Subscriber receives a successful Subscribe to Reporting Session [RAD-146] response.
This message is a websocket connection request. The Subscriber is the Client. The Manager is the Server.
The Subscriber shall send a websocket request to the hub.channel.endpoint
websocket WSS URL received from the successful Subscribe to Reporting Session [RAD-146] response.
The Manager shall process the request.
The Manager shall return an error if the websocket identifier in the WSS URL does not exist.
The Manager shall keep the websocket connection open for use as a notification channel.
The Manager shall use the opened websocket connection when sending subsequent events to the Subscriber.
The Manager processes the websocket connection request.
This is a FHIRcast Subscription Confirmation. The Subscriber is the FHIRcast Subscriber. The Manager is the FHIRcast Hub.
The Subscriber will find the duration of the websocket lease in the hub.lease_seconds
attribute of this message. When the lease expires, the Manager may drop the connection. It is the responsibility of the Subscriber to renew the subscription as needed before it expires using Subscribe to Reporting Session [RAD-146].
See IRA Security Considerations.
This transaction is not associated with an ATNA Trigger Event.