Mississippi Artificial Intelligence Network

Healthcare AI Policy Template for Practices, Clinics, and Hospitals

A complete model policy on AI use for health care organizations that you can adapt, with the decisions you need to make marked, an editable copy, and guidance on what belongs in procedures and clinical protocols.

It covers protected health information, clinical review, decision support and nondiscrimination, FDA-regulated tools, patient communication, coding and billing, AI agents, and incident reporting. It becomes your policy only when your organization approves it.

Read the model policy Download editable copy (.docx)

Who it serves
Practice owners and administrators, physician and nursing leaders, privacy and security officers, compliance, clinical informatics, and hospital leadership.
What you get
A 16-section model policy, an editable copy, a five-step adoption process, Mississippi and federal context, and an implementation checklist.
How to use it
Fill in each bracketed decision, remove what does not fit, have health care counsel and clinical leadership review it, and approve it through your usual process.

01 · Start here

Use the model at the level that fits your organization

Most of the law that governs AI in health care already applies to your organization. HIPAA governs protected health information, Section 1557 prohibits discrimination, FDA regulates medical devices, and professional standards keep clinicians responsible for care. An AI policy states how those duties apply to AI tools and who decides what.

Keep the policy short and durable. Tool lists, validation steps, and workflow rules change often, so they belong in procedures and clinical protocols that leaders can update without reapproving the policy.

Three starting points
If your organization isStart withAdd when you are ready
A small practice: a few clinicians, no dedicated IT or compliance staffSections 1 to 8, 11, 15, and 16. The practice administrator and a physician leader serve as AI lead with your HIPAA privacy and security officers. Approve only tools covered by a business associate agreement for any protected health information.Section 9 before clinical AI such as documentation tools, Section 10 before decision support tools, Section 12 before coding or billing AI, and Section 14 before automations or agents.
A clinic or group practice using AI in daily workThe full model, with a small committee and an inventory that includes AI features in your electronic health record.Routine checks of tool accuracy and patient notices for patient-facing tools.
A hospital or health systemThe full model, connected to medical staff governance, quality and patient safety, and compliance.Regular performance and bias review of decision support tools, and a check of your program against the Joint Commission and CHAI guidance under Federal law and guidance.

How to read this page

Law
A statute or regulation. Ask your counsel how it applies to your organization.
Official guidance
Advice or policy from a government agency. It informs decisions but does not itself create legal duties.
MAIN recommendation
A practice MAIN suggests. Your organization decides whether to use it.
[Local decision]
A choice your organization must make or a name it must fill in.

02 · Model policy

Model health care policy on the use of AI

The model below is a MAIN recommendation for adaptation. Where a provision repeats a legal obligation, the obligation comes from the law cited in the legal references, not from this model.

MAIN model for adaptation

Model Health Care Policy: Use of Artificial Intelligence

[Organization name]

Policy [number]: Use of Artificial Intelligence

Approved by [governing body, owner, or chief executive]. Effective [date]. Last reviewed [date].

Drafting notesThis is a model for local adaptation. It is not an adopted policy, legal advice, or a requirement from MAIN or any state or federal agency. Text in brackets marks a decision your organization must make or a name to fill in. Remove any provision you will not use. Have qualified health care counsel, your privacy and compliance officers, and clinical leadership review the final draft before approval. Drafting notes explain options. Delete them before adoption.

1. Purpose

[Organization name] (the Organization) uses artificial intelligence (AI) to support patient care, documentation, patient access, and operations. AI use also creates risks to patient safety, privacy, fairness, accuracy, and compliance. This policy sets the rules for using AI in the Organization’s work. Procedures and clinical protocols issued under this policy set the details.

2. Scope

This policy applies to all workforce members, [Local decision: including members of the medical staff, contractors, students and trainees, and volunteers], when they use AI for the Organization’s work, on its devices or networks, or with its information. It covers stand-alone AI tools, AI features inside the electronic health record and other software the Organization uses, AI-enabled medical devices, and AI agents.

