Federal law, reflected in HHS documents in the Federal Register, requires covered entities to notify the Office for Civil Rights when unsecured protected health information is breached. Breaches affecting 500 or more people are also posted to a public database. That database has long been known informally as the “wall of shame,” a term discussed in Data Breach Wall of Shame: 2013’s Highlights and Lessons.

The database provides patients and compliance officers with a way to review reported incidents involving organizations that handle protected health information. Its usefulness depends partly on whether people can read each record, narrow the results, and understand what the entries show.

Turning a raw log into a usable record

A public list supports accountability when people can interpret it. A long breach record is difficult to review without tools that separate incidents by relevant details. Filters for state and entity type let users focus on the organizations or categories they are examining.

A breach-cause filter adds context. Another option indicates whether a case remains under investigation, so users can tell an open matter from one that has closed. These categories do not provide every detail about an incident, but they make the public record easier to assess.

Sorting the entries by cause can reveal repeated patterns in reported incidents. The source notes describe routine problems, including a lost laptop, a misdirected mailing, and a phished email account. These examples show that protected health information can be exposed through ordinary handling errors. The cause does not have to be a sophisticated technical event.

The filters and sorting tools make the log more useful for specific questions. A compliance officer can review reported causes among similar entities. A patient can check whether an organization appears in the database, identify the stated cause, and see whether the matter remains under investigation.

Why public posting changes incentives

A public listing does more than inform people about an incident. An organization’s name remains in a searchable record after the case closes. That continuing visibility can affect how seriously organizations address privacy safeguards before a breach occurs.

The source notes connect this incentive to encryption. Encryption concerns the protection of stored or transmitted data. Vendor oversight concerns companies that may handle information as part of a service. Access logging concerns the ability to track activity within a system. A public breach record cannot show how an organization managed each area, but it makes a reported incident harder to disregard.

The database is not a complete ranking of organizations. Each entry records a reported breach and its status. It does not provide a full account of an organization’s privacy practices or explain every operational detail. The record is useful for identifying questions that require closer review.

Applying the information to online care

Privacy expectations continue to apply when patients use telehealth under Medicare coverage guidance. A weight loss consultation, lab results, and payment details may pass through the same platform. Before giving that information to an online prescriber, a patient can review FDA information about drugs and check whether the public breach record contains relevant information.

The portal is one part of that review. A patient can examine the organization linked to an incident, read the reported cause, and check whether the case remains under investigation. The entry may also make clear that an online service involves an operation whose structure deserves review, rather than only the individual prescriber.

Modern medication costs may direct attention to price. Our GLP-1 clinic rankings consider privacy structure alongside price and prescribing practices. That comparison does not replace the breach database. It places the database within a wider review of how an online service operates.

A practical way to read the portal

Start with the state and entity-type filters that match the organization or category under review. Read the reported cause and check whether the case remains under investigation. When several records appear, sort them by cause. This can show whether the entries involve lost equipment, misdirected communications, phishing, or another reported problem.

The results are information for further evaluation, not a single answer about whether to use a service. One listing identifies a reported incident, but it does not answer every question about the organization’s practices. The stated status and cause provide context while leaving other parts of the operation open for review.

The same record can have different uses for different readers. A patient can use it to understand the public history associated with an online service. A compliance officer can review reported patterns by entity type, state, cause, or investigation status. For both groups, the portal is most useful when its limits are clear.

A searchable breach record makes privacy review more practical by giving the public a way to examine reported incidents after they occur. The lasting record also draws attention to encryption, vendor oversight, and access logging before an incident occurs.