Clini.Cal

Revolutionizing healthcare scheduling: Streamline appointments, boost efficiency, and enhance patient experiences with our platform.

Comment

Inspiration

Our inspiration for this app stemmed from the frustrating challenges patients often face when trying to access healthcare services and the need for healthcare providers to optimize their schedules. We envisioned a solution that would streamline the scheduling process, reducing wait times by letting the patients know the best times to schedule their appointments, the recommended medical appointments they should schedule accounting for factors such as age, sex, and health issues, visit healthcare providers, improving access to care, and enhancing the overall experience. Our goal is to create a more patient-centric and efficient healthcare system for all.

What it does

Clini.Cal is a healthcare scheduling platform that simplifies the process of booking medical appointments. It allows patients to find and book appointments with their preferred healthcare providers. It offers real-time appointment availability, along with the option to track the live wait times for pharmacies as well as medical office waiting rooms for patients wanting to do a walk-in. It sends automated reminders to patients to book their yearly appointments months in advance before desired dates get scheduled, as appointments aren’t normally available for 1+ months from the point you’re trying to schedule. Patients can now have more control over their time by efficiently managing their schedules, reducing waiting times, and optimizing their appointments. The platform also offers a chatbot to help provide general recommendations of services for the patient.

How we built it

Rough sketches of mid-fidelity wireframes in Figma Front-End: Built on FlutterFlow Back-End: Database built using Supabase, AI chatbot using OpenAI API

Challenges we ran into

One of the biggest challenges we ran into was understanding how to connect the back-end and the front-end technologies. When it came to using FlutterFlow for our front end, it was difficult due to the fact that we were unable to collaborate on the same project at the same time without one of the team members getting kicked off of the design. We learned that in order to be able to fully collaborate, each team member would have to pay a subscription. On the backend, we had difficulty testing the application on our local due to technical incompatibilities on Mac and with user folders that required permissions. We also planned on incorporating a machine learning model with patient information, having the ability to create a yearly appointment checklist based on some factors such as a patient’s age and sex, scheduling deadlines, and reminders. However, we were unable to complete this step on top of resolving the technical challenges we faced.

Accomplishments that we're proud of

Overall, our team is very proud to have been able to learn new technologies and be able to implement a whole project within the span of 24 hours. We are pleased with how it came out visually while still being partially functional and are happy to know that we have the capability to use these technologies in our own future projects.

What we learned

Throughout the development of Clini.Cal, we gained valuable insights into the complexities of integrating front-end and back-end technologies. We learned about the importance of effective collaboration tools and the challenges associated with choosing the right platform for development.

What's next for Clini.Cal

Given the amount of time we had to work on this project, we are certainly not finished! Clini.Cal will be continuously worked on to add more functionality and improve on user interface. A light mode/dark mode will be in the works, as well as functional pages for the patient to message their provider, set up reminders, schedule their appointments, and view REAL live wait times. We also plan on having the chatbot function properly. This is only just the beginning, and we would love to be able to have all various medical groups to be able to utilize this platform, rather than have it be utilized by only one group.

Built With

  • back-end
  • database
  • figma
  • flutterflow
  • front-end
  • openai
  • postgresql
  • supabase
  • vscode
Share this project:

Updates