In Part I of this series I noted that we have almost no useful information on what ACOs do that affects cost and quality. I described two causes of that problem: The amorphous, aspirational “definition” of ACOs, and the happy-go-lucky attitude toward evidence exhibited by ACO proponents and many analysts. I showed how the flabby “definition” of ACO makes it impossible to operationalize this thing – to reduce it to testable components. And I asked why the health policy community let ACO proponents get away with such a vague description of the ACO. I said the answer lies in the permissive culture of the US health policy community. It is a culture that tolerates, even encourages, the promotion of vague concepts and a cavalier attitude toward evidence.
In this installment, I illustrate these problems – the vague definition of “ACO,” and loose standards of evidence – by examining a paper published last month by the Center for Health Care Strategies (CHCS) entitled, “Accountable Care Organizations: Looking back and moving forward.” In the third installment of this series I will describe the emergence of the health policy culture that tolerates intellectually flabby proposals and a devil-may-care attitude toward evidence.
I chose the CHCS paper because the organization that funded it, the Robert Wood Johnson Foundation, and the organization that wrote it are prominent advocates of managed care and its latest iteration, the ACO. The Foundation describes itself as “an early supporter of the idea that later became known as managed care” T
Moreover, the paper’s authors and funders made it clear they hoped the paper would provide a useful update on what ACOs have accomplished and how they accomplished it. In its July 2015 announcement of the $20,000 grant that supported this study, the Foundation said the study would “inform stakeholders of progress to date by accountable care organizations.” CHCS’s paper claims it “identifies key lessons from ACO activities across the country to date” (p. 1).

The term “Big Data” emerged from Silicon Valley in 2003 to describe the unprecedented volume and velocity of data that was being collected and analyzed by Yahoo, Google, eBay, and others. They had reached an affordability, scalability and performance ceiling with traditional relational database technology that required the development of a new solution, not being met by the relational data base vendors.