case study

Approved Admissions

How we Moved a Complex Cloud-Based Eligibility Verification Platform

Approved Admissions points
Question
HAVE YOU EVER FACED

an issue of legacy code limitations and low performance?

As soon as Approved Admissions experienced the danger of becoming outdated, they started to plan the migration to the newest .NET Core version and referred to our team for assistance.

About the Client

Approved Admissions is a cloud-based eligibility verification platform that monitors and reports changes in Medicare, Medicaid, and HMO payers. Healthcare organizations benefit from its automatic re-verifying system that notifies them of any changes in payer coverage minimizing billing errors.

Due to the company growth, the code, written five years ago, started to show its limitations.

So stakeholders wanted to improve the platform performance and reduce the per-transaction cost. Their secondary goals were to improve the horizontal scalability and internal security of the platform.

How Approved Admissions Meets the HIPAA Compliance Standards

HIPAA

CLIENT

Query

Reports & Notifications

APPROVED ADMISSIONS

Query

Encrypted data

01

02

03

The client deals with healthcare insurance payments and HIPAA compliance, so security, great performance, and accuracy were the main priorities of this project.

What Made
Approved Admissions Migrate from MVC to .NET Core?

On-time software modernization is a must for any business, especially a digital one.

However, AA, just as most companies, had certain reasons to start this project, namely:

declining
support for MVC

Microsoft provides extensive support for .NET Core, and there are many open source solutions that speed up the development process.

decreasing
talent pool

Over time, it was becoming more and more difficult for AA to find talents to work with Microsoft ASP .NET MVC platform.

The need
to improve performance

The speed of the app built with .NET Core is far better that is crucial for end-users.

ASP.NET MVC Compared to .NET Core

.net framework
.net core
Perfomance & Scalability Average perfomance High perfomance. Runs with a much lower number of servers/Virtual Machines (VM). The reduced servers/VMs save costs in infrastructure and hosting
Maturity Released in 2002 Released in 2016
Cross-Platform Runs on Windows Only Runs on Windows, Linux and macOS
Owner Microsoft .NET Foundation
(fully open source and collaborative.)
pie

The Challenges We Faced in
This Project

Migration of any system in use is
always challenging, as its clients
shouldn’t feel the shift.

WE HAD TWO
TECHNICAL ISSUES

The disparity in technologies

In .NET Core 3.1, the Membership Provider was replaced with ASP.NET Core Identity that uses Entity Framework as an object-relational mapping solution. AA system used NHibernate which was incompatible with .NET Core 3.1, so we had to find a way to continue using it or find an alternative to it, and migrate users with their current roles and passwords to the new platform.

Missing suitable substitutes for existing tools

In ASP.NET MVC the system used MvcSiteMapProvider that was quite outdated. Therefore, we should find a suitable substitute, which would be compatible with MvcSiteMapProvider configuration files.

Planning as an Important Groundwork

First of all our team performed an analysis stage where they divided NuGet-packages used in the system into two groups - supported in .NET core and non-supported.

In AA’s case, most of the application code was custom; that drastically simplified the migration process.

After that our engineers prepared for the migration of framework built-in technologies like Membership Provider and Dependency Injection.
orange

ModLogix Suggests

There are situations when it’s more efficient to re-write some of the app modules from scratch. This is a bright example when there is no fitting tool for change, and rewriting it for a new system would take too much time and, consequently, money. Save resources!

Technologies
and Tools We Use

SCOPE OF WORK :
6 MONTH
2 DEVELOPERS
1 TECHLEAD

Results

18% faster
page loading
LTS
support
3x lower
per-transaction
costs

As a result of jQuery plugins cleaning, we managed to clear 10 megabytes of data (800 spare files) which could have been loaded in a client’s browser. It would mean more traffic and longer loading.

The client has got the newest framework (.NET Core – 3.1) marked LTS - long-term support, that means it will be supported for a long time, it will be easy to broaden the platform and to migrate it next time.

The client was able to reduce per-transaction cost by more than 300% and exponentially increase performance. It is also more secure and stable than before. AA management expects a positive ROI as a direct result of this project within the next six months.

Results

Key Takeaways

Before doing any migration activities determine which parts of the app or code can be reused, and which should be rewritten. Those parts are critical and should be performed primarily.

Continuous testing during and after the development process is super important in such projects. Even a little button can start working in the wrong way and crack the whole app if we are talking about migration.

Re-organize and clean the code if needed. It will be much easier to develop the system and implement new features in the future.

Client Review

We are delighted to be working with customers in a variety of industries and verticals.

quotes
michail
prev
orange

Our Team
on This Project

Andrew
Andrew
software engineer

only challenges
can enable growth

Though I have been working with similar projects, some tasks here were challenging for me and my teammates. But only challenges can enable growth, so we are thankful to our client for this great opportunity to sharpen skills. Approved Admissions one of those easy-to-work clients, and we will be happy to continue cooperation.

quotes

Let’s Start a
Conversation

Share your challenge with us – we want to hear from you

* Please enter your name
* Please leave a message





    elipse