Integrated Reporting Applications
0.1.1 - ci-build
Integrated Reporting Applications, published by IHE Radiology Technical Committee. This is not an authorized publication; it is the continuous build for version 0.1.1). This version is based on the current content of https://github.com/IHE/RAD.RTC-IMR/ and changes regularly. See the Directory of published versions
This transaction is used to retrieve the current context for a given session and all associated contents in that context.
Table 2:3.X8.2-1: Actor Roles
Role | Description | Actor(s) |
---|---|---|
Subscriber | Requests current context and contents for an identified session | Image Display Report Creator Worklist Client Evidence Creator Watcher |
Manager | Returns current context and contents | Hub |
FHIRcast: Get Current Context
Figure 2:3.X8.4-1: Interaction Diagram
The Subscriber requests the current context and its contents for an identified session. 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 uses this transaction when:
[FHIRresource]-close
event and wants to synchronize with the new current context, if anyThis message is a Get Current Context Request. The Subscriber is the FHIRcast Subscriber. The Manager is the FHIRcast Hub.
The topic in the request URL will identifies the session for which the current context and contents are being requested.
The Manager shall validate if the topic
specified in the request URL is a valid session.
The Manager shall retrieve the current context and all associated contents correspond to the topic
in the request URL.
Note: The current context is the anchor context with all associated contexts. For example, in a
DiagnosticReport-open
event, the current context includesreport
,patient
andstudy
contexts, in whichreport
is the anchor context.
The Manager returns the current context and all associated contents.
The Manager receives the Get Current Context request.
This message is a Get Current Context Response. The Subscriber is the FHIRcast Subscriber. The Manager is the FHIRcast Hub.
The Manager shall include the content
key in the response. See Content Sharing Support for details.
The Subscriber shall process the context as if it had received the [FHIRresource]-open
event with the same context.
The Subscriber shall replace the set of known contents associated with the context with the resources in the content
bundle according to its business logic.
See IRA Security Considerations
Managers that support the ATNA Profile shall audit this transaction.
This transaction corresponds to a Query Information ATNA Trigger Event.