Monday, 20 December 2010
Kinect & Osirix
Monday, 26 October 2009
Feedback: 1st African PACS & RIS Edu-conference
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.
Friday, 6 March 2009
PACS and Hyper-V Server Virtualization?
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.
- http://www.iq-view.com/forum/viewtopic.php?f=33&t=607
- http://www.image-systems.biz/forum/viewtopic.php?f=33&t=1434&p=4315
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:
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
Thursday, 9 October 2008
10 TB Conquest Server
- Windows 2008 Server x64
- 2 x 2GHz Quad Core Xeon, 4GB RAM
- 6 Disks in RAID 5 for OS and DB
- 15 x 1TB SATA HDD (RAID5 2x hot spares)
- 10TB Usable Space
- 2 x SAS Connectors
- Conquest Server 1.4.14 - Dicom Server
- WAMP server 2.0c - Database and Web Server
- MySQL GUI Tools - Database Management
- UltraVNC 1.0.4 RC17 - Remote access
- Conquest Webview A1 - Dicom Web Viewer
Wednesday, 8 October 2008
Credit Crunch + PACS = ??
Wednesday, 18 June 2008
iPhone, the new modality!
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
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

Roll-over thumbnail preview

Image viewer

Search

Log file example
Thursday, 26 July 2007
Sage PACS RIS
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 was particularly interested in the interested in the following articles.
Friday, 13 April 2007
Critical Importance of Integration in PACS
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
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
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.
- Get Conquest Server Here
- Link to Download MSDE database server.
- Limitations of MSDE.
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.
- Get K-PACS Here
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
- PACSone - Opensource PACS server. (MySQL, Apache, PHP)
- Some DICOM information and links to software - A very handy page!
- ezDICOM - A Basic DICOM viewer application. (limited features)
Monday, 8 January 2007
The remote sites debate
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
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
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.
Radiology seems to have several limiting factors:
- Cost of Radiologists time
- Space available from hospital
- Film and Development costs
- Staff numbers
- 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. - 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. - 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. - 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.
- 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)
