The Calcott Consulting Blog:

   Articles on regulatory citations:


Compounding Centers get new and more regulations

October 25th, 2016 by

I just had an article describing the Compounding industry and what the FDA is doing about it. Here is the link.

Good CAPAs require good investigations – driving out human error from the work place

September 4th, 2015 by

Do you have deviations that just won’t go away?  Do they disappear for a couple of months only to reappear a few months later stronger than ever?  Have you ever wondered why?

I won’t try to say that there is one cause for this but one that I have found continuously is Human Error as a major cause of the problem.  The obvious CAPA for this observation is to retrain the operator and rewrite the SOP.  I have seen it often in companies.

When I go in to audit the QMS, this is one area I look for first.  I look at the CAPAs and tally up the retrain operator and the rewrite SOP ones and if I find it happens more than 10% of the time, I know where to focus.  Investigations are not thorough or in depth.

On a recent visit to a client, they had just exited from a grueling inspection by an agency with a total of 53 observations.  They had developed their responses which are really CAPAs in any other language.  There were a total of 135 CAPAs and 55% were “retrain operator” or “rewrite SOP”.  I asked the person in charge of getting the responses back and asked whether he thought it would correct the problem.  His reply was an honest “No, many of these problems we’ve seen before and tried that and it never works”.  So, I ask him why are you doing it again, remembering Einstein’s quote “insanity is doing the same thing again and expecting a different result”.  At least I think it’s Einstein.

I then asked, “Why did you do this when you know it will not work?”  The answer was a chilling “because the regulators will accept it and it will allow me to get back to making product!”  I wanted to say “Yes, in the same broken way as before”.

After talking with other people at the plant it became clear that their investigation skills and tools were deficient.  They could get to the human error point.  They recognized that somebody had made an error but they lacked the tools to investigate further as to why it occurred.  Was it a system that was defective, were the operators overloaded with work, were the work stations organized appropriately?

Very rarely is Human Error the root cause but rather Human Error is the symptom of things not functioning properly. It is often the result of a deficiency elsewhere.  No other industry accepts human error just our pharmaceutical one.

There are four main ways that that things fail and manifest as human errors. There has been plenty of research in this area but not in pharmaceuticals.

  1. Culture – the culture allowing or encouraging people to not follow procedures. Initially it may be innocent. “I know the procedure is wrong, but we cannot change it”. “I know it says that, but this short cut will get you there quicker and we have a goal to get on the shift” – implying doing it by the rules won’t let you get there on time. This often occurs in cultures that are volume driven. “Get the product out the door at all costs”. One company even had a goal of “Speed over perfection”. That was a difficult one to puzzle out.
  2. Systems – the systems in place just don’t work. The poor operator just can’t get it to work based on the equipment, layout, QMS in place. This can be a change control process that is no longer serving the plant, a deviation process that everybody avoids, a CAPA process that is viewed as a encumbrance. The systems are viewed as punishment. Gone has the goal that the systems are tools to help you stay on top of your processes. The goal of everybody is to move the paper to the next person as quickly as possible. These systems are often put in place at the Corporate level or by management without asking the practitioners how it should be done. The same occurs in lay out of equipment and processes. They are not designed with the user in mind but often by a corporate engineer in central headquarters. Often operators have to take readings, remember them and go to the other end of the room or even next door to log the data into the permanent record.  This also breeds scrap paper use for data transcription.
  3. Procedures – this is where the procedures, batch records are wrong. It is often because they were not written by users but rather other bodies.                                                                                                            In one case I came across batch records being filled out and there appeared to be lots of   extraneous comments.     I asked about them and queried why.  “The batch records are wrong” was the response.  “Why don’t you change them?” I questioned.  “We can’t. We are not allowed to “ was the answer.  “Why can’t you?”, I asked. “Because Process Science owns them. They write them for us”  “If they write them, do they have the same equipment as you operating at a similar scale”.  “No”.     No wonder they are wrong. Nobody consulted the actual people operating the equipment.
  4. People – which brings us to the people. They make mistakes for many reasons. The reasons are many and varied. It could be that the training was inadequate. Yes they know what to do but not why. They do not understand the criticality of the key steps. They don’t know why it must be done this way. They are rushed and in the rush they revert to the old way.

As you read through the examples above, you will see a lot of similarity and overlap and that is because, it is rarely only one of the above that fails.  It actually starts at the management level with culture.  They set the tone that creates the systems, procedures and people to fail.

So how can you detect that you have a culture problem?  A systems problem?  Poor procedures? Or people prone to human errors?

You know you have problem or potentially one if you can say yes to any of the following:

Culture Problems include

  • Silos with poor communication between
  • Box checking mentality
  • Firefighting all day and everyday
  • Deadlines that are never met
  • Deviations are considered bad and people are punished
  • A blame culture that never learns from mistakes
  • People unwilling to raise the alarm for fear of punishment
  • Heavy reliance on final check – QA will catch it
  • Metrics that drive the wrong behaviour

