Project Info
This project did not submit a demo video on Devpost.
Inspiration
The American Healthcare system is expensive and complicated. Everyone wants the best, most cost-effective insurance plan, but choosing one can feel like a daunting task. We were motivated to build a product that could deal with large benefits summaries containing opaque language and support our users' unique medical needs, all the while maintaining a high level of user personalization.
What it does
PredictAPulseAI provides users with a health questionnaire, where the answers serve as input for an ML model for heart attack risk classification. Our ML model was trained using a dataset that has features for causes of heart attacks and predicts future heart attacks. Afterward, users upload summary benefits of insurance policies to PredictAPulseAI, and it combines all of this data to find the most cost-effective insurance policy given your risk for heart attacks.
How we built it
Frontend: JS, React, Next.js, TypeScript, HTML/CSS, Material UI Backend: Python, Flask, MindsDB.api, Tesseract OCR, Open AI GPT (3.5) Database: SQL, CockroachDB Classification Model: Heart Attack Kaggle Dataset, MindsDB
Challenges we ran into
Some of the challenges we ran into were dealing with the limitations of Intel Cloud, specifically its inability to connect to Cockroach DB and port-forward for our custom backend API.
Accomplishments we're proud of
Successful implementations of functions. Replaced cookie usage. Bridged front-end to back-end, API integration, and database implementation.
What we learned
Insurance comparisons and how it helps users based on their current health conditions. We expanded our knowledge of SQL with CockroachDB, ML prediction models with MindsDB, and Flask web server with our custom-written API endpoint.
What's next
This project is not limited to predicting heart attacks and reducing the cost of treatment for our users. Other leading causes of death, such as cancer, can be effectively predicted to do the same pipeline. Most importantly, our project would save lives. We plan to adapt our project to an intuitive mobile application to increase accessibility. We also plan to effectively market our idea and utilize sponsorships from insurance companies to gain funding.
PredictAPulseAI
Personalized AI health outcome predictor and insurance selection guide
Deployed Website: https://predict-a-pulse-ai-rofr.vercel.app/
https://github.com/themeghamind/PredictAPulseAI/assets/57309755/eb6f003d-fac2-4944-8f2d-c92eda53162d
Inspiration
The American Healthcare system is expensive and complicated. Everyone wants the best, most cost-effective insurance plan, but choosing one can feel like a daunting task. We were motivated to build a product that could deal with large benefits summaries containing opaque language and support our users' unique medical needs, all the while maintaining a high level of user personalization.
What it does
PredictAPulseAI provides users with a health questionnaire, where the answers serve as input for an ML model for heart attack risk classification. Our ML model was trained using a dataset that has features for causes of heart attacks and predicts future heart attacks. Afterward, users upload summary benefits of insurance policies to PredictAPulseAI, and it combines all of this data to find the most cost-effective insurance policy given your risk for heart attacks.
How we built it
Frontend: JS, React, Next.js, TypeScript, HTML/CSS, Material UI, Vercel
Backend: Python, FastAPI, MindsDB.api, Tesseract OCR, OpenAI GPT 3.5
Database: CockroachDB
Classification Model: Heart Attack Kaggle Dataset, MindsDB Regression-Based Predictor
Challenges we ran into
Some of the challenges we ran into were dealing with the limitations of Intel Cloud, specifically its inability to connect to Cockroach DB and port-forward for our custom backend API.
Accomplishments that we're proud of
Successful implementations of functions. Replaced cookie usage. Bridged front-end to back-end, API integration, and database implementation.
What we learned
Insurance comparisons and how it helps users based on their current health conditions. We expanded our knowledge of SQL with CockroachDB, ML prediction models with MindsDB, and Flask web server with our custom-written API endpoint.
What's next for PredictAPulseAI
This project is not limited to predicting heart attacks and reducing the cost of treatment for our users. Other leading causes of death, such as cancer, can be effectively predicted to do the same pipeline. Most importantly, our project would save lives.
We plan to adapt our project to an intuitive mobile application to increase accessibility. We also plan to effectively market our idea and utilize sponsorships from insurance companies to gain funding.
Analysis
View
Metric
- 50
- 16
- 5
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- FastAPIIn code
- JavaScriptIn code
- Next.jsIn code
- OpenAIIn code
- PythonIn code
- ReactIn code
- Tailwind CSSIn code
- TypeScriptIn code
- FlaskClaimed
- SQLClaimed
- VercelClaimed
9 of 12 appear in the indexed code. 3 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
31 KB
Source files
11
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
themeghamind/PredictAPulseAI
23 files · 369 KB · @ 5e76862
Structure
Interface
6 files · 26%Screens, components and styles rendered to the user.
Application logic
1 file · 4%Domain rules, services and shared utilities.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- TypeScript79%
- Python10%
- Markdown8%
- CSS2%
- JavaScript1%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
package.json
npm · 22- @emotion/react
- @emotion/styled
- @fontsource/roboto
- @mui/icons-material
- @mui/material
- axios
- cors
- encoding
- next
- react
- react-dom
- react-drag-drop-files
- tesseract.js
- +9 more
requirements.txt
pypi · 14- charset-normalizer
- fastapi
- openai
- pandas
- pillow
- pydantic
- python-dotenv
- pytz
- requests
- six
- sqlparse
- tzdata
- urllib3
- uvicorn
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.