pynetdicom._handlers.doc_handle_create¶
- pynetdicom._handlers.doc_handle_create(event)[source][source]¶
Documentation for handlers bound to
evt.EVT_N_CREATE.User implementation of this event handler is required if one or more services that use N-CREATE are to be supported. If a handler is not implemented and bound to
evt.EVT_N_CREATEthen the N-CREATE request will be responded to using a Status value of0x0110- Processing Failure.Management of the SOP Instances created in response to an N-CREATE request is the responsibility of the user.
Event
evt.EVT_N_CREATESupported Service Classes
Modality Performed Procedure Step Management
Status
- Success
0x0000- Success- Failure
0x0105- No such attribute0x0106- Invalid attribute value0x0107- Attribute list error0x0110- Processing failure0x0111- Duplicate SOP Instance0x0116- Attribute value out of range0x0117- Invalid object instance0x0118- No such SOP Class0x0120- Missing attribute0x0121- Missing attribute value0x0124- Refused: not authorised0x0210- Duplicate invocation0x0211- Unrecognised operation0x0212- Mistyped argument0x0213- Resource limitation0xA510- Failed: an initiate media creation action has already been received for this SOP Instance0xC221- The Referenced Fraction Group Number does not exist in the referenced plan0xC222- No beams exist within the referenced fraction group0xC223- SCU already verifying and cannot currently process this request0xC227- No such object instance - Referenced RT Plan not found0xC309- The provided value of UPS State was not ‘SCHEDULED’0xC616- There is an existing Film Box that has not been printed and N-ACTION at the Film Session level is not supported. A new Film Box will not be created when a previous Film Box has not been printed- Warning
0xB300- THE UPS was created with modifications0xB600- Memory allocation not supported0xB605- Requested Min Density or Max Density outside of printer’s operating range. The printer will use its respective minimum or maximum density value instead
- Parameters
event (events.Event) –
The event representing a service class receiving a N-CREATE request message.
Eventattributes are:assoc: theassociationthat is running the service that received the N-CREATE 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-CREATE requesttimestamp: the date and time that the N-CREATE request was processed by the service.
Event properties are:
attribute_list: the decodedDatasetcontained within the N-CREATE request’s Attribute List parameter. Because pydicom uses a deferred read when decoding data, if the decode fails the returnedDatasetwill only raise an exception at the time of use.
- Returns
status (pydicom.dataset.Dataset or int) – The status returned to the peer AE in the N-CREATE response. Must be a valid N-CREATE 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).dataset (pydicom.dataset.Dataset or None) – If the status category is ‘Success’ or ‘Warning’ then a
Datasetcontaining elements of the response’s Attribute List conformant to the specifications in the corresponding Service Class.If the status category is not ‘Success’ or ‘Warning’ then
None.
- Raises
NotImplementedError – If the handler has not been implemented and bound to
evt.EVT_N_CREATEby the user.
See also
send_n_create()N_CREATEReferences
DICOM Standard Part 4, Annexes F, H, R, S, CC and DD