NELSON v. CONNEXIN SOFTWARE INC.

CourtDistrict Court, E.D. Pennsylvania
DecidedMarch 13, 2024
Docket2:22-cv-04676
StatusUnknown

This text of NELSON v. CONNEXIN SOFTWARE INC. (NELSON v. CONNEXIN SOFTWARE INC.) is published on Counsel Stack Legal Research, covering District Court, E.D. Pennsylvania primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
NELSON v. CONNEXIN SOFTWARE INC., (E.D. Pa. 2024).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE EASTERN DISTRICT OF PENNSYLVANIA

KAZANDRA BARLETTI, individually, as

natural parent and next friend of A.B. Case No. 2:22-cv-04676-JDW and C.B., minors,

,

v.

CONNEXIN SOFTWARE, INC. d/b/a

OFFICE PRACTICUM,

.

MEMORANDUM The Parties in this data breach class action seek preliminary approval of a proposed settlement of claims under various states’ laws for negligence and breach of contracts to which plaintiffs and class members were intended third party beneficiaries. After reviewing the facts and the proposed agreement, I will grant the Motion and preliminarily certify the class. I. BACKGROUND A. Factual Allegations Connexin Software, Inc. is an electronic medical records custodian that mostly serves pediatric practices. It provides data security to institutional customers who, in turn, store patients’ personally identifying information (PII) and protected health information (PHI). In August 2022, Connexin became aware of a data breach in which sensitive information of its customers (including information about pediatric patients, their parents and guardians, and insurers) was disclosed to unauthorized individuals. The

data security incident led to the unauthorized disclosure of approximately three million individuals. Among those whose information was subject to the breach were Kazandra Barletti and her minor children, Andrew Recchilongo, Bradley Hain and his minor

children, Sharonda Livingston and her minor son, Hailey Jowers, and Ikram Chowdhury (the “Class Reps”). Each named Party received medical services through a pediatric practice that was a Connexin customer. Each received notice from Connexin by mail informing them that their private information was compromised in the data breach.

B. Procedural History Each named Class Rep initiated a class action complaint. On January 12, 2023, I consolidated the cases. On March 30, 2023, I appointed Benjamin Johns and Bart Cohen as plaintiffs’ interim lead counsel and a five-member Plaintiff’s steering committee. On

April 28, 2023, the Class Reps filed a Consolidated Amended Complaint (“CAC”). Connexin moved to dismiss six of the seven counts in the CAC. I granted that motion in part on August 17, 2023. As a result, the only claims remaining in the case are claims for

negligence and breach of contracts to which plaintiffs and class members were intended third party beneficiaries. After extensive discovery, the Parties began settlement discussions. In November 2023, the Parties held a first mediation session, supervised by the Honorable Diane M. Welsh, U.S.M.J. (Ret.). During that mediation, Connexin claimed to be financially vulnerable, with the prospect of a bankruptcy filing on the horizon. After the mediation,

the Class Reps did additional diligence on Connexin’s financial status, including receiving information from Connexin and consulting with financial experts. Subsequent negotiations with Judge Welsh led to the comprehensive proposed settlement

agreement before me now. C. The Settlement The proposed settlement seeks to certify a settlement class consisting of “[a]ll natural persons whose Personal Information was compromised in the Data Security

Incident that Connexin discovered on or around August 26, 2022.” (ECF No. 85-1 at 5.) Pursuant to the terms of the settlement, Connexin will create a total settlement fund of $4,000,000, which provides: (i) compensation to class members; (ii) service awards of $2,500 to each of the named Plaintiffs; (iii) attorneys’ fees up to one-third of the

Settlement Fund’s total value; (iv) reasonable litigation expenses not to exceed $50,000; and (v) claims expenses by an agreed-upon settlement administrator (Epiq Class Action & Claims Solutions, Inc.), not to exceed $992,187.00. Class members will be able to elect

expanded credit monitoring, reimbursement for out-of-pocket expenses, or an alternative cash payment as their compensation. In addition, if approved, the settlement would require Connexin to seek SOC II certification over the next four years in an effort to enhance its internal data protection compliance measures. In exchange, the Class Reps and class members who choose to participate in the settlement will release Connexin from liability for any claims that class members did

bring or could have brought against it for harms related to the Data Security Incident. II. LEGAL STANDARD Review of proposed Rule 23 class settlement typically proceeds in two steps: (1) a

preliminary approval and (2) a subsequent fairness hearing. , 961 F. Supp. 2d 708, 713–14 (E.D. Pa. 2014). Preliminary approval of a proposed class action settlement is left to the discretion of the trial court. , 148 F.3d 283, 317 (3d Cir.

1998). “The fair, reasonable and adequate standard is lowered, and the court is required to determine whether the proposed settlement discloses grounds to doubt its fairness or other obvious deficiencies. . . .” 961 F. Supp. 2d at 714 (quotation omitted). Nevertheless, “preliminary approval is not simply a judicial ‘rubber stamp’ of the

parties’ agreement.” Rather, it is “based on an examination of whether the proposed settlement is ‘likely’ to be approved under Rule 23(e)(2).” , No. CV 19-2820-KSM, 2020 WL 7711409, at *10 (E.D. Pa. Dec. 28, 2020)

(citing Fed. R. Civ. P. 23(e)(1)(B)(i)). Where settlement precedes class certification, a court may preliminarily certify the class for purposes of providing notice. , 775 F.3d at 581-82; , 521 U.S. 591, 620-22 (1997)). Certification at this stage is not final. , 269 F.R.D. 468, 476 (E.D. Pa. 2010) (citing , 55 F.3d

768, 786 (3d Cir. 1995)). “Final certification of the class is determined by the court at the same time as the court rules on whether the final settlement agreement is to be approved.” .

III. DISCUSSION A. Class Certification To succeed on a class certification motion, a plaintiff must satisfy all four requirements of Rule 23(a) and at least one subsection of Rule 23(b).

, 265 F.3d 178, 183 (3d Cir. 2001). Rule 23(a) requires a showing of: (1) numerosity; (2) commonality; (3) typicality; and (4) adequacy. Fed. R. Civ. P. 23(a). If a plaintiff satisfies these four requirements, he must meet at least one subsection of Rule 23(b). In this case, the Class Reps seek certification pursuant to Rule 23(b)(3). Rule

23(b)(3) contains two explicit requirements: predominance and superiority , 727 F.3d 300, 305 (3d Cir. 2013). As part of a preliminary approval motion, courts can conduct a “less rigorous analysis” than the final approval stage requires.

, No. 15-MD-2654, 2016 WL 1359725, at * 4 (E.D. Pa. Apr. 6, 2016). 1. Rule 23(a) factors a. Numerosity

To satisfy the numerosity requirement, a plaintiff must show that the proposed class is so numerous that joinder of all members is impracticable. This generally requires more than 40 class members. , 837 F.3d 238, 249-50 (3d Cir. 2016). With roughly three million affected individuals, the Class Reps have

shown that joinder is not practicable. b. Commonality The commonality requirement requires a plaintiff to demonstrate that “there are questions of law or fact common to the class.” Fed. R. Civ. P.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Amchem Products, Inc. v. Windsor
521 U.S. 591 (Supreme Court, 1997)
Ehrheart v. Verizon Wireless
609 F.3d 590 (Third Circuit, 2010)
In Re Pet Food Products Liability Litigation
629 F.3d 333 (Third Circuit, 2010)
Wal-Mart Stores, Inc. v. Dukes
131 S. Ct. 2541 (Supreme Court, 2011)
In Re: Cendant Corporation Litigation
264 F.3d 201 (Third Circuit, 1992)
Marcus v. BMW of North America, LLC
687 F.3d 583 (Third Circuit, 2012)
In Re Baby Products Antitrust Litigation
708 F.3d 163 (Third Circuit, 2013)
John Rodriguez v. Natl City Bank
726 F.3d 372 (Third Circuit, 2013)
Gabriel Carrera v. Bayer Corp
727 F.3d 300 (Third Circuit, 2013)
In Re Hydrogen Peroxide Antitrust Litigation
552 F.3d 305 (Third Circuit, 2009)
McDonough v. Toys" R" US, Inc.
638 F. Supp. 2d 461 (E.D. Pennsylvania, 2009)
In Re Automotive Refinishing Paint Antitrust Litigation
617 F. Supp. 2d 336 (E.D. Pennsylvania, 2007)
Reynaldo Reyes v. Netdeposit
802 F.3d 469 (Third Circuit, 2015)
Tyson Foods, Inc. v. Bouaphakeo
577 U.S. 442 (Supreme Court, 2016)
In Re Modafinil Antitrust Litigation
837 F.3d 238 (Third Circuit, 2016)
Jaime Gonzalez v. Owens Corning
885 F.3d 186 (Third Circuit, 2018)
McDonough v. Toys "R" Us, Inc.
80 F. Supp. 3d 626 (E.D. Pennsylvania, 2015)

Cite This Page — Counsel Stack

Bluebook (online)
NELSON v. CONNEXIN SOFTWARE INC., Counsel Stack Legal Research, https://law.counselstack.com/opinion/nelson-v-connexin-software-inc-paed-2024.