ARIZONAMalwareHealthcareHealthcareRansomwareData EncryptedCustomer Data InvolvedPHIHealth (basic)Identity (basic)MediumResolved

Good Health Medical

bd_47044efcf5b20f0d · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

May 17, 2021

To disclose

—

Affected

36,781

Confidence

68%

Full breach record for Good Health Medical →

Good Health Medical dba MY DR NOW reported to HHS on 2021-05-17 a Hacking/IT Incident affecting 36781 individuals. Breached information located on Network Server. The incident involved a ransomware attack affecting ePHI including names, dates of birth, and diagnoses.

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

May 17, 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.Confirmed36,781 affectedView incident

Name: Good Health Medical
norm: good health medical
Industry: Health Care Services

Name: Good Health Medical
norm: good health medical
Industry: Health Care Services
Also named: Good Health Medicaldba oflegal entity
MY DR NOWdba oftrade name
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 36,781nationwide
Data types: PHIHealth (basic)Identity (basic)
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: OCR investigation

During the incident: Notified HHS
Notified affected individuals
Notified the media
Changes made: Revised its HIPAA security procedures
Implemented additional technical safeguards to better protect its computer systems that maintain ePHI
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: May 17, 2021
Raw hash: 7c999ddd9b47c1cdaf63d3d4b8f5cc3bd39898438c6f8c33a20c7a13d2de845a

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 entityGood Health Medical

Victim entityGood Health Medical

IncidentUnauthorized Access

Stated responseNotified HHS

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing