Legal Opinion

In re Digitek® Litigation

Texas Judicial Panel on Multidistrict Litigation

Decided August 5, 2009No. 09-0408PublishedCited by 11 opinions

1Opinion of the Court

*116ON REVIEW BY THE MULTIDIS-TRICT LITIGATION PANEL

Presiding Judge PEEPLES

delivered the opinion of the MDL Panel.

Seven defendants have asked the panel to assign a pretrial judge to nineteen drug liability cases pending in twelve counties.1 Plaintiffs allege that the defendants improperly manufactured Digitek tablets that delivered an excessive dosage and caused toxicity-related injuries. Digitek is a generic prescription drug that is used to treat certain abnormal heart rhythms and other problems.

Rule 13 authorizes us to transfer “related” cases from different trial courts to a single pretrial…

2Cases cited8 opinions

  1. Gulf Coast Investment Corp. v. NASA 1 Business CenterTexas Supreme Court · 1988
  2. In Re Hurricane Rita Evacuation Bus FireUnited States Judicial Panel on Multidistrict Litigation · 2006
  3. In Re Ad Valorem Tax LitigationUnited States Judicial Panel on Multidistrict Litigation · 2006
  4. In Re Cano Petroleum, Inc.United States Judicial Panel on Multidistrict Litigation · 2008
  5. In Re Texas Windstorm Insurance Ass'n Hurricanes Rita & Humberto LitigationUnited States Judicial Panel on Multidistrict Litigation · 2009

3 more not listed; retrieve them via the Exa API.

3Cited by11 opinions

  1. In re Deepwater Horizon Incident LitigationTexas Judicial Panel on Multidistrict Litigation · 2011
  2. In re State Farm Lloyds Hurricane Ike LitigationTexas Judicial Panel on Multidistrict Litigation · 2012
  3. In re Wellington Insurance Co. Hailstorm LitigationTexas Judicial Panel on Multidistrict Litigation · 2014
  4. In re Alcon Shareholder LitigationTexas Judicial Panel on Multidistrict Litigation · 2010
  5. In re State Farm Lloyds Hidalgo County Hail Storm LitigationTexas Judicial Panel on Multidistrict Litigation · 2014

6 more not listed; retrieve them via the Exa API.

Showing a preview — retrieve the full document via the Exa API.

Powered by the Exa API