LifeBridge Health Data Breach Exposes Personal Information: Lynch Carpenter Investigates Claims
PITTSBURGH, Oct. 23, 2025 (GLOBE NEWSWIRE) -- LifeBridge Health (“LifeBridge”), a health care provider with nearly 150 locations in and around Baltimore, Maryland,1 recently announced a cybersecurity incident in which an unauthorized user accessed data from LifeBridge’s third-party electronic health records (“EHR”) vendor. This security incident impacted the personally identifiable information (“PII”) and protected health information (“PHI”) of an unknown number of LifeBridge patients. The information compromised in the incident includes the following:
- names
- Social Security numbers
- information included within patient medical records such as:
- medical record numbers
- doctors
- diagnoses
- medicines
- test results
- images
- care and treatment.
Lynch Carpenter, LLP is investigating claims against LifeBridge related to this data breach. If you received a data breach notification from LifeBridge, you may be entitled to compensation. For an attorney to review your case, please fill out THIS FORM.
About Lynch Carpenter
Lynch Carpenter is a national class action law firm with offices in Pennsylvania, California, and Illinois. Our firm has represented millions of clients in data privacy matters for more than a decade and has earned national acclaim for complex litigation for plaintiffs across the country. To learn more, please visit www.lynchcarpenter.com.
For more information, please call Jerry Wells at (412) 322-9243, or email him at jerry@lcllp.com.
|
CONTACT Jerry Wells COMPANY Lynch Carpenter LLP PHONE (412) 322-9243 EMAIL jerry@lcllp.com WEB lynchcarpenter.com |
1 https://www.lifebridgehealth.org/about
Legal Disclaimer:
EIN Presswire provides this news content "as is" without warranty of any kind. We do not accept any responsibility or liability for the accuracy, content, images, videos, licenses, completeness, legality, or reliability of the information contained in this article. If you have any complaints or copyright issues related to this article, kindly contact the author above.