Incident · 8-K Item 8.01
Quest Diagnostics data breach: patient records accessed through the Quanum LSM ordering system in October 2026
Published . Updated 2026-11-14. By the cisonews.net Desk.
Quest Diagnostics, the medical laboratory company, learned on October 21, 2026 that an unauthorized party had got into its Quanum Lab Services Manager (LSM) system and believes it accessed certain patient records. Quanum LSM is the system some of Quest's clients use to place test orders and to receive and look up results. The Associated Press describes Quest as a New Jersey-based medical laboratory operator. Quest disclosed the incident the next day, October 22, in a Form 8-K filed under Item 8.01. No count of affected patients has been published yet. Quest says it will notify the patients and providers it finds were affected and report to the regulators once its investigation is done.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
| Date | Event |
|---|---|
| October 21, 2026 | Quest learns of unauthorized access to Quanum LSM |
| October 22, 2026 | Form 8-K, Item 8.01, filed with the SEC |
| October 26, 2026, 8:00 a.m. ET | Quest's notice says the incident is remediated and Quanum LSM is restored |
| November 14, 2026 | No Quest notice yet on the California or Washington attorney general lists |
What happened in the Quest Diagnostics breach?
The 8-K says Quest started its incident response procedures to contain the activity and investigate its scope. It told federal law enforcement and brought in outside cybersecurity experts. The filing says the incident did not materially disrupt Quest's business or its ability to serve patients.
Quest's notice page fills in the next days. As of 8:00 a.m. Eastern on October 26, 2026, Quest says it had remediated the incident and securely restored Quanum LSM for clients. It says it ended the unauthorized access and contained the incident. Two other client systems, Essential Insights and LabHQ, were paused as a precaution. Quest says no data was accessed in them, and both have been restored. Providers who order through their own lab information system or electronic medical record interfaces were not affected.
The filing went in under Item 8.01, the item for other events, not Item 1.05, which a company uses for a cybersecurity incident it has judged material. The guide to Item 8.01 versus Item 1.05 explains the difference, and health data in 8-K cyber filings compares how other health companies have described the same kind of event. Two weeks later another laboratory company, Myriad Genetics, filed its own Item 8.01 report after detecting unauthorized access on November 2, 2026 (the Myriad Genetics entry).
What information was taken in the Quest breach?
Quest has not yet said which data fields were involved. Its patient FAQ says that, based on the investigation so far, personal information and patient records were affected. Asked directly whether protected health information (PHI) or personally identifiable information was part of the access, Quest answers yes and says it is still working out the specific data. It says the patient data was within Quanum LSM and that other systems were not affected.
How many people were affected?
That is not known yet. The Associated Press reported on October 22 that how many patients and which records were affected was still unknown. When this page was checked on November 14, 2026, neither the California attorney general's list nor the Washington attorney general's list carried a Quest Diagnostics notice. This entry will add the count when a regulator records it.
When will Quest notify patients?
Quest calls itself the covered entity and says it will make notifications as required by law. The HIPAA rule requires a covered entity to notify each affected person without unreasonable delay and no later than 60 calendar days after it discovers a breach. If October 21, 2026, the day Quest learned of the access, is also the day the breach counts as discovered, 60 calendar days runs to December 20, 2026. The HIPAA Breach Notification Rule entry explains the clock and the HHS report. Quest says the letters will describe the help on offer, including credit and identity monitoring. What healthcare data breach letters tell patients shows what such letters usually contain.
Is the Quest breach related to the PHP vulnerabilities?
No, according to Quest. Its notice says the incident is not related to a PHP programming language issue. The AP reported the same answer from Quest on October 22. Quest's FAQ puts the question that way because federal officials had been urging firms that use PHP to make urgent security updates.
What should Quest patients and providers do now?
Quest warns that phishing and voice-phishing attempts can follow an incident. It asks patients and providers to check any message about lab services or Quest, including breach-notification, credit-monitoring or settlement scams. Providers who need their Quanum LSM credentials reset are told to call the IT Connectivity Help Desk at 1-800-697-9302. Results for orders placed through Quanum eLabs are also available in Quanum LSM.
Has Quest Diagnostics had a data breach before?
Yes. In June 2019, Quest said that American Medical Collection Agency (AMCA), a billing collections provider working for its contractor Optum360, had reported unauthorized access to AMCA's system. AMCA told Quest the affected system held information on approximately 11.9 million Quest patients, but not laboratory test results. The AP also recalls a 2016 breach that exposed lab results and contact details of about 34,000 people. The 2026 incident is different from both: by Quest's account it involved Quest's own Quanum LSM system, not a vendor's. The largest healthcare data breaches of 2026 reported to HHS will show where this one ranks once Quest files its HHS report.
How this disclosure's timing compares
Quest Diagnostics Incorporated disclosed 1 day after the discovery date its filing gives. Across the 21 other filings under 8-K Item 8.01 on cisonews.net that date discovery to the day, the median gap is 3 days.
The rule behind an Item 8.01 filing
Item 8.01 (Other Events) is the item the SEC's Division of Corporation Finance encouraged companies to use for a cybersecurity incident they have not yet determined to be material, or have determined is not material. Its May 21, 2024 statement says a company that later determines the incident is material should file under Item 1.05 within four business days of that decision. Source: U.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance. The guide Item 8.01 versus Item 1.05: when a cyber incident moves between them reads the rule in full, and the glossary defines Form 8-K Item 1.05.
Other health care incidents on cisonews.net
- MPOWERHealth Holdings LLC, Breach notice, first disclosed November 13, 2026
- Acadia Healthcare Company, Inc., Breach notice, first disclosed November 13, 2026
- Telecare Health, Breach notice, first disclosed November 9, 2026
- Sharecare Health Data Services, LLC, Breach notice, first disclosed November 6, 2026
- Nephrology Associates, P.C., Breach notice, first disclosed November 6, 2026
Sources
- 2026-10-22 · AQuest Diagnostics Incorporated, Form 8-K, Item 8.01 (SEC EDGAR), published October 22, 2026
- 2026-10-26 · AQuest Diagnostics, An update on an incident involving one of our systems (notice and FAQs, as of October 26, 2026), published October 26, 2026
- 2026-10-22 · BThe Associated Press (via FOX10 News), Quest Diagnostics reports 'unauthorized access' to its Quanum Lab Services Manager, published October 22, 2026
- 2019-06-03 · AQuest Diagnostics, Statement on the AMCA Data Security Incident, published June 3, 2019
- 2026-11-14 · AeCFR, 45 CFR Part 164, Subpart D (HIPAA notification in the case of breach of unsecured protected health information), published November 14, 2026
- 2026-11-14 · ACalifornia Attorney General, data security breach list (checked November 14, 2026), published November 14, 2026
- 2026-11-14 · AWashington State Attorney General, data breach notifications (checked November 14, 2026), published November 14, 2026
- 2024-05-21 · AU.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance, published May 21, 2024
Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.