Dynamic Routing Using Health Information Policy with Apache Camel

  • Edward Brown
  • Jamie Goodyear
Part of the Communications in Computer and Information Science book series (CCIS, volume 127)


Apache Camel is an implementation of a messaging framework using the enterprise integration patterns advanced by Hohpe and Woolf. This framework allows the messaging architecture to be configured at run-time, by changing routing rules which determine the disposition of messages transmitted by the system. Our work illustrates an original use of the dynamic routing capability to implement health information policy, by putting the routing rules in the hands of policy administrators rather than network managers. This paper is an extended version of reference [1].


Policy Messaging Architecture Middleware Medical context 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Brown, E., Goodyear, J.: A Flexible Policy Architecture for Medical Information Messaging. In: BIOSTEC 3rd International Joint Conference on Biomedical Engineering Systems and Technologies, pp. 70–76. INSTICC (2010)Google Scholar
  2. 2.
    Hohpe, G., Woolf, B.: Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions. Addison-Wesley Professional, Reading (2003)Google Scholar
  3. 3.
    Krasser, M.: Introduction to the open eHealth integration platform (2009),
  4. 4.
    Ibsen, C., Anstey, J., Zbarcea, H.: Camel in Action, Early Access Edition. Manning Publications (2009),
  5. 5.
    Java Message Service, Java Specification Request 914, final release (2003),
  6. 6.
    EHRS Blueprint, an Inter-operable EHR Framework. Canada Health Infoway Inc., version 1.0 edition (2003),
  7. 7.
    Brown, E., Wareham, H., et al.: Technology Choices and Privacy Policy in Health Care: Report to the Privacy Commissioner of Canada. Medical Informatics Group, Memorial University (2007),
  8. 8.
    Health Protection and Promotion Act, Revised Statutes of Ontario, s. 25. Government of Ontario, Canada (1990)Google Scholar
  9. 9.
    Bricon-Souf, N., Newman, C.R.: Context Awareness in Health Care: A review. International Journal of Medical Informatics 76(1), 2–12 (2007)CrossRefGoogle Scholar
  10. 10.
    De Clercq, E., Bangels, M., France, F.R.: Integration of Electronic Patient Record Context with Message Context. Studies in Health Technology and Informatics 107(2), 1028–1032 (2004)Google Scholar
  11. 11.
    Manzoor, S., Ceusters, W.M., Rudnicki, R.: A Middleware Approach to Integrate Referent Tracking in EHR System. In: American Medical Informatics Association Symposium Proceedings, pp. 503–507 (2007)Google Scholar
  12. 12.
    Hägglund, M., Scandurra, I., Moström, D., Koch, S.: Bridging the Gap: a Virtual Health Record for Integrated Home Care. International Journal of Integrated Care 7, e26 (2007)Google Scholar
  13. 13.
    Doukas, C., Maglogiannis, I., Karpouzis, K.: Context-Aware Medical Content Adaptation Through Semantic Representation and Rules Evaluation. In: Third International Workshop on Semantic Media Adaptation and Personalization, Washington, pp. 128–134 (2008)Google Scholar
  14. 14.
    Bardram. J. E.: Applications of Context-Aware Computing in Hospital Work: Examples and Design Principles. In: ACM Symposium on Applied Computing, New York, pp. 1574–1579 (2004)Google Scholar
  15. 15.
    CHIRIS User Manual. Canada Health Infoway Inc., version 0.2 edition (2005),
  16. 16.
    Goodyear, J.: Extending the Health Information Access Layer with a Medical Context Messaging Framework. Honours Dissertation, Department of Computer Science, Memorial University of Newfoundland (2009)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Edward Brown
    • 1
  • Jamie Goodyear
    • 2
  1. 1.Department of Computer ScienceMemorial University of NewfoundlandSt. John’sCanada
  2. 2.Progress Software CorporationSt. John’sCanada

Personalised recommendations