Thursday, September 22, 2011

A much improved Ph. Eur. Chapter 5.3.2


Vaccine manufacturers intending to market in the EU should be aware of a recent change in the European Pharmacopoeia (Ph. Eur.) chapter 5.2.3 Cell substrates for production of vaccines for human use. This chapter addresses the characterization of vaccine cell substrates. The section on Test Methods for Cell Cultures within the chapter includes an instruction to perform a co-cultivation study. The language previously was as follows: “Co-cultivation. Co-cultivate intact and disrupted cells separately with other cell systems including human cells and simian cells. Carry out examinations to detect possible morphological changes. Carry out tests on the cell culture fluids to detect haemagglutinating viruses. The cells comply with the test if no evidence of any extraneous agent is found.”

This section has been changed, as of Ph. Eur. version 7.2 effective in January of 2011, to the following: “Co-cultivation. For mammalian and avian cell lines, co-cultivate intact and/or disrupted cells separately with other cell systems including human cells and simian cells. For insect cell lines, extracts of disrupted cells are incubated with other cell systems, including human, simian, and at least 1 cell line that is different from that used in production, is permissible to insect viruses and allows detection of human arboviruses (for example BHK-21). Carry out examinations to detect possible morphological changes. Carry out tests on the cell culture fluids to detect haemagglutinating viruses, or on cells to detect haemadsorbing viruses. The test for haemagglutinating viruses does not apply for arboviruses to be detected in insect cells. The cells comply with the test if no evidence of any extraneous agent is found.”

So what is the big deal? Co-cultivation is a commonly employed technique for detecting infectious retrovirus in a cell bank. It is effective for this purpose because the chances for spread of infectious virus from test cell to indicator (host) cell are optimized by the cultivation of live cells of each kind in close proximity. The endpoint of the retrovirus assay, be it reverse transcriptase enzyme induction or rescue of an S+L- virus, is not interfered with by the presence of two cell types in one culture. The same is not always true for a co-cultivation of a test cell with an indicator (host) cell for detection of infectious virus when morphological changes (viral cytopathic effects) are one of the assay endpoints. The reason is that the diploid human cells (e.g., MRC-5 or WI-38) used as one of the indicator cells in such assays are rapidly displaced during co-cultivation with intact continuous cell lines used to produce vaccines, such as the simian cell Vero. The result of this is that within a short period of time in co-cultivation, the test culture is no longer predominated by the diploid cell but rather by the test cells and observation of the culture for cytopathic effects becomes problematic. Changing the language of this section to read “…co-cultivate intact and/or disrupted cells separately with other cell systems…” allows the user to eliminate the inoculation of intact test cells onto a diploid indicator cell.

The other useful modification to the language of this section is the following addition: “For insect cell lines, extracts of disrupted cells are incubated with other cell systems, including human, simian, and at least 1 cell line that is different from that used in production, is permissible to insect viruses and allows detection of human arboviruses (for example BHK-21).” Testing of insect cells for extraneous virus is only marginally effective when it is conducted per the usual method of inoculating another insect cell. Why? The insect cells that are available are most commonly suspension cultures, making observation for cytopathic effect problematic. The extraneous viruses that are of most concern for an insect production cell are the arboviruses (viruses transmitted via insect vectors). It has been known for some time that the Syrian hamster cell line BHK-1 is an excellent host cell for detecting arboviruses. The new language in this section of Ph. Eur. chapter 5.2.3 now clears the way for the use of the monolayer BHK-1 cell line to be used for the testing of insect cells for extraneous virus. In this regard the Ph. Eur. chapter is now more closely aligned with the World Health Organization’s 2009 Evaluation of cell substrates for the production of biologicals: revision of WHO recommendations. The latter has the following passage: "For instance, in the case of insect cell substrates, certain insect cell lines may be used for detection of insect viruses, and BHK cells may serve for the detection of arboviruses."
   
Taken together, the recent changes to Ph. Eur. Chapter 5.2.3 greatly improve the chapter and the viral safety testing of vaccine production cell banks specifically proscribed within it.

Monday, September 12, 2011

Ridding serum of viruses with gamma irradiation: part 1

by Dr. Ray Nims

Blood serum, while at times required as a medium component for cell growth in vitro, is an animal-derived material that can introduce contaminating viruses such as Cache Valley virus, REO virus, vesivirus, and epizootic hemorrhagic disease virusinto a biological product. If animal serum must be used in upstream manufacturing processes, the risk of introducing a virus may be mitigated by gamma irradiation of the frozen serum prior to use. How effective is this treatment, and against which viruses?

