{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2022,3,30]],"date-time":"2022-03-30T09:11:40Z","timestamp":1648631500335},"reference-count":0,"publisher":"IOS Press","license":[{"start":{"date-parts":[[2021,5,27]],"date-time":"2021-05-27T00:00:00Z","timestamp":1622073600000},"content-version":"unspecified","delay-in-days":0,"URL":"https:\/\/creativecommons.org\/licenses\/by-nc\/4.0\/"}],"content-domain":{"domain":[],"crossmark-restriction":false},"short-container-title":[],"published-print":{"date-parts":[[2021,5,27]]},"abstract":"<jats:p>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.<\/jats:p>","DOI":"10.3233\/shti210161","type":"book-chapter","created":{"date-parts":[[2021,5,27]],"date-time":"2021-05-27T12:56:24Z","timestamp":1622120184000},"source":"Crossref","is-referenced-by-count":0,"title":["Development of a Framework for Redesigning a Terminology Maintenance Process \u2013 Case Study in the Netherlands"],"prefix":"10.3233","author":[{"given":"Eva S.","family":"Klappe","sequence":"first","affiliation":[{"name":"Amsterdam UMC, University of Amsterdam, Department of Medical Informatics, Amsterdam Public Health Research Institute, Amsterdam, Netherlands"}]},{"given":"Nicolette F.","family":"de Keizer","sequence":"additional","affiliation":[{"name":"Amsterdam UMC, University of Amsterdam, Department of Medical Informatics, Amsterdam Public Health Research Institute, Amsterdam, Netherlands"}]},{"given":"Ronald","family":"Cornet","sequence":"additional","affiliation":[{"name":"Amsterdam UMC, University of Amsterdam, Department of Medical Informatics, Amsterdam Public Health Research Institute, Amsterdam, Netherlands"}]}],"member":"7437","container-title":["Studies in Health Technology and Informatics","Public Health and Informatics"],"original-title":[],"link":[{"URL":"https:\/\/ebooks.iospress.nl\/pdf\/doi\/10.3233\/SHTI210161","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2021,10,25]],"date-time":"2021-10-25T13:11:37Z","timestamp":1635167497000},"score":1,"resource":{"primary":{"URL":"https:\/\/ebooks.iospress.nl\/doi\/10.3233\/SHTI210161"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2021,5,27]]},"references-count":0,"URL":"https:\/\/doi.org\/10.3233\/shti210161","relation":{},"ISSN":["0926-9630","1879-8365"],"issn-type":[{"value":"0926-9630","type":"print"},{"value":"1879-8365","type":"electronic"}],"subject":[],"published":{"date-parts":[[2021,5,27]]}}}