{
  "@context": "https://schema.org",
  "@type": "Article",
  "@id": "https://www.vidyasource.com/case-studies/healthcare-gov-modernization/",
  "url": "https://www.vidyasource.com/case-studies/healthcare-gov-modernization/",
  "mainEntityOfPage": "https://www.vidyasource.com/case-studies/healthcare-gov-modernization/",
  "headline": "Making HealthCare.gov More Than 30% Faster for CMS",
  "description": "CMS saw HealthCare.gov performance rise more than 30% after Vidya's Java to Scala rebuild on AWS. A federal healthcare system modernization case study.",
  "about": {
    "@type": "Organization",
    "name": "Centers for Medicare & Medicaid Services (CMS)"
  },
  "author": {
    "@id": "https://www.vidyasource.com/#organization"
  },
  "publisher": {
    "@id": "https://www.vidyasource.com/#organization"
  },
  "image": "https://www.vidyasource.com/img/blog/health-care-gov.jpg",
  "keywords": [
    "Modernization",
    "Government",
    "Architecture",
    "Java",
    "Scala",
    "Functional Programming",
    "Testing",
    "Scala",
    "Java",
    "Play Framework",
    "Spring",
    "AWS",
    "Java Virtual Machine",
    "ScalaTest",
    "ScalaCheck"
  ],
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What was Vidya's role in the HealthCare.gov modernization?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Vidya worked as a subcontractor to Accenture Federal Services, which held the prime relationship with the Centers for Medicare & Medicaid Services and carried the overall program. Vidya's scope covered a portion of the platform, where Vidya wrote production Scala services and mentored more than 20 Java developers. Vidya makes no claim on the parts of HealthCare.gov that other teams delivered."
      }
    },
    {
      "@type": "Question",
      "name": "How much did HealthCare.gov performance improve?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "HealthCare.gov performance improved by more than 30 percent across the work Vidya's team delivered on the move from Java to Scala on AWS. Vidya cites that figure from its own engagement record rather than a published CMS benchmark. The gain came from how the code was written and not from new hardware, because Scala's Future let the checks an eligibility determination makes against outside systems run at the same time rather than one after another."
      }
    },
    {
      "@type": "Question",
      "name": "Would Vidya use Scala for this work today?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Vidya proposes other technologies for enterprise modernization. However, what carries forward is the discipline the language enforced. Vidya still writes business rules so the build rejects any combination the statute does not allow, still makes missing data impossible to overlook, still composes complex workflows from simple rules, and still runs API calls in parallel for better scalability. Simply put, use technologies that make it harder to write bugs. A program office should choose the programming ecosystem according to that principle. Ask us for suggestions."
      }
    },
    {
      "@type": "Question",
      "name": "How does Vidya approach high-traffic government website scaling?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Vidya measures the slowest thing an actual user waits on and fixes that one before anything else. On HealthCare.gov the busiest pages spent their time waiting on outside systems, so Vidya made those checks run at the same time and recovered the wait without asking CMS to buy capacity. Vidya then measures the result so the program office can show its stakeholders a before-and-after number, the way this work produced a figure above 30 percent."
      }
    }
  ]
}