MedElevator Войти в исследования
← Поиск публикаций

DOI 10.2196/101715

Медицинская библиотека · JMIR medical informatics · 2026

Cybersecurity of Large Language Models Across the Deployment Life Cycle in Health Systems.

Goh Chun Joo, Liu Haoran, Devendra Nethum, Cao Khoa Nguyen

СтатьяПеревод пока не подготовлен

Аннотация

In this Viewpoint, we highlight the principal cybersecurity measures that should be implemented to facilitate safe and effective integration of large language models (LLMs) into health care and propose a conceptual, life cycle-based framework synthesizing evidence from security and clinical informatics literature. While LLMs offer significant potential for applications in clinical documentation, triage, and medical education, their deployment creates novel vulnerabilities that can compromise patient safety and data confidentiality. We argue that these vulnerabilities must be addressed across the entire deployment life cycle, with distinct threats arising before and after a model enters clinical use. Predeployment risks include data and model poisoning, where an LLM's training data or core parameters are maliciously corrupted to embed biases or backdoors. After deployment, LLMs are susceptible to inference attacks, such as prompt injection and adversarial inputs, which can be used to manipulate model behavior and extract sensitive information. Standard performance benchmarks are often insufficient to detect these sophisticated attacks. Therefore, we argue that a proactive, multilayered security framework combining technical safeguards, rigorous governance, and human-in-the-loop oversight is essential for the safe and trustworthy adoption of LLMs in clinical practice.

Для цитирования: Goh Chun Joo, Liu Haoran, Devendra Nethum, Cao Khoa Nguyen. Cybersecurity of Large Language Models Across the Deployment Life Cycle in Health Systems.. JMIR medical informatics. 2026. DOI: 10.2196/101715.

Предметные рубрики MeSH

Подготовка и перевод публикации
Обработка статьи · этапы, ошибки и управление
Загрузка состояния…

История · было → стало

Состояние обновляется каждые 5 секунд, пока блок открыт. Процент показывается только там, где известен объём работы. Пауза останавливает продолжение этапа; текущий запрос к источнику может завершиться.

Тип публикации указан по данным источника. Уровень доказательности автоматически не присваивается.