whogothacked

Community Health Plan of Washington data breach record

Is there a breach on record for Community Health Plan of Washington?

Yes. There is one breach incident on record for Community Health Plan of Washington, first reported on December 21, 2016.

Reported to the Washington Attorney General and the HHS Office for Civil Rights.

How many
381,504 individuals, per the HHS Office for Civil Rights, the largest of three figures on record. The figures come from separate filings that do not say whether they count the same people, so they are not added together.
Data listed
Names; social security numbers; health insurance policy or id numbers.
Source record
Open this record at atg.wa.gov
What to do
Consider a credit freeze; review medical and insurance statements. If you received a notice letter, start with the letter.

Get a daily email of new incidents

Email alerts

We use your address only for these alerts and to run and test the service (privacy). Want only SEC filings? Sign up on the alerts page.

Sector
Health
State
Washington

Was Community Health Plan of Washington hacked?

The record gives a cause, in the source's own words. For the incident first reported on December 21, 2016, the record from the HHS Office for Civil Rights gives the cause as “Hacking/IT Incident (location of breached information: Network Server, Other)”.

The HHS Office for Civil Rights describes what happened in its own words. That description is quoted with the incident below.

A filing shows who notified the regulator. The filer is sometimes a vendor or a customer of the firm whose systems were affected, so a filing on its own does not establish whose systems were broken into.

The incident on record

First reported

Official record

3 source records

Community Health Plan of Washington reported a data breach to the US Department of Health and Human Services Office for Civil Rights and the Washington Attorney General. The first of 3 notices was filed on December 21, 2016 and the latest on January 3, 2017. The filings give January 16, 2016 as the date of the breach. The Washington filing says the organization became aware of it on November 30, 2016. The HHS filings put the number of individuals affected at 381,504 and 1,375, in separate notices. The Washington filing puts the number of Washington residents affected at 353,388. These figures count different groups and are not added together. The HHS filing lists the type of breach as "Hacking/IT Incident (location of breached information: Network Server, Other)". The Washington filing lists the cause as "Unauthorized Access". The HHS filing lists the type of breach as "Hacking/IT Incident (location of breached information: Network Server)". The Washington filing lists the information involved as: names, social security numbers, health insurance policy or id numbers.

Breach dated
January 16, 2016
Discovered
November 30, 2016
Latest filing
January 3, 2017

Figures on record

  • 381,504individualsper the HHS Office for Civil Rights
  • 353,388Washington residentsper the Washington Attorney General
  • 1,375individualsper the HHS Office for Civil Rights

The figures come from separate filings that do not say whether they count the same people, so they are not added together.

Cause on record

Listed by HHS as “Hacking/IT Incident”. Unauthorized access.

Data exposed, as the sources list it

  • names
  • social security numbers
  • health insurance policy or id numbers

The records behind this entry

  1. First record

    Listed on the HHS Office for Civil Rights breach portal under the name Community Health Plan of Washington.

    On this record: 381,504 individuals; cause given as “Hacking/IT Incident (location of breached information: Network Server, Other)”.

    In the words of the HHS Office for Civil Rights

    Transactions Application Group, Inc., a business associate (BA) for the covered entity (CE), Community Health Plan of Washington, failed to properly secure a port on a computer network server used for transferring electronic files (a File Transfer Protocol (FTP) server), resulting in an incident of unauthorized access to electronic protected health information (ePHI) maintained at the BA.

    Show the rest of this text (69 more words)Hide the rest of this text

    The breach affected 381,504 individuals and included individuals’ names, addresses, dates of birth, social security numbers, and certain coding information related to health care claims. The CE provided breach notification to the affected parties, the media, and HHS, and offered one year of free credit and identity theft monitoring. The CE also implemented additional technical safeguards. OCR obtained assurances that the CE implemented the corrective actions listed above .

    • Open the HHS list of HIPAA breach reports at ocrportal.hhs.govThe HHS breach portal has no page for each report. On its list, look for “Community Health Plan of Washington” (WA) with the breach submission date 12/21/2016. Reports older than 24 months are on its Archive tab. Show Advanced Options can search the list by name (CE / BA Name Search) and by submission date.
  2. Update

    Breach notice filed with the Washington Attorney General under the name Community Health Plan of Washington.

    On this record: 353,388 Washington residents; cause given as “Unauthorized Access”; breach dated Jan 16, 2016; discovered Nov 30, 2016.

    This record lists these kinds of data: names; social security numbers; health insurance policy or id numbers.

  3. Update

    Listed on the HHS Office for Civil Rights breach portal under the name Community Health Plan of Washington.

    On this record: 1,375 individuals; cause given as “Hacking/IT Incident (location of breached information: Network Server)”.

    In the words of the HHS Office for Civil Rights

    On January 3, 2017, the covered entity (CE) reported that on November 3, 2016, Summit Reinsurance, a business associate (BA), indicated it discovered ransomware on one of its computer servers. The breach affected approximately 1,375 individuals’ protected health information (PHI) and included patients’ names, addresses, dates of birth, provider names, and health insurance claim information.

    Show the rest of this text (52 more words)Hide the rest of this text

    The CE provided breach notification to HHS, affected individuals, and the media, and also provided free credit monitoring. The CE revised its policies and procedures related to the nature of the breach. OCR provided substantial technical assistance to the CE and obtained assurances that the CE implemented the corrective actions noted above.

    • Open the HHS list of HIPAA breach reports at ocrportal.hhs.govThe HHS breach portal has no page for each report. On its list, look for “Community Health Plan of Washington” (WA) with the breach submission date 01/03/2017. Reports older than 24 months are on its Archive tab. Show Advanced Options can search the list by name (CE / BA Name Search) and by submission date.

What to do if this involved you

  • Consider a credit freeze

    A freeze stops new credit being opened in your name. It is free, and you place it yourself with each of the three US credit bureaus: Equifax, Experian and TransUnion. You can check your credit reports for free as well.

    Free credit reports at AnnualCreditReport.com

  • Review medical and insurance statements

    Check statements from your insurer and providers for care you did not receive, and tell your insurer about anything that is not yours.

These steps follow from the kinds of data the sources list. If you have a notice letter, start with the letter.

If you received a notice letter

  • Keep the letter

    It names the incident and lists which of your details were involved. The letter, not this page, is the authority on what happened to your data.

  • Use any free monitoring it offers

    Many notices include free credit monitoring with an enrollment code and a deadline. Enroll using the instructions printed in the letter, not a link from an email or text.

  • Check that the letter is real

    Compare it with the source records linked on this page. If you are unsure, contact the organization using a phone number or address from its own website, not one printed in a message you were sent.

  • If your identity is misused, report it

    The Federal Trade Commission's IdentityTheft.gov gives you a recovery plan and the forms to send.

    Report identity theft at IdentityTheft.gov

About this record

Official record: A regulator filing or the organization's own disclosure exists.

Being on record here is not a finding that Community Health Plan of Washington did anything wrong or broke any law. This page reports what the source records say, and no more.

Every fact on this page comes from the source records linked above. The steps for people who received a letter are general guidance, not part of the record. How records are verified

Something wrong here? See how to dispute an entry, or write to corrections@whogothacked.com.

The same record for software: /api/v1/orgs/community-health-plan-of-washington