Figure 2:3.X3.4-1: Interaction Diagram

2:3.X3.4.1 Open Report Context Request Message

The Sender sends an event to the Manager to open a report context. The Sender shall support sending such messages to more than one Manager.

The Manager shall support handling such messages from more than one Sender.

2:3.X3.4.1.1 Trigger Events

A Sender uses this transaction when:

• It determines that work should begin on a new report, and opens a new context to synchronize that work with other Subscribers.
• It determines to resume a previously opened report that has not yet complete, and re-opens the same context to synchronize that work with other Subscribers.

2:3.X3.4.1.2 Message Semantics

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 open Event.

Additional, the contexts in the event.context shall conform to the Table 2:3.X3.4.1.2-1:

Table 2:3.X3.4.1.2-1: Context Requirements

Key | Optionality | Context Requirements — | — | – report| REQUIRED | Conform to the DiagnosticReportContext resource patient | REQUIRED | Conform to the PatientContext resource study | REQUIRED* | Conform to the ImagingStudyContext resource

Note: Rows with ‘*’ in the Optionality column have constraints different from baseline FHIRcast Request Context Change request.

If the Sender resumes a previously opened report, then the Sender shall reuse the previous report, patient and study contexts, but shall assign a new event.id.

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.

2:3.X3.4.1.3 Expected Actions

The Manager shall receive and validate the request. See 2:3.X3.4.2.2 for error conditions.

Per FHIRcast, this report context will become the current context in this reporting session.

If the report, patient and study contexts in the request match an existing report context which has not been closed, then the Manager shall update that report context and set it to be the current context.

2:3.X3.4.2 Open Report Context Response Message

2:3.X3.4.2.1 Trigger Events

The Manager finishes processing the Open Report Context request.

2:3.X3.4.2.2 Message Semantics

This message is a FHIRcast Request Context Change response. The Sender is the FHIRcast Subscriber. The Manager is the FHIRcast Hub.

The Manager shall return 400 Bad Request error if:

• If timestamp, id or event are not set
• If event.context does not include report, patient and study
• if event.hub.topic is not a known session
• If report context in the request matches an existing report context, but either patient or study context do not match

The Manager may return other applicable HTTP error status codes.

2:3.X3.4.2.3 Expected Actions

If the response is an error, then the Sender may consider retrying the request.

2:3.X3.5 Security Considerations

See IRA Security Considerations

Local policy should consider what users and systems have permissions to open a report context and configure appropriately.

2:3.X3.5.1 Security Audit Considerations

This transaction is not associated with an ATNA Trigger Event.