Lesson objective
Align session material with the practice's written rules and its existing workforce training duty, and state accurately what a session does and does not do about any obligation the practice carries.
Plain-language explanation
Why this matters now
A session that teaches a rule the practice has not written is a session that leaves learners choosing between two authorities: the visitor who left at one o'clock, and the policy they will actually be held to. The visitor loses, and should.
So before the material is built, the design has to find the practice's own written ground and stand on it. Three things are worth separating carefully, because instructors routinely blur them: what the practice already has to do, what it has voluntarily adopted, and what the instructor is offering.
Regulation: the HIPAA Security Rule, 45 CFR 164.306, 164.308 and 164.312, binding on covered entities and business associates. Section 164.306(a) requires regulated entities to ensure the confidentiality, integrity and availability of all electronic protected health information they create, receive, maintain or transmit, and to protect against reasonably anticipated threats. Section 164.306(b)(2) requires an entity, in choosing security measures, to consider its size, complexity and capabilities, its technical infrastructure, the costs, and the probability and criticality of potential risks — which is why a four-operatory practice and a forty-location group can reach different answers lawfully. Section 164.306(d) marks implementation specifications "Required" or "Addressable". Among the required administrative safeguards are risk analysis at 164.308(a)(1)(ii)(A), "an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability" of ePHI; risk management at (B); a sanction policy at (C); and information system activity review at (D), such as audit logs and access reports. Section 164.308(a)(5)(i) requires a security awareness and training programme for all workforce members, including management. Section 164.308(a)(8) requires periodic technical and nontechnical evaluation, including in response to environmental or operational changes affecting the security of ePHI. Under 164.312, unique user identification is required, audit controls and authentication are required, and encryption at rest and transmission encryption are addressable. Note carefully that encryption is currently addressable rather than required; a January 2025 proposal would change that and is only a proposal.
Voluntary framework: the NIST AI Risk Management Framework 1.0 (NIST AI 100-1), released 26 January 2023. Voluntary, rights-preserving, non-sector-specific and use-case agnostic. Its Core has four functions, GOVERN, MAP, MEASURE and MANAGE, of which GOVERN "applies to all stages" while the others apply in system-specific contexts and at lifecycle stages. NIST states that after instituting GOVERN outcomes "most users of the AI RMF would start with the MAP function". Its trustworthy-AI characteristics are: valid and reliable; safe; secure and resilient; accountable and transparent; explainable and interpretable; privacy-enhanced; and fair with harmful bias managed. It binds no dental practice, no regulator requires it, and there is no certification to it.
Voluntary standard: ISO/IEC 42001:2023, published 18 December 2023, Edition 1, from ISO/IEC JTC 1/SC 42. ISO describes it as specifying "requirements for establishing, implementing, maintaining, and continually improving an Artificial Intelligence Management System (AIMS)", as a management system standard using Plan-Do-Check-Act that, "rather than looking at the details of specific AI applications", manages AI risks and opportunities across an organisation, and as suitable for "organizations of any size involved in developing, providing, or using AI-based products or services". ISO calls it "the world's first AI management system standard". It is voluntary, its text is paid, and no law cited in this programme requires a dental practice to conform to it.
A question to sit with
The office manager tells you the practice needs "the HIPAA AI training". What exactly does the practice already owe, what does it merely hope for, and which of the two is your session actually about?
What goes wrong
1. "HIPAA requires AI training." It does not. Section 164.308(a)(5)(i) requires a security awareness and training programme for all workforce members including management. It says nothing about artificial intelligence. Whether AI-related content belongs in that programme is a judgment for the practice and its security and privacy officials.
2. A voluntary framework taught as a legal requirement. The NIST framework and ISO/IEC 42001 are voluntary. Saying "NIST requires" or "ISO 42001 compliance is mandatory" in front of a room that will later check is a credibility failure with no upside.
3. Certification language. There is no NIST certification. The ISO entry here records nothing about who certifies, and quoting clause numbers or Annex controls from a paid text you have not read is inventing authority.
4. The proposed rule taught as current. Encryption at rest and transmission encryption are currently addressable. A January 2025 proposal would change parts of the Security Rule and remains a proposal. Teaching a proposal as a duty is the most common currency failure in this field, and Module 03 treats it properly.
5. Teaching a rule the practice has not written. The session says "only the licensed tool touches patient information" and no such list exists. The learners now have an instruction with no policy behind it and no way to comply reliably.
6. Claiming the session discharges an obligation. "This session satisfies your training requirement" is a claim about the practice's compliance that no instructor is in a position to make.
The practical answer
Best practice: collect the practice's written ground before designing. Ask for six things, in writing, and record what is missing:
- the list of tools permitted to touch patient information, and what data each may receive;
- the written rule on who reviews AI-assisted output before it reaches a patient, a payer or the record;
- the risk analysis, or at least the risks it names that are relevant to the tools in your session;
- the existing security awareness and training programme and its schedule;
- the supervision and delegation arrangements for the roles in the room;
- any vendor records or agreements relevant to the tool being taught.
Best practice: map each session element to the written rule it supports. A one-page mapping is the difference between a session and a slideshow.
| Session element | Practice rule it supports | Status of that rule |
|---|---|---|
| Classify before you paste: what may reach which tool | The permitted-tool list | Practice policy, under the practice's own Security Rule duties |
| The named check before a drafted message is queued | The written review rule | Practice policy; this programme's standard is that it is recorded |
| Reporting a suspected exposure the same day | The practice's incident and sanction policies | Required administrative safeguards under the Security Rule |
| Unique logins, never shared, for any tool touching ePHI | The practice's access rules | Unique user identification is required under 164.312 |
| Where the practice's AI decisions are written down | The practice's governance, if it has adopted a framework | Voluntary if it rests on the NIST framework or ISO/IEC 42001 |
Best practice: if a rule is missing, report it, do not write it. An instructor who drafts the practice's policy from the front of the room has changed roles without being asked and without the standing to do it. Send a short written note to whoever commissioned the session naming each gap, and design only behaviours the existing rules can carry.
Best practice: state the practice's own sizing rule out loud. The Security Rule expressly allows an entity to consider its size, complexity, capabilities, technical infrastructure, costs, and the probability and criticality of potential risks. That sentence is worth reading aloud to a small practice that has been told it must do whatever a large group does. What it does not permit is doing nothing: the required specifications remain required.
Best practice: describe what your session is, precisely. You may say what the session covered, which written practice rules it supports, who attended and when. You may not say it makes the practice compliant, that it satisfies any legal or licensing obligation, that it carries any board or association recognition, or that it counts toward any professional education requirement, permit or credential. That is true of this certificate too, and an instructor who is casual about it in their own case will be casual about it in the practice's.
Remember this
- The Security Rule requires a security awareness and training programme for all workforce members including management; it says nothing about AI.
- Encryption at rest and transmission encryption are addressable today; the January 2025 proposal is a proposal.
- The NIST framework and ISO/IEC 42001 are voluntary, bind no dental practice, and carry no certification claim you may make here.
- Collect the practice's written rules first; if one is missing, report it in writing and do not draft it yourself.
- Never say a session makes a practice compliant, satisfies an obligation, or carries any recognition.
Dental practice example
Priya Nkemelu-Hart, a fictional compliance lead and trainer at the fictional Kestrel Bay Family Dental, is asked by the owner to deliver "our HIPAA AI training" before the end of the quarter. She writes back in four sentences. The Security Rule requires a security awareness and training programme for all workforce members including management, and says nothing about artificial intelligence; whether AI content belongs in that programme is a decision for the practice, its privacy official and its security official, not for her as the person delivering the session. She then asks for six written items. Four arrive: a permitted-tool list naming two licensed tools, a review rule for outbound patient messages, the practice's training schedule, and the vendor agreement for the drafting tool. Two are missing: the risk analysis is two years old and does not mention any AI tool, and there is no written rule at all about drafted clinical text. Priya sends an eighty-word note naming both gaps and designs around them. Her session covers only behaviours the existing rules can carry: classify before you paste, using the permitted-tool list; the named check before a drafted message is queued, using the existing review rule; unique logins never shared, which she ties to the required unique user identification specification; and same-day reporting of a suspected exposure, which she ties to the practice's incident and sanction policies. She builds a one-page mapping showing each of the four against the written rule it supports. A hygienist asks whether the practice is breaking the law because the tool does not encrypt stored drafts. Priya says encryption at rest is currently an addressable implementation specification rather than a required one, that a proposal published in January 2025 would change parts of the Security Rule and remains a proposal as of today, and that what the practice must do is the risk-based analysis the rule requires, which is the security official's work and not hers to conclude. Her closing slide lists the four practice rules the session supports. It does not say the practice is compliant, does not claim the session satisfies any obligation, and makes no claim of recognition by any board or association. She files the six-field session record and hands the gap note to the security official.
Responsible-use warning
Never tell a dental room that HIPAA requires AI training; the required programme is security awareness and training for the workforce and it does not mention AI. Never describe the NIST framework or ISO/IEC 42001 as legal requirements, never claim a certification to either, and never quote clause numbers from a paid standard you have not read. Never teach the January 2025 Security Rule proposal as current law, never state that a session makes a practice compliant or satisfies an obligation, and never draft the practice's missing policy yourself: report the gap in writing and design around it.
Human-review requirement
The practice owner or dentist of record, with the designated privacy official and security official, owns every conclusion about what the practice must do and whether a session forms part of its security awareness and training programme. The instructor maps session elements to existing written rules, reports gaps in writing, and designs only behaviours the current rules can carry. Before delivery, the security official reviews any slide describing a Security Rule requirement, confirms the required and addressable distinction is stated correctly, and confirms no voluntary framework is described as binding.
Practical exercise
Place a session inside a fictional practice's written governance. Use a fictional practice, fictional policies and fictional staff throughout.
- Describe a fictional dental practice in four sentences: size, operatories, roles, and whether it is part of a group.
- Write the six-item request you would send before designing: permitted tools and permitted data, the review rule, the risk analysis or its relevant named risks, the existing training programme and schedule, supervision arrangements for the roles in the room, and vendor records for the tool being taught.
- Invent a realistic reply in which two of the six are missing or out of date, and record exactly which two.
- Write the eighty-word note reporting those gaps to whoever commissioned the session, without drafting the missing policy.
- List four session elements you can build from the written rules that do exist, and map each to the specific rule it supports.
- For each mapped element, label the status of the rule: a requirement under the Security Rule, the practice's own policy, or a voluntary framework the practice has adopted.
- Write one sentence each, correctly labelled, about the security awareness and training requirement, the required versus addressable distinction, and the status of the NIST framework and of ISO/IEC 42001.
- Write the answer you would give a staff member who says the practice is breaking the law because a tool does not encrypt stored drafts.
- Draft the six-field session record, and add one line stating who decides whether it forms part of the practice's training programme.
- Write your closing slide text, naming what the session covered and the rules it supports, and strike any phrase claiming compliance, satisfaction of an obligation, or recognition by a board or association.
- Reread the whole design and mark every sentence that states a duty, confirming each names who is bound and by what.
Knowledge check
-
What training does the HIPAA Security Rule actually require, and what does it not mention?
Answer guidance: Section 164.308(a)(5)(i) requires a security awareness and training programme for all workforce members including management; the rule says nothing at all about artificial intelligence.
-
What is the current status of encryption under the Security Rule?
Answer guidance: Encryption at rest and transmission encryption are addressable implementation specifications rather than required ones; a January 2025 proposal would change parts of the rule and remains only a proposal.
-
How should the NIST AI RMF and ISO/IEC 42001 be described to a dental team?
Answer guidance: As voluntary documents that bind no dental practice and that no US regulator requires dentists to adopt, with no certification claim made for the NIST framework in this programme.
-
What should an instructor do on finding that the practice has no written rule for a behaviour they planned to teach?
Answer guidance: Report the gap in writing to whoever commissioned the session, decline to draft the policy from the front of the room, and design only behaviours the practice's existing written rules can carry.
Sources and further reading
- U.S. Department of Health and Human Services (Electronic Code of Federal Regulations) — 45 CFR 164.306 Security standards: General rules; 164.308 Administrative safeguards; 164.312 Technical safeguards. Accessed 2026-09-15.
- National Institute of Standards and Technology — Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1 (2023-01-26). Accessed 2026-09-15.
- International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC), ISO/IEC JTC 1/SC 42 — ISO/IEC 42001:2023 Information technology — Artificial intelligence — Management system (2023-12-18). Accessed 2026-09-15.
- AI Coalition Network — Certification Educational Standard: Human Review of AI-Assisted Professional Work. Accessed 2026-09-15.
- American Dental Association, House of Delegates — Policy Statement on the Use of Augmented Intelligence in Dentistry (Trans.2021:282), as printed in ADA Current Policies, Adopted 1954-2025. Accessed 2026-09-15.