Jun 21, 2007,
That's because meeting HIPAA standards requires the mainframe and minicomputer systems of social services, human services and health departments to interact.
To induce this intermingling, South Dakota would have had to put COBOL programmers to work writing programs to extract data from one system to deliver it to users in another department, said state CIO Otto Doll.
"The problem with that approach," Doll said, "is that when you make a change to any application, you also have to go back and change all those interfaces you've written."
Dissatisfied with the state's legacy system silos, Doll has gradually moved South Dakota toward a service-oriented architecture (SOA). Using translation middleware, South Dakota has started building composite applications using adapters that can pull data from separate sources.
For the past few years, SOA has made HIPAA compliance much easier, Doll said. For instance, human services employees enrolling people in Medicaid can now access birth and death records from the Department of Health.
Doll said South Dakota got serious about the enterprise application integration (EAI) approach in 2000. "We saw a need to extend the longevity of these systems," Doll explained. "We don't have the resources to refresh our systems every couple of years. Nevertheless, we've been able to move forward with more complex interactions and access to different applications whether they are old or new."
South Dakota's IT leaders aren't the only ones feeling pressure to link up data from older systems. Increasingly government services are intertwined both within and across agencies. Yet CIOs find themselves inheriting a hodgepodge of servers, mainframes and minicomputers that are difficult to integrate and don't lend themselves to business intelligence-type queries.
That may explain why the worldwide application integration and middleware market grew at a 7.1 percent clip between 2004 and 2005 to total $8.5 billion, according to Gartner.
The challenge of legacy data integration is most acute in the public sector, because unlike their private-sector counterparts, government agencies typically can't afford to regularly replace systems.
Please visit Public CIO's Web site to read the full story in the upcoming June/July issue of Public CIO.
Read real world deployments of technology in government from our sponsors.
View All Industry Solutions
Latest Government Technology News