FIG. 3 shows an example of a pharmacy database structure component 300. The prescription drug transaction access and monitoring computer system 24 in connection with the pharmacy database structure component 300 transforms isolated pharmacy transaction data of the multiple and disparate pharmacy transaction systems 12a, 12b and 12c into the pharmacy database structure component 300, which is an electronic tool for a pharmacist to make an informed decision regarding whether or not to prescribe a controlled prescription drug to an individual requesting the controlled prescription drug. The pharmacy database structure component 300 is a particular form of a database component. The structure of the pharmacy database component 300 does not exist in any singular pharmacy transaction system 12a, 12b and 12c, yet the pharmacy database component 300 is structured in such a manner that it can unify the pharmacy data from the disparate pharmacy transaction systems 12a, 12b and 12c. In this way, the pharmacy database component 300 is neutral to all of the pharmacy transaction systems 12a, 12b and 12c. In addition, the computer system 24 is configured to cloak, or otherwise encode or encrypt, sensitive and confidential pharmacy information transmitted from the pharmacy transaction systems 12a, 12b and 12c, including any information that would allow a user of the present system to associate the data with a specific pharmacy merchant, location or chain. This cloaking capability is used to preserve the confidentiality of one pharmacy's information from a competitive pharmacy's viewing.