{"title":"渴望音乐会和激进标准化:多年的计划完成自由迁徙","authors":"D. Voellmy","doi":"10.4414/SMI.29.283","DOIUrl":null,"url":null,"abstract":"After the complete rollout of an electronic patient record in a university hospital from 2007 to 2013, a critical review of some project issues was undertaken. One issue is the complexity resulting from a highly configurable and scriptable product. Complexity can be kept within reasonable limits by concepts that emphasise enterprise wide standards, and an effectual ICT governance. The rollout strategy had three functional blocks throughout all clinics in three rounds. The rollout strategy proved to be not ideal, but this was inevitable due to the evolving software development process. Requirements engineering turned out to be the key issue. Effective and consistent functionality should be ensured by a formal specification process combined with early and frequent software reviews including the clinical stakeholders. To minimise quality issues, software testing has to be formalised and intensified.","PeriodicalId":156842,"journal":{"name":"Swiss medical informatics","volume":"29 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2013-09-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":"{\"title\":\"Zwischen Wunschkonzert und radikaler Standardisierung: Bilanz einer Gratwanderung nach einem mehrjährigen KIS-Projekt\",\"authors\":\"D. Voellmy\",\"doi\":\"10.4414/SMI.29.283\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"After the complete rollout of an electronic patient record in a university hospital from 2007 to 2013, a critical review of some project issues was undertaken. One issue is the complexity resulting from a highly configurable and scriptable product. Complexity can be kept within reasonable limits by concepts that emphasise enterprise wide standards, and an effectual ICT governance. The rollout strategy had three functional blocks throughout all clinics in three rounds. The rollout strategy proved to be not ideal, but this was inevitable due to the evolving software development process. Requirements engineering turned out to be the key issue. Effective and consistent functionality should be ensured by a formal specification process combined with early and frequent software reviews including the clinical stakeholders. To minimise quality issues, software testing has to be formalised and intensified.\",\"PeriodicalId\":156842,\"journal\":{\"name\":\"Swiss medical informatics\",\"volume\":\"29 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2013-09-02\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"1\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Swiss medical informatics\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.4414/SMI.29.283\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Swiss medical informatics","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.4414/SMI.29.283","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Zwischen Wunschkonzert und radikaler Standardisierung: Bilanz einer Gratwanderung nach einem mehrjährigen KIS-Projekt
After the complete rollout of an electronic patient record in a university hospital from 2007 to 2013, a critical review of some project issues was undertaken. One issue is the complexity resulting from a highly configurable and scriptable product. Complexity can be kept within reasonable limits by concepts that emphasise enterprise wide standards, and an effectual ICT governance. The rollout strategy had three functional blocks throughout all clinics in three rounds. The rollout strategy proved to be not ideal, but this was inevitable due to the evolving software development process. Requirements engineering turned out to be the key issue. Effective and consistent functionality should be ensured by a formal specification process combined with early and frequent software reviews including the clinical stakeholders. To minimise quality issues, software testing has to be formalised and intensified.