Материал: part02

H.4.2.1.4.1.4 SOP Specific Conformance for Product Characteristics Query SOP Class​

The PHARMACY-SCP AE supports the Return Key Attributes shown in Tables H.4.2-9 and H.4.2-10. Only those attributes requested​ in the query identifier are returned. Note that queries about devices are not supported.​

Table H.4.2-9. Return Key Attributes Supported for Product Characteristics Query​

Table H.4.2-10. Product Parameter Sequence Item Concepts Supported​

Concept Name Code Sequence (0040,A043)​

(118565006, SCT, "Volume")​

(127489000, SCT, "Active Ingredient")​

Only the ASCII (DICOM Default) character set is supported by the Pharmacy Information System; Specific Character Set (0008,0005)​ is not used.​

H.4.2.1.4.1.5 SOP Specific Conformance for Substance Approval Query SOP Class​

The PHARMACY-SCP AE supports the Matching Key Attributes shown in Table H.4.2-11. It can be configured to match on Patient​ ID, or on Admission ID, or on a combination of Patient ID and Issuer of Patient ID, or on a combination of Admission ID and Issuer​ of Admission ID. As required by the SOP Class, one of Patient ID or Admission ID must be present in the query, as must Product​ PackageIdentifierandAdministrationRouteCodeSequence.Note,however,thatthePharmacyInformationSystemdoesnotsupport​ verification of administration route. Also note that queries about devices are not supported.​

Table H.4.2-11. Matching Key Attributes Supported for Substance Approval Query​

The PHARMACY-SCP AE supports the Return Key Attributes shown in Table H.4.2-12. Only those attributes requested in the query​ identifier are returned.​

- Standard -​

Page 292​ DICOM PS3.2 2020a - Conformance​

Table H.4.2-12. Return Key Attributes Supported for Substance Approval Query​

Specific Character Set (0008,0005) is returned with value ISO_IR 192 if the Patient Registration System provides non-ASCII Unicode​ characters in Patient Name.​

H.4.2.1.4.1.6 PHARMACY-SCP AE C-FIND Response Behavior​

The PHARMACY-SCP AE supports the C-FIND Response Status return values and behavior shown in Table H.4.2-13.​

Table H.4.2-13. PHARMACY-SCP AE C-FIND Response Status Return Behavior​

- Standard -​

H.4.2.2 MAR-SCP Application Entity Specification​

H.4.2.2.1 SOP Classes​

The MAR-SCP AE provides Standard Conformance to the following DICOM SOP Classes:​

Table H.4.2-14. SOP Classes for MAR-SCP AE​

H.4.2.2.2 Association Policies​

H.4.2.2.2.1 General​

The MAR-SCP AE will never initiate Associations; it only accepts Association Requests from external DICOM AEs. The MAR-SCP​ AE will accept Associations for Verification (C-ECHO) and Substance Administration Logging (N-ACTION) requests.​

The DICOM standard Application Context Name for DICOM is always accepted and proposed:​

Table H.4.2-15. DICOM Application Context for MAR-SCP AE​

The MAR-SCP AE can support multiple simultaneous Associations. Each time the MAR-SCP AE receives an Association, a child​ process will be spawned to process the Verification or Substance Administration Logging request. The maximum number of child​ processes, and thus the maximum number of simultaneous Associations that can be processed, is set by configuration. The default​ maximum number is 10 in total.​

Table H.4.2-16. Number of Simultaneous Associations as an SCP for MAR-SCP AE​

The MAR-SCP AE does not support asynchronous communication (multiple outstanding transactions over a single Association). All​ Association requests must be completed and acknowledged before a new operation can be initiated.​

- Standard -​

Page 294​ DICOM PS3.2 2020a - Conformance​

Table H.4.2-17. Asynchronous Nature as a SCP for MAR-SCP AE​

NotethatallEXAMPLE-MEDICATION-SYSTEM-GATEWAYAEsusethesameImplementationClassUIDandImplementationVersion​ Name. This Version Name is updated with each new release of the product software, as the different AE versions are never released​ independently.​

H.4.2.2.3 Association Initiation Policy​

The MAR-SCP AE does not initiate Associations.​

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-SCPAEtranslatestheloggingrequestintoadatabaseoperationontheMedicationAdministrationRecordSystemdatabase.​

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:​

a.​1 - DICOM UL service-user​

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

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

- Standard -​

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​ The Association is aborted by issuing a DICOM​ timeout). I.e. The MAR-SCP AE is waiting for the next N-ACTION Request​A-ABORT.​

on an open Association but the timer expires.​

Error message is output to the Service Audit Trail.​

Timeout expiry for an expected DICOM PDU or TCP/IP packet (Low-level​The Association is aborted by issuing a DICOM​ timeout). I.e. The MAR-SCP AE is waiting for the next message PDU but​A-ABORT.​

the timer expires.​

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.​

- Standard -​