The Pharmacists Mutual Claims Study was started in 1989 by Ken Baker, a pharmacist/lawyer at the company. While the majority of the company's claims come from independent community pharmacies, there are claims from many different practice sites: hospitals, long term care, compounding pharmacies, and chain pharmacies. The Claims Study was started to gather the claims that were being reported and organize the information in a manner that allowed other pharmacists to learn from the mistakes. There is no other organization with access to the claims information Pharmacists Mutual does. The Claims Study today has over 12,000 records in its database, with an average of 1 to 2 such claims every day, 365 days a year.
Upon successful completion of this activity, pharmacists should be able to:
- Identify main types of professional liability claims seen in pharmacy.
- Identify common medications associated with professional liability claims and understand why they occur.
- Understand the steps in the risk management process and how to apply them to their practice.
Kristen Jones, PharmD, Pharmacy Risk Management Consultant
Kristen Jones graduated from the University of Wyoming School of Pharmacy in 2003 with a Doctorate of Pharmacy. Kristen has practiced in both retail and hospital pharmacy prior to starting her position at Pharmacists Mutual in 2014. She is a member of ASHP, NCPA and IACP. She currently resides in Wheatland, Wyoming.
The cost is $25 for nonmembers. Our Virtual Coffee Break webinars are complimentary for MPhA members.
This presentation is being submitted to the Minnesota Board of Pharmacy for Continuing Education credit approval (one hour).
To receive Board of Pharmacy credits for this program the following must be completed:
Board of Pharmacy credit processing takes place on the 15th of each month.
||The Minnesota Pharmacists Association is accredited by the Minnesota Board of Pharmacy as a provider of continuing pharmacy education.
Questions? Please contact email@example.com with questions about credits.
Please contact firstname.lastname@example.org with any technical questions or issues.