Pharmacy errors are becoming more common as pharmacists break under company pressure. Many pharmacists are worried about patients’ safety, but there’s only so much they can do. Here’s how to protect yourself from pharmacists’ errors.

How to Protect Yourself from Pharmacists' Mistakes

How These Mistakes Happen


If you haven’t read our previous article breaking down concerns pharmacists have, we’ll give you a quick recap. Basically, there’s too many tasks expected of pharmacists and not enough people or time to do them. Pharmacists have been trying to get their companies to hear their concerns, but it seems like nothing has changed.

How to Protect Yourself from Pharmacists’ Mistakes


You can start by talking to your pharmacist. They probably look busy, and they are, but they know the most about the drugs they are giving out.

Pharmacy errors don’t mean that pharmacists are your enemy. It just means they are overworked.

Ask them about side effects and whether it’s safe to take with the other medications you have. By asking questions, you increase the chances of the pharmacists taking a second look at your prescription, therefore catching any mistakes.

Open the Bag

Before you leave, open your bag and check the contents. It’s easy just to leave and assume everything is correct. Make sure each bottle has the right name, address, and birthdate. While the papers on the outside have the right info, the bottles could not.

Along those lines, check the pills as well. For the most part, you’re probably familiar with what your medication looks like. If they look different, speak up, and ask questions. Don’t assume they switched to a generic version or used a new supplier.

Report Errors

Make sure to let the pharmacy know there was a mistake. You may feel bad, but not only were you put at risk, but another patient was as well. Reporting mistakes will also alert the doctor too, and every once in a while, the error could come from them.

Errors can also be reported to state pharmacy boards and lets them know what’s going on.

Read more here.