Quest Diagnostics (Quanum LSM)
Patient health information and patient-identifiable information are not synonyms, and the distinction is the entire story.
What happened?
Quest Diagnostics learned on 21 October 2026 that a threat actor had gained unauthorised access to its Quanum LSM system. The company deployed its incident response protocol to contain the activity and began assessing the nature and scope of the incident.
Quanum LSM is the system certain clients use to place test orders and to receive and look up results. Quest states the incident did not disrupt customer facing operations, and that users of direct customer LIS interfaces or EMRs were not impacted. External experts are supporting the investigation and law enforcement has been informed.
What data was actually inside?
Quest says an unauthorised party accessed certain patient records, and describes the content as patient health information and patient-identifiable information. The specific data types have not yet been determined.
Those two phrases are doing separate jobs and the separation is deliberate. Patient-identifiable information covers the fields that tie a record to a person, a name or a contact detail. Patient health information points at clinical content, which in a laboratory ordering system means the test that was ordered and the result that came back.
A test order is a diagnosis in draft. Nobody orders an HIV panel, a BRCA screen or a toxicology series at random, so the order alone discloses clinical suspicion before any result is attached. That is why the phrasing matters more than the record count that has not arrived yet.
Who gets hurt and how?
Patients of clients who used Quanum LSM, which is a population that never selected the system and in most cases has never heard its name. The relationship the patient formed was with a physician.
The harm model is disclosure first and fraud second. A laboratory record describes something true and permanent about a person's health, and unlike a card number it cannot be reissued. Medical identity theft follows if identifiers travelled alongside, and it is materially harder to unwind than financial fraud because the corrupted record lives in clinical systems where it can affect future treatment.
What did they think they were doing right?
Segmentation worked, and Quest said so precisely. Direct customer LIS interfaces and EMR integrations were not impacted, which indicates the ordering portal was architecturally separated from the integration paths. That is a real control producing a real limitation on blast radius.
The containment was also fast by the standards of this series. What the architecture did not do was reduce the sensitivity of what the portal itself held, because the ordering portal is where the clinical intent is expressed.
What did they not know about their own data?
The disclosure says the types of data affected have yet to be determined. That sentence is the inventory gap stated plainly, and it is not a criticism of Quest so much as a description of how nearly every organisation in this series has stood on day one.
Knowing that the Quanum portal was accessed is a question about systems and it was answered immediately. Knowing which test types, which results and which identifiers were in the accessed records is a question about content, and it requires somebody to examine the data itself.
Quest is a large and well resourced operator with a mature incident response function, and it still had to say that the data types were undetermined on the day it disclosed. That is the clearest demonstration available that this gap is structural rather than a failure of effort. The Ampath Laboratories entry in this series records the same gap in the same industry a week earlier.
If your environment was compromised today, could you say within 24 hours exactly what sensitive data was accessed?
Not sure where to start? How to find sensitive data across your estate
What does attribution look like the morning after?
No threat actor has been named. Quest has informed law enforcement and engaged external experts.
HIPAA requires notification to affected individuals without unreasonable delay and no later than 60 days from discovery, with notice to HHS and, above 500 residents in a state, to prominent media in that state. The 60 day clock started on 21 October. Everything inside that window is attribution work: reviewing accessed records, determining which patients they belong to, and resolving which of the many ordering clients each patient relates to, since the patient's relationship is with the physician rather than with Quest.
What would have changed the outcome?
A standing map of which fields in the ordering portal constitute clinical content as distinct from contact content. Both were in the same records, and the notification obligations turn on being able to separate them.
Second, shortening the determination. The interval between knowing a system was accessed and knowing what was in it is the interval in which patients are unaware, regulators are waiting and the organisation can say very little. It closes only for the organisation that already described its own data before anyone asked.
Quest Diagnostics (Quanum LSM) found out the hard way.
Your team could spend the next 6 months rebuilding systems, notifying customers, and answering legal questions. Or you could spend 24 hours finding out what's actually at risk.
Want to understand the process first? Read our guide to sensitive data discovery .