6.9.11 SendEventReport

6.9.11 SendEventReport
Prev	6.9 UPS-RS Worklist Service	Next

This operation sends an Event Report over an established WebSocket connection.

6.9.11.1 Request

The request message shall be formed as follows:

Resource
- N/A
Method
- WebSocket Data Frame transmission
The Event Report shall contain all mandatory attributes described indescribed in Table CC.2.4-1 in PS3.4 and Table 10.3-1 in PS3.7 for the event type.

6.9.11.1.1 Request Message Body

WebSocket Events are encoded as WebSocket data frames with an opcode of "%x1" (text).

The frame payload data shall be a DICOM JSON dataset containing the attributes of the Event Report.

Note

Example WebSocket payload:

{
"00000002": { "vr" : "UI", [ "1.2.840.10008.5.1.4.34.6.4" ] },
"00000100": { "vr" : "US", [ 256 ] },
"00000110": { "vr" : "US", [ 23 ] },
"00000800": { "vr" : "US", [ 0 ] },
"00001000": { "vr" : "UI", [ "1.2.840.10008.5.1.4.34.6.4.2.3.44.22231" ] },
"00001001": { "vr" : "US", [ 1 ] },
"00741238": { "vr" : "CS", [ "SCHEDULED" ] },
"00744041": { "vr" : "CS", [ "READY" ] }
}

The WebSocket protocol does not allow content negotiation so it is not possible to support both XML and JSON encoding of Event Report messages without extending the protocol.

Prev	Up	Next
6.9.10.3.2 Response Message Body	Home	6.9.11.2 Behavior