Free EMR Newsletter Want to receive the latest news on EMR, Meaningful Use, ARRA and Healthcare IT sent straight to your email? Join thousands of healthcare pros who subscribe to EMR and HIPAA for FREE!!

Common EHR Implementation Issue – EMR Upgrade Problems

Posted on September 29, 2011 I Written By

John Lynn is the Founder of the blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of and John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

I’m really excited that this Common EHR implementation issues series has been so popular. If you missed it, you can see the previous posts in the series: Unexpected EHR Expenses, EHR Performance Issues, a little follow up to avoiding the EHR performance issues altogether, and inadequate EHR templates.

This weeks common EHR implementation issue is: EMR Upgrade Problems

I’d like to categorize this EHR implementation issue into two areas. One is upgrading to an EHR from an old legacy EHR and/or PMS. The second is upgrading your existing EHR that’s just outdated. I’ll take them in reverse order.

Upgrade of Existing Outdated EHR
In this world of your web browser and operating system auto updating at regular intervals it’s sometimes hard to remember that not all software does that. In fact, it turns out that most software doesn’t auto update (often for good reason). Of course, this problem doesn’t apply to a SaaS based EHR software since those updates are applied whether you like it or not. The nice part is that the SaaS EHR updates appear to the user to just happen automatically with little to no intervention on their part. Of course, we’ll save what happens when a SaaS EHR update causes you problems for another post. In the client server world of EHR (or hybrid EHR as some like to call themselves when they’re web based on an in house server) you will have to deal with updating your EHR.

I think with rare exception, it’s a huge mistake to not keep your EHR software up to date (goes for most other software as well). I’m not suggesting that even client server software should auto update. Considering the deployment and upgrade model of most EHR software, it’s almost essential to review the new feature list before doing an update to ensure that the update won’t cause you unnecessary heartache. Understanding the changes that will happen with the EHR Upgrade will let you warn your users about it so that they don’t come running into your office after the upgrade wondering why their favorite feature was changed.

What’s the problem with not upgrading? Many might just think that they don’t need to update their EHR software since they don’t want/need the extra features that are part of the upgrade. This is a bad strategy for a couple reasons. First, there are often security fixes that are part of the EHR upgrade that you’ll be missing out on if you don’t upgrade. Second, a bunch of relatively minor updates is much better on a clinic than one massive one that requires a ton of change. Third, when a future update comes that has a feature you do want, it’s not always pretty to go through multiple upgrades at the same time. Fourth, try calling the EHR support when you’re on an old version. Most of the time they’re going to say you need to upgrade for them to appropriately support you.

One other suggestion on EMR Upgrades now that I’ve supported the idea of upgrading. Just because I suggest you upgrade to the latest version of your EHR, doesn’t mean you have to be the beta tester for the company. Do the upgrade early in the process, but not necessarily so early that you’re going to be the bug tester for the company.

Upgrading an EHR from a Legacy EHR or PMS
This situation happens most often when either a clinic decides to switch from their old hasn’t been updated legacy PMS (which might include some basic EHR features) or when a clinic decides to move off their existing EHR to a new one.

Upgrading from a legacy PMS could easily be a whole series of blog posts. Suffice it to say that the biggest challenge with the upgrade from the old legacy PMS system is often getting the data out of it. Some legacy PMS systems don’t provide that data willing. In fact, many will even charge you to get access to it. They’ve basically lost you as a customers, so they’re trying to maximize whatever revenue they can get. It’s not pretty.

Even if you can get access to the data, there’s often a lot of data manipulation that will have to occur. A common problem that’s related to this is whether you even want to get the data out of the old PMS. Far too often, the data in the old legacy system has so much junk in it, that it’s worth considering the option of starting from scratch. It’s not pretty to upload inconsistent and ugly data from a legacy system into your nice, new EHR software.

Switching from one EHR software to another is becoming more and more common. In 2-3 years I believe we’re going to see an amazing influx of EHR software switches. It will be the topic du jour. We’re already starting to see it in a number of situations: an EHR that isn’t certified, an EHR that the doctor hates, an EHR that’s gone under, an EHR that’s sold to another company, etc.

The biggest problem right now with switching EHR software is that there’s no standard for the data to be exported and imported into a new EHR company. Some of you might remember my post asking EHR vendors to consider the value of EHR data liberation. In it I describe why not only is it the right ethical thing to do, but it also can make a lot of business sense to do so. Sadly, I’ve only really seen one EHR software that has embraced the concept of really liberating the data in their EHR.

I’d love to support a movement from EHR vendors that embrace the concept of EMR data liberation. I imagine most are too afraid of giving their users an easy option to leave their EHR. It’s too bad EHR vendors are so focused on protecting their business instead of focusing everything they do on the customer experience, but I digress.

Considering the above described state of EHR data export, you can see why moving to an EHR is such an issue. It’s worth mentioning this topic before you even select an EHR. Before purchasing the EHR, ask the question, What if this EHR is terrible and I want to switch? This is water under a bridge if you’re already in a compromising position under contract with an EHR you don’t like.

Unfortunately, I don’t really have very many great suggestions for those in this position. Just some words of comfort. First, switching EHR software can actually be easier than implementing an EHR in the first place. You already have the computers and IT infrastructure. Plus, for some reason second EHR implementations have a much higher success and satisfaction rate from what I’ve seen. Second, while it’s a bitter bullet to bite, everyone that I know that’s done it wishes they’d done it earlier. Although, don’t rush into another EHR just because. Take your time to select an EHR properly if you’re going to switch, but don’t be afraid to switch based on what economists call sunk costs. Third, this is one case where it’s often good to hire someone who’s done these type of EHR switching before. They can be a big help.

Common EHR Implementation Issue – Inadequate EHR Templates

Posted on September 6, 2011 I Written By

John Lynn is the Founder of the blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of and John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

Time for the latest entry in my series of Common EHR Implementation Issues. See also my previous posts on Unexpected EHR Expenses, EHR Performance Issues and a little follow up to avoiding the EHR performance issues altogether.

This weeks common EHR implementation issue is: Inadequate EHR Templates.

Before I begin with the major issues of inadequate EHR templates, it’s worth noting that there are a few EHR software out there that use a different EHR documentation paradigm than templates. For example, some use voice recognition to power their documentation. Others have a system that learns your documentation over time and based on that learning remembers how you want to document certain procedures. Others, use lots of independent documentation methods (one EHR vendor calls them controls – check box, radio button, freetext field, etc.) which can be grouped and used in interesting ways.

However, even with all of the above alternative documentation methods, there’s often an element of templating that’s occurring. They’re PR and marketing people will shudder at the term template, but concepts related to templates seem to pretty much always apply. For example, in voice recognition there’s something called a Macro. That’s basically a template. The EHR system that learns your documentation method is just using your initial documentation in the EHR to create personalized templates of how you like to document. The independent documentation methods often group those various “controls” into groups of common visits. That sounds like a template to me.

I’d be interested to hear of an EHR system that doesn’t use the principles of templates. It is worth noting that all EHR templates aren’t created equal. Some are much more flexible than others. Now to some details.

The inadequate EHR templates shows itself in a number of different ways.

No Specialty Specific EHR Templates – This has to be the complaint I hear the most. It usually goes something like this, “The EHR salesperson said they had templates, but they don’t have any templates I can use.” Did someone say EMR salesperson mis-communication? Yep, happens all the time. Let’s be honest for a second. How could the EHR salesperson know how good their cardiology or neurology templates really are? They just go by what they hear and what they’re told by the EHR company.

Incomplete or Unusable EHR Templates – You may have noticed a subtlety in the quote I put above. At the end the doctor says “templates I can use.” Maybe the EHR salesperson isn’t lying to you about them having those cardiology or neurology templates. Maybe they do have a bunch of templates for those specialties (or whatever specialty that interests you). However, just because they have templates for those specialties doesn’t mean that you’re going to want to use any of the templates that they’ve created.

My favorite complaint is when they say that the specialty templates seem to have been created be a general medicine doctor and not an actual specialist from that field. I’ve heard it far too much not to mention it.

The other major problem with this point is the unique documentation preferences of each doctor. Has there ever been any two doctors that document the same way? We could debate the good and bad merits of such documentation, but the point is that each doctor is very different. Some feel the need to over document the encounter. Other doctors want to just document the bare minimum. Plus, some (purposefully or not) do a terrible job documenting the visit. The templates in an EHR could reflect any of these various documentation patterns and depending on your perspective could mean that EHR has inadequate templates for your needs.

Hard to Modify, Add to, or Adjust – While not specifically an inadequate template, this is an important part of templates. Turns out that if a user can easily modify, add to or adjust a template that is inadequate, you’re going to be a lot better off. Some template systems are like pulling teeth to modify. Others are amazing at how you can on the fly modify the template.

One promise I can make you, You WILL want to modify their templates. I can’t say I’ve ever heard of someone using the templates perfectly out of the box. Well, maybe I’ve heard of one or two using them, but that was when they were complaining that they had no way to modify the things they wanted to change.

Avoiding EHR Template Inadequacies

The best way to avoid this issue is to test drive the EHR software and the specialty specific templates you hope to use. Run through the templates like you’re charting on some common patients. You’ll learn a lot about what templates are available doing this than anything else. You’ll see if the templates are overkill or below standard for your needs.

Another great test is to try using multiple templates for a complex patient. How easily is that done and how well does the documentation display?

Then, during your EHR demo with the EHR salesperson, ask them to modify part of the EHR template they’re using to document. Tell them you don’t like to ask one of those questions, so you’d like to see them remove it from the template. Many are likely to respond, “It can be done, but I’d have to switch systems to do it or I’d have to call in to tech support to make the change.” I think we all know the real message they’re sending.

For those not interested in EHR templates, you might take a second to read Dr. West’s Experience implementing EHR templates in his office.

Avoiding EHR Performance Issues in the First Place

Posted on August 26, 2011 I Written By

John Lynn is the Founder of the blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of and John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

In my post about the common EHR implementation problem of EHR slowness, I mentioned that I’d follow up with a post on how you can avoid the EMR slowness issue altogether. It’s better to avoid than fix problems.

The best way to approach EHR performance issues is to make them part of your EHR selection process. EHR performance issues could and should be a deal breaker for you when you’re evaluating EHR companies. How then can you identify EHR software that might have these performance issues?

Red Flag #1 – EHR Demo Slowness – Bring a red pen to your demo and every time they say something like, “It’s not usually this slow?” or “It must be slow because it’s running on my laptop.” make a BIG RED mark on your paper (or tablet if you’re advanced like that). Even one red mark should be cause for concern and investigation.

Certainly there are situations where environmental issues can cause slowness to an EHR. So, you can’t completely rule them out completely for this, but this is their demo. This is there one time to shine. If they can’t get their EHR demo running at full speed, what makes you think an EHR production environment will be much better?

You can make an extra red mark if it’s a SaaS EHR that’s providing the demo. They might say it’s just “the internet connection.” Well, guess what? Soon, that’s going to be you using that EHR and often on similar internet connections.

Of course, the message to EHR vendors is to make sure your demo runs as fast as your production system.

Red Flag #2 – Site Visit Slowness – While the demo can tell you a lot about an EHR software, it can’t necessarily tell you the speed of the EHR software. Just because the EHR is fast during the EHR demo, doesn’t mean that same EHR software will be fast in a production environment. Add this to the multitude of reasons why a site visit to a current user of that EHR is so important.

Make sure to do that site visit at one comparable in size and users to your clinic. You don’t want to look at the EHR responsiveness of a solo practice if you’re going to be a 6 provider multi clinic setup. Size matters when it comes to EHR speed.

Once on site, you can get an idea of the speed and responsiveness of the EHR software in two ways. First, observe the users of the EHR in the clinic. See if they exhibit any of the systems listed in the first section of this post. Another observation is to see how quickly they’re clicking around the EHR. If you see a lot of clicks in a row with little waiting in between clicks, that’s a great thing. If you see them click, wait, click, wait, click, click , wait. Be afraid.

The second way is to ask the EHR users. The problem with doing this is that only one response has value. If they say the EHR is slow, then you’ve gleaned some important information that’s worth checking on. If they say the EHR is fast, then you don’t necessarily know. The problem is that you don’t know what the user considers fast. What’s their frame of reference for saying it’s fast? Do they know what fast is? Have they just been using the EHR software so long that they’ve hit a rhythm that makes it feel faster than it really is? It’s a good sign if they say that it’s fast, but take it with a grain of salt.

Red Flag #3 – Use A Demo EHR System Yourself – Most EHR vendors will provide you a way to demo the product yourself. This isn’t a fool proof method to test EHR slowness, but it’s another decent test of the EHR’s responsiveness. Try it out using your internet connection and your computer hardware. Nothing like first hand experience documenting some patient visits to learn about the speed of an EHR.

EHR Speed Suggestion – Don’t Skimp on Hardware
Far too often I see a clinic skimp on the hardware requirements and regret it later. In fact, they often end up spending the money twice since they have to buy new hardware since they skimped in the beginning.

Of course, this suggestion can be taken too far as well. The computer and laptop manufacturers will try to sell you the whole kitchen and you might only need the stove and refrigerator. To put it in more practical terms, you’re going to want plenty of RAM, but do you really need the webcam, Blu-ray player, and special 100 in 1 media device?

Just because an EHR vendor says their EHR software can work on a certain hardware configuration doesn’t mean it should be used on that hardware configuration. In the middle there’s a spot between can and overkill that’s called optimal. Find that hardware configuration and you’ll be a much happier EHR user.

Don’t accept an EHR that’s slow. Make sure that the EHR performs at a satisfactory level. I know of nothing that frustrates a clinic more than a slow EHR.

Common EMR Implementation Issue – EHR Performance Issues

Posted on August 24, 2011 I Written By

John Lynn is the Founder of the blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of and John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

We’re back again with our ongoing series on Common EMR Implementation Issues. Seems like readers really liked my first entry in the series about Unexpected EHR Expenses. To be quite honest, I was really happy with how that post turned out myself. It’s one of the most comprehensive and useful posts I’ve written in the 5.5+ years I’ve been writing about EMR and EHR. Hopefully we can continue that trend.

Today’s Common EMR Implementation Problem: EHR Performance Issues

I have to admit that this is a really tough problem to crack. However, it’s also incredibly common. The symptoms for this problem usually are described as, “THIS EHR IS SOOOOOO SLOW!” (This is appropriate use of ALL CAPS since they are often yelling this.) Followed by a *huff* and an angry doctor or nurse leaving their computer in a fit of rage. Other symptoms might include drumming fingers on the desk while staring blankly at the screen, lots of mouse clicks that get progressively longer and more emphatic, or the sitting back in your chair staring at the screen hoping that something will happen.

Once you’ve identified that there’s a problem with EHR slowness, then begins the fun and exciting (that was written in the sarcasm font) journey to identify the real issue. The biggest challenge with identifying the slowness is that there are a multitude of places that could be the bottleneck that’s causing your slowness. Some of which you can fix, and others you have to rely on your EHR vendor to fix.

To assist you in the ugly process of improving EHR performance issues, here’s a list of possible reasons you could have a slow EHR.

EHR Slowness You’re Responsible For
Slow Computers and/or Laptops – I’ve heard of a few EHR vendors offering free iPad’s with their EHR, but for the most part, you’re responsible for buying the computers and laptops for your EHR implementation. See my “EHR Speed Suggestion – Don’t Skimp on Hardware” below for more info on buying the right hardware. Needless to say, I’ve seen many slow computers be replaced and the EHR went a lot faster.

Slow Local Internet – Your local internet (or LAN as it’s often referred) could be the cause of your EHR slowness. I could have split this point into a half dozen possible issues. Some of them might include: Bad network card, bad cabling, bad switch, bad router, bad routing configuration, bad DNS configuration, overwhelmed network, etc etc.

Of course, in most cases you’ll probably have to call your IT service provider to solve these issues. They should be able to easily test most of the above issues and prove that it works for other internet applications and so it must be some other issue causing your EHR slowness.

Slow ISP (external internet connection) – If you’re using an in house EHR server, you won’t have to worry about this as much (except for interfaces, or EHR updates). If you’re using a SaaS EHR, then this could be a major bottleneck. Good thing is that it’s easy to test your ISP speed. If you’re speed is great to other sites, but not your EHR then you can move on to another issue. If you’re speed is bad for all sites on the internet, you need to see if your ISP can make some changes to provide the speed you’ve purchases from them. Otherwise, you might just need a bigger ISP connection than you have and you’ll be able to get your EHR running much faster.

Also, be sure you don’t have employees using up all your bandwidth downloading illegal (or legal) music or videos. That can eat up your bandwidth really quickly. There’s a reason Netflix uses up 20% of bandwidth on the internet. Movie downloads/watching might be using up your internet connection as well.

Memory on Server – I see this issue most often when a clinic tries to re-provision an old server for their new EHR or when they don’t follow the suggested specs of their EHR vendor. It can also happen when you start your EHR with 1 doctor and then grow your practice to 5 doctors. More users usually requires more memory on the server. There are good tools on servers for analyzing how much memory is being used so you’ll know if this is the problem or not.

Hard Disk Space on Server – This definitely shouldn’t happen in a fresh EHR install, but often can happen over time. Servers don’t like to run out of hard disk space and can do all sorts of crazy and unexpected things if they do. Other things that cause a hard disk to run out space might be backups or large log files. I’ve also seen where the IT administrator takes a 500 GB hard drive and divides it into multiple partitions. One partition for the O/S and one partition for the data. Often they misjudge how much to give to one partition versus the other. So, the one partition runs out of space while the other one has TONS of space left.

Good planning and regular maintenance will avoid these issues.

CPU on Server – I believe this is pretty rare these days since memory is usually the bottleneck instead of CPU. However, if the EHR software isn’t written correctly, this could be an issue. Particularly on older boxes.

Complex Workstation Setup – Your IT service provider might have told you all the great benefits of a thin client setup or some sort of virtualized desktop software solution. When done right, these solutions can work fantastic and save you a LOT of money. When done wrong, they can cause you all sorts of slowness and heartache.

EHR Slowness Your EHR Vendor Must Fix
Slow Server Configuration – There are lots of ways to tweak a server to go faster with less resources. Unfortunately, most of these tweaks are likely going to have to come from your EHR vendor. In a larger hospital implementation, you might be able to work with your EHR vendor to implement some of these tweaks. In a small clinic, you’re basically at the mercy of your EHR vendor to configure the server to run fast.

Slow Server (SaaS EHR) – Yes, SaaS EHR vendor servers can go slow too. The good thing is that your EHR vendor likely has monitoring tools that are watching for any slowness so they can proactively fix it. The problem is that then you’re at their mercy to fix the slowness. Needless to say, an EHR vendor’s server support staff rarely feel the end user pain of EHR slowness. At least the pain isn’t nearly as poignant.

Of course, a chorus of calls from EHR users to the EHR support line will help them understand better and fix the slowness. One call about your in house server doesn’t resonate quite as loud.

Slow or Overwhelmed Data Center Connection – Data Center internet connections are generally quite robust and built with a lot of redundancy. However, since data centers usually host many many different systems, they can also get overwhelmed. Sometimes through spikes of traffic, but more often through other nefarious attacks on the systems in the data center. Often, it’s not even your EHR software that’s causing the issue, but it might suffer the consequence. Not very common, but possible.

A little more common could be an EHR vendor that’s growing so rapidly that they can’t keep up with the demand for their EHR software. Other times the EHR vendor just did a poor job planning to expand their EHR data center services.

Poor EHR Code – Not all code is created equal. Some programmers are good at creating code that will execute quickly, but most are not. Fixing speed issues aren’t trivial. Particularly if you have a large code base that’s been created over a long period of time.

Poor EHR Design – The design of an EHR software often determines how fast it work. Designing for speed from the beginning is crucial. Otherwise, a poorly structured EHR can almost never be made fast.

Related to this is EHR software built on old technology. To use a car analogy, you can only make a pinto go so fast without gutting the engine. Too many EHR vendors are built on engines that can only go so fast. They can keep squeezing a bit more speed out of the engine, but eventually you have no other speed benefits because of the legacy technology limitations.

I’m sure there are other possible bottlenecks. Let me know of any I missed in the comments and I’ll add them to the list.

EHR Performance Finger Pointing
Another big problem with the complex list above is that it often leads to a bunch of finger pointing. Yes, sometimes it will feel like you’re back in Kindergarten again. Your EHR vendor will point the finger at your IT setup. Your IT service provider will point the finger at the EHR vendor. Then, the EHR vendor will point the finger at the hardware vendor. You’ll never be able to talk to a person at the hardware vendor and so you’ll have to use other tricks to prove it’s not them.

Needless to say the finger pointing can get really tiring really quick. Not to mention it can be very expensive as you spend money proving to your EHR vendor that it really is their problem and not your setup.

I’ll follow up this post with another on how to avoid EHR Performance Issues during the EHR selection process. I’ll link to that post once it’s up.

Side Note: This post was much longer than expected. I guess I did have a lot to say about this issue.

Common EMR Implementation Issues – Unexpected EHR Expenses

Posted on August 19, 2011 I Written By

John Lynn is the Founder of the blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of and John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

This is the start of a new series of posts that I plan to do over the next week or two. I’ll probably try and space them out so that they don’t overwhelm anyone. However, it’s going to be a series of common EMR implementation issues that I hear over and over again.

This series was prompted by a post on HIStalk by Inga where she talked about her visit to the doctor and his complaints about his EHR implementation. As I read through the list of complaints, I realized that they were all complaints that I’d heard before. If I’ve heard them all before, then they must be pretty common and worth talking about more.

Ideally the discussions in this EMR implementation series will help practices and doctors that are implementing an EMR to avoid these issues. I also know that I don’t necessarily know all the answers to avoiding these problems. So, I welcome others feedback on ways to avoid these problems in the comments as well.

Today’s Common EMR Implementation Problem: Many Unexpected Expenses

I can’t tell you how many times I’ve heard a doctor or medical practice talk about all the hidden expenses that they incurred during their EHR implementation that they didn’t plan for. Here are 3 tips to help you avoid this situation.

Unexpected EHR Expense Tip #1 – Plan for hidden expenses. Add $5000+ to your budget for hidden expenses. Hopefully you won’t have to use it, but if (and likely when) you need to use it you’ll already have it in your budget.

Unexpected EHR Expense Tip #2 – Get your EHR vendor to outline everything and anything they could charge you for. Once they’ve done that, consider putting the list of expenses in your EMR contract so that new expenses from your EHR vendor won’t appear. Here’s just a few EHR expenses that you might incur (and may not expect):
-Up front fee (almost everyone just focuses on this)
-Maintenance Fees (monthly, annually, etc)
-Upgrade Fees (to update your software…these are sometimes called Hot Fixes)
-Interface Fees (both sides of the lab and EMR company)
-Device Integration
-Training Fees
-Support Fees
-Licensing Fees (to license their various databases and/or clinical content)
-Install Fees
-Other non-standard modules – You mean you didn’t realize that the patient portal was an extra $150/month?
-EHR or PMS data migration Fees
-Template Creation Fees
I’m sure there are others that I’ve missed. I look forward to seeing the comments on this. I’ll update the post with other suggestions as they come in. As you can see, EHR vendors can charge you in lots of interesting ways.

Unexpected EHR Expense Tip #3
While EHR vendors can often throw unexpected fees at you, it’s probably even more likely that the other outside purchases you have to make during your EMR implementation will be a surprise. Here’s a list for you to consider the other EMR implementation related fees that might come unexpectedly:
-Server cost (almost everyone focuses on this)
-Software cost (including the operating system or third party software your EHR vendor might require)
-New Desktop/Laptop Costs
-Upgrading Desktop/Laptop Costs – You might find that your existing computers aren’t powerful enough to run the EHR you chose. This is particularly true if you’re using something like voice recognition with your EHR.
-Fax Server
-Fax Server Software
-Scanners – Yes, that is plural and people often start with one scanner and then have the unexpected cost of another scanner because they could really use 2+ scanners. Other times people use a cheap all in one scanner which quickly dies after they start scanning in bulk and they realize they need to buy a $1000+ scanner that can handle the required scanning
-Printers – You’ll likely need a few of these to print our prescriptions, patient education, etc etc etc. Plus, you’ll often need a better printer than the one you have.
-Dragon Medical Voice Recognition – The software, the mic (spend extra for a great one), etc. Some don’t realize all of this costs and doesn’t usually come with the EHR software.
-New Network Ports – You could go wireless, but many like the reliability of a wired connection. This costs to run the lines and cut out new internet connections
-Bigger Internet Connection – This is particularly true with a SaaS EHR setup. You think your current internet connection is enough and then you realize you need to pay for a bigger pipe (internet connection) or possibly even a second “backup” internet connection
-Backup Software
-Backup Hardware
-Off site Backup Service
-Cables – Lots and lots of cables required. Sometimes you even have the cable, but then realize you want a longer one. Unexpected expense!
-Power strips and other peripherals – $10 here and $10 there. This stuff starts to add up. Plus, get ready for things like your mouse to start breaking now that you’re using it a lot more.
-UPS (uninterruptible power supply)
Chip Hart added the following suggestions (Thanks!):
-Practices should purchase 25-50% more laptops/tablets (and/or batteries) than they expect.
-All those laptops and tablets will need a SECURE storage and recharge barn.
-You may be paying a carpenter and electrician.
-Integration fees? Data conversion fees?
-Will you need hands-free headsets for your staff, now?
-Maybe it’s time to get bigger monitors.

Hopefully the above lists will help you plan for all of the various fees that are associated with an EHR implementation. Many of these EMR costs are necessary, but end up being really annoying when you didn’t know they were coming. Check through this list to see if you’ve planned for all the EHR costs.

In a future post, I’ll see if I can’t take the above list and give you some ideas on how you can save on some of the costs above.