Tuesday, April 17, 2012

Tuesday, February 7, 2012

What Should You Do with a Failing EHR?


Unfortunately, you need to protect your practice and your patients against a failing EHR.  Some recent examples demonstrate the vulnerability of any practice to a failing EHR:

An EHR cloud service added customers which resulted in substantial delays for the physicians in the practice.

Monday, December 19, 2011

How are EHR Contracts Getting More Difficult?


EHR contracts contain an increasing array of complicating structures and dense terms that offer fewer and fewer commitments to your practice.  The problematic terms include:

·         Broad disclaimers further distance EHR vendors from any responsibility or liability that may result from the use of their products regardless of the cause:

o   Many contracts offer no warranties and sell the products “as is.”  Thereby, they have no obligation to fix problems or maintain product relevancy.  For example, a disclaimer that the product is offered with no representation of fitness for any specific purpose provides little to compel a vendor to address an issue or problem.

o   Many contracts include practice indemnification of the software vendor for a variety of issues.  For example, some contracts do not warrant the clinical content or the ability of the software to record information, but pass risk of any problems to the practice through broad indemnity clauses.  On a similar note, some business associate agreements have the practice indemnifying the business associate for inappropriate disclosures committed by the business associate.

o   A number of EHR vendors will not commit to support HIPAA Security or Privacy standards or Certified EHR status. 

·         Jointly marketed EHR, PMS, and/or patient portal products may require separate agreements for each product.  Each agreement includes separate terms with frequently conflicting agendas and conditions.  In the event of a problem, you could not only get caught between the different companies, but have contracts that specifically disavow any responsibility for the actions and interfaces with any “third party products.”  For example, some EHR contracts put the responsibility on the practice to maintain interfaces with any other products, including the partner PMS

·         More restrictive Agreements to protect their products and businesses.  EHR vendors are rightfully concerned with protecting their intellectual property.  However, many EHR contracts include terms that could hamper the ability of the practice to operate.  For example, many contracts prohibit disclosures about the EHR to any non-employee.  Such terms trigger technical contract violations when the practice provides EHR access for chart review or to demonstrate the EHR to prospective physicians. 

Interestingly, we are typically told that the legal terms do not represent the commitment of the vendor, and that they could not stay in business if they were not responsive and effective.  However, the legal terms of the contract frames the relationship with the vendor.  In the vast majority of cases, your practice will be dealing with a much larger and more sophisticated EHR vendor.  In order to protect your practice and preserve your patient records, you need a balanced contractual relationship.

Your practice should be wary of any PMS/EHR/Patient Portal contracts and have the contract thoroughly reviewed by a qualified professional.  In general, vendors are willing to accommodate issues you raise to get your business.  Otherwise, you are committing to a contractual relationship that puts your practice in a difficult situation that could cost you money and disrupt patient care.

Monday, December 12, 2011

Should ICD10s Affect Your EHR Strategy?


On October 1, 2013, practices will start submitting claims using the ICD10 coding system.  Any practice planning on using EHR systems to facilitate the transition to ICD10 needs to take a close look at the practicality of implementing an EHR in time to support ICD10 coding.

Wednesday, December 7, 2011

Will ICD10s be an EHR Challenge?


In theory, EHR systems will make ICD10 coding tolerable.  However, ICD10 coding presents a wide range of challenges to EHR vendors and users. 

Friday, September 2, 2011

Does Your EHR Present What Your Recorded?


With paper exam notes, the doctor and staff record information and the note reflects what they recorded.  Unfortunately, EHR based notes may not be as direct.

Thursday, July 14, 2011

Why Are Patient Portals More Important Than You Think?

Patient portals facilitate the exchange of information between patients and physician practices.  What was once considered a nice option for your EHR is becoming a necessity.  Unfortunately, not all patient portals offer the same features.  Failure to acquire an adequate patient portal could limit your EHR benefits and increase your costs.

What ACO Features Are Needed in an EHR?

Most EHR systems are based on strategies that predate accountable care organizations (ACO) and Certified EHR standards.  The key EHR requirements for ACOs are the ability to electronically exchange patient information, support provider collaboration, and monitor patient care.  The EHR focus to date has been on creating patient exam notes and specifically meeting the Evaluation and Management documentation standards.  In many cases, EHR products that have evolved to date do not adequately accommodate the operational or management needs of the ACO structure.