Cleaning Solution and a Disinfectant Solution

To the average person on the floor, there are just things to clean with. However, cleaning and sanitization are very different, and it’s important to recognize this and ensure folks are properly educated. I can’t count how many audits I’ve had where this became a tripping point.

The primary difference between a cleaning solution and a disinfectant solution lies in their purposes and the outcomes they achieve.

Cleaning Solutions

Purpose: Cleaning solutions are designed to remove dirt, dust, grime, and impurities from surfaces. This process involves using soap, detergents, or other cleaning agents combined with water and physical action (e.g., scrubbing) to lift and wash away contaminants.

Effectiveness: Cleaning physically removes germs from surfaces but does not necessarily kill them. It reduces the number of germs and prepares the surface for further treatment, such as sanitizing or disinfecting.

Examples: Common cleaning agents include all-purpose cleaners, dish soap, and glass cleaners.

Disinfectant Solutions

Purpose: Disinfectant solutions are specifically formulated to kill or inactivate harmful microorganisms on surfaces, including bacteria and viruses. They contain chemical agents that are effective against a wide range of pathogens.

Effectiveness: When used correctly, disinfectants are designed to kill nearly 100% of the germs listed on their labels. They are regulated by the Environmental Protection Agency (EPA) and must meet stringent efficacy standards.

Examples: Common disinfectants include bleach solutions, alcohol-based solutions, and products containing quaternary ammonium compounds (QUATS).

Here is a table comparing the key differences between cleaning solutions and disinfectant solutions:

Aspect	Cleaning Solutions	Disinfectant Solutions
Purpose	Remove dirt, dust, grime, and impurities	Kill or inactivate harmful microorganisms
Effectiveness	Physically removes germs but does not necessarily kill them	Kills nearly 100% of germs listed on their labels when used correctly
Examples	All-purpose cleaners, dish soap, glass cleaners	Bleach solutions, alcohol-based solutions, QUATS
Function	Reduces the number of germs	Kills or inactivates germs
Usage	First step in the cleaning process	Applied after cleaning to kill remaining germs
Regulation	Not always regulated by the EPA unless they have sanitizing or disinfecting claims	Must be registered with the EPA and meet specific efficacy standards
Contact Time	Not applicable	Requires specific contact time (usually 5-10 minutes)
Safety	Generally safer, fewer precautions needed	May require precautions such as gloves or ventilation
Impact on Equipment	Less likely to cause wear and tear on equipment	Can be harsh on surfaces and equipment, potentially causing damage over time

Comparison of the key differences between cleaning solutions and disinfectant solutions

Method Qualification and Validation

The terms “method qualification” and “method validation” are often used in the context of analytical procedures in the pharmaceutical and biotechnology industries. While related, they serve different purposes and are applied at different stages of method development. Here is a detailed comparison of the two:

Method Qualification

Definition

Method qualification demonstrates that an analytical method is suitable for its intended use during the early stages of development. It involves preliminary testing to ensure the method can produce reliable and reproducible results for the specific application.

Purpose

Early Development: This is typically performed during the early phases of drug development (e.g., preclinical and Phase I clinical trials) to assess the method’s feasibility.
Optimization: Helps in optimizing the method to ensure it meets the necessary performance criteria before full validation.
Feasibility Studies: Often referred to as feasibility or pre-validation studies, method qualification helps understand the method’s performance characteristics and establish preliminary acceptance criteria.

Characteristics

Flexibility: The method can still be modified and optimized based on the results obtained during qualification.
Parameters: This evaluation method evaluates fewer parameters than validation, focusing on key performance indicators like specificity, linearity, accuracy, and precision.
Voluntary: This is not always required by regulatory authorities, but it is a good practice to ensure the method is on the right track for future validation.

Example

A company developing a new drug might perform method qualification to ensure that their analytical method can accurately measure the drug’s concentration in biological samples before moving on to more rigorous validation studies.

Method Validation

Definition

Method validation proves that an analytical method is suitable for its intended purpose and can consistently produce reliable and reproducible results under specified conditions. It is a regulatory requirement for methods used to test drug substances and products.

Purpose

Regulatory Compliance: Required by regulatory authorities (e.g., FDA, EMA) for methods used in quality control and release testing of pharmaceutical products.
Late Development: This is typically performed during the later stages of drug development (e.g., Phase III clinical trials, and commercial production) when the method is fully developed and optimized.
Consistency: Ensures that the method produces consistent results over time and across different laboratories.

Characteristics

Rigidity: The method must be fully developed and optimized before validation. Any changes to the method after validation would require re-validation.
Comprehensive: Involves a thorough evaluation of multiple parameters as defined by guidelines such as ICH Q2(R1), including accuracy, precision, specificity, linearity, range, limit of detection (LOD), limit of quantification (LOQ), robustness, and ruggedness.
Mandatory: Required by regulatory authorities to ensure the quality, reliability, and consistency of analytical results.

Example

Before a pharmaceutical company can market a new drug, it must validate its analytical methods to demonstrate that they can reliably measure the drug’s potency, purity, and stability according to regulatory standards.

Key Differences

Aspect	Method Qualification	Method Validation
Stage of Development	Early stages (pre-clinical, Phase I)	Later stages (Phase III, commercial production)
Purpose	Feasibility and optimization	Regulatory compliance and consistency
Flexibility	Method can be modified	Method must be fully developed and optimized
Parameters Evaluated	Fewer, key performance indicators	Comprehensive, as per regulatory guidelines
Regulatory Requirement	Voluntary, good practice	Mandatory

In summary, method qualification is an early-stage activity aimed at ensuring that an analytical method is on the right path to becoming reliable and reproducible, while method validation is a more rigorous, comprehensive process required to demonstrate that the method meets all regulatory requirements for its intended use.

Practicing Humbleness

My greatest weakness is my poor track record of practicing humbleness. Balancing humility with assertiveness in professional life is essential for effective leadership and personal growth. It is critical to being an expert. So here are the things I remind myself of and practice as part of my mindfulness.

Acknowledge your limitations and knowledge gaps

Be open about areas where you still have more to learn
Admit when you don’t know something or are uncertain
Recognize that expertise in one area doesn’t make you an expert in everything

Remain open to learning from others

Listen attentively to different perspectives and ideas
Be willing to change your views based on new information
Seek out opportunities to expand your knowledge

Give credit to others

Recognize the contributions and insights of colleagues and mentors
Share credit for successes and accomplishments
Use “we” instead of “I” when discussing team achievements

Practice gratitude

Express appreciation for opportunities you’ve had to develop expertise
Thank those who have supported your growth and learning
Be grateful for chances to share your knowledge with others

Stay curious and ask questions

Maintain a learner’s mindset, even as an expert
Ask thoughtful questions to deepen your understanding
Be open to new ideas and approaches in your field

Focus on serving others with your expertise

Use your knowledge to help and empower others
Prioritize making a positive impact over personal recognition
Share your expertise generously without expectation of reward

Reflect on your journey and growth

Remember the challenges you faced in developing your expertise
Consider how much more there is still to learn in your field
Appreciate the ongoing nature of learning and development

Accept and learn from criticism and feedback

Be open to constructive criticism of your work
Use feedback as an opportunity for improvement
Avoid becoming defensive when your ideas are challenged

By consistently practicing these behaviors, we can maintain humility while confidently sharing our expertise. This approach allows us to continue growing professionally while fostering positive relationships and respect from colleagues and peers.

NIST SP 800-171

One of the reasons I joined my organization is that I wanted to experience being a Department of Defense contractor. The work Evotec is doing is just super fascinating, so it was hard to resist.

This means I am taking a NIST SP 800-171 crash course as I figure out what it means to comply with Compliance with the Defense Federal Acquisition Regulation Supplement (DFARS) cybersecurity clause 252.204-7012. I swear this makes Part 11 look like the kindergarten it is.

NIST SP 800-17 has 110 security requirements across 14 control families, including:

Access Control
Awareness and Training
Audit and Accountability
Configuration Management
Identification and Authentication
Incident Response
Maintenance
Media Protection
Personnel Security
Physical Protection
Risk Assessment
Security Assessment
System and Communications Protection
System and Information Integrity

It spells out self-assessment and implementation of the security requirements. Organizations must:

Form an assessment team
Create an assessment plan
Collect relevant documents and evidence
Assess individual requirements
Create a plan of action for unmet requirements
Develop a System Security Plan (SSP)

Here’s a comparison of NIST SP 800-171 and ISO 27001 presented in a table format:

Aspect	NIST SP 800-171	ISO 27001
Purpose	Protect Controlled Unclassified Information (CUI) in non-federal systems	Provide framework for Information Security Management System (ISMS)
Scope	Focused on data security for CUI	Broader approach to overall information security management
Origin	U.S. National Institute of Standards and Technology	International Organization for Standardization
Primary Users	U.S. Department of Defense contractors and subcontractors	Organizations worldwide seeking robust information security
Certification	No formal certification process	Offers formal certification through third-party audits
Structure	110 security requirements across 14 families	114 controls across 14 domains (Annex A)
Flexibility	Prescriptive requirements	More flexible, risk-based approach
Mandatory Controls	All requirements are mandatory	No mandatory controls; risk-based selection
International Recognition	Primarily recognized in the U.S.	Globally recognized standard
Cost	Generally less expensive to implement	Can be more costly due to certification process
Maturity Model	Does not include a maturity model	Does not include a maturity model (but compatible with other maturity models)
Documentation	Less extensive documentation requirements	Extensive documentation requirements
Regulatory Compliance	Specific to U.S. DoD contracts	Can be adapted to various regulatory requirements

comparison of NIST SP 800-171 and ISO 27001

Cleaning Validation Checklist

I’m reviewing the status of cleaning validation. Here is the list I’m currently going through, just in case it helps others.

Develop a comprehensive cleaning validation master plan that outlines your overall approach, policies, and procedures for cleaning validation at your facility. This should cover all aspects of the cleaning validation lifecycle.
Ensure you have written standard operating procedures (SOPs) for equipment cleaning processes that address different scenarios (e.g., cleaning between batches, between product changes, etc.).
Have written cleaning validation protocols for each piece of equipment that cover common issues like sampling procedures and analytical methods.
Maintain thorough documentation of your cleaning validation studies, including the protocols, results, and final reports stating whether the cleaning process for each piece of equipment is valid.
Implement a continuous verification program for routine residue monitoring after initial cleaning validation.
Be prepared to demonstrate that your cleaning procedures can consistently clean equipment to predetermined standards using scientifically sound sampling and analytical test methods.
Have data available to support your rationale for residue limits, which should be logical, practical, achievable, and verifiable.
Be ready to explain your approach for different types of equipment (dedicated vs. multi-use) and how you handle potent compounds or other high-risk materials.
Review your cleaning agent selection process and be able to justify the cleaning methods and agents used.
Ensure you have a system in place for equipment maintenance and cleaning records.
Be prepared to discuss how you handle manual vs. automated cleaning processes and any associated validation differences.
Review past audits or inspections and ensure any previous findings related to cleaning validation have been addressed.

Let me know if I’ve missed anything.