ACOs were billed as the next big thing in healthcare, a model which would create economies of scale and tame rising costs of care. In theory, unifying hospitals and doctors into an overarching entity – and creating shared clinical and financial goals – should improve care and boost efficiency.
Of course, creating them doesn’t come cheap. In fact, creating even a modest ACO typically calls for between $1 million and $3 million in capital investment, according to Michael Deegan, MD, who recently developed a course on ACOs for the University of Texas at Dallas. It also takes 18 to 24 months to launch an ACO, Deegan told an interviewer at UT.
But once all of the Ts have been crossed and the Is dotted, ACOs can meet their stated goals, right? Actually, not so much, though health IT can help things along, according to Indranil Bardham, a colleague of Deegan’s at UT Dallas who serves as professor of information systems.
According to an article in HealthcareITNews, Bardhan recently completed a study on ACO performance which concluded that health IT had a measurable impact on their efficiency. The study, which drew on 2013-2015 data from CMS, reviewed the performance of 400 ACOs.
Among the key takeways Bardhan took from his research was that the larger an ACO was, the more likely it was to be inefficient. This flies in the face of conventional wisdom, which would suggest that bigger is better when it comes to improving efficiency.
On the other hand, health IT use had the effect its champions might hope for, though modest in scope. The study concluded that a 1 percent increase in HIT usage was associated with an 0.5 percent increase in ACO efficiency.
The thing is, these measures represent just a couple of ways to evaluate ACO performance, making it hard to tell just what is working, Bardhan told HIN. “Healthcare, with respect to ACOs, is fascinating because there is not just one single output measure that you are using to compare performance,” he told the magazine’s Bill Siwicki. “…It is difficult to measure the performance of organizations against each other when you have multiple outputs that cannot easily be transformed into a single dollar number.”
This squares with commentary by other ACO researchers, who seem to agree that the whole ACO evaluation process is a bit mysterious. As health policy analyst David Introcaso notes, in a review of ACO-based Medicare Shared Savings Program, CMS isn’t helping either. “While CMS details financial and quality performance results, the agency does not explain, at least publicly, how results, favorable or unfavorable, were achieved.”
Without knowing more about what we should measure, and why – much less what steps helped in achieving their results – it’s too soon to tell what type of health IT should be deployed in ACOs. But looked at more optimistically, once we have a better idea of what ACO success factors are, it seems likely that health IT tools will help execs address them. (For a look at one completely health IT-based ACO concept, see this piece on the Virtual ACO.)