Quality personnel were performing untimely investigations with poor practices. The firm's response: reduce the retention timeframe for aseptic operation records. No nonconformance was generated. No CAPA was initiated. No risk assessment was performed. The system changed to accommodate the failure rather than correct it. The Empower Pharma 483 reveals a quality system that adapts to dysfunction rather than eliminating it.
On November 14, 2025, FDA investigators issued a Form 483 to Empower Clinic Services, L.L.C., doing business as Empower Pharma, at their compounding facility in the United States. The lead observation was direct: “There is a failure to thoroughly review any unexplained discrepancy and the failure of a batch or any of its components to meet any of its specification whether or not the batch has been already distributed.” What the observation revealed was not a routine documentation gap. It was a quality system that responded to its own dysfunction by lowering expectations rather than correcting behavior.
The most striking finding concerned change control record CHR-0000005416. The firm identified that quality personnel were exhibiting “poor practices” and conducting “untimely investigation activities.” The response was to implement a change that reduced the retention timeframe for aseptic operation records. No nonconformance report was generated to document the poor practices. No CAPA was initiated to investigate why quality personnel were performing inadequately. No risk assessment was performed to evaluate the impact of reducing record retention on product quality or regulatory compliance. A quality-impacting change was made “without supporting documentation, data, or risk assessment.”
But the change control finding was only the beginning. The FDA found that from August 29, 2024, to the date of inspection, approximately 337 of approximately 963 nonconformance reports remained unresolved. That is roughly 35% of all NCs in the quality system — open, uninvestigated, unresolved. For a facility manufacturing compounded sterile drug products, where every deviation from aseptic practice carries direct patient safety implications, the backlog represents a systemic failure in nonconformance management.
When quality personnel exhibit poor practices, a functioning quality system investigates and corrects the behavior. At Empower Pharma, the system changed to accommodate the failure. The retention timeframe was reduced. The poor practices were never documented as nonconformances. The quality system adapted to dysfunction rather than eliminating it.
21 CFR 211.192 requires manufacturers to thoroughly review any unexplained discrepancy and the failure of a batch or any of its components to meet any of its specifications — whether or not the batch has already been distributed. 21 CFR 211.22 requires the quality control unit to have the authority and responsibility to approve or reject all procedures or specifications impacting the identity, strength, quality, and purity of drug products. Together, these regulations establish that quality events must be investigated with rigor, and that changes to quality procedures must be substantiated by data and risk analysis.
At Empower Pharma, the firm’s own quality personnel were identified as performing untimely investigations with poor practices. Under any functioning quality system, this finding should have triggered a nonconformance report, a root cause investigation, and a CAPA to address the personnel-level failure. Instead, the firm implemented change control CHR-0000005416 to reduce the retention timeframe for aseptic operation records — effectively adjusting the system to accommodate the behavior rather than correcting it. The FDA’s observation is precise: this change was made “without supporting documentation, data, or risk assessment.”
The nonconformance backlog compounds the severity. With 337 of 963 NCs unresolved, the quality system was not merely slow — it was structurally incapable of processing its own quality event volume. For a compounding pharmacy producing sterile injectables, unresolved nonconformances are not administrative inconveniences. Each one represents a potential product quality or patient safety issue that has been acknowledged by the system but not investigated, not resolved, and not corrected.
The FDA also cited three additional observations that reinforce the pattern. The firm failed to establish an adequate system for cleaning and disinfecting the room and equipment to produce aseptic conditions — room cleaning procedures were not followed between formulation of different active sterile injectable lots. Aseptic process simulations did not encompass the full aseptic process, with formulation and filling operations qualified separately rather than as a single integrated simulation reflective of routine production. And the firm failed to test samples of each component for identity and conformity with all appropriate specifications. Taken together, these findings describe a facility where the quality system was not controlling the manufacturing process — it was documenting the absence of control.
337
Nonconformance reports unresolved out of 963 total — approximately 35% of all NCs
0
CAPAs initiated to address documented 'poor practices' by quality personnel
0
Risk assessments performed before reducing aseptic record retention timeframes
4
Observations spanning nonconformance management, aseptic processing, contamination prevention, and component testing
The Empower Pharma 483 describes a quality system that failed in two distinct but related ways: it allowed quality-impacting changes to proceed without substantiation, and it allowed nonconformance volume to accumulate without resolution. Both failures trace back to architectural deficiencies in how the quality system enforces its own requirements.
Change control CHR-0000005416 reduced the retention timeframe for aseptic operation records based on reported quality personnel failures. Under 21 CFR 211.22, any change that impacts product quality must be substantiated by data, justified by risk assessment, and approved through a documented quality review process. At Empower Pharma, the change control system permitted this modification without any of those prerequisites. The system did not block a quality-impacting change from proceeding without a supporting nonconformance, without a CAPA, and without a risk assessment. When a change control system allows modifications to aseptic record retention timelines without requiring evidence that the change is safe, the system is not controlling changes — it is rubber-stamping them.
The firm identified that quality personnel were performing untimely investigations with poor practices. This is a quality event. Under any rigorous interpretation of 21 CFR 211.192, documented poor practices by the personnel responsible for quality oversight should generate a nonconformance, trigger a root cause investigation, and result in corrective action — whether that action involves retraining, reassignment, procedural revision, or resource reallocation. At Empower Pharma, none of these steps occurred because the quality system did not require them. The finding of poor practices existed as a narrative justification for a change control, not as a quality event in its own right.
337 of 963 nonconformances sat unresolved across a period of approximately 15 months. This accumulation is not sudden; it is gradual, and a quality system with aging alerts, mandatory escalation timelines, and management review triggers should surface it long before it reaches 35% of total NC volume. When nonconformances can remain open indefinitely without automated escalation to site quality leadership and without blocking related production activities, the backlog is not a failure of individual investigators — it is a failure of system design.
The Empower Pharma finding is fundamentally a quality culture story. Quality personnel were performing poorly. The organizational response was to lower the bar — reduce record retention requirements — rather than raise performance. This pattern occurs when quality systems do not have mechanisms to capture and escalate cultural and behavioral indicators as quality events. When poor investigation practices are treated as an operational annoyance rather than a nonconformance requiring root cause analysis, the quality system has a blind spot for the most important category of failure: the failure of the quality function itself.
The firm identified the problem: quality personnel were performing untimely investigations with poor practices. The firm chose a solution: reduce the retention timeframe for aseptic operation records. The question every quality leader should ask: does our change control system allow that sequence?
Each comparison below addresses a specific gap documented in the Empower Pharma 483. The architectural approach does not add layers of manual review — it makes it structurally impossible for quality-impacting changes to proceed without evidence, and for nonconformances to accumulate without resolution.
Change control initiated based on narrative justification. No system requirement to link the change to a nonconformance, CAPA, or risk assessment. Quality-impacting changes to aseptic record retention timelines proceed through the change control workflow without automated checks for supporting documentation. The change is approved because the system does not block approval in the absence of evidence.
Change control system requires linkage to a triggering quality event (nonconformance, deviation, or CAPA) before a quality-impacting change can be initiated. Changes affecting GMP-critical procedures — including record retention for aseptic operations — require a completed risk assessment and documented rationale before the change can advance to the approval stage. The system blocks progression when prerequisites are missing, not when a reviewer catches the gap.
Nonconformances are opened and assigned to investigators. No automated aging alerts. No mandatory escalation timelines. No management visibility into NC backlog trends. 337 NCs accumulate over 15 months without triggering a systemic review. Quality leadership discovers the backlog when the FDA does — during the inspection.
Each nonconformance is assigned a resolution deadline based on severity classification. Automated aging alerts notify investigators, supervisors, and site quality leadership at configurable intervals. NCs that exceed their resolution window are automatically escalated and flagged in management review dashboards. Production holds can be triggered automatically when NC volume in a specific area or process exceeds defined thresholds. The system makes backlog accumulation visible and actionable before it becomes systemic.
Quality personnel performance problems — untimely investigations, poor practices — are addressed through operational channels: memos, verbal coaching, procedural changes. The behaviors are never captured as nonconformances. No root cause investigation determines why performance degraded. No CAPA addresses the systemic conditions that enabled it. The quality system has no record that the failure occurred.
Investigation timeliness is tracked automatically. When NC resolution rates fall below defined thresholds, the system generates a quality event — a nonconformance against the quality process itself. Root cause investigation examines whether the failure stems from workload imbalance, training gaps, procedural complexity, or resource constraints. Corrective actions are tracked within the same NC/CAPA system that manages product quality events. The quality system monitors its own health.
Preventing the Empower Pharma pattern requires a quality system that enforces its own standards — where changes cannot bypass substantiation, nonconformances cannot accumulate without escalation, and quality function failures are treated as quality events requiring investigation.
A change control system must enforce prerequisite documentation for any change that impacts GMP-critical procedures. When a change is initiated to modify aseptic record retention, cleaning procedures, or investigation timelines, the system must require linkage to a triggering quality event, a completed risk assessment, and documented data supporting the change before it can advance to approval. The change that occurred at Empower Pharma — reducing aseptic record retention without a nonconformance, without a CAPA, without a risk assessment — must be architecturally impossible. This is not about adding another reviewer to the approval chain. It is about making the system incapable of advancing a change without evidence.
337 unresolved nonconformances do not appear overnight. They accumulate gradually, and a quality system with automated aging controls should surface the trend long before it reaches 35% of total NC volume. Each NC must have a severity-based resolution deadline. Automated escalation must trigger at configurable aging intervals — notifying investigators, supervisors, and site quality leadership progressively. Management review dashboards must display NC aging trends, open/close ratios, and resolution velocity. When the backlog is visible in real time, the organizational response happens before the FDA inspection, not during it.
The most significant architectural gap at Empower Pharma was not in how the system handled product quality events — it was in how the system failed to handle a quality function failure. When quality personnel perform poorly, the quality system must treat that as a quality event. Investigation timeliness, NC closure rates, CAPA effectiveness metrics, and change control substantiation compliance should all be monitored automatically. When these internal quality metrics fall below defined thresholds, the system must generate a nonconformance against the quality process itself — triggering the same root cause investigation and CAPA workflow that would apply to any manufacturing deviation.
30
Running on a single integrated quality platform (Cipla deployment)
100%
21 CFR Part 11 compliance across 10+ sites (Piramal deployment)
2,700
Through digitized batch records and automated workflows (Valent BioSciences)
The objective is not to add more oversight to a broken process. It is to build a quality system where the failures documented at Empower Pharma — changes without evidence, nonconformances without resolution, quality failures without investigation — are architecturally impossible.
Review all change controls initiated in the past 24 months. For each one: was there a triggering quality event? Was a risk assessment performed? Was supporting data documented? The Empower Pharma 483 tells you exactly what the FDA will look for. Then audit the NC backlog: how many NCs are open beyond their target resolution date? What is the aging distribution? Which areas or processes have the highest concentration of unresolved events? Finally, evaluate quality personnel performance metrics — investigation timeliness, NC closure rates, CAPA completion rates — as quality indicators, not just operational metrics. Map the current state before the FDA maps it for you.
Configure the change control system to require mandatory linkage to triggering quality events, completed risk assessments, and documented data for any change affecting GMP-critical procedures. Implement automated NC aging alerts and escalation workflows with severity-based resolution timelines. Deploy management review dashboards that display NC backlog trends, aging distributions, and resolution velocity in real time. Build quality system self-monitoring — automated nonconformance generation when internal quality metrics (investigation timeliness, closure rates, CAPA effectiveness) fall below defined thresholds. The goal is a quality system that monitors its own health with the same rigor it applies to product quality.
Validate the quality system under 21 CFR Part 11 requirements with complete audit trails and electronic signatures at each workflow gate. Run challenge scenarios that mirror the Empower Pharma findings: attempt to advance a change control without a linked nonconformance or risk assessment and verify the system blocks it. Simulate NC aging beyond resolution deadlines and verify that escalation triggers fire correctly. Generate quality personnel performance data that falls below thresholds and verify that the system creates a nonconformance against the quality process. Document the validation evidence. When the FDA arrives, the system's architecture should demonstrate that the Empower Pharma failure pattern is not possible — not because people are trained to avoid it, but because the system will not allow it.
Empower Pharma’s quality personnel were performing untimely investigations with poor practices. The firm’s quality system responded by reducing the retention timeframe for aseptic operation records — without a nonconformance, without a CAPA, without a risk assessment. Meanwhile, 337 of 963 nonconformances sat unresolved. The question every quality leader should ask: could our system make the same adaptation?
The Empower Pharma 483 is not primarily about nonconformance backlog, aseptic processing failures, or inadequate component testing — though all of those findings are serious, particularly for a facility manufacturing compounded sterile drug products. The 483 is fundamentally about a quality system that responded to its own failure by lowering the standard rather than meeting it.
Change control CHR-0000005416 is the most instructive finding in this case. The firm identified a genuine problem: quality personnel were performing untimely investigations with poor practices. In a functioning quality system, that finding triggers a nonconformance report against the quality function, a root cause investigation into why performance degraded (workload? training? resources? procedures?), and a CAPA to address the underlying cause. At Empower Pharma, the system skipped every one of those steps and went directly to a change — reducing the retention timeframe for aseptic operation records. The quality system did not address the dysfunction. It accommodated it.
The 337 unresolved nonconformances reinforce the pattern. A quality system that cannot resolve 35% of its own nonconformance reports is a system that has lost capacity to manage its quality event volume. Combined with the aseptic processing deficiencies — cleaning procedures not followed between formulations, process simulations that do not reflect routine production, and component testing gaps — the 483 describes a facility where the quality system was not controlling the manufacturing process. It was documenting the distance between what the procedures required and what actually happened.
For quality leaders at pharmaceutical manufacturing facilities, the Empower Pharma finding is a specific audit prompt. Can your change control system advance a quality-impacting change without a linked nonconformance, a risk assessment, and documented supporting data? Does your quality system track NC aging and escalate unresolved events automatically? When quality personnel performance degrades, does your system capture that as a quality event — or does it treat it as an operational issue handled outside the quality framework? If your system can accommodate the Empower Pharma sequence — identify poor practices, skip the NC, skip the CAPA, skip the risk assessment, and go directly to a change — then the architectural vulnerability exists. Addressing it before the inspection is the difference between a quality system that enforces its standards and one that adapts to their violation.