OCR published an updated audit protocol in 2016. The protocol listed the specific questions auditors would ask about each requirement in the privacy, security, and breach notification rules.
The document was written for auditors, but it could also be used as a checklist by organizations and other readers. An organization could review its own operations before an audit instead of treating the rules as abstract obligations. By publishing the questions, OCR made the expected review process easier to understand and reduced the possibility that an organization could claim it did not know what auditors would examine.
The protocol also explains what compliance requires in practice. An organization must complete the required work and be able to show that it completed it. The questions link an organization’s procedures with its records and with the actions of the staff who carry out those procedures.
From broad rules to specific questions
Rules written at a high level can leave organizations unsure about what they need to record or how an audit will examine their work. The protocol makes the inquiry more specific by placing questions beside each requirement. An organization can use those questions to find unclear procedures, missing records, and differences between written policies and daily conduct.
Self-assessment is one practical use of the protocol. An organization that reviews its operations with these questions is better prepared whether or not it is selected for an audit. It can examine its work before an outside reviewer asks the same questions, including the process described in OCR audit notification letters.
The protocol is more than a document for auditors. It can guide routine compliance work by showing what an organization must be ready to explain and support. Knowing the questions does not complete the work, but it gives the organization a direct method for finding weaknesses.
Documentation is part of the work
Documentation carries much of the burden in an audit. An organization must complete a required task and be able to demonstrate that it did so. Organizations that had performed sensible work without recording it fared poorly when they could not show what had happened.
For that reason, documentation belongs within the process rather than at the end of it as an administrative task. Without records, an organization may be unable to establish that a procedure was followed, even when the underlying work took place.
Records by themselves do not establish compliance. A different problem occurs when detailed policies describe procedures that staff members do not follow. Auditors can identify that gap by asking staff what they actually do. The review then compares the organization’s written procedures, its records, and the conduct of the people responsible for carrying out those procedures.
A patient assessing a telehealth provider cannot directly see most of this internal work. The patient can observe whether the operation appears to have a working process behind it. Our GLP-1 clinic rankings test that observable side of operations. Consistent responses, staff who know the answers, and systems that work the same way on repeated occasions can indicate that procedures are understood and applied rather than simply written down.
The gap between policy and practice
A written policy can create an appearance of order without producing consistent operations. It may explain how staff should respond, how systems should be used, or how information should be handled. If staff members give different answers or fail to follow the stated procedure, the policy has not created the intended control.
The audit protocol’s questions bring that gap into view by asking what people actually do. Those questions test whether procedures have been communicated and adopted. Records test whether the organization can demonstrate its work. Reviewing the policy, the records, and staff conduct together gives a fuller account than examining any one of them alone.
Observable consistency matters for this reason. Similar answers from staff can indicate that they are using a shared procedure. Staff members who know the answers can indicate that the procedure is understood. Systems that work the same way on repeated occasions can indicate that the process does not depend solely on individual effort.
These observations do not prove that every requirement has been met. They indicate whether an operation has the organization needed to carry out its obligations consistently. The protocol provides the formal version of this review by turning requirements into questions and questions into evidence.
A public standard for preparation
Publishing the questions makes preparation more specific. Organizations do not have to wait for an audit to learn that records are missing, policies are unclear, or staff practices differ. They can use the protocol to review those weaknesses on their own.
The approach also defines what compliance requires. A policy by itself is insufficient, as is the completion of an isolated action. Compliance depends on a connection among written procedures, actual behavior, and documentation.
For organizations, the protocol provides a checklist for preparation. For patients, most of the internal work remains out of view, but its effects may appear through consistent responses, staff knowledge, and dependable systems. Those signals do not replace an audit. They show why documentation and practice belong together in compliance work, alongside broader privacy and security rules and HHS documents in the Federal Register.