{"title":"临床实践中符合IVDR的内部软件开发建议:一篇包含三个用例的指南论文","authors":"Hanneke W. M. van Deutekom, S. Haitjema","doi":"10.1515/cclm-2022-0278","DOIUrl":null,"url":null,"abstract":"Abstract Objectives The In Vitro Diagnostics Regulation (IVDR) will be effective in May 2022 by which in-house developed tests need to apply to the general safety and performance requirements defined in Annex I of the IVDR ruling. Yet, article 16 from Annex I about software can be hard to interpret and implement, particularly as laboratories are unfamiliar with quality standards for software development. Methods In this paper we provide recommendations on organizational structure, standards to use, and documentation, for IVDR compliant in-house software development. Results A practical insight is offered into novel standard operating procedures using three examples: an Excel file with a formula to calculate the pharmacokinetics of tacrolimus and to calculate the new dose, a rule for automated diagnosis of acute kidney injury and a bioinformatics pipeline for DNA variant calling. Conclusions We recommend multidisciplinary development teams supported by higher management, use of ISO-15189 in synergy with IEC-62304, and concise documentation that includes intended purpose, classification, requirement management, risk management, verification and validation, configuration management and references to clinical or performance evidence.","PeriodicalId":10388,"journal":{"name":"Clinical Chemistry and Laboratory Medicine (CCLM)","volume":null,"pages":null},"PeriodicalIF":0.0000,"publicationDate":"2022-05-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"6","resultStr":"{\"title\":\"Recommendations for IVDR compliant in-house software development in clinical practice: a how-to paper with three use cases\",\"authors\":\"Hanneke W. M. van Deutekom, S. Haitjema\",\"doi\":\"10.1515/cclm-2022-0278\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Abstract Objectives The In Vitro Diagnostics Regulation (IVDR) will be effective in May 2022 by which in-house developed tests need to apply to the general safety and performance requirements defined in Annex I of the IVDR ruling. Yet, article 16 from Annex I about software can be hard to interpret and implement, particularly as laboratories are unfamiliar with quality standards for software development. Methods In this paper we provide recommendations on organizational structure, standards to use, and documentation, for IVDR compliant in-house software development. Results A practical insight is offered into novel standard operating procedures using three examples: an Excel file with a formula to calculate the pharmacokinetics of tacrolimus and to calculate the new dose, a rule for automated diagnosis of acute kidney injury and a bioinformatics pipeline for DNA variant calling. Conclusions We recommend multidisciplinary development teams supported by higher management, use of ISO-15189 in synergy with IEC-62304, and concise documentation that includes intended purpose, classification, requirement management, risk management, verification and validation, configuration management and references to clinical or performance evidence.\",\"PeriodicalId\":10388,\"journal\":{\"name\":\"Clinical Chemistry and Laboratory Medicine (CCLM)\",\"volume\":null,\"pages\":null},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2022-05-11\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"6\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Clinical Chemistry and Laboratory Medicine (CCLM)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1515/cclm-2022-0278\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Clinical Chemistry and Laboratory Medicine (CCLM)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1515/cclm-2022-0278","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Recommendations for IVDR compliant in-house software development in clinical practice: a how-to paper with three use cases
Abstract Objectives The In Vitro Diagnostics Regulation (IVDR) will be effective in May 2022 by which in-house developed tests need to apply to the general safety and performance requirements defined in Annex I of the IVDR ruling. Yet, article 16 from Annex I about software can be hard to interpret and implement, particularly as laboratories are unfamiliar with quality standards for software development. Methods In this paper we provide recommendations on organizational structure, standards to use, and documentation, for IVDR compliant in-house software development. Results A practical insight is offered into novel standard operating procedures using three examples: an Excel file with a formula to calculate the pharmacokinetics of tacrolimus and to calculate the new dose, a rule for automated diagnosis of acute kidney injury and a bioinformatics pipeline for DNA variant calling. Conclusions We recommend multidisciplinary development teams supported by higher management, use of ISO-15189 in synergy with IEC-62304, and concise documentation that includes intended purpose, classification, requirement management, risk management, verification and validation, configuration management and references to clinical or performance evidence.