1. Introduction

PacsOne is a DICOM 3.0 compliant PACS (Picture Archive and Communication System) application that combines the following components in one machine or one box:

• A DICOM server.
• A PACS server which uses open source MySQL database.
• A Web server which uses open source Apache 2.0 HTTP server and PHP (recursive acronym for "PHP: Hypertext Preprocessor") scripts.
• A optional HL7 interface to receive and send HL7 messages via Lower Level Transport Protocol (LLTP)

The benefits of PacsOne over the traditional PACS servers are:

• It is free (Basic Edition) or low cost (Premium Edition) since it uses open source MySQL database and Apache web servers.
• It makes the life of a PACS administrator a lot easier since there is only ONE instead of multiple servers or boxes to maintain.
• Users can freely choose their favorite server platform or hardware, whether it is a PC, workstation, fully-fledged server with RAID disk arrays or even a laptop, to install and run PacsOne server software.
• Users can freely choose their favorite operating system software, whether it is Linux, Mac OS X, Windows NT, Windows 2000, Windows XP, Windows 2003 Server or Vista.
• Archiving of the PACS database is just as simple as backing up files on a regular server, which makes PacsOne fit seamlessly into the rest of IT infrastructure of the entire organization.  A PACS administrator has the freedom to choose their favorite backup solutions, software and/or archive media.

This implementation of PacsOne server is designed to provide the following features:

• The application serves as a short-term archive for images. It accepts images from external sources and stores them for later retrieval.
• PacsOne uses DICOM as the interface to external conforming clients. The DICOM server accepts DICOM association requests for the purpose of storing images and for image query and retrieve. PacsOne server will initiate DICOM association requests for the purpose of sending images to an external server, querying remote application entities, or printing images to remote Dicom printers. PacsOne server does not respond to any other type of network communication.
• PacsOne uses Apache Web server as the interface for viewing and managing the PACS database, and for reviewing images on-line through a web browser.
• The Premium Edition of PacsOne Server supports Automatic Image Routing Table, where users can define routing entries based on the following criteria:
  

  Field	Description
  Source Application Entity (AE) Title	Images received from the matching Source AE Title will be routed to the destination AE automatically based on the specified Schedule below.
  Key Attribute Tag	Currently, the Patient ID (0010,0020), Referring Physician's Name (0008,0090) and Protocol Name (0018,1030) key tags are supported. Users can define a matching pattern string with wild-card characters including '*' and '?', so that if the received image attribute matches with the specified pattern string, PacsOne Server Premium Edition will automatically route the received image to the destination AE based on the specified Schedule below.
  Destination AE Title	This is the destination AE where the received images will be routed.
  Schedule	Route Immediately (as soon as received), a [From, To] window, or based on a fixed 24-hour clock.
  Auto Purge	Whether or not to purge received images after they have been routed successfully to the destination AE(s).

  
  

• The Premium Edition of PacsOne Server supports querying remote DICOM Modality Worklist (DMWL) SCP applications and displaying the query results through the web user interface.
• The Premium Edition of PacsOne Server supports receiving event notifications sent by remote Detached Study Management SCP applications, as well as querying remote Detached Study Management SCP applications for study related information.
• The Premium Edition of PacsOne Server supports storage of DICOM V3.0 Strucutre Reports (SR), as well as presentation of the Structure Reports through the web user interface.
• The Premium Edition of PacsOne Server supports DICOM Media Storage Services and File Format (PS 3.10) as a File Set Creator (FSC) and File Set Reader (FSR) of the General Purpose CD-R and DVD Interchange Profiles. From the PacsOne web user interface, users can export selected patients/studies in the PacsOne database to a local directory using DICOM standard directory formats (DICOMDIR), which can later be archived into CD-R/RW or DVD-R/RW/RAM for media interchange. Uses can also import external patients/studies from a DICOM Media Storage Service compliant directory or CD/DVD media into the PacsOne database.
• The Premium Edition of PacsOne Server Supports the Automatic Purging Storage Directories feature by allowing the user to define a set of Low-Water and High-Water Marks in terms of disk usage percentage for PacsOne Server archive directories. If Enabled by the user and the disk usage percentage of the archive directories has dropped below the user-defined Low-Water Mark, PacsOne Server Premium Edition will start to purge older studies stored in the archive directories, by the order of the date the studies were received, until the disk usage percentage has risen above the user-defined High-Water Mark. User can also specify optionally a Destination Folder to move aged studies instead of permanently delete the aged studies.
• The Premium Edition of PacsOne Server supports printing both color and grayscale images to Dicom compliant remote printers from the PacsOne Server web user interface.
• The Premium Edition of PacsOne Server supports synchronizing its local database with remote studies stored on external application entities based on user-specified schedule (s). Users can also select whether to synchronize all remote studies or only those recent studies received in the past N days.

