XPACS Conformance Statement
This document states consistency with conformance to the DICOM standard.
Flow of Application Data
flowchart LR
C1((Send Files)) --> AE1(Storage Application Entity) -.- S1((Receive Files))
C2((Get Worklist)) <--> AE2(Worklist Application Entity) -.- S2((Provide Worklist))
C3((Query Objects/<br />Retrieve Files)) <--> AE3(Query/Retrieve<br />Application Entity) -.- S3((Provide Objects/<br />Files))
AE Function Definitions
Storage Application Entity
A client AE sends files. The Storage AE receives and processes them one by one. Each file saves to a folder then it binds to the existing study/series with the same UIDs if matched.
Worklist Application Entity
A client AE makes a request for worklist items matching search options. The Worklist AE receives the query and returns its results after searching within existing orders.
Query/Retrieve Application Entity
A client AE makes a request for studies/series/instances matching search options. The Query/Retrieve AE receives the query and returns its results after searching within existing objects.
A client AE makes a request for files whose study/series/instance matches search options. The Query/Retrieve AE receives the query and sends its corresponding files back after searching within existing objects.
AE Specifications
Storage Application Entity
SOP Classes
XPACS provides standard conformance to the following SOP Classes:
| SOP Class Name | SOP Class UID | SCU | SCP |
|---|---|---|---|
| Verification | 1.2.840.10008.1.1 |
No | Yes |
| Any image storage | 1.2.840.10008.5.1.4.1.1.* |
No | Yes |
Association Policies
The DICOM standard application context name for DICOM is always accepted and proposed: 1.2.840.10008.3.1.1.1.
The Storage AE supports multiple concurrent associations requested by client AEs.
Association Initiation Policy – Connectivity Verification
The Storage AE is invoked to perform verification. If a client AE successfully establishes an association with the Storage AE, it sends a C-ECHO request.
A possible sequence of interactions between a client AE and the Storage AE is illustrated in the figure below:
sequenceDiagram
participant SCU as Client AE
participant SCP as Storage AE
SCU->>SCP: Open Association
SCU->>SCP: C-ECHO Request
SCP->>SCU: C-ECHO Response
SCU->>SCP: Close Association
The Storage AE is capable of proposing the presentation contexts as shown in the following table:
| Abstract Syntax | UID | Transfer Syntax List | UID List | Role |
|---|---|---|---|---|
| Verification | 1.2.840.10008.1.1 |
Explicit VR Little Endian | 1.2.840.10008.1.2.1 |
SCP |
| Explicit VR Big Endian | 1.2.840.10008.1.2.2 |
|||
| Implicit VR Little Endian | 1.2.840.10008.1.2 |
Association Initiation Policy – Receive Images
The Storage AE is invoked to receive images. If a client AE successfully establishes an association with the Storage AE, it transfers instances, one after another, via the open association.
A possible sequence of interactions between a client AE and the Storage AE is illustrated in the figure below:
sequenceDiagram
participant SCU as Client AE
participant SCP as Storage AE
SCU->>SCP: Open Association
SCU->>SCP: C-STORE Request
SCP->>SCU: C-STORE Response
SCU->>SCP: Close Association
The Storage AE is capable of proposing the presentation contexts as shown in the following table:
| Abstract Syntax | UID | Transfer Syntax List | UID List | Role |
|---|---|---|---|---|
| Any image storage | 1.2.840.10008.1.4.1.* |
JPEG-LS Lossless | 1.2.840.10008.1.2.4.80 |
SCP |
| JPEG 2000 Lossless | 1.2.840.10008.1.2.4.90 |
|||
| JPEG Lossless, Non-Hierarchical, FOP | 1.2.840.10008.1.2.4.70 |
|||
| JPEG Lossless, Non-Hierarchical | 1.2.840.10008.1.2.4.57 |
|||
| RLE Lossless | 1.2.840.10008.1.2.5 |
|||
| JPEG-LS Lossy (Near-Lossless) | 1.2.840.10008.1.2.4.81 |
|||
| JPEG 2000 Lossy | 1.2.840.10008.1.2.4.91 |
|||
| JPEG Baseline | 1.2.840.10008.1.2.4.50 |
|||
| JPEG Extended | 1.2.840.10008.1.2.4.51 |
|||
| Explicit VR Little Endian | 1.2.840.10008.1.2.1 |
|||
| Explicit VR Big Endian | 1.2.840.10008.1.2.2 |
|||
| Implicit VR Little Endian | 1.2.840.10008.1.2 |
Association Acceptance Policy
The Storage AE can be configured to only accept associations with certain hosts (using TCP/IP address) and AE titles.
Worklist Application Entity
SOP Classes
XPACS provides standard conformance to the following SOP Classes:
| SOP Class Name | SOP Class UID | SCU | SCP |
|---|---|---|---|
| Verification | 1.2.840.10008.1.1 |
No | Yes |
| Modality Worklist Information Model – FIND | 1.2.840.10008.5.1.4.31 |
No | Yes |
Association Policies
The DICOM standard application context name for DICOM is always accepted and proposed: 1.2.840.10008.3.1.1.1.
The Worklist AE supports multiple concurrent associations requested by client AEs.
Association Initiation Policy – Connectivity Verification
The Worklist AE is invoked to perform verification. If a client AE successfully establishes an association with the Worklist AE, it sends a C-ECHO request.
A possible sequence of interactions between a client AE and the Worklist AE is illustrated in the figure below:
sequenceDiagram
participant SCU as Client AE
participant SCP as Worklist AE
SCU->>SCP: Open Association
SCU->>SCP: C-ECHO Request
SCP->>SCU: C-ECHO Response
SCU->>SCP: Close Association
The Worklist AE is capable of proposing the presentation contexts as shown in the following table:
| Abstract Syntax | UID | Transfer Syntax List | UID List | Role |
|---|---|---|---|---|
| Verification | 1.2.840.10008.1.1 |
Explicit VR Little Endian | 1.2.840.10008.1.2.1 |
SCP |
| Explicit VR Big Endian | 1.2.840.10008.1.2.2 |
|||
| Implicit VR Little Endian | 1.2.840.10008.1.2 |
Association Initiation Policy – Provide Worklist
The Worklist AE is invoked to return orders on inquiry. If a client AE successfully establishes an association with the Worklist AE, it transfers a request for worklist items via the open association. The Worklist AE will return the worklist items matching the query attributes.
The following worklist query attributes are supported:
| Attribute Name | Tag | Matching |
|---|---|---|
| Component Name | (0010,0010) |
Based on pattern |
| Component ID | (0010,0020) |
Based on pattern |
| Accession Number | (0008,0050) |
Based on pattern |
| Component Owner Name | (0008,0090) |
Based on pattern |
| Requested Job ID | (0040,1001) |
Based on pattern |
| Requested Job Description | (0032,1060) |
Based on pattern |
| Study Instance UID | (0020,000D) |
Exact |
| Scheduled Procedure Step Sequence | (0040,0100) |
|
| >Scheduled Procedure Step Start Date | (0040,0002) |
Within range |
| >Modality | (0008,0060) |
Exact |
| >Scheduled Operator Name | (0040,0006) |
Based on pattern |
| >Scheduled Station Name | (0040,0010) |
Based on pattern |
A possible sequence of interactions between a client AE and the Worklist AE is illustrated in the figure below:
sequenceDiagram
participant SCU as Client AE
participant SCP as Worklist AE
SCU->>SCP: Open Association
SCU->>SCP: C-FIND Request (Worklist Query)
SCP->>SCU: C-FIND Response (Worklist Item)
note left of SCP: Status = Pending
SCP->>SCU: C-FIND Response (Worklist Item)
note left of SCP: Status = Pending
SCP->>SCU: C-FIND Response (Worklist Item)
note left of SCP: Status = Success
SCU->>SCP: Close Association
- The client AE opens an association with the Worklist AE.
- The client AE sends a C-FIND request to the Worklist AE containing the worklist query attributes.
- The Worklist AE returns a C-FIND response containing the requested attributes of the first matching worklist item.
- The Worklist AE returns another C-FIND response containing the requested attributes of the second matching worklist item.
- The Worklist AE returns another C-FIND response with status success indicating that no further matching worklist items exist. This example assumes that only two worklist items match the query.
- The client AE closes the association with the Worklist AE.
The Worklist AE is capable of proposing the presentation contexts as shown in the following table:
| Abstract Syntax | UID | Transfer Syntax List | UID List | Role |
|---|---|---|---|---|
| Modality Worklist Information Model – FIND | 1.2.840.10008.5.1.4.31 |
Explicit VR Little Endian | 1.2.840.10008.1.2.1 |
SCP |
| Explicit VR Big Endian | 1.2.840.10008.1.2.2 |
|||
| Implicit VR Little Endian | 1.2.840.10008.1.2 |
Association Acceptance Policy
The Worklist AE can be configured to only accept associations with certain hosts (using TCP/IP address) and AE titles.
Query/Retrieve Application Entity
SOP Classes
XPACS provides standard conformance to the following SOP Classes:
| SOP Class Name | SOP Class UID | SCU | SCP |
|---|---|---|---|
| Verification | 1.2.840.10008.1.1 |
No | Yes |
| Study Root Query/Retrieve Information Model – FIND | 1.2.840.10008.5.1.4.1.2.2.1 |
No | Yes |
| Study Root Query/Retrieve Information Model – GET | 1.2.840.10008.5.1.4.1.2.2.3 |
No | Yes |
| Study Root Query/Retrieve Information Model – MOVE | 1.2.840.10008.5.1.4.1.2.2.2 |
Yes | Yes |
Association Policies
The DICOM standard application context name for DICOM is always accepted and proposed: 1.2.840.10008.3.1.1.1.
The Query/Retrieve AE supports multiple concurrent associations requested by client AEs.
Association Initiation Policy – Connectivity Verification
The Query/Retrieve AE is invoked to perform verification. If a client AE successfully establishes an association with the Query/Retrieve AE, it sends a C-ECHO request.
A possible sequence of interactions between a client AE and the Query/Retrieve AE is illustrated in the figure below:
sequenceDiagram
participant SCU as Client AE
participant SCP as Query/Retrieve AE
SCU->>SCP: Open Association
SCU->>SCP: C-ECHO Request
SCP->>SCU: C-ECHO Response
SCU->>SCP: Close Association
The Query/Retrieve AE is capable of proposing the presentation contexts as shown in the following table:
| Abstract Syntax | UID | Transfer Syntax List | UID List | Role |
|---|---|---|---|---|
| Verification | 1.2.840.10008.1.11 |
Explicit VR Little Endian | 1.2.840.10008.1.2.1 |
SCP |
| Explicit VR Big Endian | 1.2.840.10008.1.2.2 |
|||
| Implicit VR Little Endian | 1.2.840.10008.1.2 |
Association Initiation Policy – Provide Studies/Series/Instances
The Query/Retrieve AE is invoked to return studies/series/instances on inquiry. If a client AE successfully establishes an association with the Query/Retrieve AE, it transfers a request of objects via the open association. The Query/Retrieve AE will return the objects matching the query attributes.
The following study query attributes are supported:
| Attribute Name | Tag | Matching |
|---|---|---|
| Component Name | (0010,0010) |
Based on pattern |
| Component ID | (0010,0020) |
Based on pattern |
| Accession Number | (0008,0050) |
Based on pattern |
| Component Owner Name | (0008,0090) |
Based on pattern |
| Requested Job ID | (0040,1001) |
Based on pattern |
| Requested Job Description | (0032,1060) |
Based on pattern |
| Study Instance UID | (0020,000D) |
Exact |
| Study Date | (0008,0020) |
Within range |
| Modalities in Study | (0008,0061) |
Exact |
| Study ID | (0020,0010) |
Based on pattern |
| Study Description | (0008,1030) |
Based on pattern |
The following series query attributes are supported:
| Attribute Name | Tag | Matching |
|---|---|---|
| Study Instance UID | (0020,000D) |
Exact |
| Series Instance UID | (0020,000E) |
Exact |
| Modality | (0008,0060) |
Exact |
| Series Description | (0008,103E) |
Based on pattern |
| Protocol Name | (0018,1030) |
Based on pattern |
The following instance query attributes are supported:
| Attribute Name | Tag | Matching |
|---|---|---|
| Study Instance UID | (0020,000D) |
Exact |
| Series Instance UID | (0020,000E) |
Exact |
| SOP Instance UID | (0008,0018) |
Exact |
A possible sequence of interactions between a client AE and the Query/Retrieve AE is illustrated in the figure below:
sequenceDiagram
participant SCU as Client AE
participant SCP as Query/Retrieve AE
SCU->>SCP: Open Association
SCU->>SCP: C-FIND Request (Study/Series/Instance Query)
SCP->>SCU: C-FIND Response (Study/Series/Instance)
note left of SCP: Status = Pending
SCP->>SCU: C-FIND Response (Study/Series/Instance)
note left of SCP: Status = Pending
SCP->>SCU: C-FIND Response (Study/Series/Instance)
note left of SCP: Status = Success
SCU->>SCP: Close Association
- The client AE opens an association with the Query/Retrieve AE.
- The client AE sends a C-FIND request to the Query/Retrieve AE containing the study/series/instance query attributes.
- The Query/Retrieve AE returns a C-FIND response containing the requested attributes of the first matching study/series/instance.
- The Query/Retrieve AE returns another C-FIND response containing the requested attributes of the second matching study/series/instance.
- The Query/Retrieve AE returns another C-FIND response with status success indicating that no further matching studies/series/instances exist. This example assumes that only two objects match the query.
- The client AE closes the association with the Query/Retrieve AE.
The Query/Retrieve AE is capable of proposing the presentation contexts as shown in the following table:
| Abstract Syntax | UID | Transfer Syntax List | UID List | Role |
|---|---|---|---|---|
| Study Root Query/Retrieve Information Model – FIND | 1.2.840.10008.5.1.4.1.2.2.1 |
Explicit VR Little Endian | 1.2.840.10008.1.2.1 |
SCP |
| Explicit VR Big Endian | 1.2.840.10008.1.2.2 |
|||
| Implicit VR Little Endian | 1.2.840.10008.1.2 |
Association Initiation Policy – Provide Files
The Query/Retrieve AE is invoked to return files corresponding to studies/series/instances on inquiry. If a client AE successfully establishes an association with the Query/Retrieve AE, it transfers a request of files corresponding to objects via the open association. The Query/Retrieve AE will return the files corresponding to the objects matching the query attributes.
The following study query attributes are supported:
| Attribute Name | Tag | Matching |
|---|---|---|
| Component Name | (0010,0010) |
Based on pattern |
| Component ID | (0010,0020) |
Based on pattern |
| Accession Number | (0008,0050) |
Based on pattern |
| Component Owner Name | (0008,0090) |
Based on pattern |
| Requested Job ID | (0040,1001) |
Based on pattern |
| Requested Job Description | (0032,1060) |
Based on pattern |
| Study Instance UID | (0020,000D) |
Exact |
| Study Date | (0008,0020) |
Within range |
| Modalities in Study | (0008,0061) |
Exact |
| Study ID | (0020,0010) |
Based on pattern |
| Study Description | (0008,1030) |
Based on pattern |
The following series query attributes are supported:
| Attribute Name | Tag | Matching |
|---|---|---|
| Study Instance UID | (0020,000D) |
Exact |
| Series Instance UID | (0020,000E) |
Exact |
| Modality | (0008,0060) |
Exact |
| Series Description | (0008,103E) |
Based on pattern |
| Protocol Name | (0018,1030) |
Based on pattern |
The following instance query attributes are supported:
| Attribute Name | Tag | Matching |
|---|---|---|
| Study Instance UID | (0020,000D) |
Exact |
| Series Instance UID | (0020,000E) |
Exact |
| SOP Instance UID | (0008,0018) |
Exact |
A possible sequence of interactions between a client AE and the Query/Retrieve AE is illustrated in the figure below:
sequenceDiagram
participant SCU as Client AE
participant SCP as Query/Retrieve AE
SCU->>SCP: Open Association
SCU->>SCP: C-GET Request (Study/Series/Instance Query)
SCP->>SCU: C-STORE Request
SCU->>SCP: C-STORE Response
SCP->>SCU: C-STORE Request
SCU->>SCP: C-STORE Response
SCP->>SCU: C-GET Response (Study/Series/Instance)
SCU->>SCP: Close Association
- The client AE opens an association with the Query/Retrieve AE.
- The client AE sends a C-GET request to the Query/Retrieve AE containing the study/series/instance query attributes.
- The Query/Retrieve AE sends a C-STORE request containing the file corresponding to the first matching study/series/instance.
- The client AE returns a C-STORE response.
- The Query/Retrieve AE sends another C-STORE request containing the file corresponding to the second matching study/series/instance.
- The client AE returns a C-STORE response.
- The Query/Retrieve AE returns a C-GET response. This example assumes that only two objects match the query.
- The client AE closes the association with the Query/Retrieve AE.
The Query/Retrieve AE is capable of proposing the presentation contexts as shown in the following table:
| Abstract Syntax | UID | Transfer Syntax List | UID List | Role |
|---|---|---|---|---|
| Study Root Query/Retrieve Information Model – GET | 1.2.840.10008.5.1.4.1.2.2.3 |
JPEG-LS Lossless | 1.2.840.10008.1.2.4.80 |
SCP |
| JPEG 2000 Lossless | 1.2.840.10008.1.2.4.90 |
|||
| JPEG Lossless, Non-Hierarchical, FOP | 1.2.840.10008.1.2.4.70 |
|||
| JPEG Lossless, Non-Hierarchical | 1.2.840.10008.1.2.4.57 |
|||
| RLE Lossless | 1.2.840.10008.1.2.5 |
|||
| JPEG-LS Lossy (Near-Lossless) | 1.2.840.10008.1.2.4.81 |
|||
| JPEG 2000 Lossy | 1.2.840.10008.1.2.4.91 |
|||
| JPEG Baseline | 1.2.840.10008.1.2.4.50 |
|||
| JPEG Extended | 1.2.840.10008.1.2.4.51 |
|||
| Explicit VR Little Endian | 1.2.840.10008.1.2.1 |
|||
| Explicit VR Big Endian | 1.2.840.10008.1.2.2 |
|||
| Implicit VR Little Endian | 1.2.840.10008.1.2 |
|||
| Any image storage | 1.2.840.10008.1.4.1.* |
JPEG-LS Lossless | 1.2.840.10008.1.2.4.80 |
SCP |
| JPEG 2000 Lossless | 1.2.840.10008.1.2.4.90 |
|||
| JPEG Lossless, Non-Hierarchical, FOP | 1.2.840.10008.1.2.4.70 |
|||
| JPEG Lossless, Non-Hierarchical | 1.2.840.10008.1.2.4.57 |
|||
| RLE Lossless | 1.2.840.10008.1.2.5 |
|||
| JPEG-LS Lossy (Near-Lossless) | 1.2.840.10008.1.2.4.81 |
|||
| JPEG 2000 Lossy | 1.2.840.10008.1.2.4.91 |
|||
| JPEG Baseline | 1.2.840.10008.1.2.4.50 |
|||
| JPEG Extended | 1.2.840.10008.1.2.4.51 |
|||
| Explicit VR Little Endian | 1.2.840.10008.1.2.1 |
|||
| Explicit VR Big Endian | 1.2.840.10008.1.2.2 |
|||
| Implicit VR Little Endian | 1.2.840.10008.1.2 |
Association Acceptance Policy
The Query/Retrieve AE can be configured to only accept associations with certain hosts (using TCP/IP address) and AE titles.
Communication Profile
Supported communication stack
TCP/IP network communication support defined in Part 8 of the DICOM Standard is provided.
TCP/IP stack
Depending on TCP/IP stack supported by the operating system.
Physical medium support
Depending on a physical medium supported by the operating system.
Configuration
The following settings can be configured:
- Storage AE title and TCP/IP port
- Worklist AE title and TCP/IP port
- Query/Retrieve AE title and TCP/IP port
- Accept associations with either any client AE or only certain client hosts (using TCP/IP address) and AE titles
- Client AEs, each one can be configured with the following settings:
- Client AE title
- Client host (using TCP/IP address)
- The Storage AE accepts or does not associations with this client AE
- The Worklist AE accepts or does not associations with this client AE
- The Query/Retrieve AE accepts or does not associations with this client AE
- The host (using TCP/IP address) and TCP/IP port used in C-MOVE by the Query/Retrieve AE