Care Management Scoring Engine Case Study
This earlier .NET delivery work focused on turning business scoring logic into a maintainable XML-driven engine, enabling ASP.NET internationalization, and shipping critical custom application components ahead of schedule.
Impact Signals
Core Delivery
Problem
The application needed a way to evaluate a person's wellness based on survey answers and profile data, then use those scores to drive application behavior. The customer also needed content internationalization using ASP.NET resource patterns, but in a form that remained maintainable and testable.
My role
I delivered critical pieces of the custom .NET development effort, contributed design direction in architecture discussions, and built the scoring and content infrastructure that the application relied on.
Key engineering decisions
- Expressed the scoring model as XML so business logic could be updated outside the developer environment using tools such as InfoPath and Visual Studio.
- Designed the scoring engine so runtime behavior was driven by structured rules rather than hard-coded branching embedded throughout the application.
- Built an external resource provider for ASP.NET so internationalized content was easier to update and unit test.
- Used test-driven development throughout the project and pushed code coverage above 95% on the assemblies I wrote.
Outcome
The scoring engine and associated development work were completed two weeks ahead of schedule, reducing project risk and removing the need for additional developers that had originally been assigned to the effort.
Why This Work Still Matters
The stack was ASP.NET-era .NET rather than modern cloud infrastructure, but the design problem is still relevant: move decision logic into maintainable models, keep changeable business rules out of brittle code paths, and make configuration updates safe for the people who actually need to evolve them.
That same pattern still shows up in platform and control-plane systems, where durable workflows, policy evaluation, and externalized configuration must remain testable rather than becoming hand-maintained code tangles.