How namanh2508/nt208.p23-group-4 works
Main Components
• Frontend (Client Applications):
– React-based web application found in the “fe” folder for interactive UI components.
– Static HTML pages in “hospital” for various public and administrative interfaces.
• Backend Services (Hospital Management System):
– Django project (“hospital_web”) which encompasses multiple Django apps such as UserManagement, api, and hospitalManagement.
– This area includes REST APIs that serve the frontend and handle business logic.
• Database:
– PostgreSQL as the relational database, used to store structured data such as user records, appointment details, and EHR.
• API Gateway:
– An entry point for the clients; from the readme, it acts as the contact point for routing, authentication, and rate limiting.
• Core Services (as identified in the Readme’s component descriptions):
– Services like Auth Service, Appointment Service, EHR Service, Consultation Service, Prescription Service, Billing Service, and Notification Service.
• Infrastructure & External Services:
– Messaging or asynchronous communication (message queues for notification, etc.).
– Integration with external payment gateways, video conferencing services, SMS/Email gateways, and possibly even a search engine.
– Potential integration with the Google Calendar API for scheduling tasks like exercise reminders.
Relationships and Interactions
• Data flows exist between client applications (web/mobile) and the API Gateway.
• The API Gateway then routes incoming requests to the appropriate backend service.
• Backend services interact with the PostgreSQL database to retrieve and store data.
• External services (e.g., Payment Gateway, Video Conferencing) are called by the respective backend services.
• Additionally, the system may use asynchronous messaging (via a Message Queue) for operations like notifications or appointment confirmations.
Architectural Patterns and Design Principles
• Separation of Concerns: Frontend and backend are clearly separated; the backend is also modularized into distinct Django apps that correspond to specific business functionalities.
• API-Driven Communication: The API Gateway funnels all requests and responses, ensuring a unified access point cloud security and scalability.
• Microservices/Multi-Service Architecture: While implemented as Django apps within a single project, the design suggests discrete “services” (Auth, Appointment, etc.) that could later be decoupled.
• Scalability and Maintainability: The use of standardized technologies like React and Django REST Framework, combined with external integrations for notifications, payment, and video, assures that each layer is designed for independent scaling and easy maintenance.