What Is The FTC Looking at When It Reviews Merger Agreements?

In our last post, we spoke about a proposed merger between office supply chains Office Depot and Staples. As we noted, Office Depot shareholders recently voted to go forward with the acquisition, but the Federal Trade Agreement still has to review the agreement and make a decision, which could make or break the process.

FTC_FederalTradeCommission-SealIn reviewing any merger agreement the Federal Trade Commission—or the Department of Justice, depending on which agency reviews the agreement—an important consideration is the impact the transaction will have on the market. Speaking generally, federal law prohibits mergers that would potentially harm market competition by creating a monopoly on goods or services.

According to the FTC, competitive harm often stems not from the agreement as a whole, but from how the deal will impact certain areas of business. Problems can arise when a proposed merger has too much of a limiting effect based on the type of products or services being sold and the geographic area in which the company is doing business.

With that having been said, most mergers—95 percent, according to the FTC—present no issues in terms of market competition. Those that do present issues are often resolved by tweaking the agreement so as to address any competitive threats. In cases where the reviewing agency and the businesses cannot agree on a solution, litigation may be necessary, but it often isn’t.

Any company that plans on going forward with a merger or acquisition needs to have a clear understanding of the law and the review process. This is especially the case if issues come up regarding competitive threats.

© 2015 by McBrayer, McGinnis, Leslie & Kirkland, PLLC. All rights reserved.

New Data Security Bill Seeks Uniformity in Protection of Consumers’ Personal Information

Morgan, Lewis & Bockius LLP.

Last week, House lawmakers floated a bipartisan bill titled the Data Security and Breach Notification Act (the Bill). The Bill comes on the heels of legislation proposed by US President Barack Obama, which we recently discussed in a previous post. The Bill would require certain entities that collect and maintain consumers’ personal information to maintain reasonable data security measures in light of the applicable context, to promptly investigate a security breach, and to notify affected individuals of the breach in detail. In our Contract Corner series, we have examined contract provisions related to cybersecurity, including addressing a security incident if one occurs.

Some notable aspects of the Bill include the following:

  • Notification to individuals affected by a breach would generally be required within 30 days after a company has begun taking investigatory and corrective measures (rather than based on the date of the breach’s discovery).

  • Notification to the Federal Trade Commission (FTC) and the Secret Service or the Federal Bureau of Investigation would be required if the number of individuals whose personal information was (or there is a reasonable basis to conclude was) leaked exceeds 10,000.

  • To advance uniform and consistently applied standards throughout the United Sates, the Bill would preempt state data security and notification laws. However, the scope of preemption continues to be discussed, and certain entities would be excluded from the Bill’s requirements, including entities subject to existing data security regulatory regimes (e.g., entities covered by the Health Insurance Portability and Accountability Act).

  • Violations of the Bill would be enforced by the FTC or state attorneys general (and not by a private right of action).

ARTICLE BY

IoT – It’s All About the Data, Right?

Foley and Lardner LLP

A few weeks ago, the FTC released a report on the Internet of Things (IoT). IoT refers to “things” such as devices or sensors – other than computers, smartphones, or tablets – that connect, communicate or transmit information with or between each other through the Internet. This year, there are estimated to be over 25 billion connected devices, and by 2020, 50 billion. With the ubiquity of IoT devices raising various concerns, the FTC has provided several recommendations.

Security

The report includes the following security recommendations for companies developing Internet of Things devices:

  • Build security into devices at the outset, rather than as an afterthought in the design process

  • Train employees about the importance of security, and ensure that security is managed at an appropriate level in the organization

  • Ensure that when outside service providers are hired, that those providers are capable of maintaining reasonable security, and provide reasonable oversight of the providers

  • When a security risk is identified, consider a “defense-in-depth” strategy whereby multiple layers of security may be used to defend against a particular risk

  • Consider measures to keep unauthorized users from accessing a consumer’s device, data, or personal information stored on the network

  • Monitor connected devices throughout their expected life cycle, and where feasible, provide security patches to cover known risks

Data Minimization

The report suggested companies consider data minimization – that is, limiting the collection of consumer data, and retaining that information only for a set period of time, and not indefinitely. Data minimization addresses two key privacy risks: first, the risk that a company with a large store of consumer data will become a more enticing target for data thieves or hackers, and second, that consumer data will be used in ways contrary to consumers’ expectations.

Notice and Choice

The FTC provided further recommendations relating to notice and choice. It is recommended that companies notify consumers and give them choices about how their information will be used, particularly when the data collection is beyond consumers’ reasonable expectations.

What Does This Mean for Device Manufacturers?

It is evident from the FTC’s report that security and data governance are important features for IoT device manufacturers to consider. Although the report suggests implementing data minimization protocols to limit the type and amount of data collected and stored, IoT device manufacturers should not be short-sighted when deciding what data to collect and store through their IoT devices. For many IoT device manufacturers, the data collected may be immensely valuable to them and other stakeholders. It would be naïve to decide not to collect certain types of data simply because there is no clear use or application of the data, the costs and risks of storing such data are cost prohibitive or because they want to reduce their exposure due to a security breach. In fact, quite often IoT device manufacturers do not realize what types of data may be useful. IoT device manufacturers would be best served by analyzing who the stakeholders of their data may be.

For instance, an IoT device manufacturer that monitors soil conditions of farms may realize that the data they collect can be useful, not only to farmers, but also to insurance companies to better understand water table levels, produce suppliers, wholesalers, and retailers to predict produce inventory, farm equipment suppliers, among others. Because of this, IoT device manufacturers should identify the stakeholders of the data they collect early and revisit the data they collect to identify new stakeholders not previously identified based on trends that can be determined from the data.

Moreover, IoT device manufacturers should constantly consider ways to monetize or otherwise leverage the data they gather and collect. IoT device manufacturers tend to shy away from owning the data they collect in an effort to respect their customers’ privacy. Instead of not collecting sensitive data at all, IoT device manufacturers would be best served by exploring and implementing data collection and storage techniques that reduce their exposure to security breaches while at the same time allay the fears of customers.

ARTICLE BY

OF

FTC Releases Extensive Report on the “Internet of Things”

Mcdermott Will Emery Law Firm

On January 27, 2015, U.S. Federal Trade Commission (FTC) staff released an extensive report on the “Internet of Things” (IoT). The report, based in part on input the FTC received at its November 2013 workshop on the subject, discusses the benefits and risks of IoT products to consumers and offers best practices for IoT manufacturers to integrate the principles of security, data minimization, notice and choice into the development of IoT devices. While the FTC staff’s report does not call for IoT specific legislation at this time, given the rapidly evolving nature of the technology, it reiterates the FTC’s earlier recommendation to Congress to enact strong federal data security and breach notification legislation.

The report also describes the tools the FTC will use to ensure that IoT manufacturers consider privacy and security issues as they develop new devices. These tools include:

  • Enforcement actions under such laws as the FTC Act, the Fair Credit Reporting Act (FCRA) and the Children’s Online Privacy Protection Act (COPPA), as applicable;

  • Developing consumer and business education materials in the IoT area;

  • Participation in multi-stakeholder groups considering guidelines related to IoT; and

  • Advocacy to other agencies, state legislatures and courts to promote protections in this area.

In furtherance of its initiative to provide educational materials on IoT for businesses, the FTC also announced the publication of “Careful Connections: Building Security in the Internet of Things”.  This site provides a wealth of advice and resources for businesses on how they can go about meeting the concept of “security by design” and consider issues of security at every stage of the product development lifecycle for internet-connected devices and things.

This week’s report is one more sign pointing toward our prediction regarding the FTC’s increased activity in the IoT space in 2015.

It’s Data Privacy Day 2015

Mintz Levin Law Firm

Today is Data Privacy Day, and as you might expect, we have a few bits and bytes for you.

Use the Opportunity

Data Privacy Day is another opportunity to push out a note to employees regarding their own privacy and security — and how that can help the company.

The Federal Trade Commission Issues IoT (Internet of Things) Report

Following up on its November 2013 workshop on the Internet of Things, the Federal Trade Commission (“FTC”) has released a staff report on privacy and security in the context of the Internet of Things (“IoT”), “Internet of Things: Privacy & Security in a Connected World” along with a document that summarizes the best practices for businesses contained in the Report.  The primary focus of the Report is the application of four of the Fair Information Practice Principles (“FIPPs”) to the IoT – data security, data minimization, notice, and choice.

Data PrivacyThe report begins by defining IoT for the FTC’s purposes as “‘things’ such as devices or sensors – other than computers, smartphones, or tablets – that connect, communicate or transmit information with or between each other through the Internet,” but limits this to devices that are sold to or used by consumers, rather than businesses, in line with the FTC’s consumer protection mandate.  Before discussing the best practices, the FTC goes on to delineate several benefits and risks of the IoT.  Among the benefits are (1) improvements to health care, such as insulin pumps and blood-pressure cuffs that allow people avoid trips to the doctor the tools to monitor their own vital signs from home; (2) more efficient energy use at home, through smart meters and home automation systems; and (3) safer roadways as connected cars can notify drivers of dangerous road conditions and offer real-time diagnostics of a vehicle.

