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

DOI 10.3233/shti210161

Медицинская библиотека · Studies in health technology and informatics · 2021

Development of a Framework for Redesigning a Terminology Maintenance Process - Case Study in the Netherlands.

Klappe Eva S, de Keizer Nicolette F, Cornet Ronald

СтатьяПеревод в очереди

Аннотация

Structuring clinical data in electronic health records supports reuse of data to improve quality of care, reduce costs and perform research. This requires terminologies to assign terms from language used in a specific domain to medical concepts. Given the developing character of medical knowledge, these terminologies need continuous maintenance. Nonetheless, little is known about terminology maintenance processes. To specify the (re)design of a terminology maintenance process, we first merged and adapted two static theoretical frameworks that consisted of criteria relating to using a terminology, divided among relevant stakeholders. Following, we applied the framework to the healthcare terminology maintenance process in the Netherlands. We held interviews with relevant stakeholders and used the framework as checklist to identify missing criteria and bottlenecks. Saturation in interviews and fulfilment of the criteria indicated that all bottlenecks were discovered, therefore the framework was considered useful for redesigning a terminology maintenance process. Other countries could benefit from this framework as well to discover and resolve any unfulfilled maintenance criteria.

Для цитирования: Klappe Eva S, de Keizer Nicolette F, Cornet Ronald. Development of a Framework for Redesigning a Terminology Maintenance Process - Case Study in the Netherlands.. Studies in health technology and informatics. 2021. DOI: 10.3233/shti210161.

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

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

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

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

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