Showing posts with label DICOM. Show all posts
Showing posts with label DICOM. Show all posts

Wednesday, 13 January 2010

ClearCanvas 2.0 Beta – External Applications Feature

I managed to get ClearCanvas to pull reports from our own RIS system using the external applications featureimage in the new Beta 2.0 version.

Thanks to Jonathan for pointing me to the new ClearCanvas channel on YouTube http://www.youtube.com/clearcanvas.

Our RIS application has a web interface that allows for reports to be accessed using a basic URL. So all I did was point an external application to internet explorer and add the relevant parameters to it.

 

The $001000020$ tag is for the patient ID, which is what we currently use to identify patient reports. You can pull out any dicom tag using this tool.

I did however find that I was unable to use normal command line shortcuts like %SystemRoot% or %ProgramFiles% shortcuts. But it is not a major train smash.

Below is the video from ClearCanvas that explains how to setup an external application.

 

This is yet another great new feature added by ClearCanvas that can have many applications. Here are a coupe of other ideas on things that can be done with this great feature:

Convert Images to JPG:

You can use dcmj2pnm.exe from DCMTK (http://dicom.offis.de/dcmtk) to convert images to JPG.
Check out the screenshot below: This converts the image to a 1024 width JPG image.

I still need to figure out a method of using this feature to convert all images in a series, but at the moment the screenshot below will help you convert single images.

image

Email Images Using Blat:

You can get blat from http://www.blat.net/.

I think the screenshot below explains it pretty well. Just remember that you will need relay rights in order to use this. The script below will also only send the images to one person and one image at a time. I think It would be possible to write a bat script to do it more efficiently.

image

Emailing Multiple JPG Images

It should be possible to create a bat script that uses the above applications to convert images to JPG and then attach them to an email to be sent to an email address obtained from the user via a prompt. I am going to work on this a bit and see what I can come up with.

If there are any other external command line applications that you would like to see being used in ClearCanvas and you need a hand drop a comment with some information and I’ll see if I can help out.

Once again, thanks to the ClearCanvas team for make a really great application and continuing to add useful features!

Thursday, 9 July 2009

ClearCanvas moving away from Open Source?

CCLogo

ClearCanvas released the documentation to the community for review today. The documentation is for their upcoming software releases of ClearCanvas Workstation 1.5, ClearCanvas Image Server 1.5 and ClrearCanvas SDK 1.5.

Something interesting and concerning that I have noticed is that in the ImageServer User Guide under “Enterprise Version”. It would seem as though ClearCanvas may be making a “pay for” version of the image server software. I certainly hope this is not the case!

Anyway according to the documentation we can probably expect version 1.5 of ClearCanvas Workstation, Image Server and SDK before the end of July.

Thursday, 5 February 2009

DHCP for DICOM?

I was driving to work this morning and I started thinking about how much it sucks to setup a new modality on our network. Every time something new comes along we have to contact every modality vendor and get them to add the new machines settings, because we are not given the usernames and passwords to add them ourselves. This means you need to contact about 5 different people and try and organise time on the modality. In the end it normally takes anything from 1 to 2 weeks to get everything communicating.

Wouldn't it be great if someone came up with a DHCP protocol for the DICOM standard that would allow for a centralised management area of all modalities and their configuration settings. Imagine adding a new modality to the network and all you have to do is give the technician the DCM-DHCP server details and boom! all your DICOM settings are downloaded to that machine. Then all you need to do is add the new modality to the DCM-DHCP server and all the other modalities can now communicate with it!

I don't think this would be difficult to implement and security could be added to prevent "rouge modalities" from entering the network. With a system of centralised DICOM configuration and management life would be a lot easier for everyone, including the vendors.

Friday, 9 January 2009

Conquest & Philips MRI 3T Troubles

Our Philips 3T MRI is giving us problems when archiving to one of our Conquest servers. It seems like the Radiographers workstation sends images in MRIImageStorageEnhaced (1.2.840.10008.5.1.4.1.1.4.1 - MR) and  GrayscaleSoftcopyPresentationStateStorage (1.2.840.10008.5.1.4.1.1.11.1 - PR) format to the archive.

The Philips ViewForum, GE Centricity, K-PACS and ClearCanvas workstations that we use can not retrieve these images sent to the archive from this modality.

After doing a little bit of digging and some Googling I found that I am not the only one with this problem.

As per the advice in these forum posts I removed the following (By putting a # in front of them.) from the dgatesop.lst file:

  • MRImageStorageEnhanced    1.2.840.10008.5.1.4.1.1.4.1 sop
  • GrayscaleSoftcopyPresentationStateStorage 1.2.840.10008.5.1.4.1.1.11.1 sop

This seems to have solved the problem of new images received by the server as it changes their SOPClassUI to MRStorage 1.2.840.10008.5.1.4.1.1.4
However all existing images on the server with the SOP classes that where disabled above are now not visible to the workstations.

The same modality sends images to our old Conquest archive in the same format and everything works fine. The two Conquest servers configurations are almost identical, they are both running 1.4.14, with jpeg lossless compression enabled.

I also noticed in the logs on both servers that there where multiple entries stating:

*** Association rejected: you may need to add the listed presentation context as sop to dgatesop.lst

I have also noticed that there is a difference in the dgatesop.lst files:

dgatesop.lst compare

As you can see in the screenshot above, I used notepad++ to compare the files and found that the server giving the problems has LittleEndianExplicit disabled.

I re-enabled this and it still had little effect.

I have posted on the Conquest Server forum and hope that Marcel can come to my rescue again, because I am sitting with about 300-400 patients that can not be accessed!

Monday, 10 November 2008

Conquest Dicom Flex Web Viewer Screenshots

As promissed here are some screenshots of the Conquest Flex Webviewer system that I am working on at the moment. Please note that this system is still a work in progress and is not yet ready for release.


This is the main worklist interface which initially displays the studies for the current day.



This is the main viewer interface.



The screenshot above shows an image that could not be converted.



Above is the log screen that shows viewer events such as image conversion errors.

K-PACS v1.6 Released

I haven't been onto the k-pacs.de website in a while, but this morning I went back to be greated by a new version of thier application, K-PACS 1.6.
The system seems pretty much the same as version 1.5, but I have not had a chance yet to look at it too closely. Hopefully I can give a full review in the next couple of days.

I did notice a new disclaimer though, see screenshot below:

Monday, 3 November 2008

Conquest Web Viewer 2.0

I have recently found out about something called Adobe Flex. Flex is a programming language that allows you to make Adobe Flash applications. I did some experimentation and found that you can do a couple of cool things with it like pull information in from PHP, dynamically load images and manipulate the images.

So being the experimental type I have started writing a new web viewer system that plugs into Conquest Dicom Server. The system is a small scale PACS web viewer system.

Basically how it works:
  • Flex application calls back end PHP scripts which connect to the database to show a work list.
  • The Flex application calls a PHP script which converts images to JPG files which are then loaded into the Flex application.
  • The Flex program then has some functions for basic things like brightness, contrast, flip, rotate and cine.

The system is still a work in progress as I am slowly learning the ins and outs of a new programming language and then still doing all the rest of my work which basically sees me bouncing back and forth between C#, PHP, Flex and Javascipt. Its enough to get anyones head in a spin as all these languages have slightly different syntaxes.

Anyways I expect that I should have a working prototype ready for upload onto sourceforge some time before the end of the year so keep your eyes open. I think this system is gonna be way better than my last attempt.

If anyone is interested in getting into Adobe Flex here are some links:

Friday, 12 September 2008

DICOM Sucks

DICOM really sucks! Ok there I got it out of my system!

The concept of a standard it that there is STANDARDISATION! The DICOM standard however seems to be one of the most complicated things on the face of the earth and for no good reason as far as I can see. The sole purpose of the DICOM standard is to confuse and annoy!

The idea of it all is pretty sound (make a standard and stick to it), but it seems as though every vendor decides that they only want to conform to a certian portion of the standard. They then write a massive un-readable document explaining how they conform to the standard. The system will then only communicate correctly with other systems when it feels like it!

If the TCP/IP was this daft then we would never have the internet and you would not be able to read this rant. The main reason for my anger is that I have modality worklist working on some of my CR systems, but some of the other systems that I need to setup such as CT, MRI, US etc are having problems connecting. If DICOM where indeed a standard then logic dictates that the system would work on all or on none! (Assuming that the basic DICOM configuration and TCP/IP settings are correct)

I beg and pray that one of these days a standard is finally met by all vendors and not just portions of a standard!

Friday, 18 July 2008

View Dicom files in Windows Explorer

MicroDicom Shell Extension allows you to view thumbnails of Dicom images in Windows explorer just like any other picture. It is a very nice neat application that seems to work pretty well.

I tested it on my Windows Vista Business SP1 machine and it worked well, even with JPEG Lossless encoded Dicom images.

I think this application could be useful to help find DICOM images on your computer.


Wednesday, 18 June 2008

iPhone, the new modality!

Wow! That is all that I can say! I saw this clip on Dr. Dalai's blog and I was blown away by MiMVista. It is a viewer application for the iPhone that allows you to view CT, MRI, etc.
I think this may just be the next killer app for radiology. As they say in the clip, imagine sitting with your patient showing them the images. The iPhone seems to be bringing a whole lot to the table for medical applications. I also liked the concept of the anatomy application that was shown in the first half of the clip.

Thursday, 22 May 2008

Conquest Server Digging in the Bin


I found an interesting quirk of Conquest Dicom server today while doing some house keeping. I deleted some images in the image directory and decided to re-initialise the database. I suddely noticed that Conquest was shuffeling through the recycle bin and pulling out all the images I had just deleted! (See image)

This seems to happen when you have the data directory (MAGDevice0=D:\) of Conquest Dicom Server set as the root of a drive. (In this instance D:\) to rectify the problem I created a new folder called DICOMDATA and pointed conquest to that directory to store its images. (MAGDevice0=D:\DICOMDATA\)

I would reccomend that you do not use the root of a disk as the place to store your Dicom images. Rather create a seperate folder in that directory for image storage. I have not verified that this happens on all operating systems yet, but the system I am testing this on is Windows Vista Business Edition 64bit, with MySQL as a DB Server.

Tuesday, 22 April 2008

Conquest Dicom Server on Windows Vista 64bit

OK after a huge battle, we finally have our 2.8TB disk installed and running. Just to let you know all the various options that we tried check this list out:
System Configuration:
  • 4 x 1TB Hard Disk Drives in RAID5 Array (2.8TB) for DICOM data
  • 1 x 180GB Hard Drive for operating system an applications
The things we tried:
  • Windows XP - XP Can't see a partition bigger than 1.8 TB
  • Windows Vista 32bit - Vista 32bit automatically partitions the drive into 2 partions. There is no option to make a single large partition greater than about 2TB.
  • Ubuntu Linux - I could not get the tools on Ubuntu to recognise the RAID array correctly. It could only get it to see about 700GB. If the disk was working I was going to use samba to share the disk and mount it as a network drive on the existing server.
  • Windows Vista 64bit - Works like a dream.
Conquest Dicom Server installed fine on the 64bit version of Windows Vista. I actually used the same process as describe in my previous post on how to install Conquest Dicom Server on Windows Vista with MySQL Community Edition.

ClearCanvas Workstation 1.1

ClearCanvas Workstation 1.1 has been released. It has some handy new features which I found quite useful. Now remember I am not a radiologist so I can't comment on all the image manipulation functionality, but I will try and get some feedback from one of our radiologists as soon as I can.

From my point of view I think the new version of the workstation brings some awesome new tools to the table. For one the ability to have reference lines in studies is a huge improvement and one that I know some of our radiologists require as a standard feature.

List of new features in ClearCanvas Workstation 1.1:
  • Reference lines
  • Synchronized stacking
  • Spatial locator
  • Elliptical ROI
  • Protractor
  • Multiframe image support

Some of the tools available (Elliptical ROI, Protractor)



Spacial Locator


Reference Lines

On the whole I would like to congratulate the ClearCanvas developers for their outstanding work. I think they are going to have an amazing application. The workstation is currently on a par with others such as K-PACS (Or even better), but I think with the rapid development cycle that we have seen so far as well as the availability of the source and an SDK this workstation will very soon be able to compete with the likes of Osirix. I hope to see some 3D capabilities in the future from this exciting project. Keep up the good work guys!

Monday, 14 April 2008

Toshiba Xario/Applio Print to Windows Printer

The Xario and Applio Ultrasound machines from Toshiba currently run on Windows 2000. You can get into the operating system via the maintenance menu. The button says something like "Open Windows Explorer". You can then browse to the control panel and install a printer.

This will allow you to send Ultrasound prints directly to a standard colour laser printer without having to use an expensive DICOM print converting application.

Tuesday, 4 March 2008

ClearCanvas Workstation 1.0


Well ClearCanvas Workstation is no longer a beta. I downloaded version 1.0. And I must say I am pretty impressed! They seem to have sorted out a lot of the speed issues I mentioned in my previous entry.
The system is still a little bit rough around the edges, but I expect that the ClearCanvas developers will polish out these in no time.
Some of the things that got to me a bit where:
  • You first have to download an image from the a DICOM server and then find it in your local queue before you can view it. It would be better if you could just click view and the system woul download and then display the image.
  • You cannot seem to access a Conquest server that is running the dbaseIII driver.
  • There is no option to mark studies status, i.e. read, viewed, etc.
Some of the things I like about the system:
  • It is a lot faster than the beta version I tried initially.
  • I have not managed to crash it just yet. I can crash any application :)
  • It works fine on Windows Vista.
  • The Subset of tools seems pretty good.
  • Nice and basic to setup and use.
I see there is also a DICOM server application available from ClearCanvas, I have not tested it yet, but it looks like it could be very usefull! I will give it a try in the near future and report back.

IQ-DICOMTest V2.7


I found IQ-DICOMTest today. Its a nice util for testing dicom associations, etc.
"iQ-DICOMTEST represents a set of tools for the purpose of testing and troubleshooting DICOM communications." Image Information Systems Ltd.
You can get your copy of this software from the Image information systems website. You will have to create an account on thier forum (But I am sure you already have if you have downloaded K-PACS).

Click here to get your copy of IQ-DICOMTest.

Friday, 29 February 2008

Using Mikrotik's The Dude to Monitor Dicom Modalities


The Dude from Mikrotik is a wonderful network administrator tool for monitoring almost anything to do with your network.

I was first introduced to it a few months back when we implemented a wireless wide area network in preparation for PACS. Since then The Dude has become an indispensable tool in my everyday work life.




The Dude is capable of many things, but my favorite features are:
  • Continuous Pings to check if devices are active
  • Service checking (i.e. http, ftp, etc.)
  • Link monitoring (The dude shows live network link usage!)
  • Graphing
  • Active alerting via email, pop-up, etc.
  • Server setup (I have setup The Dude on a central server and connect to it from the console only. This assists in monitoring the system even when my laptop is shutdown)
To date I have been using The Dude exclusively for monitoring our Wide Area Network, but today I decided to implement it to monitor some key dicom modalities and see if I could get it to report on the availability of the dicom service on the modality itself. These are my findings.

Step 1: Create New Network Map
I created a new network map so that my views are not too cluttered. I have one for my WAN view and I created a new one for DICOM modalities.
You can create a new map by double clicking on the "network maps" link in the menu tree and then clicking on the + icon.

Step 2: Add DICOM modality
I then added a dicom modality to the system. The machine I chose is a Conquest Dicom Server I have setup at one of my remote sites. To add the modality you can open up the network map and press the + and select device.
You can then type in the IP Address of the modality.

Step 3: Setup Ping Monitoring
You should now see the device in the network map.
You can now right click on it and select the services tab.
Click on the + button and select ping.
You can also add a notification on the notification tab.
You can setup the notification types in the notification link in the menu tree.
I setup a notification that emails myself and the other IT admins.

Step 4: Setup DICOM service monitoring
To add a service monitor for the DICOM service you need to do the following:
Open the settings tab for the device and go to services.
Click on the pus button, then click on the small ... icon on the right hand side of the probe drop-down list.
Click on the + button and give the new service a name like "conquest dicom".
Select "TCP" for the type and then in the Port section put in the DICOM port for your modality.
I then selected the connect only option.
Once this is done you can setup email notifications, etc. So that if the DICOM service goes down on your conquest server you will be notified by email.


Conclusion
The Dude is very useful for monitoring both your standard network infrastructure as well as your dicom modalities. I find it very useful to have as it notifies the instant there is a problem though-out the entire network. In fact I normally know there is a problem with a server or a network link before my users. I would recommend that if you have a lot of devices to monitor that you give Mikrotiks The Dude a try.

Tuesday, 8 January 2008

Conquest Dicom Server Web Interface - Work In Progress

I have been developing a web interface for Conquest Dicom Server for a couple of months now and I am about to run it live on real users in the next couple of weeks! The system is a basic web interface for external physicians to view general x-ray cases from their desktop computers. I am testing the system with Firefox 2, IE 7 and IE6 and everything seems to be going ok so far. There is some basic AJAX involved in the system so JavaScript is required as well as Flash for the Simple Viewer flash viewing system. I would however like to migrate the viewer to the flash based Stratos Viewer in the near future.

The system is effectively a mish mash of several applications all strung together with a bit of PHP scripting. The main applications I am using at the moment are as follows:

1.) DICOM Server - Conquest DICOM Server
2.) Database Server - MySQL
3.) Server Side Scripting - PHP
4.) Image conversion - dcmj2pnm.exe from dcmtk-3.5.4-win32-i386 toolkit
5.) Image Display - Simple Viewer (I am trying to get stratos viewer to work at the moment, but having some trouble)

