Building Healthcare Service Navigation System for a Local Health Integration Network: A Requirements Elicitation Model

Conference paper


Local health integration networks (LHIN) are not-for-profit organisations created by the Ontario government in 2006 for planning, identifying, integrating, and funding health services and priority programmes for their regions. This chapter discusses an information systems development initiative in 1 of the 14 LHINs with the objective of facilitating healthcare service navigation by users. These healthcare services are provided by 88 member agencies of the LHIN consisting of hospitals, long-term centres, assisted living services, community support services, community care access centres, mental health agencies, addiction agencies, and community health centres. Using the proposed service-oriented architecture for the LHIN as a basis of our framework, we suggest an ontology-based requirements elicitation model for developing an automated and interactive tool capable of supporting automatic service discovery, automatic service composition, and dynamic composition.


Healthcare Service Software Product Line Requirement Elicitation Information System Development Member Agency 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.



Financial support for this study has been provided by the Odette School of Business, University of Windsor, under Research, Teaching, and Innovation Fund.


  1. Bhandari G, Snowdon A (2011) Design of a patient-centric, service-oriented health care navigation system for a local health integration network. Behav Inf Technol:1–11, First published on: 04 May 2011 (iFirst)Google Scholar
  2. Browne GJ, Ramesh V (2002) Improving information requirements determination: a cognitive perspective. Inf Manage 39:625–645CrossRefGoogle Scholar
  3. Byrd TA, Cossick KL, Zmud R (1992) A synthesis of research on requirements analysis and knowledge acquisition techniques. MIS Q 16(1):117–128CrossRefGoogle Scholar
  4. Davis A, Hickey A (2002) Requirements researchers: do we practice what we teach. Requir Eng J 7:107–111CrossRefGoogle Scholar
  5. Dobson G, Sawyer P (2006) Revisiting ontology-based requirements engineering in the age of the semantic web. In: Proceedings of the international seminar on dependable requirements engineering of computerized systems at NPPs. Available at
  6. Gruber TR (1993) A translation approach to portable ontology specifications. Knowl Acquis 5(2):199–220CrossRefGoogle Scholar
  7. Hickey AM, Davis AM (2004) A unified model of requirements elicitation. J Manage Inf Syst 20(4):65–84Google Scholar
  8. Jones S (2005) Toward an acceptable definition of service. IEEE Softw (May/June): 87–93Google Scholar
  9. Kaiya H, Saeki M (2005) Ontology based requirements analysis: lightweight semantic processing approach. In: Proceedings of the 5th international conference on quality software, 223–230Google Scholar
  10. Maiden N, Rugg G (1996) ACRE: selecting methods for requirements acquisition. Softw Eng J 11(5):183–192CrossRefGoogle Scholar
  11. Martin D et al (2004) OWL-S: semantic markup for web services. Available at
  12. Mathiassen L, Tuunanen T, Saarinen T, Rossi M (2007) A contingency model for requirements development. J Assoc Inf Syst 8(11):569–597Google Scholar
  13. Sheth A, Verma K, Gomadam K (2006) Semantics to energize the full services spectrum. Commun ACM 49(7):55–61CrossRefGoogle Scholar
  14. Thanasankit T (2002) Requirements engineering-exploring the influence of power and Thai values. Eur J Inf Syst 11(2):128CrossRefGoogle Scholar
  15. Zhang X (2011) An interactive approach of ontology-based requirement elicitation for software customization. Unpublished Master’s Thesis, University of Windsor, ONGoogle Scholar

Copyright information

© Springer Science+Business Media New York 2013

Authors and Affiliations

  1. 1.Odette School of BusinessUniversity of WindsorOntarioCanada

Personalised recommendations