State Government Digital Modernization: The Legacy System Trap and How to Escape It

30+ yrs

Average age of state government IT systems â€” many running COBOL written before the engineers maintaining them were born

State government IT modernization fails at a higher rate than almost any other category of software project. The HealthCare.gov launch, California's DMV system, and Pennsylvania's unemployment system modernization share a common failure pattern: the new system was designed to replace the old system rather than to satisfy the federal compliance obligations, data integrity requirements, and operational constraints that made the old system indispensable. The modernization patterns that work preserve state data integrity, maintain federal compliance â€” MMIS, SNAP, Medicaid â€” and are built around the modular architecture CMS now requires for federal funding approval.

Full article content coming soon.

Architecture

The engineering behind this article is available as a service.

We have done this work — not advised on it, not reviewed documentation about it. If the problem in this article is your problem, the first call is with a senior engineer who has solved it.

Talk to an Engineer See Case Studies →

State Government Digital Modernization: The Legacy System Trap and How to Escape It

What Happens to Your HIPAA BAAs When You Migrate to Cloud

FedRAMP Rev 5: What Changed and Why Most Current ATO Holders Are Already Non-Compliant

HL7 FHIR R4 to R5: The Migration Nobody Budgeted For

The engineering behind this article is available as a service.