Mediscope

Mediscope

Inspiration

Many people are hypochondriacs, and many are also the opposite. When those stoic people ignore their symptoms and try to stay home, bad things can happen for those at home and those at the hospital. When someone does not make it to the hospital in a timely manner, it can result in a life-threatening situation for the patient who delayed their visit to the physician. Our application is one that can solve that problem while also giving the user a gauge to whether or not they actually need to go to the hospital or not. We as a team wanted to help those who possibly do not know of certain conditions that can be dangerous if left alone, and we wanted to give them an easy way to contact their physician as fast as possible. COVID-19 has also left a lasting impression on us as many people with symptoms have ignored them and not gone to the hospital only to be left in dangerous situations at home. By creating Mediscope, our team wants to put an end to the harm that COVID and other dangerous conditions can cause.

What it does

Mediscope is an application that is able to take patients' data and help them schedule appointments with their Primary Care Physicians. It can take in different symptoms that a patient may be feeling and give them advice about whether or not they need to go to the hospital immediately or if they are not in danger. It logs previous risk scores and displays them to the user to show their medical records in a more simplified way. Mediscope displays current health events that are relevant to the user and gives them information on their Primary Care Physician, and the application can also schedule appointments with the physicians. Medicare also has functionality for physicians as well by having the ability to show them how many patients they have and what symptoms they have for that day while keeping the name of the patient secure.

How we built it

We began by building the front end of our site. Our mockup was based on similar dashboard formatted webpages. We used HTML, CSS, and Bootstrap to build these pages. We worked with python on our backend, which uses Cloudant as a database that stores JSON documents to contain patient information. We then ran form responses into the IBM RiskAPI we chose to work with to output a rating of the patient's health risk, which is returned to the frontend on both the patient dashboard graph and doctor side where they can schedule an appointment.

Challenges we ran into

We were unable to use Google Oauth for the login page because no one in our group had a GSuite account. We built a static login page instead. We also had trouble working with the particular RiskAPI we chose because we had to get authentication from the third-party creator.

What we learned

We learned many different things while making the application, some things might have been worse than others, and some things were not even related to the project directly. From learning what we do like to do, such as doing front-end work or back-end work to figuring out how to use Discord to work with others and researching bots that would play music. We learned how to work together on a project by dividing our work up into smaller pieces and getting things done bit-by-bit. Overall, it was a positive learning experience for us as students and as future developers

Accomplishments that we're proud of

While working on this app we have accomplished many different things that we are proud of. One instance is that we had one group member who had no deep experience with front-end development. While working on this app we were able to get them to learn more about what front-end development is and they were able to contribute to some of the front-end of the project as well. Another thing that we accomplished is getting a domain name through Domain.com and we were able to route our website through this domain and have it work completely fine. We also were able to use the APIs correctly and we were even able to talk with the higher-ups who made the API that we implemented into our application.

Built With

Submitted to

HackRPI Fall 2020
- Winner [Wolfram] Top 15 Teams
- Winner [MLH] Best Domain Registered with Domain.com

Created by

I worked on the concept and design of the page taking inspiration from other dashboard formats. I created a mockup of the site before we began building it, and I also built out the front end of the website using HTML/CSS and Bootstrap. I made our business model presentation in google slides.

Charlie-01 Stanton
I worked on the backend team and was responsible for creating databases using cloudant and python. It was my first time using cloudant so it was a little difficult at first but I was able to figure it out. I was also responsible for creating the API that accessed the information in cloudant and sent it to the front end using a flask server.

Sage Charity
I worked on the front-end design of the website as well as gathering the data from the form fields and sending it to the backed server and database. I used bootstrap as the main framework for the website, but this was not my first time using bootstrap for a website, so I was a bit experienced with working with the grid system and such. For gathering the form data and creating the JSON object, I used JavaScript. It was not my first time using JS either so I was a bit experienced in using that technology as well.

Rupak Stephen
I was the primary back-end developer for the site. The site utilized a document-object style database (CloudANT) rather than a SQL based database which was an interesting learning curve for myself. This was also the first RESTful API service I've created through the python-flask library. The flask API handled the mediation between our front and backends, allowing for JavaScript functions to request data from our database as well as remove/update data in said databases.

Sean Hale

Updates

Charlie-01 Stanton started this project — Nov 08, 2020 10:34 AM EST

Leave feedback in the comments!

Log in or sign up for Devpost to join the conversation.