How baranidharan16/digital-health-twin works
Human Health Digital Twin synchronizes wearable or simulated readings into a person-specific physiology model, then presents state, explanations, history, and an interactive anatomical view. The main path is source data → normalization → twin update and persistence → live dashboard; users can also import wearable exports and run personalized what-if scenarios. The README documents the system-level lifecycle and capabilities; sampled source confirms key engine, ingestion, frontend, and phone-app behavior. Several API routes and unsampled subsystems are represented from README documentation rather than inspected implementation.
Main entry points: twin_service.py Twin synchronization · engine.py Twin engine · client.ts Web API client · api Backend API
Components 22
Data sources
- Physiology simulator
simulator/generator.py - Android companion
mobile/android/app/src/main/java/com/healthtwin/app/MainActivity.kt - Health Connect reader
mobile/android/app/src/main/java/com/healthtwin/app/HealthReader.kt - Wearable imports
backend/app/importers.py
Twin runtime
- Reading normalization
backend/app/ingestion.py - Backend API
backend/app/api - Twin synchronization
backend/app/services/twin_service.py - Twin engine
digital_twin/engine.py - Personal baseline
digital_twin/baseline.py - Anomaly detection
digital_twin/anomaly.py - State transitions
digital_twin/state_engine.py - Twin data store
backend/app/db.py
Analytics and simulation
- History and analytics
backend/app/services/queries.py - Wellness summaries
digital_twin/wellness.py - What-if scenarios
digital_twin/whatif.py
User experience
- Web API client
frontend/src/api/client.ts - Live twin hook
frontend/src/hooks/useLiveTwin.ts - Web dashboard
frontend/src/App.tsx - Analytics and history
frontend/src/pages/AnalyticsPage.tsx - Scenario interface
frontend/src/pages/SimulationPage.tsx - 3D anatomical twin
frontend/src/twin3d/TwinScene.tsx
Other components
- Person / demo user
Connections 25
- Person / demo user → Android companion: pairs phone
README.md - Health Connect reader → Android companion: reads measurements
mobile/android/app/src/main/java/com/healthtwin/app/MainActivity.kt - Android companion → Backend API: syncs readings
README.md - Physiology simulator → Reading normalization: supplies readings
backend/app/ingestion.py - Person / demo user → Wearable imports: uploads export
README.md - Wearable imports → Reading normalization: normalizes records
backend/app/importers.py - Reading normalization → Twin synchronization: passes observations
backend/app/ingestion.py - Backend API → Twin synchronization: routes twin requests
backend/app/api/twins.py - Twin synchronization → Twin engine: updates twin
backend/app/services/twin_service.py - Twin synchronization → Twin data store: persists state
backend/app/services/twin_service.py - Twin engine → Personal baseline: assesses against
digital_twin/engine.py - Twin engine → Anomaly detection: assesses vitals
digital_twin/engine.py - Twin engine → State transitions: updates state
digital_twin/engine.py - History and analytics → Twin data store: reads history
backend/app/services/queries.py - History and analytics → Wellness summaries: uses summaries
backend/app/services/queries.py - What-if scenarios → Twin engine: classifies scenarios
digital_twin/whatif.py - Web API client → Backend API: calls endpoints
frontend/src/api/client.ts - Live twin hook → Web API client: loads twin data
frontend/src/hooks/useLiveTwin.ts - Live twin hook → Backend API: opens live stream
frontend/src/hooks/useLiveTwin.ts - Web dashboard → Live twin hook: shows live state
frontend/src/App.tsx - Web dashboard → Web API client: loads twin list
frontend/src/App.tsx - Analytics and history → Web API client: requests analytics
- Scenario interface → Web API client: submits scenarios
frontend/src/pages/SimulationPage.tsx - Web dashboard → 3D anatomical twin: renders twin view
README.md - Twin synchronization → History and analytics: serves twin analytics
README.md