How this playbook was built
Short version: the templates are drafted from published guidance (FSMB, AMA, the HIPAA security rule, NIST) and 2 state statutes, each read on 2026-11-12, then shaped around how an IME file moves through a practice. They are starting points to adapt with counsel, not tested compliance programs. Medrecords AI publishes the site and makes 1 of the tools a practice might approve.
Limits: This site gives templates and a process, not legal advice. We read the rules it cites on 2026-11-12; your state, your requesters' contracts and your counsel decide what your practice must do.
What the playbook is built from
- Professional guidance: the FSMB's April 2024 policy on AI in clinical practice, the AMA's November 2024 AI principles, and AMA Code of Medical Ethics Opinion 1.2.6 on IMEs.
- Federal rules: the HIPAA security rule sections on audit controls (164.312(b)), activity review and training (164.308) and documentation retention (164.316).
- Frameworks: the NIST AI Risk Management Framework 1.0, used for the structure of the policy.
- State statutes, used narrowly: Texas Business and Commerce Code 552.051 for the notice format, and California Labor Code 4628 for the workflow and report wording. This site does not survey state law.
- The search field: the Google top 10 for "ai for ime" and 4 related searches on 2026-11-12, read to see what existing pages already cover.
Each source is linked, with its capture date, in the table on the home page.
What we did not do
We did not run a practice through this playbook and measure the result, and we report no outcome figures. The set-up times on the home page are estimates and say so. The Ridgeview IME example and case RV-0412 are synthetic, labeled as such, and describe no real practice, patient or file. Nothing here is legal advice; templates touching state law are marked for review with counsel.
How we keep it current
We recheck every cited source at least every 45 days and date each change on the page. Health AI rules moved quickly in 2025 and 2026, so read any page more than 45 days past its update date with that in mind. Send corrections to aj@medrecords.ai.
Our conflict of interest, and how we handle it
This site is published by Medrecords AI, which makes 1 of the products it covers. A practice following this playbook will approve some record tool, and we would like it to be ours. We do not claim neutrality. These are the rules we follow:
- The playbook pages name no AI product. The templates work with any tool that meets the policy's conditions.
- Medrecords AI appears only on its own page and in boxes marked as ours, each saying where it fits and what it leaves to the practice.
- The Medrecords AI page lists what the product does not do and who should pick something else.
- Links to other organizations carry a nofollow attribute; links to medrecords.ai carry a source tag so we can see which visits came from here.
- Corrections that cut against us go live as fast as any other, within 2 business days.