MEDICALIBRATION Conformance Statement

for DICOM Link Program

DICOMLINKÓ

This conformance statement specifies the compliance of the DicomLink Package from Medicalibration to the guidelines set forward by the Joint College of Radiology and National Electrical Manufactures Association (ACR-NEMA) committee.

DicomLink utilizes DICOM services in order to communicate and import images from other DICOM compliant systems, allowing one’s desktop computer to participate in a DICOM environment. In this application DicomLink functions as a Service Class Provider (SCP) for either the Storage Service Class or the Verification Service Class.

Implementation:

This section consists of a data flow diagram describing how the DicomLink DICOM Server Application Entity (AE) works with remote DICOM devices, a functional definition of the AE and its real-world activities and a description of the Real-World sequence of events of the AE.

Storage Service:

When a remote DICOM device, such as a medical CT scanner, selects a number of files to send to DicomLink acting as the local DICOM Application Entity, a DICOM association is initiated. The local AE (DicomLink) either accepts or denies the request based on the association parameters communicated in the request. If accepted, information as to the local AE’s capabilities are communicated back to the remote AE (the CT scanner, for example) and the agreed upon communication is started with DicomLink accepting the data from the remote AE and storing the data on the local AE’s associated PC where specified, usually the PC computer’s hard disk.

The real world activity is that the files from the remote AE (the CT scanner) are stored to the local AE (the PC3D PC computer) in a manner specified within DicomLink

Verification Service:

If a remote AE (Scanner) wishes to verify that DicomLink is running at a site, it may initiate a Verification Request. DicomLink uses the same criteria for accepting or denying the association request. If accepted, DicomLink replies to the remote AE (the scanner) that is ready and capable of accepting associations.

Functional Definitions:

DicomLink can act as a Service Class Provider (SCP) for either the Storage Service Class or the Verification Service Class as diagrammed above.

Storage: DicomLink receives images from remote DICOM AE’s (such as CT scanners) and stores them locally. All images transmitted will be stored to the user defined location in their entirety, with all elements remaining intact.

Verification: DicomLink will respond to any verification requests received.

Sequencing of Real-World Activities:

The DicomLink DICOM Application Entity waits for association requests by listening on a number of previously specified TCP/IP ports. Access privileges for each port can be individually configured for varying degrees of security.

Asynchronous Nature:

Asynchronous operations window negotiations is not supported. All operations will be performed synchronously.

TCP/IP Stack:

DicomLink provides TCP/IP Network Communications Support. DicomLink inherits the TCP/IP stack from the Windows Operating System on which it is running. DicomLink is indifferent to the physical medium over which TCP/IP operates and operates over 10Base-2 ThinNet, 10Base-5 ThickNet, 10Base-T, TokenRing and other Ethernet networks conforming to the Ethernet standard.

File Configuration Parameters:

The destination to which the incoming files are to be stored can be configured by the user. The site can be to the local disk or to other removable or fixed devices connected to the machine on which

DicomLink is running. It is also possible to designate any other reachable device on the Local Area Network (LAN) connected to the local computer.

The method by which the folder hierarchy created for the incoming files is user definable.

Extended Character Sets:

DicomLink dose not support extended character sets at this time

Other Specifications:

Only the following Classes are supported in their uncompressed formats by the PC3D module CTconvert serving as an Image SCP

CT image Storage 1.2.840.10008.5.1.4.1.2

MR image Storage 1.2.840.10008.5.1.4.1.4

UltraSound Image Storage 1.2.840.10008.5.1.4.1.6

First, make sure that DICOMLNK, the DicomLink program, is launched at the end of the installation process. If that wasn't done, please execute the file ODBCINST.EXE. It should be located in the same folder as DICOMLINK. The 32 bit ODBC must be installed prior to running DICOMLNK, the DicomLink program. TCP/IP drivers must also be correctly installed and configured before attempting a connection. After the above requirements have been met, continue below to configure the ODBC32 database for use by DicomLink.

For Windows '95/98 Users

-------------------------------

-Click on 'Start'

-Select 'Settings'

-Select 'Control Panel'

-Continue below at Windows NT/95

For Windows NT Users

--------------------------------

-Click on 'Main' Program Group in Program Manager

-Click on 'Control Panel'

-Continue below at Windows NT/95

Windows NT/95/98

---------------------

-Select '32bitODBC'

-Select tab 'User DSN'

-Select 'Add'

-Select 'Microsoft Access Driver (*.mdb)'

-Select 'Finish'

-(Required) Type in ' DicomLink' in the section Data Source

Name without apostrophes!

-(Optional) Type in 'DICOM Link Main Database' in the Description field

-Select 'Select'

-Locate the DICOMLNK.MDB file with the file dialog box.

The Path should resemble: C:\ProgramFiles\Medicalibration\DICOMLink\DicomLnk.mdb

-Select 'Ok' to close file dialog box.

-Select 'Ok' to close ODBC Data Source Administrator

1) You must create a remote server entry in the File-Settings before attempting to connect.

2) Local Application Entity corresponds to Calling Application Entity. Try 'Client' if problems persist.

3) Remote Application Entity corresponds to Called Application Entity. Ask remote system administrator for proper A.E.

4) IP Address is the actual Internet address of the Remote Server. i.e., foo.bar.foo or 111.111.111.111

5) Local port address is for external DICOM clients/servers trying to establish a connection with DICOMLNK, the DicomLink program (i.e. Outside source calling DicomLink ). This port address is required for C-MOVE-RQs issued during a query/retrieval.

6) Remote port is VERY critical. Ask remote system administrator for proper value. A common DICOM port is 104

7) Image locations is the main storage place for retrieved images. It must have a trailing slash '\'

To Query a Server:

1) Select the server name in the Remote Server list box.

2) You can view the various attributes of each Patient/Study/Series by selecting that attribute in the list box.

To Retrieve a(n) Patient/Study/Series/Image:

1) Select the entries in the appropriate list. For example, George Washington in the Patient Name list or Study ID #0000001 in the study list.

2) Select 'Retrieve' and the images will start transferring.

NOTE: Selecting a patient name only followed by Retrieve will retrieve ALL of the Studies, Series and Images for that Patient. If you select a patient, a study and then select Retrieve, you will receive all of the Series and Images of that selected Study of that Patient.

RETRIEVE NOTE: Some Image types are not currently supported. The following list indicates supported file types.

(CT) - Computed Tomography

(MRI) - Magnetic Resonance Imaging

(US) - Ultrasound (Single Frame)

To Send ( Push ) an Image (Currently DISABLED)

1) Make sure the image is located in the LOCAL volume's database.

a) Select FILE followed by ADD TO DATABASE

b) Locate and select desired file

c) Select OK.

2) Establish a connection as in step #1 of "To query a server" above.

3) Select the LOCAL volume

4) Select the Patient, Study, Series or Image on the LOCAL volume

5) Select SEND. Connection and transfer should follow

If you have any questions or comments, you can contact Technical Support

at Medicalibration: 1 (800) 782-7360

or: 1 (209) 524-6789

or leave Email at: techsupport@medicalibration.com