Home » News » Currently Reading:

From the Consultant’s Corner 7/2/14

July 2, 2014 News No Comments

Practice Mergers and EHR/PM Platforms: 5 Considerations for a Single System

As physician practices merge, forming larger group practices and multispecialty organizations, they often run into a situation where the various practices use separate EHRs and practice management (PM) systems. This creates inefficiencies and inconsistencies that ultimately limit some of the merger’s intended benefits. To prevent this, merging physician offices should consider moving to single EHR and PM technology platforms.

In my experience, pursuing single platforms yields several patient and practice benefits. For example, it streamlines the patient experience, allowing an individual to complete one registration and receive one bill, rather than registering on different systems used by physicians in the same practice and receiving patient statements from each provider. Not only does efficient access prevent patient frustration and potential leakage, it can have a positive impact on the patient’s choice of practice.

Consolidated applications also generate cost benefits by eliminating the administrative and staffing expenses that come from supporting multiple systems. Moreover, single solutions allow organizations to standardize workflow based on best practices, reducing process variation and elevating clinical and financial work streams to foster greater efficiency and performance.

A unified platform also improves business intelligence and informatics capabilities because all data comes from one source. This allows the practice to dig deeper into the data to improve overall quality of care delivery and enhance population health. When practices retain disparate systems, it can be cost prohibitive to aggregate data, particularly for small to mid-size practices.

While the potential benefits are significant, it can be challenging for merging practices to choose the right EHR/PM system. I recommend keeping these five points in mind during the selection process.

  1. Understand the true cost of a potential solution. In my experience, no two vendors have the same cost structure, so be sure when calculating total system costs to make note of one-time charges, such as installation fees, and recurring expenses, like annual software license renewal fees. Don’t forget to include the full scope of physician training in the cost analysis, as many estimates do not include the value of the physician’s time spent in training.
  2. Assess a vendor’s ability to support the practice’s specialized clinical needs. Not every system will adequately support clinical operations, and practices should make sure to check for the necessary depth and breadth of content. Keep in mind that clinicians require robust functionality that can be tailored or modified to meet multiple clinical specialty requirements.
  3. Consider the full impact on physicians and other providers. It is wise to determine if a system truly allows providers to perform their jobs better, such as by seeing more patients, completing charts efficiently or improving patient communication. Even though completing tasks faster is important, the quality of data and the ability to leverage it across the care continuum are even more so. I’ve seen first-hand how strong provider documentation can substantively improve quality of care, accelerate learning about best practices, and enhance clinical and financial outcomes.
  4. Look at the systems currently used across the merging practices. Review integration capabilities and requirements across the care continuum, including those of current and future hospital partners and referring providers. I have seen situations where having the same platform provided a competitive advantage for future risk-sharing or care collaboration opportunities. At the same time, evaluate the scalability of the various practice solutions to meet the expanded complexities of the merged practice.
  5. Assess the practice’s current and future state requirements to “future-proof” the technology investment. To make sure a new system does not become obsolete as the merged practice evolves, it is important to think about current as well as future needs. For example, look at physician productivity and billing performance, practice growth plans, changing reimbursement patterns, evolving reporting requirements, potential new specialties and future alignment opportunities with hospitals or other groups. Within this context, evaluate the vendor’s track record for flexibility and innovation, as well as costs associated with previous new developments and rollouts.

In the end, we all know that making the decision to pursue a single EHR and/or PM platform is not quick or easy. Using these five considerations as a guide, organizations should devote sufficient time to fully analyzing the options before deciding on a strategy that best meets the practice’s current and future needs and goals.

image

Brad Boyd is vice president of sales and marketing for Culbert Healthcare Solutions.


Contacts

Mr. H, Lorre, Jennifer, Dr. Jayne, Dr. Gregg, Lt. Dan, Dr. Travis

More news: HIStalk, HIStalk Connect.

Get HIStalk Practice  updates.
Contact us online.

JennHIStalk

Platinum Sponsors


  

  

  


  

Gold Sponsors


 

Subscribe to Updates




Search All HIStalk Sites



Recent Comments

  1. The article about Pediatric Associates in CA has a nugget with a potentially outsized impact: the implication that VFC vaccines…

  2. Re: Walmart Health: Just had a great dental visit this morning, which was preceded by helpful reminders from Epic, and…

  3. NextGen announcement on Rusty makes me wonder why he was asked to leave abruptly. Knowing him, I can think of…

  4. "New Haven, CT-based medical billing and patient communications startup Inbox Health..." What you're literally saying here is that the firm…

  5. RE: Josephine County Public Health department in Oregon administer COVID-19 vaccines to fellow stranded motorists. "Hey, you guys over there…

RSS Industry Events

  • An error has occurred, which probably means the feed is down. Try again later.