Data Integration in Reporting Systems Using Enterprise Service

Data Integration in Reporting Systems Using Enterprise Service

Data Integration in Reporting Systems using Enterprise Service Bus A Thesis Presented in Partial Fulfillment of the Requirements for the Degree of Master of Science in the Graduate School of The Ohio State University By Ketaki Koppal Graduate Program in Computer Science and Engineering The Ohio State University 2009 Thesis Committee: Dr. Rajiv Ramnath, Advisor Dr. Jayashree Ramanathan Dr. Paul Sivilotti © Copyright by Ketaki Koppal 2009 Abstract Data integration, the process of combining data from different sources into a unified view, has become a significant problem in the field of computer science. As the volume of data and rate of information exchange increases, data integration becomes more challenging. An ideal data integration system is the one that allows loose coupling among heterogeneous data sources, facilitates access management and maintains currency of the data. One of the reasons for data integration is the generation of reports. While the process of designing a reporting system inherits the challenges in designing a typical data integration system, it also has some characteristic issues of its own. One of the key issues is allowing mass customization. Existing reporting tools are limited in addressing one or the other of these challenges. This thesis is an attempt to come up with a customizable integration architecture that meets these requirements in the clinical domain. We will also discuss one of the web 2.0 technologies – data mashup - and how it can be leveraged to design an advanced solution for this problem. ii Dedication Dedicated to my family. iii Acknowledgements I would like to express my sincere gratitude to my advisors, Dr. Rajiv Ramnath for his constant guidance and encouragement and Dr. Jay Ramanathan for her insights and counsel that played an important role in shaping my research. I would also like to thank Strategic Thinking Industries for their part in influencing and funding this work. Lastly, I would like to thank my family, for it is because of their unfaltering support that I am able to accomplish this milestone. iv Vita 2005……………………………B.E. Computer Engineering, University of Pune, India August 2005 – August 2007 …………… Software Engineer, Infosys Technologies Ltd. Fields of Study Major Field: Computer Science and Engineering v Table of Contents Abstract............................................................................................................................... ii Dedication..........................................................................................................................iii Acknowledgements............................................................................................................ iv Vita...................................................................................................................................... v Table of Contents............................................................................................................... vi List of Tables ..................................................................................................................... ix List of Figures..................................................................................................................... x Chapter 1: Problem Statement...................................................................................... 1 1.1 Report Generation............................................................................................... 2 1.1.1 Challenges in Report Generation.................................................................... 2 1.2 Electronic Health Record (EHR) ........................................................................ 4 1.3 STI Outbound Interfacing................................................................................... 8 Chapter 2: Related Work ............................................................................................ 12 2.1 Extract, Transform, Load (ETL)....................................................................... 13 2.1.1 Discussion..................................................................................................... 15 vi 2.2 Software Product Line ...................................................................................... 17 2.2.1 Requirement Modeling ................................................................................. 20 2.2.2 Discussion..................................................................................................... 21 2.3 The Enterprise Service Bus (ESB).................................................................... 22 2.3.1 Discussion..................................................................................................... 24 2.4 Mashups............................................................................................................ 25 2.4.1 Mashup Classification................................................................................... 27 2.4.2 Discussion..................................................................................................... 34 Chapter 3: Solution Approach .................................................................................... 35 3.1 Modified system architecture based on ESB:................................................... 35 3.1.1 ChainBuilder ESB......................................................................................... 36 3.1.2 User Interface................................................................................................ 40 3.2 Scope for future work ....................................................................................... 42 Chapter 4: Implementation/Results ............................................................................ 44 4.1 Snapshots .......................................................................................................... 45 4.1.1 CBESB Format Editor .................................................................................. 45 4.1.2 CBESB Map Editor....................................................................................... 46 4.1.3 CBESB Driver File Editor ............................................................................ 48 4.1.4 CBESB Connection File Editor .................................................................... 49 vii 4.1.5 CBESB Component Flow Editor.................................................................. 50 4.1.6 CBESB Admin Console................................................................................ 52 4.2 Key Contributions............................................................................................. 55 Chapter 5: Conclusion and Future Work.................................................................... 57 5.1 User Interface.................................................................................................... 57 5.2 Mashup based solution...................................................................................... 57 References......................................................................................................................... 59 viii List of Tables Table 1: Mashups – summarized. ..................................................................................... 29 ix List of Figures Figure 1: Electronic Health Data – Pre-EHR...................................................................... 6 Figure 2: Electronic Health Record .................................................................................... 7 Figure 3: STI Outbound Interfacing Framework ................................................................ 8 Figure 4: STI Outbound Interfacing Schematic.................................................................. 9 Figure 5: U of M Outbound Interface............................................................................... 10 Figure 6: Simple schematic for a data warehouse - the ETL process............................... 13 Figure 7: The Information Mashup fabric ........................................................................ 26 Figure 8: Outbound Interface based on ESB .................................................................... 36 Figure 9: ChainBuilder ESB product schematic............................................................... 39 Figure 10: ChainBuilder ESB format Editor .................................................................... 45 Figure 11: ChainBuilder ESB map editor......................................................................... 47 Figure 12: ChainBuilder ESB Driver File Setup .............................................................. 48 Figure 13: ChainBuilder ESB Connection File Editor ..................................................... 49 x Figure 14: ChainBuilder ESB component flow editor...................................................... 51 Figure 15: ChainBuilder ESB Admin Console – Components/Control ........................... 52 Figure 16: ChainBuilder ESB Admin Console – Assemblies/Control............................. 54 Figure 17: ChainBuilder ESB Admin Console – Endpoints Status.................................. 54 xi Chapter 1: Problem Statement Data integration, the process of combining data from different sources into a unified view, has become a significant problem in the field of computer science. As the volume of data and rate of information exchange increases, data integration becomes more challenging. An ideal data integration system is the one that allows loose coupling between heterogeneous

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    74 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us