2. Implementation Model

PacsOne Server provides for storage, query/retrieval and management of Dicom formatted images and reports. It runs on the following platforms:

• Windows NT
• Windows 2000
• Windows XP
• Windows 2003 Server
• Windows Vista
• Linux (Premium Edition)
• Mac OS X (Premium Edition)

as a background process (service) that accepts association requests from external applications. PacsOne server employs a configurable thread pool to service requesting applications. PacsOne server will initiate a DICOM C-STORE association in response to either a C-MOVE request from an external application, user forwarding requests entered from the web user interface, or matches with automatic image routing table entries. PacsOne server is started automatically when Windows starts up, users which have Windows Administrator's privilege can stop and re-start PacsOne server process manually from the "Services" tablet of the Windows Control Panel.

The following parameters of the PacsOne server are configurable by executing the 'SETUP.EXE' program during Installation, or by modifying the Windows Registry values manually under the following key:

HKEY_LOCAL_MACHINE\\SOFTWARE\\RainbowFish Software\\PacsOne\\

After modifying any of the above Registry settings, the PacsOne server needs to be restarted in order for the changes to take effect.

2.1 Application Data Flow Diagram

Figure 1 shows the relationship of PacsOne server to external applications. As noted above, PacsOne server does not initiate any action except in response to requests which are received either via DICOM associations or from the web user interface.

FIGURE 1. PacsOne Server Implementation Model

2.2 Functional Definition of Application Entities

PacsOne server waits for another application to connect to the TCP/IP port number specified when the application is initiated. When a DICOM association request is received, PacsOne server uses a MySQL database table and the following logic to verify the incoming request:

• PacsOne server is permissive when verifying the Called Application Entity Title of the incoming association request. It does not reject an incoming association request based on the specified Called Application Entity Title.
• PaceOne server queries the 'applentity' table to verify if there is a row whose 'title' field matches (case insensitive) with the Calling Application Entity Title of the incoming request.
• If there is a match, PacsOne server then verifies that the matching application entity has access to the MySQL database, by querying the 'allowaccess' field of the 'applentity' table.
• If 'allowaccess' field is Enabled (non-zero), PacsOne server then proceeds to service the incoming association request.
• If 'allowaccess' field is Disabled ('0') or no matching application entity is found for the Calling Application Entity Title, PacsOne server will reject the incoming association request from this application entity.

2.3 Sequencing of Real-World Activities

See the Association Initiation and Acceptance Policy sections below on real-world activities for all SOP classes supported by PacsOne Server.

3. AE Specifications

PacsOne server is started automatically when Windows starts up, or user can manually stop and re-start PacsOne server from the 'Services' tablet of the Windows Control Panel.  PacsOne server uses a configurable thread pool to service all DICOM 3.0 protocol I/O processing.  The number of threads in the thread pool has a default value of 2, and can be configured by modifying the following Windows Registry:

HKEY_LOCAL_MACHINE\\SOFTWARE\\RainbowFish Software\\PacsOne\\ThreadPoolSize

NOTE: Setting a large value for the number of threads in the thread pool does not necessarily increase the overall performance of PacsOne server.  It is recommended to set the size of thread pool to be twice the number of available processors or CPU's in the system. PacsOne server needs to be re-started if the size of thread pool is modified.

3.1 AE PacsOne Server - Specification

PacsOne server provides Standard Conformance to the following DICOM 3.0 SOP Classes as a SCU:

PacsOne server provides Standard Conformance to the following DICOM 3.0 SOP Classes as a SCP:

3.2 Association Establishment Policies

3.2.1 General

The DICOM Application Context Name (ACN) proposed by PacsOne Server is fixed: "1.2.840.10008.3.1.1". The maximum PDU size which can be transmitted by PacsOne server is fixed at 32 Kbytes.  The maximum PDU size which can be received by PacsOne server is up to 32 Kbytes.

3.2.2 Number of Associations

The number of simultaneous associations which can be accepted by PacsOne server are limited only by the kernel parameters of underlying TCP/IP implementation and resource utilization of the computer where PacsOne server is installed. PacsOne server utilizes a thread pool to service each association request that it receives. Therefore, PacsOne server can have multiple simultaneous connections, and there is no inherent limitation on the total number of simultaneous associations which a PacsOne server can maintain.

3.2.3 Asynchronous Nature

PacsOne server does not support asynchronous operations and will not perform asynchronous window negotiation.

3.2.4 Implementation Identifying Information

PacsOne server provides the following implementation class UID:

1.2.826.0.1.3680043.2.737

PacsOne server provides the following implementation version name:

PACSONE01AUG03

3.3 Association Initiation Policy

PacsOne server will attempt to initiate associations in response to user requests from the web user interface to verify DICOM connection status (C-ECHO) to remote Application Entity (AE).

PacsOne server will attempt to initiate associations in response to user requests from the web user interface to query and retrieve (C-FIND) remote Query/Retrieve SCP applications.

PacsOne server will attempt to initiate associations in response to C-MOVE requests from other Application Entities. PacsOne server will only initiate associations in response to valid C-MOVE requests for images that are stored in the MySQL database.

PacsOne server will attempt to initiate associations in response to user selected forwarding requests from the web user interface, where users can select one or more patient(s), study(s) or series to forward (C-STORE) to a remote destination application entity (AE).

The Premium Edition of PacsOne server can also initiate associations to remote destination AE(s) automatically based on the automatic routing table. Users can define entries in the automatic routing table which consist of a source AE title, destination AE title and a schedule, so that the images received from the specified source AE will be automatically forwarded (C-STORE) to one of more destination AE(s) based on the specified schedule, either as soon as received (Immediately) or on a particular 24-hour clock interval., e.g., 7:00 p.m.

PacsOne Server Premium Edition can initiate Modality Worklist - FIND requests to remote Modality Worklist SCP applications, either in response to unsolicited Study Scheduled N-EVENT-REPORT notifications, or by querying the Worklist SCP regularly based on a configurable polling interval. Users can also initiate Modality Worklist - FIND request by clicking on the Get Worklist link from the web user interface.

3.3.1 Real-World Activity - Verification

3.3.1.1 Associated Real-World Activity - Verification

From the PacsOne Server web user interface, users can select the 'Application Entity' Page to display a list of defined application entities (AE). If the TCP port number for an AE is defined, a Ping link will be displayed in the 'Verify Connection' column. Clicking on the Ping link will initiate a C-ECHO request to the TCP port number of the corresponding AE. A confirmation message will be displayed if the C-ECHO request is successfully acknowledged by the remote AE, otherwise a timeout error or any error response from the remote AE will be displayed.

3.3.1.2 Proposed Presentation Contexts - Verification

Table 4 below shows the presentation contexts that are proposed by PacsOne server for verification operations..

3.3.1.3 SOP Specific Conformance Statement - Verification

3.3.2 Real-World Activity - Query/Retrieve

3.3.2.1 Associated Real-World Activity - Query/Retrieve

From the PacsOne Server web user interface, users can select the 'Application Entity' Page to display a list of defined application entities (AE). If the TCP port number for an AE is defined, a Query/Retrieve link will be displayed in the 'Remote Exams' column. Clicking on the Query/Retrieve link will initiate a C-FIND request to the TCP port number of the corresponding AE. Any matching patients and/or studies returned by the remote AE will be displayed, otherwise a timeout error or any error response from the remote AE will be displayed.

3.3.2.2 Proposed Presentation Contexts - Query/Retrieve

Table 5 shows the presentation contexts used by PacsOne server when initiating C-FIND requests to remote Query/Retrieve SCP applications.

3.3.2.3 SOP Specific Conformance Statement - Query/Retrieve

Table 6 below contains the key matching methods supported by PacsOne Server when initiating C-FIND requests to remote Query/Retrieve SCP applications:

Table 7 below indicates which keys are used by the PacsOne server for the Patient Root information model when initiating C-FIND requests to remote Query/Retrieve SCP applications.

3.3.3 Real-World Activity - Move Request From An External Node

3.3.3.1 Associated Real-World Activity - Move Request

The associated Real-World activity is a C-MOVE request received from an external application. If an application successfully establishes an association with the PacsOne server and makes a valid C-MOVE request that identifies one or more images known by the PacsOne server, the PacsOne server will query the 'applentity' MySQL database table to see if a matching entry can be found for the specified destination application entity title.  If a match is found, the PacsOne server will initiate an association with the destination application entity specified in the incoming C-MOVE request.

3.3.3.2 Proposed Presentation Contexts - Move Request

In response to a C-MOVE request, PacsOne server builds a complete list of images to be moved. The list includes the SOP class of each image to be moved. PacsOne server extracts the unique SOP classes from the image lists and proposes a set of presentation contexts that includes one presentation context for each unique SOP class identified in the image list. Thus, the association request may have a single presentation context or multiple presentation contexts. Each presentation context contains the abstract syntax that identifies one image class as found in the image list.

3.3.3.3 Proposed Transfer Syntaxes - Move Request

PacsOne Server Basic Edition only supports Implicit VR Little Endian Transfer Syntax. Some images may have been stored by the PacsOne server with private elements whose encoding scheme is unknown by the PacsOne server. These elements will be transmitted by PacsOne server exactly as they were received (in Implicit VR Little Endian Transfer Syntax), so they should be unaltered upon transmission.

PacsOne Server Premium Edition supports the following additional transfer syntaxes:

When sending images to a remote AE, PacsOne Server will propose the same transfer syntax in which the stored SOP instance is encoded. If the encoding transfer syntax is Explicit VR Little-Endian transfer syntax (UID 1.2.840.10008.1.2.1), PacsOne Server will also propose the default Implicit VR Little-Endian transfer syntax (UID 1.2.840.10008.1.2), so that when sending images to applications that do not support the Explicit VR Little-Endian transfer syntax (for example, eFilm), PacsOne Server Premium Edition will translate from the encoding Explicit VR Little-Endian to the Implicit VR Little-Endian transfer syntax.

3.3.3.4 SOP Specific Conformance Statement - Move Request

All C-STORE operations are in the context of a C-MOVE request from an external application.  PacsOne server sends one C-MOVE response message for each attempted C-STORE operation.  PacsOne server does not attempt any extended negotiation.  PacsOne server does not delete any elements from the files it transfers. Therefore the set of optional elements depends entirely on the contents of the files which were originally stored on the PacsOne server.

In the event that PacsOne server receives an unsuccessful C-STORE response, PacsOne server will continue sending the remaining images in the requested set.

3.3.4 Real-World Activity - User Forwarding

3.3.4.1 Associated Real-World Activity - User Forwarding

From the PacsOne web user interface, users can select one or more patient(s), study(s) or series while browsing through the list, if the current user has 'Forward' privilege (Premium Edition) or 'Modify' privilege (Basic Edition) enabled, there will be a Forward button displayed below the listed patient, study or series list. Users can click on the Forward button and then select a destination AE title from a drop-down list of application entities currently defined in the 'applentity' table.

3.3.4.2 Proposed Presentation Contexts - User Forwarding

Same as Section 3.3.3.2.

3.3.4.3 Proposed Transfer Syntaxes - User Forwarding

Same as Section 3.3.3.3.

3.3.4.4 SOP Specific Conformance Statement - User Forwarding

Same as Section 3.3.3.4.

3.3.5 Real-World Activity - Automatic Routing (Premium Edition only)

3.3.5.1 Associated Real-World Activity - Automatic Routing

PacsOne Server Premium Edition supports automatic image routing based on entries defined in the Automatic Routing table. When an image is received by PacsOne Server, it will query the Automatic Routing table to see if there is an entry matches with the source application entity (AE) title. If a match is found, then the received image will be forwarded to the destination AE title specified for the matching source AE title, based on the schedule specified for the matching entry. If there are multiple matches (multiple destination AEs defined for the same source AE), then the received image will be forwarded to multiple destination AEs based on the corresponding schedule.

