As the healthcare landscape continues to evolve, and more Accountable Care Organizations (ACO) come together, the need for cohesion and interoperability is increasing. Often, the physicians and hospitals within these organizations will have different EHR systems, creating quite a few areas of difficulty when trying to connect them all seamlessly. A Community Connect program can help.
CMS defines an ACO as a group of doctors, hospitals, and other health care providers, who voluntarily come together to provide coordinated, high-quality care to their Medicare patients. Medicare first established ACOs; however, we are now seeing private payers contracting with ACOs. One of the primary benefits of an ACO is that it allows for contracts with payers; designating that a team of caregivers will provide coordinated patient care across the healthcare continuum. The goal is to manage patient populations, improve patient care coordination, enhance preventive care, and eliminate unnecessary and duplicative costs to patients.
A Community Connect program is a strategic collaboration between healthcare organizations and community physicians and hospitals and is an effective way to integrate these groups into an overall electronic health record (EHR). To understand how a Community Connect program can help ACOs, it is first essential to understand some of the difficulties facing these organizations when trying to communicate with each other.
ACOs and value-based care are here to stay. However, it has become challenging for ACOs to capture the necessary data and get the right data in the hands of the providers. One of the most obvious hurdles is the number of different EHRs that ACOs are documenting in today. Having different kinds of software makes it challenging to get the provider a clear picture of the patient's previous care in a timely manner. To alleviate these issues, ACOs are taking on the financial burden of creating interfaces, known as Application Programming Interfaces (APIs). APIs are the messenger that delivers a request to the EHR that is requested and then delivers the response back to the requesting system. EHR vendors have developed proprietary APIs independently of each other, and functionality is often different. Some allow for read-only data, while others allow for discrete data. Having to evaluate each vendor is tedious and time-consuming and creates a significant hurdle when it comes to interoperability.
Interoperability is necessary. CMS requires ACO members to use the 2015 certified EHR technology (CEHRT). ACOs are working with Health Information Exchanges (HIE) but still don't always get the necessary patient data, requiring manual interaction via phone or fax. Healthcare organizations participating in one or more ACOs are looking to one EHR software solution to avoid the need for this manual intervention. Similarly, many ACOs are requiring members to move to one EHR solution. Although this can be an adjustment and an initial cost burden for both the members and the organization, one platform allows ACOs to standardize workflows and increase control over ACO operations. When everything is standardized, community providers can receive patient data from a care team immediately without having to go through the HIE. Scheduling for consults also becomes streamlined and registries and preventative care profit from utilizing one system.
A question that arises from Stark Law and the Anti-Kickback statute is patient referrals outside of the ACO. Providers participating in the ACO are going to be more likely to refer their patients to the same providers and hospitals within the ACO they participate. Therefore, the government is going to have to address this possible conflict if they expect providers to manage patients under the authority of the ACO.
Here's how the participating organizations ranked Epic Community Connect on a 100-point scale:
If you are interested in learning more about Optimum's Community Connect Workshop, please click here.
Send this to a friend