ARIZONAMalwareHealthcareHealthcareRansomwareData EncryptedCustomer Data InvolvedRansom DemandedPHIHealth (basic)Identity (basic)Government IDHighResolved

Francisco Jaume, D.O.

bd_549812b62c02e028 · schema v1 · pii pii-v1

Severity

High

Discovered

Aug 22, 2016

Filed

Oct 4, 2016

To disclose

6 weeks

Affected

14,236

Linked

3 filings

Confidence

66%

Full breach record for Francisco Jaume, D.O. →

Francisco Jaume, D.O. reported to HHS on 2016-10-04 a Hacking/IT Incident affecting 14,236 individuals. Breached information located on Network Server. The incident involved a ransomware attack starting August 22, 2016, exposing PHI including names, addresses, medical info, and SSNs.

J jump to incidentP pin to compareR raw source

HIPAA clock✓ HHS report on time6 weeks discovery → filing

⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Incident timeline

discovery → filing · 6 weeks / 43 days

Aug 22, 2016

Begins

Aug 22, 2016

Discovered

Oct 4, 2016

Filed

vs. sector median

6 wks faster

This filing is one of 3 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Massachusetts State AGbd_5e3f58c220791a9c2016-10-04Verified
Montana State AGbd_f5be6224ede003d22016-10-03 · +1dVerified

Name: Francisco Jaume, D.O.
norm: francisco jaume do
Industry: Health Care Services

Name: Francisco Jaume, D.O.
norm: francisco jaume do
Industry: Healthcaresource default

Discovered: Aug 22, 2016
Breach occurred: Aug 22, 2016
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 14,236nationwide
Data types: PHIHealth (basic)Identity (basic)Government ID
HHS breach type: Hacking / IT incident
Where the data lived: Network server
Covered-entity type: Healthcare provider
Attack vector: Unauthorized Access
MITRE ATT&CK: T1486 Data Encrypted for Impact
Threat actor: ExternalFinancial
Regulator citations: Notified HHSOCR investigation conductedOCR obtained assurances of corrective actions

During the incident: Worked to regain control of its data
Investigated the incident using forensic analysis
Changes made: Implemented regular remote monitoring and monthly reporting of intrusion activity
Implemented anti-virus management
Changed/strengthened system passwords
Revised backup processes
Trained staff
Revised HIPAA policies and procedures
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 6 weeks(43 days from discovery to filing)
Compliance flags: HHS report on timeHHS notified
Discovery-date grounding: occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
Clock breakdown: Statute Window Elapsed Threshold Status
HIPAA
Discovered: Aug 22, 2016
→ Notified: not extracted
— 60 days HHS report on time
HIPAA
Discovered: Aug 22, 2016
→ Notified: not extracted
— regulatory submission HHS notified

Statute	Window	Elapsed	Threshold	Status
HIPAA	Discovered: Aug 22, 2016 → Notified: not extracted	—	60 days	HHS report on time
HIPAA	Discovered: Aug 22, 2016 → Notified: not extracted	—	regulatory submission	HHS notified

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Montana State AGOct 3 · first

Massachusetts State AG+1d

HHS OCR+1d · this page

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: Oct 4, 2016
Raw hash: 1fa906bfa1d0c2351bba8b48d43a0f5fb948b76dff71c9afb2ee8079419d632d

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.9 KB

Download View at source

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityFrancisco Jaume, D.O.

Victim entityFrancisco Jaume, D.O.

Incidentdiscovered Aug 22, 2016

Stated responseWorked to regain control of its data

ComplianceHHS report on time

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing