JS PACS

...keeping you connected to your images.

  • Increase font size
  • Default font size
  • Decrease font size
jspacs.com

Site Slowness

E-mail Print PDF

As we get the new format of our website off the ground, I have been noticing some significant slowness on the JS PACS website.  I have also heard others state that they feel it is a bit slow as well.  

I am currently trying to track down the source of the slowness and hope that while I work to resolve the isses that you continue to use the site and contribute to the forum.

Thank you for your patience and continued use of the JS PACS webiste.

Regards, 

John 



Add this page to your favorite Social Bookmarking websites
Reddit! Del.icio.us! Mixx! Free and Open Source Software News Google! Live! Facebook! StumbleUpon! Yahoo! Free Joomla PHP extensions, software, information and tutorials.
Last Updated on Monday, 09 March 2009 21:32
 

Codonics Integrity - A Review

E-mail Print PDF

 

Today I had the opportunity to demo the Codonics Integrity CD importing device.   If you haven't seen this device, you can see information on it at the vendor site here.

 It is simply a device that looks similar to a Mac Mini if you are familiar with that particular Apple product.  There is no keyboard, Mouse or monitor.  The operating system and system/DICOM configuration files are  kept on a thumb drive that plugs into the back of the integrity.  The box itself is nothing more than a CD/DVD reader and an 80GB hard drive.

 The beauty of this system is that it can be put anywhere and all a user has to do is stick a DICOM CD/DVD in the drive and after it reads it and stores the images locally, it spits the disc back out for the user to return to the patient. The file-room staff can then navigate to the device via a web browser and reconcile those imported studies to the modality worklist or make manual patient edits as needed and then pushing those studies to PACS.

 The device works wonderfully from a clinical perspective offering ease of use and speed. It is in some of the IT aspects of the device where I feel it falls short.  

 The device does allow you to configure it for DHCP, a nice change in the DICOM world of static TCP/IP configurations and you can join the device to your organizations domain and use DNS for browsing to the device.  Where I feel the device comes up short is in the user database.  Some may think this is trivial but given the fact that it is a fairly advanced device, it would certainly be beneficial for Active Directory authentication to be a feature of this system.  Maintinating disparate user databases on DICOM equipment can be time consuming and tedious so Codonics should consider developing that in a future release.

 If you have encountered the Codonics Integrity, have questions about it or would like to post your thoughts about it, visit the discussion forum and let us know.

I will close by saying this is a review and nothing more than that. I have yet to purchase this product or encourage/discourage others to purchase it, I just wanted to share my thoughts after being able to demo the device today.



Add this page to your favorite Social Bookmarking websites
Reddit! Del.icio.us! Mixx! Free and Open Source Software News Google! Live! Facebook! StumbleUpon! Yahoo! Free Joomla PHP extensions, software, information and tutorials.
Last Updated on Wednesday, 22 April 2009 19:47
 

Workstation Management: Build Your Own Workstations

E-mail Print PDF

The day of the vendor provided workstation is coming to an end.  For so long we have always heard that we have to purchase our PACS workstations pre-built and pre-configured.  Well, I think the time is upon us here it is time to take control of our workstations.  Your organization can gain a lot by moving PACS workstation development in house.  You can save money, standardize workstation build and utilize your organizations software such as antivirus and patch management.

 

I am currently in the process of building a Centricity 1000 workstation form scratch and want to say that it is not the mysterious process that these vendors will have you believe.  We simply purchased a license, obtained the software and purchased recommended hardware.  In fact, we purchased a workstation well over the minimum specifications so we know we’ll get great performance out of it.

 

The most arduous process of building this workstation so far consisted of two issues, the first one was getting XP installed on the HP workstation (see the JS PACS Article on PACS Workstation troubleshooting) and the other was getting the license.  The license acquisition wasn’t difficult, just took some time getting an account on the GE licensing system and the registering the Centricity serial number that I had received in order to generate the license.

 

With the workstation up and running and the license file in hand, it was rather trivial to install the cardiology software.  I have gotten it all installed and configured but I haven’t given it the true test of sending DICOM images to the workstation.  I am not that worried about that portion of the testing however because from this point, it is just a tweaking of the settings.

 

The most important aspect of this process for me was a re-affirmation of the fact that an organization really can be successful in building its own workstations and software only solutions can be a viable part of the strategy to maintain workstations and keep them all refreshed.  The biggest advantage to purchasing, building and maintaining your own workstations is that you can shop for the best prices, standardize your workstations with regards to hardware and align the software to your organizations overall strategy (virus protection etc.).  

 

To comment on this article or let the JS PACS community know how you manage your workstations, visit the Discussion Forum.



Add this page to your favorite Social Bookmarking websites
Reddit! Del.icio.us! Mixx! Free and Open Source Software News Google! Live! Facebook! StumbleUpon! Yahoo! Free Joomla PHP extensions, software, information and tutorials.
Last Updated on Wednesday, 13 May 2009 09:04
 

PACS Troubleshooting Tips: Installing Windows XP on the HP xw series workstations.

E-mail Print PDF

This troubleshooting tip relates to rebuilding PACS workstations on the HP xw series platforms.  A lot of PACS workstations these days are running on this particular platform, many being the HP xw 4300 or xw8600.  There are many models in the series but their price and performance have been very attractive and are one of our preferred platforms.

This issue doesn’t occur all the time but there are some of those workstations that hit you with the dreaded BSOD (Blue Screen of Death with an error of 0x0000000007B – which is a device inaccessible error) when trying to install Windows XP Pro from the install disk.

The particular issue is related to the onboard RAID controller that some of these devices come with or the lack of LSI drivers for the hard drive controller.  Either will cause the Windows install to fail but here are some steps to take to get through that issue.

First, if you get the BSOD on windows install, check the BIOS and under ‘Storage Options’, disable the RAID controller, setting it to IDE Independent.  This will allow the windows installer to see the boot sector of the drive and prevent the install from failing.

If you still get the error, you may need to add the LSI drivers during the Windows install.  There are two ways to do this.  First, download the correct LSI drivers for your model from the HP website and extract those drivers onto a workstation you have access to.   You can then put those onto a floppy drive and during the windows install; there is a point where you will see the message “Press F6 to install third party SCSI drivers” at the bottom of the screen.  When you see this, press F6 and then you will be presented with a section that allows you to load those drivers into the install process.  Given that not too many workstations ship with floppy drives these days, the second method might be a much better solution.

That second solution involves created a new install disk that that contains those LSI drivers.  To do this, there is a great FREE product called nLite that will allow you to do this.  This software can be downloaded at http://www.nliteos.com/ .   There is good documentation on that site so I won’t go into the details of using that software but suffice it to say that this tool allows you to rebuild your install disc and include the drivers you need (such as the LSI drivers).  As a side note, there are a lot of other things you can add to the install disk such as service packs, additional programs, registry edits etc, that will all be included in the install. 

Once you have the disk built, pop it in your CD drive, fire up the workstation and the install should go smoothly.  

If you have any related experiences install Windows XP Pro onto the HP xw series workstations, post them in the JSPACS Forum - PACS Troubleshooting section and let the community know how you solved those issues.



Add this page to your favorite Social Bookmarking websites
Reddit! Del.icio.us! Mixx! Free and Open Source Software News Google! Live! Facebook! StumbleUpon! Yahoo! Free Joomla PHP extensions, software, information and tutorials.
 

Government, Open source and Healthcare IT. Is it a good fit?

E-mail Print PDF

The government recently released open source software that is designed to allow federal agencies and private organizations to transfer healthcare information between their systems.

I am a fan of open source, but have some initial concerns about the government running various aspects of our proposed national healthcare record on open source software.

If the software is going to be open source, I fear that it will be more difficult to protect the healthcare information that is transferred utilizing this system.  More people would have access to the software or to create hooks into the software for various purposes.  Additionally, could the resources needed to manage opens source projects like this become more expensive than privately developed software that was developed off of a government contract.  Remember, open source software has its hidden costs in the specialized people needed to manage it.

On the other hand, open source software certainly offers flexibility and ingenuity as there can be many people working on various aspects of the system, designing robust and customized solutions for almost any scenario.

Again, I am a fan of open source software, but without all the details yet, it is hard to know if open source is really the right choice for the government.  Regardless, it will be interesting to see how this develops in the next year or two.

What are your thoughts?

 



Add this page to your favorite Social Bookmarking websites
Reddit! Del.icio.us! Mixx! Free and Open Source Software News Google! Live! Facebook! StumbleUpon! Yahoo! Free Joomla PHP extensions, software, information and tutorials.
Last Updated on Wednesday, 27 May 2009 11:29
 
  • «
  •  Start 
  •  Prev 
  •  1 
  •  2 
  •  3 
  •  4 
  •  5 
  •  6 
  •  Next 
  •  End 
  • »


Page 1 of 6

JS PACS Login

There is a lot of content that can't be seen unless you login!

Currently in Chat

No users online