DePuy ASR Hip Litigation: Status and Recall Record Case Study

Why this case matters

The DePuy ASR hip litigation is one of the most closely watched episodes in modern medical-device law, and it is frequently cited as a template for how a high-volume implant dispute is consolidated, negotiated and administered. The matter is identified in the publication’s coverage as MDL No. 2197, consolidated in the Northern District of Ohio, with a settlement reached in 2013 and continued case-status questions in 2026.

That framing already tells a reader most of what makes the case instructive. A single device (the ASR hip implant), a defendant (DePuy), a federal multidistrict proceeding before one court, and a negotiated resolution rather than a series of individual trials: each of these elements shapes what claimants, courts and observers can actually verify years later.

The purpose of this retrospective is narrower than the original reporting. It asks a specific question: what does the documentary record supplied for this analysis actually establish, and where is it silent? The short answer is that the record assembled here is thin on the ASR matter itself and heavy on generic regulatory background. That gap is itself part of the story, because it illustrates the distance between how a case is described in coverage and what a reader can independently confirm from the primary sources at hand.

The official record

The documents assembled for this analysis are drawn almost entirely from US regulatory and court-administration sources rather than from the litigation file.

Several are openFDA data endpoints. One is an enforcement (recall) endpoint, one is a 510(k) premarket notification endpoint, one is a device recall endpoint and one is a food enforcement endpoint. Each carries the standard openFDA disclaimer stating that the data should not be relied upon for medical-care decisions and that results should be assumed unvalidated. The device recall document contains entries about unrelated products (a portable radiographic system, sterile hood packaging and similar items), none of which concern a hip implant. The food enforcement document contains entries about cream, mooncake and supplement products, none of which concern a medical device at all.

Two further documents are agency reference pages. One is the FDA’s 510(k) premarket notification database page, which explains in general terms what a 510(k) submission is: a premarket submission made to demonstrate that a device to be marketed is substantially equivalent to a legally marketed device not subject to premarket approval. The other is the Federal Register’s FDA agency page, which describes the agency’s public-health mission and notes that the electronic edition is unofficial until the Administrative Committee of the Federal Register confers official status.

Finally, there is a US Courts statistics-and-reports page, which consists of site navigation and general descriptions of the federal judiciary and does not contain any statistics about the ASR litigation.

Critically, none of these documents is a court filing, a docket sheet, a settlement agreement, an FDA recall notice for the ASR device, or a judicial opinion. The record does not include the MDL docket, the settlement terms, the recall classification or any order in the case.

What the documents establish

Working strictly within the supplied record, several propositions can be stated and several cannot.

What the documents establish is procedural and definitional. The 510(k) database page confirms that premarket notification is a substantial-equivalence pathway, not an approval pathway. The Federal Register page confirms that the electronic edition is not itself the official legal text. The openFDA endpoints confirm only that the agency publishes unvalidated recall and enforcement data and that the disclaimers attached to those endpoints warn against relying on them for care decisions.

What the documents do not establish is almost everything a reader would want to know about the ASR litigation. The record supplied here contains no statement of what the ASR device was, when it was recalled, how the recall was classified, what the 2013 settlement provided, how many claims were resolved, what the MDL judge ordered, or what the status of the proceeding is in 2026. There is no dollar figure anywhere in the documents, no claimant count, no recall number for the device, no docket entry and no quotation from any party or court.

The record does not state a figure for the settlement. The record does not state a figure for the number of implants affected. The record does not state a date for the recall. Stating any of these would require a source not supplied here. The correct characterization is that the documents are silent on the substance of the case, and the case description in the publication’s coverage is not corroborated by the materials attached to this analysis.

This is not a defect in the case. It is a defect in the record assembled for this particular exercise, and it is worth naming plainly because a retrospective that fills gaps from memory rather than from documents is not a retrospective at all.

How a claim of this kind is assessed

Setting the ASR specifics aside, the documents do support a general account of how a device claim travels through the regulatory and judicial systems, and that account is useful for understanding the structure of a matter like this one.

The regulatory layer comes first. A device reaches the US market either through premarket approval or through the 510(k) substantial-equivalence pathway described on the FDA database page. The pathway matters because it determines what evidence of safety and effectiveness was before the agency at the time of clearance. When a device is later subject to a recall, the agency’s enforcement data records the recall and its classification, though the openFDA disclaimers attached to those endpoints caution that the data is unvalidated.

The judicial layer comes second. When many claimants assert similar injuries from the same product, federal practice permits consolidation of pretrial proceedings before a single judge as a multidistrict litigation. That structure is designed to avoid duplicative discovery and inconsistent pretrial rulings. Consolidation of pretrial proceedings is not the same as a class action: each claimant ordinarily retains an individual case, and the MDL court manages common issues while individual claims are resolved through bellwether trials, settlement or remand.

The resolution layer comes third. A negotiated settlement in an MDL typically follows a settlement agreement, a claims-administration process and court approval of the framework. Whether a given settlement binds a given claimant depends on the terms of the agreement and on whether that claimant participated, which is why settlement figures reported in the press are frequently aggregate figures that do not describe any individual recovery.

None of this tells a reader what happened in the ASR matter specifically. It describes the machinery that any such matter passes through, and it identifies the documents (docket entries, the settlement agreement, the claims-administration reports, the recall notice) that would be needed to answer the specific questions.

What to check before relying on any figure

The single most useful habit in reading about device litigation is to ask what document stands behind a number. The record assembled here shows why.

If a figure is attributed to a settlement, the document to look for is the settlement agreement or the court order approving it, not a press summary. If a figure describes the number of claimants, the document to look for is a court filing or a claims-administration report, not a news account. If a date is given for a recall, the document to look for is the agency’s enforcement record for that specific device, not a general recall endpoint, because the endpoints supply records for many unrelated products and a general query does not establish that a particular device appears in them. If a characterization of a device’s regulatory history is offered, the document to look for is the specific premarket submission, not the database’s explanatory page.

Two cautions follow from the documents themselves. The openFDA disclaimers state that the data should be assumed unvalidated and should not be used for medical-care decisions, which means enforcement records are a starting point rather than a conclusion. The Federal Register page states that the electronic edition is not the official legal text until the Administrative Committee confers official status, which means a citation to the electronic version should be checked against the official edition before it is relied upon in legal research.

Finally, a reader should distinguish between four different kinds of statement, because they carry different weight. An allegation is a claim made by a party and not yet established. A court order is a judicial determination binding on the parties before the court. A regulatory action is an agency determination with its own procedural effect. A settlement is a negotiated resolution, frequently without any admission, and a verdict is a determination by a jury or judge after trial. Coverage of device litigation often blurs these categories, and the ASR matter, like any other, can only be understood by keeping them apart.

On the record supplied for this analysis, the honest conclusion is that the case description is the publication’s, and the documents do not independently corroborate its specifics. A reader seeking verification should go to the MDL docket in the Northern District of Ohio, the FDA enforcement record for the ASR device and the settlement documents themselves. Those are the sources that would answer the questions this record leaves open.

Sources

• U.S. Food and Drug Administration
• U.S. Food and Drug Administration
• U.S. Food and Drug Administration
• 510(k) Premarket Notification
• Federal Register :: Agencies - Food and Drug Administration
• U.S. Food and Drug Administration
• Data & News