The legacy systems were on a state-by-state basis, so such a list would be exhaustive. At the federal level, it had to tie to IRS, FBI, INS, SSA, Medicare, Medi

The legacy systems were on a state-by-state basis, so such a list would be exhaustive. At the federal level, it had to tie to IRS, FBI, INS, SSA, Medicare, Medicaid, and others. Each of these systems have their own extensive security rules as well, so something like authenticating users is a real pain. And there's fraud potential too. On top of that, consider that the system needs to serve populations that are, shall we say, less sophisticated in the ways of technology and finance than the average startup's customer base? When I worked on a state system, we called it the "Amish problem", because our state has a significant Amish population. There are people who don't read. People who don't speak English. People who are absolutely terrified of authorities. People who have religious beliefs that isolate them from computers. It's difficult and ugly.