In essence the system is relatively simple and works as follows:
1.) Images recieved by dicom server converted to JPEG using an export converter.
i.e. ExportConverter2 = "dcmj2pnm.exe +oj +Wm --scale-x-size 600 %f C:\inetpub\wwwroot\images\%i\%b.jpg"

2.) When the home page is opened the system looks for all cases done today in the dicom server MySQL database and displays the patients done on the given day.

3.) Some other PHP scripts create thumbnail images for a preview image to be displayed.

4.) When a series is selected the PHP script tries to convert the image to a JPG if it has not already been converted by the export script. It then generates the XML needed and passes it to the Simple Viewer flash component for display.

5.) The system also has a log file that logs certain information such as failed login attempts, images viewed by users, file conversion errors, etc.


Some Screenshots of the system in action
example work-list


Roll-over thumbnail preview


Image viewer


Search


Log file example

I am planning on making my system available in the near future, but I just need to work out some of the bugs and integrate the stratos viewer, or some other viewer software that will allow for some basic image manipulation by the client.

Monday, 7 January 2008

K-PACS v1.5

K-PACS version 1.5 has been released recently. It has some interesting improvements.
The new features include the following:

1.) Patient Level View
You can now view all the patients in a single pane as opposed to only having a study level view. This feature works both on the local database as well as on remote databases.







