Legal Opinion

Battle Creek Health System v. Leavitt

Court of Appeals for the Sixth Circuit

Decided August 14, 2007No. 06-1775PublishedCited by 41 opinions

1Opinion of the Court

OPINION

GRIFFIN, Circuit Judge.

Plaintiffs-appellants Battle Creek Health System (“Battle Creek”) and Trinity Health-Michigan (“Trinity Health”), doing business as Mercy General Health Partners, are acute-care hospitals and participating Medicare providers located in southwestern Michigan. Plaintiffs brought the present action against defendant-appellee Michael Leavitt, Secretary of the United States Department of Health and Human Services (“defendant” or “the Secretary”), pursuant to Title XVIII of the Social Security Act, 42 U.S.C. §§ 1395-1395ggg (the “Medicare Act”) and the Administrative…

2Cases cited16 opinions

  1. Chevron U. S. A. Inc. v. Natural Resources Defense Council, Inc.Supreme Court of the United States · 1984
  2. Christensen v. Harris CountySupreme Court of the United States · 2000
  3. Thomas Jefferson University v. ShalalaSupreme Court of the United States · 1994
  4. Shalala v. Guernsey Memorial HospitalSupreme Court of the United States · 1995
  5. Jewish Hospital, Inc. v. Secretary of Health and Human ServicesCourt of Appeals for the Sixth Circuit · 1994

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

3Cited by41 opinions

  1. City of Cleveland v. OhioCourt of Appeals for the Sixth Circuit · 2007
  2. Alliance for Community Media v. Federal Communications CommissionCourt of Appeals for the Sixth Circuit · 2008
  3. Atrium Medical Center v. United States Department of Health & Human ServicesCourt of Appeals for the Sixth Circuit · 2014
  4. Thornton v. Graphic Communications Conference of the International Brotherhood of Teamsters Supplemental Retirement & Disability FundCourt of Appeals for the Sixth Circuit · 2009
  5. Chao v. Occupational Safety & Health Review CommissionCourt of Appeals for the Sixth Circuit · 2008

36 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