Requirements engineering in health care: the example of chemotherapy planning in paediatric oncology

  • Authors:

  • Sebastian Garde;Petra Knaup

  • Affiliations:

  • Health Informatics Research Group, Faculty of Business and Informatics, Central Queensland University, 4702, Rockhampton, QLD, Australia;Department of Medical Informatics, Institute for Medical Biometry and Informatics, University of Heidelberg, Im Neuenheimer Feld 400, 69120, Heidelberg, QLD, Germany

  • Venue:
  • Requirements Engineering
  • Year:
  • 2006

Quantified Score

Hi-index 0.00

Visualization

Abstract

Health care is characterized by highly complex processes of patient care that require unusual amount of communication between different health care professionals of different institutions. Sub-optimal processes can significantly impact on the patient’s health, increase the consumption of services and resources and in severe cases can lead to the patient death. For these reasons, requirements engineering for the development of information technology in health care is a complex process as well: without constant and rigorous evaluation, the impact of new systems on the quality of care is unknown and it is possible that badly designed systems significantly harm patients. To overcome these limitations, we present and discuss an approach to requirements engineering that we applied for the development of applications for chemotherapy planning in paediatric oncology. Chemotherapy planning in paediatric oncology is complex and time-consuming and errors must be avoided by all means. In the multi-hospital/multi-trial-centre environment of paediatric oncology, it is especially difficult and time-consuming to analyse requirements. Our approach combines a grounded theory approach with evolutionary prototyping based on the constant development and refinement of a generic domain model, in this case a domain model for chemotherapy planning in paediatric oncology. The prototypes were introduced in medical centres and final results show that the developed generic domain model is adequate.