3. Definitions

  1. Artificial intelligence. [Local decision: Use the definition in Mississippi law, shown here, or adopt your own.] “Artificial intelligence” means a machine-based system that can, for a given set of human-defined objectives, make predictions, recommendations or decisions influencing real or virtual environments. Artificial intelligence systems use machine- and human-based inputs to perceive real and virtual environments; abstract such perceptions into models through analysis in an automated manner; and use model inference to formulate options for information or action. (House Bill 1723, 2026 Regular Session, codified in Chapter 3, Title 1, Mississippi Code of 1972.)
  2. AI tool means any software, service, device, or product feature that uses artificial intelligence to generate content, analyze information, make predictions or recommendations, or take actions.
  3. AI agent means an AI tool that can take actions in other systems on its own, such as sending messages, scheduling, changing records, placing orders, or running code.
  4. Approved AI tool means an AI tool the Organization has approved under Section 7 for a stated purpose, group of users, and category of information.
  5. Protected health information has the meaning given in the HIPAA Rules, 45 C.F.R. § 160.103. Confidential information means protected health information and [Local decision: the other categories in the Organization’s data classification policy].
  6. Patient care decision support tool means a tool used to support clinical decision-making, as the term is used in the Section 1557 rule, 45 C.F.R. Part 92.
  7. Higher-risk use means any AI use that (1) informs diagnosis, treatment, triage, or another clinical decision; (2) creates or changes content in the medical record; (3) communicates with patients without a qualified person reviewing each message first; (4) processes protected health information; (5) informs coverage, utilization review, coding, or billing; (6) informs an employment decision; or (7) allows an AI agent to act for the Organization.

4. Principles

The Organization’s use of AI will:

  • put patient safety first;
  • keep licensed clinicians responsible for clinical decisions;
  • protect the privacy and security of health information;
  • avoid discrimination and watch for unequal effects on patient groups;
  • be explained to patients and staff in plain language;
  • rest on evidence that a tool works for its purpose and for the Organization’s patients; and
  • use controls that match the level of risk.

5. Responsibilities

  1. [Local decision: The chief executive or practice owner] will designate [Local decision: an AI lead or an AI governance committee] to maintain procedures under this policy, keep the inventory of approved AI tools, approve higher-risk uses, coordinate training, and coordinate the response to AI-related incidents.
  2. [Local decision: Clinical leadership or the medical staff] will approve clinical uses of AI and the clinical protocols for them.
  3. The privacy officer and security officer will review AI tools that use protected health information.
  4. Managers will make sure their teams follow this policy and its procedures.
  5. Each workforce member is responsible for any work they produce, send, sign, or approve with AI assistance.
Drafting noteA small practice can assign these duties to the practice administrator, one physician leader, and the privacy and security officers it already has under HIPAA. A hospital or health system can use a committee that includes clinical leadership, nursing, the medical staff, privacy, security, compliance, quality and patient safety, clinical informatics, and legal.

6. Permitted, approved, and prohibited uses

  1. Permitted. Workforce members may use approved AI tools for drafting, summarizing information that is not confidential, education, research, and routine administrative tasks, subject to Sections 8 through 15.
  2. Permitted with approval. Any clinical use, any use of protected health information, any other higher-risk use, and any AI tool that is not yet approved require approval under Section 7 before use begins.
  3. Prohibited. No one may use AI for the Organization’s work to:
    1. enter protected health information or other confidential information into an AI tool that is not approved for that category of information;
    2. make a diagnosis, treatment, or coverage decision based solely on AI output;
    3. place AI-generated content in the medical record without review by the responsible clinician;
    4. use an AI-enabled medical device outside its authorized intended use without [Local decision: review and approval by clinical leadership];
    5. create false or misleading content, including fake reviews or images, audio, or video that falsely depict a real person;
    6. get around the Organization’s security controls or technology use policies; or
    7. [Local decision: add any other prohibited uses the Organization chooses].

7. Review and approval of AI tools

  1. Before an AI tool is approved, [the AI lead or committee] will review at least:
    1. the clinical or business purpose and the evidence that the tool serves it;
    2. whether the tool is an FDA-regulated medical device and, if so, its authorized intended use;
    3. how the tool performs for the Organization’s patient population and settings, and the plan to test it before and after go-live;
    4. what information the tool uses, whether a business associate agreement is required, and whether the vendor may use the Organization’s data to train or improve its products;
    5. security, including access controls, multifactor authentication, logging, and how the vendor reports incidents;
    6. for a patient care decision support tool, whether it uses input variables or factors that measure race, color, national origin, sex, age, or disability, and how any risk of discrimination will be mitigated;
    7. the vendor’s documentation of how the tool was developed, tested, and is meant to be used;
    8. accessibility for patients and workforce members with disabilities; and
    9. for an AI agent, the actions it may take, its limits, how its actions are logged, and who can stop it.
  2. This review also applies when the electronic health record or other software the Organization uses adds AI features.
  3. The Organization will keep an inventory of approved AI tools showing each tool’s purpose, users, categories of information, regulatory status, owner, and next review date.
  4. Approval may be limited, paused, or withdrawn when a tool does not perform as expected, harms patients, or no longer meets these requirements.

8. Privacy and security of health information

  1. Protected health information may be entered only into AI tools approved for it. When a vendor creates, receives, maintains, or transmits protected health information for the Organization, a business associate agreement is required before use.
  2. Workforce members will use the minimum necessary protected health information for the task.
  3. Information treated as de-identified must meet the HIPAA de-identification standard in 45 C.F.R. § 164.514.
  4. AI tools that use electronic protected health information will be included in the Organization’s HIPAA security risk analysis and risk management.
  5. Because AI can imitate voices, video, and writing, workforce members must confirm unusual requests for payments, credentials, or patient information through a separate, known contact method before acting on them.

9. Clinical use and patient safety

  1. AI may support, but not replace, the judgment of licensed clinicians acting within their scope of practice. The treating clinician remains responsible for clinical decisions.
  2. AI-generated clinical documentation, including notes drafted from recorded visits, must be reviewed and corrected by the responsible clinician before it is signed. [Local decision: State whether and how the record notes that AI assisted.]
  3. Clinical AI tools will be tested for the Organization’s patients and settings before use and monitored after go-live for accuracy, safety, and changes in performance. A tool that does not perform as expected will be suspended until it is reviewed.
  4. AI-enabled medical devices will be used consistent with their FDA authorization and intended use, and updates will be managed consistent with the manufacturer’s instructions.
  5. [Local decision: State whether and when patients are told that AI supported their care, and how they may ask questions.]

10. Nondiscrimination

  1. The Organization will not discriminate on the basis of race, color, national origin, sex, age, or disability through its use of patient care decision support tools, including AI.
  2. The Organization will make reasonable efforts, on an ongoing basis, to identify patient care decision support tools that use input variables or factors that measure race, color, national origin, sex, age, or disability.
  3. For each tool identified, the Organization will make reasonable efforts to mitigate the risk of discrimination and will document those efforts.
  4. [The Section 1557 coordinator or compliance officer] will coordinate this work.
Drafting noteThese provisions track 45 C.F.R. § 92.210, which applies to covered entities under Section 1557, including recipients of federal financial assistance. Confirm with counsel whether your organization is covered. The provisions are a sound practice even where they are not required.

11. Patient communication

  1. AI tools that communicate with patients, such as chat or messaging tools, will [Local decision: tell patients they are interacting with AI], give patients a way to reach a qualified person, and be monitored for accuracy and safety.
  2. AI may draft individual clinical advice only within an approved clinical workflow. A qualified clinician must review and approve each proposed message before it is sent. Approval of the tool or workflow does not replace that review.
  3. Patient-facing content created with AI will be reviewed for accuracy, readability, and accessibility before it is published.

12. Coverage, coding, and billing

  1. AI may assist with utilization review, coding, and billing, but a qualified person must review AI output before a claim is submitted or a decision is made to deny, delay, or change care.
  2. Coverage and medical necessity decisions will be based on the individual patient’s circumstances.
  3. [Local decision: For Medicare Advantage organizations only.] Coverage determinations will follow 42 C.F.R. § 422.101(c), and an algorithm or AI tool will not be the sole basis to deny admission, downgrade to an observation stay, or end post-acute care.

13. Employment and human resources

  1. AI may assist with employment decisions, including credentialing support, but may not be the sole basis for them.
  2. AI tools used in recruiting, hiring, scheduling, evaluation, discipline, or termination are higher-risk uses and will be reviewed for job-relatedness, effects on groups protected by law, and accessibility before use.
  3. Applicants and employees may ask for a reasonable accommodation or [Local decision: an alternative process] when an AI tool is part of an employment process.

