Mock HIPAA Auditthe OCR examiner, before the exam

How the review scores your pack

The review is deterministic and runs in your browser. Each applicable requirement is marked mentioned, partly, planned, undecided or not evidenced, and the score is the unweighted count of mentioned rows over applicable rows. The same pack gives the same answer every time.

This page is the method. It is deterministic and it runs in your browser; no model writes anything while you wait. The same pack gives the same answer every time. Here is exactly what each status means and how the number is made.

What do the status words mean?

How does the addressable decision work (164.306(d)(3))?

Addressable does not mean optional. For each addressable specification the rule sets a three-branch decision: assess whether it is reasonable and appropriate; if yes, implement it; if no, document why and implement an equivalent alternative where reasonable and appropriate. A sentence in your pack that records that decision, beside the requirement it concerns, reads as mentioned. Nothing either way reads undecided, and the first question for that row is the assessment itself.

How is the score calculated?

The percentage is the count of mentioned rows over the applicable rows, with no weighting. It is a reading of your text, not a compliance score, and not a ruling that a requirement is met. A standard, a required specification and an addressable specification each count the same, which is why the page shows the per-requirement status and never the number alone.

Why are there sixty-seven requirements?

The set is the standards and implementation specifications of 45 CFR Part 164 Subpart C as read here: Administrative 32 (including 164.306, the general rules), Physical 12, Technical 12, Organizational 6, and Policies and documentation 5. The rule’s own numbering is inconsistent between sections, for example 164.308 holds a standard at (a)(1)(i) with its specifications at (a)(1)(ii)(A) to (D), while 164.310 holds a standard at (a)(1) with its specifications at (a)(2)(i) to (iv); we reproduce that rather than tidy it up. Where a requirement is a Standard rather than a specification it is labelled so.

What does the review not do?

It does not read your systems, interview your staff or verify that a stated control operates. It scores the text you paste. An assessor decides compliance. Applicability turns on your entity’s size, complexity, infrastructure and risk, in the rule’s own words; the review does not collect those, so it asks the entity-role and conditional questions and treats your answers as the scope.