Showing posts with label PACS. Show all posts
Showing posts with label PACS. Show all posts

Monday, 20 December 2010

Kinect & Osirix

Check out this video I received. It shows Microsoft kinect being used to control Osirix. It looks like a great product and I expect that we will see a lot more similar interfaces showing up soon.
Thanks for sending me the link Steffen.

As they mention in the video the use of hands free controls has major benefits and allows doctors to prevent infection and does not tie them down to a keyboard or mouse.

I hope all the major PACS vendors are looking at this and making their own versions that integrate with their products as I think a lot of doctors are going to start demanding this type of technology for their theaters once they see what is possible.




Monday, 26 October 2009

Feedback: 1st African PACS & RIS Edu-conference

image

The 1st African PACS & RIS Edu-conference was a fantastic event. I think the organisers put together a great show and taught the local PACS & RIS community a great many things.

I am so glad to know that there are that many Southern African people out there going through the same issues that we are. It was a real eye opener to share in the experiences of both private practice and that of government, who share some issues, but on the whole have very different outlooks on the systems at large.

The formation of a local organisation to address PACS & RIS issues was raised. I think this will be a great asset to the local community as it will give us a platform to communicate, educate and drive the industry forward.

Well done to the event organisers, it was great to be a part of the event and thank you for teaching us so much.

http://www.pacsrisafrica.com

Friday, 6 March 2009

PACS and Hyper-V Server Virtualization?

Hyper-V is the Microsoft Server Virtualization product that comes standard with Windows 2008 Server. (There are a couple of other virtualization products, but Hyper-V is free with Windows 2008 server) I went to a presentation recently explaining Hyper-V, among other things. I have always though that server virtualization may be a good idea for a PACS implementation, but until recently I hadn't really given it too much thought. 

Server virtualization basically means that you create 1 or more virtual servers on a physical server. i.e. There is some software that does some fancy magic to make it possible to install multiple operating systems on your computer as though they are a complete system on its own.

The major benefit of server virtualization that I can see is the fact that the server itself is in effect a file now when it is Virtual. You can take a snapshot of the server and copy it off to a new location. In the event of a massive failure, all you need to do is copy the file back and you will have you server running as it was when you took the snapshot!

This is obviously fantastic if you consider that you can make backups of your entire server with the click of a button just before a software upgrade and then test to see how it goes. If you are feeling really clever you can even take the snapshot of your server and re-boot it on another computer and test the software upgrade away from the live environment!

Another fantastic feature of server virtualisation is that you can run almost any operating system as a virtual server! So you can have one Windows 2008 Box that has Windows 2003, Windows 2000 and even a flavour of linux running on it all at the same time!

Virtual machines can also be migrated to new hardware much more easily as the snapshot of the server can be coppied to a new higher spec machine, more resource allocated to it and then turn it on and BAM! Server upgraded!

The downside to virtualization technology is that if you have one physical server running several virtual machines, then if you loose the one physical server due to hardware failure, you loose all the virtual servers running on that hardware.
You can setup some advanced configurations that will automatically fail-over to another server, but eventually you need to consider your risk appetite and your budget.

But I think virtualization is definetly something to look at if you are getting a new PACS system.

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.

Thursday, 9 October 2008

10 TB Conquest Server

Finally our new Dell Server arrived! It has been quite a mission to set the whole thing up. All I can say is that there wher tons of boxes and lots of manuals to go through, but it was worth it. The Dell server and rack are amazing! Everything snaps into place and looks so neat and tidy. (Compared to our other cheap cabinets).

We have the following system now:

Dell PowerEdge 2950
  • Windows 2008 Server x64
  • 2 x 2GHz Quad Core Xeon, 4GB RAM
  • 6 Disks in RAID 5 for OS and DB
Dell PowerVualt MD3000
  • 15 x 1TB SATA HDD (RAID5 2x hot spares)
  • 10TB Usable Space
  • 2 x SAS Connectors
