People are dying. It already takes enough time for paramedics to reach the patients, so it's even worse that they must use additional time to diagnose them. What if there was a way for bystanders, without any professional medical training, to accurately diagnose a patient before the medics even arrive? Introducing WebMD 2.0.
What it does
The user must check off symptoms of the patient from a list of 271 symptoms. Based on the user's selection of symptom(s), WebMD 2.0 will give a list of possible diagnoses, sorted from most probable to least likely.
How we built it
Java, Android Studio, XML, and APIMedic.
Challenges we ran into
Setting up, incompatible hardware, pre-planning, Java's inability to easily import external libraries, and splitting up tasks evenly.
Accomplishments that we're proud of
We got a working build of our project (big s/o to Ryan Walsh). Successfully implemented APIMedic for our project. Learning everything about Android Studio (GUI, IDE). Thinking up a useful app that can potentially save lives.
What we learned
Java cannot easily import external libraries. Java has its fair share of limitations. Pre-planning before a big project is extremely important. Version controlling is extremely useful once mastered. Dividing up the work would have helped a lot. Planning ahead on what environment we want is important.
What's next for WebMD 2.0
Implement a classification tree. This will allow us to give faster and more accurate diagnoses. The user will first choose symptoms from a list of very simple, easily recognizable symptoms. Then, based on the chosen symptoms, the list of symptoms given will be specific and advanced (Think Akinator). Implementing the app's ability to suggest simple, quick treatments that instruct the user on how they can relieve the patient's pain before the medics arrive.