Clean or cultured meat are terms used for animal muscle produced by growing cells directly rather than via the rearing and slaughtering of an animal. The idea of growing meat (or muscle) from cells outside the body (in vitro) to produce a product that replicates the characteristics of a product obtained from muscle harvested from slaughtered animals has been contemplated for a long time. In recent years, tools have been developed that have made the commercial production of a muscle food product in vitro a real possibility. As startup companies in the United States and elsewhere have gotten closer to getting an actual product to the market, the regulation of this type of product has become a topic of discussion.

Many questions arise. Who will regulate this product, USDA, FDA, or both agencies? How should this type of product be named? If it is grown from muscle cells and looks and tastes like meat, should it be called meat? And if yes, how should it be distinguished from traditionally produced meat which is obtained from a carcass after an animal has been slaughtered?

Apparently concerned about the effect the marketing of this type of meat product may have on the “traditional” industry, the United States Cattlemen’s Association (USCA) filed a petition with the USDA Food Safety and Inspection Service (FSIS) asking that FSIS establish formal definitions of “meat” and “beef” that exclude what petitioners call lab grown meat and products prepared from plant or insect protein. USCA asks that FSIS require that any “product labeled as ‘beef’ come from cattle that have been born, raised, and harvested in the traditional manner,” rather than from “alternative” sources such as a synthetic product from plant, insects, or any product grown in laboratories from animal cells. USCA further asks that FSIS narrow the definition of “meat” to “the flesh of animals that have been harvested in the traditional way,” and that FSIS add these new definitions to the FSIS Food Standards and Labeling Policy Book.

In support of its petition, USCA discusses the definition of “meat” and “beef” in common dictionaries and by USDA, the Federal Trade Commission’s (FTC’s) truth in advertising standard, and the labeling of “alternative products” as beef and meat in the market place. Somewhat surprisingly, USCA also cites FDA’s actions regarding Just Mayo in support of its petition; although FDA initially objected to that name for a product that failed to meet the standard of identity for mayonnaise by virtue of not containing egg, the Agency ultimately allowed the marketing of the product with that name provided that the product was clearly identified as egg-free.

This Petition formalizes regulatory consideration of an issue that until now was being considered informally, and bears watching on that basis alone. The Petition is limited to beef. Since development of clean pork and poultry is proceeding apace, it will be interesting to see if traditional producers of those animal products will follow USCA’s lead. We will be keeping an eye on this issue as it unfolds.

A hat tip to K&H’s The Daily INTAKE for putting this petition on our radar.

Barely a week apart, FDA announced the publication of a slew of guidance documents intended to further implement the food supply chain-related provisions of the Food Safety Modernization Act (FSMA).  In this posting, we look at the first set of documents, published on January 24.  In an upcoming posting, we’ll look at the second set of documents, published on January 31.

The first set of guidance documents – some draft, some not – brings home the extent to which the Agency is leveraging importers and producers to help ensure the safety of food, regardless of its origin.  The documents also show the difficulty of trying to weave together the FSMA regulations in a way that is comprehensible and doesn’t result in undue burdens or complexity.  Any party involved in the importation and production of food should closely read these documents, which are briefly summarized below.

• Foreign Supplier Verification Programs for Importers of Food for Humans and Animals: Guidance for Industry (Draft Guidance) – This 108(!) page draft guidance includes Q&As on a range of topics, including:
  • Applicability of the regulation under given circumstances (e.g., importation of food contact substances; return of  U.S. goods by a foreign purchaser; importation of live animals)
  • Requirements of an FSVP (e.g., single vs. multiple FSVPs depending on types of food imported and the number of suppliers; whether a supplier’s process or procedure provides at least the “same level of public health protection” – a potentially complex analysis that is the subject of its own guidance (see further below); FSVP obligations that apply to receiving facilities under the preventive controls regulation)
  • Qualifications of individuals who develop an FSVP and perform FSVP activities, as well as auditors
  • Conduct of a hazard analysis (e.g., identification of known or reasonably foreseeable hazards; obligation to address hazards that are intentionally introduced; records that must be maintained)
  • Conduct of an evaluation for foreign supplier approval and verification (e.g., scenarios where a foreign supplier relies on its supplier to control a hazard; evaluation of a supplier’s compliance with FDA food safety regulations; circumstances under which the risk posed by a food and a foreign supplier’s performance must be reevaluated)
  • Conduct of foreign supplier verification activities (e.g., how to satisfy this obligation when purchasing food from a broker or distributor; factors to consider in selecting appropriate verification activities; conduct of onsite audits; verification activities for hazards related to transportation; mitigation of conflicts of interest)
  • Importation of foods that can’t be consumed without a hazard control, or where a hazard is controlled subsequent to importation, including provision of disclosure statements
  • Corrective actions, including examples of such actions and assessment of actions taken by a supplier
  • Identification of the FSVP importer at entry
  • Maintenance of FSVP records (e.g., retention, storage, and availability to FDA; translation of records in a foreign language)
  • FSVP requirements applicable to importation of dietary supplements (e.g., rationale for modified requirements and criteria for eligibility; obligations with respect to importation of finished dietary supplements)
  • Requirements applicable to very small importers and to importation of certain foods from countries with an officially recognized or equivalent food safety system
  • Consequences of failure to comply (e.g., issuance of 483s and warning letters; refusal of admission; import alert; civil and criminal actions; and debarment)
• Guidance for Industry: Foreign Supplier Verification Programs for Importers of Food for Humans and Animals: What You Need to Know About the FDA Regulation; Small Entity Compliance Guide – This much shorter guidance focuses on modified procedures for importers that qualify as a “very small importer” as that term is defined in the FSVP regulation, as well as importers of food from certain small foreign suppliers (e.g., qualified facilities and farms that grow produce but are not “covered farms” as that term is defined in the produce safety regulation).  The guidance also addresses modified requirements applicable to importers of dietary supplements and components, and of food from countries with officially recognized or equivalent food safety systems.
• Considerations for Determining Whether a Measure Provides the Same Level of Public Health Protection as the Corresponding Requirement in 21 CFR part 112 or the Preventive Controls Requirements in part 117 or 507: Guidance for Industry (Draft Guidance) – In FDA’s words, “[t]his guidance describes FDA’s current thinking on considerations for determining whether a measure or procedure used in lieu of an FDA requirement in 21 CFR part 112, 117, or 507 provides the same level of public health protection (SLPHP) as the corresponding FDA requirement.”  Ugly as the acronym SLPHP may be, it’s best to get used to it because it represents a core concept integrated into several FSMA regulations.  FDA can be expected to closely scrutinize the basis for an SLPHP determination.  The guidance sets forth “Points to Consider” that are “intended to provide a general framework for evaluating the adequacy of a measure to provide the necessary level of public health protection that FDA determined is appropriate by establishing the corresponding requirement” – a potentially heavy lift, given the effort ordinarily expended by FDA in establishing food safety requirements.  The guidance forthrightly flags FDA’s expectation that “an SLPHP determination should be supported by sound scientific evidence that is analyzed by competent individuals, taking into account any unique measure-specific considerations.”  That said, the guidance recognizes that the scope of an SLPHP evaluation can vary widely, and one can reasonably expect that the corresponding burdens will vary accordingly.  The Points to Consider included in the draft guidance are listed below:
  • Are the relevant data and information in support of the use of a measure sufficient to make a determination that the measure provides the “same level of public health protection” as the corresponding requirement?
  • Are there any unique considerations relevant to the level of public health protection provided by that measure?
  • Was the evaluation of scientific and technical evidence conducted by competent individuals using an appropriate process?
  • Is the determination of “same level of public health protection” properly documented?

• Hazard Analysis and Risk-Based Preventive Controls for Human Food: Draft Guidance for Industry, Chapter 15: Supply-Chain Program for Human Food – FDA previously issued the first six chapters of this draft guidance.  Issuance of another chapter that focuses on the supply-chain program requirements in part 17, subpart G dovetails with the issuance of the FSVP guidance documents discussed above.  Chapter 15 weighs in at a solid 49 pages and addresses numerous topics, including:
  • The definition of “receiving facility” (with examples), and the circumstances under which certain activities required of a receiving facility can be conducted by other entities
  • The role of a corporate parent in establishing a supply-chain program
  • How to deal with situations where a supply-chain-applied control is applied by an entity other than a supplier
  • The use of sampling and testing as a supplier verification activity
  • What types of records constitute “relevant food safety records”
  • Factors to consider in approving a supplier and determining appropriate supplier verification activities (e.g., a supplier’s food safety history)
  • Development of written procedures for receiving raw materials, including those received from brokers or distributors
  • Alternative supplier verification activities when a supplier is a “qualified facility”
  • Qualifications of a “qualified auditor” (including the need for “at least some actual experience in auditing”)
  • Summary of several types of records required to document a supply-chain program
• Policy Regarding Certain Entities Subject to the Current Good Manufacturing Practice and Preventive Controls, Produce Safety, and/or Foreign Supplier Verification Programs: Guidance for Industry – This guidance states FDA’s intent to exercise enforcement discretion with respect to certain requirements in the regulations on preventive controls for human and animal food, produce safety, and FSVP.  The scope of this exercise of enforcement discretion is summarized in a handy fact sheet. As one especially notable example, each of the four regulations includes a requirement that a manufacturer/processor/importer disclose to its customer when a food is not processed to control an identified hazard, and obtain in return a written assurance that the hazard will be controlled.  Based on “feedback from industry expressing concern that certain product distribution chains would require vastly more written assurances… than anticipated by FDA during the rulemaking process,” FDA will not enforce the written assurance requirements pending the initiation of amendatory rulemaking.

Comments on the three draft guidance documents discussed above are due by May 25, 2018.

Buried in the 250 pages of the Bipartisan Budget Act of 2018 (BBA 2018), which was signed by President Trump on Friday, February 9, are several provisions directly affecting the discounts brand drug manufacturers must pay under federal drug benefit programs:

Increase in Part D Coverage Gap Discount (BBA 2018 section 53116): The first provision will substantially increase coverage gap discounts payable by brand manufacturers under the Medicare Part D prescription drug benefit beginning in 2019. Under Part D, enrollees have heightened co-insurance responsibilities in the so-called coverage gap – i.e., the annual period after the enrollee and the plan have spent a specified amount on covered drugs ($3,750 in 2018), but before the enrollee’s out-of-pocket costs reach the catastrophic coverage threshold ($5,000 in 2018). Under the Coverage Gap Discount Program, the manufacturer of an innovator drug (i.e., a drug approved under an NDA or BLA) dispensed to an enrollee in the coverage gap is currently required to subsidize 50% of the “negotiated price” of the drug – that is, the amount the Part D plan has agreed to pay the pharmacy for the drug. The enrollee and the plan share the remainder of the cost. Before BBA 2018, the enrollee’s cost-sharing amount in the coverage gap, 35% in 2018, was to decrease to 30% in 2019 and 25% in 2020 and thereafter. BBA 2018 has accelerated that reduction so that enrollees will pay 25% in 2019 and thereafter. At the same time, BBA 2018 increased the manufacturer’s subsidy under the Coverage Gap Discount Program from 50% to 70% of the negotiated price, beginning in 2019. (Drugs approved under ANDAs are unaffected by this amendment, since they are not subject to coverage gap discounts.)

