HIPAA Compliance Checklist for Dental Offices (2026): Owners and Proof
The renewal form from your cyber insurer asks for the date of your last risk analysis. An attorney reviewing a possible sale of the practice asks for your Business Associate Agreements. Someone in the morning huddle says "we're fine, our IT company handles HIPAA." You are the office manager, and you have just been made the person who has to show the paperwork.
Work the checklist in nine blocks: administrative, technical, physical, vendor, training, risk analysis, incident readiness, documentation, and the proposed Security Rule changes. For every line record a named owner, the evidence that proves it happened, and a status (done, in progress or gap). Items without an owner drift; items without evidence cannot be shown to anyone who asks.
This page is the action list, not the explainer. If you want the background on the Privacy Rule, the Security Rule, the safeguard categories and who owns what inside a practice, read the HIPAA compliance and dental IT guide first, then come back and work through the tasks.
Nothing on this checklist certifies a practice's standing under HIPAA, and neither can a vendor or an IT company. What it does is give you a defensible, documented picture of what is in place, who owns it, and what proves it. Where a line quotes the regulation, it quotes the text of 45 CFR Part 164 as published on 6 November 2026; it is not legal advice, and the decisions that depend on it belong with qualified privacy counsel.
Work the checklist in nine blocks: administrative, technical, physical, vendor, training, risk analysis, incident readiness, documentation, and the proposed Security Rule changes. For every line record a named owner, the evidence that proves it happened, and a status (done, in progress or gap). Items without an owner drift; items without evidence cannot be shown to anyone who asks.
In this guide
- How to Use This Checklist
- What does HIPAA actually require a dental office to have in place?
- 1. Administrative Checklist
- 2. Technical Checklist
- 3. Physical Checklist
- 4. Vendor and Business Associate Checklist
- 5. Training Checklist
- 6. Risk Analysis and Risk Management Checklist
- 7. Incident Readiness Checklist
- 8. Documentation Checklist
- What would the proposed 2025 Security Rule changes add to this checklist?
- The IT side: which checklist items should your IT provider evidence for you?
- What to ask your IT provider about HIPAA evidence
- Turning Gaps Into a Plan
- Frequently asked questions
How to Use This Checklist
Copy the list into a shared document or spreadsheet with four columns. The first row below is the example; the next two show what a technical line and a vendor line look like when they are done properly.
| Item | Owner | Evidence | Status |
|---|---|---|---|
| Example: workforce HIPAA training on the practice's documented cadence | Practice administrator | Signed attendance log + course completion export | Done — 2026-06-04 |
| Example: multi-factor authentication on every Microsoft 365 mailbox | Security Official, with the IT provider | MFA enrollment report exported from the Microsoft 365 admin center, dated | In progress — 2 of 14 accounts outstanding |
| Example: signed Business Associate Agreement with the cloud imaging vendor | Privacy Official | Countersigned BAA PDF in the vendor register, renewal date recorded | Gap — sent for signature 2026-10-28 |
Rules that keep it honest:
- One named owner per line. Co-ownership means no ownership.
- Evidence must be a file, log, export or signed record someone else could read, not a memory.
- Anything marked "gap" gets a target date and lands in your remediation list.
- Review the whole sheet on a cadence your practice defines in writing, and after any staff change, software change, location change or security incident.
- Keep every superseded version. The documentation rule's retention clock runs from the date a document "last was in effect", so old versions are part of the record, not clutter.
The nine blocks, who usually owns each one in a dental office, and the standard each block answers:
The nine checklist blocks at a glance (45 CFR citations from the Legal Information Institute text, read 6 November 2026)
| Block | Usual owner in a dental office | 45 CFR standard it answers | Evidence that proves it | Review trigger |
|---|---|---|---|---|
| 1. Administrative | Privacy Official (often the office manager) | 164.308(a)(1)–(4), 164.530 | Designation memos, dated policies, access reviews | Any staff change; your written cadence |
| 2. Technical | Security Official with the IT provider | 164.312, 164.308(a)(5) | Account list, MFA and encryption exports, patch and backup reports | Any software or hardware change |
| 3. Physical | Office manager | 164.310 | Asset inventory, key-holder list, disposal certificates | Any move, remodel or equipment retirement |
| 4. Vendors and BAAs | Privacy Official | 164.308(b), 164.314(a) | Vendor register, countersigned BAAs | Every new vendor; every renewal |
| 5. Training | Privacy Official | 164.308(a)(5), 164.530(b) | Attendance logs, completion exports, outlines | New hire; your written cadence; after an incident |
| 6. Risk analysis and risk management | Security Official | 164.308(a)(1)(ii)(A)–(B) | The written analysis, the risk register, remediation records | Material change in systems, locations or staffing |
| 7. Incident readiness | Security Official | 164.308(a)(6), 164.400–414 | The plan, the offline contact sheet, the incident log | After every event, however small |
| 8. Documentation | Practice owner or administrator | 164.316 | Indexed, version-dated library; six-year retention | Every policy review |
| 9. Proposed Security Rule changes | Security Official with the IT provider | Proposed rule, 90 FR 898 (not in force) | A dated "where we stand" note against each proposal | Each time the federal agenda moves |
What does HIPAA actually require a dental office to have in place?
The Security Rule lists standards and, under each, implementation specifications marked either "Required" or "Addressable". Required ones must be implemented. Addressable ones must be assessed; you implement them if reasonable and appropriate, or document why not and what you did instead. Neither label means optional, and the documentation of the decision is itself a requirement.
The text is plainer than its reputation. Under 45 CFR 164.306(d), when a standard "includes required implementation specifications, a covered entity or business associate must implement the implementation specifications." For addressable ones it must "Assess whether each implementation specification is a reasonable and appropriate safeguard in its environment," then either implement it or, if that is not reasonable and appropriate, "Document why it would not be reasonable and appropriate to implement the implementation specification" and "Implement an equivalent alternative measure if reasonable and appropriate."
So a dental office that skips encryption on laptops because it is "only addressable" has misread the rule. The office may decide against a specific measure, but it must write the assessment down and show the alternative. The table below is the part of the rule a checklist is built from.
Security Rule implementation specifications most relevant to a dental office, with the label the rule gives each one (45 CFR 164.308, 164.310, 164.312, 164.316, read 6 November 2026)
| Safeguard area | Specification, as named in the rule | Label | What it looks like in a dental office |
|---|---|---|---|
| Administrative, 164.308(a)(1) | Risk analysis | Required | A written assessment covering every system that holds ePHI: practice management, imaging, email, cloud storage, backups, phones |
| Administrative, 164.308(a)(1) | Risk management | Required | A plan that reduces the identified risks, with owners and dates |
| Administrative, 164.308(a)(1) | Sanction policy | Required | A written consequence for staff who break privacy or security rules |
| Administrative, 164.308(a)(1) | Information system activity review | Required | Someone reads the audit logs, access reports and incident reports on a schedule |
| Administrative, 164.308(a)(3) | Termination procedures | Addressable | Access removed on the last day, across every system |
| Administrative, 164.308(a)(5) | Security reminders; Protection from malicious software; Log-in monitoring; Password management | Addressable (all four) | Periodic reminders, endpoint protection, failed-login review, a password policy |
| Administrative, 164.308(a)(7) | Data backup plan; Disaster recovery plan; Emergency mode operation plan | Required (all three) | Backups that exist, a restore procedure, and a way to see patients while systems are down |
| Administrative, 164.308(a)(7) | Testing and revision procedures | Addressable | A dated restore test and a review of the plan |
| Physical, 164.310(a) | Facility security plan; Access control and validation procedures; Maintenance records | Addressable | Locked server room, visitor rules, a log of repairs that touch security |
| Physical, 164.310(d) | Disposal; Media re-use | Required (both) | Wiped or destroyed drives, with a record, before anything leaves or is reassigned |
| Physical, 164.310(d) | Accountability; Data backup and storage | Addressable | A record of who moved which device, and a backup before equipment is moved |
| Technical, 164.312(a) | Unique user identification; Emergency access procedure | Required (both) | One named login per person, and a documented way to reach records in an emergency |
| Technical, 164.312(a) | Automatic logoff; Encryption and decryption | Addressable | Screen locks and session timeouts; encrypted drives and media |
| Technical, 164.312(b) | Audit controls (standard) | Standard | Logging turned on in the practice management system and retained |
| Technical, 164.312(d) | Person or entity authentication (standard) | Standard | A procedure that verifies each person signing in is who they claim to be: passwords today, a second factor wherever the risk analysis points to it |
| Technical, 164.312(e) | Integrity controls; Encryption | Addressable | Encrypted transmission of referrals, lab files and email containing PHI |
| Documentation, 164.316(b) | Time limit; Availability; Updates | Required (all three) | Six-year retention, documents reachable by the people who use them, periodic review |
Two things the table makes obvious. First, items that tend to slip in a busy office, such as the restore test and the screen lock, are addressable, which is why they drift. Second, the items that carry the heaviest consequences when missing, such as the risk analysis, unique logins and disposal, are required and have no "we assessed it" escape.
1. Administrative Checklist
The administrative block is the practice's own. An IT provider can supply exports and advice, but the designations, the policies and the sanction decisions are made and signed inside the office.
- Designate a HIPAA Privacy Official in writing. The Privacy Rule, 45 CFR 164.530(a), requires a covered entity to designate "a privacy official who is responsible for the development and implementation of the policies and procedures of the entity."
- Designate a HIPAA Security Official in writing. 45 CFR 164.308(a)(2) requires you to "Identify the security official who is responsible for the development and implementation of the policies and procedures." In a small office this can be the same person as the Privacy Official; record that decision.
- Maintain a current, written set of privacy and security policies and procedures that match how the office actually operates, not how a template says it should.
- Maintain a workforce sanction policy for privacy and security violations (a Required specification), and record every time it is applied.
- Document a process for granting, modifying and revoking system access, covering practice management software, imaging, email, cloud storage, remote access, payer portals and door codes.
- Run periodic access reviews across those systems and keep the export. The rule's "Information system activity review" is Required: somebody has to read the logs and sign that they did.
- Remove departing staff from every system on their last day, including shared services, payer portals and door codes. Shared payer-portal logins are the usual leak; our guide to shared payer portal logins and MFA in dental groups works through them payer by payer.
- Maintain a Notice of Privacy Practices and a documented process for patient rights requests (access, amendment, restriction, confidential communications). 45 CFR 164.520 gives individuals "a right to adequate notice of the uses and disclosures of protected health information." ADA members can find a sample notice and a practice checklist behind the member login on the ADA's HIPAA resources page.
- Keep an inventory of systems and locations where ePHI is created, received, stored or transmitted. The proposed rule would make this a standard in its own right (block 9); it is already the foundation of a defensible risk analysis.
- Record the date and outcome of each policy review.
Evidence to keep: signed designation memos, dated policy documents with version history, access review exports, offboarding checklists, the ePHI system inventory, the sanction log.
2. Technical Checklist
The technical block is where the IT provider does most of the work and the practice keeps most of the proof. Every line below should end in an export, a report or a screenshot that a reviewer could read without logging into anything.
- Unique named login for every workforce member; no shared or generic accounts. The rule gives "Unique user identification" the Required label (45 CFR 164.312(a)(2)(i)), so there is no documented alternative to choose instead. On a shared operatory computer that means fast user switching, badge or PIN sign-in, or per-user practice management logins, not one "Op3" account. The password management for dental offices guide covers the policy lines, the shared-workstation answer and the password manager requirements.
- Role-based permissions matched to job function, reviewed periodically. Front desk does not need the imaging administrator role; a hygienist does not need to export the patient database.
- Multi-factor authentication on email, remote access, cloud practice management (Dentrix Ascend, Curve, Denticon, Open Dental Cloud), payer portals where supported, and every administrator account. The current rule does not name MFA; the proposed rule would require it (block 9), and cyber insurers already ask about it. See the dental cyber insurance requirements guide for the twelve controls carriers ask about.
- Automatic screen lock and session timeout on all workstations ("Automatic logoff" is Addressable, so write down the timeout you chose and why).
- Full-disk encryption (BitLocker on Windows Pro) on workstations, laptops and any portable media. Keep the recovery keys somewhere other than the device.
- Encryption in transit for email containing PHI, remote sessions and file transfers to labs and specialists. The HIPAA email for dental offices guide covers the mail side; the secure way to send scans to a dental lab covers the file side.
- Managed endpoint protection on every device that touches ePHI, and a console that shows coverage. The difference between a signature antivirus and endpoint detection and response matters for insurance forms as much as for security; our guide to EDR vs antivirus for dental offices explains it.
- Business-grade firewall with current firmware; guest Wi-Fi separated from clinical systems; remote access only through the firewall's VPN or a managed remote-support tool, never an exposed remote desktop port.
- Audit logging enabled in the practice management system and retained for a defined period. "Audit controls" is a standard under 164.312(b): the system must "record and examine activity".
- A defined patch cycle covering operating systems, practice management and imaging software, firewall and network firmware, with a report that shows what was patched when.
- No unsupported operating systems holding or reaching ePHI. Windows 10 Home and Pro reached end of support on 14 October 2025 (Microsoft Lifecycle). Windows Server 2016 reaches the end of extended support on 12 January 2027; our guide to Windows Server 2016 end of support for dental offices lays out the replacement path.
- Documented backup schedule with copies on separate media and at least one off-site or immutable copy. The CISA-hosted "Data Backup Options" paper states the baseline as the 3-2-1 rule: "Keep 3 copies of any important file: 1 primary and 2 backups", on "2 different media types", with "1 copy offsite".
- Restore tests performed and recorded, not assumed. The data backup plan is Required; the testing of it is Addressable, which is exactly why practices discover a broken backup during the outage. See dental backup solutions for the mechanics and the dental backup and disaster recovery checklist for the test record format.
Evidence to keep: user account list with roles, MFA enrollment report, encryption status report, endpoint console export, firewall configuration summary and firmware version, patch reports, operating-system inventory, backup job history, dated restore-test records, log retention settings.
3. Physical Checklist
Physical safeguards feel like facilities rather than compliance, which is why they are rarely written down. Two of them, Disposal and Media re-use, are Required specifications.
- Server, NAS and network equipment in a locked room or cabinet with controlled key or code access, and a list of who holds the keys or codes.
- Front-desk and operatory monitors positioned or shielded so patients cannot read them; privacy filters where repositioning is impossible.
- Visitor and after-hours access procedures for areas holding equipment or records, including cleaning crews and contractors.
- A log of repairs and modifications that touch security (door locks, cabinet locks, camera placement). "Maintenance records" is an Addressable specification under 164.310(a)(2)(iv).
- Any remaining paper records in locked storage, with a shredding process and a certificate from the shredding vendor.
- Documented, verifiable disposal or wipe for retired computers, drives, imaging sensors with local storage, and the old server after a migration. The rule requires policies "to address the final disposition of electronic protected health information, and/or the hardware or electronic media on which it is stored."
- Wipe before reassignment. "Media re-use" requires "removal of electronic protected health information from electronic media before the media are made available for re-use", which includes the old front-desk PC that becomes the break-room computer.
- An asset inventory that records which devices exist, where they are and who uses them, plus a record of movements when a device changes rooms or locations.
- A backup before equipment is moved (Addressable), which in practice means a verified backup before the server is relocated or the operatory is remodelled.
Evidence to keep: asset inventory with locations, key and code holder list, visitor log, maintenance log, disposal or certificate-of-destruction records, photos or notes from a walkthrough.
4. Vendor and Business Associate Checklist
A dental office shares patient data with more companies than it realises: the practice management vendor, the cloud imaging host, the clearinghouse, the backup provider, the IT company, the email host, the phone system if it transcribes voicemails, the patient-texting platform. The rule's test is simple to state: a covered entity may let a business associate "create, receive, maintain, or transmit electronic protected health information on the covered entity's behalf only if the covered entity obtains satisfactory assurances" (45 CFR 164.308(b)(1)), and those assurances take the form of a written contract under 164.314(a).
- Maintain a list of every vendor that creates, receives, stores or transmits ePHI on your behalf, and ask the rule's question of every new vendor before anything is shared.
- Execute a Business Associate Agreement with each of them before ePHI is shared, and keep the countersigned copy.
- Store signed BAAs where they can be produced quickly, with renewal or review dates tracked.
- Review vendor remote-access accounts and remove them when an engagement ends, including the previous IT company's accounts and remote tools.
- Record what each vendor is permitted to access and why.
- Ask each vendor what it would do and whom it would call in a breach; the proposed rule would require written verification of a business associate's technical safeguards (block 9).
A starter vendor register for a dental office (the "ePHI on your behalf?" column is the question the rule asks; confirm each answer with your counsel, not with the vendor's marketing page)
| Vendor type | Examples the reader may use | Handles ePHI on your behalf? | What to record |
|---|---|---|---|
| Practice management software (cloud or hosted) | Dentrix Ascend, Eaglesoft, Open Dental, Curve, Denticon | Typically yes | BAA, data location, who holds the admin login |
| Imaging software and cloud image storage | DEXIS, Carestream, Planmeca Romexis, cloud image archives | Typically yes | BAA, where images are stored, retention |
| Clearinghouse and billing services | Electronic claims, remote billing companies | Typically yes | BAA, which payer portals they log into |
| Backup and disaster recovery provider | Managed backup, cloud storage of backups | Typically yes | BAA, encryption, where the copies live |
| IT support or managed service provider | Your IT company | Typically yes | BAA, list of remote tools and accounts, offboarding commitment |
| Email host | Microsoft 365, Google Workspace | Typically yes if PHI is sent or stored | BAA, MFA status, retention settings |
| Phone and voicemail transcription | Cloud phone systems that transcribe or record | Depends on features in use | BAA if recordings or transcripts hold PHI |
| Patient communication and texting | Reminder and two-way texting platforms | Typically yes | BAA, what data it syncs from the PMS |
| Shredding and e-waste disposal | Document and hardware destruction vendors | Depends on what they handle | Certificate of destruction per pickup |
| Cleaning, construction and other on-site services | Contractors with physical access only | Usually no (physical access, not data) | Visitor and after-hours procedures instead of a BAA |
Evidence to keep: vendor register, signed BAAs with dates, vendor access list, offboarding notes, the "what would you do in a breach" answers.
5. Training Checklist
Training is the block most offices can prove least, because the session happened and the paperwork did not. The rule requires "a security awareness and training program for all members of its workforce (including management)" under 164.308(a)(5), with four Addressable specifications: "Security reminders", "Protection from malicious software", "Log-in monitoring" and "Password management". The Privacy Rule adds its own training requirement under 164.530(b).
- Deliver HIPAA and security awareness training at onboarding, before access is granted where practical. Our guide to HIPAA training for dental offices: who, how often and what to keep quotes the cadence rules and separates what staff cover from what IT covers.
- Repeat training on a cadence your policy defines, and after significant changes (a new practice management system, a new location, an incident).
- Cover role-specific realities: front-desk disclosures, phishing, safe handling of radiographs and referrals, texting and email rules, personal device use, and what a fake "IT support" phone call sounds like. Our guide to fake IT support scams aimed at dental offices has the scripts to rehearse.
- Train staff on how to report a suspected incident, with a blame-free path and a named person to tell.
- Log attendance, date, topics and materials for every session; keep the course outline with the log.
- Keep the "Security reminders" trail: the dated email or huddle note counts as evidence of an Addressable specification you chose to implement.
Evidence to keep: signed attendance logs, training platform completion reports, course outlines, reminder emails or huddle notes, phishing simulation results if you run them.
6. Risk Analysis and Risk Management Checklist
The risk analysis is the document every other block depends on and the one most often missing. The rule's words are worth keeping in front of you: "Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information held by the covered entity or business associate" (164.308(a)(1)(ii)(A), Required), followed by risk management: "Implement security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level" (164.308(a)(1)(ii)(B), Required).
- Conduct a documented risk analysis covering all ePHI systems, not just the server: practice management, imaging, email, cloud storage, backups, phones, remote access, personal devices that reach email.
- Record identified risks, likelihood, potential impact and the decision made for each.
- Maintain a risk management plan showing how identified risks are being reduced, with owners and target dates.
- Repeat the analysis when systems, locations, staffing or workflows change materially, and on a cadence you define in policy. The current rule does not name an interval; the proposed rule would (block 9).
- Keep prior versions so progress over time is visible.
- If you have no analysis at all, start with the free federal tool. The ONC and OCR Security Risk Assessment Tool (SRA Tool v3.7) is a desktop application for 64-bit Windows whose "target audience ... is medium and small providers"; "All information entered into the tool is stored locally on the user's computer", and version 3.7 adds a "New assessment-scope question to ensure SRAs account for every location that creates, receives, maintains, or transmits ePHI." It is a starting point, and its own page says the survey alone may not identify every risk.
The HIPAA risk assessment and audit preparation guide walks through the method, the scoring and the mock request list; this block is the checklist view of it.
Evidence to keep: the risk analysis report, the risk register, remediation tickets or project records, dated prior versions, the SRA Tool export if you used it.
7. Incident Readiness Checklist
Incident readiness is tested at the worst moment, so it has to be written, printed and reachable when the network is down. The one clock everyone misremembers is in 45 CFR 164.404(b): a covered entity "shall provide the notification required by paragraph (a) of this section without unreasonable delay and in no case later than 60 calendar days after discovery of a breach." Sixty is the outer limit, not the target, and the determination that a breach occurred is made with counsel.
- Written incident response plan naming who is called first, in what order: the IT provider, the cyber insurance carrier's breach line, privacy counsel, the practice owner.
- Contact details for all of them stored somewhere accessible when the network is down (printed, and on a phone that is not joined to the office Wi-Fi).
- Documented downtime procedures so the practice can keep seeing patients without systems: paper schedule export, paper charting forms, a way to reach the imaging software's local cache. This is the "Emergency mode operation plan", a Required specification.
- Instructions to preserve evidence rather than wiping or rebuilding immediately; the insurer's forensics team will ask for logs and images.
- A clear statement that breach determinations are made with qualified counsel, not informally in the huddle.
- An incident log capturing date, discovery, actions taken and outcome for every event, including small ones: a misdirected fax, a lost USB stick, a phishing click that was caught. Small entries prove the process works.
- A tabletop exercise once a year or after a staffing change, with notes. The proposed rule would require testing the incident plan at least every 12 months (block 9).
Evidence to keep: the plan document, the offline contact sheet, downtime forms, incident log entries, tabletop notes, after-action notes. The ransomware recovery playbook covers the response sequence hour by hour.
8. Documentation Checklist
Documentation is its own standard, not an afterthought. 45 CFR 164.316(b) requires written records of policies, procedures and of "the action, activity, or assessment" the rule requires, and its three implementation specifications are all Required: "Time limit", "Availability" and "Updates".
- Central, access-controlled location for all compliance documentation, with a backup of the library itself.
- Version dates on every policy and plan, and a changelog line for each revision.
- Retention of six years. The rule says: "Retain the documentation required by paragraph (b)(1) of this section for 6 years from the date of its creation or the date when it last was in effect, whichever is later." A policy retired in 2026 is kept until 2032.
- Availability: "Make documentation available to those persons responsible for implementing the procedures to which the documentation pertains." The front desk needs the privacy procedures; the Security Official needs the technical ones; nobody should have to ask IT for the office's own policies.
- Updates: "Review documentation periodically, and update as needed, in response to environmental or operational changes." A new practice management system, a new location and a new IT provider are each a review trigger.
- An index so a specific document can be produced without a search through inboxes.
- Evidence organised by safeguard category so it maps to how a review is likely to be structured. The HIPAA risk assessment and audit preparation guide explains how to build that evidence inventory.
Evidence to keep: the index itself, the retention schedule, the access list for the documentation library.
What would the proposed 2025 Security Rule changes add to this checklist?
The proposed rule of 6 January 2025 (90 FR 898) would turn several addressable or unnamed practices into explicit requirements. It is a proposal and binds nobody today; the Fall 2025 Unified Agenda files it under Long-Term Actions and dates the final action July 2027. Score your practice against them now; cyber insurers already ask about several.
The agenda status is on reginfo.gov (RIN 0945-AA22, Fall 2025 edition): "Stage of Rulemaking: Long-Term Actions", with "Final Action 07/00/2027". That date is an agency estimate, not a deadline, and it has moved before. The HIPAA Security Rule updates for dental practices explainer tracks the rule's progress; this block translates it into checklist rows.
Block 9: what the proposed Security Rule would add, quoted or closely paraphrased from the proposed rule's own text (90 FR 898, 6 January 2025, read on federalregister.gov 6 November 2026); none of it is in force
| Proposal | What the proposed rule says | Checklist row to add now |
|---|---|---|
| End of the Required/Addressable split | OCR proposes "to remove the distinction between 'addressable' and 'required' implementation specifications" and "require regulated entities to comply with both the standards and implementation specifications" | Treat every addressable row in the table above as if it were required; keep the documented assessment anyway |
| Technology asset inventory and network map | A standard that "would require a regulated entity to conduct and maintain an accurate and thorough written technology asset inventory and a network map", reviewed "at least once every 12 months" and after changes | Build the inventory now (block 1); ask IT for a network diagram and date it |
| Multi-factor authentication | The proposal adds a definition of "Multi-factor Authentication" and would require it as a technical safeguard, with limited exceptions | Finish MFA on email, remote access, cloud PMS and admin accounts (block 2) |
| Encryption of ePHI at rest and in transit | Encryption would move from addressable to required, with exceptions to be documented | Encrypt every workstation, laptop and backup set; record the exceptions (block 2) |
| Patching with deadlines | Patch "within 15 calendar days of identifying the need to address a critical risk" and "within 30 calendar days of identifying the need to address a high risk", where a patch is available | Ask IT for a patch report that shows time-to-patch by severity (block 2) |
| Vulnerability scanning and penetration testing | Automated vulnerability scans "at least once every six months" and periodic penetration tests | Ask whether your provider runs scans today and what the last report found |
| Backup technical controls, tested | Deploy technical controls for backups and "review and test the effectiveness of such technical controls at least once every six months" | Schedule a restore test every six months and keep the record (block 2) |
| 72-hour restoration | Written procedures "to restore both its critical relevant electronic information systems and data within 72 hours of the loss" | Write down which systems are critical (PMS, imaging, phones) and ask IT how long each restore takes today |
| Workforce access changes within 24 hours | Notify other regulated entities of a terminated workforce member's access change "no later than 24 hours" after it | Add payer portals and vendor portals to the last-day offboarding list (block 1) |
| Annual compliance audit | "perform and document an audit of their compliance with each standard and implementation specification of the Security Rule at least once every 12 months" | Date your own full pass through this checklist and keep it; that is the audit record |
| Incident plan testing | Test security incident response plans at least once every 12 months and document the results | Run the tabletop (block 7) and file the notes |
| Written verification from business associates | Obtain "written verification from the business associate that the business associate has deployed the required technical safeguards" | Add a "safeguards attestation" column to the vendor register (block 4) |
None of these rows should be presented to anyone as current law. They are the direction of travel, and a practice that can already produce the evidence for them has very little to fear from the final rule when it arrives.
The IT side: which checklist items should your IT provider evidence for you?
A dental office cannot delegate HIPAA, but it can and should delegate the production of technical evidence. The split that works: the practice owns the policy, the decision and the signature; the IT provider owns the configuration and exports the proof on a schedule you set, in a format a non-technical reviewer can read. The evidence each layer should produce is listed in the nine layers a data protection service covers.
This is the part of the checklist that dental cybersecurity services exist to make routine.
Who produces what: the technical checklist items, the export your IT provider should hand you, and the part the practice still owns
| Checklist item | What IT exports (dated) | What the practice still owns |
|---|---|---|
| Unique logins, no shared accounts | User account list with roles, from Windows and from the PMS | The access policy; the decision to remove an account |
| Multi-factor authentication | MFA enrollment report from Microsoft 365 or Google Workspace; cloud PMS MFA status | Which accounts are exceptions, and why, in writing |
| Encryption at rest | BitLocker or disk-encryption status by device; recovery-key storage location | The decision to encrypt everything; media handling rules |
| Endpoint protection | Console export showing every device covered, and the uncovered count | Reporting a new device so it gets an agent |
| Patching and supported systems | Patch report by device and severity; operating-system inventory with end-of-support dates | The budget decision to replace unsupported machines |
| Firewall and remote access | Firmware version, VPN or remote-tool user list, no open remote desktop ports | Approving who may connect remotely |
| Audit logging | PMS and server log settings and retention; evidence that logs were reviewed | Reading the review summary and signing it |
| Backups and restore tests | Backup job history; a restore-test record with date, what was restored and how long it took | Deciding which systems are critical and how long the office can be down |
| Email security | Mail-flow and encryption settings; SPF, DKIM and DMARC records in place | The rule for what may be emailed and to whom |
| Vendor remote access | List of every vendor and former provider with remote tools, and removal dates | The BAA and the decision to end an engagement |
What this looks like when it is done: when Legend Networking completed the technology installation for Trueform Dental in Temecula, the project update documented computers, networking, software, imaging integration, backups and security configuration, which is the inventory a practice can hand to its Security Official on day one. Legend Networking has served over 3,500 practices since 2004 from its Dallas headquarters, provides 24/7 monitoring, and uses in-house engineers with no outsourced first-level triage, so the exports above come from the people who configured the systems. Ian Lynch, with 22 years in dental IT, oversees the NOC, onsite dispatch and client technology roadmaps.
Running the checklist across more than one location
In one office, the person who keeps this sheet can usually walk to every computer it describes. A group of three or more locations has a different problem: the evidence exists per location, in different formats, and nobody can say whether every office would pass today. The fix is one standard and one evidence pipeline: the same account policy, the same backup product, the same endpoint console, and reports that roll up by location. That is the operating model behind DSO IT support, and it is also what a buyer's due-diligence list will test during an acquisition. Whatever your size, the checklist and the exports should read the same in every operatory, from a Dallas startup to dental IT in your city.
What to ask your IT provider about HIPAA evidence
Most IT companies will say they "handle HIPAA". The useful question is what they will hand you, how often, and in what form. Use these questions at your next review meeting, or when comparing managed IT services for dental practices that will own the technical blocks.
Questions to ask before you rely on an IT provider for the technical blocks
- Which items on this checklist will you export evidence for, on what schedule, and in what format a non-technical reviewer can read?
- Will you sign a Business Associate Agreement, and what do you commit to doing within the first 24 hours of a suspected incident?
- How many of our devices currently have no endpoint agent, and how would we know if that number changed?
- When was our last restore test, what was restored, how long did it take, and where is the record?
- Which of our systems still run an unsupported operating system, and what is the dated replacement plan?
- Which accounts do not have multi-factor authentication today, and why?
- Which remote-access tools and accounts exist on our network, including those of previous providers, and who approved each?
- Can you show the audit-log retention settings in our practice management system and who reviews the logs?
- What is in our network diagram and asset inventory, and when was it last updated?
- If we ended the engagement, how would you hand back our administrator credentials, documentation and evidence files?
A provider that answers these with exports rather than reassurances is doing the technical half of the job. A provider that answers with "we are fully covered" is telling you that the evidence does not exist yet.
Turning Gaps Into a Plan
When you finish a pass, you will have a set of gap lines. Planning guidance, not a legal ranking: a practical first pass is to prioritise gaps by likely exposure and operational impact rather than by effort; items involving credentials, remote access, untested backups, unsupported systems and missing BAAs are common examples. HIPAA does not prescribe a universal remediation order, so document the reasoning behind your own priorities. Common HIPAA violations in dental practices walks through remediation examples for each pattern, and the dental cybersecurity risk assessment checklist gives the 25-point technical view that sits underneath blocks 2 and 6.
Assign every gap an owner and a date, then re-review. A checklist that never changes state is a document, not a program. A simple gap register keeps the plan honest:
A gap register layout that survives staff turnover (one row per gap line from the checklist)
| Column | What goes in it | Example |
|---|---|---|
| Gap | The checklist line, quoted | Restore test performed and recorded |
| Block | 1 to 9 | 2. Technical |
| Exposure | Your own high / medium / low, with a sentence of reasoning | High: backups have never been restored since the server move |
| Owner | One named person | Security Official, with the IT provider |
| Target date | A date, not "Q1" | 2026-12-05 |
| Evidence when closed | The file that will exist when the gap is closed | Restore-test record with timings, filed under block 2 |
| Status and date | Open / in progress / closed, dated | In progress, 2026-11-20 |
If you want the technical items implemented, monitored and evidenced for you, our HIPAA compliance service covers the environment side while your practice keeps ownership of the program. Practices that also handle card payments should review our dental HIPAA and PCI compliance services, which cover both frameworks in one program. Legend Networking holds a 4.8 rating from 173 Google reviews.
Frequently asked questions
What should a dental HIPAA compliance checklist include?
Administrative, technical, physical, vendor, training, risk analysis, incident readiness and documentation items, plus a block for the proposed Security Rule changes so you can score yourself against what is coming. Every line carries a named owner, the evidence that proves it and a current status. A checklist without an evidence column is a list of intentions, not a compliance record.
Who should own each item on the checklist?
A single named person. In most dental offices the Privacy Official, usually the office manager, owns policy, patient rights, vendor agreements and training items; the Security Official owns technical, risk analysis and incident items, working with the IT provider for the exports; the practice owner or administrator signs off on the whole sheet and the gap register. Co-ownership means no ownership.
What counts as evidence for a checklist item?
Something a third party could read without logging into anything: a signed policy with a date, a training attendance log, an access review export, a backup restore-test record with timings, a signed Business Associate Agreement, a patch report, an MFA enrollment report or an incident log entry. A verbal assurance from the IT company, or a memory that it was done, is not evidence.
How often should the checklist be reviewed?
On a cadence your practice sets in writing, and additionally after staff changes, new software or locations, or any security incident. The current Security Rule does not prescribe a single universal interval for every practice; the proposed 2025 rule would require a documented compliance audit at least once every 12 months, which is a sensible cadence to adopt now and date.
Does completing this checklist mean my practice has achieved HIPAA compliance?
No. It gives you a documented view of your program and its gaps, which is what a reviewer, an insurer or a buyer will ask to see. No checklist, software product or IT company can certify a practice's standing under HIPAA. Compliance conclusions and any legal determinations should involve qualified privacy or security counsel who can read the evidence you have gathered.
Does HIPAA apply to a small dental office with one dentist?
HIPAA applies to "covered entities", and 45 CFR 160.103 defines one to include "A health care provider who transmits any health information in electronic form in connection with a transaction covered by this subchapter," such as electronic insurance claims. The definition has no size threshold. Whether a particular office meets it is a question for counsel, but most offices that bill insurance electronically plan on the basis that they do.
Is multi-factor authentication required by HIPAA for dental offices?
The current Security Rule does not name multi-factor authentication; it requires unique user identification and lets a practice choose its authentication method through the risk analysis. The proposed rule published in January 2025 would require MFA with limited exceptions, and most cyber insurance applications already ask about it. Treat it as a checklist item today and keep the enrollment report as evidence.
Does HIPAA require a dental office to encrypt its computers?
Encryption is an Addressable specification under 45 CFR 164.312(a)(2)(iv) and 164.312(e)(2)(ii). The office has to weigh encryption against its own environment in writing; where it decides against it, the file must show the reasoning and the substitute measure. For a dental office with laptops, portable media and backups, the documented decision almost always ends in encrypting everything and recording the exceptions.
How long must a dental office keep HIPAA documentation?
Six years. 45 CFR 164.316(b)(2)(i) requires a covered entity to "Retain the documentation required by paragraph (b)(1) of this section for 6 years from the date of its creation or the date when it last was in effect, whichever is later." Retired policies count, so keep every superseded version with its dates and store the library somewhere that is itself backed up.
Is a HIPAA compliance checklist the same as a HIPAA risk analysis?
No. The checklist is the inventory of safeguards, owners and evidence across the whole program. The risk analysis is one Required item on it: a written assessment of the risks to electronic patient data across every system that holds it, followed by a risk management plan. You can tick most of the checklist and still have no risk analysis, which is why the two are tracked as separate records.
Can my IT company handle HIPAA for my dental office?
Partly. An IT provider can configure the technical safeguards and export the evidence for them: account lists, MFA and encryption reports, patch and backup records, restore tests, log settings. It cannot designate your Privacy and Security Officials, write your policies, train your staff, sign your vendors' agreements or make breach determinations. Ask for the exports on a schedule and keep the rest in the office.

