Jonathan Bush, other HIT Leaders Dive into Healthcare’s Interoperability Problem at World Health Care Congress | Healthcare Informatics Magazine | Health IT | Information Technology Skip to content Skip to navigation

Jonathan Bush, other HIT Leaders Dive into Healthcare’s Interoperability Problem at World Health Care Congress

May 1, 2017
by Rajiv Leventhal
| Reprints
Bush said at the annual conference in D.C. that cloud-based EHRs, rather than “pre-Internet systems,” will be the future

A panel of three leaders in the health IT space, including outspoken athenahealth CEO Jonathan Bush, discussed the current interoperability landscape and what new strategies will help shape the future of healthcare connectivity.

Bush was joined in the keynote panel—part of this year’s World Health Care Congress, held at the Marriott Wardman Park Hotel in Washington, D.C.—by Steven J. Corwin, M.D., president and CEO of NewYork-Presbyterian (NYP, New York City) and Craig Samitt, M.D., executive vice president and chief clinical officer, Anthem, Inc. The session was moderated by Dan Diamond, health policy reporter at Politico.

When asked about what the industry is doing well and where they are failing, Drs. Corwin and Samitt had rather pessimistic tones, with Corwin noting that the current electronic health records (EHRs) at NYP, which actually only account for some 40 percent of the organization’s data, are fragmented and not interoperable. “The promise of interoperability is something that has been over-promised,” Corwin said. “The idea was that that various EHRs could be perfectly compatible, but that has not been [the case]. For us, it gets down to having a single EHR, taking [out] the expense of putting them together over a multi-layered system, and then reducing the number of exchanges and linkages we need to have. At this point, our linkage exchange looks like spaghetti wires,” adding that in NYP’s interface engine there are currently 6,000 interfaces, though the goal is to cut that number down to 3,000. “We just can’t toggle back and forth between systems,” he said.

Similarly, Samitt noted that the issue isn’t a technology one, but rather one of willingness and incentives. The Anthem senior executive said he is “highly critical of our industry since other industries have figured it out.” He added, “When there's a will, there's a way. I think there is a way for interoperability but less of a will. Information should be a common good as it relates to population health and better care at a lower cost, but we do not treat it that way.” He went on to talk about data ownership, noting, “Payers probably have the most complete data set but it's not timely. Doctors have the most acute data but it’s not complete. And patients have most relevant data, but it's not actionable.”

The panelists were then asked who’s to blame for these data sharing issues, a question that usually elicits varying responses from those pointing fingers at vendors to others assigning fault to providers and policymakers. From the payer perspective, Samitt said that claims information is only a subset of the data, and that it’s challenging to get providers to share data, though he also admitted that payers are not so willing themselves. “None of us should own the information; it should be a common good. Let's keep the information safe and pool it so we can have a true longitudinal patient record,” Samitt said.

Webinar

Advancements in Healthcare: Interoperability, Data Exchange, and More

Micky Tripathi, President and Chief Executive Officer of the Massachusetts eHealth Collaborative, is one of the most well-informed and well-respected healthcare IT leaders in the U.S. Tripathi has...

From the vendor vantage point, Bush—who two years ago famously tweeted at Judy Faulkner, CEO and founder of Epic Systems, that he would pay the user fee for Epic if the giant EHR vendor would join the CommonWell Health Alliance, an interoperability initiative of which athenahealth is a part of—agreed that the incentives to share healthcare data are not rewarding enough for stakeholders. “For my entire career, no one has wanted to exchange information,” Bush said. “The government has made it largely illegal for providers to get paid by digitally flowing information upstream. And [the feds] do not let just any provider see Medicare data,” adding that his company went through the laborious process of filling out applications and hiring lawyers so that they could get access to this CMS (Centers for Medicare & Medicaid Services) data, only to get denied. “Historically,” Bush said, “Hospitals have said that they are the only place that data can flow so that they keep referral volume and preserve their institution.”

However, things are beginning to change, Bush continued, noting dedication from new Health and Human Services Secretary Tom Price, M.D. to reverse things. “We are [seeing] a willingness on the part of forward-thinking healthcare systems to win by being open. Last year, the 21st Century Cures Act [was passed] and that makes it illegal to block data,” he said.

