Navard compass mark NAVARD
navard.ai  |  contact@navard.ai  |  916-214-7166
HIPAA 2026 Compliance · Aligned to NIST AI RMF

2026 AI Governance Checklist for Healthcare

A practical assessment and action framework for verifying your organization's AI systems against the 2026 HIPAA Security Rule.

Prepared by Navard LLC  ·  M.S. Cybersecurity  ·  CISM  ·  AIGP Candidate

For Chief Compliance Officers, CISOs, Privacy Officers, and Healthcare Security Teams

0 of 0 verified

How to use this checklist

Work through each section in order. Check each box when the control is verified — not when it is planned. Complete the AI Inventory Worksheet first; it is the foundation for every section that follows. This document constitutes a cybersecurity and AI governance assessment tool only. It does not constitute legal advice. Consult qualified legal counsel for regulatory compliance determinations.

SECTION 1 AI System Inventory Worksheet

Complete this section first. List every AI tool in use — approved by IT and shadow (unofficial). This is your compliance scope for all sections below.

Discovery instructions

Survey department heads, clinical leads, and IT. Ask specifically: (1) What AI tools does your team use for work, including personal subscriptions? (2) Has any AI tool been purchased or subscribed to without formal IT approval? (3) Does any staff member use a general AI assistant (ChatGPT, Copilot, Claude, Gemini) for work-related tasks involving patient data?

AI Tool NameVendorDept / OwnerData AccessBAA?Encrypted?Status
Y / NY / NOK / Gap
Y / NY / NOK / Gap
Y / NY / NOK / Gap
Y / NY / NOK / Gap
Y / NY / NOK / Gap
Y / NY / NOK / Gap
Y / NY / NOK / Gap
Y / NY / NOK / Gap
Y / NY / NOK / Gap
Y / NY / NOK / Gap
Y / NY / NOK / Gap
Y / NY / NOK / Gap

Data Access: PHI (Protected Health Info)  |  PII (Personal Info)  |  Financial  |  Operational  |  Clinical Decision Support

Shadow AI tools identified (list all unauthorized tools found):
SECTION 2 Business Associate Agreement Audit

For every AI tool in Section 1 with PHI access, verify a signed BAA exists before any PHI flows.

HIPAA 2026 requirement

Every vendor that accesses, stores, transmits, or processes PHI on your behalf requires a signed BAA before any PHI flows to their systems. Older BAAs may not cover AI-specific processing — verify coverage explicitly.

AI Vendor / ToolBAA Exists?BAA Covers AI?Expiry / Review DateAction Required
Y / NY / N
Y / NY / N
Y / NY / N
Y / NY / N
Y / NY / N
Y / NY / N
Y / NY / N
Y / NY / N
Y / NY / N
Y / NY / N

Immediate action: Any tool with PHI access and no BAA must be suspended until the BAA is executed. Document suspension and execution dates.

SECTION 3 Encryption Verification Checklist

Verify encryption for every AI tool with PHI access. HIPAA 2026 mandatory encryption applies to all storage and transmission — including vendor-side logs, caches, and output stores.

Primary database encryption at rest — confirmed and documented
Obtain written confirmation from vendor that primary data store is encrypted at rest using AES-256 or equivalent. Document encryption standard, key management, and date verified.
HIGH
Encryption in transit (TLS 1.2 minimum) — confirmed and documented
Verify all data in transit is encrypted with TLS 1.2 or higher. TLS 1.0 and 1.1 are deprecated.
HIGH
Prompt and conversation logs — encryption status verified
AI tools store prompt history and conversation logs that may contain PHI. Verify encryption status with vendor.
HIGH
Model output caches — encryption status verified
Output caches are often unencrypted by default. Confirm vendor encryption status for all cached outputs.
HIGH
API integration logs — encryption status verified
API integration layers may log full request content including PHI. Confirm logs do not store PHI in cleartext.
HIGH
Fine-tuning or training data — PHI inclusion confirmed absent
If vendor fine-tunes the model using customer data, confirm in writing that PHI is excluded from training datasets.
MEDIUM
Backup and disaster recovery storage — encryption verified
Backup copies must also be encrypted. Verify vendor backup and DR environment meets same standards.
MEDIUM
Encryption key management — documented and controlled
Verify who holds encryption keys and under what conditions the vendor can access encrypted data.
MEDIUM
Encryption gaps identified and remediation plan:
SECTION 4 Human Oversight Documentation

HHS 2026 AI guidance requires documented human oversight procedures for clinical AI. Complete one row per system.

What HHS requires

For every clinical AI system, document: (1) named human reviewer, (2) review frequency, (3) escalation path for unexpected outputs, (4) decision logging mechanism, (5) adverse event reporting process. A general policy statement does not satisfy this requirement.

Named human reviewer designated for each clinical AI system
Each clinical AI system must have a named, accountable individual responsible for reviewing outputs. Document name, title, and designation date.
HIGH
Review frequency documented and schedule established
Define review cadence appropriate to the clinical risk of each AI's decision support role.
HIGH
Escalation procedure written and distributed
Step-by-step procedure for unexpected, potentially harmful, or biased AI output. Who is notified? Who can suspend the tool?
HIGH
AI-assisted decision logging mechanism in place
Log: AI system used, output produced, who reviewed, whether reviewer concurred or overrode, final action taken.
HIGH
Adverse event reporting procedure established
Define process for reporting AI-related adverse events to clinical leadership and HHS under applicable requirements.
HIGH
Clinical staff training on oversight obligations completed
All clinical staff using AI decision support tools must be trained. Document completion dates and sign-offs.
MEDIUM
Oversight procedure reviewed and signed by clinical leadership
Each procedure should be signed by the relevant department head and CMO or designee.
MEDIUM

Human Oversight Log — Complete one row per clinical AI system:

Clinical AI SystemNamed ReviewerReview FrequencyLogging MethodProcedure Date
SECTION 5 NIST AI RMF Gap Assessment Scorecard

Self-assess across all four NIST AI RMF functions. Rate each control: Full / Partial / None.

Scoring guidance

Full = documented, implemented, and verifiable with evidence. Partial = policy exists but implementation is incomplete or evidence is missing. None = not in place. Use the Current State column to record your finding.

NIST FunctionSub-CategoryControl DescriptionCurrent StateTargetGap?
GOVERNGV-1.1AI governance policy established and approvedFull
GOVERNGV-1.2AI oversight roles and responsibilities assignedFull
GOVERNGV-2.1AI risk tolerance defined and documentedFull
GOVERNGV-4.1AI acceptable use policy distributed to staffFull
MAPMP-1.1Complete AI system inventory conductedFull
MAPMP-2.1PHI exposure classified per AI toolFull
MAPMP-3.1Regulatory obligations mapped per AI systemFull
MAPMP-4.1Shadow AI tools identified and documentedFull
MEASUREMS-1.1Encryption at rest verified per AI toolFull
MEASUREMS-1.2Encryption in transit verified per AI toolFull
MEASUREMS-2.1BAA confirmed for every AI vendor with PHI accessFull
MEASUREMS-3.1Human oversight procedures documentedFull
MEASUREMS-4.1AI output accuracy metrics establishedPartial
MANAGEMG-1.1Identified gaps remediated with documented evidenceFull
MANAGEMG-2.1AI incident response procedure written and testedFull
MANAGEMG-3.1AI vendor risk reviews scheduled quarterlyFull
MANAGEMG-4.1Regulatory monitoring process in placeFull
Priority remediation items identified (list top 5 gaps by risk):
SECTION 6 HIPAA 2026 AI Compliance Verification

Mandatory controls only. No risk-based alternatives apply.

Addressable safeguard review completed — all updated to required status
Controls previously classified as addressable must now be implemented or compensating controls documented.
HIGH
Encryption at rest mandatory — verified for all AI systems with PHI access
AES-256 or equivalent mandatory for all PHI at rest across AI systems, logs, caches, backups, and DR environments.
HIGH
Encryption in transit mandatory — verified for all AI data flows
TLS 1.2 minimum for all PHI in transit including API calls, browser/app data, and AI outputs returned to your systems.
HIGH
BAA executed with every AI vendor before PHI access
No AI vendor may access PHI without a signed BAA. Verify current BAAs cover AI-specific processing.
HIGH
Shadow AI policy implemented and distributed to all staff
Written policy prohibiting unauthorized AI tool use with PHI. Include approved tools, prohibited data types, and violation consequences.
HIGH
Human oversight documentation in place for all clinical AI
Per HHS 2026 AI guidance. Absence of documentation is a distinct compliance gap from other HIPAA controls.
HIGH
AI-related breach notification procedure established
Shadow AI incidents and unauthorized AI data disclosures qualify as potential HIPAA breaches under the 2026 rule.
HIGH
Risk analysis updated to include AI systems
HIPAA risk analysis must explicitly include all AI systems, their data access, encryption status, and specific risks.
HIGH
Workforce training updated to include AI security obligations
Training must include AI-specific content: approved tools, prohibited PHI use, shadow AI risks, and reporting procedures.
MEDIUM
AI vendor security assessments documented
Obtain SOC 2 Type II or equivalent from all AI vendors with PHI access. Review annually.
MEDIUM
Audit logs reviewed for AI tool access and use
Configure AI tool access logging where feasible. Review quarterly for unusual patterns.
MEDIUM
Incident response plan updated for AI-specific scenarios
Include playbooks for: shadow AI exposure, AI vendor breach, harmful clinical AI output, unauthorized PHI access.
MEDIUM
SECTION 7 Assessment Summary & Next Steps

Complete this section after finishing all six sections above.

SectionTotal ItemsCompletedGaps IdentifiedPriority Actions
1 — AI InventoryWorksheet
2 — BAA AuditWorksheet
3 — Encryption8
4 — Human Oversight7 + Log
5 — NIST Scorecard17
6 — HIPAA 2026 Controls12
TOTAL

30-Day Priority Action Plan

PriorityAction RequiredOwnerDue DateStatus
H / M / L
H / M / L
H / M / L
H / M / L
H / M / L
H / M / L
H / M / L
H / M / L