MedPromatic

Inspiration

The need for day-to-day medical services has increased in these unprecedented times, and we are working to address this. Typically, a user will need multiple apps/platforms to access a variety of medical services, such as online appointment booking, symptom checker, medicine reminders, online medicine ordering, and easy ambulance booking in emergency situations. We attempted to consolidate all services under one roof. Furthermore, there is a lack of proper service provided to doctors in order for them to keep track of their schedules, upcoming appointments, and provide patients with digital prescriptions.

What it does

MedPromatic addresses the major issue of rushing to hospitals and pharmacies for various medical needs; our app is a one-stop-shop for all of these issues. Furthermore, there is a lack of proper service provided to doctors in order for them to keep track of their schedules, upcoming appointments, and provide patients with digital prescriptions. Keeping this in mind, we added a feature to complete this requirement!

How we built it

The app is built using Flutter + Dart and is cross-platform and currently optimized for android.

Multiple firebase services like firestore, authentication cloud storage, cloud messaging, etc are used as a backend for the app.

Other services like Google Maps API. ApiMedic API and Open Route Service API are also used. The dashboard is a web app made using React for the frontend and Firebase for the backend.

It allows doctors to view all upcoming appointments, write prescriptions, and a calendar managed for the doctor. The authentication, user creation, and user management are done using Firebase as the backend. Sign-up can be done in a few simple steps. Cloud firestore and cloud storage is used to store user data.

Challenges we ran into

During the development of the app, we encountered two major issues: first, we were unable to use the firebase cloud functions, and second, we were unable to use the Google Directions API, both of which require the setup of a payment method.

Accomplishments that we're proud of

We discovered a replacement for the directions API. We got the polyline points from the open route service API and plotted them on the map for directions; it's an open-source API, so we didn't have any issues. Also, completing the project prototype before the deadline.

What we learned

As the app grew larger and more stateful components were added, reducing bugs and unwanted behavior became more difficult, but we learned to solve it with extensive testing and debugging.