Bush also called out Epic, Cerner and Meditech, which he refers to as “pre-Internet companies” for now being more open to interconnectivity, proving that there are signs of change in regards to stakeholders’ willingness. "Payers are also giving us claims data they didn't use to give us, and that gives us information on patients that we can pull together that we weren't able to before," he said.

Chiming in on the topic of data blocking, Corwin said that hospitals hoarding data is a fair criticism. “People believe that data can be monetized in healthcare, and that’s particularly true with well-curated genetic information,” he said. “I'm less enamored with that idea; I think that the data [belongs] to the patients, not to the providers. But there are those [providers] out there who do think there's a market advantage. I'm a big believer in not monetizing data unless it improves patient outcomes,” he said.

Bush further said that athenahealth is building a master patient index (MPI) and also a calendar product that would help doctors on athenaNet get more patient appointments. He referred to EDI and HL7 as standards that will “die since they are pre-Internet.” Bush said it was these outdated companies that advocated as part of HITECH (the Health Information Technology for Economic and Clinical Health Act) to eliminate interoperability as a requirement for meaningful use.

He continued, saying these pre-Internet companies “claim to be interoperable but never will be. They need to go,” he attested. Bush added, “Cloud companies can easily be interoperable. HITECH got everyone onto systems that they're now stuck with, and the Internet was shut out of HITECH. You have 60 medical specialties and [the idea is that] any EHR will be the right one for all 60?  That is absurd. How many apps on your iPhone were written by Apple? Four of them. So [we won’t reach] interoperability until we get rid of these servers.”

Bush went on, “That means we need to invite our competition onto the platforms and be like [Jeff] Bezos [founder of Amazon]. “We must accommodate a new generation and we have to move to the Internet in healthcare. This cannot be a questionable proposition in healthcare in 2017. The new cloud-based EHR companies are coming onto our platform; the nightmare Steven [Corwin] is experiencing connecting different old systems is becoming a thing of the past, slowly.”

Samitt agreed with Bush on how the future might look, arguing that it’s not going to be about EHR-to-EHR connectivity going forward, but rather capturing data elements in the cloud to manage population health. “EHRs connecting won’t be as relevant in the future,” he said. “Data inputted is less crucial than data outputted. So the pooling of information and the analytics will be crucial, not which EHR you are on,” he said.

To close the discussion, the panelists were asked about when healthcare connectedness will no longer be an issue. Bush estimated it would take some five years. On the other end of the spectrum, Corwin predicted that interoperability will be superseded by disruptors such as telehealth, artificial intelligence and machine learning. “Interoperability won't be solved in the short-run. Patients will demand their own data. And connecting people via regional HIEs won't happen. I’m very pessimistic about the [prospects] of true interoperability. Samitt was more optimistic, predicting that real interoperability can be achieved in 10 years. He noted that much of it comes down to payment reform as well, pointing out that nearly 60 percent of Anthem’s payments are now tied to value. “Connectivity is not just data connectivity, but we also need to achieve alignment with the patient at the center,” he said.


The Health IT Summits gather 250+ healthcare leaders in cities across the U.S. to present important new insights, collaborate on ideas, and to have a little fun - Find a Summit Near You!


/article/interoperability/jonathan-bush-other-hit-leaders-dive-healthcare-s-interoperability-problem
/news-item/interoperability/where-information-blocking-rule-health-it-now-criticizes-missed-deadline

Where is the Information Blocking Rule? Health IT Now Criticizes Missed Deadline

December 17, 2018
by Heather Landi, Associate Editor
| Reprints

Industry group Health IT Now, a coalition of healthcare and technology companies, responded today to the Trump Administration's latest missed deadline for publication of a proposed information blocking rule as required under the 21st Century Cures law.

The proposed rule was sent by the Office of the National Coordinator for Health IT (ONC) to the Office of Management and Budget (OMB) on September 17, 2018, setting off a 90-day timeline for the agency to complete its review; a period which was now expired without publication of a proposed rule, according to Health IT Now.

