Mobile Platform for Executing Medical Business Processes and Data Collecting

  • Jerzy Brzeziński
  • Anna Kobusińska
  • Jacek Kobusiński
  • Andrzej Stroiński
  • Konrad Szałkowski
Part of the Lecture Notes in Computer Science book series (LNCS, volume 7798)

Abstract

Medicine becomes more and more complex domain. The process from patient registration through to the provision of the right treatment becomes complex and sophisticated, and any mistakes or inaccuracies can have a significant consequences for both the patient and the care professionals. This paper presents a MMDCP — Medical Mobile Data Collecting Platform, which aims is to reduce the error rate and speed up the process of data collection. Since medical staff should have the access to medical data from any place of the healthcare facility, the MMDCP provides it’s users the mobility. The proposed platform also distinguishes itself with flexibility, simplicity of maintenance and integration.

Keywords

data collecting business process electronic health record integration SOA REST 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    ESKULAP Hospital Information System, http://www.systemeskulap.pl/
  2. 2.
    Health Level Seven International, http://www.hl7.org/
  3. 3.
    Hibernate Object-Relational Mapping Framework, http://www.hibernate.org/
  4. 4.
    Hibernate Reference Manual, http://docs.jboss.org/hibernate/orm/4.1/
  5. 5.
    Hypertext Transfer Protocol – HTTP/1.1, http://www.w3.org/Protocols/rfc2616/
  6. 6.
    Jersey JAX-RS (JSR 311) Reference Implementation, http://jersey.java.net/
  7. 7.
    Simple Object Access Protocol (SOAP) 1.1, http://www.w3.org/TR/soap/
  8. 8.
    W3C: Web Architecture, http://www.w3.org/standards/webarch/
  9. 9.
    Web Services Description Language (WSDL) 2.0, http://www.w3.org/TR/wsdl20/
  10. 10.
    Web services addressing, ws-addressing (2004), http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/
  11. 11.
    Web services security: Soap message security 1.1, ws-security (2006), https://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf
  12. 12.
    Web services business process execution language version 2.0 (2007), http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.pdf
  13. 13.
    Brzeziński, J., Danilecki, A., Flotyński, J., Kobusińska, A., Stroiński, A.: Workflow Engine Supporting RESTful Web Services. In: Nguyen, N.T., Kim, C.-G., Janiak, A. (eds.) ACIIDS 2011, Part I. LNCS, vol. 6591, pp. 377–385. Springer, Heidelberg (2011)CrossRefGoogle Scholar
  14. 14.
    Brzeziński, J., Danilecki, A., Flotyński, J., Kobusińska, A., Stroiński, A.: ROsWeL Workflow Language: A Declarative, Resource-oriented Approach. New Generation Computing 30(2-3), 141–163 (2012)CrossRefGoogle Scholar
  15. 15.
    Fielding, R.T.: Architectural Styles and the Design of Network-based Software Architectures. Ph.D. thesis, University of California, Irvine (2000)Google Scholar
  16. 16.
    Krafzig, D., Banke, K., Slama, D.: Enterprise SOA: Service-Oriented Architecture Best Practices. Prentice Hall PTR, Upper Saddle River (2004)Google Scholar
  17. 17.
    Menola, F., Miller, E.: Implementation Guide for the Use for Bar Code Technology in Healthcare (2003), http://www.himss.org/
  18. 18.
    Richardson, L., Ruby, S.: RESTful Web Services (2007)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Jerzy Brzeziński
    • 1
  • Anna Kobusińska
    • 1
  • Jacek Kobusiński
    • 1
  • Andrzej Stroiński
    • 1
  • Konrad Szałkowski
    • 1
  1. 1.Institute of Computing SciencePoznań University of TechnologyPoznańPoland

Personalised recommendations