The problem Medster solves

The rise in insurance policies that India witnessed in the pandemic suggests that more people will now consider buying insurance policies. A new add OPD was introduced in 2018-2019 in the insurance industry. OPD insurance helped in daily visits to the doctor by reimbursing its customers consultation fee and drug expenses. OPD market is still new but one of the reasons it isn't growing is the hassle to get said reimbursement. People can only go to certain doctors within the insurer network and they had to fill out a long-form and get it signed by their doctor. These all challenges involved force people not to opt for OPD insurance even when they are willing to pay for it. Come Medster, medster tackle all those challenges and make the process of getting consultation easier. Our idea is, get yourself checked and walk out, we'll take care of the rest. A person books an appointment or scan a QR code at the doctor's office and medster will transfer funds directly to the doctor.

Challenges we ran into

We faced some hurdles, some we were able to resolve, some we weren't.
We used Maps Apis to plot all the hospitals that are covered by your insurer, so if a particular situation arises and you have to rush to the hospital, you can quickly glance at the hospital close to you covered by your insurer.
We had to use maps, Place API, and geolocation API in perfect synchrony.
We weren't able to show info windows of the already plotted markers so that person can quickly know about the hospital.
And while we were able to use geolocation, we couldn't do distance API's to direct to the nearest hospital.

We faced some problems with the routing and verification of email.
While we were able to send a string that the user will enter to verify their email, we faced some problems fetching the string from our database and verifying the string.
We redeveloped our entire database model to get it to work and realized that it was clashing with our doctor verification model and the users model was looking in the wrong database, so we were able to rectify that