This operation sends an Event Report over an established WebSocket connection.
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.
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.
Example WebSocket payload:
{
"00000002": [ "1.2.840.10008.5.1.4.34.6.4" ],
"00000100": [ 256 ],
"00000110": [ 23 ],
"00001000": [ "1.2.840.10008.5.1.4.34.6.4.2.3.44.22231" ],
"00001001": [ 1 ],
"00741238": [ "SCHEDULED" ],
"00744041": [ "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.