Monthly Archives: March 2010

If I Were a Doctor … EMR

If I Were a Doctor … EMR

Several doctors I know have asked me for advice on buying an Electronic Medical Records (EMR) system. Here’s my advice:

Start with a network of other doctors in your specialty. You don’t have the time to do all the research and evaluate all the options on your own. You will also need that network after you purchase the system. An ideal network for this is probably between three and six doctors. If a doctor you know has an EMR that she likes, start there and then check the rest of my recommendations.

A network will give you better points of view and more resources to make the buying decision. If a vendor knows that a sale to one will probably lead to a sale to several they will work harder at assuring you that the system meets your needs. They will also be more willing to consider changes or enhancements if that will lead to multiple sales.

After the sale, there will be issues. If several of you have the same issue, you are more likely to get prompt vendor attention. If the issue can be solved by training, your staff can work with staff from the offices of the other doctors to share what they know. For this reason, I would bring the person in my office who has the best attitude toward computers with me to some of your network meetings and suggest that others do the same. Computers can make people feel very stupid. It helps if you can call someone you know for help or take a call to give help.

Get the service via the Internet. You will have to have computers in your office but data will be stored off-site, problems can be addressed remotely, and system will be kept current. A vendor will provide redundancy (backups), secure storage, and should have better general security than on a stand-alone system. HIPAA and other regulations are applicable.

Insist that all programs are written in one of a number of common programming languages and data is stored and accessed using SQL. If you need to migrate to a new system – EMRs are still in their infancy and change will happen – it will be easier if everything uses standard parts and solutions.

Listen for flexibility when the vendor talks about the system. There are new products coming, think of the iPad. Google Health and Microsoft Health Vault are adding features and functions. Your patients are using the Internet to make better use of their time; they will expect you to support that. Simple example, have the capability to post your reports on their personal health records so they can share them with other doctors so they don’t have to take the same test over and over. Sometimes this will be with doctors who do not even have systems and you probably don’t know. Today, that takes several phone calls and a FAX or two. Way too time consuming. They also own the data and you need to help them use it responsibly.

Expect online help to come with the system. Your staff should be able to learn to use the system with a combination of basic computer skills plus online documents on the system. Not the best way but you can’t send every new-hire off to a class and routines that are not used get forgotten. Example: Change a patient’s name when they get married so the old and new records are continuous? Add a new doctor to the practice? Change a staff member’s password?

Have one doctor’s office install first and check it out. With orders waiting in the wings they will get better service and all of you will get to watch the system and the vendor in action. Send the person in your office with the best attitude toward computers to sit in on some of the training sessions and to get some practice. Get the administrative parts of the system stable in each office before the doctor’s in that office start to use the system. It is easier to fix administrative records and staff downtime is less expensive than doctor time.

No guarantee of success or satisfaction, but that is always true with computer systems. These steps will improve your odds of getting a system you and your staff will like and find useful.

Advertisements