The onus to publish the regulation falls on ONC, the health IT branch of the federal government that is tasked with carrying out specific duties that are required under the 21st Century Cures Act, which was signed into law in December 2016. Some of the core health IT components of the Cures legislation include encouraging interoperability of electronic health records (EHRs) and patient access to health data, discouraging information blocking, reducing physician documentation burden, as well as creating a reporting system on EHR usability.

The information blocking part of the law has gotten significant attention since many stakeholders believe that true interoperability will not be achieved if vendors and providers act to impede the flow of health data for proprietary reasons.

“Now, more than two years after 21st Century Cures was enacted, patients and providers are still without an information blocking rule - undermining the intent of the law,” Health IT Now officials stated.

ONC has delayed regulation around information blocking a few times already, previously stating that the rule would be released in April then revising its timeline to September, before finally submitting the rule to OMB on September 17th.  

As previously reported by Healthcare Informatics Managing Editor Rajiv Leventhal, during an Aug. 8 episode of the Pulse Check podcast from Politico, National Coordinator for Health IT Donald Rucker, M.D., said that the rule is "deep in the federal clearance process." And even more recently, a bipartisan amendment to the U.S. Senate's Department of Defense and Labor, Health and Human Services, and Education Appropriations Act for Fiscal Year 2019 includes a requirement for the Trump administration to provide Congress with an update, by September 30.

“It is stunning that, more than two years after 21st Century Cures became law, we are still waiting on regulators to actually do what the law says,” HITN Executive Director Joel White said in a statement issued Monday. “Patients and providers have looked on with disappointment as the administration blows through one missed deadline after another for publicly releasing a proposed information blocking rule. It is time to say 'enough.' By continuing to slow walk these regulations, the administration is adding to uncertainty in the marketplace and is quickly reaching a point whereby it will be in obvious defiance of the spirit of the Cures law.”

White further stated, “Lawmakers who worked doggedly to get this landmark, bipartisan bill across the finish line should be incensed by the way that bureaucratic delays have weakened their signature achievement. This holiday season, the best gift that OMB could give consumers would be an expedited completion of its review and the public release of a robust information blocking rule. In the meantime, we are hopeful that industry stakeholders will not delay interoperability initiatives as a result of the ambiguity created by these continued delays.”

It is not the first time that the Health IT Now executive director has been publicly critical of the Trump administration for not yet publishing any regulation on information blocking. In an op-ed published September 8 in STAT, White wrote, “More than 600 days after the enactment of the Cures Act, not a single regulation has been issued on information blocking.” White added in frustration, “Health IT Now has met with countless officials in the Trump administration who share our commitment to combat information blocking. But those sentiments must be met with meaningful action.”

More From Healthcare Informatics

/article/interoperability/intermountain-cmio-stan-huff-need-greater-interoperability-we-re-killing

Intermountain CMIO Stan Huff on the Need for Greater Interoperability: “We’re Killing Too Many People”

December 6, 2018
by Rajiv Leventhal, Managing Editor
| Reprints
About 250,000 people die per year due to preventable medical errors, and that’s the biggest motivator there is for more advanced interoperability, says one clinical IT leader

Stan Huff, M.D., chief medical informatics officer (CMIO) at the Salt Lake City, Utah-based Intermountain Healthcare for the past 31 years, has long been a top leader in his field. Working on the leadership team for a health system like Intermountain and serving as a co-chair of the HL7 Clinical Information Modeling Initiative (CIMI), while also having been a former member of the ONC Health IT Standards Committee, Huff has a wealth of knowledge coming from both provider- and standards-focused perspectives.

Huff, who represented Intermountain at a White House meeting on interoperability this week, recently chatted with Healthcare Informatics about all things interoperability, including the different types of data exchange that exist today, the greatest barriers, and how potential pending regulations could shake up the landscape. Below are excerpts from that discussion.

When you look at the interoperability landscape today, how bullish are you on where things stand, broadly speaking? Or rather than bullish, are you more concerned?

I don’t know if I am bullish or not, but I think we are making progress—and it’s significant progress. There is an incredible amount of work to be done. I’m not concerned at the progress; I am happy, but mindful of how much work is left to do to really reap the benefits that people are hoping for.

You’re currently a co-chair of the HL7 Clinical Information Modeling Initiative while also having been a member of former the ONC Health IT Standards Committee. How important is it to figure out the issues around standards before things can progress?

Webinar

Advancements in Healthcare: Interoperability, Data Exchange, and More

Micky Tripathi, President and Chief Executive Officer of the Massachusetts eHealth Collaborative, is one of the most well-informed and well-respected healthcare IT leaders in the U.S. Tripathi has...

I wish it had a higher priority. Most of the time when people are talking about interoperability now, they are thinking about caring for an individual patient and thinking about sharing information between different systems that have information on that patient. They are usually thinking about EHR [electronic health record]-to-EHR for patient care—they have a very focused idea.

But there are other dimensions. There is interoperability relative to public health, meaning how we share data from an organization to a public health [entity] so that we understand what’s going on with a whole population relative to a particular disease.

There is also research interoperability, so we can share data that’s coming from research activities. And closely related to that is interoperability of clinical trial data and all of the randomized controlled trial data that comes with that.

Then there is interoperability that comes from devices and data coming from devices, which is a whole field onto itself. So you have to be careful when you talk about interoperability. This is one axis of interoperability, in that it has to do with the scope of systems you are communicating with.

The other axis of interoperability has to do with how truly interoperable you are, and there are different levels there as well. One level is the interoperability you get with the HL7 version 2 [standard], where you have a structure and people know how to send messages between systems. And there is a lot of negotiation that happens when you set up an HL7 version 2 interface to say what terminology you are using, and if you send something as two fields or one field. There is a lot that goes on there and that’s helped quite a bit when you talk about HL7 FHIR [Fast Healthcare Interoperability Resources]—it has a more defined structure and has more things specified about terminology use.

And then you can get an even better of interoperability if you are using the Argonaut [Project] profiles. But even at that Argonaut profile level, you aren’t plug-and-play interoperable. There still is ambiguity in the Argonaut definitions that lead to different implementations by different companies and organizations.

The highest level is what I would call “plug-and-play” where this no bilateral negotiation around terminology or anything like that. The standard is explicit enough so that it could be tested for conformance and you can say whether a given system is conformant or not, and the data can be used in the way it was intended. We don’t have any plug-and-play interoperability to speak of right now, and that’s what I’m trying to shoot for.

One of three biggest motivators for me is patient safety. There is really good and convincing data that shows we are killing 250,000 people per year due to preventable medical errors. And that won’t be solved by “zero harm” programs, or by “sort of” interoperable systems. In the end, the “sort of” interoperable systems means that a person still has to look at things and make a judgment. And people are not perfect information processors. So you need a situation where the data is explicit enough where I can write rules that prevent the death or improper treatment of patients.

And we are not at that level yet. How urgent is it? I think it’s incredibly urgent and you can make an argument that it’s more important than lots of other things we’re spending money on that would have less of an impact on patient care. I work in this area, so yes, I am biased.

But I’m persuaded that it’s worth an investment, and to get to where I want to get to will not be easy. This won’t be something where you make one $20 million investment and then it’s done; it will take five or 10 years, and you will make incremental progress over that period of time. Think of it like a military campaign or a crusade, because it’s that type of timeframe and scale where you need planning and infrastructure to really accomplish what we want to do in the end—which is save lives, decrease the cost of care, and reduce the burden of clinicians.

Many folks believe that until the business incentives change, stakeholders will not be incentivized to be open with their systems. Do you agree with this and how much incentive exists today?

There isn’t a whole lot of incentive yet. If the patient care and safety issues were sufficient enough incentives, then this would have been solved a long time ago because those incentives have been there. People know and understand that we’re not caring for patients in the best way possible. And it’s the financial and proprietary considerations that keep us from doing that, ultimately.

We have to be careful [with incentives] though, because there are unexpected consequences. Going back to when I was on the HIT Standards Committee, we thought that we were doing useful and good for U.S. healthcare when we set up the meaningful use measures. And while meaningful use solved the EHR adoption issue, what it taught people was how to manage measures but not manage quality.

People became incredibly good when it came to managing the measures to get paid and to meet the qualifications, but I don’t think anyone would assert that those things improved the quality of care in any measurable way. So I think we didn’t meet the goal that we were shooting for—providing better quality care at a lower cost.

The ONC annual conference took place last week, and there seemed to be significant conversations around pending regulations such as possibly making interoperability a requirement to stay in Medicare and prohibiting information blocking. How does all of this land for you?

I welcome the change; it’s a good as thing you move from meaningful use to promoting interoperability. What I don’t know is if these specific [rules] being proposed are going to accomplish what [we want]. We thought we were doing the right things back when we were doing meaningful use.

At a high level, I would agree that it would be wonderful to require interoperability as a requirement for Medicare participation. But it’s undefined. When talking about the dimensions and these things, there has to be an understood and a useful level for the interoperability that’s required. But I haven’t seen the details to know whether what’s being asked for is both achievable and valuable if it were to be achieved. But I do agree with the [overall] direction.

Intermountain is often at the forefront of health and health IT initiatives such as its sponsorship of the Opioid Community Collaborative. How can these learnings be shared so they can improve the digital healthcare ecosystem?

The thing I try to emphasize to people is that if you look at what we are doing, and you take it in aggregate across the country—the things people are applying decision support to—it’s a tiny part of what we could do. And the reason for that is we don’t have interoperability. You can create a good program at Intermountain, or at Kaiser Permanente, or at Mayo Clinic, but the only place it works well is where it was developed. You cannot move it. If you move it, you have to recreate it. Until you have interoperability, I can’t write a rule that works on top of a Cerner system and also on an Epic system, or for that matter works on two different Cerner implementations. This cannot happen until you have those platforms supplying APIs so I can hook my decision support up to their system without rewriting all of the logic in a different technology platform.

So we are doing good things, and want to continue to do good things, but wouldn’t it be wonderful if what we did, or what the University of Utah is doing with opioids, can be directly moved and used, in the same way people can buy apps for their iPhones in the app store, or any other platform.

The realization is we might be doing 150 things at Intermountain in terms of decision support applications, but there is an opportunity to do 5,000 things, and we will never get to those 5,000 things unless we get to an interoperable platform so that when knowledge is created it can be shared. That’s my real emphasis behind interoperability.

 


Related Insights For: Interoperability

/article/interoperability/klas-wake-commonwell-carequality-connection-ehr-vendors-making-significant

KLAS: EHR Vendors Making Significant Progress with CommonWell, Carequality Connection

December 4, 2018
by Heather Landi, Associate Editor
| Reprints
While most EHR vendors have connections to the national network, only athenahealth and Epic customers have connected en masse, KLAS reports
Click To View Gallery

With the establishment of connectivity between CommonWell and Carequality, announced back in August, as well as other interoperability advancements by electronic health record (EHR) vendors, the ability to exchange patient records is within the reach of most acute care or clinic-based provider organizations, regardless of size or financial situation, according to a new report from Orem, Utah-based KLAS Research.

In the report, “Interoperability: Real Progress with Patient Record Sharing Via CommonWell and Carequality,” KLAS researchers note that since the last KLAS report on interoperability, which was published in March 2018, the acute care/ambulatory EHR market has taken critical steps forward in sharing data via national networks. The most notable advancements include the establishment of the CommonWell-Carequality link, Meditech’s initial connection to CommonWell, and notable Carequality adoption among NextGen Healthcare customers, according to KLAS researchers.

Most of the prevalent acute care/ambulatory EHR vendors are connected to the national framework, marking significant progress for interoperability, according to KLAS researchers. The report findings come a few weeks after CommonWell and Carequality announced that the connection to the Carequality framework was “generally available.” Cerner and Greenway Health successfully completed a focused rollout of the connection with a handful of their provider clients, who have been exchanging data daily with Carequality-enabled providers, CommonWell officials said.

In August, CommonWell Health Alliance and Carequality announced initial connectivity, which is the beginning of a broader effort to increase health data exchange nationwide, and builds on an announcement made almost two years ago. In December 2016, CommonWell and Carequality announced connectivity and collaboration efforts with the aim of providing additional health data sharing options for stakeholders. Officials said that the immediate focus of the work between Carequality and CommonWell would be on extending providers’ ability to request and retrieve medical records electronically from other providers. In the past year and a half, teams at both organizations have been working to establish that connectivity.

