Jeff Rasmussen’s Healthcare IT Blog

August 9, 2006

Medical Software Problems

Filed under: Healthcare — jrasmussen0 @ 4:06 pm

Here is an interesting discussion about some problems with Medical Software. Unfortunately, this just begins to scratch the surface. I have been using and managing medical software for 5 years and I am amazed at how poorly a vendor can treat a customer once the contract is signed.

Some doctors who use Dr. Notes’ electronic medical records software say they have been denied access to the program and their patients’ medical records because they refused to pay increased technical support fees.

Multiple doctors cut off from records by Dr. Notes – South Florida Business Journal:

Fortunately, the situation isn’t entirely bleak. New online communities are developing to build and market free software solutions. LinuxMedNews is a regularly updated online forum for discussing industry news. GPLMedicine is a similar site maintained by Fred Trotter, project manager for the Free software ClearHealth management system. A project by Canada’s McMaster University, OSCAR, became the first IT system certified by OntarioMD.

Although these don’t have the name recognition among the medical community of commercial ventures such as Dr. Notes, they’re available for testing and implementation—free of charge and usage restrictions—today.

If you are a doctor or other healthcare provider, you owe it to yourself and your patients to take a look at these forums and applications. At the worst, you’ll find them uninteresting and unuseful. However, you could also find ways to protect your patients’ and your own best interests—all while saving money.

Your data or your life | Free Software Magazine

The Problem

Too many unique software packages and too few dollars for development.

If you look at it, the real value that a medical facility gives is the doctor’s expertise. Sure there is lots of tools that a doctor needs to be effective but a doctor can still make good decisions without the fanciest equipment in the world. If you believe as I do, then everything else is just an expense to maximize the doctor’s dollar. That means that there is less money to spend on software. At a conference a keynote speaker told us that medical facilities spend the lowest per revenue dollar on IT (IIRC 5% for medical and 10% for banking)

Medical facilities need multiple software packages to do very specialized and unique processes even for similar departments. For example, we use one software package to schedule radiology (Radiology Information System), one system to schedule clinic visits, and another to schedule patients that stay overnight. The reason a hospital needs 3 systems is because each system is better at managing it’s department than a general scheduler. I haven’t even covered the transcription department, the billing department, and the medical records department. I’m sure I’m missing some but you should get the idea.

When a medical facility shops for vendors usually they are lucky to find 2 competitors in a marketplace. Sure there may be many small boxed software but usually you find one very strong industry leader and a weak second place competitor. That vendor that you pick may be the best in the industry but since the other one is still using an abacus for calculations, the medical facility feels over a barrel.

The main thing I wanted to say was the medical field needs to start embracing open standards and open source software. It is too expensive for medical facilities to ignore. Medical facilities are also very keen on working with their competitors. We don’t have a problem sharing information between other sites as long as they are not across the street stealing patients.

I believe that if HL7 had a BSD style license for their standard and maintained a slow backwards compatibility, interfaces between applications would drop to under $1,000 from the $10,000 we see today.  I’m usually a GPL guy but something as low level as HL7 you probably need the proprietary software guys and the open source software guys to come up with a standard.

technorati tags:, , ,

June 9, 2006

EPIC Printing

Filed under: Healthcare — jrasmussen0 @ 10:20 am

We are in the midst of implementing our Wave 2 of EPIC and ran into a doozie problem.  The Zebra label printer driver for an LP28844-Z that EPIC required is causing our print spooler service on Windows 2003 to crash intermittently.

After calling Microsoft and determining that the cause was specifically from the Zebra driver, we contacted Zebra.  They are aware of some customers getting this error and said that the newest driver fixes the issue. Zebra Universal Driver 5.5.7.17

Now EPIC probably put a few months of coding behind the creation of our labels and doesn’t seem to want to allow us to upgrade to the new driver unless we can crash the print spooler device on command.

The difficult part in this vendor gymnastics, is that for 8 days, our patients have had slower service because the printed labels are taking longer than 1 minute to print or not printing at all.

What surprises me is that I could have almost anticipated the problem before we went live.  We spent the better part of a month creating 3 methods for printing from EPIC.  The printing system is too complicated with too many moving parts.  Here is an example of one method:  EPIC sends a job from unix to a Windows load-balanced pair of servers (EPIC print server) which then has to authenticate and forward the job to a Windows print server.  This happens to be the method that is experiencing the crashing print spooler service.  The other methods are printing plain text directly to the print device from unix or printing to a locally defined printer of the connected client.  Of course, we are implementing a Citrix environment which adds another layer of complexity.

All testing prior to go-live was successful to appearances.  However, it seemed to have too many minor issues that had to be fixed.  After our first tests, we had 50% failure of printers.

technorati tags:, ,

May 23, 2006

Compare RIS and Ghost

Filed under: Healthcare — jrasmussen0 @ 11:48 am

RIS vs Ghost – Sell me on which one – Topic Ars OpenForum

We used to use Ghost and now have switched over to RIS.  The best part is the ability to set up a computer with admin credentials in 5 minutes and walk away.  The user can then log onto the machine in approximately 20 minutes because it is part of the Domain.

Biggest hangups with RIS:

  1. There are 6 Hals, so there are a maximum of 6 different images that need to be created (depending on your environment).  For us, we had to create 3 different images.
  2. The other big hangup for RIS is trying to use a ghosted machine to create the image.  You are much better off recreating the image entirely on RIS.   I had to manually hack what HAL was used and I’m not sure if I did it correctly.

Biggest benefits with RIS:

  1. All images are located on a network share.  You can easily add or delete files from the image.
  2. Setting up an image is only 5 minutes of work, then you can walk away. 

Mediawiki in the Workplace

Filed under: Healthcare — jrasmussen0 @ 11:34 am

NewsForge | Putting MediaWiki to use in an organization

I installed a mediawiki server for our IT department documentation.  After showing a couple people the web pages, they commented immediately on the lack of security.  I thought that security was unessesary since all changes could be linked to an IP address and the original content couldn’t be changed but I think everybody would have had a better feeling if there was security already installed. 

 

technorati tags:

Older Posts »

Blog at WordPress.com.