Материал: part02

H.3 Introduction​

H.3.1 Revision History​

Table H.3.1-1. Revision History​

H.3.2 Audience,Remarks,Terms and Definitions, Basics of DICOM Communication, Abbrevi-​ ations, References​

See example text in Section A.3.​

H.3.3 Additional Remarks for This Example​

The EXAMPLE-MEDICATION-SYSTEM-GATEWAY relies on the associated, but independent, Pharmacy and Medication Adminis-​ trationRecordSystemstofulfillthemedicalapplicationfunctionsimplicitintheDICOMservicessupported.Inparticular,thesefunctions​ are part of a critical patient safety workflow. However, those patient safety functions are not specified by DICOM, and they are not​ fullydescribedbythisConformanceStatement.PleaseseetheproductspecificationsofthePharmacyandMedicationAdministration​ Record Systems for full details on the clinical decision support and records management features of those systems.​

ThisdocumentisasampleDICOMConformanceStatementcreatedforDICOMPS3.2.Itistobeusedsolelyasanexampletoillustrate​ how to create a DICOM Conformance Statement for a server supporting the DICOM Substance Administration Information Services.​ The subject of the document, EXAMPLE-MEDICATION-SYSTEM-GATEWAY, is a fictional product.​

H.4 Networking​

H.4.1 Implementation Model​

H.4.1.1 Application Data Flow​

The division of EXAMPLE-MEDICATION-SYSTEM-GATEWAY into the separate DICOM Application Entities represents their inde-​ pendent logical functionality.​

By default all of the defined Application Entities have different AE Titles. However, EXAMPLE-MEDICATION-SYSTEM-GATEWAY​ can be configured so that the PHARMACY-SCP AE and MAR-SCP AE share the same Application Entity Title.​

- Standard -​

Figure H.4.2-1. Example-Medication-System-Gateway DICOM Data Flow Diagram​

H.4.1.2 Functional Definition of AEs​

H.4.1.2.1 Functional Definition of PHARMACY-SCP Application Entity​

The PHARMACY-SCP AE handles incoming external queries for pharmacy (drug and contrast agent) product data, and also handles​ requests for approval of administration of pharmacy product. The PHARMACY-SCP AE handles queries by translating the standard​ DICOM queries to the non-standard interface of the Pharmacy Information System and the Patient Registration System.​

The PHARMACY-SCP AE waits for another application to connect at the presentation address configured for its Application Entity​ Title. PHARMACY-SCP AE will accept Associations with Presentation Contexts for SOP Classes of the DICOM Substance Adminis-​ tration Information Service Class, and Verification Service Class. It will handle query requests on these Presentation Contexts and​ respond with values corresponding to the information provided by the Pharmacy Information System.​

H.4.1.2.2 Functional Definition of MAR-SCP Application Entity​

The MAR-SCP AE receives incoming DICOM notifications of drug or contrast agent administration, and adds them to the Medication​ Administration Record System database.​

The MAR-SCP AE waits for another application to connect at the presentation address configured for its Application Entity Title. The​ MAR-SCP AE will accept Associations with Presentation Contexts for SOP Classes of the Substance Administration Logging and​ Verification SOP Classes. Any drug or contrast agent administration images notifications received on such Presentation Contexts will​ be added to the Medication Administration Record System database.​

H.4.1.3 Sequencing of Real-World Activities​

There are no sequencing constraints across the EXAMPLE-MEDICATION-SYSTEM-GATEWAY Application Entities. Each query or​ notification is handled independently.​

- Standard -​

H.4.2 AE Specifications​

H.4.2.1 PHARMACY-SCP Application Entity Specification​

H.4.2.1.1 SOP Classes​

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

Table H.4.2-1. SOP Classes for PHARMACY-SCP AE​

H.4.2.1.2 Association Policies​

H.4.2.1.2.1 General​

The PHARMACY-SCP AE will never initiate Associations; it only accepts Association Requests from external DICOM AEs. The​ PHARMACY-SCP AE will accept Associations for Verification (C-ECHO) and Query (C-FIND) requests.​

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

Table H.4.2-2. DICOM Application Context for PHARMACY-SCP AE​

ThePHARMACY-SCPAEcansupportmultiplesimultaneousAssociations.EachtimethePHARMACY-SCPAEreceivesanAssociation,​ a child process will be spawned to process the Verification or Query 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 is 10 in total.​

Table H.4.2-3. Number of Simultaneous Associations as a SCP for PHARMACY-SCP AE​

ThePHARMACY-SCPAEdoesnotsupportasynchronouscommunication(multipleoutstandingtransactionsoverasingleAssociation).​ All Association requests must be completed and acknowledged before a new operation can be initiated.​

Table H.4.2-4. Asynchronous Nature as a SCP for PHARMACY-SCP AE​

Table H.4.2-5. DICOM Implementation Class and Version for PHARMACY-SCP AE​

- Standard -​

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.1.3 Association Initiation Policy​

The PHARMACY-SCP AE does not initiate Associations.​

H.4.2.1.4 Association Acceptance Policy​

H.4.2.1.4.1 Activity - Handling Query Requests​

H.4.2.1.4.1.1 Description and Sequencing of Activity​

The PHARMACY-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 PHARMACY-SCP AE for handling queries (C-FIND-Requests) :​

1.​Peer AE opens an Association with the PHARMACY-SCP AE.​

2.​Peer AE sends a C-FIND-RQ Message​

3.​If the query is for a Substance Administration Approval, PHARMACY-SCP AE requests basic patient demographic data (e.g.,​ name, sex) from the Patient Registration System​

4.​PHARMACY-SCP AE translates the query into a request for the Pharmacy Information System (for either Product Information​ or for Substance Administration Approval), which responds with the requested data (or an indication of no matching data for the​ query).​

5.​If matching information is provided, PHARMACY-SCP AE returns a C-FIND-RSP Message to the peer AE with the matching in-​ formation.​

6.​A final C-FIND-RSP is sent indicating that the matching is complete.​

7.​Peer AE closes the Association. Note that the peer AE does not have to close the Association immediately. Further C-FIND Re-​ quests can be sent over the Association before it is closed.​

ThePHARMACY-SCPAEmayrejectAssociationattemptsasshowninthetablebelow.TheResult,SourceandReason/Diagcolumns​ 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)​

Table H.4.2-6. Association Rejection Reasons​

- Standard -​

The PHARMACY-SCP AE will close the Association under the exceptional circumstances listed in Table H.4.2-7.​

Table H.4.2-7. 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 PHARMACY-SCP AE is waiting for the next C-FIND​ A-ABORT.​

Request 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 PHARMACY-SCP AE is waiting for the next message​ A-ABORT.​

PDU but the timer expires.​

H.4.2.1.4.1.3 SOP Specific Conformance for Verification SOP Class​

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

- Standard -​