Oladoc is a digital healthcare platform in Pakistan. It helps you find and instantly book appointments or online video consultations with the best doctors in Pakistan. Their transparent and intuitive platform helps you choose the right doctors by letting you check up on patient reviews, consultation fees, satisfaction scores, and wait times. oladoc has already served over 15 million+ patients across the country and counting. Now assuming you want to build the console based system by implementing the oladoc system with some additional functionalities in c++.

Following are the main Module of Oladoc

1. Appointment Management Module
2. Doctor Schedule Management Module
3. Patient Management Module
4. Doctor Management Module
5. Login Module
6. Registration Module

This system has three users. Admin, Doctor, and Patient. So all feature has been divided between these three users.

o Admin can Add Edit Delete and view Doctor’s data. o Admin can view all patient’s data. o Admin can Schedule any Doctor Availability and manage that data like edit or delete it. o Admin can view all doctor appointment data and he or she can also process appointments (update or cancel).

• Doctor can register into this system.
• Doctor can log in to this system.
• Doctor can Add, Edit and Delete their availability and hourly charge.
• Doctor can view only their appointment data; they cannot see other doctor appointment data.
• Doctor can check the appointment patient’s details.
• Doctors must have their particular specialization areas
• To each area, there must be a separate/distinct view and possibly sub-views
• Doctor can change the status the of appointment as approve, pending and reject. Initially, the status of all the appointments request will be pending until Doctor confirms the request as approved.
• Doctor can edit his profile details (timing, location, rates, etc.).
• Doctor can check all his scheduled appointments in his profile.

• Patient can register into this system.
• Patient can log in to this system.
• Patient can reset the password.
• Patient can search for doctors by (Specialty, Area, and Hospitals)
• Patient can check Doctor’s availability and chargers.
• Patient can book and cancel the appointment with Doctor.
• Patient can update the appointment details (only the scheduled time).
• Patient can change their profile details.
• Patient can Book in-person or video consultations with the Doctor.
• Patient can check all his scheduled appointments in his profile.
• Patient can recharge their account

Registration details are stored in three separate txt/dat files namely admin, doctor, and patient. These files have User details. Note: carefully analyze and select the attributes that need to be stored in these files.

• A new doctor can register in the system with a valid CNIC or email.
• The doctor account is only created if a valid 13-digit CNIC is provided. CNIC and email must not be repeated in the existing record. Otherwise, appropriate messages should be generated to notify the users.
• Password must be 8 characters long and the use of a minimum of one special character, uppercase, lowercase, and the numeric digit is a must.
• While registration the system should verify any typing mistake in password by asking the user to re-enter the password.
• After successful registration, the system will ask for details about the doctor e.g Years of experience, his specialization area, the hospital name he is working in, availability hours for an appointment, and city (Can be more attributes as per the requirements of the system)

• A new patient can register into the system with a valid CNIC.
• The patient account is only created if a valid 13-digit CNIC is provided and CNIC must not be repeated in the existing record. Otherwise, appropriate messages should be generated to notify the users.
• Password must be 8 characters long and the use of a minimum of one special character, uppercase, lowercase, and the numeric digit is a must.
• Patient must re-enter the password and the system should verify any typing mistake.
• After successful registration, the initial balance for each patient will be Rs. 3500.

• Admin can login to the system by predefined username and password
• Display proper error message in case of wrong credentials.

• A doctor can log in to the system by the username and password provided at the time of registration.
• Display proper error message in case of wrong credentials.

• A patient can log in to the system by the username and password provided at the time of registration.
• Display proper error message in case of wrong credentials.

A menu is provided to each user (Admin, doctor, patient) separately to navigate the full system.

• After completion of each step, users are provided with a menu for the subsequent process and a link to the main menu (different menu for the different users e.g. Admin, patient, doctor).
• Basic details about the system are available for every user without login. System-specific details like Book appointments, Cancellation, check availability, etc. are only accessible to the registered users.

There are many ways a patient can find a doctor to book an appointment

• Patient can find a doctor via his/her specialty (categories) like dermatologist, neurologist, etc
• Patient can also find doctors via hospital name or city
• Your system cannot book 2 appointments for the same doctor at the same time.
• Before booking an appointment, display a list of day and hours slots and the charges that are available for the doctor.
• Charges for in-person and video consultation appointments are different for each Doctor.
• Patient can check all his booked appointments and their status in his profile
• Maintain a separate file to store the appointment information which will include Doctor CNIC, Doctor name, Patient CNIC, patient name, appointment mode, day, and time.
• For appointment cancellation, do the required implementation as well (think about it how will you reflect in the system that the appointment is canceled and it is no more scheduled)

• After a checkup/appointment, a feedback menu should be displayed on the patient’s account
• The new displayed menu should be used to write a review + give a rating (out of 5 stars) about the doctor
• Feedback rating must be maintained based on patients’ reviews about the doctor
• The feedback must be shown on the concerned doctor’s profile
• The overall ratings that would be displayed on the doctor’s profile must be the average of all the ratings which will never exceed length 5
• Bonus: A reply on the review of patients from the management can also be implemented

The payment details for each booked appointment are recorded. Appointment charges for all the appointments are displayed to the users.

• Charges for in-person and video consultation appointments are different for each Doctor.
• The system must calculate the charges by keeping in mind that video consultation is 70% of the in-person appointment charges (30% less).
• As the payment is a transaction from the doctor’s account to the patient’s account, the return would be the inverse of the transaction
• The patient should be able to select an E-Gateway for the transaction such as JazzCash, EasyPaisa, PayPak, UnionPay or Bank Transfer
• Set a criterion for if the patient does not show up on the date of appointment, a percentage would be deducted from the amount he paid + he would have to pay that percentage again
• -30% after one day E.g., 100 already paid for an appointment, 30 would he pay if come a day later
• -60% after two days (Patient would have to pay 60% extra) E.g., 100 already paid for an appointment, 60 would he pay if come a day later
• -100% on three days (Patient would have to fix the appointment again) E.g., 100 already paid for an appointment, the patient would re-fix an appointment and would have to pay 100 again if he comes after three days
• In case the patient wants to cancel the appointment
• 100% return on the same day of fixing the appointment
• 60% return on the second day of fixing the appointment
• 30% return on the third day of fixing the appointment
• No return after the third day

• Your program should never exit. Always display a menu to the user.
• All the operations are done via file handling so no need to log out from one user and go back to another using only one console, your program must be able to run multiple consoles using the same code and same file paths.
• After completion of each step, users are provided with a menu for the subsequent process and a link to the main menu (different menu for the different users e.g. Admin, patient, doctor)
• Also, provide the functionality of Logout to each user.
• Solid marks for building a proper hierarchy for modules(folders), classes(files) and user interfaces
• Aesthetic sense(design) has bonus marks