A $5.5 million HIPAA settlement turned on a basic security question: who had accessed which records? The organization could not answer that question adequately, and improper access continued without detection. The issue was not limited to whether unauthorized people could enter a system. The organization also needed to know what happened after someone was already inside.

That distinction makes audit controls one of the less visible parts of the security rule. Access controls determine who may enter a system. Audit controls record what users do after they enter. Without both functions, an organization may restrict entry yet remain unable to determine what occurred during authorized access.

Access is not the same as accountability

Access control asks whether a person can enter the system. Audit control asks what that person did after entering. The second question matters because a person with authorized access can still misuse it.

If a system does not record user activity, the organization may have no practical way to separate ordinary use from improper activity. A login record can show that a user was permitted to access a platform, but it may not show which records the user viewed. Audit controls create a record that the organization can examine later.

That record supports an investigation when someone with system access may have misused it. It can link a user to specific activity and help establish which records were involved. Without such a record, an organization may know that access was possible while still being unable to determine what took place.

Audit controls are more than a technical feature added to an access system. They allow an organization to supervise people who already have permission to use that system. Deciding who may enter is only the first step. The organization also needs a way to determine who looked at records and which records they accessed.

The cost of not knowing

After an incident, an organization needs to answer a basic question: what was actually accessed? Without adequate logs, it may not be able to answer. That uncertainty can lead to broader notification than the known facts require because the organization cannot exclude possible access.

The problem continues after notification. Incomplete records leave investigators with fewer facts. The organization may be unable to determine the extent of improper access or reconstruct the activity connected to the incident. It may know that someone used the system without knowing what that person did.

This explains why audit controls matter even when access controls appear strong. A system can restrict entry while leaving the organization unable to determine what authorized users did after they entered. When the records are missing or incomplete, a specific question becomes an unresolved one.

For telehealth users, this issue sits alongside other practical considerations. Someone comparing modern medication costs can review a comparison of telehealth clinic organizations while also considering whether the provider appears able to manage the systems behind its website. A public page cannot usually reveal every technical control. The question is whether the organization shows signs that it has the capacity to operate those systems.

The capability gap

Effective audit logging requires systems that produce useful records and staff who review those records. Logs that no one reviews may fail to reveal improper access soon enough. Staff also cannot assess user activity properly when the system does not capture sufficient information.

Small organizations often lack both the systems and the staff. That gap helps explain why breach findings cluster there. This does not mean that every small organization is insecure, and size alone does not determine performance. Audit controls require operating capacity as well as a stated commitment to security.

Telehealth includes organizations with very different levels of technical and operational capacity. A platform that runs on well-configured infrastructure and has a security function differs substantially from a small team that relies on consumer tools. A website may not reveal those differences. A polished interface does not show how the organization records access, who reviews the records, or whether staff can investigate an incident.

The same limitation applies in the other direction. A smaller organization may follow sound practices that are not apparent from its public presentation. Consumers generally cannot inspect technical controls themselves, so public signals should be treated as indicators, not proof.

The practical signals available

The useful proxies are organizational. Verifiable corporate details can show that a provider is identifiable. Staffed support can give patients a way to raise problems. Identifiable clinical leadership can clarify who has responsibility for the care operation.

These signals do not replace evidence of audit logging. They can indicate whether a telehealth organization appears to have the structure needed to manage sensitive systems. They may also help distinguish a provider with an operating organization behind it from a service whose public presence provides little information about who runs it.

That is why our GLP-1 clinic rankings weigh these factors. The purpose is not to infer technical compliance from branding. It is to account for capabilities that patients cannot inspect directly, such as the ability to record access, review those records, and determine what happened when something goes wrong.

The settlement illustrates the central point. Access controls determine who can enter. Audit controls help determine what happened after entry. Without the second function, improper access may continue without detection, and the organization may be unable to establish the scope of an incident.