Inspiration

These days our online resources have become increasingly cluttered, making it harder than ever for the average user to get the information they need as accessible as it should be. My goal is to add to the pool of resources that put the user first in providing the information required to make educated decisions on their health.

What it does

Given a brief list of symptoms written in plain english (as one would describe to a doctor), CarePath will categorize the urgency and possible explanations for your symptoms. If the symptoms are concerning, CarePath will also provide a list of steps for you to take to help ease discomfort and safely find yourself care with medical professionals. There is also a list of nearby hospitals sorted by distance with links to google maps to quickly get on your way to help.

How we built it

Full transparency, the entire project was vibecoded, but the specifications and ethics are still mine. Due to it's lightweight nature, it all runs off of a python flask server which serves a basic site using html + css.

Challenges we ran into

The primary challenges are in ensuring the accuracy of output. The current state of the application is intended to flesh out the key features and how they fit together into a cohesive product. Because of this, less emphasis was placed on accuracy in the data itself which is a must have for this to be a viable solution.

Accomplishments that we're proud of

First time I vibe coded something. While I generally disagree with the process, I find it interesting how much of an impact prompt engineering has on the quality of the output. I am very proud of the extremely short turnaround time on a project that is outside my wheelhouse.

What we learned

The most important takeaway I had working on this project is that we aren't done yet, not even close. I could keep coming up with essential features to improve the experience for users, not to mention the other facets of daily life that remain polluted with weird solutions to our weird problems.

What's next for CarePath

The most obvious step forward would be to scrap the generative AI component of symptom analysis. I would pivot to real data with a internally trained LLM designed to provide recommendations rooted in absolute fact. Another natural step would be to allow for temporary logs to track the progress of acute illnesses with timestamps, actions recommended and actions taken.

Final words

Yes, CarePath was cobbled together with little thought for the process. I truly believe in the message, the path we must take to ensure everyone can get the care that they not only need, but deserve.

(No AI was used in the process of making this section, it's just me <3)

Built With

Share this project:

Updates