-
-
Intro Screen
-
The full body screen, users can select which general area is hurting.
-
A specific ending screen. The icon on the left can be sent to the nurse.
-
Another example, using a different section of the body.
Inspiration
Our inspiration for this project came during the researching portion. When we started out, we didn't have any concrete ideas of what we wanted to create. However, after talking with some friends and people associated with the healthcare industry, we found something that we wanted to support. We found out that healthcare workers, especially nurses, are often overworked. So to help them out, we wanted to create some type of tool that could reduce their workload.
What it does
Where are you Hurt?, is a simple application that runs can run on your browser. It starts by asking for pertinent information, then gives a diagram of the human body. The user will select the general area where they are in pain, and it will take them to a more detailed view of that area. From there, once they select a specific location, a meter will show up, asking the user to rank their pain on a scale from 1 to 10. Finally, an icon containing all the relevant information will appear, and this can be sent to the nurse to prevent them from having to determine that information themselves.
Why should you use this?
The goal of our tool is to make use of the time spent in the doctor's office waiting for an appointment in a more constructive way that will benefit the patient, doctor, and nurses. It's simple interface is access-able and easy to use, and it's heavy use of visuals means it can be easily implemented all over the world. Since the wait in a doctor's office is often caused by an overflow of patients, a tool that takes the time of the patients to reduce the time spent by the doctor and nurse will provide benefits to both parties.
Challenges we ran into
Since the two of us are both relatively new to programming, we ran into many issues with the Unity game engine, as well as C#. For example, we spent a large chunk of time tossing ideas back and forth on how to transfer variables between different scripts and objects in the code. We also had to come up with a good way to display our code. We didn't want to require users to have to download something to use our program, so by using WebGL, we made it simple to access our code straight from the browser.
What we learned
After this project, we've both come away with new skills and a new level of understanding of the healthcare industry. Our coding skills have improved, and we've learned to use new tools and features to help further our future projects. We've also learned the value of time management and taking breaks, which helped to improve our concentration and efficiency while working. We both definitely underappreciated the work that these people do before starting this project, and by working on it, hope to give back to them as thanks for the hard work that they do.
Log in or sign up for Devpost to join the conversation.