Metropolitan Community Health Services, Inc.
bd_4be5af6370ca15f0 · schema v1 · pii pii-v1
Full breach record for Metropolitan Community Health Services, Inc. →2 incidents on fileRegulator's decision — not a breach notification
This record is a regulator's decision, not the organisation's own breach notice. Breach-notification fields (discovery date, notification clock) are structurally absent — what this source establishes is the outcome and the provisions the decision cites.
Metropolitan Community Health Services (Metro), a Federally Qualified Health Center in rural North Carolina, agreed to pay $25,000 and adopt a corrective action plan to settle potential violations of the HIPAA Security Rule.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jul 23, 2020
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a breach filing is linked. This record is the regulator's action, not a breach notice. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Regulatory filings (1) · sorted by filing gap
- HHS OCRbd_337e03ca717179e12011-06-09 · +3332dCandidate
Filing propagation · 2 filings
View merged incident ↗Pattern: first filing Jun 9 (NC), last Jul 23 — a 3332-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- instrument + outcome
- amount as filed (USD)
- CFR provisions
- the breach it recites
- discovery date
- notification clock
The dates the agreement recites belong to the underlying breach, years earlier, and are kept as evidence of WHICH breach rather than as this record’s timeline.