The risks highlighted by the Report include, among others, (1) unauthorized access and misuse of personal information; (2) unexpected uses of personal information; (3) collection of unexpected types of information; (4) security vulnerabilities in IoT devices that could facilitate attacks on other systems; and (5) risks to physical safety, such as may arise from hacking an insulin pump.

In light of these risks, the FTC staff suggests a number of best practices based on four FIPPs. At the workshop from which this report was generated, all participants agreed on the importance of applying the data security principle.  However, participants disagreed concerning the suitability of applying the data minimization, notice, and choice principles to the IoT, arguing that minimization might limit potential opportunities for IoT devices, and notice and choice might not be practical depending on the device’s interface – for example, some do not have screens.  The FTC recognized these concerns but still proposed best practices based on these principles.

Recommendations

Data Security Best Practices:

  • Security by design.  This includes building in security from the outset and constantly reconsidering security at every stage of development. It also includes testing products thoroughly and conducting risk assessments throughout a product’s development

  • Personnel practices.  Responsibility for product security should rests at an appropriate level within the organization.  This could be a Chief Privacy Officer, but the higher-up the responsible part, the better off a product and company will be.

  • Oversee third party providers.  Companies should provide sufficient oversight of their service providers and require reasonable security by contract.

  • Defense-in-depth.  Security measures should be considered at each level at which data is collected stored, and transmitted, including a customer’s home Wi-Fi network over which the data collected will travel.  Sensitive data should be encrypted.

  • Reasonable access control.  Strong authentication and identity validation techniques will help to protect against unauthorized access to devices and customer data.

Data Minimization Best Practices:

  • Carefully consider data collected.  Companies should be fully cognizant of why some category of data is collected and how long that data should be stored.

  • Only collect necessary data.  Avoid collecting data that is not needed to serve the purpose for which a customer purchases the device. Establish a reasonable retention limit on data the device does collect.

  • Deidentify data where possible.  If deidentified data would be sufficient companies should only maintain such data in a deidentified form and work to prevent reidentification.

Notice and Choice Best Practices:  The FTC initially notes that the context in which data is collected may mean that notice and choice is not necessary. For example, when information is collected to support the specific purpose for which the device was purchased.

When notice or choice are necessary, the FTC offers several suggestions for how a company might give or obtain that, including (1) offer choice at point of sale; (2) direct customers to online tutorials; (3) print QR codes on the device that take customers to a website for notice and choice; provide choices during initial set-up; (4) provide icons to convey important privacy-relevant information, such a flashing light that appears when a device connects to the Internet; (5) provide notice through emails or texts when requested by consumers; and (6) make use of a user experience approach, such personalizing privacy preferences based on the choices a customer already made on another device.

Legislation.  The FTC staff recommends against IoT-specific legislation in the Report, citing the infancy of the industry and the potential for federal legislation to stifle innovation.  Instead, the FTC recommends technology-neutral privacy and data security legislation.  Without saying it explicitly, this appears to be a recommendation for something akin to the Consumer Privacy Bill of Rights recently proposed by the President, along with giving the FTC authority to enforce certain privacy protections, including notice and choice, even in the absence of a showing of deceptive or unfair acts or practices.

In the meantime, the FTC notes that it will continue to provide privacy and data security oversight of IoT as it has in other areas of privacy.  Specifically, the FTC would continue to enforce the FTC Act, the Children’s Online Privacy Protection Act, and other relevant statutes.  Other initiatives would include developing education materials, advocating on behalf of consumer privacy, and participating in multi-stakeholder groups to develop IoT guidelines for industry.

FTC Denies AgeCheq Parental Consent Application But Trumpets General Support for COPPA Common Consent Mechanisms

Covington BUrling Law Firm

The Federal Trade Commission (“FTC”) recently reiterated its support for the use of “common consent” mechanisms that permit multiple operators to use a single system for providing notices and obtaining verifiable consent under the Children’s Online Privacy Protection Act (“COPPA”). COPPA generally requires operators of websites or online services that are directed to children under 13 or that have actual knowledge that they are collecting personal information from children under 13 to provide notice and obtain verifiable parental consent before collecting, using, or disclosing personal information from children under 13.   The FTC’s regulations implementing COPPA (the “COPPA Rule”) do not explicitly address common consent mechanisms, but in the Statement of Basis and Purpose accompanying 2013 revisions to the COPPA Rule, the FTC stated that “nothing forecloses operators from using a common consent mechanism as long as it meets the Rule’s basic notice and consent requirements.”

The FTC’s latest endorsement of common consent mechanisms appeared in a letter explaining why the FTC was denying AgeCheq, Inc.’s application for approval of a common consent method.  The COPPA Rule establishes a voluntary process whereby companies may submit a formal application to have new methods of parental consent considered by the FTC.  The FTC denied AgeCheq’s application because it “incorporates methods already enumerated” in the COPPA Rule: (1) a financial transaction, and (2) a print-and-send form.   The implementation of these approved methods of consent in a common consent mechanism was not enough to merit a separate approval from the FTC .  According to the FTC, the COPPA Rule’s new consent approval process was intended to vet new methods of obtaining verifiable parental consent rather than specificimplementations of approved methods.  While AgeCheq’s application was technically “denied,” the FTC emphasized that AgeCheq and other “[c]ompanies are free to develop common consent mechanisms without applying to the Commission for approval.”  In support of common consent mechanisms, the FTC quoted language from the 2013 Statement of Basis and Purpose and pointed out that at least one COPPA Safe Harbor program already relies on a common consent mechanism.

OF

U.S. Sentencing Commission Weighing Recommendation to Increase Criminal Antitrust Penalties

Dickinson Wright Logo

In June, the United States Sentencing Commission, which is appointed by the President to make recommendations to Congress on the criminal penalties for the violation of federal law, issued a request for comments regarding whether the guidelines for calculating antitrust fines should be modified. Currently, corporate fines for cartel price fixing are calculated on a sliding scale, tied to the amount of the “overcharge” imposed by the violators, with the standard maximum fine under the Guidelines for a corporation capped at $100 million and, for an individual, capped at $1 million. The deadline for such comments was July 29, and the views expressed on the issue varied considerably.

Contending that the current Guidelines do not provide an adequate deterrent to antitrust violations, the American Antitrust Institute urged the Commission to recommend an increase in the fines for cartel behavior. The AAI stated that the presumption in the Guidelines that antitrust cartels, on average, “overcharge” consumers for goods by 10% is greatly understated, and thus should be corrected to reflect more accurate levels. Pointing to economic studies and cartel verdicts, the AAI suggests that the median cartel “overcharge” is actually in excess of 20%, and therefore the presumption should be modified in the Guidelines. If adopted, the AAI’s proposal would double the recommended fines under the Guidelines for antitrust violations.

Perhaps surprisingly, the DOJ responded to the Commission’s Notice by stating that it believes that the current fines are sufficient, and that no increase in antitrust fines is warranted at this time. The DOJ indicated that the 10% overcharge presumption provides a “predictable, uniform methodology” for the calculation of fines in most cases, and noted that the Guidelines already permit the DOJ to exceed the fine levels calculated using the 10% overcharge presumption in some circumstances. Specifically, the DOJ noted that the alternative sentencing provisions of 18 USC 3571 already permit it to sidestep the standard guidelines and seek double the gain or loss from the violation where appropriate. Notably, the DOJ utilized this provision in seeking a $1 billion fine from AU Optronics in a 2012 action, although the court declined the request, characterizing it as “excessive”. The court did, however, impose a $500 million fine, an amount well in excess of the cap under the standard antitrust fine guidelines.

Finally, D.C. Circuit Court of Appeals Judge Douglas Ginsburg and FTC Commissioner Joshua Wright offered a completely different view on the issue in comments that they submitted to the Sentencing Commission. Suggesting that fines imposed on corporations seem to have little deterrent effect, regardless of amount, they encouraged the Commission to instead recommend an increase in the individual criminal penalty provisions for antitrust violations. Notably, they encouraged the Commission not only to consider recommending an increase in the fines to which an individual might be subjected (currently capped at $1 million), but also to recommend an increase in the prescribed range of jail sentences for such conduct (which currently permit for imprisonment of up to 10 years).

The Commission will now weigh these comments and ultimately submit its recommendations to Congress by next May. If any changes are adopted by Congress, they would likely go into effect later next year. Stay tuned.

ARTICLE BY

 
OF 

Too Good To Be True: FTC’s Crackdown On L’Occitane’s Body Slimming Almond Extracts

