Staff trained on the AI policy
A policy nobody has read changes nothing. Completion by role shows real coverage.
Providers are trialing ambient documentation tools, the EHR vendor is switching on AI features, and front-desk staff have found that a chatbot writes a decent appeal letter. Some of this is useful. Some of it means protected health information is being pasted into tools with no business associate agreement and unknown retention. Most practices have no written position yet.
We would help you write a short, practical AI use policy: which tools are approved and for what, what data may go into them, who reviews AI output, and how new requests get evaluated. The medical director and compliance lead approve it, and we help train staff so the rules are followed rather than filed.
Run a short, no-blame survey and review software subscriptions and browser extensions to find which AI tools providers and staff already use and for what.
Separate low-risk uses with no patient data, such as drafting a job post, from uses involving protected health information or clinical content, which need a BAA and closer review.
Draft a two- or three-page policy covering approved tools, prohibited data, required human review of output, and how to request a new tool, written for staff rather than lawyers.
Create a standard checklist for AI vendors covering BAA, data retention, training use, access controls, audit logs and how output is documented in the chart.
Run a short session for each role with real examples, then review the approved list and any incidents every quarter as tools and regulations change.
How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
A policy nobody has read changes nothing. Completion by role shows real coverage.
The gap between tools in use and tools reviewed is the practice's actual exposure.
If reviews take months, staff will route around the policy. A short, predictable answer keeps people asking.
For example, in an illustrative six-provider family medicine practice, two physicians start using different ambient scribe apps they found online, and a medical assistant has been drafting prior authorization letters in a free chatbot. The practice pauses both, inventories use and runs a vendor review. One scribe product with a BAA is approved for a structured pilot, the free chatbot is barred for patient data, and an enterprise AI assistant is approved for non-clinical drafting.
In the first 30 days we would run the AI use survey, review subscriptions and EHR settings, and meet the medical director and privacy officer to agree risk categories. By day 30 the practice would have a draft policy, an initial approved tool list and a vendor checklist.
A ban is easy to write and hard to enforce, and it tends to push use out of sight. A short policy that approves a few safe tools and clearly prohibits patient data in everything else usually works better. It gives staff a legitimate option and gives leadership visibility into what is actually being used.
Usually a small group: the medical director or a physician lead for clinical uses, the practice administrator for operations, and the privacy or compliance officer for data handling. We would act as the technology lead who prepares vendor reviews and recommendations, but the decisions sit with practice leadership.
It may apply to some uses, particularly where AI informs significant decisions about patients or employees, and details continue to evolve. We do not give legal advice. We would flag uses that look likely to fall in scope and document them so your counsel can make the call with full information.
Illustrative defaults for a medical practice. Replace them with your numbers.
a month in staff time, before any lost sales
Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.
AI usage policy and governance: full guide
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.