One of the biggest problems in healthcare is medication reconciliation. After patients have been written a prescription, they often don't pick them up, or if they do, they don't take them as prescribed. This inconsistency is not only a health risk to patients, but also a business risk to healthcare providers.

What it does

Pam is a simple software platform that helps patients manage their prescriptions, as well as give providers insight on their customers adherence. By integrating with an EMR system (electronic medical records), providers can continue to use the tools they are use to, but enhanced with statistics on medication reconciliation. Patients have the option to download a simple mobile app that will given them convenient reminders to take their medication and track their usage.

How I built it

Pam consists of three crucial applications. First, the minimalist mobile app for quick and non-intrusive prescription tracking, build with Ionic and Angular 7. This app is backed by a robust Spring API that collects usage data and can calculate adherence metrics per patient. Finally, the API integrates with an EMR (OpenEMR for the concept), so that the statistics can easily be managed with the tools that clinicians are using today. With our CI/CD pipeline, all of these pieces are continuously deployed in Docker containers to a cloud server.

Challenges I ran into

EMRs are large and complex systems, and many different types exist. For the sake of demonstration, we decided to create our own fork of the OpenEMR project and add new functionality to integrate with Pam. Writing PHP code for a legacy open-source system was a slow learning process, but the work was crucial to the vision of the project.

Accomplishments that I'm proud of

Integrating with the EMR was no small feat, and took a lot of effort from multiple team members. Everyone on our team has hackathon experience, but because of the integration work, this is the most production-ready hackathon project we've ever created.

What I learned

We all learned a vast amount about the healthcare field, specifically in improving patient experience. Working with mentors and domain experts gave us great insight on the issues they face, and they were happy to help us understand how we can help. None of the developers of our team were familiar with EMRs before this hackathon, so a lot of out time was spent learning how these systems are build and managed, as well as how they integrate with insurance companies and pharmacies.

What's next for pam

There are a number of features that we would like to add but did not have time to implement. First, more complete authentication, including user preference settings and security compliance. We also planned to add a machine-learning algorithm that could process the statistics we collect and calculate risk scores so that providers can make predictions on how patients will adhere to their prescriptions in the future. Finally, we want to enhance the practitioners' reporting portal to include more data visualization and user experience improvements (i.e. sorting, filtering, etc.).

Share this project: