Computers

Computers

II COMPUTERS Setting Up a QA System by Renato Cataldo, Jr., PharmD Q: I have been asked to coordinate our quality assurance (QA) system. Are there ...

1MB Sizes 10 Downloads 106 Views

II

COMPUTERS

Setting Up a QA System by Renato Cataldo, Jr., PharmD

Q: I have been asked to coordinate our quality assurance (QA) system. Are there software packages specifically for QA or should I adapt off-theshelf software program? A: Commercial software

programs are available for most standard QA activities, such as medication errors, adverse drug reactions, pharmacist inteIVentions, and drug use evaluations. QA software usually specializes in one type of monitoring. But to decide if you want a specific software package, you must first consider what kind of QA you plan to conduct. QA can vary greatly depending on the type of practice and information you wish to evaluate. The keys to QA are to define what you plan to measure, collect the data, and compare actual measurements to expected performance. To perform the QA evaluation adequately, hundreds of data elements may be required. A computer-assisted QA process can provide summary and cross-;reference data. Based on the type of QA you plan to conduct, one of the commercial products may conform to your needs. Carefully evaluate AMERICAN PHARMACY

the type of input required by the program, reports, and statistical capabilities. Ask yourself if the product will allow you to prospectively control the data collection process and limit unnecessary information. Most products also can customize reports. Several pharmacy QA products can assist you with information retrieval and analysis. Always review the current version and any upcoming additions or enhancements. Some of the current QA products include: The Evaluator, a product primarily intended for drug use evaluations; QARx, a QA and drug use review product; and The Formulary ADR, which focuses on adverse drug reactions. All the programs are IBM-compatible. Detailed information can be requested from the publishers (see box). If the commercial QA products do not meet your specifications, then a generic database or spreadsheet software programs can do your QA monitoring. Many pharmacists use this option. A spreadsheet may seem to be a great place to store data, but I usually recommend database products for QA because they offer greater flexibility and retain

all the statistical capabilities of spreadsheet software. Many of the generic database products available today can be used on the equipment you have available. Your computer's operation is controlled by specialized software and is referred to as the operating system. Most of the operating systems used by the business world (e.g., MSDOS, System 7, Unix) will work with database managers. You should verify what operating system you are working with before evaluating software. Even if you use a commercial QA product, you should learn how to use a generic database manager for other projects. There are two basic types of database products, relational and flat file. The relational database manager can be used to develop more complex databases with interrelationships between files. The flat file database product creates independent files that can be easily manipulated. If you have never tried a database product, then a flat file program may be a good place to start. Flat file databases such as PC-File, Personal RBase, Professional File, Q&A, and Reflex are inexpensive, relatively easy to learn, and easily purchased. To learn more about these products, read the reviews published in the microcomputer press. For example, the December 1991 PC Magazine (pp. 111 -167) published a comparison of the nonprogrammabIe databases.

Whether you decide on a pharmacy QA product or a more generic database manager, you should be able to monitor your activities efficiently. It will take time to learn how to use a new software product, but it will payoff significantly during the evaluation and review process. Renato Cataldo, Jr., PharmD, is director of microcomputer applications and assistant professor ofpharmacy administration, St. Louis College of Pharmacy, St. Louis, Mo.

February 1992/110 Vol. NS32, No.2