System problems are evident by these

  • Congestion on the plant floor
  • Poor work flows
  • Physical conditions not adequate – lighting, temperature, humidity
  • Unreliable equipment that breaks down
  • Poor ergonomics of operators
  • Electronic systems that are no longer tools serving the worker
  • People avoiding using e-systems
  • Don’t know the cost of non-conformance
  • User not involved in design

Procedure problems are exemplified by

  • Long complex SOPs – they read like War and Peace
  • Too many double or even triple checks
  • SOPs written to satisfy auditors or regulators not for operators
  • CAPAs never working
  • All investigations / CAPAs must be complete in 30 days
  • Everything given equal importance

Which brings us to People

  • No time for breaks
  • Workers operating on permanent overtime
  • Multitasking that does not work
  • Reliance on memory because documents and records aren’t where the work is
  • Training explains the how but not the why. No understanding of the consequences of the procedure
  • Too many distractions
  • Training in a class room versus where the job is done

Of course this is not a comprehensive list but you get the picture!!

To get rid of all these types of problem requires both management and workers to take responsibility.  We must move to a culture exemplified by

  1. Create a positive attitude to human error. People make mistakes because the systems supporting them fail them. The error is pointing out an opportunity for improvement.
  2. Create a blame free culture. We must have a freedom to speak out where we see an issue and focus on the event and not who did it. Ask the question “what went wrong?” rather than “what did you do wrong?”
  3. Drive out complexity. Complexity is the enemy, it makes SOPs unworkable and an unworkable SOP translates to error. Reward simple procedures.
  4. Use user centered design. Get the workers involved in writing SOP, Batch Records, designing equipment and process layout. You will create ownership and it will be right.
  5. Introduce safeguards into processes, equipment. The operator knows what can go wrong, what they do under stress. Ask for their advice.
  6. Have a rapid reporting system. A system that responds in hours, not days, week or never.
  7. Seek out and remove risk. The workforce is your best friend to identify what or could go wrong. They see it every day.
  8. Create education and not training programs. Education explains how and what but also why it is done this way. It includes what can go wrong if steps are done wrong. Tells you what the critical steps are and why the new is better than the old.
  9. Management must assign roles and responsibilities and hold people accountable. Ownership and pride in the job well done ensues.

The road is a long one fraught with challenges but as my father used to wisely tell me “Knowing you have a problem is 50% of the way to solving it”.  How true!!!!

How to handle metrics that drive the wrong behavior

March 17th, 2015 by

Over my career I have lived and, unfortunately, died by Metrics.  What do I mean by that?  Metrics if developed carefully, and with thought, can help us attain our goals.  However, badly thought out metrics don’t just not help us from attaining our goals, they can actually prevent us from attaining them.  Because they can be counter productive.

Is this new?  No, I have seen it for decades both working in the industry but also as a consultant to the industry.  I find it’s amazing that these bad metrics are not isolated to companies with poor compliance records, but also to the companies who are leaders in doing things right.  Of course, with confidentiality, I can not name names, but I can talk about them and give advise in the public domain.

What are these bad metrics.  They are metrics that have been set up in order to measure and control certain outputs.  However, when set up, they encourage the wrong behavior.  How is that possible?    I will give you two examples.  Now, let me explain.

  1. First example

I was visiting a company recently for a training session on quality systems.  During the break, one of the attendees took me aside and described a situation at his company.  He asked the situation to be kept private.  And by that he meant that not only should I not describe it in  public describing his company but he did not want management at his company to hear about it ascribed to him.  Of course, I honored his request so you will learn neither who the person is or the company.

As with most companies, they wrestle with investigations taking long times to close out which leaves the company vulnerable both operationally and from a compliance perspective.  So to combat that and to drive closure, the company instituted a metric of “All investigations to be closed in 30 days”.  Depending on the number open during the year, the persons performance rating would be impacted.  Performance impacted equals decreased pay raise, bonus etc.  You get the picture.

Result, the number of investigations lingering past 30 days goes down.  Management is content and everything is improved.  Or is it?

The answer is no!!!!!  Yes, investigations are closed out quickly, but are they really completed and accurately describe what the root cause or contributing factors are?  In the haste to get a good grade, people are closing out investigations prematurely with poor root cause analysis.  Without this “good” investigation, the CAPAs developed are not directed to the right things.  So the CAPAs do not solve the problem and the result is that the problem reappears – in other word, we get repeat observations.

A better metric would be a goal of no repeat deviations or discrepancies.  That would indicate the CAPA worked because the investigation was thorough.  With decreased repeats, the work load would decrease giving better opportunity for effort on the unique observations.

2.  Second example

I was visiting a client one day to examine their quality systems, especially deviations and their handling.  I had flown for several hours to visit the company and was met by the plant manager who indicated that the issue that I was there for had been solved and they did not need my services for that.  Since I was already there, and he was paying anyway, I suggested I look at the remediation and maybe other systems in need of help. So off we went.

Apparently, over the last few weeks the PM had had a great idea.  He linked pay for performance to the number of deviations in  the department.  And immediately (for the last two weeks at least), there had been a 20% reduction in deviations.  The first thing I did was to go to the lot disposition department to see how things were and talked to the staff there.  They immediately reported that over the last week or so there had been an increase in the number of batch records arriving with serious errors and deviations that had not been highlighted. Previously, the Production department were encouraged to self report deviations and highlight them to QA. Now it was up to QA to try and find the errors.  Clearly a step backwards.  So the metric of reducing deviations had not decreased the number but rather the reporting of the deviations.  The deviations were still there but not reported.  We all want less deviations but this is not how to get it.