To answer this question, I have surveyed the literature from the past two decades. A number of investigations have been conducted and the results are in the public domain. The most useful of these studies have examined the dose-response relationships for viral inactivation (rendering of the virus as non-infectious) by gamma irradiation.

In the table below, I have assembled the results obtained for 7 viruses, including four that might be expected to be found in bovine serum: (bovine viral diarrhea virus [BVDV], infectious bovine rhinotracheitis virus [IBR], respiratory-enteric orphan virus [REO virus], and parainfluenza type 3 virus [PI3]). The other three (canine adenovirus, porcine parvovirus [PPV], and mouse minute virus [MMV]), while perhaps not expected to be found in bovine serum, have been studied as model viruses for the adenovirus and parvovirus families (click on table to enlarge).

The efficacy of gamma irradiation for viral inactivation is reported as log10 reduction in titer per kGy, rather than the more commonly employed D10 (Mrad dose required to reduce the titer by 1 log10), as I find the former value to be more useful. To estimate the effectiveness of a given dose of gamma radiation for inactivation of a virus, just multiply the dose in kGy by the log10 reduction in titer per kGy value from the table. The result is the number of logs of inactivation estimated to be achieved for that virus at that radiation dose.

These data tell us that the mid- to large-sized viruses BVDV, IBR, PI3, REO, and CAV should be readily inactivated at the gamma radiation doses normally applied to frozen serum for risk mitigation (25-45 kGy). On the other hand, the two parvoviruses, PPV and MMV, are more difficult to inactivate, presumably due to their small size. Parvoviruses are often used to challenge viral removal and inactivation processes due to their size and lack of an envelope. Higher kGy dose levels may increase the effectiveness of inactivation for these viruses, although at such levels the performance of the animal serum being irradiated may be adversely impacted.

Gamma-irradiation can effectively mitigate the risk of introducing other potential contaminants of bovine serum, including Cache Valley virus, blue tongue virus, and epizootic hemorrhagic disease virus. Like the parvoviruses, however, other relatively small non-enveloped viruses of the calicivirus, picornavirus, polyomavirus, and circovirus families may represent cases where gamma irradiation is less effective at the doses normally applied. Other means of mitigating the risk associated with these viruses may need to be considered.

< This information was excerpted in part from Nims, et al. Biologicals (2011) >


Information sources: Daley et al., FOCUS 20(3):86-88, 1998; Wyatt et al. BioPharm 1993: 6(4):34-40; Purtel et al., 2006; Hanson and Foster, Art to Science 16:1-7, 1997; Hyclone Labs Art to Science 12(2): 1-6, 1993; Gauvin and Nims 2010; Plavsic et al. BioPharm 2001: 14(4):32-36.

Friday, August 26, 2011

Our take on process-specific vs. generic host cell protein assays

By Drs. Ray Nims and Lori Nixon 

The residual host cell protein (HCP assay) is used to determine the concentration, in process streams, of protein originating from the production cell (Chinese hamster, NS0, E. coli, etc.) used in the manufacture of a biologic. Host cell protein is considered to be a process-related impurity/contaminant. The most typical approach to quantitation of residual host cell protein in a test sample is the enzyme-linked immunosorbant assay (ELISA) platform.

Generic vs. process-specific assays.  A question that often arises is whether a process-specific HCP assay is required, or whether a generic assay can be used. Although there is a spectrum of “process specificity” that can be described, in this discussion, we are considering a generic assay to be one that is developed from a broad set of antigens from the host strain or closely-related strains, but not necessarily under specific process conditions mimicking the actual production/purification process of the protein of interest. That is, the reagents for a generic assay could be developed in advance of a defined production process. For example, it is often possible to purchase a “generic” HCP ELISA kit from a commercial provider, such as Cygnus Technologies, selecting a kit that matches the production cell line. Practically speaking, most firms start with generic HCP methods in early development for an obvious reason: you can’t have a process-specific assay until you have a defined process. Even after the process is defined, the lead time for developing custom (process-specific) HCP reagents and an assay using these can be as long as 1-2 years.
It should be appreciated from the outset that there is no perfect HCP assay. Production cells can express thousands of proteins, with expression patterns differing under different growth conditions. At each successive stage of the recovery and purification process, the population of HCPs is altered. At the final drug substance stage, there may be only a few HCPs present that have co-purified with the product. If you attempt to design an assay that only selects those few remaining HCPs, then some will argue that you might miss HCPs that might make it through under other circumstances (such as a process deviation).  If you attempt to design antibody reagents using the entire unpurified mixture of proteins from the production cell, the proteins of most interest may not elicit a good antibody response and you may have inadequate sensitivity to quantify HCP in your final drug substance. In fact, it has been reported that process-specific antibodies lead to HCP assays that are more sensitive for certain HCP species (and sometimes more broadly reactive) than the antibodies provided in a generic HCP assay. 
In recent years, there has been some regulatory pressure setting an expectation that a process-specific HCP assay must be developed for product registration. In our opinion, this is unjustified as a blanket prescription.  There are a multitude of approaches for creating antigen and antibody reagents, but the resulting assay should be judged primarily on its own merits.
Suitability of any HCP assay (whether generic or process-specific) must be evaluated on a case-by-case basis, and the assay validated for the specific product in question. One of the first characteristics to aim for is an assay that is able to readily quantitate HCP in the final drug substance. Without this sensitivity, it is difficult to get results that are meaningful to guide process optimization or ensure control of your product. If the available generic method(s) have limited sensitivity for the sample of interest (results are below the required range of quantitation), then it is a good idea to start planning the development of more process-specific reagents—which are likely to afford better sensitivity. Since the numerical values reported from these assays are semi-quantitative at best, sensitivity should be judged on the performance in actual samples rather than on the product specification. Of course there are other assay characteristics (non-reactivity to product, precision, dilutional linearity, spike recovery, etc) that are required to meet validation acceptance criteria. The antigen coverage should be determined, typically by 2D electrophoresis or 2D HPLC-ELISA. It is unrealistic to expect 100% coverage of all of the proteins present in the production cell; on the other hand, it is relatively more important to ensure response against bands that persist in the purification process.  All other things being equal, of course greater coverage is more desirable.
Example of 2D electrophoresis of E. coli proteins, from Kendrick Labs

Whether a generic or process-specific method is implemented, it is vital to ensure a consistent reagent supply that will last throughout the commercial life of the product. If using vendor-supplied antigen and antibody, be aware that by nature these are “single-source” reagents with associated supply risks. If creating a custom reagent set, make enough supplies to last for years to decades.
As mentioned above, most firms start with a generic assay and may move to a process-specific assay in later stages of development. A close evaluation of the generic assay during its characterization and validation may lead to the conclusion that the generic assay is suitable for your product.  In this case, be prepared to make a strong case in defense of your generic assay—based on empirical data with your product, rather than theoretical speculation.

Monday, July 25, 2011

Rapid Identification of Viral Contaminants, Finally

By Ray Nims, Ph.D.


There was a time, not long ago, when it might take months to years to identify a viral contaminant isolated from a biological production process or from an animal or patient tissue sample. The identification process took this long because it involved what I have referred to as the “shotgun approach”, or it involved luck.

Let’s start with luck. That is probably the wrong term. What I mean by this is that there have been instances where an informed guess has led to a fairly rapid (i.e., weeks to months) identification of a contaminant. For instance, our group at BioReliance was able to rapidly identify contamination with REO virus (REO type 2 actually) and Cache Valley virus  because we had observed these viruses in culture previously and because these viruses had unique properties (a unique cytopathic effect in the case of REO and a unique growth pattern in the case of Cache Valley virus). The time required to identify these viruses consisted of the time required to submit and obtain results from confirmatory PCR testing for the specific agents.

The first time we ran into Cache Valley virus, however, it was a different story. This was, it turns out, the first time that this particular virus had been detected in a biopharmaceutical bulk harvest sample. In this case, we participated in the “shotgun approach” that was applied to the identification of the isolate. The “shotgun approach” consisted of utilizing any detection technique available at the lab, namely, in vitro screening, bovine screening, application of any immunofluorescent stains available, and transmission electron microscopy (TEM). The TEM was helpful, as it indicated a 80-100 nm virus with 7-9 nm spikes. A bunyavirus-specific stain showed positive, and eventually (after months of work), sequencing and BLAST alignment was used to confirm the identity of the virus as Cache Valley virus.

The “shotgun approach” was subsequently applied to a virus isolated from harbor seal tissues, with no identity established as a result. After approximately a year of floundering using the old methods, the virus was eventually found to be a new picornavirus (Seal Picornavirus 1).  How was this accomplished? During the time between the identification of the Cache Valley virus and the seal virus, a new technology called deep sequencing became available. Eric Delwart’s group used the technique to rapidly identify the virus to the species level. As this was the first time this particular picornavirus had ever been detected, deep sequencing is likely the only method that would have been able to make the identification.

