Skip to main content
Patient Protect circular logo mark in purple and white used for site navigationPatient Protect
HIPAA ResponseBreach FilingVerified

Medtronic breach notification: device-manufacturer data flows and BAA scope

Medtronic notified state attorneys general of a breach. The Washington filing reports 64,035 state residents, while contemporaneous reporting put the incident near 3.8 million people. Where a device manufacturer holds patient data, the BAA language determines what the practice is entitled to know.

Source of record: State attorney general breach notificationJuly 3, 2026Last verified August 22, 2026

What the source establishes

Business associate relationships with medical technology vendors create a category of PHI exposure that sits entirely outside a practice's own perimeter controls. Patient data flows to device manufacturers for warranty registration, clinical support, and post-market surveillance — and once it leaves your systems, the security controls protecting it are the vendor's, not yours. The Medtronic breach, involving 3.8 million individuals whose personal and medical information was accessed by the ShinyHunters extortion group through corporate IT systems, illustrates exactly how a practice's compliance state can be compromised by a distant vendor's security failure.

The regulatory exposure is real: HIPAA holds covered entities responsible for ensuring their business associates protect PHI under the terms of a compliant BAA — and if that agreement lacks specific breach notification language, a vendor incident can become your notification problem before you even knew the vendor was breached.

What HIPAA requires here

§164.308(a)(1) — Risk Analysis and Risk Management — requires covered entities to assess risks to ePHI wherever it resides, including in vendor environments. §164.314(a)(1) — the Business Associate Contract standard — requires that every BA agreement specify the BA's obligations for safeguarding PHI, including breach notification timelines. §164.404 — the Breach Notification Rule — sets a 60-day discovery-to-notification clock that applies to covered entities and flows through BAAs to business associates. Gaps in any of these three provisions are what transform a vendor's security failure into a covered entity's regulatory exposure.

Patient Protect mapping

  • BAA Management tracks every business associate agreement in a centralized register, flags missing or expiring agreements, and surfaces BAAs that lack required breach-notification language — before a vendor incident forces a scramble.
  • Vendor & BAA Governance records which third parties hold PHI and whether each relationship has a current, executed agreement covering it.
  • Security Risk Assessment (SRA) extends your formal risk analysis beyond your own systems to account for vendor-held data, satisfying §164.308(a)(1) for the full scope of your PHI footprint.
  • Information Systems Inventory maintains an up-to-date map of every system and partner that receives, processes, or stores patient data — giving you the asset visibility required to know what's at risk when a vendor reports a breach.
  • Autonomous Compliance Engine Recalculates your compliance state from what the practice has recorded in Patient Protect, so new vendor relationships are added or existing agreements change, rather than treating vendor risk as a once-a-year checkbox.

Controls worth reviewing

  • Audit every device-vendor BAA in the near term — confirm breach-notification timelines are explicit, not vague, and that they meet the 60-day HIPAA requirement.
  • Inventory what PHI each device manufacturer holds — warranty records, device-enrollment data, and clinical-support logs all qualify; document the data categories in your risk analysis.
  • Update your Security Risk Assessment to include vendor-held PHI environments as in-scope assets, not external exclusions.
  • Establish an internal procedure for vendor breach notifications — define who receives the vendor's notice, who evaluates patient impact, and who decides whether a supplemental practice-level notification is required under your state's law.
  • Review data-sharing agreements for minimization language — confirm vendors are contractually limited to retaining only the PHI required for their defined function, and for no longer than necessary.

View underlying canonical breach event →

Sources

Source of record. Medtronic Inc. appears in the HHS OCR breach portal, reported June 29, 2026, with no individual count disclosed. Where this page and the OCR record disagree, the OCR record is correct. The filing does not publish root cause, whether data was exfiltrated, or which categories of PHI were involved; those remain unknown unless a source establishes them.

Secondary reporting. Security Week. Reporting can establish that something happened; it does not establish what was filed. Written with AI assistance under Patient Protect’s editorial standards.

Corrections & Updates

Healthcare security data changes as investigations progress, vendors update systems, and laws and guidance evolve. If you see something outdated, incomplete, or incorrect — or have newer source material — we’d appreciate hearing from you.

Submit a correction →