Now, since the connection went live in July, officials noted that CommonWell-enabled providers have bilaterally exchanged more than 200,000 documents with Carequality-enabled providers locally and nationwide, as reported by Healthcare Informatics in November.

Webinar

Advancements in Healthcare: Interoperability, Data Exchange, and More

Micky Tripathi, President and Chief Executive Officer of the Massachusetts eHealth Collaborative, is one of the most well-informed and well-respected healthcare IT leaders in the U.S. Tripathi has...

CommonWell, an alliance formed five years ago, operates a health data sharing network that enables interoperability using a suite of services aiming to simplify cross-vendor nationwide data exchange. Major vendors connecting to CommonWell include athenahealth, Cerner, CPSI, eClinicalWorks, Greenway Health and Meditech.

Meanwhile, Carequality, an initiative of The Sequoia Project that launched about a year later, is a national-level, consensus-built, common interoperability framework to enable exchange between and among health data sharing networks. Vendors using Carequality include athenahealth, Epic, eClinicalWorks and NextGen Healthcare. Nearly all major EHR vendors have aligned with one or both of these options, according to KLAS.

Together, CommonWell members and Carequality participants represent more than 90 percent of the acute EHR market and nearly 60 percent of the ambulatory EHR market. Today, more than 15,000 hospitals, clinics, and other healthcare organizations have been actively deployed under the Carequality framework or CommonWell network, officials attest.

This latest KLAS interoperability follows a report back in March in which KLAS researchers positioned that the CommonWell Health Alliance’s interoperability efforts were hindered by a lack of provider adoption and its interoperability services currently lacked value. However, when CommonWell and Carequality eventually connect, “instant value” will be created for users, KLAS researchers attested in that report.

Currently, Epic is not a member of CommonWell, despite other major EHR vendors pushing them in that direction. Back in 2015, athenahealth CEO Jonathan Bush famously tweeted to Epic’s CEO Judy Faulkner that his company would pay for Epic to join.

Indeed, KLAS reported in March that CommonWell will likely see a significant adoption increase with a solid Carequality connection. “Since its launch five years ago, the tendency to over-market the level of adoption of CommonWell has created apprehension and a lack of trust among potential participants and prompted this report, showing a snapshot of providers’ success,” the researchers said in the March report. KLAS researchers also claimed that when CommonWell connects to Carequality, “the entire Epic base will become available, creating instant value for most areas of the country.”

Following the publication of that report, CommonWell’s Executive Director Jitin Asnaani, in an exclusive interview with Healthcare Informatics, defended his organization’s mission and attested that the network is continuing to grow and prove its worth.

Asnaani also critiqued the KLAS report’s claim that vendors such as athenahealth and Epic give their customers a head start by enabling plug-and-play data sharing via Carequality. Asnaani called this specific critique “totally bogus,” asserting that the quality of data sharing is dependent on the vendors rather than dependent on CommonWell or Carequality.

KLAS Assessment on the Progress of CommonWell-Carequality Connection

In this latest report, KLAS researchers focused specifically on the progress EHR vendors have made in sharing patient records via the standardized (plug-and-play) networks of CommonWell and Carequality.

KLAS researchers assert that this focus is important because the “plug-and-play” option is the “only option” that allows provider organizations “avoid significant costs, delays, and organizational workload.”

KLAS also acknowledged that “virtually all major EMR vendors can successfully share patient records through the traditional point-to-point connections (a costlier approach in terms of time, resources, ongoing maintenance, and money), local HIEs (health information exchanges) and direct exchange (where records are manually sent to other providers).”

Referring to the CommonWell-Carequality connectivity as the “connection heard round the U.S.,” KLAS researchers contend that this connection should be “key in driving value and opening the floodgates so that any provider organization that desires to can exchange patient records with relative ease and little cost.” KLAS plans to measure the impact of this sharing in a 2020 interoperability report.

