DARWIN
Modernising benefit configuration on an existing platform.
We migrated a defined part of a legacy platform to Angular and .NET: the configuration pages where teams manage client, plan and group rules.
Explore the configuration workspaceconfiguration pages rebuilt
Configuration context and code-level actions.
Category navigation
Benefit categories organise the settings into sections. The selected configuration remains visible as staff move between its rules.
Parent configuration
Client, plan and group settings identify the scope of each rule before it is edited.
Code-level actions
An expanded record exposes individual codes, their actions and rejection details within the selected configuration.
Shared components across pricing and benefit limits.
Pricing and accumulator settings share search, dates, selectors and field help. Reusable components give each new configuration page an established structure.
Pricing options and effective dates.
Section search, pricing selectors and effective dates are grouped in the same form. Field help accompanies the values that staff review and save.
Deductibles and out-of-pocket limits.
Deductible and out-of-pocket settings reuse the same navigation, selectors and form controls. Each page keeps its business rules while sharing the underlying interface components.
Component reuse and backend refactoring.
The migration also addressed how the application was organised, how components were reused and how requests reached the backend.
- 01
Architecture and delivery review
Reviewed the application architecture, development and deployment process, and proposed improvements for the migration.
- 02
Reusable frontend components
Built shared controls and refactored the component structure used across the configuration pages.
- 03
Request handling and backend refactoring
Restructured backend code and improved request handling and data processing for the new interface.
The technology behind DARWIN.
The stack used for the migrated configuration area.
Configuration interface
Angular 15 and TypeScript support the configuration interface and its reusable components.
API & database
C# and ASP.NET Web API on .NET 6 handle application requests, with MS SQL Server for the database.
Start with the workflow your legacy system holds back.
Bring one configuration area, its business rules and the systems it depends on. We will define the migration boundary, reusable components and checks needed before replacing the existing screens.
Plan a focused migration