Biosimilars no longer exempt from coverage gap discounts (BBA 2018 section 53113): Before BBA 2018, biosimilars were exempt from coverage gap discounts. That exemption will now terminate beginning in 2019.

Correction of alternative rebate for line extensions under Medicaid Drug Rebate Program (BBA section 53104): Under the Medicaid Drug Rebate Program, a line extension (for example, an extended release formulation) of an oral solid dosage form innovator drug is subject to an alternative unit rebate amount (URA) calculation, if that calculation produces a URA higher than that produced under the ordinary statutory methodology. The alternative calculation was intended to tie the URA of the line extension drug to the degree of the original drug’s price increases, in order to prevent manufacturers from avoiding price increase penalties by making small changes in a line extension. However, the alternative calculation formula, enacted in 2010 as part of the Affordable Care Act, did not work as intended, and has now been corrected by BBA 2018.

Before BBA 2018, the alternative URA calculation took the highest additional rebate (i.e., the penalty rebate for price increases greater than inflation) of any strength of the original drug as a percentage of the original drug’s average manufacturer price (AMP), and multiplied that amount by the AMP of the line extension drug. Under the BBA 2018 amendment, an amount is calculated as described above, but that amount is added to the base rebate (usually 23.1% of the AMP) of the line extension drug. Therefore, the alternative URA calculation will be greater under the BBA 2018 revision than under the original provision. The new amendment is effective as of October 1, 2018. Note that CMS has yet to issue regulations defining a “line extension” – something the agency said two years ago that it intends to do.

The Center for Devices and Radiological Health (CDRH) says it has a plan for fostering digital health innovation while reimagining the regulatory oversight to provide patients with access to safe and effective digital health products. One step in the plan is developing a Digital Health Software Precertification (Pre-Cert) Program. We blogged on the overall digital health plan here.

As part of developing the Pre‑Cert Program, Dr. Jeff Shuren, Center Director of CDRH, welcomed the audience to a two day workshop at the end of January. Bakul Patel, Associate Director for Digital Health, introduced the program in detail, summarizing its progress to date and sharing lessons learned. The workshop was divided into five panels with opportunities for the audience to ask questions on the first day and three breakout sessions with time to share breakout discussions with the larger group on the second day.

The panels included representatives from among Pre-Cert pilot participants, CDRH Pre-Cert team members (many of whom doubled as workshop moderators), patients, payers, providers, investors, assessors, trade associations, and academic institutions.

The Pre-Cert Program has been touted as an organization-based streamlined regulatory approach for Software as a Medical Device (SaMD) that relies on a demonstrated Culture of Quality and Organizational Excellence (CQOE), where SaMD is defined as software intended to be used for one or more medical purposes that perform these purposes without being part of a hardware medical device. The excellence principles are:

1. Patient Safety
2. Product Quality
3. Clinical Responsibility
4. Cybersecurity Responsibility
5. Proactive Culture.

One of the overarching workshop themes was that FDA intends to work closely with stakeholders to develop the Pre-Cert Program. The idea is CDRH could “precertify” companies that exhibit CQOE, based on objective criteria. These organizations would qualify to market their lower-risk devices without additional FDA review or with a more efficient premarket review (depending on the product).  This focus on the manufacturer, and not the product, would be a significant departure from the Agency’s historical approach to premarket product review.

The following were interesting or notable aspects of the discussion:

The notion of using CQOE principles for evaluation of software firms was received well, but a lot of questions were raised about what metrics, as a practical matter, would be suitable. There was also a question about how frequently companies would need to re-certify. The moderators also asked participants to consider what the certification review would look like and emphasized that it needed to be feasible for both small and large organizations and align with how software firms conduct themselves.

No consensus answers emerged. True to form for a technological crowd, some panelists suggested crowdsourcing to identify key performance indicators (KPIs metrics).  The crowdsourcing approach was also suggested for collecting real world data from users on product performance, which would then be shared with developers, who would use this feedback to improve safety and effectiveness in the next software version. This iterative life‑cycle approach has the potential to tie in nicely with the Center’s efforts to promote the National Evaluation System for health Technology (NEST), which is being developed to generate better evidence for medical device evaluation across the total product lifecycle and regulatory decision-making.

We learned that the nine pilot participants each had hosted CDRH for a two-day site visit. The visits were the first steps from CDRH to engage stakeholders. Representing small and large organizations, profit and non-profit, the participants agreed on ensuring high‑quality products reached market sooner and promoting a concept of transparency to ensure confidence and credibility of both the program and its participants.

During these visits, CDRH and the pilot participants had discussed common organizational traits such as having agile processes and a culture that recognizes and supports efforts to ensure quality, but also recognized the difficulty in aligning the five excellence principles with the four validating perspectives (i.e., organizational resource, customer, learning and growth, and process). Another outcome of these interactions was that FDA postulated that a library of KPIs could be used to determine a CQOE, acknowledging that no one set would fit every company.

