The prescription drug transaction results data 306 may include, without limitation, brand name, generic name, preferred name, order dosage, order quantity, refill number, refill cycle in days. This data is stored for each prescription drug requested during a session of server 26. For instance, the prescription drug could be a controlled drug or substance, such as, a C2-C5 drug. For each of these prescription drugs requested, the associated prescription drug transaction results are stored in pharmacy database structure component 300. Data 306 may also include filled confirmation information and denied confirmation information. The filled confirmation information includes the identity of the prescription drug requested and filled, a confirmation of the fulfillment, and the reason(s) the prescription drug was filled. The denied confirmation information includes the identity of the prescription drug requested and denied, a confirmation of the denial, and the reason(s) the prescription drug request was denied.

The prescriber data 308 may include, without limitation, first name, last name, DEA license number, NPI license number, and clinic/office address.

The pharmacist user data 310 may include, without limitation, user first name, user last name, user pharmacist national license number, and pharmacy employee number.

The pharmacy data 311 may include a transaction number, a merchant code, a pharmacy location number, a location category code, longitude of location, latitude of location, address of location, zip code of location, carrier code of the location and/or hot spot score for the location. The hot spot score is a range of scores indicative of the likelihood that the location is a hot spot for abuse of prescription drug requests.