Users can add, delete and modify entries in the Automatic Routing table from the PacsOne Server web user interface, given that the logged-in user has the required 'Modify' privilege enabled.

3.3.5.2 Proposed Presentation Contexts - Automatic Routing

Same as Section 3.3.3.2.

3.3.5.3 Proposed Transfer Syntaxes - Automatic Routing

Same as Section 3.3.3.3.

3.3.5.4 SOP Specific Conformance Statement - Automatic Routing

Same as Section 3.3.3.4.

3.3.6 Real-World Activity - Modality Worklist Management (Premium Edition only)

3.3.6.1 Associated Real-World Activity - Modality Worklist Management

From the PacsOne Server web user interface, users can select the 'Application Entity' Page to display a list of defined application entities (AE). If the TCP port number for an AE is defined and the remote AE has been defined as Modality Worklist SCP ('worklistScp' column set to 'True' in the 'applentity' table), a Get Worklist link will be displayed in the 'Modality Worklist' column. Clicking on the Get Worklist link will initiate a Modality Worklist - FIND request to the TCP port number of the corresponding AE. Any matching result returned by the remote Modality Worklist SCP will be displayed, otherwise a timeout error or any error response from the remote AE will be displayed.

PacsOne Server Premium Edition can also receive unsolicited Study-Scheduled N-EVENT-REPORT notifications. PacsOne Server will then send Modality Worklist - FIND commands to query all configured Modality Worklist SCP application entities for the corresponding study.

PacsOne Server Premium Edition also polls any configured Modality Worklist SCP application entities to update the Worklist table on a regular basis. The default polling interval is 10 minutes, which can be changed by modifying the following Windows Registry value:

HKEY_LOCAL_MACHINE\\SOFTWARE\\RainbowFish Software\\PacsOne\\{AETITLE}\\WorklistPollInterval\\

NOTE: Change the polling interval value to zero(0) will disable automatic polling of Modality Worklist SCP applications.

3.3.6.2 Proposed Presentation Contexts - Modality Worklist Management

Table 10 below shows the presentation contexts that are proposed by PacsOne server for Modality Worklist - FIND operations..

3.3.6.3 SOP Specific Conformance Statement - Modality Worklist Management

Table 11 below contains the key matching methods supported by PacsOne Server when initiating Modality Worklist-FIND requests to remote Worklist SCP applications:

Table 12 below indicates which keys are used by the PacsOne Server for the Modality Worklist - FIND requests to remote Modality Worklist SCP applications.

3.3.7 Real-World Activity - Printing (Premium Edition only)

3.3.7.1 Associated Real-World Activity - Printing

After logging into the PacsOne Server web user interface, if the 'Print' privilege has been enabled, the current user can select a list of patients, studies, series or images, and click on the Print button.

The user can then select the destination remote printer, make any appropriate changes to the print parameters, then click on the Print button to send the selected patients, studies, series or images to the printer.

3.3.7.2 Proposed Presentation Contexts - Printing

3.3.7.3 Proposed Transfer Syntaxes - Printing

See Table 13 above.

3.3.7.4 SOP Specific Conformance Statement - Printing

PacsOne Server supports the following required print SOP classes for the Basic Grayscale/Color Management Meta classes:

PacsOne Server supports the following optional print SOP classes for the Basic Grayscale/Color Management Meta classes:

3.3.7.4.1 Conformance for Basic Film Session SOP Class

PacsOne Server supports the following attributes for N-CREATE command of the Basic Film Session SOP class:

PacsOne Server also uses N-DELETE to delete the created Basic Film Sessio SOP instance returned by the remote Print SCP.

3.3.7.4.2 Conformance for SOP Class Basic Film Box

PacsOne Server supports the following attributes for N-CREATE command of the Basic Film Box SOP class:

PacsOne Server also uses N-ACTION to print a complete Basic Film Box SOP instance and N-DELETE to delete the SOP instance after printing is complete.

3.3.7.4.3 Conformance for SOP Class Basic Grayscale Image Box