The panels at the workshop provided interesting perspectives on how a precertification program would be understood and received by their communities. For instance, one panelist from the healthcare stakeholder perspectives panel noted the need for clarification between software reviewed under a product based pathway such as the 510(k) versus software considered under a firm based approach as imagined in the Pre-Cert. She also noted that payers will have to consider reimbursement of apps judiciously. The reimbursement process will take time and could frustrate software developers.

Another panelist from the same group pointed out that healthcare is moving towards a value based system that considers clinical outcomes. He expressed concern about constantly evolving algorithms in software and the potential disruption to clinical workflow. The same panelist wondered how a clinician would obtain information to help choose one company’s software over another.

Another panelist brought up recent experience with electronic health records (EHR). The EHR implementation included cybersecurity, lost data, power failure, and interoperability issues. These same issues could begin to plague digital health software.

A panelist challenged the notion that digital health should be subject to traditional processes. He cited the tradeoffs patients are willing to make in exchange for faster access to technology and highlighted the challenges of costly, time‑consuming clinical studies which could lag well behind innovation.

In general, there was much spirited discussion that showed there is still a long way to go in standing up the Pre-Cert program, something the CDRH moderators acknowledged as well. The good news is that CDRH clearly is interested in developing the Pre‑Cert program with input from the community.

It seems to us that the key issue is the KPI metrics that will be used to assess companies. It is easy to sketch out the broad CQOE principles.  Figuring out how to operationalize these principles with concrete KPI metrics is much harder.  Some of the metrics that were introduced and discussed during breakout sessions included employee performance, customer engagement, and brand reputation. However, even these metrics are fairly abstract and hard to measure.  One wonders how “brand reputation” would even apply to smaller start ups.  All in all, it is probably fair to say that the workshop shed light on how difficult it will be to adopt a binding list of KPI metrics and how far off those decisions are.

CDRH has invited those who are willing to share their thoughts on the Pre-Cert Program, whether it be in the form of questions or requests for clarification, to do so in an email to FDAPre-CertPilot@fda.hhs.gov or through a comment on the open docket entitled “Fostering Medical Innovation: A Plan for Digital Health Devices; Software Precertification Pilot Program”.

* Senior Medical Device Regulation Expert

On Friday, February 9, 2018, from 2:00-3:30 PM ET, the Food and Drug Law Institute (“FDLI”) will be hosting a webinar, titled “New Medical Device Requirements and Where Manufacturers Should Focus:  MDUFA, FDARA, and 21st Century Cures.” Hyman, Phelps & McNamara, P.C.’s Jeffrey N. Gibbs will be moderating the webinar.

As the title of the webinar suggests, several important pieces of FDA legislation have recently been enacted that significantly affect the medical device industry.  FDA has been busy implementing the new laws, issuing numerous final and draft guidance documents and policies.  These developments directly affect device companies:

• Implementing changes in device inspections to make them more risk-based
• Establishing pilots for the use of Real World Evidence
• Issuing new checklists for de novo submissions
• Evolving approaches for patient preference information
• Developing guidance in the digital health space
• Streamlining MDR reporting, and more

Keeping up with the array of changes and proposed changes is challenging.  Join a panel of industry and agency experts for a status update on what’s happened already, what’s coming, and where medical device companies should be focusing their efforts.

You can register here for the webinar.

The third-party 510(k) review process was an emphasis in the most recent user fee negotiations and statutory changes under the FDA Reauthorization Act of 2017 (FDARA). This process has been criticized in the past for being restrictive, ineffective, and not beneficial for applicants.  On January 26, 2018, FDA took its first step towards complying with the new requirements when it issued performance metrics for third-party reviewers (available here).

As discussed in our FDARA summary (available here), the types of devices has been modified. Addressing the restrictive aspect, the most significant change was that devices requiring clinical data are no longer excluded from eligibility for the program.  This change has opened up the possibility of more devices, most notably IVDs, being able to undergo third-party review in the future.

FDA will issue a draft guidance regarding the factors it will use to determine whether a Class I or II device is eligible for third-party review, and the Agency will finalize the guidance within 24 months from issuance of the draft. On the same day the guidance is finalized, FDA will also publish a list of Class I and II devices eligible for third-party review. Until this new list is published, the current list of devices eligible for third-party review is still in effect. In addition, as part of the user fee negotiations, FDA agreed, by the end of 2018, to issue draft guidance regarding criteria for reaccreditation of third party reviewers and the suspension or withdrawal of accreditation of a third party.

Finally, FDA agreed to publish performance metrics regarding third-party reviewers with at least five completed submissions on the web. FDA’s published statistics for FY2018 only, meaning, at most, less than four months worth of data.  There were seven third party reviewers totaling 18 510(k) submissions since October 1, 2017.  Only one of the reviewers had more than five submissions during this timeframe.  This report was issued on January 26, but it is not clear when data collection for the report ceased.  This sparse data set is of little to no use.  Presumably, the next data set will be more meaningful.

The user fee commitment did not specify a timeframe for analysis. It seems odd that FDA selected FY2018.  It provides very limited information because it is such a short time frame.  The utility of the report is, accordingly, limited.  We look forward to FDA completing its other required tasks related to the third party review process.  The process certainly holds potential but has been consistent in one respect – during its two decades, it has not lived up to its expectations or potential.  Perhaps these steps will help change that.

REMINDER: Join Us in April to Learn More about Improving Regulatory Compliance While Minimizing Products Liability! (Sign up here.)

