diff --git a/dev/_sources/index.rst.txt b/dev/_sources/index.rst.txt
index 789f9a4d4..469ad5c67 100644
--- a/dev/_sources/index.rst.txt
+++ b/dev/_sources/index.rst.txt
@@ -4,7 +4,7 @@
============
:gh:`pynetdicom The The The source code for the application can be found here The The The The echoscp¶
Description¶
echoscp
application implements a Service Class Provider (SCP) for the
-Verification service class. It listens for
+Verification service class. It listens for
incoming association requests on the specified port, and once an association
is established, responds to incoming C-ECHO requests. The application can be
used to verify basic DICOM connectivity.echoscu¶
Description¶
echoscu
application implements a Service Class User (SCU) for the
-Verification service class. It establishes an
+Verification service class. It establishes an
association with a peer Application Entity (AE), sends a
-C-ECHO request and waits for a
+C-ECHO request and waits for a
response. The application can be used to verify basic DICOM connectivity.findscu¶
Description¶
findscu
application implements a Service Class User (SCU) for
-the Query/Retrieve and
-Basic Worklist Management service classes. It
+the Query/Retrieve and
+Basic Worklist Management service classes. It
requests an association with a peer Application Entity and once established,
sends a C-FIND query to be matched against the SCP’s managed SOP Instances.
The SCP then responds with the matching query keys.getscu¶
Description¶
getscu
application implements a Service Class User (SCU) for
-the Query/Retrieve service class. It requests an
+the Query/Retrieve service class. It requests an
association with a peer Application Entity and once established, sends a C-GET
query to be matched against the Query/Retrieve SCP’s managed SOP Instances.
The QR SCP then responds by sending a copy of the matching SOP Instances (i.e.
diff --git a/dev/apps/movescu.html b/dev/apps/movescu.html
index 3b036dac2..a80dfa5a5 100644
--- a/dev/apps/movescu.html
+++ b/dev/apps/movescu.html
@@ -135,8 +135,8 @@ movescu¶
Description¶
movescu
application implements a Service Class User (SCU) for
-the Query/Retrieve service class and optionally
-a Service Class Provider (SCP) for the Storage
+the Query/Retrieve service class and optionally
+a Service Class Provider (SCP) for the Storage
service class. It requests an association with a peer Application Entity and
once established, sends a C-MOVE query to be matched against
the Query/Retrieve SCP’s managed SOP Instances. The QR SCP then responds by
diff --git a/dev/apps/qrscp.html b/dev/apps/qrscp.html
index 88bedea5b..7f155dc74 100644
--- a/dev/apps/qrscp.html
+++ b/dev/apps/qrscp.html
@@ -130,7 +130,7 @@ qrscp¶
Description¶
qrscp
application implements a Service Class Provider (SCP) for the
-Verification, Storage and Query/Retrieve
+Verification, Storage and Query/Retrieve
service classes. It listens for incoming association requests on the
configured port, and once an association is established, allows Service Class
Users (SCUs) to:Descriptionqrscp application implements a Service Class Provider (SCP) for the
-Basic Modality Worklist, and Unified Procedure Step
+Basic Modality Worklist, and Unified Procedure Step
service classes, but currently will only return empty results (0 records)
Warning
diff --git a/dev/apps/storescp.html b/dev/apps/storescp.html index 2926bb7d3..26dbc494d 100644 --- a/dev/apps/storescp.html +++ b/dev/apps/storescp.html @@ -125,7 +125,7 @@The storescp
application implements a Service Class Provider (SCP) for
-the Storage service class. It listens for
+the Storage service class. It listens for
incoming association requests on the specified port, and once an association
is established, allows Storage SCUs to transfer SOP Instances.
The source code for the application can be found here
diff --git a/dev/apps/storescu.html b/dev/apps/storescu.html index 95b39b099..88fe20b06 100644 --- a/dev/apps/storescu.html +++ b/dev/apps/storescu.html @@ -125,7 +125,7 @@The storescu
application implements a Service Class User (SCU) for
-the Storage service class. It requests an
+the Storage service class. It requests an
association with a peer Application Entity and once established requests the
transfer of one or more SOP Instances.
The source code for the application can be found here
diff --git a/dev/examples/basic_worklist.html b/dev/examples/basic_worklist.html index a4eef64a3..7f73e24e5 100644 --- a/dev/examples/basic_worklist.html +++ b/dev/examples/basic_worklist.html @@ -108,7 +108,7 @@The DICOM Basic Worklist Management Service +
The DICOM Basic Worklist Management Service provides a mechanism for a service user to access worklists on another AE. Querying of the SCP for worklists is accomplished by utilising the DIMSE C-FIND service.
@@ -119,7 +119,7 @@from pydicom.dataset import Dataset
diff --git a/dev/examples/display.html b/dev/examples/display.html
index b7afd9bfd..2269367c0 100644
--- a/dev/examples/display.html
+++ b/dev/examples/display.html
@@ -108,7 +108,7 @@
Display System Management Service Examples¶
-The DICOM Display System Management Service
+
The DICOM Display System Management Service
allows an Application Entity to retrieve Display Subsystem parameters from a
peer by using the N-GET service. It only has a single
supported SOP Class.
diff --git a/dev/examples/mpps.html b/dev/examples/mpps.html
index a1eafc21e..a56ffb5b3 100644
--- a/dev/examples/mpps.html
+++ b/dev/examples/mpps.html
@@ -109,7 +109,7 @@
Modality Performed Procedure Step Management Service Examples¶
-The DICOM Modality Performed Procedure Step Management (MPPS) service
+
The DICOM Modality Performed Procedure Step Management (MPPS) service
allows an Application Entity to log or track procedures performed by a
modality through the N-CREATE, N-SET, N-EVENT-REPORT and N-GET services. It
has three SOP Classes:
diff --git a/dev/examples/print.html b/dev/examples/print.html
index 9bfb1e4fe..65df2e641 100644
--- a/dev/examples/print.html
+++ b/dev/examples/print.html
@@ -112,7 +112,7 @@
Print Management Service Examples¶
-The DICOM Print Management service
+
The DICOM Print Management service
facilitates print of images and image related data. There are two Basic Print
Management Meta SOP Classes which correspond with the minimum functionality
that an implementation of the Print Management service class shall support (i.e
diff --git a/dev/examples/qr_find.html b/dev/examples/qr_find.html
index f95725cfc..c451bc1dc 100644
--- a/dev/examples/qr_find.html
+++ b/dev/examples/qr_find.html
@@ -108,7 +108,7 @@
Query/Retrieve (Find) Service Examples¶
-The DICOM Query/Retrieve Service
+
The DICOM Query/Retrieve Service
provides a mechanism for a service user to query the SOP Instances managed
by a QR SCP. The QR (Find) SOP classes allow an SCU to receive a list of
attributes matching the requested query. This is accomplished through the
diff --git a/dev/examples/qr_get.html b/dev/examples/qr_get.html
index 9760e149c..906d0e658 100644
--- a/dev/examples/qr_get.html
+++ b/dev/examples/qr_get.html
@@ -108,7 +108,7 @@
Query/Retrieve (Get) Service Examples¶
-The DICOM Query/Retrieve Service
+
The DICOM Query/Retrieve Service
provides a mechanism for a service user to query and retrieve the SOP Instances
managed by a QR SCP. The QR (Get) SOP classes allow an SCU to receive SOP
Instances that match the requested query. This is accomplished through the
@@ -156,7 +156,7 @@
Query/Retrieve (Get) SCU
If you’re going to write SOP Instances (datasets) to file it’s recommended
that you ensure the file is conformant with the
-DICOM File Format, which requires adding the
+DICOM File Format, which requires adding the
File Meta Information.
Check the
handler implementation documentation
diff --git a/dev/examples/qr_move.html b/dev/examples/qr_move.html
index 9236d5d76..8a711d0d9 100644
--- a/dev/examples/qr_move.html
+++ b/dev/examples/qr_move.html
@@ -108,7 +108,7 @@
Query/Retrieve (Move) Service Examples¶
-The DICOM Query/Retrieve Service
+
The DICOM Query/Retrieve Service
provides a mechanism for a service user to query and retrieve the SOP Instances
managed by a QR SCP. The QR (Move) SOP classes allow an SCU to request an SCP
send matching SOP Instances to a known Storage SCP over a new association.
diff --git a/dev/examples/relevant_patient.html b/dev/examples/relevant_patient.html
index 53c662b0d..34a907624 100644
--- a/dev/examples/relevant_patient.html
+++ b/dev/examples/relevant_patient.html
@@ -108,7 +108,7 @@
Relevant Patient Information Query Service Examples¶
-The DICOM Relevant Patient Information Query Service
+
The DICOM Relevant Patient Information Query Service
provides a mechanism for an SCU to access relevant patient information managed
by an SCP. This is accomplished through the DIMSE C-FIND service.
diff --git a/dev/examples/storage.html b/dev/examples/storage.html
index 7cd14fb88..2e2a79d04 100644
--- a/dev/examples/storage.html
+++ b/dev/examples/storage.html
@@ -108,7 +108,7 @@
Storage Service Examples¶
-The DICOM Storage Service
+
The DICOM Storage Service
provides a mechanism for an SCU to request the transfer
of supported Storage SOP Class instances to
the service provider. Transfer is accomplished by utilising the
@@ -198,7 +198,7 @@
Storage SCUa 0x0000 Success status.
If you’re going to write SOP instances (datasets) to file it’s recommended
that you ensure the file is conformant with the
-DICOM File Format,
+DICOM File Format,
which requires adding the File Meta Information.
Check the
handler implementation documentation
diff --git a/dev/examples/verification.html b/dev/examples/verification.html
index 8f5c36d86..a5b43c341 100644
--- a/dev/examples/verification.html
+++ b/dev/examples/verification.html
@@ -108,7 +108,7 @@
Verification Service Examples¶
-The DICOM Verification Service
+
The DICOM Verification Service
allows an Application Entity to verify application level communication between
itself and another AE by using the DIMSE C-ECHO service. It only has a single
supported SOP Class.
diff --git a/dev/index.html b/dev/index.html
index e20859fb3..1201210a8 100644
--- a/dev/index.html
+++ b/dev/index.html
@@ -91,7 +91,7 @@
pynetdicom¶
pynetdicom is a pure Python package
-that implements the DICOM networking protocol.
+that implements the DICOM networking protocol.
Working with
pydicom, it allows the easy creation
of DICOM Application Entities (AEs), which can then act as Service Class
@@ -148,7 +148,7 @@ Getting started
Supported Service Classes¶
-pynetdicom currently supports the following DICOM service classes:
+pynetdicom currently supports the following DICOM service classes:
diff --git a/dev/reference/generated/pynetdicom.PYNETDICOM_IMPLEMENTATION_UID.html b/dev/reference/generated/pynetdicom.PYNETDICOM_IMPLEMENTATION_UID.html
index 09df4f296..9970822f3 100644
--- a/dev/reference/generated/pynetdicom.PYNETDICOM_IMPLEMENTATION_UID.html
+++ b/dev/reference/generated/pynetdicom.PYNETDICOM_IMPLEMENTATION_UID.html
@@ -124,7 +124,7 @@
pynetdicom.PYNETDICOM_IMPLEMENTATION_UID¶
-
-pynetdicom.PYNETDICOM_IMPLEMENTATION_UID: UID = '1.2.826.0.1.3680043.9.3811.2.1.0'[source]¶
+pynetdicom.PYNETDICOM_IMPLEMENTATION_UID: UID = '1.2.826.0.1.3680043.9.3811.2.1.0'[source]¶
The (0002,0012) Implementation Class UID used by pynetdicom
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_acse.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_acse.html
index cac104b1d..f28accb07 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_acse.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_acse.html
@@ -131,7 +131,7 @@
pynetdicom._handlers.doc_handle_acse¶
-
-pynetdicom._handlers.doc_handle_acse(event: Event, *args: Sequence[Any]) None [source]¶
+pynetdicom._handlers.doc_handle_acse(event: Event, *args: Sequence[Any]) None [source]¶
Documentation for handlers bound to evt.EVT_ACSE_RECV
or
evt.EVT_ACSE_SENT
.
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_action.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_action.html
index d1521a6cf..166123084 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_action.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_action.html
@@ -139,7 +139,7 @@
pynetdicom._handlers.doc_handle_action¶
-
-pynetdicom._handlers.doc_handle_action(event: Event, *args: Sequence[Any]) Tuple[Dataset | int, Dataset | None] [source]¶
+pynetdicom._handlers.doc_handle_action(event: Event, *args: Sequence[Any]) Tuple[Dataset | int, Dataset | None] [source]¶
Documentation for handlers bound to evt.EVT_N_ACTION
.
User implementation of this event handler is required if one or more
services that use N-ACTION are to be supported. If a handler is
@@ -150,12 +150,12 @@
pynetdicom._handlers.doc_handle_actionevt.EVT_N_ACTION
Supported Service Classes
-
-
-
-
-
-
+
+
+
+
+
+
Status
+DICOM Standard, Part 7, Annex C).
dataset (pydicom.dataset.Dataset or None) – If the status category is ‘Success’ or ‘Warning’ then a
Dataset
containing elements for the
response’s Action Reply conformant to the specifications in the
@@ -308,16 +308,16 @@
pynetdicom._handlers.doc_handle_actionReferences
-DICOM Standard, Part 4, Annex H
-DICOM Standard, Part 4, Annex J
-DICOM Standard, Part 4, Annex P
-DICOM Standard, Part 4, Annex S
-DICOM Standard, Part 4, Annex CC
-DICOM Standard, Part 4, Annex DD
+DICOM Standard, Part 4, Annex H
+DICOM Standard, Part 4, Annex J
+DICOM Standard, Part 4, Annex P
+DICOM Standard, Part 4, Annex S
+DICOM Standard, Part 4, Annex CC
+DICOM Standard, Part 4, Annex DD
DICOM Standard, Part 7, Sections
-10.1.4,
-10.3.4 and
-Annex C
+10.1.4,
+10.3.4 and
+Annex C
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_assoc.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_assoc.html
index 0368fc4db..05b5d519a 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_assoc.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_assoc.html
@@ -131,7 +131,7 @@
pynetdicom._handlers.doc_handle_assoc¶
-
-pynetdicom._handlers.doc_handle_assoc(event: Event, *args: Sequence[Any]) None [source]¶
+pynetdicom._handlers.doc_handle_assoc(event: Event, *args: Sequence[Any]) None [source]¶
Documentation for handlers bound to evt.EVT_ACCEPTED
,
evt.EVT_ESTABLISHED
, evt.EVT_REJECTED
, evt.EVT_REQUESTED
,
evt.EVT_RELEASED
or evt.EVT_ABORTED
.
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_async.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_async.html
index 2668af1bc..2347648ad 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_async.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_async.html
@@ -139,11 +139,11 @@
pynetdicom._handlers.doc_handle_async¶
-
-pynetdicom._handlers.doc_handle_async(event: Event, *args: Sequence[Any]) Tuple[int, int] [source]¶
+pynetdicom._handlers.doc_handle_async(event: Event, *args: Sequence[Any]) Tuple[int, int] [source]¶
Documentation for handlers bound to evt.EVT_ASYNC_OPS
.
User implementation of this event handler is optional. If a handler is
not implemented and bound to evt.EVT_ASYNC_OPS
then no response to the
-Asynchronous Operations Window Negotiation
+Asynchronous Operations Window Negotiation
item will be sent in reply to the association requestor.
Because pynetdicom doesn’t support asynchronous operations if the
handler is implemented then the response to the asynchronous
@@ -197,7 +197,7 @@
pynetdicom._handlers.doc_handle_asyncReferences
-DICOM Standard, Part 7, Annex D.3.3.3
+DICOM Standard, Part 7, Annex D.3.3.3
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_c_get.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_c_get.html
index f58def75e..2a71b2126 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_c_get.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_c_get.html
@@ -139,7 +139,7 @@
pynetdicom._handlers.doc_handle_c_get¶
-
-pynetdicom._handlers.doc_handle_c_get(event: Event, *args: Sequence[Any]) Iterator[int | Dataset | None] [source]¶
+pynetdicom._handlers.doc_handle_c_get(event: Event, *args: Sequence[Any]) Iterator[int | Dataset | None] [source]¶
Documentation for handlers bound to evt.EVT_C_GET
.
User implementation of this event handler is required if one or more
services that use C-GET are to be supported. If a handler is
@@ -151,12 +151,12 @@
pynetdicom._handlers.doc_handle_c_getevt.EVT_C_GET
Supported Service Classes
-
-
-
-
-
-
+
+
+
+
+
+
Status
@@ -250,7 +250,7 @@ pynetdicom._handlers.doc_handle_c_getDataset
object then
it may also contain optional elements related to the Status (as in
-DICOM Standard, Part 7, Annex C).
+DICOM Standard, Part 7, Annex C).
dataset (pydicom.dataset.Dataset or None) – If the status category is ‘Pending’ then yield the
Dataset
to send to the peer via a C-STORE
sub-operation over the current association.
@@ -272,18 +272,18 @@ pynetdicom._handlers.doc_handle_c_getReferences
-DICOM Standard, Part 4, Annex C
-DICOM Standard, Part 4, Annex U
-DICOM Standard, Part 4, Annex X
-DICOM Standard, Part 4, Annex Y
-DICOM Standard, Part 4, Annex Z
-DICOM Standard, Part 4, Annex BB
-DICOM Standard, Part 4, Annex HH
-DICOM Standard, Part 4, Annex II
+DICOM Standard, Part 4, Annex C
+DICOM Standard, Part 4, Annex U
+DICOM Standard, Part 4, Annex X
+DICOM Standard, Part 4, Annex Y
+DICOM Standard, Part 4, Annex Z
+DICOM Standard, Part 4, Annex BB
+DICOM Standard, Part 4, Annex HH
+DICOM Standard, Part 4, Annex II
DICOM Standard, Part 7, Sections
-9.1.3,
-9.3.3 and
-Annex C
+9.1.3,
+9.3.3 and
+Annex C
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_create.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_create.html
index d9f2e6d97..20d42739b 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_create.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_create.html
@@ -139,7 +139,7 @@
pynetdicom._handlers.doc_handle_create¶
-
-pynetdicom._handlers.doc_handle_create(event: Event, *args: Sequence[Any]) Tuple[Dataset | int, Dataset | None] [source]¶
+pynetdicom._handlers.doc_handle_create(event: Event, *args: Sequence[Any]) Tuple[Dataset | int, Dataset | None] [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
@@ -152,12 +152,12 @@
pynetdicom._handlers.doc_handle_createevt.EVT_N_CREATE
Supported Service Classes
-
-
-
-
-
-
+
+
+
+
+
+
Status
@@ -252,7 +252,7 @@ pynetdicom._handlers.doc_handle_createDataset
object then
it may also contain optional elements related to the Status (as in
-DICOM Standard, Part 7, Annex C).
+DICOM Standard, Part 7, Annex C).
dataset (pydicom.dataset.Dataset or None) – If the status category is ‘Success’ or ‘Warning’ then a
Dataset
containing elements of the
response’s Attribute List conformant to the specifications in the
@@ -273,16 +273,16 @@
pynetdicom._handlers.doc_handle_createReferences
-DICOM Standard, Part 4, Annex F
-DICOM Standard, Part 4, Annex H
-DICOM Standard, Part 4, Annex R
-DICOM Standard, Part 4, Annex S
-DICOM Standard, Part 4, Annex CC
-DICOM Standard, Part 4, Annex DD
+DICOM Standard, Part 4, Annex F
+DICOM Standard, Part 4, Annex H
+DICOM Standard, Part 4, Annex R
+DICOM Standard, Part 4, Annex S
+DICOM Standard, Part 4, Annex CC
+DICOM Standard, Part 4, Annex DD
DICOM Standard, Part 7, Sections
-10.1.5,
-10.3.5
-and Annex C
+10.1.5,
+10.3.5
+and Annex C
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_data.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_data.html
index 5be37801d..09e1ce1aa 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_data.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_data.html
@@ -131,7 +131,7 @@
pynetdicom._handlers.doc_handle_data¶
-
-pynetdicom._handlers.doc_handle_data(event: Event, *args: Sequence[Any]) None [source]¶
+pynetdicom._handlers.doc_handle_data(event: Event, *args: Sequence[Any]) None [source]¶
Documentation for handlers bound to evt.EVT_DATA_RECV
or
evt.EVT_DATA_SENT
.
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_delete.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_delete.html
index f7fc4a930..93953d32d 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_delete.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_delete.html
@@ -139,7 +139,7 @@
pynetdicom._handlers.doc_handle_delete¶
-
-pynetdicom._handlers.doc_handle_delete(event: Event, *args: Sequence[Any]) int | Dataset [source]¶
+pynetdicom._handlers.doc_handle_delete(event: Event, *args: Sequence[Any]) int | Dataset [source]¶
Documentation for handlers bound to evt.EVT_N_DELETE
.
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
@@ -150,8 +150,8 @@
pynetdicom._handlers.doc_handle_deleteevt.EVT_N_DELETE
Supported Service Classes
Status
- Return type:
pydicom.dataset.Dataset or int
@@ -229,12 +229,12 @@ pynetdicom._handlers.doc_handle_deleteReferences
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_dimse.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_dimse.html
index 3b74454d2..9667be175 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_dimse.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_dimse.html
@@ -131,7 +131,7 @@
pynetdicom._handlers.doc_handle_dimse¶
-
-pynetdicom._handlers.doc_handle_dimse(event: Event, *args: Sequence[Any]) None [source]¶
+pynetdicom._handlers.doc_handle_dimse(event: Event, *args: Sequence[Any]) None [source]¶
Documentation for handlers bound to evt.EVT_DIMSE_RECV
or
evt.EVT_DIMSE_SENT
.
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_echo.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_echo.html
index 3e42fb269..81682eed5 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_echo.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_echo.html
@@ -139,7 +139,7 @@
pynetdicom._handlers.doc_handle_echo¶
-
-pynetdicom._handlers.doc_handle_echo(event: Event, *args: Sequence[Any]) int | Dataset [source]¶
+pynetdicom._handlers.doc_handle_echo(event: Event, *args: Sequence[Any]) int | Dataset [source]¶
Documentation for handlers bound to evt.EVT_C_ECHO
.
User implementation of this event handler is optional. If a handler is
not implemented and bound to evt.EVT_C_ECHO
then the C-ECHO request
@@ -148,7 +148,7 @@
pynetdicom._handlers.doc_handle_echoevt.EVT_C_ECHO
Supported Service Classes
Status
- Return type:
pydicom.dataset.Dataset or int
@@ -217,11 +217,11 @@ pynetdicom._handlers.doc_handle_echoReferences
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_event_report.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_event_report.html
index eca791745..5dcb5e528 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_event_report.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_event_report.html
@@ -139,7 +139,7 @@
pynetdicom._handlers.doc_handle_event_report¶
-
-pynetdicom._handlers.doc_handle_event_report(event: Event, *args: Sequence[Any]) Tuple[Dataset | int, Dataset | None] [source]¶
+pynetdicom._handlers.doc_handle_event_report(event: Event, *args: Sequence[Any]) Tuple[Dataset | int, Dataset | None] [source]¶
Documentation for handlers bound to evt.EVT_N_EVENT_REPORT
.
User implementation of this event handler is required if one or more
services that use N-EVENT-REPORT are to be supported. If a handler is
@@ -150,13 +150,13 @@
pynetdicom._handlers.doc_handle_event_reportevt.EVT_N_EVENT_REPORT
Supported Service Classes
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Status
dataset (pydicom.dataset.Dataset or None) – If the status category is ‘Success’ or ‘Warning’ then a
Dataset
containing elements of the
response’s Event Reply conformant to the specifications in the
@@ -250,15 +250,15 @@
pynetdicom._handlers.doc_handle_event_reportReferences
-DICOM Standard, Part 4, Annex F
-DICOM Standard, Part 4, Annex H
-DICOM Standard, Part 4, Annex J
-DICOM Standard, Part 4, Annex CC
-DICOM Standard, Part 4, Annex DD
+DICOM Standard, Part 4, Annex F
+DICOM Standard, Part 4, Annex H
+DICOM Standard, Part 4, Annex J
+DICOM Standard, Part 4, Annex CC
+DICOM Standard, Part 4, Annex DD
DICOM Standard, Part 7, Sections
-10.1.1,
-10.3.1
-and Annex C
+10.1.1,
+10.3.1
+and Annex C
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_find.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_find.html
index 63649dc29..b9a648efb 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_find.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_find.html
@@ -139,7 +139,7 @@
pynetdicom._handlers.doc_handle_find¶
-
-pynetdicom._handlers.doc_handle_find(event: Event, *args: Sequence[Any]) Iterator[Tuple[Dataset | int, Dataset | None]] [source]¶
+pynetdicom._handlers.doc_handle_find(event: Event, *args: Sequence[Any]) Iterator[Tuple[Dataset | int, Dataset | None]] [source]¶
Documentation for handlers bound to evt.EVT_C_FIND
.
User implementation of this event handler is required if one or more
services that use C-FIND are to be supported. If a handler is
@@ -153,16 +153,16 @@
pynetdicom._handlers.doc_handle_findevt.EVT_C_FIND
Supported Service Classes
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
Status
@@ -241,7 +241,7 @@ pynetdicom._handlers.doc_handle_findDataset
object then
it may also contain optional elements related to the Status (as in
-DICOM Standard, Part 7, Annex C).
+DICOM Standard, Part 7, Annex C).
identifier (pydicom.dataset.Dataset or None) – If the status category is ‘Pending’ then the Identifier
Dataset
for a matching SOP Instance. The
exact requirements for the C-FIND response Identifier are Service
@@ -260,20 +260,20 @@
pynetdicom._handlers.doc_handle_findReferences
-DICOM Standard, Part 4, Annex C
-DICOM Standard, Part 4, Annex K
-DICOM Standard, Part 4, Annex Q
-DICOM Standard, Part 4, Annex U
-DICOM Standard, Part 4, Annex V
-DICOM Standard, Part 4, Annex X
-DICOM Standard, Part 4, Annex BB
-DICOM Standard, Part 4, Annex CC
-DICOM Standard, Part 4, Annex HH
-DICOM Standard, Part 4, Annex II
+DICOM Standard, Part 4, Annex C
+DICOM Standard, Part 4, Annex K
+DICOM Standard, Part 4, Annex Q
+DICOM Standard, Part 4, Annex U
+DICOM Standard, Part 4, Annex V
+DICOM Standard, Part 4, Annex X
+DICOM Standard, Part 4, Annex BB
+DICOM Standard, Part 4, Annex CC
+DICOM Standard, Part 4, Annex HH
+DICOM Standard, Part 4, Annex II
DICOM Standard, Part 7, Sections
-9.1.2,
-9.3.2 and
-Annex C
+9.1.2,
+9.3.2 and
+Annex C
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_fsm.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_fsm.html
index c68ccd61e..8ac95aca3 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_fsm.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_fsm.html
@@ -131,7 +131,7 @@
pynetdicom._handlers.doc_handle_fsm¶
-
-pynetdicom._handlers.doc_handle_fsm(event: Event, *args: Sequence[Any]) None [source]¶
+pynetdicom._handlers.doc_handle_fsm(event: Event, *args: Sequence[Any]) None [source]¶
Documentation for handlers bound to evt.EVT_FSM_TRANSITION
.
- Parameters:
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_move.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_move.html
index a0ba632e9..c5d5772ba 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_move.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_move.html
@@ -139,7 +139,7 @@
pynetdicom._handlers.doc_handle_move¶
-
-pynetdicom._handlers.doc_handle_move(event: Event, *args: Sequence[Any]) Iterator[Tuple[str, int] | Tuple[str, int, Dict[str, Any]] | int | Dataset | None] [source]¶
+pynetdicom._handlers.doc_handle_move(event: Event, *args: Sequence[Any]) Iterator[Tuple[str, int] | Tuple[str, int, Dict[str, Any]] | int | Dataset | None] [source]¶
Documentation for handlers bound to evt.EVT_C_MOVE
.
User implementation of this event handler is required if one or more
services that use C-MOVE are to be supported. If a handler is
@@ -166,12 +166,12 @@
pynetdicom._handlers.doc_handle_moveevt.EVT_C_MOVE
Supported Service Classes
-
-
-
-
-
-
+
+
+
+
+
+
Status
@@ -273,7 +273,7 @@ pynetdicom._handlers.doc_handle_moveDataset
then it may also contain optional
elements related to the Status (as in
-DICOM Standard, Part 7, Annex C).
+DICOM Standard, Part 7, Annex C).
dataset (pydicom.dataset.Dataset or None) – If the status is ‘Pending’ then yield the
Dataset
to send to the peer via a C-STORE
sub-operation over a new association.
@@ -295,17 +295,17 @@ pynetdicom._handlers.doc_handle_moveReferences
-DICOM Standard, Part 4, Annex C
-DICOM Standard, Part 4, Annex U
-DICOM Standard, Part 4, Annex X
-DICOM Standard, Part 4, Annex Y
-DICOM Standard, Part 4, Annex BB
-DICOM Standard, Part 4, Annex HH
-DICOM Standard, Part 4, Annex II
+DICOM Standard, Part 4, Annex C
+DICOM Standard, Part 4, Annex U
+DICOM Standard, Part 4, Annex X
+DICOM Standard, Part 4, Annex Y
+DICOM Standard, Part 4, Annex BB
+DICOM Standard, Part 4, Annex HH
+DICOM Standard, Part 4, Annex II
DICOM Standard, Part 7, Sections
-9.1.4,
-9.3.4 and
-Annex C
+9.1.4,
+9.3.4 and
+Annex C
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_n_get.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_n_get.html
index 00f4c468a..97ce38161 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_n_get.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_n_get.html
@@ -139,7 +139,7 @@
pynetdicom._handlers.doc_handle_n_get¶
-
-pynetdicom._handlers.doc_handle_n_get(event: Event, *args: Sequence[Any]) Tuple[Dataset | int, Dataset | None] [source]¶
+pynetdicom._handlers.doc_handle_n_get(event: Event, *args: Sequence[Any]) Tuple[Dataset | int, Dataset | None] [source]¶
Documentation for handlers bound to evt.EVT_N_GET
.
User implementation of this event handler is required if one or more
services that use N-GET are to be supported. If a handler is
@@ -150,12 +150,12 @@
pynetdicom._handlers.doc_handle_n_getevt.EVT_N_GET
Supported Service Classes
-
-
-
-
-
-
+
+
+
+
+
+
Status
@@ -230,7 +230,7 @@ pynetdicom._handlers.doc_handle_n_getDataset
object then it may also contain
optional elements related to the Status (as in DICOM Standard, Part
-7, Annex C).
+7, Annex C).
dataset (pydicom.dataset.Dataset or None) – If the status category is ‘Success’ or ‘Warning’ then a
Dataset
containing elements matching the
request’s Attribute List conformant to the specifications in the
@@ -247,16 +247,16 @@
pynetdicom._handlers.doc_handle_n_getReferences
-DICOM Standard, Part 4, Annex F
-DICOM Standard, Part 4, Annex H
-DICOM Standard, Part 4, Annex S
-DICOM Standard, Part 4, Annex CC
-DICOM Standard, Part 4, Annex DD
-DICOM Standard, Part 4, Annex EE
+DICOM Standard, Part 4, Annex F
+DICOM Standard, Part 4, Annex H
+DICOM Standard, Part 4, Annex S
+DICOM Standard, Part 4, Annex CC
+DICOM Standard, Part 4, Annex DD
+DICOM Standard, Part 4, Annex EE
DICOM Standard, Part 7, Sections
-10.1.2,
-10.3.2
-and Annex C
+10.1.2,
+10.3.2
+and Annex C
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_pdu.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_pdu.html
index 93f3ddf80..450ea2e35 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_pdu.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_pdu.html
@@ -131,7 +131,7 @@
pynetdicom._handlers.doc_handle_pdu¶
-
-pynetdicom._handlers.doc_handle_pdu(event: Event, *args: Sequence[Any]) None [source]¶
+pynetdicom._handlers.doc_handle_pdu(event: Event, *args: Sequence[Any]) None [source]¶
Documentation for handlers bound to evt.EVT_PDU_RECV
or
evt.EVT_PDU_SENT
.
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_set.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_set.html
index 6817ab8c1..68cdec1ed 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_set.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_set.html
@@ -139,7 +139,7 @@
pynetdicom._handlers.doc_handle_set¶
-
-pynetdicom._handlers.doc_handle_set(event: Event, *args: Sequence[Any]) Tuple[Dataset | int, Dataset | None] [source]¶
+pynetdicom._handlers.doc_handle_set(event: Event, *args: Sequence[Any]) Tuple[Dataset | int, Dataset | None] [source]¶
Documentation for handlers bound to evt.EVT_N_SET
.
User implementation of this event handler is required if one or more
services that use N-SET are to be supported. If a handler is
@@ -150,10 +150,10 @@
pynetdicom._handlers.doc_handle_setevt.EVT_N_SET
Supported Service Classes
-
-
-
-
+
+
+
+
Status
@@ -261,7 +261,7 @@ pynetdicom._handlers.doc_handle_setDataset
object then it may also contain
optional elements related to the Status (as in DICOM Standard, Part
-7, Annex C).
+7, Annex C).
dataset (pydicom.dataset.Dataset or None) – If the status category is ‘Success’ or ‘Warning’ then a
Dataset
containing elements of the response’s
Attribute List conformant to the specifications in the corresponding
@@ -282,14 +282,14 @@
pynetdicom._handlers.doc_handle_setReferences
-DICOM Standard, Part 4, Annex F
-DICOM Standard, Part 4, Annex H
-DICOM Standard, Part 4, Annex CC
-DICOM Standard, Part 4, Annex DD
+DICOM Standard, Part 4, Annex F
+DICOM Standard, Part 4, Annex H
+DICOM Standard, Part 4, Annex CC
+DICOM Standard, Part 4, Annex DD
DICOM Standard, Part 7, Sections
-10.1.3,
-10.3.3
-and Annex C
+10.1.3,
+10.3.3
+and Annex C
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_sop_common.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_sop_common.html
index 7280422be..d7769e5c4 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_sop_common.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_sop_common.html
@@ -139,10 +139,10 @@
pynetdicom._handlers.doc_handle_sop_common¶
-
-pynetdicom._handlers.doc_handle_sop_common(event: Event, *args: Sequence[Any]) Dict[UID, SOPClassCommonExtendedNegotiation] [source]¶
+pynetdicom._handlers.doc_handle_sop_common(event: Event, *args: Sequence[Any]) Dict[UID, SOPClassCommonExtendedNegotiation] [source]¶
Documentation for handlers bound to evt.EVT_SOP_COMMON
.
User implementation of this event handler is required only if
-SOP Class Common Extended Negotiation
+SOP Class Common Extended Negotiation
is to be supported by the association.
Event
evt.EVT_SOP_COMMON
@@ -186,7 +186,7 @@ pynetdicom._handlers.doc_handle_sop_commonReferences
-DICOM Standard, Part 7, Annex D.3.3.6
+DICOM Standard, Part 7, Annex D.3.3.6
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_sop_extended.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_sop_extended.html
index 10e35b506..72e48c078 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_sop_extended.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_sop_extended.html
@@ -139,10 +139,10 @@
pynetdicom._handlers.doc_handle_sop_extended¶
-
-pynetdicom._handlers.doc_handle_sop_extended(event: Event, *args: Sequence[Any]) Dict[UID, bytes] [source]¶
+pynetdicom._handlers.doc_handle_sop_extended(event: Event, *args: Sequence[Any]) Dict[UID, bytes] [source]¶
Documentation for handlers bound to evt.EVT_SOP_EXTENDED
.
User implementation of this event handler is required only if
-SOP Class Extended Negotiation
+SOP Class Extended Negotiation
is to be supported by the association. If a handler
is not implemented and bound to evt.EVT_SOP_EXTENDED
then no response
will be sent to the SOP Class Extended Negotiation request.
@@ -190,7 +190,7 @@ pynetdicom._handlers.doc_handle_sop_extendedReferences
-DICOM Standard, Part 7, Annex D.3.3.5
+DICOM Standard, Part 7, Annex D.3.3.5
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_store.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_store.html
index 31e1d21f9..c1d1da919 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_store.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_store.html
@@ -139,22 +139,22 @@
pynetdicom._handlers.doc_handle_store¶
-
-pynetdicom._handlers.doc_handle_store(event: Event, *args: Sequence[Any]) int | Dataset [source]¶
+pynetdicom._handlers.doc_handle_store(event: Event, *args: Sequence[Any]) int | Dataset [source]¶
Documentation for handlers bound to evt.EVT_C_STORE
.
User implementation of this event handler is required if one or more
services that use C-STORE are to be supported. If a handler is
not implemented and bound to evt.EVT_C_STORE
then the C-STORE request
will be responded to using a Status value of 0xC211
- Failure.
If the user is storing the dataset in the
-DICOM File Format then they are
+DICOM File Format then they are
responsible for adding the
-File Meta Information.
+File Meta Information.
Event
evt.EVT_C_STORE
Supported Service Classes
-
-
+
+
Status
- Return type:
pydicom.dataset.Dataset or int
@@ -251,12 +251,12 @@ pynetdicom._handlers.doc_handle_storeReferences
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_transport.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_transport.html
index c8cea64cd..7e527808f 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_transport.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_transport.html
@@ -131,7 +131,7 @@
pynetdicom._handlers.doc_handle_transport¶
-
-pynetdicom._handlers.doc_handle_transport(event: Event, *args: Sequence[Any]) None [source]¶
+pynetdicom._handlers.doc_handle_transport(event: Event, *args: Sequence[Any]) None [source]¶
Documentation for handlers bound to evt.EVT_CONN_OPEN
or
evt.EVT_CONN_CLOSE
.
diff --git a/dev/reference/generated/pynetdicom._handlers.doc_handle_userid.html b/dev/reference/generated/pynetdicom._handlers.doc_handle_userid.html
index 040dee005..f1b2efe02 100644
--- a/dev/reference/generated/pynetdicom._handlers.doc_handle_userid.html
+++ b/dev/reference/generated/pynetdicom._handlers.doc_handle_userid.html
@@ -139,10 +139,10 @@
pynetdicom._handlers.doc_handle_userid¶
-
-pynetdicom._handlers.doc_handle_userid(event: Event, *args: Sequence[Any]) Tuple[bool, bytes | None] [source]¶
+pynetdicom._handlers.doc_handle_userid(event: Event, *args: Sequence[Any]) Tuple[bool, bytes | None] [source]¶
Documentation for handlers bound to evt.EVT_USER_ID
.
User implementation of this handler is required if
-User Identity Negotiation
+User Identity Negotiation
is to be supported by the association. If no handler is
implemented and bound to evt.EVT_USER_ID
then the association will be accepted (provided there’s no other reason
@@ -210,7 +210,7 @@
pynetdicom._handlers.doc_handle_useridReferences
-DICOM Standard, Part 7, Annex D.3.3.7
+DICOM Standard, Part 7, Annex D.3.3.7
diff --git a/dev/reference/generated/pynetdicom.acse.ACSE.html b/dev/reference/generated/pynetdicom.acse.ACSE.html
index 9328a2391..ddaf16829 100644
--- a/dev/reference/generated/pynetdicom.acse.ACSE.html
+++ b/dev/reference/generated/pynetdicom.acse.ACSE.html
@@ -121,13 +121,13 @@
pynetdicom.acse.ACSE¶
-
-class pynetdicom.acse.ACSE(assoc: Association)[source]¶
+class pynetdicom.acse.ACSE(assoc: Association)[source]¶
The Association Control Service Element (ACSE) service provider.
The ACSE protocol handles association negotiation and establishment, and
normal and abnormal release of an association.
-
-__init__(assoc: Association) None [source]¶
+__init__(assoc: Association) None [source]¶
Create the ACSE service provider.
- Parameters:
@@ -226,7 +226,7 @@ pynetdicom.acse.ACSE
-
-is_aborted(abort_type: str = 'both') bool [source]¶
+is_aborted(abort_type: str = 'both') bool [source]¶
Return True
if an A-ABORT and/or A-P-ABORT request has been
received.
@@ -251,7 +251,7 @@ pynetdicom.acse.ACSE
-
-is_release_requested() bool [source]¶
+is_release_requested() bool [source]¶
Return True
if an A-RELEASE request has been received.
New in version 1.1.
@@ -260,14 +260,14 @@ pynetdicom.acse.ACSE
-
-negotiate_association() None [source]¶
+negotiate_association() None [source]¶
Perform an association negotiation as either the requestor or
acceptor.
-
-negotiate_release() None [source]¶
+negotiate_release() None [source]¶
Negotiate association release.
New in version 1.1.
@@ -284,7 +284,7 @@ pynetdicom.acse.ACSE
-
-send_abort(source: int) None [source]¶
+send_abort(source: int) None [source]¶
Send an A-ABORT request to the peer.
- Parameters:
@@ -303,13 +303,13 @@ pynetdicom.acse.ACSE
-
-send_accept() None [source]¶
+send_accept() None [source]¶
Send an A-ASSOCIATE (accept) to the peer.
-
-send_ap_abort(reason: int) None [source]¶
+send_ap_abort(reason: int) None [source]¶
Send an A-P-ABORT to the peer.
- Parameters:
@@ -332,7 +332,7 @@ pynetdicom.acse.ACSE
-
-send_reject(result: int, source: int, diagnostic: int) None [source]¶
+send_reject(result: int, source: int, diagnostic: int) None [source]¶
Send an A-ASSOCIATE (reject) to the peer.
- Parameters:
@@ -375,7 +375,7 @@ pynetdicom.acse.ACSE
-
-send_release(is_response: bool = False) None [source]¶
+send_release(is_response: bool = False) None [source]¶
Send an A-RELEASE (request or response) to the peer.
- Parameters:
@@ -387,7 +387,7 @@ pynetdicom.acse.ACSE
-
-send_request() None [source]¶
+send_request() None [source]¶
Send an A-ASSOCIATE (request) to the peer.
diff --git a/dev/reference/generated/pynetdicom.ae.ApplicationEntity.html b/dev/reference/generated/pynetdicom.ae.ApplicationEntity.html
index 32ef28546..e7f7cca7c 100644
--- a/dev/reference/generated/pynetdicom.ae.ApplicationEntity.html
+++ b/dev/reference/generated/pynetdicom.ae.ApplicationEntity.html
@@ -120,13 +120,13 @@
pynetdicom.ae.ApplicationEntity¶
-
-class pynetdicom.ae.ApplicationEntity(ae_title: str = 'PYNETDICOM')[source]¶
+class pynetdicom.ae.ApplicationEntity(ae_title: str = 'PYNETDICOM')[source]¶
Represents a DICOM Application Entity (AE).
An AE may be a Service Class Provider (SCP), a Service Class User (SCU)
or both.
-
-__init__(ae_title: str = 'PYNETDICOM') None [source]¶
+__init__(ae_title: str = 'PYNETDICOM') None [source]¶
Create a new Application Entity.
Changed in version 2.0: ae_title should be str
@@ -249,7 +249,7 @@ pynetdicom.ae.ApplicationEntity
-
-add_requested_context(abstract_syntax: str | UID, transfer_syntax: str | UID | Sequence[str | UID] | None = None) None [source]¶
+add_requested_context(abstract_syntax: str | UID, transfer_syntax: str | UID | Sequence[str | UID] | None = None) None [source]¶
Add a presentation context to be
proposed when requesting an association.
When an SCU sends an association request to a peer it includes a list
@@ -338,15 +338,15 @@
pynetdicom.ae.ApplicationEntityReferences
DICOM Standard, Part 8,
-Section 7.1.1.13
+Section 7.1.1.13
DICOM Standard, Part 8,
-Table 9-18
+Table 9-18
-
-add_supported_context(abstract_syntax: str | UID, transfer_syntax: str | UID | Sequence[str | UID] | None = None, scu_role: bool | None = None, scp_role: bool | None = None) None [source]¶
+add_supported_context(abstract_syntax: str | UID, transfer_syntax: str | UID | Sequence[str | UID] | None = None, scu_role: bool | None = None, scp_role: bool | None = None) None [source]¶
Add a presentation context to be
supported when accepting association requests.
When an association request is received from a peer it supplies a list
@@ -483,7 +483,7 @@
pynetdicom.ae.ApplicationEntity
-
-associate(addr: str, port: int, contexts: List[PresentationContext] | None = None, ae_title: str = 'ANY-SCP', max_pdu: int = 16382, ext_neg: List[MaximumLengthNotification | ImplementationClassUIDNotification | ImplementationVersionNameNotification | AsynchronousOperationsWindowNegotiation | SCP_SCU_RoleSelectionNegotiation | SOPClassExtendedNegotiation | UserIdentityNegotiation | SOPClassCommonExtendedNegotiation] | None = None, bind_address: Tuple[str, int] = ('', 0), tls_args: Tuple[SSLContext, str] | None = None, evt_handlers: List[Tuple[NotificationEvent | InterventionEvent, Callable] | Tuple[NotificationEvent | InterventionEvent, Callable, List[Any]]] | None = None) Association [source]¶
+associate(addr: str, port: int, contexts: List[PresentationContext] | None = None, ae_title: str = 'ANY-SCP', max_pdu: int = 16382, ext_neg: List[MaximumLengthNotification | ImplementationClassUIDNotification | ImplementationVersionNameNotification | AsynchronousOperationsWindowNegotiation | SCP_SCU_RoleSelectionNegotiation | SOPClassExtendedNegotiation | UserIdentityNegotiation | SOPClassCommonExtendedNegotiation] | None = None, bind_address: Tuple[str, int] = ('', 0), tls_args: Tuple[SSLContext, str] | None = None, evt_handlers: List[Tuple[NotificationEvent | InterventionEvent, Callable] | Tuple[NotificationEvent | InterventionEvent, Callable, List[Any]]] | None = None) Association [source]¶
Request an association with a remote AE.
An Association
thread is returned
whether or not the association is accepted and should be checked using
@@ -515,7 +515,7 @@
pynetdicom.ae.ApplicationEntityrequested_contexts
property will be requested instead.
ae_title (str, optional) – The peer’s AE title, will be used as the Called AE Title
parameter value (default 'ANY-SCP'
).
-max_pdu (int, optional) – The maximum PDV receive size
+
max_pdu (int, optional) – The maximum PDV receive size
in bytes to use when negotiating the association (default
16832
). A value of 0
means the PDV size is unlimited.
ext_neg (list of UserInformation objects, optional) –
A list containing optional extended negotiation items:
@@ -625,7 +625,7 @@ pynetdicom.ae.ApplicationEntity
-
-make_server(address: Tuple[str, int], ae_title: str | None = None, contexts: List[PresentationContext] | None = None, ssl_context: SSLContext | None = None, evt_handlers: List[Tuple[NotificationEvent | InterventionEvent, Callable] | Tuple[NotificationEvent | InterventionEvent, Callable, List[Any]]] | None = None, server_class: Type[_T] | None = None, **kwargs: Any) _T | ThreadedAssociationServer [source]¶
+make_server(address: Tuple[str, int], ae_title: str | None = None, contexts: List[PresentationContext] | None = None, ssl_context: SSLContext | None = None, evt_handlers: List[Tuple[NotificationEvent | InterventionEvent, Callable] | Tuple[NotificationEvent | InterventionEvent, Callable, List[Any]]] | None = None, server_class: Type[_T] | None = None, **kwargs: Any) _T | ThreadedAssociationServer [source]¶
Return an association server.
New in version 1.5.
@@ -694,7 +694,7 @@ pynetdicom.ae.ApplicationEntity
-
-remove_requested_context(abstract_syntax: str | UID, transfer_syntax: str | UID | Sequence[str | UID] | None = None) None [source]¶
+remove_requested_context(abstract_syntax: str | UID, transfer_syntax: str | UID | Sequence[str | UID] | None = None) None [source]¶
Remove a requested presentation context.
Depending on the supplied parameters one of the following will occur:
@@ -793,7 +793,7 @@ pynetdicom.ae.ApplicationEntity
-
-remove_supported_context(abstract_syntax: str | UID, transfer_syntax: str | UID | Sequence[str | UID] | None = None) None [source]¶
+remove_supported_context(abstract_syntax: str | UID, transfer_syntax: str | UID | Sequence[str | UID] | None = None) None [source]¶
Remove a supported presentation context.
Depending on the supplied parameters one of the following will occur:
@@ -984,7 +984,7 @@ pynetdicom.ae.ApplicationEntity
-
-shutdown() None [source]¶
+shutdown() None [source]¶
Stop any active association servers and threads.
New in version 1.2.
@@ -993,7 +993,7 @@ pynetdicom.ae.ApplicationEntity
-
-start_server(address: Tuple[str, int], block: bool = True, ssl_context: SSLContext | None = None, evt_handlers: List[Tuple[NotificationEvent | InterventionEvent, Callable] | Tuple[NotificationEvent | InterventionEvent, Callable, List[Any]]] | None = None, ae_title: str | None = None, contexts: List[PresentationContext] | None = None) ThreadedAssociationServer | None [source]¶
+start_server(address: Tuple[str, int], block: bool = True, ssl_context: SSLContext | None = None, evt_handlers: List[Tuple[NotificationEvent | InterventionEvent, Callable] | Tuple[NotificationEvent | InterventionEvent, Callable, List[Any]]] | None = None, ae_title: str | None = None, contexts: List[PresentationContext] | None = None) ThreadedAssociationServer | None [source]¶
Start the AE as an association acceptor.
New in version 1.2.
diff --git a/dev/reference/generated/pynetdicom.association.Association.html b/dev/reference/generated/pynetdicom.association.Association.html
index 3bcaea69a..9e5893c5c 100644
--- a/dev/reference/generated/pynetdicom.association.Association.html
+++ b/dev/reference/generated/pynetdicom.association.Association.html
@@ -121,7 +121,7 @@
pynetdicom.association.Association¶
-
-class pynetdicom.association.Association(ae: ApplicationEntity, mode: str)[source]¶
+class pynetdicom.association.Association(ae: ApplicationEntity, mode: str)[source]¶
Manage an Association with a peer AE.
-
@@ -236,7 +236,7 @@
pynetdicom.association.Association
-
-__init__(ae: ApplicationEntity, mode: str) None [source]¶
+__init__(ae: ApplicationEntity, mode: str) None [source]¶
Create a new Association
instance.
The association starts in State 1 (idle). Association negotiation
won’t begin until an AssociationSocket
@@ -405,7 +405,7 @@
pynetdicom.association.Association
-
-abort() None [source]¶
+abort() None [source]¶
Abort the Association
by sending an A-ABORT to the remote
AE.
@@ -431,7 +431,7 @@ pynetdicom.association.Association
-
-bind(event: NotificationEvent | InterventionEvent, handler: Callable, args: List[Any] | None = None) None [source]¶
+bind(event: NotificationEvent | InterventionEvent, handler: Callable, args: List[Any] | None = None) None [source]¶
Bind a callable handler to an event.
New in version 1.3.
@@ -459,7 +459,7 @@ pynetdicom.association.Association
-
-get_events() List[NotificationEvent | InterventionEvent] [source]¶
+get_events() List[NotificationEvent | InterventionEvent] [source]¶
Return a list
of currently bound events.
New in version 1.3.
@@ -468,7 +468,7 @@ pynetdicom.association.Association
-
-get_handlers(event: NotificationEvent | InterventionEvent) List[Tuple[Callable, List[Any] | None]] | Tuple[Callable, List[Any] | None] [source]¶
+get_handlers(event: NotificationEvent | InterventionEvent) List[Tuple[Callable, List[Any] | None]] | Tuple[Callable, List[Any] | None] [source]¶
Return the handlers bound to a specific event.
New in version 1.3.
@@ -508,7 +508,7 @@ pynetdicom.association.Association
-
-kill() None [source]¶
+kill() None [source]¶
Kill the Association
thread.
@@ -555,7 +555,7 @@ pynetdicom.association.Association
-
-release() None [source]¶
+release() None [source]¶
Initiate association release by send an A-RELEASE request.
@@ -567,7 +567,7 @@ pynetdicom.association.Association
-
-request() None [source]¶
+request() None [source]¶
Request an association with a peer.
A request can only be made once the Association
instance has
been configured for requestor mode and been assigned an
@@ -576,13 +576,13 @@
pynetdicom.association.Association
-
-run_reactor() None [source]¶
+run_reactor() None [source]¶
The main Association
reactor.
-
-send_c_cancel(msg_id: int, context_id: int | None = None, query_model: str | UID | None = None) None [source]¶
+send_c_cancel(msg_id: int, context_id: int | None = None, query_model: str | UID | None = None) None [source]¶
Send a C-CANCEL request to the peer AE.
Changed in version 2.0: Added query_model and made context_id optional
@@ -603,7 +603,7 @@ pynetdicom.association.Association
-
-send_c_echo(msg_id: int = 1) Dataset [source]¶
+send_c_echo(msg_id: int = 1) Dataset [source]¶
Send a C-ECHO request to the peer AE.
- Parameters:
@@ -617,10 +617,10 @@ pynetdicom.association.AssociationDataset
containing at least a
(0000,0900) Status element, and, depending on the returned
Status value, may optionally contain additional elements (see
-DICOM Standard, Part 7, Annex C).
-
The DICOM Standard, Part 7, Table 9.3-13 indicates that the Status
+DICOM Standard, Part 7, Annex C).
+The DICOM Standard, Part 7, Table 9.3-13 indicates that the Status
value of a C-ECHO response “shall have a value of Success”. However
-Section 9.1.5.1.4
+Section 9.1.5.1.4
indicates it may have any of the following
values:
-
-send_c_find(dataset: Dataset, query_model: str | UID, msg_id: int = 1, priority: int = 2) Iterator[Tuple[Dataset, Dataset | None]] [source]¶
+send_c_find(dataset: Dataset, query_model: str | UID, msg_id: int = 1, priority: int = 2) Iterator[Tuple[Dataset, Dataset | None]] [source]¶
Send a C-FIND request to the peer AE.
Yields (status, identifier) pairs for each response from the peer.
@@ -678,7 +678,7 @@ pynetdicom.association.Association
dataset (pydicom.dataset.Dataset) – The C-FIND request’s Identifier dataset. The exact requirements
for the Identifier dataset are Service Class specific (see the
-DICOM Standard, Part 4).
+DICOM Standard, Part 4).
query_model (pydicom.uid.UID or str) – The value to use for the C-FIND request’s (0000,0002) Affected
SOP Class UID parameter, which usually corresponds to the
Information Model that is to be used.
@@ -702,8 +702,8 @@ pynetdicom.association.AssociationDataset
containing at least a (0000,0900)
Status element, and depending on the returned value, may
optionally contain additional elements (see the DICOM Standard,
-Part 7, Section 9.1.2.1.6 and
-Annex C).
+Part 7, Section 9.1.2.1.6 and
+Annex C).
The status for the requested C-FIND operation should be one of the
following values, but as the value depends
on the peer this can’t be assumed:
@@ -771,7 +771,7 @@ pynetdicom.association.AssociationDataset
If the status
category is not ‘Pending’ this will be None
. The exact contents
of the response Identifier are Service Class specific (see the
-DICOM Standard, Part 4).
+DICOM Standard, Part 4).
- Raises:
@@ -788,26 +788,26 @@ pynetdicom.association.AssociationReferences
-DICOM Standard, Part 4, Annex C
-DICOM Standard, Part 4, Annex K
-DICOM Standard, Part 4, Annex Q
-DICOM Standard, Part 4, Annex U
-DICOM Standard, Part 4, Annex V
-DICOM Standard, Part 4, Annex X
-DICOM Standard, Part 4, Annex BB
-DICOM Standard, Part 4, Annex CC
-DICOM Standard, Part 4, Annex HH
-DICOM Standard, Part 4, Annex II
+DICOM Standard, Part 4, Annex C
+DICOM Standard, Part 4, Annex K
+DICOM Standard, Part 4, Annex Q
+DICOM Standard, Part 4, Annex U
+DICOM Standard, Part 4, Annex V
+DICOM Standard, Part 4, Annex X
+DICOM Standard, Part 4, Annex BB
+DICOM Standard, Part 4, Annex CC
+DICOM Standard, Part 4, Annex HH
+DICOM Standard, Part 4, Annex II
DICOM Standard, Part 7, Sections
-9.1.2,
-9.3.2 and
-Annex C
+9.1.2,
+9.3.2 and
+Annex C
-
-send_c_get(dataset: Dataset, query_model: str | UID, msg_id: int = 1, priority: int = 2) Iterator[Tuple[Dataset, Dataset | None]] [source]¶
+send_c_get(dataset: Dataset, query_model: str | UID, msg_id: int = 1, priority: int = 2) Iterator[Tuple[Dataset, Dataset | None]] [source]¶
Send a C-GET request to the peer AE.
Yields (status, identifier) pairs for each response from the peer.
A C-STORE handler
@@ -824,7 +824,7 @@
pynetdicom.association.Association
dataset (pydicom.dataset.Dataset) – The C-GET request’s Identifier dataset. The exact
requirements for the Identifier are Service Class specific (see
-the DICOM Standard, Part 4).
+the DICOM Standard, Part 4).
query_model (pydicom.uid.UID or str) – The value to use for the C-GET request’s (0000,0002) Affected
SOP Class UID parameter, which usually corresponds to the
Information Model that is to be used.
@@ -848,8 +848,8 @@ pynetdicom.association.AssociationDataset
containing at least a (0000,0900)
Status element, and depending on the returned value may
optionally contain additional elements (see the DICOM Standard,
-Part 7, Section 9.1.3.1.6 and
-Annex C).
+Part 7, Section 9.1.3.1.6 and
+Annex C).
The status for the requested C-GET operation should be one of the
following values, but as the value depends on the peer this
can’t be assumed:
@@ -927,24 +927,24 @@ pynetdicom.association.AssociationReferences
-DICOM Standard, Part 4, Annex C
-DICOM Standard, Part 4, Annex U
-DICOM Standard, Part 4, Annex X
-DICOM Standard, Part 4, Annex Y
-DICOM Standard, Part 4, Annex Z
-DICOM Standard, Part 4, Annex BB
-DICOM Standard, Part 4, Annex HH
-DICOM Standard, Part 4, Annex II
+DICOM Standard, Part 4, Annex C
+DICOM Standard, Part 4, Annex U
+DICOM Standard, Part 4, Annex X
+DICOM Standard, Part 4, Annex Y
+DICOM Standard, Part 4, Annex Z
+DICOM Standard, Part 4, Annex BB
+DICOM Standard, Part 4, Annex HH
+DICOM Standard, Part 4, Annex II
DICOM Standard, Part 7, Sections
-9.1.3,
-9.3.3 and
-Annex C
+9.1.3,
+9.3.3 and
+Annex C
-
-send_c_move(dataset: Dataset, move_aet: str, query_model: str | UID, msg_id: int = 1, priority: int = 2) Iterator[Tuple[Dataset, Dataset | None]] [source]¶
+send_c_move(dataset: Dataset, move_aet: str, query_model: str | UID, msg_id: int = 1, priority: int = 2) Iterator[Tuple[Dataset, Dataset | None]] [source]¶
Send a C-MOVE request to the peer AE.
Yields (status, identifier) pairs for each response from the peer.
The peer will attempt to start a new association with an Storage SCP
@@ -963,7 +963,7 @@
pynetdicom.association.Association
dataset (pydicom.dataset.Dataset) – The C-MOVE request’s Identifier dataset. The exact
requirements for the Identifier are Service Class specific (see
-the DICOM Standard, Part 4).
+the DICOM Standard, Part 4).
move_aet (str) – The value of the Move Destination parameter for the C-MOVE
request, should be the AE title of the Storage SCP for the
C-STORE sub-operations performed by the peer.
@@ -990,8 +990,8 @@ pynetdicom.association.AssociationDataset
containing at least a (0000,0900)
Status element, and depending on the returned value, may
optionally contain additional elements (see the DICOM Standard,
-Part 7, Section 9.1.4.1.7 and
-Annex C).
+Part 7, Section 9.1.4.1.7 and
+Annex C).
The status for the requested C-MOVE operation should be one of the
following values, but as the value depends
on the peer this can’t be assumed:
@@ -1064,23 +1064,23 @@ pynetdicom.association.AssociationReferences
-DICOM Standard, Part 4, Annex C
-DICOM Standard, Part 4, Annex U
-DICOM Standard, Part 4, Annex X
-DICOM Standard, Part 4, Annex Y
-DICOM Standard, Part 4, Annex BB
-DICOM Standard, Part 4, Annex HH
-DICOM Standard, Part 4, Annex II
+DICOM Standard, Part 4, Annex C
+DICOM Standard, Part 4, Annex U
+DICOM Standard, Part 4, Annex X
+DICOM Standard, Part 4, Annex Y
+DICOM Standard, Part 4, Annex BB
+DICOM Standard, Part 4, Annex HH
+DICOM Standard, Part 4, Annex II
DICOM Standard, Part 7, Sections
-9.1.4,
-9.3.4 and
-Annex C
+9.1.4,
+9.3.4 and
+Annex C
-
-send_c_store(dataset: str | Path | Dataset, msg_id: int = 1, priority: int = 2, originator_aet: str | None = None, originator_id: int | None = None) Dataset [source]¶
+send_c_store(dataset: str | Path | Dataset, msg_id: int = 1, priority: int = 2, originator_aet: str | None = None, originator_id: int | None = None) Dataset [source]¶
Send a C-STORE request to the peer AE.
Changed in version 2.0:
@@ -1123,7 +1123,7 @@ pynetdicom.association.AssociationDataset
containing at least a
(0000,0900) Status element, and, depending on the returned
value, may optionally contain additional elements (see DICOM
-Standard, Part 7, Annex C).
+Standard, Part 7, Annex C).
The status for the requested C-STORE operation should be one of the
following, but as the value depends on the peer SCP this can’t be
assumed:
@@ -1191,18 +1191,18 @@ pynetdicom.association.AssociationReferences
-DICOM Standard, Part 4, Annex B
-DICOM Standard, Part 4, Annex GG
+DICOM Standard, Part 4, Annex B
+DICOM Standard, Part 4, Annex GG
DICOM Standard, Part 7, Sections
-9.1.1,
-9.3.1 and
-Annex C
+9.1.1,
+9.3.1 and
+Annex C
-
-send_n_action(dataset: Dataset, action_type: int, class_uid: str | UID, instance_uid: str | UID, msg_id: int = 1, meta_uid: str | UID | None = None) Tuple[Dataset, Dataset | None] [source]¶
+send_n_action(dataset: Dataset, action_type: int, class_uid: str | UID, instance_uid: str | UID, msg_id: int = 1, meta_uid: str | UID | None = None) Tuple[Dataset, Dataset | None] [source]¶
Send an N-ACTION request to the peer AE.
Changed in version 1.4: Added meta_uid keyword parameter
@@ -1236,8 +1236,8 @@ pynetdicom.association.AssociationDataset
containing at least a (0000,0900)
Status element, and depending on the returned value, may
optionally contain additional elements (see the DICOM Standard,
-Part 7, Section 10.1.4.1.10 and
-Annex C).
+Part 7, Section 10.1.4.1.10 and
+Annex C).
General N-ACTION (DICOM Standard, Part 7, Section 10.1.4 and
Annex C)
@@ -1281,22 +1281,22 @@ pynetdicom.association.AssociationReferences
-DICOM Standard, Part 4, Annex H
-DICOM Standard, Part 4, Annex J
-DICOM Standard, Part 4, Annex P
-DICOM Standard, Part 4, Annex S
-DICOM Standard, Part 4, Annex CC
-DICOM Standard, Part 4, Annex DD
+DICOM Standard, Part 4, Annex H
+DICOM Standard, Part 4, Annex J
+DICOM Standard, Part 4, Annex P
+DICOM Standard, Part 4, Annex S
+DICOM Standard, Part 4, Annex CC
+DICOM Standard, Part 4, Annex DD
DICOM Standard, Part 7, Sections
-10.1.4,
-10.3.4 and
-Annex C
+10.1.4,
+10.3.4 and
+Annex C
-
-send_n_create(dataset: Dataset, class_uid: str | UID, instance_uid: str | UID | None = None, msg_id: int = 1, meta_uid: str | UID | None = None) Tuple[Dataset, Dataset | None] [source]¶
+send_n_create(dataset: Dataset, class_uid: str | UID, instance_uid: str | UID | None = None, msg_id: int = 1, meta_uid: str | UID | None = None) Tuple[Dataset, Dataset | None] [source]¶
Send an N-CREATE request to the peer AE.
Changed in version 1.4: Added meta_uid keyword parameter
@@ -1329,8 +1329,8 @@ pynetdicom.association.AssociationSection 10.1.5.1.6
-and Annex C).
+Section 10.1.5.1.6
+and Annex C).
General N-CREATE (DICOM Standard, Part 7, Section 10.1.5 and
Annex C)
@@ -1429,22 +1429,22 @@ pynetdicom.association.AssociationReferences
-DICOM Standard, Part 4, Annex F
-DICOM Standard, Part 4, Annex H
-DICOM Standard, Part 4, Annex R
-DICOM Standard, Part 4, Annex S
-DICOM Standard, Part 4, Annex CC
-DICOM Standard, Part 4, Annex DD
+DICOM Standard, Part 4, Annex F
+DICOM Standard, Part 4, Annex H
+DICOM Standard, Part 4, Annex R
+DICOM Standard, Part 4, Annex S
+DICOM Standard, Part 4, Annex CC
+DICOM Standard, Part 4, Annex DD
DICOM Standard, Part 7, Sections
-10.1.5,
-10.3.5
-and Annex C
+10.1.5,
+10.3.5
+and Annex C
-
-send_n_delete(class_uid: str | UID, instance_uid: str | UID, msg_id: int = 1, meta_uid: str | UID | None = None) Dataset [source]¶
+send_n_delete(class_uid: str | UID, instance_uid: str | UID, msg_id: int = 1, meta_uid: str | UID | None = None) Dataset [source]¶
Send an N-DELETE request to the peer AE.
Changed in version 1.4: Added meta_uid keyword parameter
@@ -1474,8 +1474,8 @@ pynetdicom.association.AssociationSection 10.1.6.1.7
-and Annex C).
+Section 10.1.6.1.7
+and Annex C).
General N-DELETE (DICOM Standard, Part 7, Section 10.1.6 and
Annex C)
@@ -1509,18 +1509,18 @@ pynetdicom.association.AssociationReferences
-
-send_n_event_report(dataset: Dataset, event_type: int, class_uid: str | UID, instance_uid: str | UID, msg_id: int = 1, meta_uid: str | UID | None = None) Tuple[Dataset, Dataset | None] [source]¶
+send_n_event_report(dataset: Dataset, event_type: int, class_uid: str | UID, instance_uid: str | UID, msg_id: int = 1, meta_uid: str | UID | None = None) Tuple[Dataset, Dataset | None] [source]¶
Send an N-EVENT-REPORT request to the peer AE.
Changed in version 1.4: Added meta_uid keyword parameter
@@ -1556,8 +1556,8 @@ pynetdicom.association.AssociationSection 10.1.1.1.8
-and Annex C).
+Section 10.1.1.1.8
+and Annex C).
General N-EVENT-REPORT (DICOM Standard, Part 7, Section 10.1.1
and Annex C)
@@ -1600,21 +1600,21 @@ pynetdicom.association.AssociationReferences
-DICOM Standard, Part 4, Annex F
-DICOM Standard, Part 4, Annex H
-DICOM Standard, Part 4, Annex J
-DICOM Standard, Part 4, Annex CC
-DICOM Standard, Part 4, Annex DD
+DICOM Standard, Part 4, Annex F
+DICOM Standard, Part 4, Annex H
+DICOM Standard, Part 4, Annex J
+DICOM Standard, Part 4, Annex CC
+DICOM Standard, Part 4, Annex DD
DICOM Standard, Part 7, Sections
-10.1.1,
-10.3.1
-and Annex C
+10.1.1,
+10.3.1
+and Annex C
-
-send_n_get(identifier_list: List[BaseTag], class_uid: str | UID, instance_uid: str | UID, msg_id: int = 1, meta_uid: str | UID | None = None) Tuple[Dataset, Dataset | None] [source]¶
+send_n_get(identifier_list: List[BaseTag], class_uid: str | UID, instance_uid: str | UID, msg_id: int = 1, meta_uid: str | UID | None = None) Tuple[Dataset, Dataset | None] [source]¶
Send an N-GET request to the peer AE.
Changed in version 1.4: Added meta_uid keyword parameter
@@ -1649,8 +1649,8 @@ pynetdicom.association.AssociationSection 10.1.2.1.9
-and Annex C).
+Section 10.1.2.1.9
+and Annex C).
General N-GET (DICOM Standard, Part 7, Section 10.1.2 and
Annex C)
@@ -1726,22 +1726,22 @@ pynetdicom.association.AssociationReferences
-DICOM Standard, Part 4, Annex F
-DICOM Standard, Part 4, Annex H
-DICOM Standard, Part 4, Annex S
-DICOM Standard, Part 4, Annex CC
-DICOM Standard, Part 4, Annex DD
-DICOM Standard, Part 4, Annex EE
+DICOM Standard, Part 4, Annex F
+DICOM Standard, Part 4, Annex H
+DICOM Standard, Part 4, Annex S
+DICOM Standard, Part 4, Annex CC
+DICOM Standard, Part 4, Annex DD
+DICOM Standard, Part 4, Annex EE
DICOM Standard, Part 7, Sections
-10.1.2,
-10.3.2
-and Annex C
+10.1.2,
+10.3.2
+and Annex C
-
-send_n_set(dataset: Dataset, class_uid: str | UID, instance_uid: str | UID, msg_id: int = 1, meta_uid: str | UID | None = None) Tuple[Dataset, Dataset | None] [source]¶
+send_n_set(dataset: Dataset, class_uid: str | UID, instance_uid: str | UID, msg_id: int = 1, meta_uid: str | UID | None = None) Tuple[Dataset, Dataset | None] [source]¶
Send an N-SET request to the peer AE.
Changed in version 1.4: Added meta_uid keyword parameter
@@ -1774,8 +1774,8 @@ pynetdicom.association.AssociationSection 10.1.3.1.9
-and Annex C).
+Section 10.1.3.1.9
+and Annex C).
General N-SET (DICOM Standard, Part 7, Section 10.1.3 and
Annex C)
@@ -1884,20 +1884,20 @@ pynetdicom.association.AssociationReferences
-DICOM Standard, Part 4, Annex F
-DICOM Standard, Part 4, Annex H
-DICOM Standard, Part 4, Annex CC
-DICOM Standard, Part 4, Annex DD
+DICOM Standard, Part 4, Annex F
+DICOM Standard, Part 4, Annex H
+DICOM Standard, Part 4, Annex CC
+DICOM Standard, Part 4, Annex DD
DICOM Standard, Part 7, Sections
-10.1.3,
-10.3.3
-and Annex C
+10.1.3,
+10.3.3
+and Annex C
-
-set_socket(socket: AssociationSocket) None [source]¶
+set_socket(socket: AssociationSocket) None [source]¶
Set the socket to use for communicating with the peer.
- Parameters:
@@ -1911,7 +1911,7 @@ pynetdicom.association.Association
-
-unbind(event: NotificationEvent | InterventionEvent, handler: Callable) None [source]¶
+unbind(event: NotificationEvent | InterventionEvent, handler: Callable) None [source]¶
Unbind a callable handler from an event.
New in version 1.3.
diff --git a/dev/reference/generated/pynetdicom.association.ServiceUser.html b/dev/reference/generated/pynetdicom.association.ServiceUser.html
index f04891e09..8d22ebfaa 100644
--- a/dev/reference/generated/pynetdicom.association.ServiceUser.html
+++ b/dev/reference/generated/pynetdicom.association.ServiceUser.html
@@ -121,7 +121,7 @@
pynetdicom.association.ServiceUser¶
-
-class pynetdicom.association.ServiceUser(assoc: Association, mode: str)[source]¶
+class pynetdicom.association.ServiceUser(assoc: Association, mode: str)[source]¶
Convenience class for the Association
service user.
An Association
object has two ServiceUser
attributes, one
representing the association requestor and the other the association
@@ -208,7 +208,7 @@
pynetdicom.association.ServiceUser
-
-__init__(assoc: Association, mode: str) None [source]¶
+__init__(assoc: Association, mode: str) None [source]¶
Create a new ServiceUser
.
- Parameters:
@@ -327,7 +327,7 @@ pynetdicom.association.ServiceUser
-
-add_negotiation_item(item: MaximumLengthNotification | ImplementationClassUIDNotification | ImplementationVersionNameNotification | AsynchronousOperationsWindowNegotiation | SCP_SCU_RoleSelectionNegotiation | SOPClassExtendedNegotiation | SOPClassCommonExtendedNegotiation | UserIdentityNegotiation) None [source]¶
+add_negotiation_item(item: MaximumLengthNotification | ImplementationClassUIDNotification | ImplementationVersionNameNotification | AsynchronousOperationsWindowNegotiation | SCP_SCU_RoleSelectionNegotiation | SOPClassExtendedNegotiation | SOPClassCommonExtendedNegotiation | UserIdentityNegotiation) None [source]¶
Add an extended negotiation item to the user information.
Items can only be added prior to starting the association negotiation.
@@ -412,7 +412,7 @@ pynetdicom.association.ServiceUser
-
-get_contexts(cx_type: str) List[PresentationContext] [source]¶
+get_contexts(cx_type: str) List[PresentationContext] [source]¶
Return a list
of
PresentationContext
items
corresponding to cx_type.
@@ -534,7 +534,7 @@ pynetdicom.association.ServiceUser
-
-remove_negotiation_item(item: MaximumLengthNotification | ImplementationClassUIDNotification | ImplementationVersionNameNotification | AsynchronousOperationsWindowNegotiation | SCP_SCU_RoleSelectionNegotiation | SOPClassExtendedNegotiation | SOPClassCommonExtendedNegotiation | UserIdentityNegotiation) None [source]¶
+remove_negotiation_item(item: MaximumLengthNotification | ImplementationClassUIDNotification | ImplementationVersionNameNotification | AsynchronousOperationsWindowNegotiation | SCP_SCU_RoleSelectionNegotiation | SOPClassExtendedNegotiation | SOPClassCommonExtendedNegotiation | UserIdentityNegotiation) None [source]¶
Remove an extended negotiation item from the user information.
Items can only be removed prior to starting the association
negotiation.
@@ -569,7 +569,7 @@ pynetdicom.association.ServiceUser
-
-reset_negotiation_items() None [source]¶
+reset_negotiation_items() None [source]¶
Remove all extended negotiation items.
Items can only be removed prior to starting the association
negotiation.
diff --git a/dev/reference/generated/pynetdicom.debug_logger.html b/dev/reference/generated/pynetdicom.debug_logger.html
index fce6fbf2e..9fdbf80ea 100644
--- a/dev/reference/generated/pynetdicom.debug_logger.html
+++ b/dev/reference/generated/pynetdicom.debug_logger.html
@@ -122,7 +122,7 @@
pynetdicom.debug_logger¶
-
-pynetdicom.debug_logger() None [source]¶
+pynetdicom.debug_logger() None [source]¶
Setup the logging for debugging.
diff --git a/dev/reference/generated/pynetdicom.dimse.DIMSEServiceProvider.html b/dev/reference/generated/pynetdicom.dimse.DIMSEServiceProvider.html
index bc36b2c05..fcd8b2f3d 100644
--- a/dev/reference/generated/pynetdicom.dimse.DIMSEServiceProvider.html
+++ b/dev/reference/generated/pynetdicom.dimse.DIMSEServiceProvider.html
@@ -123,7 +123,7 @@
pynetdicom.dimse.DIMSEServiceProvider¶
-
-class pynetdicom.dimse.DIMSEServiceProvider(assoc: Association)[source]¶
+class pynetdicom.dimse.DIMSEServiceProvider(assoc: Association)[source]¶
The DIMSE service provider.
Changed in version 1.2: Added msg_queue attribute
@@ -258,11 +258,11 @@ pynetdicom.dimse.DIMSEServiceProviderReferences
-
-__init__(assoc: Association) None [source]¶
+__init__(assoc: Association) None [source]¶
Initialise the DIMSE service provider.
Changed in version 1.3: Class initialisation now only takes assoc parameter.
@@ -334,7 +334,7 @@ pynetdicom.dimse.DIMSEServiceProvider
-
-get_msg(block: bool = False) Tuple[None, None] | Tuple[int, C_ECHO | C_FIND | C_GET | C_MOVE | C_STORE | N_ACTION | N_CREATE | N_DELETE | N_EVENT_REPORT | N_GET | N_SET] [source]¶
+get_msg(block: bool = False) Tuple[None, None] | Tuple[int, C_ECHO | C_FIND | C_GET | C_MOVE | C_STORE | N_ACTION | N_CREATE | N_DELETE | N_EVENT_REPORT | N_GET | N_SET] [source]¶
Get the next available DIMSE message.
New in version 1.2.
@@ -370,7 +370,7 @@ pynetdicom.dimse.DIMSEServiceProvider
-
-peek_msg() Tuple[None, None] | Tuple[int, C_ECHO | C_FIND | C_GET | C_MOVE | C_STORE | N_ACTION | N_CREATE | N_DELETE | N_EVENT_REPORT | N_GET | N_SET] [source]¶
+peek_msg() Tuple[None, None] | Tuple[int, C_ECHO | C_FIND | C_GET | C_MOVE | C_STORE | N_ACTION | N_CREATE | N_DELETE | N_EVENT_REPORT | N_GET | N_SET] [source]¶
Return the first message in the message queue or None
.
New in version 1.2.
@@ -389,7 +389,7 @@ pynetdicom.dimse.DIMSEServiceProvider
-
-receive_primitive(primitive: P_DATA) None [source]¶
+receive_primitive(primitive: P_DATA) None [source]¶
Process a P-DATA primitive received from the remote.
New in version 1.2.
@@ -411,7 +411,7 @@ pynetdicom.dimse.DIMSEServiceProvider
-
-send_msg(primitive: C_CANCEL | C_ECHO | C_FIND | C_GET | C_MOVE | C_STORE | N_ACTION | N_CREATE | N_DELETE | N_EVENT_REPORT | N_GET | N_SET, context_id: int) None [source]¶
+send_msg(primitive: C_CANCEL | C_ECHO | C_FIND | C_GET | C_MOVE | C_STORE | N_ACTION | N_CREATE | N_DELETE | N_EVENT_REPORT | N_GET | N_SET, context_id: int) None [source]¶
Encode and send a DIMSE-C or DIMSE-N message to the peer AE.
- Parameters:
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.C_CANCEL_RQ.html b/dev/reference/generated/pynetdicom.dimse_messages.C_CANCEL_RQ.html
index dcf591f1d..049bc319a 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.C_CANCEL_RQ.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.C_CANCEL_RQ.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.C_CANCEL_RQ¶
-
-class pynetdicom.dimse_messages.C_CANCEL_RQ[source]¶
+class pynetdicom.dimse_messages.C_CANCEL_RQ[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.C_ECHO_RQ.html b/dev/reference/generated/pynetdicom.dimse_messages.C_ECHO_RQ.html
index 226c8bbb3..b9d7f558b 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.C_ECHO_RQ.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.C_ECHO_RQ.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.C_ECHO_RQ¶
-
-class pynetdicom.dimse_messages.C_ECHO_RQ[source]¶
+class pynetdicom.dimse_messages.C_ECHO_RQ[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.C_ECHO_RSP.html b/dev/reference/generated/pynetdicom.dimse_messages.C_ECHO_RSP.html
index 67ddf49d6..8127b4623 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.C_ECHO_RSP.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.C_ECHO_RSP.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.C_ECHO_RSP¶
-
-class pynetdicom.dimse_messages.C_ECHO_RSP[source]¶
+class pynetdicom.dimse_messages.C_ECHO_RSP[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.C_FIND_RQ.html b/dev/reference/generated/pynetdicom.dimse_messages.C_FIND_RQ.html
index e75a9252b..869044215 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.C_FIND_RQ.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.C_FIND_RQ.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.C_FIND_RQ¶
-
-class pynetdicom.dimse_messages.C_FIND_RQ[source]¶
+class pynetdicom.dimse_messages.C_FIND_RQ[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.C_FIND_RSP.html b/dev/reference/generated/pynetdicom.dimse_messages.C_FIND_RSP.html
index 5eb1944e3..19431ca0e 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.C_FIND_RSP.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.C_FIND_RSP.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.C_FIND_RSP¶
-
-class pynetdicom.dimse_messages.C_FIND_RSP[source]¶
+class pynetdicom.dimse_messages.C_FIND_RSP[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.C_GET_RQ.html b/dev/reference/generated/pynetdicom.dimse_messages.C_GET_RQ.html
index cc8bb76f9..1f657a278 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.C_GET_RQ.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.C_GET_RQ.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.C_GET_RQ¶
-
-class pynetdicom.dimse_messages.C_GET_RQ[source]¶
+class pynetdicom.dimse_messages.C_GET_RQ[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.C_GET_RSP.html b/dev/reference/generated/pynetdicom.dimse_messages.C_GET_RSP.html
index 0c1786b10..d7ea21b3a 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.C_GET_RSP.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.C_GET_RSP.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.C_GET_RSP¶
-
-class pynetdicom.dimse_messages.C_GET_RSP[source]¶
+class pynetdicom.dimse_messages.C_GET_RSP[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.C_MOVE_RQ.html b/dev/reference/generated/pynetdicom.dimse_messages.C_MOVE_RQ.html
index 2288ba997..31f9bea10 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.C_MOVE_RQ.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.C_MOVE_RQ.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.C_MOVE_RQ¶
-
-class pynetdicom.dimse_messages.C_MOVE_RQ[source]¶
+class pynetdicom.dimse_messages.C_MOVE_RQ[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.C_MOVE_RSP.html b/dev/reference/generated/pynetdicom.dimse_messages.C_MOVE_RSP.html
index b978adc5a..745b20229 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.C_MOVE_RSP.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.C_MOVE_RSP.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.C_MOVE_RSP¶
-
-class pynetdicom.dimse_messages.C_MOVE_RSP[source]¶
+class pynetdicom.dimse_messages.C_MOVE_RSP[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.C_STORE_RQ.html b/dev/reference/generated/pynetdicom.dimse_messages.C_STORE_RQ.html
index 5dd859f85..562f77c8b 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.C_STORE_RQ.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.C_STORE_RQ.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.C_STORE_RQ¶
-
-class pynetdicom.dimse_messages.C_STORE_RQ[source]¶
+class pynetdicom.dimse_messages.C_STORE_RQ[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.C_STORE_RSP.html b/dev/reference/generated/pynetdicom.dimse_messages.C_STORE_RSP.html
index a101a69ab..523510044 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.C_STORE_RSP.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.C_STORE_RSP.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.C_STORE_RSP¶
-
-class pynetdicom.dimse_messages.C_STORE_RSP[source]¶
+class pynetdicom.dimse_messages.C_STORE_RSP[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.N_ACTION_RQ.html b/dev/reference/generated/pynetdicom.dimse_messages.N_ACTION_RQ.html
index 4d4bc3950..4873ad3a0 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.N_ACTION_RQ.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.N_ACTION_RQ.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.N_ACTION_RQ¶
-
-class pynetdicom.dimse_messages.N_ACTION_RQ[source]¶
+class pynetdicom.dimse_messages.N_ACTION_RQ[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.N_ACTION_RSP.html b/dev/reference/generated/pynetdicom.dimse_messages.N_ACTION_RSP.html
index d300308f7..717045452 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.N_ACTION_RSP.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.N_ACTION_RSP.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.N_ACTION_RSP¶
-
-class pynetdicom.dimse_messages.N_ACTION_RSP[source]¶
+class pynetdicom.dimse_messages.N_ACTION_RSP[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.N_CREATE_RQ.html b/dev/reference/generated/pynetdicom.dimse_messages.N_CREATE_RQ.html
index b57f8fc46..bc46c3107 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.N_CREATE_RQ.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.N_CREATE_RQ.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.N_CREATE_RQ¶
-
-class pynetdicom.dimse_messages.N_CREATE_RQ[source]¶
+class pynetdicom.dimse_messages.N_CREATE_RQ[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.N_CREATE_RSP.html b/dev/reference/generated/pynetdicom.dimse_messages.N_CREATE_RSP.html
index 25c4bce5b..aae49bd14 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.N_CREATE_RSP.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.N_CREATE_RSP.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.N_CREATE_RSP¶
-
-class pynetdicom.dimse_messages.N_CREATE_RSP[source]¶
+class pynetdicom.dimse_messages.N_CREATE_RSP[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.N_DELETE_RQ.html b/dev/reference/generated/pynetdicom.dimse_messages.N_DELETE_RQ.html
index 93c04e2aa..9e71c9c3e 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.N_DELETE_RQ.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.N_DELETE_RQ.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.N_DELETE_RQ¶
-
-class pynetdicom.dimse_messages.N_DELETE_RQ[source]¶
+class pynetdicom.dimse_messages.N_DELETE_RQ[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.N_DELETE_RSP.html b/dev/reference/generated/pynetdicom.dimse_messages.N_DELETE_RSP.html
index e5bf64436..db681e9a7 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.N_DELETE_RSP.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.N_DELETE_RSP.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.N_DELETE_RSP¶
-
-class pynetdicom.dimse_messages.N_DELETE_RSP[source]¶
+class pynetdicom.dimse_messages.N_DELETE_RSP[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.N_EVENT_REPORT_RQ.html b/dev/reference/generated/pynetdicom.dimse_messages.N_EVENT_REPORT_RQ.html
index e4d1376d2..c88c9bbff 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.N_EVENT_REPORT_RQ.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.N_EVENT_REPORT_RQ.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.N_EVENT_REPORT_RQ¶
-
-class pynetdicom.dimse_messages.N_EVENT_REPORT_RQ[source]¶
+class pynetdicom.dimse_messages.N_EVENT_REPORT_RQ[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.N_EVENT_REPORT_RSP.html b/dev/reference/generated/pynetdicom.dimse_messages.N_EVENT_REPORT_RSP.html
index 88e91b9b8..0614103d2 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.N_EVENT_REPORT_RSP.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.N_EVENT_REPORT_RSP.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.N_EVENT_REPORT_RSP¶
-
-class pynetdicom.dimse_messages.N_EVENT_REPORT_RSP[source]¶
+class pynetdicom.dimse_messages.N_EVENT_REPORT_RSP[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.N_GET_RQ.html b/dev/reference/generated/pynetdicom.dimse_messages.N_GET_RQ.html
index 57b3d6789..22854463f 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.N_GET_RQ.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.N_GET_RQ.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.N_GET_RQ¶
-
-class pynetdicom.dimse_messages.N_GET_RQ[source]¶
+class pynetdicom.dimse_messages.N_GET_RQ[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.N_GET_RSP.html b/dev/reference/generated/pynetdicom.dimse_messages.N_GET_RSP.html
index 2775f7eeb..4a20d5a43 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.N_GET_RSP.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.N_GET_RSP.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.N_GET_RSP¶
-
-class pynetdicom.dimse_messages.N_GET_RSP[source]¶
+class pynetdicom.dimse_messages.N_GET_RSP[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.N_SET_RQ.html b/dev/reference/generated/pynetdicom.dimse_messages.N_SET_RQ.html
index 99dccb963..b995ef4fd 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.N_SET_RQ.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.N_SET_RQ.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.N_SET_RQ¶
-
-class pynetdicom.dimse_messages.N_SET_RQ[source]¶
+class pynetdicom.dimse_messages.N_SET_RQ[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_messages.N_SET_RSP.html b/dev/reference/generated/pynetdicom.dimse_messages.N_SET_RSP.html
index 8e195565f..f6ebfd8ab 100644
--- a/dev/reference/generated/pynetdicom.dimse_messages.N_SET_RSP.html
+++ b/dev/reference/generated/pynetdicom.dimse_messages.N_SET_RSP.html
@@ -124,10 +124,10 @@
pynetdicom.dimse_messages.N_SET_RSP¶
-
-class pynetdicom.dimse_messages.N_SET_RSP[source]¶
+class pynetdicom.dimse_messages.N_SET_RSP[source]¶
-
diff --git a/dev/reference/generated/pynetdicom.dimse_primitives.C_CANCEL.html b/dev/reference/generated/pynetdicom.dimse_primitives.C_CANCEL.html
index c7897860a..0b3c7b00d 100644
--- a/dev/reference/generated/pynetdicom.dimse_primitives.C_CANCEL.html
+++ b/dev/reference/generated/pynetdicom.dimse_primitives.C_CANCEL.html
@@ -124,7 +124,7 @@
pynetdicom.dimse_primitives.C_CANCEL¶
-
-class pynetdicom.dimse_primitives.C_CANCEL[source]¶
+class pynetdicom.dimse_primitives.C_CANCEL[source]¶
Represents a C-CANCEL primitive.