PacsOne Server supports the following attributes for N-SET command of the Basic Grayscale Image Box SOP class:

3.3.7.4.4 Conformance for SOP Class Printer

PacsOne Server supports the following attributes for N-GET command of the Printer Box SOP class:

3.3.7.4.5 Conformance for Basic Annotation Box SOP Class

PacsOne Server supports the following attributes for N-GET command of the Basic Annotation Box SOP Class:

3.3.8 Real-World Activity - Remote Synchronization (Premium Edition only)

3.3.8.1 Associated Real-World Activity - Remote Synchronization

PacsOne Server Premium Edition supports synchronizing its local database with remote studies stored on external application entities, based on user-specified synchronization schedules for the remote AE.

When adding or modifying an application entity, if the remote AE supports Dicom Query/Retrieve functions as a SCP, i.e., the 'Query/Retrieve SCP' checkbox is selected, users can select whether to enable or disable remote-synchronization for this remote AE, and whether to synchronize with all remote studies or only those recent studies received within the last N days on the remote AE.

Users can add, delete and modify synchronization schedules (up to 24 per remote AE) from the PacsOne Server web user interface, provided that the logged-in user has the required 'Modify' privilege enabled.

3.3.8.2 Proposed Presentation Contexts - Remote Synchronization

Same as Section 3.3.2.2.

3.3.8.3 Proposed Transfer Syntaxes - Remote Synchronization

Same as Section 3.3.2.2.

3.3.8.4 SOP Specific Conformance Statement - Remote Synchronization

Same as Section 3.3.2.3.

3.3.9 Real World Activity - Detached Study Management (Premium Edition only)

PacsOne server accepts unsolicited N-EVENT-REPORT notifications sent from Detached Study Management SCP application entities. PacsOne Server will then issue N-GET request back to the remote SCP to get more information for the corresponding study.

Additionally, upon receipt of the Study Scheduled event notification sent from the Detached Study Management SCP, PacsOne Server will initiate a Modality Worklist - FIND request to configured Modality Worklist SCP application entity(s) to query about the corresponding study information contained in the event report.

3.3.9.1 Associated Real World Activity - Detached Study Management

When PacsOne Server receives any Detached Study Management N-EVENT-REPORT notifications sent from a Detached Study Management SCP AE, it will first validate the association request by checking the remote AE title against the internal 'applentity' table. If access is Enabled in the 'applentity' table, the association request will be accepted and the event notification will be processed. Otherwise, the association request will be rejected by PacsOne Server and this event notification will not be processed.

3.3.9.2 Presentation Context Table - Detached Study Management

Table 21 shows the presentation contexts that may be accepted by PacsOne server for Detached Study Management N-EVENT-REPORT notifications.

3.3.9.3 SOP Specific Conformance for SOP Class - Detached Study Management

PacsOne Server supports the following attributes in the N-EVENT-REPORT-RQ notification sent from a Detached Study Management SCP application entity:

PacsOne Server returns one of the following status codes in the N-EVENT-REPORT-RSP sent back to the Detached Study Management SCP:

3.3.9.4 Presentation Context Acceptance Criterion - Detached Study Management

PacsOne server will accept any number of Detached Study Management SOP classes that are listed in Table 21 above, provided that the requesting application is allowed access to the PacsOne server (via the 'applentity' MySQL database table). The PacsOne server defines no limit on the number of presentation contexts accepted. In the event that the PacsOne server runs out of resources when trying to accept multiple presentation contexts, PacsOne server will reject the association request.

PacsOne server does not check for duplicate presentation contexts and will accept duplicate presentation contexts.

3.3.9.5 Transfer Syntax Selection Policies - Detached Study Management

PacsOne Server only supports the Implicit VR Little Endian transfer syntax when accepting Detached Study Management N-EVENT-REPORT requests. Any proposed presentation context which includes the Implicit VR Little Endian transfer syntax will be accepted with the Implicit VR Little Endian transfer syntax. Any proposed presentation context that does not include the Implicit VR Little Endian transfer syntax will be rejected.

3.4 Association Acceptance Policy

PacsOne server accepts associations for the purpose of storing images in its MySQL database or for the purpose of performing query/retrieve operations on the images that have been previously stored.

