Unified health intelligence platform with a React + Vite frontend and Node.js + Express backend, including wearable data streaming, medication tracking, care planning, nutrition logs, insurance, documents, and AI-style health insights.
- Health dashboard and profile experience
- Medication and symptom tracking
- Provider/doctor planning tools
- Live wearable stream (WebSocket)
- Intelligence insights and correlation analysis
- Family medication tracking
- Nutrition logging
- Insurance support workflows
- Document management and timeline support
- Frontend: React, Vite, React Router, TailwindCSS
- Backend: Node.js, Express
- Database: SQLite + Knex migrations
- Realtime: WebSocket (
ws)
mediSync/
├── client/ # React frontend
├── server/ # Express API, services, routes, tests
├── knexfile.js # Knex/SQLite config
├── .env.example # Environment template
└── package.json # Root scripts for full-stack dev
- Node.js 18+ (recommended)
- npm 9+ (recommended)
-
Clone and enter the project.
-
Install dependencies:
npm run install:all
-
Create environment file:
cp .env.example .env
-
Update
.envkeys as needed.
The app supports mock/fallback behavior when many keys are missing.
npm run dev- Client:
http://localhost:5173 - Server:
http://localhost:3001
npm run servernpm run clientThe backend uses SQLite (server/data/medisync.sqlite3) and runs migrations at server startup.
Manual migration commands:
npm run migrate
npm run migrate:rollbackSeed demo data:
npm run seed/api/users/api/medications/api/symptoms/api/drugs/api/providers/api/wearable/api/intelligence/api/family/api/insurance/api/nutrition/api/documents/api/timeline/api/symptom-logs
Health check endpoint:
GET /health
Frontend build:
npm --prefix client run buildServer tests:
node --test server/tests/*.test.jsSee .env.example for all keys. Integrations include:
- openFDA
- Infermedica
- Nutritionix
- USDA FoodData Central
- Healthcare.gov
- Anthropic (optional insight explanations)
- Current client lint script references ESLint, but ESLint is not present in
client/devDependencies. - Large frontend bundle warnings may appear during production build; functionality is unaffected.