An Innovative App Development for Healthcare Industry

Patient360

The purpose of Patient360 is to assist practices with improving quality, increasing incentives, and preventing payment adjustments by CMS. A Qualified Clinical Data Registry (QCDR), Patient360 also offers Orthopedic Neuromuscular and Osteopathic Manipulative Medicine (NMM/OMM), Chiropractic, Physiatry, Physical and Occupational Therapy, Podiatry, and Sport Medicine. The P360 has been submitting data to CMS since 2015 on behalf of more than 5000+ NPIs and 500+ TINs.

Business Idea and Challenges

“P360 shows practice scores in advance of submitting the data to CMS, so clinics can adjust their records to raise the score.”

Chris Watson, chief strategy officer at Brightree

Challenges

Bulk data processing: Clinics send patient data in different forms, which P360 has to convert into a single form, so it can be submitted to CMS.
Keeping an eye on CMS: CMS frequently changes its regulations, so P360 has to make sure that any change is quickly updated in the system so clinics can verify that.

A Successful Report Starts Here

The practices have to include all relevant details, such as NPI, TIN, patients’ details and diagnosis reports. Once P360 receives patient data from practices, it will process the data and generate the Score Preview which will be very similar to the actual score for the clinics. The clinic will verify the score and can make changes to their data until they are satisfied with the results.

01
Strategy

Development span for such applications like Patient360 is always gradual with a base focused on core functionalities. Started with a very small team of software engineers gradually teams of more than 10 members on shore and offshore.
02
Engineering

Development span for such applications like Patient360 is always gradual with a base focused on core functionalities. Started with a very small team of software engineers gradually teams of more than 10 members on shore and offshore.
03
Modernizing

Development span for such applications like Patient360 is always gradual with a base focused on core functionalities. Started with a very small team of software engineers gradually teams of more than 10 members on shore and offshore.

Modernizing Application for
Security and Stability

Version Migrations

In keeping with the open source nature of both Ruby and Rails, we need to adhere to industry standards practices as software engineers. The engineering team decided to upgrade Ruby and Rails periodically. It took around 1 to 3 months for each upgrade phase which includes recode, test and deployment on the server.

Infrastructure Migrations

Initially, Patient360 was hosted on Heroku server which took approximately 1 to 3 months to upgrade each phase, which included recording, testing, and deploying on the server.h a single server and a number of background jobs, including workers and cron jobs. Patient360 moved to Google cloud due to the increasing number of clinics and their data. Infrastructure migration took around six months, which included setting up servers, creating security policy, migrating storage data, and installing background servers.

Innovative product that helps the healthcare industry work more efficiently

Login / Create / Manage Account

User’s manage login information in an account. you can manually manage a user’s login information in an account.

Select Your Measures

MIPS Beginner Reporting (M4B) is an excellent choice for practices that have not participated in Medicare reporting before.

Add Your Data

Successful MIPS 2019 reporting will ensure that practices do not receive a negative payment adjustment and offers potential for bonus with exceptional …

Review & Submit

QCDR Reporting is the best option for practices that have limited MIPS Quality Measures to report under the traditional MIPS Registry Quality Measure options.

Business Idea behind Patient360

Most of the time, clinics submit their data directly to CMS without understanding the consequences. The resulting low quality points affect their payment adjustment. P360 provides scores to practices in advance so they can change their data to increase the score before submitting it to CMS.

"Development was taking place round the call and rapid development/deployment cycles taking place periodically as going through many conferences, CMS update and customer review meeting helps production to evolve in regular phase."

Chris Watson, chief strategy officer at Brightree

Impact by Numbers

41
Sessions

Started with a very small team of software engineers gradually teams of more than 10 members on shore and offshore.
63
Organic search traffic

Started with a very small team of software engineers gradually teams of more than 10 members on shore and offshore.
35
Pageviews

Started with a very small team of software engineers gradually teams of more than 10 members on shore and offshore.