• There are no suggestions because the search field is empty.

What to focus on when validating a computer system? (2)

Author Avatar
QbD Group
Software Solutions & Services
Pharma & Biotech

In the first blog we discussed the definitions of validation and computerized systems. Checking the fitness of the system is to check whether the system operates according to the needs of the process for which it is acquired.

What to focus on when validating a computer system? (2) | QbD Group
2:40

When categorizing, GAMP5® takes two main aspects of a system into account: the complexity and the inherent risk. The more standard and tested software is, the lower the category and the lower the validation effort for the end user. However, the more customized the software is, the higher the category. Thus, the more testing / verification is required. 

QbD 5 categories for succes

To determine which of the inventory’s computer systems has an impact on GxP processes, some characteristics should be assessed. It is possible that the same system possesses one or more of these characteristics. A computer system has an impact on GxP processes if: 

  • The creation, maintenance or preservation of records or documentation is related to GxP businesses, such as evaluating product quality and making security decisions; 
  • Automation best practices, product quality or decisions have an impact on product safety;
  • The data is used as input or output for or from other system and that data is GxP related.

Examples of impact on GxP are:

  • Patient safety: the release of products and managing information for patient use (batch, instructions, expiration), e.g. HPLC, software coding, etc.
  • Product quality: systems directly involved in making or evaluating critical parameters, e.g. IR spectrum, TOC, PLC or an autoclave, etc.
  • Data integrity: the ERP systems, inventory control, document management systems, etc.
  • Regulatory compliance: SGC control systems, spreadsheets with training plans or maintenance control, electronic logbooks, etc.
  • Internal policies: systems that manage the qualification of personnel, security systems, etc.

A category 1 most likely doesn’t require validation. An example of a category 1 is the commercial operating system, e.g. Windows, Linux. These infrastructure systems serve the application to function. They are verified and tested indirectly during validation. A verification of the installation and version control must be in place.

Furthermore, if computer systems do not have an impact GxP businesses evidence of this should be provided, for example through a system characterization with the help of a checklist. 

Hopefully this gives you an impression of what to focus on when it comes to validation efforts. Our next blog will talk about what else can impact product quality. In the meanwhile, please contact us if you have any questions concerning computer system validation!

 

Stay ahead in life sciences

Keeping up with the fast-paced life sciences industry doesn’t have to be overwhelming.

Our newsletter delivers the latest insights, industry updates, and expert content directly to your inbox, helping you stay informed and make smarter decisions.

Circles-banner-short

Discover more expert content

preview_image
Webinar

From Requirements to Code: a unified MDSW development cycle that covers all requirements

Watch our webinar on demand to master medical device software development. Learn about IEC standards, cybersecurity, AI integration, and FDA expectations.
preview_image
Whitepaper

Mobile health on the rise: exploring the regulatory landscape for reimbursement

This whitepaper will help you navigate the maze of the DTx regulatory environment, highlighting several important countries and regulations.
preview_image
Whitepaper

GAMP 5 Software Validation Approach for GMP, GCP and GLP regulations

Learn how to comply with GMP, GCP, and GLP regulations using the GAMP 5 Software Validation Approach. Download the whitepaper for more insights.
preview_image
Webinar

Getting Started: Overcoming Initial Obstacles in Medical Device Software Development

Watch our webinar on demand and learn about regulatory obstacles, MDR, AI Act, and best practices for medical device software development and market entry.
preview_image
Blog

What Makes Usability Testing Crucial for Near-Patient and Self-Testing Devices under IVDR?

It shouldn’t be a surprise that today, “Near-Patient Testing (NPT)” and...
preview_image
Blog

When does Annex XIV apply in Performance Studies, and what key documentation is needed for compliance?

In the European regulatory landscape, conducting performance studies for in...
preview_image
Blog

How to define your Clinical Performance Strategy?

1. Start with a clear intended purpose A strong clinical...
preview_image
Blog

The Holy Grail: Achieving Inspection Readiness

In a previous blog post, we talked about the various activities...