Client Profile

The Client is a prominent healthcare payment company in the US with expertise in payment collection that spans over two decades. Their products are HIPAA and PCI compliant and address every point of the payment process from eligibility verification to fully managed payment plans.

Client Requirement

The Client was trying to integrate changes in the system originally built in 2006 which was modified to suit the healthcare payments industry when the opportunity arose in the sector in 2009. Over the years, the system underwent numerous changes. The advent of tablets & mobiles and their immense popularity demanded corresponding changes in their legacy system.

Key Challenges

Feathersoft was roped into re-design their legacy system to a product architecture in the shifting business scenario. The challenges identified were as follows:

• Barriers to Scalability: The enormous database of the ever-increasing customer list was getting difficult to manage and had started affecting scalability.
• Risk of Redundancy: The legacy system faced redundancy risk every time new upgrades and patches were brought and it was unyielding to further changes.
• System Inflexibility: Incorporating the latest features and regulatory compliance requirements was not possible with the current inflexible system architecture and these technical updates were a requisite for business growth and stability.
• Extended Project Timeline: Legacy system migration was a challenge and revamping the whole system would take years to complete, threatening the collapse of a business that was meticulously built up over the years.

Our Approach

The consultants at Feathersoft suggested a multipronged product approach using the SOA (Service Oriented Architecture) framework to revive the legacy system.

• Service-Oriented Architecture (SOA): SOA made it possible to give flexibility to the legacy system ensuring the new user-friendly front-end coexist with the backend without breaking the old system.
• MVC (Model-View-Controller) Framework: MVC framework allowed reusable and extensible code that was easier to maintain. This made it possible to make changes in the front-end side on an iteration basis without much work on the back-end side.
• Features as modules: Each service or new feature that was added was developed as independent modules and the same was communicated through to the existing legacy system.
• Easy data management: Multitenant database architecture was used to ensure management scalability and performance.
• Effortless system maintenance: SOA based generic services increase reusability and its loosely coupled architecture helps extensibility and easy system maintenance.

Impact on Business

• Improved Application Performance: The Client derived significant improvement in application performance with the implementation of easy business process outflow.
• Data Security & Scalability: The implementation of Multitenant database architecture helped to store sensitive data in data centers complying with HIPAA guidelines. The front-end application was stored in the cloud to ensure scalability.
• Reduction in Cost of Migration: The cost of Migration was reduced to a tenth of what it would have incurred if the architecture was build up from scratch.
• Undisturbed business process: The phase by phase retiring of the old legacy system ensured the business system was not disrupted in any way.