NEW JERSEYHackingHealthcareHealthcarePhishingBusiness Associate (HIPAA)Customer Data InvolvedPHIHealth (basic)Identity (basic)Government IDHighContained

Jersey City Medical Center

bd_5195e9242e710494 · schema v1 · pii pii-v1

Severity

High

Discovered

—

Filed

Feb 15, 2022

To disclose

—

Affected

1,130

Confidence

69%

Full breach record for Jersey City Medical Center →4 incidents on file

Jersey City Medical Center reported to HHS on 2022-02-15 a Hacking/IT Incident affecting 1130 individuals. Breached information located on Email. A business associate employee was victim of an email phishing scheme compromising PHI including names, DOBs, and SSNs. The CE implemented additional administrative and technical safeguards.

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

Feb 15, 2022

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.Confirmed1,130 affectedView incident

Name: Jersey City Medical Center
norm: jersey city medical center
Industry: Health Care Services

Name: Jersey City Medical Center
norm: jersey city medical center
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 1,130nationwide
Data types: PHIHealth (basic)Identity (basic)Government ID
HHS breach type: Hacking / IT incident
Where the data lived: Email
Covered-entity type: Healthcare providerBusiness associate involved
Attack vector: Unauthorized Access
MITRE ATT&CK: T1566.002 Spearphishing Link
Threat actor: External
Regulator citations: Notified HHS
Initial access: phishing_link

During the incident: Notified HHS
Notified affected individuals
Notified the media
Changes made: Implemented additional administrative and technical safeguards
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: Feb 15, 2022
Raw hash: 34fa161cf90cdcb532d5b918fac266a7e2b22dbf96ed50d2533427af7d5cb420

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 entityJersey City Medical Center

Victim entityJersey City Medical Center

IncidentUnauthorized Access

Stated responseNotified HHS

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing