Enforcing Data Integrity in Pharmacy

Enforcing Data Integrity in Pharmacy

C. David Butler (Teradata, Inc., USA)
DOI: 10.4018/978-1-4666-0309-7.ch015
OnDemand PDF Download:
No Current Special Offers


Data integrity is essential to every organization and to every healthcare practitioner in order to ensure the correct use of patient information to optimize care. It provides the assurance that the data you see every day is the same as it was the day before. It assures you that the drug dosage regimen “QID,” whether you define it as four times daily or four times daily with meals and at bedtime, is applied using the same parameters for every patient, as you define a patient, across every day (or any time period), as you define day in your health care setting. Definitions about data must be made by the business person (the practitioner), rather than by Information Technology (IT). Only by doing this can appropriate business rules by applied by a database, which manages the information used in electronic medical records. Once a decision is made about what a datum represents, whether by an individual or a group, it is imperative that the decision remain consistent over time. Should the definition evolve, it is also imperative that that evolution be tracked. Thus, organizations must establish governance committees to maintain consistency both across an organization and across time. Governance committees must have the highest level of authority to ensure that rules are not overridden on a casual, intermittent basis. Once business rules for data have been established, use of a relational database provides one of the strongest tools for ensuring that data integrity is maintained. This chapter explores the concepts serving as the foundation for today’s relational database management systems. A top-down approach is described using an Entity-Relationship diagram that can be used to create a relational model for implementation in a relational database management system. A bottom-up approach is described using functional dependencies and normalization. A pharmacist should be able to apply these concepts in corporation with a database architect to ensure the appropriate, consistent use of drug data within an organization. A pharmacist must be able to validate all drug information being used across the organization in order to minimize medication errors and optimize patient care. Only by being the subject matter expert on governance committees and working closely with IT and quality assurance can pharmacy maintain appropriate control over the use of drug information by healthcare technology.
Chapter Preview


Edward (Ted) Codd first proposed the relational model in 1970 (Codd, 1970). The relational model is based on first-order predicate logic. Since that time, an RDBMS has become the primary tool for storing and retrieving data across major organizations. It has also been applied to applications focused on personal storage and retrieval of data. Much of this growth has come from the simple, elegant principle of the relational model, along with its accompanying query language, SQL. Relations and tables differ (Date, 2004). However, RDBMs minimize these discrepancies and this author minimizes differences between the two terms in order to make it easier on the reader.

Complete Chapter List

Search this Book: