How raviprassand/ai-powered-ehealth-appointment-scheduling-agent works
This repository contains documentation and integration notes, not the backend or frontend source branches. The documented user journey is a patient using the portal and conversational booking agent; backend AI interprets requests and retrieves patient context, while deterministic rules validate bookings and confirmed appointments and notifications are persisted for portal display. The graph reflects README-described capabilities only; implementation paths and internal call ownership cannot be verified from this tree.
Components 12
Patient Portal
- Patient Portal
Backend Services
- Booking Agent
- REST APIs
- Booking Validation
- Doctor Selection
AI Capabilities
- Intent Extraction
- Patient Context RAG
Clinical Data
- Appointments
- Doctor Notifications
- Patient Records
Other components
- Patient
- Doctor
Connections 13
- Patient → Patient Portal: uses
README.md - Patient Portal → REST APIs: calls
README.md - REST APIs → Booking Agent: exposes booking
README.md - Booking Agent → Intent Extraction: extracts intent
README.md - Booking Agent → Patient Context RAG: retrieves context
README.md - Booking Agent → Booking Validation: validates booking
README.md - Booking Validation → Doctor Selection: selects doctor
README.md - Doctor Selection → Doctor: uses family doctor
README.md - Patient Context RAG → Patient Records: retrieves data
README.md - Booking Validation → Appointments: stores confirmed
README.md - Booking Agent → Doctor Notifications: creates notifications
README.md - Patient Portal → Appointments: views appointments
README.md - Patient Portal → Doctor Notifications: views notifications
README.md