PacsOne server will only accept association requests from applications that have been defined during configuration.  In addition, the PacsOne server will only store images sent by application entities that have been enabled in the 'applentity' MySQL database table.

3.4.1 Real World Activity - Verification

PacsOne server accepts associations from applications that wish to perform a verification (C-ECHO) operation on the PacsOne server.

3.4.1.1 Associated Real World Activity - Verification

The real-world activity associated with the C-ECHO request is that an external application wishes to verify network or server operation without initiating any actual work.

3.4.1.2 Presentation Context Table - Verification

Table 24 shows the presentation contexts that may be accepted by PacsOne server for verification operations..

3.4.1.3 SOP Specific Conformance for SOP Class - Verification

3.4.1.4 Presentation Context Acceptance Criterion - Verification

PacsOne server will accept any number of verification SOP classes that are listed in Table 3 above, provided that the requesting application is allowed access to the PacsOne server (via the 'applentity' MySQL database table). The PacsOne server defines no limit on the number of presentation contexts accepted. In the event that the PacsOne server runs out of resources when trying to accept multiple presentation contexts, PacsOne server will reject the association request.

PacsOne server does not check for duplicate presentation contexts and will accept duplicate presentation contexts.

3.4.1.5 Transfer Syntax Selection Policies - Verification

PacsOne Server only supports the Implicit VR Little Endian transfer syntax when accepting verification requests. Any proposed presentation context which includes the Implicit VR Little Endian transfer syntax will be accepted with the Implicit VR Little Endian transfer syntax. Any proposed presentation context that does not include the Implicit VR Little Endian transfer syntax will be rejected.

3.4.2 Real-Word Activity - Storage

PacsOne server accepts associations from applications that wish to store images using the C-STORE command.

3.4.2.1 Associated Real-World Activity - Storage

The associated Real-World activity associated with the C-STORE operation is the storage of the images on the disk of the system upon which the PacsOne server is running. Images are stored by writing the data set of the C-STORE command directly to disk, either with no further header or interpretation ("Native" format), or with the standard file header described in the DICOM 3.0 Part 10 document (DICOM Part 10 format).  The above storage formats are configurable when PacsOne server is installed by running the 'SETUP.EXE' program, they can also be modified later by changing the following Windows Registry key value:

HKEY_LOCAL_MACHINE\\SOFTWARE\\RainbowFish Software\\PacsOne\\StorageFormat\\

to either "DicomPart10" or "Native" string values (case insensitive).

After an image is stored to disk, the PacsOne server updates the MySQL database with patient, study, series and image information; this MySQL database is used by the PacsOne server for query/retrieve operations, it is also used by the Apache web server to display patient, study, series, and image information, display stored images through a web browser, and maintain patient/study/series/ image tables for authorized users.

PacsOne server will issue a failure status if it is unable to store the image on disk, if the image does not conform to the IOD of the SOP class under which it was transmitted, or if the PacsOne server is not able to successfully update its MySQL database.

3.4.2.2 Presentation Context Table - Storage

The following Presentation Contexts shown in Table 25 are acceptable to the PacsOne server when receiving images.

3.4.2.3 SOP Specific Conformance for SOP Class - Storage

The PacsOne server implements Level 2 (Full) conformance for the Storage SOP Class.  The raw image files themselves are not modified.

In the event that an image is successfully stored by PacsOne server, it may be accessed by requesting associations with the PacsOne server and performing query/retrieve operations.  PacsOne server can also display stored images to web browser clients through the Apache web server interface.

PacsOne server stores images for an indefinite period.  The stored images, as well as stored patient, study, series and image database records can be deleted from the Apache web server interface by users authorized with UPDATE privilege to the MySQL database.

PacsOne server returns the following status codes in response to a C-STORE request:

In the case of an error of an error storing an image, there is no documented method for recovery.  Trouble-shooting information can be retrieved from the PacsOne server log file.  The directory path for PacsOne server log files is stored in Windows Registry under:

HKEY_LOCAL_MACHINE\\SOFTWARE\\RainbowFish Software\\PacsOne\\LogFile

3.4.2.4 Presentation Context Acceptance Criterion - Storage