On Monday, January 21 (amid the government shutdown) the Center for Veterinary Medicine of the Food and Drug Administration (CVM) released a draft guidance document addressing Subpart C of the Agency’s regulation titled “Current Good Manufacturing Practice, Hazard Analysis, and Risk-Based Preventive Controls for Food for Animals” (PC rule). Subpart C contains the requirements for facilities to use when developing a written animal food safety plan, conducting a hazard analysis and implementing risk-based preventive controls, if needed.

The draft guidance includes five chapters:

• food safety plan requirements;
• recommendations for conducting a hazard analysis;
• hazards associated with the manufacturing, processing, packing and holding of animal food;
• examples of preventive controls that may be used to significantly minimize or prevent animal food hazards; and
• preventive control management components.

In the federal register notice, CVM identifies them as the first five chapters suggesting that more will be added at a later time.

Similar to what FDA did in the draft guidance for human food preventive controls, CVM prepared a list of different animal food ingredients with specific references to hazards. Although this listing of hazards may seem helpful, it does have disadvantages and seems somewhat inconsistent with the PC rule.  Inspectors can be expected to use the list to determine whether a company has included the listed hazards listed in it’s hazard evaluation.  This appears inconsistent with the requirement that a company must conduct its own analysis based on the scientific literature, personal experience, illness data, etc.  We also note that the list of hazards for various ingredients appears to be based on data going back to 1989 – almost thirty years ago.  Query to what extent thirty year old data are relevant.

The timing of the draft guidance is somewhat unfortunate, because the compliance date for all businesses except those that are small or very small has already passed. FDA published final rules to implement the hazard analysis and risk-based preventive control (PC) provisions for human and animal food on September 17, 2015.  Businesses that are not small or very small businesses under the rule were required to comply with the animal food preventive control provisions as of September 18, 2017.  (Small businesses need to comply by no later than September 17, 2018, and very small businesses need to comply with limited provisions by September 17, 2019.)  FDA announced last year in August that it planned to delay routine preventive controls inspections for large businesses until fall 2018.  However, at that time the Agency made clear that this delay in inspections did not mean that companies should wait with the development of their food safety plan.  In the absence of CVM guidance, those food safety plans may not include or have considered hazards that CVM now has identified.  It remains to be seen how CVM will use its own guidance and whether it will rely on the hazards identified in this draft guidance.

Comments to the draft guidance are due by July 23, 2018.

On January 30, 2018, Dr. Gottlieb of FDA and Secretary Perdue of the USDA announced that they had signed a formal agreement to make the coordination and collaboration between the two agencies more efficient and effective.

The USDA has jurisdiction over most meat, poultry, catfish, and certain egg products whereas FDA has jurisdiction over all other foods such as dairy, seafood, produce and packaged foods. Over the years, the two agencies have worked together and made agreements about information sharing, e.g., a Memorandum of Understanding (MOU) from 1999 concerning information sharing about establishments and operations that are subject to dual jurisdiction and an MOU from 2000 concerning review of ingredients intended for use in products under USDA jurisdiction.

The purpose of the January 30, 2018 formal agreement is to “document and formalize ongoing coordination and collaborative efforts between the USDA and the FDA relative to issues of shared concern.” The agreement specifically calls out the issues of dual-jurisdiction facilities, produce safety, and the regulation of biotechnology products.  As far as dual jurisdiction facilities are concerned, “USDA and FDA share the goals of identifying and potentially reducing the number of establishments subject to the dual regulatory requirements of USDA and FDA, bringing greater clarity and consistency to jurisdictional decisions under USDA and FDA’s respective authorities, including transition period, and decreasing unnecessary regulatory burdens.”  Although this likely comes as good news for such facilities, the agreement seems to be a statement of intent and does not provide details as to how the agencies anticipate accomplishing their goals.

The fact is, regulatory compliance has an impact on products liability.  Yet, the two are seldom considered together.

We aim to change that with a special day and a half program (April 12th and 13th).  Our FDA regulatory firm has teamed up with a renowned medical device liability insurer, MEDMARC Insurance, for a joint program.  It will be held at Virginia Tech’s state-of-the-art conference facility in Arlington, Virginia.

Based upon years of claims experience, MEDMARC has identified the specific FDA regulatory areas that pose the most products liability danger.  We will teach you about improving regulatory compliance in those areas.  MEDMARC will help you understand how to reduce products liability risks.  The combination of these two topics creates a synergy that adds up to powerful risk management.

So give yourself a competitive advantage!  Learn the ounce of prevention that will save you many tens of thousands of dollars every time your FDA inspection goes right or a costly products liability lawsuit is prevented.

All the key program details are in the conference brochure.  You can register here for the conference.

We can’t wait to see you this April to share what we know about mitigating the “other risks” associated with government regulation.

UPDATE:

Changes to the format and dates for the MEDMARC, HPM, VaTech program originally scheduled for this April. 
We will continue to partner with MEDMARC and VaTech to cover topics from the existing April agenda but do so in a series of Webex events that will take place beginning later on this year.  This format change will allow us to reach a larger audience more effectively.

Vape shops in several states have banded together in litigation challenging the constitutionality of FDA’s Deeming Rule (for background information on that regulation, see our prior posting here). Plaintiffs are pursuing the litigation simultaneously in several federal district courts – perhaps with the objective of accelerating the emergence of any potential split in the lower courts that would enhance the chances of obtaining Supreme Court review.

The complaints (see here, here, and here) allege that the Deeming Rule violates the Appointments Clause of Article II because it was issued by an FDA employee who lacked the authority to do so. According to Plaintiffs, “[b]ecause the issuance of a rule is final, because a rule binds the government and the regulated public, and because a rule cannot be easily reversed, only a principal officer of the United States—one who has been nominated by the President and confirmed by the Senate—may exercise such authority” (emphasis added). Plaintiffs acknowledge that the Appointments Clause permits Congress to “vest the appointment of ‘inferior Officers… in the President alone, in the Courts of Law, or in the Heads of Departments’” (emphasis added). However, Plaintiffs argue that, even if an inferior officer can issue a rule such as the deeming regulation, “mere agency employees may not.”

The complaints further allege that the Deeming Rule violates the First Amendment by imposing “significant restrictions on truthful, non-misleading speech” in relation to modified-risk tobacco products. The use of a claim to the effect that a given tobacco product presents a lower risk of harm than a commercially marketed tobacco product must first be approved by FDA pursuant to a showing that the given product “will… significantly reduce harm and the risk of tobacco-related disease to individual tobacco users; and… benefit the health of the population as a whole taking into account both users of tobacco products and persons who do not currently use tobacco products.” Even a “reduced exposure” claim, such as a claim that vaping liquids do not have several carcinogens found in cigarettes, requires FDA’s preapproval. Plaintiffs contend that this “imposes an extraordinary prior restraint” on manufacturers and retailers, in that it’s not enough to show that the speech in question is truthful; in addition, one must show that the “truthful speech will create a net benefit.” The Deeming Rule thereby “impermissibly inverts the constitutionally required burden of proof, under which the government, not the speaker, must demonstrate that a restriction on speech directly and materially advances a valid interest asserted by the government” (emphasis in original).

Given the filing of similar complaints in multiple jurisdictions, we would not be surprised to see the government first try to get the cases consolidated (or at least coordinated). We look forward to seeing how the government eventually addresses Plaintiffs’ allegations.

While we’ve seen variations on the First Amendment argument with some frequency in a number of recent FDA cases, the Appointments Clause argument appears to be an issue of first impression in the FDA space.  Significantly, the theory is not limited to the regulations at issue in the case.  If successful, by logical extension it would implicate thousands of FDA regulations.  The statute of limitations for suits against the government may limit the number of affirmative suits challenging regulations to those issued in the past 6 years (28 USC 2401), but nothing would prevent regulated entities from raising this argument as a defense in an FDA enforcement action based on a “defective” regulation.  That said, it’s not clear how a “win” for the plaintiff in this case would play out.  The Appointments Clause argument, if successful, would seem to only invalidate the issuance of the final rule (not, by way of contrast, the notice and comment process).  Presumably, FDA could, without much difficulty, re-issue any affected final rules in short order—if it wanted to do so.  The administration could only re-issue some regulations, however.   In addition to any filings in this action, we’ll also be watching to see under whose authority FDA’s next final rule is issued.

Last month, the U.S. Court of Appeals for the Eleventh Circuit affirmed prison sentences for Stewart and Michael Parnell, and Mary Wilkerson, formerly of the Peanut Corporation of America (PCA). If you missed our earlier coverage of this historic case (here and here), PCA was responsible for a salmonella outbreak that killed at least nine people and sickened thousands in 2009.

In 2014, Stewart and Michael Parnell were convicted of fraudulently introducing misbranded (and, in Michael’s case, also adulterated) food into interstate commerce, interstate shipment and wire fraud, and conspiring to commit those crimes. Stewart and Mary Wilkerson were convicted of obstruction of justice. Stewart Parnell was sentenced to 28 years in prison followed by three years supervised release, Michael Parnell was sentenced to 20 years in prison followed by three years supervised release, and Mary Wilkerson was sentenced to 5 years in prison followed by two years supervised release. All three Defendants challenged their convictions and sentences on various grounds before the District Court for the Middle District of Georgia, and subsequently appealed to the Eleventh Circuit.

The Eleventh Circuit carefully dispensed with the Defendants’/Appellants’ arguments, indicating that they raised no significant legal issues. The Court’s opinion stated at the outside that it “applied only established law” to the facts, and thus was “written only for the benefit of the parties.”  Nevertheless, the Court went into particular detail about the Defendants’ collective claim that the jury’s verdict was tainted by extrinsic evidence of deaths caused by the salmonella outbreak (this evidence was excluded from the trial). Despite finding that individual jurors had, in fact, learned of the deaths during the trial and discussed those deaths during jury deliberations, the Court concluded, among other things, that (1) the District Court did not clearly err in refusing to credit the testimony of one juror who had expressed a bias towards Mary Wilkerson in the past, and (2) the weight of the evidence against the Defendants was such that the additional knowledge about the deaths did not influence or contribute to the verdict. Defendants’/Appellants’ other evidentiary and procedural arguments also failed.

While it is possible that the Parnells and Wilkerson will petition the U.S. Supreme Court for review, and/or petition the Eleventh Circuit for rehearing or hearing en banc, the chances that either court will grant such petitions are relatively slim. Therefore, this may well be the end of the line for Defendants– they will continue to serve out historic prison sentences. Despite the particularly egregious nature of the case, they may also serve as a cautionary tale.

On January 17, 2018, in an effort to overhaul the regulation of over-the-counter (OTC) monograph drugs, U.S. Senators Johnny Isakson and Bob Casey introduced bipartisan legislation, the Over-the-Counter Drug Safety, Innovation, and Reform Act, S.2315.

As readers of this blog know, the current monograph system, which was implemented in 1972, has received criticism and there have been several efforts to revise the system. Drawbacks include the slow rulemaking process (many OTC drugs are marketed under incomplete monographs), the inability to swiftly and promptly address safety issues, and barriers to innovation (eligibility is largely limited to active ingredients that were marketed before 1972).  In addition, FDA has asserted that it lacks the resources to effectively regulate the OTC monograph products.

The proposed bill is intended to speed up the slow time-consuming regulatory procedures by introducing the administrative order process to replace the current rulemaking procedures. It provides options for manufacturers to request administrative orders and for FDA to initiate administrative orders on its own initiative as well as in response to a citizens’ petition.

The bill would also establish a process for the introduction of new OTC products that are marketed without an approved New Drug Application. Under certain circumstances, such drugs would be subject to two-year exclusivity period.

The bill includes provisions that would provide FDA with the authority to take rapid action in event of safety issues with OTC drugs. It would also require that FDA evaluate the cold and cough monograph with respect to children under the age of six and report annually to Congress on the progress of this evaluation.

Importantly, the bill provides FDA with the authority to collect user fees to help cover much of the costs of the updated regulatory system and provide the necessary resources to evaluate and monitor the market.

Other than the two-year exclusivity provision, the proposed bill is similar to previous proposals. See, e.g., Over-the-Counter Monograph Safety, Innovation, and Reform Act of 2017, authored by representatives Bob Latta (R-OR), Diana DeGette (D-CO), Chairman Burgess, Vice Chairman Brett Guthrie (R-KY), Ranking Member Gene Green (D-TX), and Rep. Debbie Dingell (D-MI).

We will be monitoring further developments.

We have seen the stock language in every guidance document FDA issues claiming its guidance is non-binding:

This guidance represents the current thinking of the Food and Drug Administration (FDA or Agency) on this topic. It does not establish any rights for any person and is not binding on FDA or the public. You can use an alternative approach if it satisfies the requirements of the applicable statutes and regulations.

or

FDA’s guidance documents, including this guidance, do not establish legally enforceable responsibilities. Instead, guidances describe the Agency’s current thinking on a topic and should be viewed only as recommendations, unless specific regulatory or statutory requirements are cited. The use of the word should in Agency guidance means that something is suggested or recommended, but not required.

This language provided little solace to FDA-regulated companies who have seen regulatory consequences result from a failure to comply with FDA’s guidance, for example in Warning Letters citing to guidance documents to support findings of noncompliance.

Until now. Last November, the Trump Administration reaffirmed that “the Administrative Procedure Act requires notice-and-comment rulemaking when purporting to create rights or obligations binding on members of the public or the agency,” and made clear its view that guidance “may not be used as a substitute for rulemaking.” The Department of Justice announced that it will discontinue its own practice of binding private parties without rulemaking, and imposed on itself the requirement that its guidance documents clearly state, among other things, “that compliance with those standards is voluntary and that noncompliance will not, in itself, result in any enforcement action.”

Last week, DOJ Associate Attorney General Rachel Brand announced that it will apply DOJ’s position about its own guidance documents to prohibit DOJ from using its civil enforcement authority to convert other agency guidance documents into binding rules. DOJ issued a memorandum directed at all DOJ civil litigators who bring affirmative civil enforcement (ACE) cases, defined as “civil lawsuits on behalf of the United States to recover government money lost to fraud or other misconduct or to impose penalties for violations of Federal health, safety, civil rights or environmental laws.” Of note, DOJ made clear that this policy is “new,” and that it “helps restore” the appropriate role of guidance documents. DOJ now limits the use of guidance documents to certain circumstances – e.g., to prove the requisite mens rea – and “effective immediately,” prevents civil litigators from using “noncompliance with guidance documents as a basis for proving violations of applicable law.” This policy applies to pending and future civil enforcement actions.

DOJ specifically identifies False Claims Act cases as subject to this new policy. For FDA-regulated companies, the impact could be huge. DOJ can no longer base False Claims Act cases on allegations that a company engaged in off-label promotion because it did not meet the requirements set forth in FDA’s Good Reprint Practice Guidance or the draft guidance governing Responses to Unsolicited Requests for Information.   It cannot support a theory that products are unapproved because they do not have the documentation recommended in FDA’s guidance on Deciding When to Submit a New 510(k) for a Change to an Existing Device or establishing Preamendment Status. And it cannot enforce requirements on compounding facilities that have failed to perfectly follow the countless guidance documents FDA has issued in lieu of notice-and-comment rulemaking.

We note that DOJ’s policy cannot stop FDA from continuing to allege violations of its guidance and taking administrative action against companies. Perhaps that will change soon. Nevertheless, the impact of the DOJ policy necessarily will extend to FDA enforcement decisions given DOJ involvement in any ACE cases brought to enforce FDA laws.

On January 24, 2018, FDA and the Federal Trade Commission (FTC) posted joint warning letters to 11 marketers and distributors of opioid cessation products, alleging that those products were unapproved new drugs that violated the Federal Food, Drug, and Cosmetic Act (FDC Act) and made unsubstantiated, deceptive claims in violation of the FTC Act.  Nine of the letters went to dietary supplement marketers, and two to marketers of homeopathic products. The FTC issued four additional warning letters to unidentified marketers of similar products, although it is not clear why those particular marketers (who apparently were not simultaneously targeted by FDA) were permitted to remain anonymous. While it is certainly not unprecedented for the FTC and FDA to issue joint warning letters, the large number of letters bespeaks the importance of this issue to both agencies.

At the end of 2017, an industry coalition of industry trade associations already reminded the industry and consumers that dietary supplement marketers cannot claim that their products treat opioid addiction or withdrawal symptoms.  Under the FDC Act, such claims cause the products to be unapproved drugs. Moreover, FDA has taken the position that opioid addiction is a condition that is not amenable to self-diagnosis or treatment without the supervision of a licensed practitioner and, thus, opioid cessation products cannot be sold over-the-counter. They are regulated as prescription drugs.

As noted above, two of the warning letters, the letter to King Bio, Inc. and the letter to GUNA, Inc., target products labeled as “homeopathic” drugs. Many drug products labeled as homeopathic are manufactured and distributed without FDA approval under enforcement policies set out in the Agency’s Compliance Policy Guide (CPG), which FDA acknowledges in the letters. However, as FDA explains, this does not mean that any product meeting the CPG conditions can be marketed without approval, because “the enforcement policies set forth in the CPG are not unlimited.” Rather, the CPG “delineates those conditions under which homeopathic drugs may ordinarily be marketed in the U.S.” See FDA, Warning Letters to King Bio, Inc. and GUNA, Inc. (Jan. 11, 2018). There are special circumstances that supersede that policy, and the nationwide opioid crisis is one of those special circumstances.

As to the FTC Act violations, the letters note that the claims must be supported by competent and reliable scientific evidence at the time the claims are made. The FTC points to previous FTC enforcement actions challenging claims for the treatment of opiate addiction and withdrawal symptoms FTC v. Sunrise Nutraceuticals, LLC, and FTC v. Catlin Enterprises, Inc., as examples of the possible consequences of making unsupported claims.

FDA and the FTC have requested responses from all the companies within 15 working days.

The final Unique Device Identifier (UDI) Rule was published on September 24, 2013. The last phases of implementation related primarily to Class I and Unclassified devices.  Due to complex issues identified during implementation of the UDI Rule for Class II and III devices, FDA is delaying compliance dates for implantation of the UDI Rule for Class I and Unclassified devices by two years.  Industry was notified of the Agency’s plan to delay last summer via letter, and this enforcement discretion policy has now been formally documented in FDA’s Immediately in Effect Guidance for Industry and FDA Staff, “Unique Device Identification: Policy Regarding Compliance Dates for Class I and Unclassified Devices,” issued on January 16.

The UDI Rule requires a device to have a UDI on its label and packages unless an exception or alternative applies. 21 C.F.R. § 801.20. There are special labeling requirements that apply to stand-alone software regulated as a device. 21 C.F.R. § 801.50). Additionally, the rule requires that certain dates on device labels be in a standard format.  FDA’s UDI system is designed to capture information regarding distributed and used devices and to incorporate this information in an integrated health system, including in the supply chain, registries, and electronic health records.

The UDI requirements have been phased in over the last five years beginning with highest-risk, Class III devices. The final two phases are set to occur on September 24, 2018 and September 24, 2020 with implementation of the below requirements:

Since June 2014, 5% of guidances (8/152) issued by CDRH related to UDI topics. This number of guidances is remarkable given the time it takes to draft and review guidance documents, and the multitude of other important topics CDRH must address. Among these guidances was the November 2017 guidance relating to direct marking of devices with a UDI.  This guidance is noteworthy for those entities required to comply with the Class II marketing requirements taking affect in September 2018.

With the exception of the Class II direct marking requirements, last summer’s letter from FDA to industry extended all of the other upcoming compliance dates by two years. In this letter, FDA promised to issue guidance on articulating its enforcement discretion for the Class I and unclassified device compliance dates.  On January 16, FDA issued such guidance: the immediately-in-effect (for new acronym connoisseurs, IIE) document entitled, “Unique Device Identification: Policy Regarding Compliance Dates for Class I and Unclassified Devices.” The below table shows the original and new compliance dates based on the guidance.

According to the guidance, this extension was granted so that the Agency and industry could identify and address policy and technical challenges to ensure that UDI data are high quality, available, and integrated in standardized and meaningful ways from higher risk devices before focusing on lower risk devices.

In the guidance, FDA distinguishes between class I and unclassified devices manufactured and labeled on or after the original compliance date (September 24, 2018) and finished devices manufactured and labeled prior to the original compliance date established by the FDA. The latter group is excepted from the requirement to bear a UDI for a period of three years after that compliance date. In other words, if your device is manufactured before September 24, 2018, this inventory is afforded a three year exemption out to September 24, 2021. Practically speaking, this means that pre-September 24, 2018 inventory does not need to be reworked to include a UDI on its label or package until September 24, 2021.  If your device is manufactured between September 24, 2018 and September 24, 2020, you lose this rework grace period and are expected to comply with UDI requirements as of the new compliance date (September 24, 2020).  This might prove to be complicated logistically; companies will need to rework inventory built between September 24, 2018 and September 24, 2020 before the new compliance date while not needing to rework pre-September 24, 2018.  FDA offers no rationale for the use of different, misaligned compliance dates.

While this guidance is intended to reduce the burden associated with the UDI rule for finished devices, it appears that misalignment between enforcement dates for devices manufactured before September 24, 2018 and between September 24, 2018 and September 24, 2020 could actually create more burden and confusion. We recommend interested parties comment on the burden that this misalignment will create in two and a half years when the requirements will take effect.

* Senior Medical Device Regulation Expert