Deep (massively parallel) sequencing is one of a few new technologies that will make virus isolate identification routine and rapid in the future. It has been adopted for detection of viral contaminants in cells and viral seed stocks and for evaluating vaccine cell substrates by BioReliance.The other is referred to as the T5000 universal biosensor. Houman Dehghani’s group at Amgen has been characterizing this methodology as a rapid identification platform for adventitious agent contaminations.  Each technology has its advantages. Deep sequencing is more labor intensive, but has the ability to indicate (as described above) a new species. The universal biosensor can both serve as a detection method and as an identification method. Both can identify multiple contaminants within a sample.

Since identification of an adventitious viral contaminant of a biopharmaceutical manufacturing process is required for establishment of root cause, for evaluating effectiveness of facility cleaning procedures and viral purification procedures, and for assuring safety of both workers and patients, it is critical that the identification of a viral isolate is completed accurately and rapidly. Happily, we now have the tools at hand to accomplish this.

Saturday, July 9, 2011

Can You Decide on CAPA?

By Dr. Scott Rudge


When things go wrong in pharmaceutical manufacturing, consequences can be dire.  Small changes in the quality of the pharmaceutical product can cause major consequences for patients in ways too numerous to list in this blog.  It can be surmised that the failure mode was not anticipated, so the manufacturer is wise to determine the cause of the failure, correct it, and prevent it from happening again.  This exercise is known as CAPA, Corrective and Preventive Actions.
There are numerous tools for determining the root causes of failures, many of these are embedded fully in software, and ICH Q9, that helps a manufacturer’s quality organization to track the resolution of CAPAs.  Fault Tree Analysis and Root Cause Analysis are two common and popular examples of these tools.  These tools help to trace the cause of a failure back to the basic characteristics of the failure.  Once these basic characteristics have been identified, they can be remediated (eliminated).

When the root cause is found, it is eliminated, and the process goes on.  The CAPA is closed and everyone waits for the next crisis or problem that needs to be fixed.  Right?

But root cause elimination, although a worthy corrective objective, does not appear to be sufficient as a preventive action.  One should consider how the root cause is to be eliminated.  And one should consider whether the manner and means of root cause elimination might lead to other failure modes.

The first consideration, how to eliminate a root cause, is a decision.  Decision analysis can be used to improve the process of choosing between multiple remediation options.  When there are multiple good options for fixing a problem, or perhaps a series of “less bad” options, it’s a good idea to do some analysis. 

First, the decision should be defined.  The required objectives that the remediation option must meet should be listed.  These should be specific and measureable.  Each option for addressing the problem should also be listed, and the “features” of each option listed, so there is little uncertainty about the option and its implementation.  Each option must fully meet all the required objectives, any option that partially addresses must be considered incomplete.  Any option that is incomplete should either 1) not be considered further, or 2) have elements added that allow the option to completely satisfy the required objectives.  All options that meet each of the required objectives is a “qualified option”.

There are often additional objectives that are less absolute that should be considered in choosing a remediation option.  These might be considered as differentiating objectives.  For example, cost may be a required objective (the remediation must be implemented within the current budget) and a differentiating objective (the least costly option, within the budget, is preferred).  These differentiating objectives should also be listed, and weighted according to their relative importance.  The objectives of all stake holders must be considered.  The weightings may be controversial among stakeholders, but with practice, an organization can learn to appropriately weight objectives. 
Qualified options can be scored according to the weighted differentiating objectives.  Each qualified option is ranked according to how it fulfills these objectives, and the score is multiplied by the weight.  The weighted scores are summed, and a “most preferred” option is identified as a result. 

But wait, there’s more.  A final check of failure modes should be made.  The last thing we want is to implement a remediation option that introduces more vulnerabilities into our systems.  A simple FMEA can be used for this.  If your organization routinely uses FMEAs and has standard criteria for scoring them, then you probably only need to perform one FMEA, and ensure no resulting risk priority numbers exceed the established threshold value for risk.  If your organization doesn’t have this experience, then you may have to perform a comparative FMEA on two or more qualified options, to gauge relative risk.

If your decision making is already perfect, then there is no need for this analysis.  Such excellent seat of the pants decision making would be useful for the rest of us to see!  For the rest of us, when new issues arise, the decision analysis can be revisited, and organizational assumptions revised, to improve the decision making in the future.  And it might be useful to have documented the options you considered, and how you selected among them.