According to the report, this fall, two CommonWell-connected Cerner organizations tested and validated the ability to connect with Epic sites via Carequality. “Their initial reports are that the connection enables data sharing with critical partners otherwise out of their reach and adds tremendous value to their existing CommonWell exchange. The Epic sites involved indicate that they also are able to see and consume data via the new connection,” KLAS researchers wrote.

In a blog post, KLAS researcher Corey Tate, the author of the latest KLAS report, reiterated the value of the CommonWell-Carequality connection with regard to the availability of Epic data to provider organizations who connect. “Access to the Epic data is exactly what was talked about by the initial sites that tested the CommonWell connection to Carequality. Ironically enough, Epic’s intra-operability, which was initially dismissed, will likely be the catalyst that pulls widespread patient-record sharing forward. “

Currently, all but two of the other major EHR vendors—athenahealth, Cerner, CPSI, eClinicalWorks, Epic, Greenway Health, MEDITECH, NextGen Healthcare, and Virence Health (formerly GE Healthcare)—have customers connecting, according to KLAS. At this point, Allscripts and MedHost have yet to connect to CommonWell or Carequality. However, Allscripts recently announced more solidified plans to have their Carequality connection ready in Q1 2019 and to then roll it out in product updates throughout the year, according to KLAS. MedHost has been aligned with CommonWell since 2014 but has yet to have any live connections, KLAS researchers state.

While all of these vendors have connections to this national network, only athenahealth and Epic customers have connected en masse, according to Tate, in his blog post. “Each vendor has more than 90 percent of their customers connected. Cerner is next at around 35 percent. Many other vendors’ customer bases are just getting started,” Tate wrote.

“Epic and athenahealth have near complete uptake among their customers, allowing them to work on the next steps for interoperability, such as fine-tuning usability and increasing value for clinicians,” KLAs researchers wrote in the latest report. The researchers noted that plug-and-play sharing is “virtually invisible and automatic” for athenahealth and Epic customers, and “both vendors remove the big obstacles” to providers’ success.

KLAS researchers also highlight Epic’s and athenahealth’s approach to facilitating participation, via an opt-out approach, and removing governance barriers, via predetermined handling of outside data. The researchers contend that this indicates that “regardless of customer size, vendors can facilitate widespread adoption if they choose.”

NextGen Healthcare and eClinicalWorks show the most notable progress in connecting to the national framework, according to KLAS. Since NextGen Healthcare made their bidirectional connection available in Q1 2018, customers have rapidly taken up connections to Carequality. “With 80 customers connected, there is still much room for additional uptake—though NextGen has removed both financial and technical barriers to make this a reality. eClinicalWorks customers have also rapidly taken up connections, with nearly triple the number participating today (~2,500) compared to March 2018,” according to the report.

Meditech also made their first connection to CommonWell, and CPSI has made notable progress this year as well, KLAS reports. Cerner continues to actively push for customer participation and has added 35 hospital customers.

“Virence Health (GE Healthcare) has been slower to get out of the gate despite good feedback from early adopters,” the KLAS researchers wrote. “Greenway Health also doesn’t have much momentum, and overall, interviewed Greenway organizations are the least excited about their CommonWell connection.”

KLAS researchers also note that with CommonWell and Carequality linked, the biggest technical obstacle to widespread patient-record sharing has been removed, and the biggest remaining obstacle is local community adoption. “The healthcare industry is rapidly approaching the point where an organization using any of the major acute care/ambulatory EMRs should be able to easily connect to other provider organizations with minimal cost and effort,” KLAS researchers state. “Many vendors have eliminated obstacles on the path to data exchange—all but Virence offer connections to customers at no cost, and all but Cerner have made this plug and play by removing technical barriers.”

“Today, the biggest barriers preventing widespread participation are governance and the need for organizations to decide to participate. Even Epic and athenahealth customers report diminished value from their connection when local exchange partners opt not to connect to the national networks,” KLAS researchers wrote in the report. KLAs also believes that until other vendors take an opt-out approach, provider organization leaders will need to be proactive in promoting local connections to the networks to ensure high value from the connection.


See more on Interoperability

agario agario---betebet sohbet hattı betebet bahis siteleringsbahis