In both these incidents, the metric had driven the wrong behavior.  So how do you set up metrics that work.  I recommend this simple process.

  1. First identify the system that you want to work on. In these cases, the investigation system.
  2. Define the out come you want.
    1. In the first, closure of investigations.  While timeliness is important, surely, getting it right so we have a good chance of an effective CAPA to prevent recurrence is the real goal.
    2. In the second case, of course, you want to get no deviations, but if they have occurred, you want them reported, so they can be investigated properly so we can get effective CAPAs so they don’t appear again.
  3. Based on the input of point 2, set up metrics to drive the right behavior.
    1. For example one, you can have a metric of no repeat observations.  That indicates that the investigation was thorough and the CAPA directed to the right thing.  Hence, it solves the problem.
    2. For example 2, we want batch records to arrive in QA – right first time (RFT).  That is completed, checked and all deviations highlighted and put into the system for resolution.

Both these sets of metrics looks in to the future versus simply the immediate.

Are these the only examples or areas.  Of course not, but if you follow these principles, you will get improved operations.  Before any metric is established, ask the questions”will this metric drive the behavior and result I really want?”  And be careful what you ask for.  It might not be what you really want.

You thought the Indian companies were taking a hammering. Better look to the US Pharmacies

April 26th, 2014 by

In the first quarter of 2014, 3 Indian companies were issued warning letter (see my posting on the blog) whereas 7 pharmacies were hit.  Statistically significant?  Perhaps.

After the debacle of the New England Compounding Center about a year ago, the FDA has been on a rampage in the Pharmacy world.  I am no lawyer but the way I read it is the pharmacies are using a loophole in the law centered around the  issues of FDA jurisdiction.  FDA basically regulates interstate distribution of drugs, so make a drug in state X and “export” it to state Y – yep FDA has jurisdiction. So the manufacturers of drugs are under FDA rule.

Now, pharmacies are allowed to take these drugs and dispense prescriptions.  So when you go to your corner pharmacist, you can see them dispensing.  Counting out pills and putting them into bottles.  Hardly much risk here so long as they don’t muddle them up, get them cross contaminated  etc.  But they can also do further dispensing.  For instance, they can take a sterile vial or bottle of a drug and dispense it to another sterile container.  Now this is another matter.  What we are describing is aseptic processing.  As we all know that’s a risky business.  How many manufacturers fall foul of the regulations in industry?  The number of warning letters are numerous.

But it seems that FDA can not step in unless there is a demonstrated safety calamity.  But we don’t want to wait for that each and every time.  So what can the FDA do?  Their tack is to inspect these operations when they suspect that the Pharmacy has overstepped their authority.  It seems that in a majority of the 7 letter this quarter they have seen that the pharmacies have been dispensing these aseptically prepared drugs without prescriptions and compounding several drugs together.  Some of these drugs have different regimes of taking the drug.  Ergo, they are no longer dispensing, but manufacturing.

Now when they go in and inspect they cite for lack of GMP adherences and the story goes on.  Call me naive, but if I go to a pharmacy, I want an assurance that the drugs I am receiving are not adulterated.  I don’t care who regulates them but I want it done properly.  Clearly the Boards of Pharmacy have not been doing a good job (they are the ones who regulate at a state level rather than FDA).  What we have here is a standard clash between Federal and state control – we see it every day in other matters but in this case they are using our health as a pawn in the game.

 

Keep up the good work FDA.

He is the link to the 7 warning letters

Nora Apothecary Services ,  Lowlite Investments DBA Olympia PharmacyPallimed SolutionsWedgewood Village PharmacyTotal Pharmacy Services ,Avella of Deer ValleyVillage Fertility Pharmacy

 

Not just telling you your faults but how to rectify

March 30th, 2014 by

When I read FDA Warning Letters and I do often, most take the format of telling you the observations and then indicating that this is not a complete list. However, about 10% go one step further and basically read you the riot act suggesting that you need to hire a consultant to “educate you” on the errors of your ways. These are quite common.
But I believe they went to the next level for USV Limited of Mumbai. In the 2/6/2014 WL, they even listed out 7 steps for remediation. View this as reading the riot act 7 times over. Basically there was suspicion of fraud in the data.

The link is Warning Letter

They went on as follows
Get a consultant specialising in data fraud to do the following
1.) Identify the time period when the issue occurred
2.) Identify and interview employees involved in that period
3.) Identify and interview employees who have left who were employed during the period
4.) Gather data to support what comes out of the interview
5.) Trace issues to specific managers including senior management
6.) Determine if any other offending managers are in a position to influence data integrity decisions and expand your oversight
7.) Put into place procedures to prevent recurrence and assure there are no discrepancies between what was filed and reality. Create CAPAs to remedy issues. This does not apply simply to what we found but everything in essence.
Nothing revolutionary just common sense.