What’s the best way to structure medicine inventory and prescription records in Bubble’s database, ensuring secure data handling and easy prescription verification?

How should I design my Bubble database tables (data types) for medicines and prescriptions in a way that makes it easy to manage inventory, verify prescriptions, and keep everything secure?

Hey, there are many ways you could do it. I’d have one datatype for medication and one for prescription.

It’s important to notice that prescriptions have their own recurrency, so it’s good to use option sets to define for how long a medication should be taken and the hour spacing between medications.

You could also have an option set for how the medication is taken (oral, vein…)

Each prescription has a medication and a user.

It’s important to rely on privacy rules to ensure no data leaks.

Those are just general ideas. If you want to talk more, ping me via DM.

Other thoughts on permissions:

  • Who creates a prescription? A doctor? You’d need a user type for that (which also can be an Option Set)
  • Who sees the prescription? Doctors, Nurses, and the own patient? You’d need privacy rules for that.

There are many questions I’d ask, but yeah, ping me if you need help. :wink:

This topic was automatically closed after 70 days. New replies are no longer allowed.