| Literature DB >> 25848618 |
Nancy Maloney1, Arvela R Heider1, Amy Rockwood1, Ranjit Singh2.
Abstract
INTRODUCTION: Secure exchange of clinical data among providers has the potential to improve quality, safety, efficiency, and reduce duplication. Many communities are experiencing challenges in building effective health information exchanges (HIEs). Previous studies have focused on financial and technical issues regarding HIE development. This paper describes the Western New York (WNY) HIE growth and lessons learned about accelerating progress to become a highly connected community.Entities:
Year: 2014 PMID: 25848618 PMCID: PMC4371445
Source DB: PubMed Journal: EGEMS (Wash DC) ISSN: 2327-9214
Figure 1.Connected Community: Transformation Process
Figure 2.Expansion of Data Sources, by number of facilities, April 2010 to September 2013
Notes: *Blue bars indicate the number of data sources in each category before the Beacon project, in April 2010. **Green bars indicate additional data sources connected during the course of the Beacon project, by September 2013. The total height of each bar shows the total number of data sources in place as of September 2013.
Figure 3.Expansion of Data Feeds, April 2010 to September 2013
Notes: ADTS=Admission, Discharge, and Transfer notifications; ER = Emergency Room.
*Blue bars indicate the number of data feeds of each type before the Beacon project, in April 2010. **Green bars indicate additional feeds created during the course of the Beacon project, by September 2013. The total height of each bar shows the total number of data feeds in place as of September 2013.
Figure 4.WNY Providers with HIE Results Delivery, 2009–2013
Figure 5.WNY HIE Patient Consents
Figure 6.Patient Virtual Health Record Annual Lookup Totals, 2009–2013
Technical Lessons
| Age and complexity of software and hardware can create problems. | The HIE needs to analyze current software and hardware to optimize interoperability. | Older, and especially small, rural hospitals need additional resources to participate in the HIE. | |
| Hospital systems are not fully integrated and often act as separate entities (pharmacy, ER, etc.). | The HIE needs to plan on having multiple data feeds. | This adds up front costs and ongoing maintenance complexity, since each software product upgrade may require HIE changes. | |
| EHR vendors often have competing priorities (e.g., Meaningful Use, ICD-10) that do not always align with HIE needs; specific barriers include cost of initial development, scarce resources, and competing projects. | A new HIE should consider beginning with vendors that already have interfaces. | Nationwide collaborative efforts such as the Standards and Interoperability (S&I) Framework are critically important for expanding regional HIEs. | |
| Products were developed for in-house use and not for data exchange. | Interface development can be accomplished by working with vendors. | Cost can be prohibitive unless the vendor realizes the benefit of HIE in marketing the product to other customers. | |
| Although these entities recognize the value of interoperability, there are no Meaningful Use incentives to drive adoption. | The HIE needs to provide staff education and assistance with workflow changes. | Even if HIE capability is set up, it will not be used unless staff understand the benefits and workflows are changed. |
Organizational Lessons
| Organizations are protective of their data and are often reluctant to exchange data electronically. | Utilizing community-based clinical transformation partners is an effective tool to build trust. | HIEs need to build trust before tackling the technical issues. | |
| Interface development is a slow and tedious process with many vendors. | HIEs need to carefully explain that the process takes time and effort. | Overpromising the benefits to get organizations to participate leads to frustrations. | |
| Staff members are typically more comfortable continuing their existing routines rather than using new technology. | New workflows need to be developed to integrate HIE into patient care. | The workflow redesign cannot be underestimated when promoting HIE usage. | |
| Each organization has its unique own set of circumstances including resource limitations, availability of expertise, priorities, and time limitations. | Expansion of HIEs requires flexibility in scheduling and resource allocation—one practice may need more help with technical issues while another may need more time on workflow. | HIEs need to analyze resources in each organization and establish scopes of work based on the practice capabilities. |
Community Lessons
| The pressure of competition and fear of violating antitrust laws often keep health care organizations apart. | HEALTHeLINK was able to convene stakeholders while assuring no areas of competition would be impacted by the HIE process. | The HIE can serve as the neutral playing field when there is not a large dominant health care system. | |
| Individuals with the technical expertise to understand HIT and HIE do not “speak” the language of the medical community and do not understand its culture. | HEALTHeLINK created a team with diverse expertise including technical, clinical, and business expertise. | Technical expertise alone is not enough to successfully expand HIE usage. | |
| New York is an “Opt-In” state, meaning that patients must sign the required consent form. | Using a communitywide consent form given to patients by their physicians was found to be effective. | The communitywide consent process allows multiple providers to access patient information without the need for duplicate consents. | |
| HIEs often focus on hospitals and primary care practices. | Reaching out to organizations and provider types (i.e., Transplant Services, dentists, social workers, emergency medical technicians, behavioral health providers, etc.) can add data sources and data users. | Increasing the number of data feeds and data users adds value to the HIE and accelerates usage. | |
| It is difficult to quantify cost savings and outcomes during the rollout. | Classifying the practices into groups based on the start of HIE was attempted,but about 20% of the providers changed practices during the 3 years and these changes made it difficult to attribute hospitalization data to length of use of HIE. | Additional studies are needed to determine cost savings. |