Nexus Health

Inspiration

Referrals and intake are still heavily manual (fax/EHR handoffs, phone calls, fragmented portals), which creates “referral leakage” (patients never book), long turnaround times, and poor visibility for clinics. In time-sensitive settings like hospice, delays can directly translate to lost admits and staff burnout.

What it does

Nexus Health is a closed-loop referral + intake workflow that takes documents, extracts/validates key fields, tracks eligibility/prior auth status, routes tasks/messages to the right person, and drives the referral to a booked appointment with risk-based follow-ups and an audit trail.

How we built it

Next.js app with role-based dashboards (doctor/patient/staff), Supabase (Postgres + Auth + Row Level Security) for data, real-time updates for messaging, and a lightweight “risk scoring + follow-up scheduler” service. We developed in VS Code, used Git/GitHub for collaboration, and tested end-to-end using only synthetic demo data.

Challenges we ran into

Designing a workflow that matches real clinic ops without EHR/payer integrations, handling edge cases (missing docs, wrong insurance, patient unresponsive), keeping roles/permissions safe, and merging multiple contributors’ code without breaking the UI or database constraints.

Accomplishments that we're proud of

We got a functional end-to-end system working: referral creation → verification → eligibility/auth tracking → scheduling workflow, plus messaging and metrics. We also successfully merged different teammates’ work into one codebase that runs together and supports a coherent demo.

What we learned

Healthcare workflows are mostly exception-handling, not the “happy path.” Clear status states, ownership (who’s responsible next), and auditable actions matter as much as the UI. We also learned how to collaborate faster with cleaner interfaces, better schema planning, and disciplined commits.

What's next for Nexus Health

Make the automation smarter (better doc extraction + validation), expand scheduling (availability matching + reminders), add deeper reporting for clinics (leakage cohorts, bottleneck analysis), and integrate with real systems via safe APIs (EHR/payer/clearinghouse) once compliance and partnerships are in place.

Built With

• css
• html
• plpgsql
• typescript