I want to implement a NT 4.0 C++ client application which connects to a
DICOM server, displays the available patients/studies/images and then
downloads a image from the server and stores it somewhere in memory for
I want to use the free OFFIS-Dicom-Toolkit (dcmtk) as the
DICOM implementation if possible.
It looks like the easiest way to download the image would be using the
C-GET Service, but it's not supported in dcmtk 3.3.0 and the support in
3.4.0 is "experimental". So the only other possibility might be C-MOVE.
I assume that I have to establish a SCP for the C-MOVE on the client
Now here my questions:
1. Is the C-GET support in dcmtk 3.4.0 stable?
2. Is there a freeware CTN imageserver which runs unter NT 4.0 and
supports C-GET and information queries and displays a lot of debug
information? It seems that there is no public DICOM-PACS server
available on the web...
3. Do all DICOM-PACS servers support C-GET?
4. Does C-MOVE automatically delete the images on the imageserver when
it moves them to my client's SCP?
5. Are there freeware object-oriented implementations of DICOM for
NT4.0/Visual C++ which have higher abstraction objects for queries
and image retrievals?
I've taken a look at DicomObjects from Medical Connections but it's
too expensive and the examples and helpfiles are too much Visual
Sent via Deja.com http://www.deja.com/
Before you buy.
1) to integrate it into your application in less than 2 hours
2) edit and read DicomDir through browse, delete and import
3) query/retrieve or send to dicom servers
4) compress in jpeg lossless or decompress jpeg lossless, lossless rle, jpeg
5) edit or anonymise patients (create and edit Normalized Patient)
6) customize the DicomDir toolbar to add button-popup menus that calls back
The browser itself is highly customisable (resizable window, change columns
positions, size and title by the user or the registry). Naturally we provide
a Dicom detailed toolkit with most options implemented.
Lastly it is most cheaper than Dicom objects and run Windows 98 and NT.
Our toolkit is Visual C++ oriented, the easiest way to get full access to
Dicom, we also are moving towards higher level stuff (to be used with visula
basic, visual interdev, etc...) but with some restrictions and slower
Let me know if interested, you can try it with support for a month for free.
Do not despair. C-Get is nothing but a C-Move to "myself" :-). C-Get is not
widely supported because of this very fact. If you are a regular reader of
this news group you will notice that this subject is discussed on a regular
Wit the Offis tool kit you can achieve everything you need just by using the
code in the C-MOVE SCU and the Q/R SCPs It is fairly easy to use, and compiles
without a hitch out of the box. As I found out lately you can link with MFC as
a static library if you do not use any of the recompiled headers.
> It looks like the easiest way to download the image would be using the
> C-GET Service, but it's not supported in dcmtk 3.3.0 and the support in
> 3.4.0 is "experimental". So the only other possibility might be C-MOVE.
> I assume that I have to establish a SCP for the C-MOVE on the client
Very few devices support C-GET and almost all support C-MOVE so I would
recommend forgetting about C-GET altogether.
The history behind this is that most devices support C-STORE as an SCP
already, so they are sitting there waiting for inbound images anyway.
It is a small step to add a C-MOVE SCU to ask for more images to be moved
to oneself to the C-STORE SCP.
This obviously requires two associations and is a different paradigm
to http-like protocols, which is why most web-aware people at first
say why not use C-GET, i.e. just one association ?
Since this is just a coding convenience rather than a fundamental issue
of functionality, I always strongly recommend choosing the more popular
service to maximize interoperability with conventional medical imaging
David A. Clunie mailto:dcl...@idt.net
Director, Medical Imaging Technologies http://idt.net/~dclunie/
Quintiles Intelligent Imaging http://www.i2image.com/
521 Plymouth Rd #115 Work 610-238-0572 Fax -0578
Plymouth Meeting PA 19462 Home 570-897-7123 Fax -5117
As far as C-GET vs C-MOVE I aggree with David.
> 4. Does C-MOVE automatically delete the images on the imageserver when
> it moves them to my client's SCP?
No such thing is mentioned in the baseline or extented C-MOVE SCP Behavior.
The matched SOP Intances just "copied" to your C-STORE SCP
> 5. Are there freeware object-oriented implementations of DICOM for
> NT4.0/Visual C++ which have higher abstraction objects for queries
> and image retrievals?
> I've taken a look at DicomObjects from Medical Connections but it's
> too expensive and the examples and helpfiles are too much Visual
> Basic oriented.
Take a look at:
There is a lot of DICOM stuff (source code in C++) based in the public
domain UCDMC DICOM implementation (Runs also in NT40/Visual C++ 6).
There is also an STL based DICOM Implementation, which still make use of
parts of the UCDMC code. This might help you,
Center for Medical Informatics and Health Telematics Applications
Computer Vision and Robotics Division,
Institute for Computer Science,
Foundation for Research and Technology, HELLAS,
P.O. Box 1385, GR 711 10, S.TE.P., Heraklion, Crete, Greece
tel: +30 81 391692 (91), fax: +30 81 391601,
email: kost...@csi.forth.gr, WWW: http://www.ics.forth.gr/~kostoman
Since I need a NT4.0 DICOM Image Server for testing my client, I'd like
to know what server you would recommend for testing of DICOM client
I am currently using imagectn from OFFIS but would also like to connect
to a remote public server.