R Lenz1. 1. Universität Erlangen-Nürnberg, Department Informatik, Lehrstuhl für Informatik 6 (Datenmanagement), Martensstrasse 3, D-91058 Erlangen, Germany. Richard.Lenz@informatik.uni-erlangen.de
Abstract
OBJECTIVES: To identify core challenges and first steps on the way to sustainable information systems in healthcare. METHODS: Recent articles on healthcare information technology and related articles from Medical Informatics and Computer Science were reviewed and analyzed. Core challenges that couldn't be solved over the years are identified. RESULTS: The two core problem areas are process integration, meaning to effectively embed IT-systems into routine workflows, and systems integration, meaning to reduce the effort for interconnecting independently developed IT-components. Standards for systems integration have improved a lot, but their usefulness is limited where system evolution is needed. CONCLUSIONS: Sustainable Healthcare Information Systems should be based on system architectures that support system evolution and avoid costly system replacements every five to ten years. Some basic principles for the design of such systems are separation of concerns, loose coupling, deferred systems design, and service oriented architectures.
OBJECTIVES: To identify core challenges and first steps on the way to sustainable information systems in healthcare. METHODS: Recent articles on healthcare information technology and related articles from Medical Informatics and Computer Science were reviewed and analyzed. Core challenges that couldn't be solved over the years are identified. RESULTS: The two core problem areas are process integration, meaning to effectively embed IT-systems into routine workflows, and systems integration, meaning to reduce the effort for interconnecting independently developed IT-components. Standards for systems integration have improved a lot, but their usefulness is limited where system evolution is needed. CONCLUSIONS: Sustainable Healthcare Information Systems should be based on system architectures that support system evolution and avoid costly system replacements every five to ten years. Some basic principles for the design of such systems are separation of concerns, loose coupling, deferred systems design, and service oriented architectures.