Success Story Healthcare

US Healthcare Payer Launches Hybrid App & Adds 100K+ New Users

Enhancing user access and security

As the healthcare landscape rapidly evolves, payers must reimagine themselves to support the delivery of better quality healthcare services and improve customer experiences.

The customer, a Michigan-based payer, wanted to expand their active user base and improve engagement with its 1 million policy members by being available on multiple channels. They also needed to be compliant with regulatory requirements while improving stakeholder collaboration and enhancing user access and security.

The challenge

3 key areas

Exhaustive scrutiny of the customer’s existing processes exposed various challenges like:

Reduced Growth

Reduced Growtht Slack in member registration that impaired the growth of active user base

Inadequate Engagement

Inadequate Engagement Lack of adequate engagement with policy members

Non-availability

Non-availability Non-availability on multiple channels

The Solution

11 key areas

By adopting a design thinking approach, Apexon worked with the customer to come up with wide-ranging member convenience solutions that included:

Hybrid Mobile App Development

Hybrid Mobile App Building a hybrid mobile app supporting multiple devices and form factors

Ensuring compliance to regulatory requirements

Ensuring Compliance Ensuring compliance to regulatory requirements (PHI, PII, and HIPPA)

Clear SLAs & KPIs

Clear SLAs & KPIs Defining clear SLAs and KPIs for successful delivery

Automating the regression tests

Better & Faster Releases Automating the regression tests for better and faster releases

Performance Engineering Investment

Performance Engineering Investment Investing in performance engineering to ensure the app scales for the expected load

DevOps with continuous integration

DevOps DevOps with continuous integration and test automation

Leveraging CoEs and industry best practices

Best Practices Leveraging CoEs and industry best practices

Releasing an MVP version within 3 months

MVP Version Releasing an MVP version within 3 months

Executing the project’s first release

First Release Executing the project’s first release with an average team size of 19 FTEs for 9 months 

Delivering the project in 80:20 offshore to onsite ratio

Offshore Vs Onsite Delivering the project in 80:20 offshore to onsite ratio

Delivering production releases

New Features Delivering production releases with new features every 2 months