Central Texas Pediatric Orthopedics
ent_bcf3f1d483905b62a2a8cbdf
Disclosures
4
State AG · HHS OCR · 4 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
140,121
nationwide · State AG IN
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Central Texas Pediatric Orthopedics
- Normalized
- central texas pediatric orthopedics— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (4)newest first
- 🦞Maine State AGas victim2025-04-14
Central Texas Pediatric Orthopedics reported a data breach impacting 9 Maine residents. The breach, which occurred between January 23, 2025, and January 26, 2025, was discovered on February 4, 2025. The incident was described as an external system breach (hacking). Affected individuals were notified on April 11, 2025.
- 🏎️Indiana State AGas victim2025-04-11
Central Texas Pediatric Orthopedics reported a data breach to the Indiana Attorney General. The breach occurred on 2025-01-23 and was reported on 2025-04-11. 32 Indiana residents were affected. 140,121 individuals affected in total.
- 🍁Vermont State AGas victim2025-04-11
Central Texas Pediatric Orthopedics notified patients of a security incident where an unauthorized actor accessed systems from Jan 23-26, 2025. Affected data included minors' names, dates of birth, and x-ray images. The company engaged forensic investigators, notified the FBI, and implemented security enhancements including EDR and password resets.
- TEXASHHS OCRas victim2025-04-04
Central Texas Pediatric Orthopedics (TX) reported to HHS OCR on 2025-04-04 a ransomware attack affecting 140,000 individuals. PHI located on a Network Server was compromised, including names, dates of birth, x-ray images, and other treatment information. The entity is a pediatric orthopedics provider, so affected records likely involve minors. The CE notified HHS, affected individuals, and the media, posted substitute notice, and responded by revising security policies and implementing new technical safeguards.