Turning a Legacy Tool into a Platform for Growth

When a leading medical association needed to modernize a core internal tool, they looked for a team that would serve as a strategic partner, not just a technical vendor. SPR collaborated with them to boost productivity and innovation, reimagining the tool as a resilient, forward-looking platform.

The organization is the primary authority in pathology and laboratory standards in the U.S. It developed an internal protocol authoring tool, which is a system used to create and deliver structured cancer reporting templates to EHR and lab systems across the country. Since these templates are licensed to EHR and lab systems, the tool significantly influences the organization’s role in the clinical ecosystem and serves as a key part of its vendor relationships.

Over time, the tool (which was built as a desktop application using an Access/.NET stack) became cumbersome. It was hard for the team of domain experts (modelers) to keep up with changing cancer reporting standards and increasing metadata complexity. Even small updates required manual work and careful coordination. Stakeholders worried about bottlenecks: reliance on power users, slow revision cycles, and limited capacity to scale or connect with external systems.

The medical association needed a transformation. The goals were to:

• Improve user productivity and reduce friction for its modeling team
• Enable smoother delivery cycles even as content complexity rises
• Lay the groundwork for vendor integration via APIs
• Preserve their domain knowledge while modernizing the delivery platform
• Position the system to evolve (rather than decay) over the long term

Shared Understanding as the Foundation: We started by listening to the client’s challenges, understanding how modeling works, and gaining a shared sense of purpose. Over an onsite inception engagement, SPR led collaborative workshops that surfaced:

• How the organization’s modeling work really happens today
• What users struggle with or workaround
• What “success would look like, both in user satisfaction and business flexibility
• Core personas, prioritized user stories, and architectural constraints
• Risks, assumptions, and cost estimates tied to a future-state roadmap

This phase aligned the stakeholders (business, domain experts, and internal IS teams) around a clear mission: modernize the system without losing the nuance of years of modeling experience.

Roadmapping & Planning: From the inception, we turned ideas into a delivery plan. SPR and the client defined about 50 user stories for an MVP, with additional nonfunctional items (performance, versioning, support). We scheduled them into a sprint plan, assigned roles in a hybrid team model, and refined planning estimates using story points. The roadmap also included architectural guardrails: how much of existing infrastructure to reuse, where to draw boundaries, and how to phase in future capabilities.

Using the Legacy System as a Springboard: We view legacy systems not as problems to erase but as bodies of domain knowledge to honor and evolve. The organization’s original system was rich in embedded logic, such as template structure, transformation rules, metadata semantics, XML/HTML conversion pipelines. Though its UI and architecture were dated, the core modeling rules had evolved over years of careful work.

Our strategy was to use that legacy system as a launchpad. We didn’t throw it away. Instead, we extracted, documented, and migrated the domain logic into a refreshed architecture. This approach provided continuity: modelers could trust that the new system would adhere to familiar logic while gaining room to grow. It also reduced risk and rework, since we weren’t reinventing domain rules from scratch.

At the end of SPR’s inception engagement, the medical association had a shared direction. Business, domain, and technical stakeholders were aligned around who we were building for, what the MVP would include, and how to sequence effort.

The roadmap was supported by cost estimates, a prioritized backlog, and a sprint structure that integrated the team for learning and ownership. On the technical side, the design enabled both desktop and web options, secure vendor integration through an API gateway, and a modular architecture that could develop into microservices. Additionally, we maintained the existing SSP database for continuity while addressing its limitations in performance and flexibility.

The end deliverable was a launch plan for a modern MVP timed to the organization’s content release cycle. In business terms, the organization gained a transformation vehicle: a pathway from a constrained tool to a scalable, maintainable, extensible system. For SPR, this engagement reaffirms our way of working: deep partnership, clarity up front, and pragmatic modernization that respects domain know-how.

This modernization is a powerful example of how SPR helps organizations move beyond legacy constraints into future-fit platforms. We help organizations unlock safer, smarter evolution.