It started with a simple frustration
Medicine information is available online, but finding a clear answer is often harder than it should be. The same ingredient appears under many brand names. Useful details are spread across product pages, package inserts and pharmacy listings. It can be difficult to tell where the information ends and the sales pitch begins.
I built OpenMedsDB because I wanted a simpler place to look things up. Search for a medicine, see what it contains, understand its form and strength, and find the important warnings without first being pushed towards a purchase.
I am a software engineer, not a doctor or pharmacist. OpenMedsDB is not an attempt to replace either of them. It is an attempt to organize information well enough that people can understand what they are looking at and ask better questions.
What I want it to be
I want OpenMedsDB to be useful at ordinary moments: when someone is reading a medicine strip, checking whether two brand names contain the same ingredient, or trying to make sense of a warning they have seen.
The site should be quick, readable on a small phone and usable without an account. It should explain where information came from and admit when a record is incomplete. When it compares prices or compositions, it should show how that comparison was made.
Most importantly, it should remain a reference rather than become a pharmacy. A cheaper brand is not automatically the right brand. Two matching ingredients do not always make products interchangeable. Those decisions still belong with a qualified healthcare professional.
Why it is open
OpenMedsDB is an open project because healthcare information needs accountability. The code can be inspected, the data structure can be examined and mistakes can be reported.
Being open does not make the database perfect. Medicine records change, prices become outdated and source data can contain errors. I would rather make those limits visible than pretend they do not exist.
My goal is to improve the project in public: add clearer sources, show retrieval dates, explain how tools work and mark weak records instead of presenting every page with the same confidence.
What comes next
The next stage is not only about adding more medicines. It is about making the existing information more useful.
That means better comparisons, clearer quality indicators, stronger source attribution and more original analysis of the data. I also want to write about what I learn while building it—both the healthcare questions and the engineering decisions behind the project.
OpenMedsDB will never know a person's full medical history, and it should never act as if it does. But it can make scattered information easier to search, compare and question. That is the project I want to keep building.