DICOM PS3.2 2016c - Conformance

H.4.2.2.4 Association Acceptance Policy
Prev | H.4.2.2 MAR-SCP Application Entity Specification | Next

##### H.4.2.2.4 Association Acceptance Policy

###### H.4.2.2.4.1 Activity - Handling Substance Administration Logging Requests

###### H.4.2.2.4.1.1 Description and Sequencing of Activity

The MAR-SCP AE accepts Associations only if they have valid Presentation Contexts. If none of the requested Presentation Contexts are accepted then the Association Request itself is rejected. It can be configured to only accept Associations with certain hosts (using TCP/IP address) and/or Application Entity Titles.

The following sequencing applies to the MAR-SCP AE for handling Substance Administration Logging Requests (N-ACTION) :

1. Peer AE opens an Association with the MAR-SCP AE.

2. Peer AE sends N-ACTION-RQ to request logging of a substance administration event.

3. If the request does not include the Patient ID, MAR-SCP AE requests the Patient ID corresponding to the Admission ID from the Patient Registration System

4. MAR-SCP AE translates the logging request into a database operation on the Medication Administration Record System database.

5. MAR-SCP AE responds with N-ACTION-RSP to indicate that it received and processed the request.

6. Peer AE closes the Association. Note that the peer AE does not have to close the Association immediately. Further N-ACTION Requests can be sent over the Association before it is closed.

The MAR-SCP AE may reject Association attempts as shown in the Table below. The Result, Source and Reason/Diag columns represent the values returned in the corresponding fields of an ASSOCIATE-RJ PDU (see Section 9.3.4 “A-ASSOCIATE-RJ PDU Structure” in PS3.8 ). The following abbreviations are used in the Source column:

1. 1 - DICOM UL service-user

2. 2 - DICOM UL service-provider (ASCE related function)

3. 3 - DICOM UL service-provider (Presentation related function)

Table H.4.2-19. Association Rejection Reasons

Result | Source | Reason/Diag | Explanation
--- | --- | --- | ---
2 - rejected-transient | c | 2 - local-limit-exceeded | The (configurable) maximum number of simultaneous Associations has been reached. An Association request with the same parameters may succeed at a later time.
2 - rejected-transient | c | 1 - temporary-congestion | No Associations can be accepted at this time due to the real-time requirements of higher priority activities (e.g., during image acquisition no Associations will be accepted) or because insufficient resources are available (e.g., memory, processes, threads). An Association request with the same parameters may succeed at a later time.
1 - rejected-permanent | a | 2 - application-context-name-not-supported | The Association request contained an unsupported Application Context Name. An association request with the same parameters will not succeed at a later time.
1 - rejected-permanent | a | 7 - called-AE-title-not-recognized | The Association request contained an unrecognized Called AE Title. An Association request with the same parameters will not succeed at a later time unless configuration changes are made. This rejection reason normally occurs when the Association initiator is incorrectly configured and attempts to address the Association acceptor using the wrong AE Title.
1 - rejected-permanent | a | 3 - calling-AE-title-not-recognized | The Association request contained an unrecognized Calling AE Title. An Association request with the same parameters will not succeed at a later time unless configuration changes are made. This rejection reason normally occurs when the Association acceptor has not been configured to recognize the AE Title of the Association initiator.
1 - rejected-permanent | b | 1 - no-reason-given | The Association request could not be parsed. An Association request with the same format will not succeed at a later time.

The MAR-SCP AE will close the Association under the exceptional circumstances listed in Table H.4.2-20.

Table H.4.2-20. PHARMACY-SCP AE Communication Failure Behavior

Exception | Behavior
--- | ---
Timeout expiry for an expected DICOM Message Request (DIMSE level timeout). I.e. The MAR-SCP AE is waiting for the next N-ACTION Request on an open Association but the timer expires. | The Association is aborted by issuing a DICOM A-ABORT. Error message is output to the Service Audit Trail.
Timeout expiry for an expected DICOM PDU or TCP/IP packet (Low-level timeout). I.e. The MAR-SCP AE is waiting for the next message PDU but the timer expires. | The Association is aborted by issuing a DICOM A-ABORT. Error message is output to the Service Audit Trail.
Association aborted by the SCU or the network layers indicate communication loss (i.e., low-level TCP/IP socket closure) | Error message is output to the Service Audit Trail.

###### H.4.2.2.4.1.2 Accepted Presentation Contexts

The MAR-SCP AE will accept Presentation Contexts as shown in Table H.4.2-21.

Table H.4.2-21. Accepted Presentation Contexts By MAR-SCP AE

Presentation Context Table
Abstract Syntax | Transfer Syntax | Role | Extended Negotiation
--- | --- | --- | ---
Name | UID | Name | UID
Verification | 1.2.840.10008.1.1 | DICOM Implicit VR Little Endian | 1.2.840.10008.1.2 | SCP | None
Substance Administration Logging | 1.2.840.10008.1.42 | DICOM Implicit VR Little Endian | 1.2.840.10008.1.2 | SCP | None
DICOM Explicit VR Little Endian | 1.2.840.10008.1.2.1

###### H.4.2.2.4.1.3 SOP Specific Conformance for Verification SOP Class

The MAR-SCP AE provides standard conformance to the Verification SOP Class as an SCP.

###### H.4.2.2.4.1.4 SOP Specific Conformance for Substance Administration Logging SOP Classes

As required by the SOP Class, one of Patient ID or Admission ID must be present in the Substance Administration Logging request. If the request does not include the Patient ID, the MAR-SCP AE requests the Patient ID corresponding to the Admission ID from the Patient Registration System.

The MAR-SCP AE SCP translates the attributes shown in Table H.4.2-22 into database fields of the Medication Administration Record System. All other provided attributes are converted to text strings and placed in the ClinicalNotes field of the database.

Table H.4.2-22. Attributes of Logging Request Imported to Mar Database

Patient ID | (0010,0020)
Product Package Identifier | (0044,0001)
Product Name | (0044,0008)
Substance Administration DateTime | (0044,0010)
Administration Route Code Sequence | (0054,0302)
Operator Identification Sequence | (0008,1072)

The MAR-SCP AE supports the N-ACTION Response Status return values and behavior shown in Table H.4.2-23.

Table H.4.2-23. MAR-SCP AE N-ACTION Response Status Return Reasons

Service Status | Further Meaning | Status Code | Reason
--- | --- | --- | ---
Success | Success | 0000 | The log entry was successfully received and stored in the Medication Administration Record System database.
Failure | Processing failure | 0110 | The AE is unable to establish a session with the Medication Administration Record System (Error ID=C003), or with the Patient Registration System (Error ID=C002). Error message is output to the Service Audit Trail.
Operator not authorized to add entry to Medication Administration Record | C10E | The AE received a user authorization rejection from the Medication Administration Record System. Error message is output to the Service Audit Trail.
Patient cannot be identified from Patient ID or Admission ID | C110 | The AE is unable to identify the Patient. Error message is output to the Service Audit Trail.
Update of Medication Administration Record failed | C111 | The Medication Administration Record System reported a database error. Error message is output to the Service Audit Trail.

Prev | Up | Next
H.4.2.2.3 Association Initiation Policy | Home | H.4.3 Network Interfaces

DICOM PS3.2 2016c - Conformance