PacsOne server will accept any number of storage SOP classes that are listed in Table 25 above, provided that the requesting application is known to the PacsOne server and has been enabled to store images on the MySQL database (via the 'applentity' MySQL database table).

PacsOne server defines no limit on the number of presentation contexts accepted. In the event that PacsOne server runs out of resources when trying to accept multiple presentation contexts, the PacsOne server will reject the association request.

PacsOne server does not check for duplicate presentation contexts and will accept duplicate presentation contexts in the association request.

3.4.2.5 Transfer Syntax Selection Policies - Storage

PacsOne Server Basic Edition only supports the Implicit VR Little Endian transfer syntax. Any proposed presentation context which includes the Implicit VR Little Endian transfer syntax will be accepted with the Implicit VR Little Endian transfer syntax. Any proposed presentation context that does not include the Implicit VR Little Endian transfer syntax will be rejected.

PacsOne Server Premium Edition supports the following additional transfer syntaxes:

When PacsOne Server Premium Edition receives association requests which contain multiple presentation contexts with different transfer syntaxes, PacsOne Server Premium Edition will accept those presentation contexts with supported transfer syntaxes listed above, and reject any presentation context with un-supported transfer syntax. If multiple transfer syntaxes are proposed in a presentation context by the remote C-STORE SCU, and PacsOne Server Premium Edition supports one of more of them, then the first transfer syntax on the list presented will be selected. Users can also define a preferred transfer syntax by defining a named Registry value below:

HKEY_LOCAL_MACHINE\\SOFTWARE\\RainbowFish Software\\PacsOne\\{AETITLE}\\PreferredXferSyntaxRx\\

If the above named Registry value is defined and it's on the list of transfer syntaxes presented by the remote C-STORE SCU, PacsOne Server Premium Edition will use the specified transfer syntax instead of selecting the first supported transfer syntax from the list presented by the remote AE.

3.4.2.6 Structured Reporting Storage as an SCU and SCP (Premium Edition only)

PacsOne Server Premium Edition provides Standard Conformance to the following DICOM V3.0 Structured Reporting SOP Class as an SCU and SCP.

The following Image Storage SOP Classes may be referenced by instances of Structured Reporting SOP Class.

3.4.3 Real World Activity - Query/Retrieve

PacsOne server accepts associations from applications that wish to perform query (C-FIND) and retrieve (C-MOVE) operations on images that have been previously stored in the MySQL database.

3.4.3.1 Associated Real World Activity - Query/Retrieve

The real-world activity associated with C-FIND and C-MOVE requests are query and retrieval operations initiated by another application. An application other than the PacsOne server queries PacsOne server for patient/study/series/image information that has been previously stored in the MySQL database and can request that the PacsOne server send images to a third application entity.

3.4.3.2 Presentation Context Table - Query/Retrieve

Table 29 shows the presentation contexts that may be accepted by PacsOne server for query operations.

3.4.3.3 SOP Specific Conformance Statement - Query/Retrieve

PacsOne server supports relational queries in addition to hierarchical queries. Table 31 below indicates which keys are supported by the PacsOne server for the Patient Root information model. Table 32 below indicates which keys are supported by the PacsOne server for the Study Root information model.

PacsOne server also supports the Patient/Study Only information model. The keys supported for that model are the same keys found in Table 31 with a level of either "Patient" or "Study".

Table 30 below contains the key matching methods supported by PacsOne Server when processing C-FIND requests from remote Query/Retrieve SCU applications:

Table 31 indicates which keys are supported by the PacsOne server for the Patient Root information model. These tables include all optional and required keys that are supported. Optional keys are supported like required keys.

Table 32 indicates which keys are supported by the PacsOne server for the Study Root information model. These tables include all optional and required keys that are supported. Optional keys are supported like required keys.

PacsOne server supports the three FIND SOP classes listed in Table 3. In response to a C-FIND request, PacsOne server returns the following C-FIND-RSP status codes:

PacsOne server supports the three MOVE SOP classes listed in Table 3. In response to a C-MOVE request, PacsOne server supports the Storage SOP classes that are listed in Table 8 when initiating C-STORE sub-operations.

PacsOne server returns the following status codes in response to a C-MOVE request: