When regulatory authorities make observations, it signals an indication that the company's systems, processes and controls may not comply with regulatory standards. Observations do not imply necessarily that the company's products are flawed or that quality systems have failed in their entirety. Nonetheless, observations reflect concerns raised by the regulatory authorities that necessitate assessing the situation and taking actions wherever required.
The unique aspect of observations is that inspectors rarely stop at their conclusion. Therefore, a minor defect may lead to inspections of related systems, documentation, actions taken and the management of such activities. This is why companies need to know not only how to act in response to observations but also why the observations have been made.
Some typical categories include some operational areas, including:
- Manufacturing operations
- Quality control laboratories
- Data integrity
- Documentations
- Hygiene and sanitation process and procedures
- Validation of processes
- Qualification of equipment
- Professional training
- Computer systems
- Changes in control
- Changes and CAPA management
- Environmental monitoring
- Suppliers control and monitoring
The variation in terms and classification also depends on the agency you are dealing with. For instance, the FDA documents its observation in veterinary Form FDA 483.
Take, for instance, a situation where, for example, there is a continuous problem with documentation. If management continuously perceives it to be a fault of one operator, the company’s management will not be able to identify a problem with form design, lack of training or heavy workload as a possible reason.
In the course of an inspection, inspectors may see a pattern and widen their evaluation.
This is why a good investigation should ask:
Why was the problem possible in the first place?
rather than simply:
Who made the mistake?
The most important requirement is that data generated in the process of GMP should be accurate, complete, attributed to a source and protected.
Importance of documentation errors grows if it does not allow the entity to recreate events that actually happened.
The below are some examples:
An investigation that claims "the operator is at fault" without assessing the design of procedures, training, equipment, work environment, workload and many other factors is not considered effective in determining the real cause of the issue.
The same goes for CAPA that needs to address the root cause of issues and not just provide retraining.
For instance, compliance personnel may look for:
As an example, if there is only a single incident regarding documentation deficiencies, it might be of a limited significance. However, if there are various undocumented critical manufacturing processes, it can raise serious questions on the reliability of batch records and quality systems.
The response may have the following structure:
In the response, it is better not to use options like "the employees will be retrained" without having actual evidence that training will address the cause that was identified.
Imagine a case where an improper entry is made by an analyst in a laboratory record.
In this case, the immediate cause can be stated as analyst’s failure; however, the investigation should look at the factors contributing to the error.
Was there confusion about the form?
What is Regulatory Observation?
A regulatory observation is a concern recorded by an inspector during inspections when they conclude that a procedure, record, system, background or process does not satisfy the applicable regulatory requirements or GMP.Some typical categories include some operational areas, including:
- Manufacturing operations
- Quality control laboratories
- Data integrity
- Documentations
- Hygiene and sanitation process and procedures
- Validation of processes
- Qualification of equipment
- Professional training
- Computer systems
- Changes in control
- Changes and CAPA management
- Environmental monitoring
- Suppliers control and monitoring
The variation in terms and classification also depends on the agency you are dealing with. For instance, the FDA documents its observation in veterinary Form FDA 483.
Reason for Regulatory Observations
Numerous observations are not due to one single wrongdoing by the employee. There is a possibility that it is a result of some weaknesses in the quality system.Take, for instance, a situation where, for example, there is a continuous problem with documentation. If management continuously perceives it to be a fault of one operator, the company’s management will not be able to identify a problem with form design, lack of training or heavy workload as a possible reason.
In the course of an inspection, inspectors may see a pattern and widen their evaluation.
This is why a good investigation should ask:
Why was the problem possible in the first place?
rather than simply:
Who made the mistake?
Common Areas of Regulatory Observations
1. Data Integrity
Data integrity is one of the key focuses of regulatory bodies. Issues can relate to incomplete documentation, improper access, lack of audit trails, unauthorized modifications, use of common accounts and failure to keep original data.The most important requirement is that data generated in the process of GMP should be accurate, complete, attributed to a source and protected.
2. Documentation
In the course of an inspection, inspectors can find insufficient batch records, missing signatures, missing documents, wrong changes and mismatched data.Importance of documentation errors grows if it does not allow the entity to recreate events that actually happened.
3. Process Validation
Observations may take place when validation fails to demonstrate proper process control.The below are some examples:
- Insufficient understanding of the process
- Poor risk management
- Unjustifiable acceptance criteria
- Inadequate sampling
- Failure to evaluate unanticipated results
- Inadequate ongoing process verification
4. Deviations and CAPA
A common observation is ineffective analysis of deviations.An investigation that claims "the operator is at fault" without assessing the design of procedures, training, equipment, work environment, workload and many other factors is not considered effective in determining the real cause of the issue.
The same goes for CAPA that needs to address the root cause of issues and not just provide retraining.
Why Some Observations Become Serious
There are many aspects that lead to the seriousness of an observation.For instance, compliance personnel may look for:
- Potential impact on product
- Impact on patients
- Magnitude of the issue
- Repetition of the issue
- Reliability of the data
- Effectiveness of the measures already in place
- Management awareness
- Not solving previously identified problem
As an example, if there is only a single incident regarding documentation deficiencies, it might be of a limited significance. However, if there are various undocumented critical manufacturing processes, it can raise serious questions on the reliability of batch records and quality systems.
How to Respond to a Regulatory Observation
A good reaction should be based on evidence and should always be precise and informative. To start with, it is vital that the organization knows exactly what the inspector meant.The response may have the following structure:
1. Acknowledge the issue
In a clear and simple way, explain the non-compliance issue without writing anything that is not based on facts.2. Immediate correction
Describe what was performed to solve the immediate issue.3. Investigation
Use a proper methodology to find out the root cause (or the most probable cause) of the issue.4. Impact assessment
Evaluate how many batches, products, systems, records and data could potentially be affected by the issue.5. CAPA
State the corrective and preventive actions that need to be taken in order to address the cause.6. Effectiveness verification
Indicate how the organization is going to check whether the CAPA was successful.In the response, it is better not to use options like "the employees will be retrained" without having actual evidence that training will address the cause that was identified.
Root Cause Matters More Than the Symptom
One of the major shortcomings of regulatory actions is their failure to go beyond the immediate cause that prompted the incident.Imagine a case where an improper entry is made by an analyst in a laboratory record.
In this case, the immediate cause can be stated as analyst’s failure; however, the investigation should look at the factors contributing to the error.
Was there confusion about the form?
Was the procedure unclear?
Was the analyst trained sufficiently?
Was there no proper verification done?
Did any problem arise in the computer system?
Did the analyst have too much work?
If the real cause of the failure is that the process was badly designed, retraining the analyst will help only temporarily.
Some examples include:
An updated standard operating procedure does not mean that employees adhere to it. Training documentation does not mean that people are competent. Completed Corrective Actions do not mean that the action was effective.
The organization is responsible for justifying the relationship between the action and the identified risk.
Some of the helpful practices include:
Excellent quality systems require workers to speak up if there is a deviation, documentation mistake, equipment malfunction or any risk affecting quality.
Thus, we can draw a clear line when comparing having problems and having problems we cannot control.
Every production facility experiences deviations and unusual events. The quality system proves it is mature in terms of identification, investigation, correction and prevention of such events.
Observations conducted by regulatory bodies have significant implications for the weaknesses evident in the quality systems of pharmaceutical organizations. Receiving an observation is not a desirable occurrence; however, it may draw attention to problems that would have been unnoticed otherwise.
It is essential that the organization looks further than just the particular observation and makes a determination whether the problem is just isolated or has roots in systemic weakness. The corrective actions taken should address the root cause of the issue, check the potential product and patient consequences and conduct proper effectiveness checks.
Finally, it must be pointed out that the compliance with regulations should not entail preparation for inspections. The aim of the organization is a daily business that has processes under control, reliable information and an informed employee who can understand his or her role in preventing quality problems from happening before the inspection.
If the real cause of the failure is that the process was badly designed, retraining the analyst will help only temporarily.
Evidence Makes a Response Reliable
A regulatory response is believed to be superior when backed up by substantial evidence.Some examples include:
- Updated Standard Operating Procedures
- Training documentation
- Validation documents
- Risk evaluation
- Trend analysis
- Corrective Actions documentation
- Results of the Audit
- Digital documentation when needed.
- Updated process
- Results of the effectiveness review
An updated standard operating procedure does not mean that employees adhere to it. Training documentation does not mean that people are competent. Completed Corrective Actions do not mean that the action was effective.
The organization is responsible for justifying the relationship between the action and the identified risk.
Avoiding Regulatory Observations
Inspection preparedness must be integrated into every day processes and not something done only before an inspection.Some of the helpful practices include:
- Performing honest internal audits
- Tracking consistent deviations
- Evaluating the effectiveness of CAPAs
- Watching for risks of data integrity
- Conducting periodic quality reviews
- Keeping validations up to date
- Making sure training is performed well
- Assessing documentary practices
- Looking into systematic issues
- Issuing formal reports on serious incidents that affect quality
A Mature Approach to Regulatory Compliance
A leading pharmaceutical company does not determine the maturity of its quality culture by the number of observations it has. Instead, it looks at whether issues are resolved or identified and solved before they become regulatory findings.Excellent quality systems require workers to speak up if there is a deviation, documentation mistake, equipment malfunction or any risk affecting quality.
Thus, we can draw a clear line when comparing having problems and having problems we cannot control.
Every production facility experiences deviations and unusual events. The quality system proves it is mature in terms of identification, investigation, correction and prevention of such events.
Observations conducted by regulatory bodies have significant implications for the weaknesses evident in the quality systems of pharmaceutical organizations. Receiving an observation is not a desirable occurrence; however, it may draw attention to problems that would have been unnoticed otherwise.
It is essential that the organization looks further than just the particular observation and makes a determination whether the problem is just isolated or has roots in systemic weakness. The corrective actions taken should address the root cause of the issue, check the potential product and patient consequences and conduct proper effectiveness checks.
Finally, it must be pointed out that the compliance with regulations should not entail preparation for inspections. The aim of the organization is a daily business that has processes under control, reliable information and an informed employee who can understand his or her role in preventing quality problems from happening before the inspection.
No comments:
Post a Comment
Please don't spam. Comments having links would not be published.