A Look at the Latest ASAP PDMP Reporting Standard
PTMR publisher, Bill Lockwood, talks to Kevin Borcher, Pharm.D., about the latest ASAP (American Society for Automation in Pharmacy) standard, V5.0. Borcher played a key role in framing up Version 5.0. During the development of the new implementation guide, he served as VP for PDMP (prescription drug monitoring program) and pharmacy programs at CyncHealth for Nebraska’s PDMP.
Borcher is currently senior project coordinator, PDMP TTAC, at the Institute for Intergovernmental Research (IIR).
PTMR: Let’s begin with a brief overview of your history in the PDMP space.
Kevin Borcher: Thank you for inviting me to talk with you about this, Bill. In 2016 I was hired to be the PDMP director for Nebraska’s prescription drug monitoring program. Our system was built from the ground up for a go-live in 2017. I had over 20 years working with retail and hospital pharmacy systems as an informatics coordinator, so I had a basic understanding of how and what pharmacies report to PDMPs.
I became involved in the ASAP PDMP stakeholder meetings for version 4.2A in 2016 and then again in 2019 for ASAP version 4.2B to both learn more about ASAP and the process and to provide my input. What was unique about Nebraska’s PDMP was the fact that legislation required all prescriptions to be reported in 2018. In order to implement this mandate using ASAP, we had to perform a thorough evaluation of the ASAP standard and ensure that our PDMP could adhere to what was needed. With Nebraska’s model focusing on a patient care tool, I kept in close contact with ASAP to make suggestions for future versions.
PTMR: Turning to Version 5.0 of the ASAP reporting standard, what were the key changes made to the standard?
Keep reading with a 7-day free trial
Subscribe to Pharmacy Technology & Management Review to keep reading this post and get 7 days of free access to the full post archives.