Advertisement

Goal-Driven Development of a Patient Surveillance Application for Improving Patient Safety

  • Saeed Ahmadi Behnam
  • Daniel Amyot
  • Alan J. Forster
  • Liam Peyton
  • Azalia Shamsaei
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 26)

Abstract

Hospitals strive to improve the safety of their patients. Yet, every year, thousands of patients suffer from adverse events, which are defined as undesirable outcomes caused by health care business processes. There are few tools supporting adverse event detection and these are ineffective. There is hence some urgency in developing such a tool in a way that complies with the organizations goals and privacy legislation. In addition, governments will soon require hospitals to report on adverse events. In this paper, we will show how a pilot application we developed contributes to the patient safety goals of a major teaching hospital and how our goal-driven approach supported the collaboration between the university researchers and hospital decision makers involved. Benefits and challenges related to the modeling of requirements, goals, and processes, and to the development of the application itself, are also discussed.

Keywords

Adverse Events Business Process Modeling Goal Modeling Health Care Patient Safety User Requirements Notation 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. [1]
    Amyot, D.: Introduction to the User Requirements Notation: Learning by Example. Computer Networks 42(3), 285–301 (2003)CrossRefGoogle Scholar
  2. [2]
    Baker, G.R., Norton, P.G., Flintoft, V., Blais, R., Brown, A., Cox, J., et al.: The Canadian Adverse Events Study: the incidence of adverse events among hospital patients in Canada. CMAJ 170(11), 1678–1686 (2004)CrossRefGoogle Scholar
  3. [3]
    Cullen, D.J., Bates, D.W., Small, S.D., Cooper, J.B., Nemeskal, A.R., Leape, L.L.: The incident reporting system does not detect adverse drug events: a problem for quality improvement. Joint Commission Journal on Quality Improvement 21(10), 541–548 (1995)CrossRefGoogle Scholar
  4. [4]
    Forster, A.J., Halil, R.B., Tierney, M.G.: Pharmacist surveillance of adverse drug events. American Journal of Health-System Pharmacy 61(14), 1466–1472 (2004)Google Scholar
  5. [5]
    Gandhi, T.K., Weingart, S.N., Borus, J., Seger, A.C., Peterson, J., Burdick, E., et al.: Adverse Drug Events in Ambulatory Care. The New England Journal of Medicine 348(16), 1556 (2003)Google Scholar
  6. [6]
    Gurwitz, J.H., Field, T.S., Avorn, J., McCormick, D., Jain, S., Eckler, M., et al.: Incidence and preventability of adverse drug events in nursing homes. American Journal of Medicine 109(2), 87–94 (2000)CrossRefGoogle Scholar
  7. [7]
    ITU-T – International Telecommunications Union: Recommendation Z.151 (11/08): User Requirements Notation (URN) – Language definition. Geneva, Switzerland (2008)Google Scholar
  8. [8]
    Liu, L., Yu, E.: Designing Information Systems in Social Context: A Goal and Scenario Modelling Approach. Information Systems 29(2), 187–203 (2004)CrossRefGoogle Scholar
  9. [9]
    Michel, P., Quenon, J.L., de Sarasqueta, A.M., Scemama, O.: Comparison of three methods for estimating rates of adverse events and rates of preventable adverse events in acute care hospitals. British Medical Journal 328(7433), 199–203 (2004)CrossRefGoogle Scholar
  10. [10]
    Pourshahid, A., Chen, P., Amyot, D., Forster, A.J., Ghanavati, S., Peyton, L., Weiss, M.: Toward an integrated User Requirements Notation framework and tool for Business Process Management. In: 3rd Int. MCeTech Conference on eTechnologies, Montréal, Canada, January 3-15, 2008, IEEE Computer Society, Los Alamitos (2008)Google Scholar
  11. [11]
    Stead, W.W., Lin, H.S.: Computational Technology for Effective Health Care: Immediate Steps and Strategic Directions. In: Committee on Engaging the Computer Science Research Community in Health Care Informatics, National Research Council, USA, National Academies Press, Washington (2009)Google Scholar
  12. [12]
    The Institute of Medicine. To err is human: building a safer health system. National Academy Press, Washington D.C (2000)Google Scholar
  13. [13]
    Univ. of Ottawa: jUCMNav 3.2 (2008), http://jucmnav.softwareengineering.ca/jucmnav/
  14. [14]
    Weiss, M., Amyot, D.: Business Process Modeling with URN. International Journal of E-Business Research 1(3), 63–90 (2005)CrossRefGoogle Scholar
  15. [15]
    van Lamsweerde, A.: Requirements engineering: From System Goals to UML Models to Software Specifications. John Wiley & Sons, Chichester (2009)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Saeed Ahmadi Behnam
    • 1
  • Daniel Amyot
    • 1
  • Alan J. Forster
    • 2
  • Liam Peyton
    • 1
  • Azalia Shamsaei
    • 1
  1. 1.SITEUniversity of Ottawa
  2. 2.Department of MedicineUniversity of Ottawa and OHRIOttawaCanada

Personalised recommendations