Meaningful Use Begins with EHR Vendor Agreement
Providers looking to claim a piece of the incentive pie for “meaningful use” of an electronic health record (EHR) system face a difficult decision—choosing EHR system software. Early adopters of the American Recovery and Reinvestment Act of 2009 (ARRA) provision stand to gain the most, but haste makes waste. Before your practice signs an agreement with a vendor, take time to read the fine print. There are certain things to watch out for.
In a Healthcare IT News article on EHR contract negotiations, Jeffery Daigrepont, senior vice president at Coker Group said that ensuring federal incentive funds begins during the vendor agreement stage.
“Many vendors offer a money back guarantee if their product does not comply with stimulus,” Daigrepont said. “Every contract should have a warranty that requires a vendor to correct defects at their expenses and under NO circumstances should you ever sign a contract without being entitled to future upgrades and new releases.”
The following is Daigrepont’s list of five health care IT decisions you’ll want to avoid (as seen in Healthcare IT News):
1. Buying defective software – It may not be your fault, but it’s your problem. Defects in software range from minor glitches to major liabilities. Most defects can be corrected, or workarounds developed. However, in cases where the defect creates a threat to security or patient safety, or a liability to the organization, the defect MUST be addressed immediately and/or use must be discontinued—just as Toyota has had to do with their cars’ sticking gas pedals.
2. Buying non-compliant software – Your entire organization is expecting the software to meet national standards or federal mandates, but the vendor fails to develop their product in accordance to these guidelines. In the case of stimulus incentives, being disqualified becomes a possibility. Moreover, penalties for not adopting could be enforced.
3. Not seeing the writing on the wall – Your system is installed, working and meeting the needs of the organization, but your vendor has commercially discontinued the product and is no longer creating enhancements. In short, you’re on a sinking ship. Not acting or refusing to accept the obvious is only delaying the unavoidable reality of having to rip out and replace your system.
4. One-offs – A “one-off” occurs when you cave to pressure from a department or individual who needs a specific IT solution to fill gaps around the existing program. In some cases, you have no other option, but there can be some trap doors when doing this. It’s always best to first see if there is a workflow workaround or if there can be a behavior change by those who feel they must have their own solution.
5. Going live with an incomplete system – The pressure to go live on a new system is often driven by a vendor who is trying to recognize revenue by burning through the hours in the budget so they can get to the next install. The system (in some cases) was not properly tested before going live. As a result, the users or physicians get first bitten by a bad experience or worse, backsliding starts to occur. This can be avoided by adopting a simple plan called “DBVT” (Design, Build, Validate, Test). For example, design your order form, build your order form, validate the build with end users, test the form with end users. This exercise will help you avoid proceeding with an incomplete system design.
For a sample contract language on how to protect your organization from some of these fatal IT decisions, contact Jeffery Daigrepont at: firstname.lastname@example.org or 770-597-0590.
Source: Healthcare IT News, Feb. 4