Executive Summary: Purpose and Scope of This Specification
Executive Summary: Purpose and Scope of This Specification
Product/Service Description
XXX PACS software provides a means of receiving, displaying, and storing images from modalities. It also
provides measurement tools to allow users to edit or create new measurements on them.
Product Context
The XXX PACS product is based on a modular design allowing it to be used with a host system platform. XXX
PACS integrates with medical devices that send and receive images and measurement data.
Requirements
Functional Requirements
Imaging Requirements
Req Descripti
# on
Req Descripti
# on
Re Series Navigation control: allows the user to navigate through the series when the exam has
q- more than one series
AV Next series
-01
Previous series
First series
Last series
Current series: display and allows the user to edit the value to go to specific series
Display the total number of series in the exam
Re General tools and Annotations
q-
AV The user should be able to draw free tools that don’t depend on the image.
-02 Free tools are: Text, line, arrow, marker and highlighter
The color and size of these tools should be controlled
Change the tool color using the standard color picker window dialog
Change the thickness using a thickness picker dialog
The user should be able to control the font of the text and standard font properties
like weight and style.
Req Image Layout window: we need to be able to allow displaying multiple images in the current
-
AV- available display area.
03
1 UP takes the whole display area
2UP displays two images spanning one row and two columns
4UP displays four images spanning two rows and two columns
support for generic n x m up (Rows x Columns)
support automatic n x m layout for stress module
Ability to maximize any view to full screen
Re Customize default mouse action
q-
AV- We can choose for each of the 3 mouse buttons (Left, Middle, Right) the default action
04
The action can be: pan, zoom, brightness/contract, frame scroll, none
Re WW/WL presets
q-
AV- We need to give the user the ability to save and apply a ww/wl presets.
05
The user can change the ww/wl using mouse interaction, then press save to capture
the ww/wl values for future use.
The user at any time can select a ww/wl value from the preset table and apply it to any or
all images.
Re Overlay Support
q-
AV- Some images have a single or multiple overlay plans; we need to load all of them into a
06 single plan.
The user should have a global check box to enable or disable showing
found..
The wireframes below are screen blueprints and visual guides that represent the skeletal framework of the
XXX product UI.
IMPLEMENTATION MODEL
XXX DICOM services are implemented as one single process XXX server which listen on two different ports one
for store SCP and the second for worklist SCP. Every service has its own configured Application Entity Title.
The XXX Server is responsible for image reception and transmission in addition to accepting requests for
database queries and retrieves. It maintains logs of all studies that entered and left the system. It can perform
scheduled image transfers to remote Application Entities.
The XXX Database and XXX server are integral parts of a XXX installation.
ICOM
Accept C- S
tandard Remote
Store and
Neurev Interface
save data in Store SCU
eal Store Initiate C-
the database
SCP Store
Initiate C- Neurev
eal Store Store SCP
Store and SCU Accept C-
transfer of Store
studies
Accept C- Neureve
al worklist SCP Association Response Initiate C-
Find and service Find for
send
worklist
worklist
C-FIND-RQ, C-MOVE-RQ
Neureveal
Initiate C-FIND Query/Retrieve SCU Query/
Query and C- Retrieve
SCP
MOVE transfer
The Application Entity of the XXX worklist front-end application acts as an SCP for the worklist SOP classes.
General
The configuration of the XXX DICOM services shall define such parameters as Application Entity title, host
name, and port number that are shared by the Connection, Database
Number of Associations
The XXX server supports multiple associations both as an SCU and SCP. There is no maximum number of
simultaneous associations.
When receiving images as an SCP the Connection Service will start a new thread for each association that is
being handled. As an SCU the Connection Service also supports multiple associations, for instance to verify a
remote destination and simultaneously send images to a storage SCP.
Synchronous Nature
The XXX DICOM server supports asynchronous operations.
Association Initiation Policy
XXX initiates associations for the following activities:
Verify Communication
Send dicom objects to remote system
Query/retrieve dicom objects from a remote system
Extende
● Abstract Syntax ● Transfer Syntax ● R
d
O
● Name ● UID ● Name ● UID
Negoti
L ati
E o
n
∙ ∙ ● Explicit ● 1.2.840.10008.1.2 ● S ∙
VR . C
1
● Littl P
e
Endi
an
There are no specific rules for acceptance and prioritization of presentation contexts and XXX server will
accept all presentation contexts that match those listed in the table shown above.
A remote system wants to send images and structured reports to XXX server to be archived in XXX image and
clinical database . Once the transfer is completed the new images and reports will automatically be included in the
user’s image and analysis view of the local database of XXX server and can be selected for display.
● R
O
● N
e
o
t
i
a
t
i
E
● Comprehensi ● 1.2.840.10008.5.1.4.1.1.88.33 ● Implicit VR, Little ● 1.2.840.10008.1.2 ● N
Endian
● S
ve Structured O
Report
● Explicit VR, Little ● 1.2.840.10008.1.2.1
C
Endian N
P
● Explicit VR Big Endian ● 1.2.840.10008.1.2.2
E
O Negotiatio n
Name UID Name UID
L
E
Implicit VR 1.2.840.10008.1.2 SC None
U
Little
Patient Root
Endi
Query/Retri an
eve
1.2.840.10008.5.1.4.1.2.1
Explicit VR 1.2.840.10008.1.2. SC None
.
Information
1 1 U
Little
Model -
FI Endi
N an
D
Explicit VR 1.2.840.10008.1.2.2 SC None
Big U
Endian
Patient Root 1.2.840.10008.5.1.4.1.2.1 Implicit VR 1.2.840.10008.1.2 SC None
.
Query/Retri 2 U
eve Little
Endi
Information
an
Model - Explicit VR 1.2.840.10008.1.2. SC None
M
OV 1 U
E Little
Endi
an
Explicit VR 1.2.840.10008.1.2.2 SC None
Big U
Endian
Study Root 1.2.840.10008.5.1.4.1.2.2 Implicit VR 1.2.840.10008.1.2 SC None
.
Query/Retri 1 U
eve Little
Endi
Information
an
Model - Explicit VR 1.2.840.10008.1.2. SC None
FI
N 1 U
D Little
Endi
an
Explicit VR 1.2.840.10008.1.2.2 SC None
Big U
Endian
Study Root 1.2.840.10008.5.1.4.1.2.2 Implicit VR 1.2.840.10008.1.2 SC None
.
Query/Retri 2 U
eve Little
Endi
Information
an
Model - Explicit VR 1.2.840.10008.1.2. SC None
M
OV 1 U
E Little
Endi
an
Explicit VR 1.2.840.10008.1.2.2 SC None
Big U
Endian
Patient/Stu 1.2.840.10008.5.1.4.1.2.3 Implicit VR 1.2.840.10008.1.2 SC None
dy .
1 U
Only Little
Endi
Query/Retri
eve
an
Explicit VR 1.2.840.10008.1.2. SC None
Information
1 U
Model - Little
FI Endi
N
D
an
Explicit VR 1.2.840.10008.1.2.2 SC None
Big U
Endian
Patient/Stu 1.2.840.10008.5.1.4.1.2.3 Implicit VR 1.2.840.10008.1.2 SC None
dy .
2 U
Only Little
Endi
Query/Retri
eve
an
Explicit VR 1.2.840.10008.1.2. SC None
Information
1 U
Model - Little
M Endi
OV
E
an
Explicit VR 1.2.840.10008.1.2.2 SC None
Big U
Endian
SOP Specific Conformance Statement for Patient Root Query/Retrieve Information Model Find SOP Class
Modality 0008,0060
∙
Study ID 0020,0010
∙
SOP Specific Conformance Statement for Study Root Query/Retrieve Information Model Find SOP Class
Modality 0008,0060
∙
SOP Specific Conformance Statement for Patient Root Query/Retrieve Information Model MOVE SOP Class
Level
Patient ID 0010,0020
∙
Level
Extensions/Specializations/Privatizations
Configuration
Configuration will be done only by a XXX technical support.