Implementation Questions and Challenges: May – December 2015
Although bringing the agencies together was a crucial first step, the department’s new leaders had to figure out how to make Snyder’s vision a reality. Officials began by crafting a diagram mapping the program’s clients and their needs. The exercise was revealing. Of the (approximately) 2.3 million Medicaid recipients in Michigan, 909,000 citizens also received food assistance, and 60,000 people obtained Medicaid as well as cash and food assistance. The agency had identified some of the state’s highest-need citizens and, as Becker said, now needed to “get at the core of their issues that are bringing them in our doors.”
The best way to identify these “root causes” was to put different programs in dialogue with one another, but with 140 programs accustomed to operating in silos, this was a formidable task. For one thing, the existing IT infrastructure had developed around Medicaid, so IT staff knew a lot about that program and little about others. This meant that disseminating program data—which was similarly segmented in different warehouses—would require retraining IT staff and crafting a system that transcends boundaries. “I wanted to take that [expertise] out and spread it horizontally across the organization where they can drive the change we’re talking about,” Becker explained, “and mak[e] sure that we’re cutting across the administrations and not just staying in the silo[s].”
DHHS leaders have begun that process by sketching a plan for a new online dashboard to help clients, staff, and different programs interact easily. The platform will have an online portal that clients can use to complete a needs assessment and work with staff to create a “success plan,” which will guide progress throughout clients’ time with the agency. Meanwhile, staff in different programs will be able to view comprehensive client profiles and communicate and share data across programs as they work to determine the best way to help the client. To Becker, this setup—and the collaborative process it would foster—was imperative to focus the agency on a client’s core needs. “It doesn’t matter how well we run our programs,” he emphasized, “if we don’t get back to the heart of the matter and ask the real question: what is it that brought the people to us to begin with?”
Supporting Social Workers
Another priority is easing the administrative burden on social workers. In recent years, some social workers in Detroit and Wayne County have been responsible for 800 cases. “You can’t possibly manage that,” Becker lamented. Other social workers have been overwhelmed because they have had to enter data from applications that are as much as 64-pages long. These critical public servants, Becker observed, “have become disillusioned because we’ve turned them into processors.”
DHHS is taking multiple steps to free social workers to work with clients. One is a plan to cull the initial client application to 12 questions. At the same time, the agency is trying to connect social workers with clients proactively. For example, Pathways to Potential, a program that began before the merger, has put social workers in 312 public schools across the state. DHHS is looking to apply a similar model in community mental health facilities. This will help social workers identify high-need citizens and, most importantly, contribute to the overarching objective, as Becker said, of “free[ing] up our social workers to be social workers again.”