Did you know that women who had heart disease, stroke, or autoimmune disease were far more likely to be initially misdiagnosed compared to men? When it comes to levels of pain, women tend to experience it more than men, and therefore often have their pain disregarded when getting a diagnosis. This situation applies to many other groups as well and unfortunately leads to a worsening of illness in many cases. Because of this, we wanted to build a tool that can help doctors make accurate diagnoses and prevent the careless dismissal of valid concerns and symptoms.
What it does
PainPoint is a software designed to improve communication between doctors and patients, especially with regards to pain perception. Each person has their own ways of perceiving pain and varying pain thresholds, which make understanding pain levels using traditional methods particularly difficult. This is where PainPoint comes in.
PainPoint asks users a series of questions to gauge their tolerance to pain. Various potentially painful scenarios are given, and users are asked to rate the amount of pain they would experience on a scale from 1-10 (1 is least painful, 10 is most painful). If the user does not have an answer, or if the scenario does not apply to them, they may choose to select 'N/A'. Then, the PainPoint algorithm calculates a normalized pain score for the user after comparing their pain tolerance scores to the mean pain tolerance scores of other users.
The result of PainPoint is a more normalized way of measuring pain in patients, which will aid physicians and healthcare workers in understanding how a patient feels and how to better treat their pain. The result is smooth communication between and patient and the provider and a more positive healthcare experience.
How we built it
PainPoint is built off a Python web development tool called Dash. We connected an authentication and database service called Firebase to our Python web application to store login info, and personal data for users of our service.
Challenges we ran into
We had some issues figuring out how to put together the different components in our project, especially because all of us were new to several of the tools we used to build this project.
Accomplishments that we're proud of
We all came away from PainPoint with experience in a new tech stack. Only one person on our team had used Dash before, and we worked really hard to educate ourselves about unfamiliar technology and use it effectively. Also, we are really proud of the communication skills we displayed despite the online nature of this hackathon. Even though many of us had never met before, we were able to come together virtually to create a project that can make a real impact!
What we learned
Dash & Firebase - While one team member had some prior experience using Dash for web applications, most of us were new to using the platform. We also learned to use Firebase as we worked on the project.
What's next for PainPoint
Our most important next step is growing our database to be as representative of the demographics of our user base as possible. We would also like to build out a "pain profile" for individual users, which can help them understand which types of pain they are more or less tolerant to in order to better assist them in diagnostic processes .