Medverse

Landing Page + agar.io
Clerk authentication + login
Our top diagnosis page, based on upvotes and comments of the day.
Our top diagnosis page but in dark mode!
A diagnosis post where a user shares information on a patient in compliance with HIPAA.
Comment section given by other accreddited doctors based on the HIPAA approved information shared.

Inspiration

Patient safety is an issue very close to my heart; my father was misdiagnosed with lung cancer when he actually had Chronic Obstructive Pulmonary Disease (COPD). This led to us spending valuable time and money on unnecessary cancer treatments, such as chemotherapy, when we could have been managing his COPD more effectively from the start.

What it does

Our project Medverse aims to reduce human error, involving more qualified humans into the diagnosing process. For tech people, think of it as stack overflow for only licensed medical professionals. Medical professionals will share a diagnosis anonymously that they are unsure of, and people in the same field can give their two cents on it.

How we built it

In the frontend we used React, Next.js, TailwindCSS, OpenAI and Typescript. The backend was built using JavaScript, Express, MongoDB, and RSA encryption. We deployed our application using Google Cloud's Cloud Engine and our domains were form GoDaddy.

Challenges we ran into

Over the weekend, we faced a series of challenges. Our initial plan to deploy our application using containers hit a roadblock due to system incompatibilities with Google Cloud's infrastructure. We had to quickly adapt and shift our development environment to the Google Cloud Code Shell. Additionally, integrating MongoDB proved to be complex, as we worked to ensure it functioned smoothly within our application's architecture. These challenges tested our technical skills and pushed us to find innovative solutions under pressure

Accomplishments that we're proud of

We have fully integrated our system with Google Cloud's services, deploying our application on their platform and incorporating the Healthcare API to leverage AI for de-identifying Protected Health Information (PHI), ensuring HIPAA compliance. We also acquired expertise in utilizing and implementing MongoDB to enhance our data management capabilities

What we learned

This was our first time integrating Google Cloud's API's at all and we were shocked at how much it had to offer.

What's next for Medverse

We want to integrate this tool internally for hospitals so we can have a community for doctors that work at the same facility. In the future we aim for this to possibly be a research tool for educational institutions. In the future we will also create our own proprietary software to deidentify patient information, incase Google Cloud Healthcare API gets depreciated at all.