The Windows 2008 Server system seems to have taken the Conquest installation quite well. I have had no hicups yet. The software installed for was the following:
I have only encountered one setup issue at the moment and that is regarding the Windows 2008 and Dell Storage management software. It seems as though once again Windows will only recognise a certain amount of hard disk space for a single partition. The magic number in Windows 2008 64bit seems to be roughly 2TB. So I have had to make 6 partitions for the Dicom Data. I am a bit concerned how Conquest is going to handle this as I have never played with the MAGDevices functionality, but accoring to their forum it should work. 
Partitioning the disks and spanning the dicom data across multiple partitions is probably going to break the Conquest Web Viewer system as it can only look in one folder for images. I will have to take a look at this and make some modifications to the code to make it function better. I am also experimenting with ZIP functinoality allowing users to download a zip file containing all the DICOM images in a series to thier local machine via the web viewer interface.

I will post some more information once I have the system is live.

Wednesday, 8 October 2008

Credit Crunch + PACS = ??

I have been trying to keep track of the whole "credit crunch" story eminating from the US sub-prime loans fiasco and how it has been affecting global markets. I have been intreeged by the fact that many "High Risk" investments have been taking a hit, for instance the local curreny where I live has hit a 6 year low against the US dollar and other major international currencies.

Now I know that I am no financial wiz or that this is not a financial blog, but I am interested to see what the knock-on effect of the whole market turmoil is going to do to the PACS market.
The PACS world seems to be in a constant state of flux with bigger vendors buying up smaller ones, rumors of some suppliers selling off thier PACS divisions and all maner of patent lawsuites that have become the flavor of the week lately.

I imagine that the PACS market is going to have to take a long hard look at itself and make some major changes if the current market situation continues.

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.

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.

Thursday, 26 July 2007

Sage PACS RIS

Sage Software appears to have released a PACS/RIS/Billing System.
Intergy RIS/PACS
You can find out more here ....

http://sagehealth.com/wps/wcm/myconnect/sagehealth/www.sagehealth.com/products/radiology/


The System looks rather basic based on the flash demo shown. I think it may be a good solution for a smaller institution as it integrates all the primary functions of a Radiology System namely PACS, RIS and Billing, all in one.

Monday, 16 April 2007

Links to some PACS Reading

I found this site today Medicalimagingmag it seems to be a very useful site full of information for people interested in PACS.
I was particularly interested in the interested in the following articles.

Friday, 13 April 2007

Critical Importance of Integration in PACS

The importance of integrating a PACS, RIS and back-office system in a Radiology department can not be understated. The benefits of having these three systems tightly integrated will make major differences to the way the business performs. The work flow of a PACS system brings major benefits to the practice and can lead to massive improvements in the turn-around time of patients. This increase in turn around times however is useless unless the back-office systems can keep up and provide the billing functions in a timely and efficient manner. Without integrated systems this becomes a bottleneck in the work flow.

Consolidating Systems
I am a firm believer in consolidating computer systems so they are more manageable in terms of security, maintenance and backup procedures. Systems that are separate and architecturally different provide problems because these systems become difficult to manage due to the fact that the computer administrators need a larger skill set and more time to manage and secure these different systems. One should stick to a standard in computing be it a standard manufacture, Operating System, Database Server, Etc.

Wednesday, 11 April 2007

LEAN and Radiology

I recently came across an article on how LEAN methodologies used by manufacturing companies can be implemented using ERP systems and began to note similarities as to how the these LEAN methodologies can be used to make a Radiology department more efficient. You can find the article from SYSPRO here.

The LEAN methodology in its most basic form says do more with less. I believe this is the objective of any radiology department. We want to be able to do more work with less effort, equipment, expense and staff. I believe that this document can be used as a good comparison as to how other industries have modernised their processes and systems to allow them to become more efficient and can thus be used as a justification for getting a PACS system which will allow the practice to do more work with less.

Monday, 22 January 2007

Some DICOM Tools

I have been testing some DICOM programs. Below is a list of them as well as my experiences with them. Please note that there are many applications out there, but I was specifically looking for some of the free ones to do some lab testing. I was specifically looking for a small DICOM server and a viewer with a small foot print while still having reasonable capabilities.

Conquest Server
DICOM server application for receiving, storing and querying DICOM images. The software is a little tricky to install. I am planning on using this as a temporary setup for a Mini PACS system to allow us to store and query images from some of our digital modalities, i.e. panorex, CT, MR, Ultrasound, etc.

K-PACS
K-PACS is a great solution for a basic workstation that needs, store, query/retrieve and view capabilities. It is very easy to install and configure. At the moment we set a K-PACS workstation up on an old workstation for our Radio Isotopes department to view images remotely from a reporting workstation. The Siemens eCAM was pretty easy to configure to send images. The only drawback of the K-PACS workstation is that the printing is not quite as good as it could be. The radioisotopes doctor wants to view images in inverted colour (i.e. black on white) . The system allows you to invert the colours, but when it comes time to print, it reverts back to the original state of the image.

HIPAX Dicom Print Server
This is a nice system to allow DICOM images to be printed from a modality to a windows printer. We currently have setup a small HIPAX print server which allows our doctors to print DICOM images directly to a windows colour laser printer.
  • Download the Evaluation Version Here
Some other useful tools and links to DICOM applications:

Monday, 8 January 2007

The remote sites debate

PACS systems are typically housed in hospital on a LAN system with the odd remote "Tele Radiology Site" that sends images to a central server for analysis by a in hospital doctor. The situation my practice is faced with is slightly different. We have 1 main site and 6 remote sites. Of these 6 remote sites 2 are of a "Tele Radiology" size and the others require a little more as they are hospitals too. Now I know in more developed countries you can get data lines that will allow sites to link together at a relatively high speed, unfortunately our practice is not in one of these countries. The fastest fixed line internet service is 1024 kbps which is ADSL (Asynchronous) so it has an uplink speed of only 256 kbps, which will mean that the links will effictivly be 256kbps links. The service is also capped at 3GB. You can obviously buy a larger cap and such, but the service is just not adequate for our needs as they are sold as internet access solutions and not WAN links.

Now the other offerings from our fixed line operators are Diginet which at speeds of anything over 1Mbps are so expensive that it is crippling there is not much else on offer. Our other avenue of research has led us to a wireless solution, but this is not legal here. We sit now in a situation where we effectively have to have multiple smaller PACS installations on remote sites which sync with a main archive at our main branch.

The entire aim of implementing a PACS system for our practice is to try and allow for workload distribution throughout the sites by allowing all Radiologists to view a single work list and thereby having all our Radiologists working at maximum capacity or at lease spreading the workload so some are not sitting idle at a remote site. The mini PACS site solution effectivly destroys this whole notion as it would take a massive amount of time to pull images across a WAN line running at up to 1Mbps.

Is anyone out there aware of a solution to such a situation that would allow us to have a bandwidth friendly system. I know that the Philips iSite has a proprietary solution called iSyntax, but I believe that this solution is still aimed at alleviating traffic on a LAN link of 10Mbps, which is probably 10 times more than the bandwidth than we will be able to get!

Are there any WAN compression tools, QOS or any other services out there that others have implemented with success on a low bandwidth medium?

Wednesday, 15 November 2006

PACS - The Bad and Ugly

PACS is like anything in the world, it has Pros and it has Cons. I will be focusing on some of the negatives in PACS in this post. I will focus specifically on some of the hidden costs that one may not be aware of in the beginning.

The Network Problems
PACS systems are essentially a communication and distribution system. Networking is the base of a good PACS system. The system requires a good network to get the images around in a timely fashion to both Radiologists and external doctors. With this in mind you need to consider the following before implementing a PACS system.
  • The Local Area Network (LAN)
  • The Wide Area Network (WAN)
  • The Hospital Network
  • And Finally Internet Connectivity
The Local Area Network
A local area network (LAN) is defined as "a computer network covering a local area, like a home, office or small group of buildings such as a college." [from wikipedia.com]. This is basically the computer network within the Radiology department responsible for distributing images between various modalities, the PACS archive, the radiologist workstation, etc. It is critical that you have a network with quality hardware to handle the volumes of information that will be generated by the digital system. I suggest having a Gigabit network when ever possible and at the very least a 100Mbps network.

The Wide Area Network
A WAN is a network used to connect local area networks (LANs) together, so that users and computers in one location can communicate with users and computers in other locations. [from wikipedia.com]. If you have multiple sites and you wish to connect them all to a central PACS Archive you will need to re-evaluate your WAN to accommodate the increased traffic. WAN's are typically considered to be very costly and this could considerably alter your budget. You will need to consult with your PACS vendor on their requirements for a WAN based on the modalities and volumes of studies you will be performing at remote sites.

The Hospital Network
The hospital network can also be a blind spot when it comes to PACS. One needs to consider how images are going to be distributed within the hospital to the various doctors, wards, etc. Negotiations with the hospital on these items is essential as their network will be responsible for delivering images to your clients and if their network is not up to certain standards your services will be viewed in a bad light.

Internet Connectivity
Internet connectivity for distribution of images via a web server is also something else to consider. Exposing your network to the internet without proper security measures such as a decent firewall or other security measures could open you up to security vulnerabilities that could result confidential information being compromised. Internet connectivity bandwidth also needs to be capable of coping with the information exchange between external doctors and your web server.

The DICOM Problem
The other problem I have picked up on is that the DICOM compliance of modalities needs to be addressed. Modalities may need to be upgraded to be capable of DICOM worklist, DICOM send, DICOM receive, etc. This also has relatively big cost implications on a PACS implementation.

All of the above mentioned items are best addressed ahead of time so that key decision makers in the organisations are aware of the cost implications and so that they can budget for them accordingly.

Tuesday, 14 November 2006

The beginning - PACS the good.

I though I should start off with a brief look at why PACS is important to Radiology.
Radiology seems to have several limiting factors:
  1. Cost of Radiologists time
  2. Space available from hospital
  3. Film and Development costs
  4. Staff numbers
I believe that PACS will help address these issues in the following ways:
  1. Cost of Radiologists
    With PACS a lot of the mundane work currently placed on the Radiologist is removed. For instance there is no more hanging up the film, hand writing reports (if you still do this), constant interruptions from radiographers coming and going with film, manually looking up patient details in a patient information system, etc. These tasks may seem to be insignificant, but over a period of time they add up to a considerable waste to the most highly paid individuals in the process. These unnecessary tasks can be eliminated in a digital environment by making allowing instant access to imaging and patient information from one unified intuitive interface. This would have the net effect of making Radiologists more productive and theoretically allow a Radiology department to have less Radiologists, or to increase the capacity of the current Radiologists.
  2. Space available in Hospital
    This one is debatable, but with digital equipment your throughput on a machine is supposed to be increased dramatically. A DR system is supposed do the work of up to 3 analog rooms. This can allow considerable space savings. However on the flip side with PACS you will probably need a dedicated server room to house your PACS servers, so this might be more of a one for one pay off.
  3. Film development costs
    The cost of film development is almost eliminated by implementing PACS as you now only distribute images in digital format. This however is once again a payoff as the cost of implementing a DR system and or CR system will ultimately eliminate any savings.
  4. Staff numbers
    The staffing aspect of implementing a PACS system is often one that is very sensitive. I am a firm believer that the dark room staff in an institution will not be eliminated when PACS is introduced. I believe that these staff members can be put to use operating the CR systems and other administrative tasks. However implementing PACS should allow you to reduce staff in future.
There are many other benefits to PACS that I will try an summarize below:
  • Ability to distribute images and reports instantly to external doctors, hospital wards, ER and other doctors.
  • Allows for sharing workload of Radiologists by having a single centralized work list.
  • Minimize resets by allowing software manipulation of images. (i.e. Contrast, Brightness, software shutters, etc.)
  • Instant access to past studies.
  • Speech recognition technology.
  • Enhanced security.
  • Digitization of most paper documentation. (i.e. referral note)
My next post will take a look at some of the darker side of PACS and I hope to investigate some of the bad and ugly when it comes to PACS.