Lesson objective
Write a non-delegable list as enforceable controls and explain why a Medicare supervision condition is about people rather than software.
Plain-language explanation
Why this matters now
The register from Lesson 2 says who holds each decision. This lesson says what nobody may hand over at all, to a tool, a supplier or a management company, and it ends with the clearest worked example in federal payment rules of a duty that is about people and cannot be met by software.
Start with the payment rule, because practices that bill Medicare already live inside it.
- Law / rule (42 CFR 410.26, Medicare Part B conditions for services and supplies furnished incident to a physician's professional service; binds physicians and practitioners who bill incident-to services): 410.26(b)(5) provides that "In general, services and supplies must be furnished under the direct supervision of the physician (or other practitioner)", with designated care management services and behavioral health services by auxiliary personnel permitted under general supervision, and states that "only the supervising physician (or other practitioner) may bill Medicare for incident to services". 410.26(a)(2) allows the presence required for direct supervision to "include virtual presence through audio/video real-time communications technology (excluding audio-only)" for services without a 010 or 090 global surgery indicator. 42 CFR 410.32(b)(3)(ii) defines direct supervision in the office setting as the physician being present in the office suite and immediately available, though not necessarily in the room; the eCFR shows 410.32 last amended by an entry dated 1 January 2026. Under 410.26(b)(7), services must be furnished in accordance with applicable State law.
Read the words. The supervision is of auxiliary personnel — people. The presence is a person's presence, whether physically in the office suite or through real-time audio and video. Nothing in the regulation mentions software, and no AI tool can be the supervising practitioner, be immediately available in the office suite, or bill for the service. A practice that reasons "the system is monitoring the visit" has not satisfied a supervision condition. It has invented one, and the consequences of that invention land in claims that were billed under someone's number.
State scope-of-practice and supervision rules for physician assistants, nurse practitioners and medical assistants vary by state and are not covered here. Look yours up; 410.26(b)(7) makes state law part of the Medicare condition anyway.
Two other duties belong on the same page.
- Professional guidance (FSMB, adopted April 2024; guidance to state boards, binding only where a board adopts it): the physician "is ultimately responsible for the use of AI and should be held accountable for any harms that occur", "failure to apply human judgement to any output of AI is a violation of a physician's professional duties", and physicians "retain their duty to review records created with AI".
- Professional guidance (AMA House of Delegates, adopted 12 November 2024; advocacy, no legal duty): Policy 2(b) states that AI "cannot augment, create, or otherwise generate records, communications, or other content on behalf of a physician without that physician's consent and final review", and Policy 1(g) asks for specified qualified human intervention points, a qualified human being a licensed physician able to provide the same service without AI.
A question to sit with
Your list says the practice never lets AI make clinical decisions. Name the setting, permission or required signature that would stop it happening tomorrow. If the answer is the sentence itself, the sentence is all you have.
What goes wrong
The slogan list. "We always keep a human in the loop" is not a control. It cannot be audited, it cannot be tested, and it cannot be broken visibly, which means nobody ever finds out it failed.
The tool treated as a supervisor. A practice reads a monitoring feature as satisfying direct supervision and schedules accordingly. The regulation requires a practitioner's presence, physical or real-time audio and video, and only the supervising practitioner may bill.
The auto-accept. A drafted note, letter or reply files itself if nobody acts within a set period. The output then carries a clinician's name with no consent and no final review, which is precisely what AMA Policy 2(b) describes as unacceptable and what FSMB describes as a failure to review records created with AI.
The shared login. Two or three staff work under one account, so the audit trail cannot say who performed the step. 45 CFR 164.312 makes unique user identification a Required implementation specification, and a list that depends on knowing who acted cannot survive a shared account.
The suggestion that becomes the decision. A coding suggestion appears next to an encounter and is accepted routinely. The final code belongs with the clinician's documentation and the coding professional who assigns it; OIG's 2000 guidance lists upcoding, defined as "billing for a more expensive service than the one actually performed", among the conduct most often investigated, and it makes no difference to that list whether a person or a product proposed the code.
The management company holding the switch. A group office configures defaults, sets who may mark something reviewed and chooses retention periods. If the practice cannot say what was configured or on whose judgement, a non-delegable item has quietly been delegated.
The list nobody tests. A non-delegable list only proves itself the first time someone senior is told no and it holds. A practice with five AI tools and no recorded refusal in a year has a paragraph, not a programme.
The practical answer
Write six items, each as a control rather than a sentence. These are this programme's recommendations; adapt them to your state, your payers and your systems.
| Nobody may delegate | The control that makes it real |
|---|---|
| The clinician's diagnosis, orders and treatment decisions | No tool output is saved into the record as a finding; the clinician enters or edits and authenticates |
| Signing or authenticating the note | No auto-accept, no timed filing, no account other than the clinician's able to authenticate |
| The final code and the decision to submit a claim | The coding professional confirms the code against what the clinician documented; submission requires a person to act |
| A patient communication conveying clinical information | Routed to a licensed clinician before sending; non-clinical roles cannot send from the clinical template set |
| Supervision of auxiliary personnel for incident-to billing | The supervising practitioner is present in the office suite, or present through real-time audio and video where permitted, and is the one who bills |
| Approving, restricting or withdrawing an AI tool | Recorded by the AI programme owner with a date; a supplier or group office recommendation is an input, never the decision |
Convert each item with four questions. For every line, ask: what configuration enforces it; what would show it had been bypassed; who is notified when it is; and what the practice does in the meantime if the software cannot enforce it. The fourth question is the honest one. Where a system cannot enforce a rule, the practice records the gap, names an interim control such as a weekly check of a named report, and treats closing it as a purchasing requirement at renewal.
Test the list by trying to break it. Take a fictionalised item through each route and record what happened.
| Test | What you are looking for |
|---|---|
| Ask a non-clinical account to send from a clinical template | A refusal, not a warning that can be clicked past |
| Leave a drafted note untouched past the timeout | Nothing files; a task appears for the clinician |
| Have a second staff member log in as a colleague | Impossible, because identifiers are unique |
| Submit a claim where the suggested code exceeds what is documented | A stop before submission, with a named person notified |
| Ask the supplier to change a default without practice approval | A contractual and practical refusal, and a record of the request |
Keep a refusal log. One line each: what was proposed, which item it hit, who refused it, the date. Three entries in a year in a practice running several tools is a working programme. Zero entries usually means the list is unread rather than unbroken.
Remember this
- 42 CFR 410.26 requires supervision of auxiliary personnel by a practitioner, allows virtual presence only through real-time audio and video for eligible services, and lets only the supervising practitioner bill; software cannot meet it.
- FSMB describes the physician as ultimately responsible for AI use and as retaining the duty to review records created with AI; AMA Policy 2(b) asks for consent and final review before AI generates content on a physician's behalf.
- Write six non-delegable items as controls: a configuration, a permission or a required signature, never a sentence.
- Unique user identification is Required at 45 CFR 164.312; shared logins destroy the evidence a list depends on.
- Test the list by trying to break it, and keep a refusal log with a date on every line.
Medical practice example
Meridian Street Dermatology is a fictional practice with two physicians, one physician assistant, three medical assistants and a two-person front office. It bills Medicare, and some visits by the physician assistant are billed incident-to. The practice has a one-page AI policy whose non-delegable list reads, in full, that AI never makes clinical decisions and a human always reviews. The administrator, Delia Mbeki, tests it rather than admiring it. She asks a front-desk account to send a message from the clinical template set. It sends. She leaves a drafted visit note untouched overnight; at 2am it files itself under Dr Aurelio Vance name, because the vendor default accepts a draft after eighteen hours of inactivity. She asks a medical assistant to log in as a colleague; it works, because the two share an account created when one was covering maternity leave. She finds a fourth thing she was not testing for: the clinic schedules the physician assistant on Thursday afternoons when both physicians are at the satellite site, and somebody has reasoned that the documentation system flags anything unusual, so supervision is covered. Delia writes four findings and takes them to the partners. The first three are configuration problems with owners and dates. The fourth is not a configuration problem at all: 42 CFR 410.26 requires supervision by the practitioner and only the supervising practitioner may bill, and a system that flags things is not a person present in the office suite or present through real-time audio and video. The partners change the Thursday schedule the same week and ask their billing lead to review how those encounters were billed, with counsel. Delia then rewrites the list as six controls. The auto-accept is switched off and the vendor confirms in writing that the default cannot be reinstated without the practice approval. The shared account is split, which takes an afternoon and two arguments. The clinical template set is locked to clinician accounts. A refusal log is started, and its first entry is Dr Vance own request for a shortcut that would let his medical assistant close his drafted notes at the end of clinic. The refusal is recorded with a date and a two-line reason, and it is the entry Delia is most pleased with, because it is the one that proves the list survives contact with a busy physician.
Responsible-use warning
Never let a tool appear to supply supervision, review or identity. A monitoring feature is not a practitioner present in the office suite or present through real-time audio and video, and only the supervising practitioner may bill an incident-to service. A timeout that files a draft is not consent and final review. A shared login destroys the record of who performed the step, which 45 CFR 164.312 addresses by making unique user identification Required. Each of these fails silently and each is fixed in configuration rather than in a policy sentence. Check your own state supervision rules as well; 42 CFR 410.26(b)(7) makes state law part of the Medicare condition.
Human-review requirement
The treating clinician owns every clinical output, the content of the record and its authentication, and the supervising practitioner owns the supervision on which an incident-to claim depends; neither is transferable to a tool, a supplier or an administrator. The coding professional assigns the final code from what the clinician documented, and a named person acts before any claim is submitted. The AI programme owner records every approval, restriction and withdrawal with a date. The owner checks that each non-delegable item has an enforcing configuration or a written interim control, that the list has been tested rather than only published, and that the refusal log is current.
Practical exercise
Use a fictional practice or your own, with no patient information.
- Write your practice current non-delegable list exactly as it stands, however short.
- For each line, ask the four questions: what configuration enforces it, what evidence would show a bypass, who is notified, and what interim control applies where the software cannot enforce it. Answer honestly and leave blanks where there is nothing.
- Rewrite the list as six controls, each naming a setting, a permission, a required signature or a named report.
- Run the five break tests from the lesson. Record what actually happened, not what should have happened.
- Open the user administration screen of every AI-touching system. List each account, its role, and whether any login is shared. Mark every account able to authenticate, approve, send or submit.
- Find every timeout, auto-accept or default that would let an output be filed or sent without a named person acting. Write the configuration change that removes each one and who will make it.
- If the practice bills incident-to, write down the supervision arrangement for each session, the state rule you are relying on with its citation, and confirm that a person rather than a system meets it.
- List any default a supplier or group office set that touches one of your six items. Write the question you will put to them and the date you will put it.
- Start a refusal log with four columns: what was proposed, which item it hit, who refused it, the date. Enter anything from the last year you can evidence, and nothing you cannot.
- Name the one item you are least confident would hold under pressure, and write the two sentences you would say to the most senior person in the practice when enforcing it.
Knowledge check
-
What does 42 CFR 410.26 require for incident-to services, and why can no AI tool satisfy it?
Answer guidance: It generally requires services and supplies to be furnished under the direct supervision of the physician or other practitioner, with designated care management and behavioral health services by auxiliary personnel allowed under general supervision, and provides that only the supervising practitioner may bill Medicare for incident-to services. The presence may include virtual presence through real-time audio and video excluding audio-only for services without a 010 or 090 global surgery indicator. The supervision is of people by a practitioner, so software cannot be present, supervise or bill.
-
What is the difference between a slogan and a control on a non-delegable list?
Answer guidance: A slogan such as keeping a human in the loop cannot be audited, tested or visibly broken, so a failure goes unnoticed. A control names the thing that enforces it: a permission removed, a template set restricted to clinician accounts, an auto-accept switched off, a signature required before submission, or a named report checked weekly where software cannot enforce the rule. Each control also names what evidence would show a bypass and who is notified.
-
Why does a shared login defeat a non-delegable list, and what does HIPAA say about it?
Answer guidance: A list that reserves an action to a qualified person depends on the record showing who performed the action, and a shared account makes that impossible while also letting anyone act in another person name. 45 CFR 164.312 makes unique user identification a Required implementation specification and includes audit controls and person or entity authentication among the technical safeguards, so the fix is technical rather than a policy reminder.
-
What do FSMB and AMA policy say about a drafted note that files itself when nobody acts?
Answer guidance: FSMB policy adopted in April 2024 states that physicians retain their duty to review records created with AI and that failure to apply human judgement to any AI output is a violation of a physician professional duties. AMA House of Delegates policy adopted on 12 November 2024, at Policy 2(b), states that AI cannot generate records, communications or other content on behalf of a physician without that physician consent and final review. Both are guidance rather than law, and both describe a timed auto-accept as unacceptable.
Sources and further reading
- Centers for Medicare & Medicaid Services (CMS), HHS (eCFR) — 42 CFR 410.26 Services and supplies incident to a physician's professional service: Conditions. Accessed 2026-09-15.
- Federation of State Medical Boards — Navigating the Responsible and Ethical Incorporation of Artificial Intelligence into Clinical Practice. Accessed 2026-09-15.
- American Medical Association (AMA), House of Delegates — Augmented Intelligence Development, Deployment, and Use in Health Care (AMA Board of Trustees report and policy adopted November 12, 2024) (2024-11-12). Accessed 2026-09-15.
- 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.
- U.S. Department of Health and Human Services, Office of Inspector General (HHS-OIG) — OIG Compliance Program Guidance for Individual and Small Group Physician Practices (65 FR 59434, October 5, 2000) (2000-10-05). Accessed 2026-09-15.
- AI Coalition Network — Certification Educational Standard: Human Review of AI-Assisted Professional Work. Accessed 2026-09-15.