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 identify specific report contents to other subscribers for potential synchronization.
Table 2:4.151.2-1: Actor Roles
Role | Description | Actor(s) |
---|---|---|
Sender | Selects report content(s) | Content Creator |
Manager | Manages the selection state of contents | Hub |
FHIRcast: Content Sharing
FHIRcast: DiagnosticReport select Event
FHIR R5: DiagnosticReport resource
Figure 2:4.151.4-1: Interaction Diagram
The Sender sends an event to the Manager to indicate some report contents are selected.
The Sender shall support sending such messages to more than one Manager. The Manager shall support handling such messages from more than one Sender.
The Sender determines the selection state of some report contents should be synchronized with other Subscribers.
The Sender determines that the selected content are no longer required and reset the selection.
Note: Prior selected content are automatically reset by the selection of new content. Reset is used when the current selected content should be unselected without selecting new contents. See DiagnosticReport select Event Workflow for details.
Selections are initiated manually by a user, or automatically for reset only.
This message is a FHIRcast Request Context Change request. The Sender is the FHIRcast Subscriber. The Manager is the FHIRcast Hub.
The event.context
shall conform to DiagnosticReport select Event.
The Sender shall include all selected resources in the event, including resources that were selected previously which should remain selected.
Note: This is necessary because there is an implicit unselect of any previously selected resources for each new
DiagnosticReport-select
event received. See DiagnosticReport select Event Workflow for details.
If the Sender is retrying this context change request due to not receiving a response from the Manager for a prior request, then the Sender shall use the same event.id
. If the Manager received the original request, this allows it to detect that it is a duplicate message.
If the Sender retries the request due to an error response from the Manager, then the Sender shall assign a new event.id
to indicate that it is a new request.
The Manager shall receive and validate the request. See Section 2:4.151.4.2.2 for error conditions.
The Manager shall ignore any selected resources in the request that are not known based on any previous DiagnosticReport-open
or DiagnosticReport-update
events.
Note: The Manager should continue to process the request and should not return an error due to unknown selected resources.
The Manager finishes processing the Select Report Content request.
This message is a FHIRcast Request Context Change response. The Sender is the FHIRcast Subscriber. The Manager is the FHIRcast Hub.
If the Manager ignore unknown resources, then it shall return 206
Partial Content.
The Manager shall return 400
Bad Request error:
timestamp
, id
or event
are not setevent.context
does not include report
and select
event
.hub.topic
is not a known sessionThe Manager may return other applicable HTTP error status codes.
If the response is an error, then the Sender may consider retrying the request.
See IRA Security Considerations.
Local policy should consider what users and systems have permissions to select report content and configure appropriately.
This transaction is not associated with an ATNA Trigger Event.