New England Innovation: Collaborative IT Foundations for Accountable Care

January 18, 2013
| Reprints
Dr. David Wennberg shares his perspectives on the gains he and his colleagues are making in jointly laying the IT foundations for accountable care
New England Innovation: Collaborative IT Foundations for Accountable Care

David Wennberg, M.D., M.P.H., is CEO of the Northern New England Accountable Care Collaborative, a Portland, Maine-based collaborative organization founded by four hospital-based organizations in New England: Eastern Maine Medical Center (Bangor, Me.), MaineHealth (Portland, Me.), the Dartmouth-Hitchcock healthcare system (Lebanon, N.H.), and Fletcher Allen Health Care (Burlington, Vt.). Of those organizations, Eastern Maine and Dartmouth-Hitchcock are  Pioneer ACOs [accountable care organizations] under the Medicare Shared Savings Program, while Maine Health is a participant in the regular Medicare Shared Savings Program for ACOs; and the executives at Fletcher Allen Health Care are considering participation in one of those programs.

Wennberg spoke recently with HCI Editor-in-Chief Mark Hagland about the creation and development of the Northern New England Accountable Care Collaborative (NEACC), and about the IT foundations needed to facilitate accountable care. Below are excerpts from that interview.

Tell me about your organization?

Our owners are four health systems, and they’ve created what is essentially a shared services organization with a products suite and a services suite. And the products suite provides an intelligent infrastructure to support accountable care, but it also works for bundled payment and patient-centered medical home models.


David Wennberg, M.D., M.P.H.

How and when did your founding organizations come together to share services to support accountable care?

The conversation started about a year and a half ago, and we were officially incorporated in March. So essentially, the setting was that the Affordable Care Act had been published, including this concept of shared savings, but neither the regular nor the pioneer regulations had yet been published. But general information was out there, and there was enough interest in it in Maine. They thought they should save money on the initial investment, and could also learn from each other about how to do things better. They’re using the same data model and applications; their care models are all different. But all have the same basic financing model. The differences between the pioneer and regular shared savings model aren’t that great.

What are some of the mechanics behind the collaboration?

We integrate claims data from ADT [admissions/discharge/transfer] information, including, interestingly enough, via HealthInfoNet [Maine’s statewide health information exchange], whose leaders we’ve been working with. So we get access to ADT data statewide; and we get select data from EMR vendors, from Epic, from Cerner, from GE Centricity; and soon, we’ll get data from others as well. And we get laboratory data. We will be getting patient reporting measures later this year; and the data are integrated into a longitudinal, patient-centric data model.

Where do the analytics tools come into this process?

We use SAS a lot, developing new IT and predictive analytics models. And we use Crystal Reports for our presentation; and Business Objects as a hosted, cloud-based design; and we have applications for care coordinators, physicians, and administrators, that sit on top of the predictive models, and the Business Objects tools are used primarily by super-users who are accessing their own data warehouse. There’s a virtual data warehouse for each of the four systems. It’s a private cloud, actually sitting at Dartmouth College. And we do all the management, predictive models, and risk models, and it’s all served over the web, via web-based applications.

When did you go live with sharing of data or using data?

We went live earlier this month [January]. The first version of this solution is being used by care coordinators—some call them health coordinators or care managers; but it’s basically a patient list with clinical risk scores, recent events like admissions and transfers, admission or readmission risk, etc. And it has some areas for notation and planning, outreach calls, etc. So essentially, it’s a workflow tool. Initially, we’ve got about 75 care coordinators across three sites, about 25 care managers at each of the sites, using this; and the fourth site will eventually be determined. That’s for the first application.

Application two will be the physician view. Using that application, physicians will be able to use dashboards to compare the cost and quality of their care for their patient panel to those of their physician peers. And it will provide us all with regional benchmarking across all four participating health systems. In an ideal world, you could say, I’d like to find all my heart failure patients with a moderate or high risk of readmission whom we haven’t seen in the past three or four weeks; and you could instantly see where your opportunities for improving population health might be.

That approach would be similar to how some of the Beacon Communities are approaching population health, correct?

Exactly. And, when successful, a solution like that should be able to communicate to itself; you could say, I’d like to have the following 15 people seen, so it will essentially communicate within the system what needs to happen.

And application three will be the administrator application, which will provides the clinical and financial data.

And that’s where the heavier analytics stuff comes in?

Page
of 2Next
Topics