Reliability and change at the same time
The portfolio required uninterrupted service while features, fixes, and policy-driven updates continued to move.
— CASE STUDY
Keeping federal health and insurance services reliable while they evolved
Maintaining and extending OPM Healthcare and Insurance applications
theta. maintained and extended a portfolio of OPM Healthcare and Insurance applications, pairing dependable operations with continuous product improvement. Across claims correspondence, benefits information, and plan-brochure workflows, theta. delivered stable service, new features, and accessible digital content.
— CASE STUDY
Keeping federal health and insurance services reliable while they evolved
theta. maintained and extended a portfolio of OPM Healthcare and Insurance applications, pairing dependable operations with continuous product improvement. Across claims correspondence, benefits information, and plan-brochure workflows, theta. delivered stable service, new features, and accessible digital content.
customer
U.S. Office of Personnel Management (OPM)
Contract Role
Subcontractor
Mission
Federal health and insurance services
Delivery Focus
Application operations, feature delivery, and accessible content
Capabilities
Build & Integrate | Secure, Test & Release | Enable & Transfer
Mission Context
OPM’s Healthcare and Insurance portfolio included a dozen applications serving claims, benefits information, and plan-document workflows. Those services had to remain dependable while policy, content, and user needs continued to change. theta. combined operations and maintenance with iterative development so the portfolio could stay available, absorb new requirements, and improve without separating reliability from product delivery.
Why it mattered
Federal employees, retirees, carriers, and program staff rely on accurate, accessible insurance information.
Federal employees, retirees, carriers, and program staff rely on accurate, accessible insurance information. A slow release process or unstable application can delay decisions, correspondence, and plan communication across a large benefits ecosystem.
The Challenge
Keep a broad benefits portfolio reliable while requirements change
A broad application landscape
Twelve connected applications introduced different technologies, users, and maintenance needs.
Accessible plan information
Benefits content had to work across web and document formats while meeting Section 508 expectations.
How theta. Delivered
One delivery model for operations and continuous improvement
Operated and improved the portfolio
theta. resolved defects, optimized applications, and delivered planned updates as part of one continuous product workflow.
Enhanced claims correspondence
theta. extended the FEHB disputed-claims Correspondence Module to support evolving program needs.
Improved benefits information
theta. maintained and expanded Benefits Plus capabilities across FEHB and FEDVIP data.
Modernized brochure production
theta. improved tools for producing health-plan brochures in accessible HTML and PDF formats.
Outcomes
Reliability and product improvement moved together
theta. kept essential benefits services dependable while continuously advancing the applications behind them.
Stable service with rolling delivery
Operations, defect resolution, and feature work moved together instead of competing for separate release windows.
More maintainable digital services
Targeted modernization reduced friction across claims, benefits, and brochure workflows.
Knowledge preserved for continuity
Structured documentation and transition practices protected operational knowledge beyond individual releases.
Built for What Comes Next
A sustainable foundation for future service changes
The portfolio left the engagement with stronger delivery routines, clearer operational knowledge, and a more sustainable foundation for future benefits-service changes.
Technical environment
Technology and delivery practices
.NET Framework, .NET Core, ASP.NET MVC, Docker, MongoDB, SQL Server, Entity Framework, AngularJS, JavaScript, jQuery, Knockout, Selenium, Jira, Confluence, and Azure
Have a complex mission to turn into a usable digital product?
Let us start with the policy, people, systems, and operating realities that shape the work.
Related work
Related case studies
CDOC
theta. kept essential corrections workflows moving while CDOC transitioned from aging custom applications to a modern enterprise suite. By resolving data issues, restructuring backend logic, and improving applications that would remain in place, theta. reduced friction in the legacy environment and created a safer path through a complex, multi-system transition.
VA
theta. expanded VA’s Rapid Ready for Decision approach to PACT Act claims, connecting claims workflows with existing health data so eligible cases could move forward with less manual retrieval and fewer avoidable exams. The work paired product strategy, prototyping, secure integration, and iterative delivery around the needs of Veterans and claims processors.
CMS
theta. advanced product direction and delivered API, authentication, and credentialing capabilities for CMS’s BCDA and DPC products. The work gave authorized organizations a more dependable way to receive Medicare claims data for care coordination, performance analysis, and value-based care.