MINNESOTAHackingHealthcareHealthcareBusiness Associate (HIPAA)Customer Data InvolvedHealth (basic)Identity (basic)Government IDHighResolved

Ramsey County

bd_678d536a726a9f63 · schema v1 · pii pii-v1

Severity

High

Discovered

—

Filed

Jan 29, 2021

To disclose

—

Affected

8,687

Confidence

75%

Full breach record for Ramsey County →2 incidents on file

County of Ramsey reported to HHS on 2021-01-29 a Hacking/IT Incident affecting 8,687 individuals. The breach occurred at a business associate and involved a cyber-attack on a network server. Information compromised included names, addresses, dates of birth, Social Security numbers, claims information, and treatment information.

J jump to incidentP pin to compareR raw source

HIPAA clock✓ HHS notified

⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

⚠ No discovery dateThe OCR public portal omits the discovery date, so the 60-day notification clock cannot be evaluated from this source — only that the filing was submitted.

Incident timeline — partial

? — ?

Breach window unknown

Jan 29, 2021

Filed

—

No filing yet · watching

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

Tracked as a single-filing incident — the only disclosure on record for this event so far.Confirmed8,687 affectedView incident

Name: Ramsey County
norm: ramsey county
Industry: Health Care Services

Name: Ramsey County
norm: ramsey county
Industry: Health Care Services
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 8,687nationwide
Data types: Health (basic)Identity (basic)Government ID
HHS breach type: Hacking / IT incident
Where the data lived: Network server
Covered-entity type: Healthcare providerBusiness associate involved
Attack vector: Unauthorized Access
Threat actor: Partner
Regulator citations: Notified HHS

Changes made: Strengthened its technical safeguards to better protect its ePHI
Terminated its relationship with the BA
Source: Quoted from the filing itself, not independently verified.

Compliance flags: HHS notified
Discovery-date grounding: no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.
Clock breakdown: Statute Window Elapsed Threshold Status
HIPAA
Discovered: not extracted
→ Notified: not extracted
— regulatory submission HHS notified

Statute	Window	Elapsed	Threshold	Status
HIPAA	Discovered: not extracted → Notified: not extracted	—	regulatory submission	HHS notified

Status: No extraction artifact recorded for this disclosure.

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://ocrportal.hhs.gov/ocr/breach/breach_report.jsf
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Jan 29, 2021
Raw hash: 41615893260efc1b630c9f448566b13e4fd5cf053fbd9bf2055b49989184a3c2

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html1.5 KB

Download View at source

Reporting entityRamsey County

Victim entityRamsey County

IncidentUnauthorized Access

Stated responseStrengthened its technical safeguards to better protect its ePHI

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing