The Data Quality Equation
Regulatory agencies around the globe are focused on assuring patient safety and product quality; if we focus on the latter, product quality, many regulations and guidance identify the elementary expectations to achieve it. Product quality is derived from quality data that supports or gives evidence to the quality of the product. Recent regulatory observations direct industry to the conclusion that there can be severe penalties for not having data quality that leads to product quality.
What is Data Quality and how do we achieve it?
Data Integrity provides data we can trust and it is also the foundation of the Data Quality Equation. Data Management is the process by which we create, control, manage, utilize and maintain our data’s integrity. The combination of Data Integrity and Data Management results in Data Quality. In other words, Data Quality is mutually dependent on both Data Integrity and Data Management. Subsequently, Data Quality can be represented as:
Data Integrity + Data Management = Data Quality
Another element of this equation that should be considered is that better Data Integrity and/or better Data Management would produce better Data Quality. For example, if a more efficient means for Data Management can be created that eliminates risk and adds value to the process you can in turn realize fewer mistakes and higher Data Quality. Conversely, Data Quality with Data Integrity but without Data Management lacks control of your data. Similarly Data Management without Data Integrity will lack the elements necessary to have Data Quality.
Data Integrity can be expressed in ALCOA+ elements, where the acronym stands for Attributable, Legible, Contemporaneous, Original, Accurate, complete, consistent enduring and available. Data Integrity is achieved when all ALCOA+ elements are present.
- HPLC & Gas Chromatography (GC) computer software lacked active audit trail functions to record changes to data, including information on original results, the identity of the person making the change, and the date of the changes.
- At least five HPLCs were used with software audit trail function not enabled, resulting in the fact that raw data sample sets could not be satisfactorily verified.
- GC software lacked active audit trail functions to record any changes to the data, including the previous entries, who made the changes & when the change were made.
- Use of correction tape over multiple entries of raw material batch number in a log book.
- The audit trail feature for your gas chromatography (GC) instruments was not used until October 2013, even though your 2009 GC software validation included a satisfactory evaluation of the audit trail capability.