Sheppard Mullin Law Firm

L’Occitane Inc’s advertisements for its topically-applied body sculpting almond extracts seemed straightforward: “Almond Shaping Delight 3 out of 4 women saw firmer, lifted skin. This luxuriously lightweight massage gel instantly melts into the skin to help visibly refine and sculpt the silhouette” and “Almond Beautiful Shape Trim 1.3 inches in just 4 weeks. This ultra-fresh gel cream helps to visibly reduce the appearance of cellulite, while smoothing and firming the skin.”

Unfortunately for L’Occitane, an international skin care company with over 150 shops across the U.S., the Federal Trade Commission (FTC) found those claims dubious at best, and earlier this year charged the company with violating the Federal Trade Commission Act (“FTC Act”).

According to the FTC’s complaint, which was filed on January 7, 2014, L’Occitane had been manufacturing, advertising, and selling the two products at issue, “Almond Beautiful Shape” and “Almond Shaping Delight,” in interstate commerce and violated the FTC Act by promoting them as being able to slim and reshape the body. The FTC alleged that L’Occitane did not have sufficient scientific data to support L’Occitane’s advertising claims that the creams could trim the user’s thighs, reduce cellulite, and slim the body in just weeks. The FTC asserted that  L’Occitane based its advertising claims in large part on two unblinded and non-controlled clinical trials and greatly exaggerated the results from one of the studies. The FTC charged L’Occitane with violating Sections 5(a) and 12 of the FTC Act, which declare unfair or deceptive acts or practices unlawful and bar false advertisements likely to induce the purchase of food, drugs, devices, or cosmetics. As part of the final consent order, the FTC fined L’Occitane $450,000 and prohibited it from making future false and deceptive weight-loss claims.

L’Occitane, however, is not the only entity which the FTC has recently fined because of questionable advertising claims. The FTC has also charged Sensa Products, LeanSpa, and HCG Diet Direct with violations of the FTC Act for allegedly misleading the public with unfounded weight loss claims and misleading endorsements relating to their products. These complaints, along with L’Occitane’s, were part of the FTC’s recent “Operation Failed Resolution” initiative, aimed at combating deceptive weight-loss claims.

One of the companies charged, Sensa Products, which claimed weight loss results from one of its dietary supplements, had to pay a $26 million fine for FTC Act violations. As a part of “Operation Failed Resolution,” the FTC also released an updated media guide for spotting deceptive weight-loss claims in advertising, entitled “Gut Check: A Reference Guide for Media on Spotting False Weight-Loss Claims.”

Manufactures and marketers of health products, cosmetics, drugs, and dietary supplements should be mindful of the FTC’s continuing and increasing vigilance in taking action with respect to enforcement of the FTC Act to stop unfounded weight loss claims. Companies making weight-loss claims in advertising and marketing materials must make sure that their claims are defensible and supported by sufficient credible scientific data.

Jordan Grushkin contributed to this article.

Article By:

Of:

New Updated FTC Care Labeling Rules: “Do’s and Don’ts”

Sheppard Mullin 2012

The Federal Trade Commission (“FTC”) enforces federal labeling requirements that require manufacturers, importers, sellers and distributors of certain textile and wool clothing  to accurately label their products. For example, FTC rules require that manufacturers indicate the country of origin and fiber content in their clothing. In addition, the Care Labeling Rule requires that manufacturers and importers attach “care labels” to garments and certain piece goods.

Navigating these various labeling requirements can be tricky. On May 5, 2014, the FTC amendment of the labeling rules, known as the Textile Rules, became effective.

Care labels, which can influence consumers’ purchasing decisions more than labels indicating fiber content or country of origin or manufacture, are important to carefully consider.

“Do’s” for Clothing Manufacturers and Importers:

Place all care labels permanently, securely and visibly, so that consumers can easily see or locate them prior to purchase. Ensure that labels will remain legible not just at the point of sale, but throughout the lifecycle of the product.

Include a washing or drycleaning instruction (or both) if either method is safe for the product. If a product can be neither washed nor drycleaned, the label must state “Do not wash – Do not dry clean.” A simple “dryclean” instruction is acceptable in most cases, unless “any part of the drycleaning process would harm the product.” In that case, more specificity is required (e.g., “Professionally Dryclean” or “Dryclean. No Steam.”).

Indicate whether the product is to be washed by machine or by hand. The FTC has stated that water temperature settings must be indicated if “regular use of hot water will harm the product.” Similarly, if using chlorine bleach will harm the product, whereas other bleaches will not, the label must state “Only non-chlorine bleach, when needed.” The appropriate label in the event that no bleach is safe to use is “Do not bleach.”

State how to dry the product and how to iron it, if the product requires regular ironing. Temperature settings for drying and ironing are not needed unless the “regular use of high temperature will harm the product.”

If selling a garment with multiple pieces, only one label is required if the same instructions apply to all parts of the garment, and if the garment is sold as a single unit. The label should be attached to the “major piece” of the garment. In the event that the garment is not sold as a single unit, or if the instructions differ from one part of the garment to the next, then each separate piece of the garment needs its own care label.

If the garment cannot be cleaned without damaging the garment, potential customers must be warned on the label. It is imperative that following the care labeling instructions does not ordinarily lead to product damage. Along these lines, labels must inform consumers not to engage in certain procedures that they may erroneously but reasonably assume are acceptable, given the instructions of the label. For example, if a label indicates that clothes can be washed, a reasonable consumer might infer that the product can also be safely ironed. If these understandable assumption is incorrect, the FTC has stated that the label must indicate the risks involved.

One should always have a “reasonable basis” for everything written on a care labeling instruction. If a piece of clothing indicates that it cannot safely be ironed, there must be some proof (based upon experience, industry expertise or testing) known to the manufacturer or importer that ironing the clothing would cause damage. The FTC has alternatively stated that the manufacturer or importer must have “reliable evidence” to support all warnings or instructions on product labels. Guesswork is insufficient. However, what constitutes “reliable evidence” or a “reasonable basis” does depend on the circumstances. It is incumbent on manufacturers conducting tests to ensure that the results of any tests conducted on only one portion of multi-part garments do, in fact, have applicability to the entire garment.

Importers must ensure that these labels are placed on products before they sell them in the United States. It is not necessary for the labels to be attached as the products enter the country, however. Domestic manufacturers similarly must ensure that care labels are placed on finished products prior to sale.

“Don’ts” for Clothing Manufacturers and Importers:

Certain kinds of exempt apparel, including gloves, hats, and shoes, do not require care labels. Many items are also excluded from the care labeling requirements, including handkerchiefs, belts, suspenders, neckties, or non-woven garments made for one-time use. For piece goods sold for making apparel at home, it is not necessary to include care labeling instructions for any “marked manufacturers’ remnants of up to 10 yards when the fiber content is not known and cannot be determined easily.” These items are exempted from the Care Labeling Rule.

Garments custom-made from fabrics provided by consumers, or products sold directly to institutional buyers for commercial use (e.g., uniforms sold to Office Depot for use by clerks during business hours, and not purchased directly by the clerks), do not require care labels. This also includes items that the consumer may ask to be added to the garment (e.g. lining or buttons).

Use non-standard terms on labels. The FTC recommends, but does not expressly require, that manufacturers ensure that any terms they use on labels are in accord with the definitions in the Rule’s Appendix A glossary, where applicable. For example, the term “Warm” applies to initial water temperature ranging from 87 to 111 degrees F [31 to 44 degrees C]; “Hot” is from 112 to 145 degrees F [45 to 63 degrees C]; and “Cold” is up to 86 degrees F [30 degrees C].

*Gregg Re Summer Associate contributed to this article.

Article By:

Of:

Federal Trade Commission (FTC) Wins Appeal: ProMedica Merger with St. Luke’s Not Allowed

vonBriesen

On April 22, 2014, the U.S. Court of Appeals for the Sixth Circuit (Sixth Circuit) upheld the Federal Trade Commission’s (FTC) finding that the merger between Ohio-basedProMedica Health System, Inc. (ProMedica) and St. Luke’s Hospital (St. Luke’s), an independent community hospital that operates in the one of the same counties as ProMedica, would adversely affect competition in violation of federal antitrust law. Prior to the merger, ProMedica and St. Luke’s comprised two of the four hospital systems in Lucas County, Ohio. After the two systems merged, ProMedica held more than 50% of the applicable market share.

Accordingly, in 2011 the FTC ordered ProMedica to divest itself of St. Luke’s. ProMedica appealed the FTC’s order to the Sixth Circuit. In a unanimous opinion, the Sixth Circuit denied ProMedica’s petition to overturn the FTC order, citing concerns about anti-competitive behavior and the ability of ProMedica to unduly influence reimbursement rates with healthcare insurance companies.

The full 22-page court opinion may be accessed here.

Article By:

Of: