Quest Diagnostics Incorporated Patent litigation record

Company 10 cases

10 cases on record naming Quest Diagnostics Incorporated: 1 as claimant, 9 as respondent. Each row links to that case’s full docket record.

Litigation indexPatsnap Litigation Data··Docket source: PACER

10 cases on record

Cases on record
10
As claimant
1
As respondent
9
Patents held
Not recorded
Core tech
Not recorded
Case no.PartiesRoleCourtFiledDurationOutcome
6:20-cv-00972 Ravgen, Inc. v. Quest Diagnostics Incorporated Defendant W.D. Tex. 16 Oct 2020 395 d Case Transferred
2:17-cv-05169 Cedars Sinai Medical Center v. Quest diagnostics, Inc. Defendant C.D. Cal. 13 Jul 2017 799 d Judgment on the Merits
2:17-cv-02082 Symbology Innovations, LLC v. Quest Diagnostics Incorporated Defendant D.N.J. 30 Mar 2017 183 d Procedural Outcome
2:17-cv-00226 NeoDiagnostix, Inc. v. Quest diagnostics, Inc. Defendant E.D. Tex. 23 Mar 2017 139 d Voluntary dismissal
2:15-cv-01024 Data Carriers, LLC v. Quest Diagnostics Incorporated Defendant E.D. Tex. 12 Jun 2015 375 d Likely Settlement
2015-1279 MyMedicalRecords, Inc. v. Quest Diagnostics Incorporated Defendant Fed. Cir. 22 Jan 2015 166 d Closed
6:14-cv-00462 Presqriber, LLC v. Quest Diagnostics Incorporated Defendant E.D. Tex. 8 May 2014 273 d Likely Settlement
2:14-cv-00152 Quest Diagnostics Incorporated v. Myriad Genetics, Inc. Plaintiff D. Utah 3 Mar 2014 344 d Likely Settlement
2:13-cv-00967 University of Utah Research Foundation v. Quest Diagnostics Incorporated Defendant D. Utah 22 Oct 2013 476 d Likely Settlement
2:13-cv-02538 MyMedicalRecords, Inc. v. Quest diagnostics, Inc. Defendant C.D. Cal. 10 Apr 2013 639 d Judgment on the Merits
Source: Patsnap Litigation Data. Cases naming Quest Diagnostics Incorporated in the current snapshot. Run this in Eureka
Patsnap Eureka

See what Quest Diagnostics is protecting

Portfolio, claim scope and where its coverage is thin. Every answer cites the records behind it.

Analyse this portfolio
10,000 free credits to start

About this summary. This page summarises the litigation records within the coverage and snapshot dates stated here. Counts describe records in that dataset and do not, by themselves, establish the conduct, litigation success or legal position of any person or organisation.

Docket data has limits. Records are drawn from a snapshot and may lag the live docket. Sealed filings, amended complaints, counterclaims and post-closure motions may not be reflected. Party names, attorney names and firm affiliations are reproduced as recorded and may contain omissions. Where a field is absent from the record, this page marks it as not recorded rather than inferring a value.

No characterisation of the parties or the outcome. This page reports what the record contains. Nothing here should be read as an assertion that any party infringed, that any patent is valid or invalid, that any settlement occurred, or that any party prevailed. The filing of a claim is not a court finding, and a docket marked “closed” does not by itself establish infringement, validity, settlement or a decision on the merits.

No FTO or validity opinion. Nothing on this page constitutes a freedom-to-operate, novelty, validity or infringement opinion. Any decision touching a live patent dispute should be verified independently and reviewed with qualified patent counsel.

Third-party names and marks. Party, attorney, judge and company names appear for identification only. Company names may be trademarks of their owners; their appearance does not, by itself, imply affiliation with or endorsement by Patsnap.

Corrections and privacy requests. To report an inaccurate record or attribution, use the “Report an incorrect record” link on this page. For requests concerning your personal information, including, where applicable, the rights to access, rectify, erase, restrict or object to processing, use the “Privacy request” link. We assess requests under applicable law. See our Privacy Policy for details of this processing.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.