Home  |   Bright Summer School 2017 on Software Engineering and IS  |   Summer School Program  |   Software Engineering for Healthcare

Software Engineering for Healthcare

Software Engineering for Healthcare, which can be sub-divided into (a) Software Quality through improved process; (b) What is healthcare software and why is it different; (c) Implementing quality and healthcare regulations into software;  (d) Implementing Connected Health.

Software Quality through improved process:
I will discuss the importance of software process, and how improving the software engineering process can improve the quality of software.  I will include Total Quality Management theories.

What is healthcare software and why is it different:
I will define Medical software as recognised by the European Union.  I know that legally the situation is different in other countries, but I still believe that, as professionals, we should be very aware of the consequences of our actions.  Other developing countries, such as India, are introducing regulations – and maybe some of our participants will promote such regulation within developing countries.  I will discuss how this changes our view of Software engineering – recognising how the ‘concept of healthcare’ can inform software requirements.

Implementing software and healthcare regulations into software:
I will discuss software engineering process models (e.g. Capability Maturity Model Integrated CMMI) and how these can be mapped to Medical Device regulations to improve our software engineering process for healthcare.

Implementing Connected Health:
I will look at the wider concept of Connected Health, and how care pathways can be changed through the introduction of technology.  Doing this needs professional software engineers who can bring their modelling and process techniques to this domain, thus providing efficient and effective change through Connected Health solutions.

Suggested reading:

Issac, G., Rajendran, C., & Anantharaman, R. N. (2003). Do Quality Certifications Improve the Software Industry’s Operational Performance?. Software Quality Professional Magazine, 6(1).

Burton, J., McCaffery, F., & Richardson, I. (2006, May). A risk management capability model for use in medical device companies. In Proceedings of the 2006 international workshop on Software quality (pp. 3-8). ACM.

Richardson, I., O’Mahony, J., Howarth, P., O’Connor, P., & Glenny, L. (2016, May). Connected health: from rural Ireland to rural India. In Proceedings of the International Workshop on Software Engineering in Healthcare Systems(pp. 39-42). ACM.

Carroll N., Travers M., Richardson I. (2017) Connecting Multistakeholder Analysis Across Connected Health Solutions. In: Fred A., Gamboa H. (eds) Biomedical Engineering Systems and Technologies. BIOSTEC 2016. Communications in Computer and Information Science, vol 690. Springer, DOI: 10.1007/978-3-319-54717-6_18

Consider a medical condition / disease.  Put yourself in the position of the patient and write a description presenting your care.  You should think about who you interact with (doctors, nurses, physiotherapists, family etc), where you interact with them (at home, in a clinic, in a hospital), what information you have to give them, what information they have about you before you meet them, where it is stored etc.  The description should be approximately 300 words.

Skip to toolbar