pynetdicom._handlers.doc_handle_delete¶
- pynetdicom._handlers.doc_handle_delete(event)[source][source]¶
Documentation for handlers bound to
evt.EVT_N_DELETE.Use of handlers for
evt.EVT_N_DELETEis not yet supported.User implementation of this event handler is required if one or more services that use N-DELETE are to be supported. If a handler is not implemented and bound to
evt.EVT_N_DELETEthen the N-DELETE request will be responded to using a Status value of FIXME.Event
evt.EVT_N_DELETESupported Service Classes
Status
- Parameters
event (events.Event) –
The event representing a service class receiving a N-DELETE request message.
Eventattributes are:assoc: theassociationthat is running the service that received the N-DELETE request.context: the presentation context the request was sent under as apresentation.PresentationContextTuple.description: a description of the event that occurred as str.name: the name of the event that occurred as str.request: the receivedN-DELETE requesttimestamp: the date and time that the N-DELETE request was processed by the service.
- Returns
status – The status returned to the peer AE in the N-DELETE response. Must be a valid N-DELETE status value for the applicable Service Class as either an
intor aDatasetobject containing (at a minimum) a (0000,0900) Status element. If returning aDatasetobject then it may also contain optional elements related to the Status (as in DICOM Standard Part 7, Annex C).- Return type
- Raises
NotImplementedError – If the handler has not been implemented and bound to
evt.EVT_N_DELETEby the user.
See also
send_n_delete()N_DELETEReferences
DICOM Standard Part 4, Annexes H and DD