Clustered 2 filings across 1 jurisdiction · filed Aug 31, 2018. View entity profile → Other incidents for this victim →
incident inc_b07515539a2a40c7 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Health (basic) · Identity (basic) · Financial account
CA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 9, 2018
When the intrusion reportedly occurred, per the linked filings
Aug 9, 2018
Reported by HHS OCR filing
California state AG breach notification (SB24) for Port City Operating Company (d/b/a St. Joseph's Medical Center). The filing is a sample notice; specific incident details, dates, and affected counts are not provided in the HTML page.
On August 9, 2018, St. Joseph's Medical Center (Port City Operating Company) discovered that hard drives from two old laboratory machine analyzers were missing during removal and replacement. The drives contained ePHI of approximately 4,984 individuals, including names, dates of birth, genders, account information, lab tests, test results, and ordering physicians. The CE and its BA searched facilities and interviewed staff but could not recover the drives. Breach notifications were sent to HHS, affected individuals, and media. The BA updated policies/procedures and retrained staff; OCR confirmed corrective actions. Breached info located on Other Portable Electronic Device.
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Affected (this filing): 4,984