TRV-2026-1538Certified recordPeer-reviewed

Institutional approaches to artificial intelligence policy and guidance in health informatics and information management education: emerging trends and inconsistencies

Objective To examine the characteristics, scope, and thematic content of institutional and program-level academic artificial intelligence (AI) policies and guidance documents used by CAHIIM-accredited Health Informatics (HI) and Health Information Management (HIM) master's programs in the United States. Materials and methods This convergent mixed‑methods study examined publicly available AI‑related documents (eg, student handbooks, integrity policies, program manuals) from all 48 CAHIIM‑accredited HI and HIM mas…

Policy · Problem Space — documented harm · certified 2026-10-16 · v1 · article view · machine-readable

Current reading — problem

Eight of 48 accredited programs had no qualifying AI document, and the rest varied in structure and scope, mostly offering guidance rather than formal policy.

What this doesn’t fix

The study analyzed only publicly available documents, and the authors say links to curriculum development and organizational AI governance remain unexamined.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1538, v1: “Institutional approaches to artificial intelligence policy and guidance in health informatics and information management education: emerging trends and inconsistencies.” Truvace, 2026-10-16. /record/TRV-2026-1538 (accessed at citation time). sha256 3e8810cbb48f8305…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv13e8810cbb48f…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1538 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.