How jamal-khan-i/medikiosk works
MediKiosk is a multilingual hospital outpatient intake and clinical handoff platform. Patients register at a kiosk, answer adaptive questions, and submit prior records; the system synthesizes and prioritizes clinical information for physician review, while staff manage the queue and operations. The graph includes the documented kiosk, physician, admin, and triage surfaces plus backend intake, document, identity, and persistence layers. Several backend routes and service integrations were not sampled in full, so their relationships are shown only where README or indexed source references support them.
Main entry points: server.js HTTP and realtime API · api.js API client · App.jsx Surface router · documentService.js Document OCR
Components 21
Patient and staff UI
- Surface router
frontend/src/App.jsx - Patient kiosk
frontend/src/surfaces/kiosk/PatientKiosk.jsx - Physician workstation
frontend/src/surfaces/physician/PhysicianDashboard.jsx - Hospital admin
frontend/src/surfaces/admin/HospitalAdmin.jsx - Triage alert surface
frontend/src/surfaces/triage/TriageAlertSurface.jsx - API client
frontend/src/services/api.js
Intake backend
- HTTP and realtime API
backend/server.js
Clinical processing
- Adaptive intake
backend/services/intakeService.js - Red-flag triage
backend/services/triageService.js - Document OCR
backend/services/documentService.js - Clinical reasoning
backend/services/llmService.js - Bhashini language services
backend/services/bhashiniService.js
Identity and records
- ABDM identity
backend/services/abdmService.js - Staff authentication
backend/services/authService.js - FHIR record builder
backend/services/fhirService.js - Audit trail
backend/services/auditService.js - Relational file store
backend/db/store.js
Other components
- Patient
- Hospital staff
- Google Gemini
- Bhashini platform
Connections 28
- Patient → Patient kiosk: checks in
- Patient kiosk → API client: requests intake
frontend/src/surfaces/kiosk/PatientKiosk.jsx - API client → HTTP and realtime API: calls API
frontend/src/services/api.js - HTTP and realtime API → Adaptive intake: generates questions
backend/server.js - HTTP and realtime API → Document OCR: processes documents
backend/server.js - Document OCR → Bhashini language services: uses OCR
backend/services/documentService.js - Document OCR → Clinical reasoning: uses extraction
backend/services/documentService.js - HTTP and realtime API → Clinical reasoning: generates summary
backend/server.js - Clinical reasoning → Google Gemini: requests reasoning
- Bhashini language services → Bhashini platform: requests language services
- HTTP and realtime API → Red-flag triage: routes triage
backend/server.js - HTTP and realtime API → ABDM identity: handles identity
backend/server.js - HTTP and realtime API → Staff authentication: uses staff auth
backend/server.js - HTTP and realtime API → FHIR record builder: supports records
backend/server.js - HTTP and realtime API → Audit trail: records audit
backend/server.js - HTTP and realtime API → Relational file store: reads and writes
backend/server.js - Staff authentication → Relational file store: checks staff
backend/services/authService.js - Audit trail → Relational file store: persists events
backend/services/auditService.js - Hospital staff → Physician workstation: reviews cases
- Hospital staff → Hospital admin: manages operations
- Hospital staff → Triage alert surface: responds to alerts
- Physician workstation → API client: requests records
frontend/src/surfaces/physician/PhysicianDashboard.jsx - Hospital admin → API client: manages staff
frontend/src/surfaces/admin/HospitalAdmin.jsx - Triage alert surface → API client: receives updates
frontend/src/surfaces/triage/TriageAlertSurface.jsx - Surface router → Patient kiosk: routes to
frontend/src/App.jsx - Surface router → Physician workstation: routes to
frontend/src/App.jsx - Surface router → Hospital admin: routes to
frontend/src/App.jsx - Surface router → Triage alert surface: routes to
frontend/src/App.jsx