Hospital AI Lab Practical information on medical AI for U.S. hospitals

Updated:

Medical AI glossary

Medical AI terms you meet in proposals and meetings, collected to the extent needed for a practical assessment. You can jump straight to a term by its name.

Terms tied to law are given as of the time of writing, based on the U.S. rules in force then. They are summaries, not the text of the law. Before you decide, check the primary source and, where needed, ask a specialist.

Regulation and certification

Software as a medical device (SaMD)

Software whose intended use makes it a medical device, so that FDA oversight applies. FDA says its digital health policies apply to software functions that meet the device definition, including functions intended for patients or caregivers.

Why it mattersThe first question for any clinical AI proposal is whether the vendor treats the product as a device. Ask for the answer and its basis in writing.

Source: fda.gov (Opens in a new tab)

Clinical decision support (CDS) software

Software that supports clinical decisions. Under section 520(o)(1)(E) of the FD&C Act, certain clinical decision support functions that meet statutory criteria are excluded from the device definition; FDA’s guidance explains how it reads those criteria.

Why it mattersA vendor may call a product “just decision support.” Whether that is right depends on the criteria and on what the software actually does, not on the label.

Source: fda.gov (Opens in a new tab)

Predetermined change control plan (PCCP)

A plan in a marketing submission that describes planned changes to a device and how the manufacturer will develop, test and implement them, so that FDA can authorize those changes in advance. FDA lists a final guidance dated August 2025 for AI-enabled device software functions.

Why it mattersAI products can change over time. Ask whether the product has a PCCP and which changes it covers.

Source: fda.gov (Opens in a new tab)

FDA list of AI-enabled medical devices

A public list of AI-enabled medical devices authorized for marketing. FDA states that it is not a comprehensive resource of AI-enabled devices, because devices were identified mainly by AI-related terms in their summaries or classifications.

Why it mattersPresence on the list is not a performance guarantee, and absence is not proof that a product is not a device.

Source: fda.gov (Opens in a new tab)

Decision support intervention (DSI)

A term used in the ONC health IT certification criterion at 45 CFR 170.315(b)(11). The HTI-5 final rule (91 FR 67916, October 28, 2026) removes paragraphs (b)(11)(iv) through (vi), the source attribute and risk-management requirements, with an effective date of December 28, 2026 (three instructions January 1, 2027).

Why it mattersA certified EHR vendor may no longer have to meet those federal certification requirements, so ask for model information directly.

Source: ecfr.gov (Opens in a new tab) / federalregister.gov (Opens in a new tab)

Information blocking

A practice likely to interfere with access, exchange or use of electronic health information, except as required by law or covered by an exception. For a health care provider, the standard is that the provider knows the practice is unreasonable and likely to interfere (45 CFR 171.103).

Why it mattersRefusing to share data, for example with a vendor or another provider, can raise this question. Check the exceptions in Part 171 with compliance.

Source: ecfr.gov (Opens in a new tab)

Patient care decision support tool (Section 1557)

A term in the Section 1557 regulation. Under 45 CFR 92.210, a covered entity must not discriminate on the basis of race, color, national origin, sex, age or disability through such tools, must make reasonable efforts to identify tools that use those characteristics as inputs, and must make reasonable efforts to mitigate the risk.

Why it mattersThis applies to tools the hospital uses in its programs, including many AI tools. Keep a list.

Source: ecfr.gov (Opens in a new tab)

Data and privacy

Covered entity

Under HIPAA, a health plan, a health care clearinghouse, or a health care provider that transmits any health information in electronic form in connection with a covered transaction (45 CFR 160.103).

Why it mattersA hospital that transmits health information electronically in covered transactions is a covered entity, and the Privacy, Security and Breach Notification rules apply to it.

Source: ecfr.gov (Opens in a new tab)

Protected health information (PHI)

Individually identifiable health information that is transmitted or maintained in any form or medium, with exceptions listed in the definition (45 CFR 160.103). Electronic PHI is called ePHI.

Why it mattersWhether data counts as PHI decides which rules apply to it. De-identified data under 164.514(b) is not PHI.

Source: ecfr.gov (Opens in a new tab)

Business associate and business associate agreement

A person who, on behalf of a covered entity, creates, receives, maintains or transmits PHI for a regulated function, or who provides listed services such as legal, consulting or data aggregation involving PHI (45 CFR 160.103). A covered entity may disclose PHI to a business associate only after documenting satisfactory assurance in a written contract that meets 45 CFR 164.504(e).

Why it mattersIf an AI vendor handles PHI for you, it is likely a business associate. No agreement means no disclosure.

Source: ecfr.gov (Opens in a new tab) / ecfr.gov (Opens in a new tab)

De-identification

Under 45 CFR 164.514(b), health information can be treated as not individually identifiable by expert determination (a qualified person finds the risk very small and documents the method) or by removing the listed identifiers with no actual knowledge that the data could identify a person.

Why it mattersVendors sometimes say data is “anonymized.” Ask which of the two methods was used and who documented it.

Source: ecfr.gov (Opens in a new tab)

Breach

An acquisition, access, use or disclosure of PHI not permitted by the Privacy Rule that compromises its security or privacy. It is presumed to be a breach unless a risk assessment shows a low probability of compromise (45 CFR 164.402). Notice to individuals is due without unreasonable delay and within 60 calendar days of discovery.

Why it mattersThe 60-day clock starts at discovery, including when a workforce member or agent knew or should have known.

Source: ecfr.gov (Opens in a new tab) / ecfr.gov (Opens in a new tab)

Minimum necessary

When using or disclosing PHI or requesting it, a covered entity or business associate must make reasonable efforts to limit it to the minimum necessary for the purpose, with exceptions listed in 45 CFR 164.502(b).

Why it mattersIt applies to what you send to a vendor. Do not send more than the tool needs.

Source: ecfr.gov (Opens in a new tab)

Standards and terminology

Security Rule risk analysis

A required assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of ePHI, together with security measures sufficient to reduce them to a reasonable and appropriate level (45 CFR 164.308(a)(1)(ii)(A)–(B)).

Why it mattersAdding an AI tool changes your systems, so the analysis should be updated.

Source: ecfr.gov (Opens in a new tab)

NIST AI Risk Management Framework

A framework from NIST to help manage risks to individuals, organizations and society associated with AI. NIST says it is intended for voluntary use. AI RMF 1.0 was released on January 26, 2023, and a generative AI profile on July 26, 2024.

Why it mattersIt is a common vocabulary for governance discussions with vendors. It is not a legal requirement.

Source: nist.gov (Opens in a new tab)

This glossary is not a translation of the Korean or Japanese edition. Each regulatory entry is written from official U.S. sources that were checked separately. Anything we could not confirm is left out.