You are browsing as a guest. Sign up (or log in) to start making projects!

PulseFlow AI

By @Vedant_Daga

  • 1 Devlogs
  • 3 Total hours

PulseFlow AI is an AI-powered digital hospital platform that simulates patient flow, resource utilization, and operational bottlenecks in real time. It helps hospitals predict and prevent capacity issues before they impact care. I used SimPy, FastAPI, Next.js, and Google OR-Tools. It combines monitoring, forecasting, staffing, and AI recommendations. The platform allows administrators to test different staffing, and coordinate care using a digital twin of the hospital.
Open comments for this post

@Vedant_Daga on PulseFlow AI

3h 24m 20s logged

PULSEFLOW AI IS FINALLY LIVE

Just deployed the full stack today (backend is on Render and frontend is on Vercel).

The backend was so easy to get running, only took 10ish mins. MIGHT have forgot that Optional wasn’t imported in the config.py.

The frontend was SO MUCH HARDER OMG! first, Vercel blocked the deploy three times because of Next.js 15.0.3 had security vulnerabilities. i just updated to 15.3.3 (this didnt work because it had its own CVE). after that i tried using next@lastest, but then i needed ESLint 9, which broke the entire dependency tree.

I used ^15 so npm resolves the latest patched 15.x without jumping major versions. Four deploys, two CVEs, one peer dependency conflict. ahhh this was painful

BUT, IT FINALLY WORKS SO IT WAS WORTH IT!!!!

(image shows it running on vercel)

@Vedant_Daga

PULSEFLOW AI IS FINALLY LIVE

Just deployed the full stack today (backend is on Render and frontend is on Vercel).

The backend was so easy to get running, only took 10ish mins. MIGHT have forgot that Optional wasn’t imported in the config.py.

The frontend was SO MUCH HARDER OMG! first, Vercel blocked the deploy three times because of Next.js 15.0.3 had security vulnerabilities. i just updated to 15.3.3 (this didnt work because it had its own CVE). after that i tried using next@lastest, but then i needed ESLint 9, which broke the entire dependency tree.

I used ^15 so npm resolves the latest patched 15.x without jumping major versions. Four deploys, two CVEs, one peer dependency conflict. ahhh this was painful

BUT, IT FINALLY WORKS SO IT WAS WORTH IT!!!!

(image shows it running on vercel)

Replying to @Vedant_Daga
0
5

Followers

Loading…