14. Software, automations, and AI agents

  1. Scripts, applications, integrations, low-code workflows, and agents created with AI must meet the Organization’s software, data, and change-control requirements before they use confidential information, receive privileged access, are shared, or are relied on for operations.
  2. An AI agent may act for the Organization only within the systems, information, actions, and limits approved under Section 7, and each agent will have a named person who is responsible for it and can stop it.
  3. A qualified person must review and approve each proposed order, medication change, individual clinical message, claim submission, or other consequential action before execution. Approval of the agent, its access, or its workflow does not replace that review.
  4. Agent actions will be logged and reviewed [Local decision: at a set frequency].

15. Incidents and reporting

  1. Workforce members must report AI-related incidents promptly to [office or person]. Incidents include patient harm or near misses, exposure of protected health information, inaccurate records, discriminatory output, unauthorized AI use, and fraud attempts that use AI.
  2. Incidents will be handled through the Organization’s patient safety, privacy, and security incident processes, including breach notification under the HIPAA Breach Notification Rule and Mississippi law where they apply.
  3. Where a medical device may have caused or contributed to a death or serious injury, the Organization will follow FDA’s medical device reporting requirements for user facilities where they apply.

16. Training, compliance, and review

  1. The Organization will provide training on this policy before workforce members use AI for its work. Training covers approved tools, rules for protected health information, checking AI output, recognizing AI-enabled fraud, and reporting incidents. Workforce members must complete [Local decision: the required training] before any higher-risk use.
  2. Violations of this policy may result in [Local decision: discipline under the Organization’s usual procedures and, for medical staff, under the medical staff bylaws].
  3. [The AI lead or committee] will review this policy at least [Local decision: once a year] and when relevant law, tools, or services change, and will report to [governing body, owner, or chief executive] on approved tools, incidents, and recommended changes.

Legal references

Legal references. [Local decision: Confirm with counsel and keep only those that apply.]

  • HIPAA Privacy, Security, and Breach Notification Rules, 45 C.F.R. Parts 160 and 164
  • Section 1557 of the Affordable Care Act, 42 U.S.C. § 18116; 45 C.F.R. § 92.210
  • Federal Food, Drug, and Cosmetic Act, Section 520(o), 21 U.S.C. § 360j(o); Medical Device Reporting, 21 C.F.R. Part 803
  • Medicare Advantage coverage determinations, 42 C.F.R. § 422.101 (Medicare Advantage organizations only)
  • Title VII of the Civil Rights Act of 1964, 42 U.S.C. § 2000e et seq.; Americans with Disabilities Act, Title I, 42 U.S.C. § 12111 et seq.
  • Section 75-24-29, Mississippi Code of 1972 (notice of breach of security)
  • House Bill 1723, 2026 Regular Session (definition of artificial intelligence)

Cross-references: [HIPAA privacy and security policies; data classification; business associate management; medical staff bylaws; clinical documentation; patient safety event reporting; compliance and billing; technology acceptable use; procurement]

Get the editable copy

The download contains the same model policy, with every decision highlighted. Save a working copy in your organization’s approved editor before you change it.

Download model policy (.docx) Plain-text version (.txt)

Next, record each choice with MAIN’s Adapt and Adopt companion and decision worksheet.

03 · Document structure

What goes in policy, procedures, and clinical protocols

Separate documents let the policy stay stable while procedures and protocols keep pace with new tools. Where a rule is already set by law, accreditation standards, or medical staff bylaws, point to it rather than restate it.

Four document types
DocumentUsually approved byWhat belongs there
Organization policyThe governing body, owner, or chief executivePurpose, scope, authority, boundaries, responsibilities, and review. The model policy above.
ProceduresThe AI lead or committee, with the privacy and security officersThe approved-tool inventory, business associate agreement checks, the review checklist, rules for each category of information, incident steps, and training requirements.
Clinical protocolsClinical leadership or the medical staffHow a specific tool is used in a clinical workflow, what the clinician must check before signing, and when the tool must not be used.
Implementation adviceNot adoptedRecommended practices, examples, and pitfalls, such as the guidance and checklist on this page.

Keep tool names out of the policy. A rule such as “clinicians may use a named documentation tool in primary care visits” belongs in a clinical protocol. The policy should say only that approved tools are listed and who approves them.

04 · Adapt and adopt

Five steps from template to approved policy

  1. Name an owner

    Choose who drafts the policy and who signs off. Include a clinical leader and your HIPAA privacy and security officers from the start.

  2. List the AI already in use

    Include AI features in your electronic health record, practice management, imaging, and patient messaging systems, and any personal AI accounts staff use for work. The list shows which provisions you need now.

  3. Make each decision

    Fill in every bracketed decision and delete provisions you will not use. Record why you chose each option with the Adapt and Adopt decision worksheet.

  4. Review and approve

    Have health care counsel, compliance, and clinical leadership review the draft, especially Sections 8 through 12. Then approve it through your usual process, including medical staff approval where your bylaws require it.

  5. Put it to work

    Publish the approved-tool inventory, train the workforce, add AI questions to purchasing and business associate reviews, and set the date for the first review.

05 · Mississippi context

What applies in Mississippi

Mississippi health care organizations set their own AI rules within existing law. MAIN does not regulate AI use and does not set state AI policy. [5]

Law State definition of artificial intelligence

House Bill 1723 of the 2026 Regular Session defines artificial intelligence in Mississippi law, effective July 1, 2026. It sets a definition only. The model policy offers it as an option in Section 3. [1]

Law Notice of a data breach

Section 75-24-29 of the Mississippi Code requires notice to affected Mississippi residents, without unreasonable delay, after unauthorized acquisition of certain unencrypted personal information, such as a name combined with a Social Security number, driver’s license number, or financial account number with its access code. [3] It applies alongside the HIPAA Breach Notification Rule. Ask counsel how the two apply to an incident involving an AI tool.

Health care AI bills in the 2026 session

Three 2026 House bills on AI in health care died in committee on February 3, 2026. House Bill 1717 would have required disclosure in the medical record when AI materially contributes to a diagnosis, treatment plan, order, or clinical note, required clinician review and approval of that output, and prohibited automated denial or delay of coverage. House Bills 1720 and 1048 would have prohibited AI in professional mental and behavioral health care, with exceptions for administrative support. [2] Similar proposals may return. Sections 9 and 12 of the model policy already address these topics.

Official guidance The ITS AI Acceptable Use Policy

The Mississippi Department of Information Technology Services (ITS) approved an AI Acceptable Use Policy on November 25, 2025. State agencies, including state-operated health entities, should confirm with ITS how it applies to them. Its rules, such as human review of AI output and no confidential data in unapproved tools, are a useful benchmark for private organizations too. [4]

Legislative study

The Artificial Intelligence Regulation (AIR) Task Force, created by Senate Bill 2426 in 2025, studies AI policy and reports to the Legislature. [6]

For the wider picture, see Who sets AI policy in Mississippi.

06 · Federal law and guidance

Federal law and guidance to check

These federal sources bear on the uses the model policy covers. Several changed in 2025 and 2026. Confirm current status with counsel before you rely on them.

Federal sources that bear on AI in health care
SourceTypeWhat it means for AI use
HIPAA Privacy, Security, and Breach Notification RulesLawGovern protected health information in AI tools. HHS guidance says a cloud service provider that creates, receives, maintains, or transmits electronic protected health information for a covered entity is a business associate, even if it stores only encrypted data and has no key, and a business associate agreement is required. Breach notice to individuals is due without unreasonable delay and no later than 60 days after discovery. [7] HHS proposed Security Rule updates on January 6, 2025. The existing Security Rule remains in effect while the proposal is pending. A rulemaking-agenda target is not an effective or compliance date; confirm any later final action directly with HHS. [8]
Section 1557 of the Affordable Care Act, 45 C.F.R. § 92.210LawProhibits covered entities from discriminating on the basis of race, color, national origin, sex, age, or disability through patient care decision support tools. Covered entities must make reasonable efforts to identify tools that use input variables measuring those characteristics and to mitigate the risk of discrimination. The identification and mitigation duties applied from May 1, 2025. An HHS notice of June 2, 2026 lists the provisions of the 2024 rule vacated in Tennessee v. Kennedy (S.D. Miss.); § 92.210 is not among them. [9]
FDA: device software and clinical decision supportLaw and official guidanceSome clinical decision support software is excluded from the medical device definition if it meets four statutory criteria, including that a health care professional can independently review the basis for its recommendations. FDA’s final guidance, issued January 6, 2026 and reissued January 29, 2026, says software intended for patients rather than health care professionals does not meet the criteria, and that software supporting time-critical decisions, such as alarms for life-threatening conditions, generally does not. FDA keeps a list of authorized AI-enabled devices, has final guidance on predetermined change control plans, and has draft lifecycle guidance from January 2025. [10] [11]
FDA Medical Device Reporting, 21 C.F.R. Part 803LawFor a covered device user facility, a suspected device-related death is reported to FDA and the manufacturer within 10 work days of becoming aware. A device-related serious injury is reported to the manufacturer within 10 work days, or to FDA if the manufacturer is unknown. Covered facilities also have annual reporting requirements. The definition includes specified facilities and excludes physician offices. Confirm the facility, event, awareness date, and pathway under 21 C.F.R. Part 803. [12]
ASTP/ONC health IT certification (HTI-1 and HTI-5)Certification rules; HTI-5 revisions effective December 28, 2026Certification requirements apply to developers of certified health IT and affect the information vendors provide about decision support. HTI-5 was published on October 28, 2026. Effective December 28, 2026, amendatory instruction 11(g) removes the source-attribute and intervention risk management requirements in 45 C.F.R. § 170.315(b)(11)(iv) through (vi). Those provisions remain in effect until that date. Confirm the vendor’s certification obligations and any contractual commitments for the specific tool. Clinical evaluation, safety, privacy, and human review still need their own assessment. [13]
CMS guidance on Medicare Advantage coverage decisions (February 6, 2024)Official guidanceAn algorithm or software tool may assist Medicare Advantage plans, but coverage decisions must rest on the individual patient’s circumstances. For inpatient admissions, algorithms or AI alone cannot be the basis to deny admission or downgrade to an observation stay, and a length-of-stay prediction alone cannot be the basis to end post-acute care. CMS did not finalize proposed AI guardrails in its April 2025 rule. [14]
Title VII, the ADA, and the ADEALawTitle VII and ADA Title I generally cover employers with 15 or more employees, subject to statutory coverage and counting rules. The ADEA generally covers private employers with 20 or more employees; state and local government employers are covered regardless of employee count. Falling below a threshold does not remove all federal duties. Section 1981 protects equal contracting rights against racial discrimination without Title VII’s employee threshold, and Equal Pay Act duties may also apply. Confirm the actual employing entity, exceptions, and available remedies with counsel. [15]
Executive Order 14365 (December 11, 2025)Executive order: federal executive-branch directionsExecutive Order 14365 directs federal officials to take specified actions concerning state AI laws. It is not itself a general exemption from applicable state law. An agency position, proposed policy statement, or filed lawsuit is not a judicial ruling that a particular state requirement is preempted. Confirm the controlling statute, final agency action, or court order for the actual issue. [16]

Voluntary framework Benchmarks for an AI program

The Joint Commission and the Coalition for Health AI released Responsible Use of AI in Healthcare on September 17, 2025. It describes seven elements: AI policies and governance structures; patient privacy and transparency; data security and data use protections; ongoing quality monitoring; voluntary, blinded reporting of AI safety-related events; risk and bias assessment; and education and training. [17] The NIST AI Risk Management Framework and its Generative AI Profile, NIST Cybersecurity Framework 2.0, NIST’s incident response guidance, and CISA’s Cross-Sector Cybersecurity Performance Goals can help organize the review in Section 7 and the security work in Section 8. [18]

07 · Guidance by topic

Guidance for procedures and clinical protocols

These notes are MAIN recommendations. Use them to write the procedures and protocols the policy calls for. Each topic lists the decisions to make and the pitfalls to avoid.

AI-drafted clinical documentation

Decide in protocols

  • Which visit types and settings may use documentation tools, and how patients are told when a visit is recorded.
  • What the clinician must check before signing, and whether the record notes AI assistance.

Common pitfalls

  • Signing AI-drafted notes without reading them, including invented findings or wrong medications.
  • Copying AI summaries forward without checking them against the source record.
Decision support, validation, and monitoring

Decide in procedures

  • How each clinical tool is tested on your patients before go-live, who reviews its performance after go-live, and what triggers suspension.
  • Which tools are FDA-regulated devices, and what their authorized intended uses are.

Common pitfalls

  • Using a tool outside the population or setting it was tested in.
  • Missing a vendor update that changed how a tool behaves.
  • Treating an alert or score as a finding rather than a prompt for clinical judgment.
Nondiscrimination and patient groups

Decide in procedures

  • How the Organization finds decision support tools that use race, color, national origin, sex, age, or disability as inputs, including tools built into the electronic health record.
  • What mitigation looks like for each tool, and where it is documented.

Common pitfalls

  • Assuming a vendor tool is unbiased without documentation.
  • Reviewing a tool once and never checking results across patient groups again.
Protected health information and vendors

Decide in procedures

  • Which tools may receive protected health information, confirmed against signed business associate agreements.
  • The AI questions added to every purchase and renewal: data use for model training, retention, subcontractors, security, and incident notice.

Common pitfalls

  • Pasting patient details into a public chatbot, or into a free version of a tool the Organization licenses under a business associate agreement.
  • Missing protected health information in uploaded images, documents, or free text.
  • Missing AI features that arrive through routine software updates.
Patient-facing tools

Decide in procedures

  • Which patient messages AI may draft, which a person must review before sending, and when a conversation must go to a person.
  • How patients are told they are interacting with AI.

Common pitfalls

  • Chat tools that give clinical advice with confidence and without review.
  • Patient materials that are inaccurate, hard to read, or inaccessible.
Coding, billing, and utilization review

Decide in procedures

  • Who reviews AI-suggested codes and claims before submission, and how accuracy is audited.
  • How individual review of each patient’s circumstances is documented in utilization decisions.

Common pitfalls

  • Letting AI suggestions become submitted codes without review.
  • Letting an algorithm effectively decide denials.
AI agents and automations

MAIN recommends treating any AI that can retrieve protected health information, draft chart content, place orders, message patients, or start workflow steps as higher risk than a chat assistant. Use approved environments, minimum necessary access, business associate agreements where required, action logs, tested stop conditions, and approval by a qualified person before any consequential action. The model policy covers this in Section 14. MAIN’s AI Agents Playbook covers planning and oversight in more depth.

Security and AI-enabled fraud

Decide in procedures

  • How staff confirm unusual payment, credential, or patient-record requests, given that AI can imitate a familiar voice or writing style.
  • How AI tools fit into the HIPAA security risk analysis, access controls, and incident response.

Common pitfalls

  • Assuming a model is safe because it runs on your own hardware.
  • Treating an AI error as ordinary user error when it may require patient safety review or breach analysis.

08 · Checklist

Implementation checklist

Before approval

  • Every bracketed decision is made and unused provisions are removed.
  • The policy names who approves AI tools, clinical uses, and higher-risk uses.
  • Counsel, compliance, and clinical leadership have reviewed the draft.

Before the workforce relies on AI

  • The approved-tool inventory shows which information each tool may receive and which tools are covered by a business associate agreement.
  • Clinical protocols exist for each clinical tool, including what the clinician checks before signing.
  • Decision support tools have been reviewed for inputs that measure protected characteristics.
  • The workforce knows what not to enter into AI tools and how to report a problem.

Within the first year

  • The workforce has completed training.
  • Clinical tools have had a performance review after go-live.
  • AI incidents are part of patient safety, privacy, and security incident processes.
  • The first policy review is scheduled.

09 · Prepare your team

Build skills while the policy moves forward

The policy asks clinicians and staff to check AI output and protect patient information. Training makes that workable.

MAIN resources for Mississippi health care teams

Questions about this template? Contact MAIN.

Sources and notice

Sources

Checked October 26, 2026. Laws and guidance change. Confirm current text with the source before relying on it.

  1. Law Mississippi Legislature, House Bill 1723, 2026 Regular Session, and bill history (approved March 9, 2026; Chapter 311; effective July 1, 2026).
  2. Law Mississippi Legislature, 2026 bill histories: House Bill 1717, House Bill 1720, and House Bill 1048 (each died in committee February 3, 2026).
  3. Law Mississippi Legislature, HB 277 (2021), §9, amending Mississippi Code §75-24-29 (tribal-ID amendment effective July 1, 2021). Read the full definitions, investigation and notice conditions, processor duties, and alternatives. Confirm the current codified text and any later amendments with counsel before relying on it.
  4. Official guidance Mississippi Department of Information Technology Services, AI Acceptable Use Policy information (approved November 25, 2025).
  5. MAIN Who sets AI policy in Mississippi.
  6. MAIN Mississippi AI Regulation Task Force (Senate Bill 2426, 2025 Regular Session).
  7. Official guidance U.S. Department of Health and Human Services, HIPAA for Professionals, Guidance on HIPAA and Cloud Computing, and Breach Notification Rule. Law: 45 C.F.R. Parts 160 and 164.
  8. Proposed rule HHS, HIPAA Security Rule NPRM, January 6, 2025; current HHS proposal information. Confirm later final action; an agenda target is not a compliance deadline.
  9. Law HHS, Nondiscrimination in Health Programs and Activities, final rule, May 6, 2024; 45 C.F.R. § 92.210; and Notice of Vacatur, June 2, 2026.
  10. Official guidance FDA, Clinical Decision Support Software final guidance (issued January 6, 2026; reissued January 29, 2026), and Guidances with Digital Health Content. Law: 21 U.S.C. § 360j(o).
  11. Official guidance FDA, AI-Enabled Medical Devices list, predetermined change control plan final guidance, and lifecycle management draft guidance, January 2025.
  12. Law FDA, Mandatory Reporting Requirements: Manufacturers, Importers and Device User Facilities. Law: 21 C.F.R. Part 803.
  13. Rules HTI-1 final rule, January 9, 2024; HTI-5 final rule, 91 Fed. Reg. 67916, October 28, 2026, DATES at p. 67916, § III.A.2.e at pp. 67940–67943, and amendatory instruction 11(g) at p. 67994. The decision-support revisions take effect December 28, 2026; amendatory instructions 7, 10, and 12 take effect January 1, 2027. See also ONC’s criteria-revision table.
  14. Official guidance CMS, FAQs related to coverage criteria and utilization management requirements in CMS final rule (CMS-4201-F), February 6, 2024 (copy hosted by the American Hospital Association); CMS, CMS-4201-F fact sheet; Skilled Nursing News, CMS Rule Fails to Put Restrictions on Medicare Advantage Plans’ AI Use, April 4, 2025 (analysis).
  15. Law and official explanation EEOC, Coverage of Business/Private Employers and Coverage of State and Local Governments; Supreme Court, Mount Lemmon Fire District v. Guido, November 6, 2018, opinion pp. 1 and 4-6; 42 U.S.C. §1981.
  16. Executive order Executive Order 14365, 90 Fed. Reg. 58499, December 16, 2025; The Regulatory Review, The Hidden Costs of AI Preemption, October 7, 2026 (analysis).
  17. Voluntary framework The Joint Commission and Coalition for Health AI, Responsible Use of AI in Healthcare, September 17, 2025, as summarized by Duane Morris; Joint Commission announcement.
  18. Voluntary framework NIST, AI Risk Management Framework and Generative AI Profile (NIST AI 600-1); Cybersecurity Framework 2.0; SP 800-61 Rev. 3; CISA, Cross-Sector Cybersecurity Performance Goals; FBI, Criminals Use Generative Artificial Intelligence to Facilitate Financial Fraud, December 3, 2024.

Notice

This healthcare AI policy template is a planning resource. It is not a final institutional policy, legal advice, medical advice, or a mandatory model. Adapt it to your organization’s mission, legal and regulatory environment, risk profile, people, data, systems, and operating context.

This template is offered as general information for consideration. It carries no warranty, and nothing in it states what any organization is required to do. Statements about law, regulation, and agency guidance may be incomplete or become outdated. Users remain responsible for their decisions and outcomes. MAIN and Mississippi Gulf Coast Community College accept no responsibility or liability for its use. See Legal Information.

Search MAIN

Courses, guides, news, and information.