In the modern laboratory, software is as critical as any piece of equipment. From Laboratory Information Management Systems (LIMS) to complex Excel spreadsheets, the software used to manage and process data must be validated to ensure the integrity of your results. This guide provides a roadmap for achieving compliance with the software requirements of ISO/IEC 17025.

The ALCOA+ Principles of Data Integrity

Your software validation process should be built around the ALCOA+ principles of data integrity:

  • Attributable: Who performed an action and when?
  • Legible: Can you read the data?
  • Contemporaneous: Was the data recorded as it was generated?
  • Original: Is the data a true copy of the first recording?
  • Accurate: Does the data reflect the true value?
  • Complete: Is all the data there?
  • Consistent: Is the data presented in a consistent format?
  • Enduring: Will the data be available for the required retention period?
  • Available: Can the data be accessed when needed?

Validating a LIMS

Validating a commercial off-the-shelf (COTS) LIMS can be a daunting task. The key is to take a risk-based approach. Focus your validation efforts on the critical functions of the LIMS, such as:

  • Sample tracking and management
  • Data entry and calculations
  • Reporting of results
  • Audit trails

Validating Complex Spreadsheets

Excel spreadsheets are a common source of data integrity issues. A spreadsheet used for complex calculations or to make decisions must be validated. The validation process should include:

  • Cell Protection: Lock all cells that contain formulas or constants.
  • Formula Auditing: Use Excel's built-in formula auditing tools to check your calculations.
  • Independent Verification: Have a second person independently verify the calculations.
  • Version Control: Have a system for tracking changes to the spreadsheet.

The Bottom Line

Software validation is not a one-time event. It is an ongoing process that requires vigilance and a commitment to data integrity. By taking a risk-based approach and focusing on the critical functions of your software, you can build a compliant system that you can trust.