In July 2023, the FDA issued a warning letter to Intas Pharmaceuticals Limited, citing critical data integrity lapses. These included aborted chromatographic sequences, inadequate oversight of CGMP documents, and insufficient controls over computerized systems. The FDA found instances where laboratory staff aborted chromatographic runs without investigation, raising concerns about the reliability of analytical data. These oversights pointed to a lack of a robust data integrity culture.

This example underscores that data integrity isn’t merely about compliance checklists. It requires embedding a culture where every team member values accurate and reliable data. For startups, building this culture early is essential for long-term success and operational resilience.

Why Culture Matters

One of our client’s CDMOs failed to maintain proper source data for analytical method validation, leading to delays and costly rework during their regulatory submission. This wasn’t just a technology issue but a reflection of an organizational culture that didn’t prioritize DI. A robust DI culture acts as the glue that binds all compliance and operational activities. Without it, even the most advanced systems and processes can fail.

Startups, in particular, face challenges because they often lack dedicated compliance teams. Instead, DI responsibilities are distributed among employees who are more focused on scientific and operational goals. This dual responsibility makes it even more crucial to embed DI into daily activities.

Practical Steps to Build a DI Culture

1. Leadership Commitment: Change starts at the top. When leadership prioritizes DI and visibly supports initiatives, employees are more likely to follow suit. Regularly communicate its importance and link it to the company’s mission.
2. Comprehensive Training: DI training should go beyond explaining guidelines. Use real-world examples to illustrate the consequences of failures and successes. For example, during an audit for one of our clients at their facility, employees ignored critical system error messages instead of reporting them, potentially compromising data. Training emphasized the importance of addressing such errors to prevent similar risks.
3. Empower Employees: Employees are often the first to identify potential DI issues. Create an environment where they feel empowered to raise concerns without fear of repercussions. Encourage feedback and suggestions on improving DI processes.
4. Align Incentives: Avoid creating incentives that conflict with DI principles. For instance, a company that prioritized speed and success in tests over accuracy found employees bypassing controls to meet performance targets, jeopardizing data reliability.
5. Integrate DI into KPIs: Measure and reward adherence to DI standards. KPIs can include audit compliance rates, training completion, and incident reporting.

The Role of Technology

While culture is the foundation, technology plays a supporting role. For example, one QC lab configured its systems to restrict access and monitor activities using audit trails, reinforcing DI principles. Another team reformatted invalid Excel sheets used in bioanalytical services, securing the source data and ensuring verification processes aligned with DI standards. However, these tools are only effective when paired with a workforce that understands and values their purpose.

Many startups seek mock inspection services to evaluate their compliance readiness before regulatory reviews. Additionally, ensuring chemistry manufacturing controls meet industry standards plays a vital role in maintaining data integrity.

Building a DI culture is an investment in your company’s future. It not only ensures compliance but also strengthens investor confidence and operational efficiency. By embedding DI into your organization’s ethos, you set the stage for sustainable growth and innovation.

You are invited to watch the next YouTube video for more information on the topic

One of the most common challenges for startups is navigating the labyrinth of regulatory requirements—particularly when it comes to computerized systems validation (CSV). Take, for example, a biotech company that invested in a lab system advertised as “21 CFR Part 11-compatible.” They rested assured, believing that the vendor’s certification guaranteed compliance. However, they later discovered that accessing the system’s audit trail required vendor intervention, a process that introduced delays and increased costs. This scenario highlights a critical misconception—compatibility does not equate to compliance, and relying solely on vendor assurances can leave companies vulnerable.

Understanding 21 CFR Part 11

Part 11 governs the use of electronic records and signatures to ensure they are as reliable as their paper counterparts. Its objectives include ensuring the authenticity, integrity, and traceability of electronic data.

Core requirements include:

• System Validation: Ensuring systems perform reliably and consistently.
• Audit Trails: Tracking all changes to records.
• Access Controls: Restricting data access to authorized personnel.
• Electronic Signatures: Linking signatures to their corresponding records.

Compliance vs. Compatibility

Using a Part 11-compatible system is a good starting point, but it’s not enough. Compatibility means the system has features that can support compliance, such as audit trails and user controls. Compliance, however, requires proper governance, processes, and training.

What to Do When Systems Are Not Compatible or Compliant

For startups using systems that fall short in compatibility or compliance, solutions exist. Addressing these issues proactively can save time and prevent costly setbacks:

1. Assess System Gaps: Conduct a gap analysis to identify missing features or functionalities in your systems. Engage with the vendor to understand the limitations and determine if upgrades or additional configurations are possible.
2. Implement Procedural Workarounds: If your system lacks certain compliance features, establish robust standard operating procedures (SOPs) to address these gaps. For instance, in one case, manual audit trail reviews became an interim solution while a company planned its long-term CSV strategy.
3. Leverage Third-Party Tools: Consider integrating third-party software to enhance existing system capabilities. Tools that provide audit trail management or validation support can bridge gaps while maintaining compliance.
4. Train Personnel Extensively: Equip your team with detailed training to handle non-compliant systems effectively. In one instance, an employee’s confusion about deleting results underscored the importance of well-defined SOPs and training.
5. Plan for Future Investments: While short-term fixes can address immediate needs, long-term planning should focus on transitioning to compliant systems. One client’s hybrid approach, combining electronic and paper records, mitigated risks while paving the way for system upgrades.

