-
Notifications
You must be signed in to change notification settings - Fork 0
MS1
MS1 Product
- Created user stories
- Identified requirements
- Designed system architecture
- Created architecture UML diagram
- Set up repositories
- Started working on: User service, Booking service, Map service, Logging service, Notification service, Patient frontend.
The user service now has implemented api for patient related functions. It also has its own postgres SQL database that stores all the data.
The booking service handles booking-related information and functions such as CRUD said information is stored in a Mongo database.
In the map service, we are using geocoder as an API to receive the coordinates for a given address. This integration allows our system to convert location-based information into geographic coordinates. We also have CRUD operations to create, fetch, update, and delete clinic locations.
The logging service subscribes to all topics from our message broker and logs every MQTT message inside a database with no regard to a structure. All other services are designed to publish logging data when their apis are interacted with.
The notification service is responsible for sending email notifications to the user after they complete a booking. It uses Gmail API.
The patient-client is a web interface for the patients that will use the system. It has different pages that allow patients to register themselves, make bookings, and edit their information. Currently it is not yet connected to the backend.