PharmEasy

PharmEasy

We work hard, so you PharmEasy.

Justin Esguerra

PharmEasy was created because of the software shortcomings I observed as a retail pharmacy technician. These shortcomings include but are not limited to…

  • Failure to receive e-prescriptions from hospitals/medical offices
  • Miscommunications between the mobile app and the computer application (resulted in the following failures)
    • Unsynchronized Online Pay
    • Failed Medication Refills
    • Unrecorded Vaccine Appointments
  • Patient’s lack of control over their health information on the mobile app
    • Insurance Eligibility Information
    • Mailing Address
    • Allergies
    • Health Conditions
    • Phone Number

Having this all in mind, I attempted to program a proof of concept in Python when I first began programming, unaware of the vastness of the endeavor. The prototype amounted to little, but allowed me to get my hands dirty in actually trying to make a console application.


In 2021, my friends and I participated in KnightHacks. This was a year after the inception of the pharmacy idea, and at the start of the hackathon PharmEasy was officially born.

In the 36 hours that we had, we were able to design most of the user interface, the login screen, some components, and a half finished user authentication. Due to my lack of skill at the time I was primarily in charge of the mockups and the video presentation. Miraculously through our efforts we won a sponsored prize at the competition.



However, after the hackathon I began working on the database. I installed PostgreSQL and started learning about databases, ERD’s, queries and SQL. At the writing of this article, I’ve only gotten so far as to normalize the database to the third normal form (3nf). Despite that I have yet to deploy the database or connect it to the user authentication nor the front end.

PharmEasy has regressed back into the planning stage, however I believe that is for the better. I have come to realize that a software as complex as a pharmacy management system is not something that can be rushed to production.

Rushing, just like in healthcare, leads to errors. Preventing those mistakes by taking the time necessary to plan, prototype, and learn. Is the correct decision.

I’ll keep working hard and maybe someday, pharmacies and patients alike can PharmEasy.