Lessons from the Field

Failures in CSV can create vulnerabilities. For example, an HPLC system permitted uncontrolled data generation through its operation panel, highlighting risks such as the absence of audit trails to monitor changes or the lack of access restrictions to prevent unauthorized modifications. These gaps emphasize the importance of addressing unvalidated systems to mitigate operational risks effectively. By physically disabling this feature, a company ensured stricter controls and mitigated risks. Such proactive measures demonstrate the importance of combining technological fixes with operational safeguards.

Why Compliance Matters

Non-compliance can lead to severe consequences, from rejected submissions to tarnished reputations. More importantly, it’s about safeguarding the integrity of the data that underpins every decision in pharmaceutical development.

Many startups seek regulatory consulting to help navigate these compliance challenges and align their operations with regulatory expectations. Another critical aspect is quality assurance in clinical trials, ensuring that all procedures and documentation adhere to the highest industry standards.

By bridging the gap between technology and governance, startups can achieve not just compliance but also operational excellence. Startups aiming to navigate the complexities of 21 CFR Part 11 can gain actionable insights here to align their operations with regulatory expectations.

You are invited to watch the next YouTube video for more information on the topic

In pharmaceutical startups, expertise often centers on the science and innovation needed to bring products to life, leaving peripheral but critical activities—like data integrity (DI)—underprioritized. While DI is widely acknowledged as essential, many founders and teams struggle to understand the expectations and tools available to meet them. Let’s break down why DI matters, its core principles, and how startups can integrate it seamlessly into their operations.

What is Data Integrity?

At its core, data integrity ensures “the whole truth and nothing but the truth.” This principle plays a pivotal role in distinguishing between original and raw data, as highlighted in the webinars. Original data refers to the certified copies or initial records necessary for reconstructing findings, such as signed case report forms or instrument outputs. On the other hand, raw data includes unprocessed readings or observations directly from laboratory instruments. For example, in one instance shared during the series, raw data from a laboratory’s pH meter had to be meticulously validated and preserved as source data to ensure its reliability for future analysis and regulatory submissions. It signifies the extent to which your data can be trusted. Reliable data must be complete, consistent, and accurate at every stage—from generation and processing to storage and eventual archiving.

Regulatory bodies like the FDA, EMA, and MHRA mandate adherence to DI principles. Their guidelines emphasize robust data management systems, good documentation practices, and cultivating a culture where employees value DI. Many startups turn to biopharma regulatory consulting to help them navigate these complex requirements and ensure compliance from the outset.

Why is Data Integrity Critical?

Data is the lifeblood of pharmaceutical development. Consider these critical aspects:

1. Regulatory Submissions: Data integrity is foundational for regulatory approvals. A single error could result in rejections or costly delays.
2. Investor Confidence: Startups thrive on investment, and reliable data builds trust with investors who assess risk based on your records.
3. Operational Efficiency: Solid data practices prevent errors, reduce redundancies, and save valuable time and resources.

This focus on DI must extend beyond internal systems to include external partners. In one case, a CDMO’s failure to maintain proper source data caused delays during a client’s regulatory submission. The regulatory burden is shared, and startups must ensure all collaborators meet the same high standards.

One key aspect of preparedness is inspection readiness. Regulatory agencies may conduct audits at any time, and companies must be equipped to demonstrate compliance. This requires proactive planning, robust documentation, and continuous training to ensure data integrity is maintained across all operations.

The ALCOA+ Principles

To ensure reliable data, startups must adhere to the ALCOA+ principles:

• Attributable: Know who generated the data.
• Legible: Ensure data is easy to read and understand.
• Contemporaneous: Record data at the time of its generation.
• Original: Preserve the initial data or its verified true copies.
• Accurate: Data must reflect reality without distortion.

The “plus” expands these principles to include completeness, consistency, enduring accessibility, and availability on demand.

Embedding DI into Your Operations

Here’s how startups can prioritize DI:

• Train Your Team: Ensure all staff understand their role in maintaining DI. Insufficient training often leads to compliance gaps, such as employees unintentionally bypassing controls. During a recent audit, untrained staff ignored system alerts, emphasizing the need for structured DI training.
• Validate Systems: Confirm all computerized systems adhere to regulatory requirements. A client’s use of a hybrid approach combining paper and electronic systems highlights the importance of defining interim solutions while planning long-term upgrades. One startup implemented a Windows-based workaround for an outdated system, leveraging built-in access controls and logs as an interim compliance measure.
• Audit Regularly: Conduct internal and external audits to identify and address gaps.
• Document Thoroughly: Maintain detailed records that demonstrate adherence to DI principles.

In today’s highly regulated pharmaceutical landscape, data integrity is non-negotiable. It’s not just about compliance; it’s about building a foundation of trust that supports innovation, growth, and, ultimately, better patient outcomes. This article is the first in a four-part series designed to help startups navigate the complexities of data integrity, ensuring they meet regulatory demands while building robust operational frameworks.

You are invited to watch the next YouTube video for more information on the topic