2.) Preview Thumbnails for local studies
The system now shows you a preview thumb of the series in the study. This feature however only appears to work on the local image database and not on remote studies.


3.) Built-in Burn to Disc Feature
K-Pacs now comes with its very own built in CD-Burning utility. It appears to work very well and even includes its own DICOM viewer.
I Did not manage to get the software to recognise the CD/DVD RW Drive of my Dell Latitude D820. So I created a CD project and burnt the files to a disc manually with the bundled software.
Edit: Got the CD Burning feature to work after a re-boot. It works like a dream.











4.) Status Icons
There are now status icons in the bottom right hand side of the K-PACS window which indicate available disk space on the workstation and also the status of the K-PACS server itself.

5.) Measuring and Annotations
Some new measuring and annotations have been added to the system as well.

I think this is a good step forward for K-PACS, but there is still quite a long way for them to go before they can compete with the likes of Osirix.
You can get your copy of K-PACS from www.k-pacs.net

Saturday, 8 December 2007

Conquest Dicom Server Custom Log File

How to setup your own custom Conquest server log file
I have setup my Conquest server with a logging system that effectively saves information to a CSV file every time images are sent or received by the machine.
I then also wrote a small bat script to archive the log files to prevent the log from becoming to large.

  1. open the dicom.ini file with a text editor like notepad or notepad++.
  2. At the end of the file add an export converter.
    You can do this as follows:
    ExportConverters = 1
    ExportConverter0 = append "%d,%f,%p,%m,%s,%b,%o,%u,%c,%i%n" to c:\conquest\logs\incoming_log.csv
This tells conquest to log all incoming dicom images to a csv log file.
The letters preceded by a % are variables that represent things such as the calling AE title et. You can find a list of these in the help file supplied with conquest.

I noticed that this was effective, but the log file would soon fill up, so I created a bat file that would copy the file to an archive folder so that the log file would not become too large and slow when opening it.

the contents of the bat script to copy and rename the file to an archive location are as follows:

@ECHO OFF
copy "C:\conquest\logs\incoming_log.csv" "C:\conquest\logs\archive\%Date:~6,4%.%Date:~3,2%.%Date:~0,2% incoming_log.csv"
del "C:\conquest\logs\incoming_log.csv"
echo "Date","File Name","File Path","Modality","Station Name","File base name","SOP Instance","Calling AE","CalledAE","patient ID" > C:\conquest\logs\incoming_log.csv
This script then also re-creates a blank log file and adds the column headings in the csv file to make viewing easier.
You can copy and paste the above code into notepad and save it as a bat file and run it via the task scheduler.

Hope this helps someone out there.