ASAP A History of Working with PDMPs

1. ASAP ASAP A History of Working with PDMPs American Society for Automation in Pharmacy 492 Norristown Road • Suite 160 • Blue Bell, PA 19422 610/825-7783 • 610/825-7641 (fax) • www.asapnet.org

2. A History of Working with PDMPs • First ASAP standard developed in 1995 Standard has evolved over the years, based on requests from PDMPs to: • Improve the quality of the information reported to better detect abuse and diversion. • Expand the data elements for a more complete picture of those receiving controlled substances. • Refine examples on how to submit data for specific data elements. • ASAP Workgroups average 20 or so participants. Workgroups include representation from PDMPs, system vendors, drug chains, PDMP hubs and data collection organizations. • ASAP named as the reporting standard in state PDMP legislation enacted. • Latest ASAP standard required for SAMHSA grant funding.

3. A History of Working with PDMPs 4.2, the current version, published in September 2011. Minimal changes to Version 4.1. Example: Increased field lengthsfor a few data elements based on PDMP suggestions.  4.2 not only being used by retail and outpatient pharmacies, but veterinarians and physicians dispensing from stock. 4.2 used by pharmacies to report CS Rxs written by not only physicians but veterinarians and dentists as well.  4.2 can be used for real-time reporting as well as batch reporting.

4. A History of Working with PDMPs The required data elements form the minimum data set. These are the data elements states agreed must be reported. Optional data elements can be invoked based on a state’s reporting requirements.  Examples: Some states want the species reported (animal vs. human). Some states want an ID (military ID, driver’s license, tribal ID, green card, etc.) and first and last name of person dropping off or picking up the Rx, if different from the patient, and the relationship to the patient.  Other examples: Method of payment. Date sold vs. date dispensed.

5. A History of Working with PDMPs • Zero Report Standard  In 2011 added this standard in response to industry request that we needed one way to report when no controlled substances were dispensed during the reporting period. Workgroup had representation from all the stakeholders. • Error Report Standard Also added a common data structure and minimum data set to communicate specific errors identified by a PDMP within each batch file received that must be corrected and resent.

6. A History of Working with PDMPs • ASAP Web Service Standard • Published in January 2013, to move ad hoc queries on a person of interest into the workflow of a pharmacy management system and EHR system.  • XML based.  • Supports automated polling of PDMP data to see if anyone hit the state’s threshold for triggering an unsolicited report. Would happen as a background task. • Ad hoc queries can handle reference numbers and “pick lists” where probable matches are returned to ensure selection of the correct person of interest. • Supports all the data elements in the ASAP reporting standard in order to provide states with flexibility for the information provided in a response. • Provide sample program to facilitate implementation (tested and works).  • Low cost for PDMPs to implement (a prime consideration).   • It is cost neutral — there is no transaction charge involved for a query.  • Uses NIEM tags.

7. A History of Working with PDMPs • General • All ASAP standards are made available to PDMPs and state and federal agencies at no charge. • Have established a close working relationship with state programs over the years. • Have had regular attendance at Annual Harold Rogers National Meetings over the years to stay abreast of the issues facing PDMPs and how ASAP can respond.