Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
USING A RULE BASED SERVICE BUS FOR CONTROLLING DATA-FLOWS IN PATIENT CENTRIC HOSPITAL INFORMATION SYSTEMS Klaus Bayrhammer...
Motivation <ul><li>modern  Hospital Information Systems (HIS)  have to integrate a multitude of specialized sub-systems. <...
Prototyped Architecture <ul><li>based on a service-oriented architecture </li></ul><ul><li>loose coupling  of components <...
Messaging Infrastructure <ul><li>event system  built on top of an enterprise service bus </li></ul><ul><li>persistent and ...
Plug-in Concept <ul><li>integrating new systems can easily be achieved by an additional plug-in concept </li></ul>
Rule-Based Message Routing <ul><li>sub-systems and their corresponding plug-ins communicate exclusively by messages distri...
Rule-Based Message Routing <ul><li>the rule engine can distribute incoming messages to  multiple consumers </li></ul><ul><...
Integrating Off-The-Shelf Software <ul><li>integrating off-the-shelf products in hospital information systems can be compl...
Results and Discussion <ul><li>our system shows how specialized systems can be seamlessly integrated in the work-flow of a...
Upcoming SlideShare
Loading in …5
×

Using a Rule Based Service Bus For Controlling Data-Flows in Patient Centric Hospital Information Systems

666 views

Published on

Published in: Health & Medicine, Technology
  • Be the first to comment

Using a Rule Based Service Bus For Controlling Data-Flows in Patient Centric Hospital Information Systems

  1. 1. USING A RULE BASED SERVICE BUS FOR CONTROLLING DATA-FLOWS IN PATIENT CENTRIC HOSPITAL INFORMATION SYSTEMS Klaus Bayrhammer, Thomas Grechenig, Harald Köstinger, Michael Fiedler, Wolfgang Schramm Vienna University of Technology Research Group for Industrial Software (INSO)
  2. 2. Motivation <ul><li>modern Hospital Information Systems (HIS) have to integrate a multitude of specialized sub-systems. </li></ul><ul><li>I ntegrating applications into a HIS context is complicated and associated with high cost/time requirements. </li></ul><ul><li>a high interoperability within the hospital information system is required. </li></ul><ul><li>work-flows and data-flows have to operate seamlessly across application borders </li></ul>
  3. 3. Prototyped Architecture <ul><li>based on a service-oriented architecture </li></ul><ul><li>loose coupling of components </li></ul><ul><li>data-flow is controlled by a rule-engine </li></ul><ul><li>third party systems can be connected by a plug-in mechanism </li></ul><ul><li>(built solely with open source components) </li></ul>
  4. 4. Messaging Infrastructure <ul><li>event system built on top of an enterprise service bus </li></ul><ul><li>persistent and reliable one-way messaging is provided by the Java Messaging System (JMS) </li></ul>
  5. 5. Plug-in Concept <ul><li>integrating new systems can easily be achieved by an additional plug-in concept </li></ul>
  6. 6. Rule-Based Message Routing <ul><li>sub-systems and their corresponding plug-ins communicate exclusively by messages distributed by a rule engine </li></ul>
  7. 7. Rule-Based Message Routing <ul><li>the rule engine can distribute incoming messages to multiple consumers </li></ul><ul><li>the rules can access the payload of the message as well as the attached meta-data </li></ul><ul><li>for receiving messages a plug-in has to implement a specific interface as well as being registered by the core-system. </li></ul><ul><li>communication is carried out asynchronously, which makes it possible to have multiple results per request . </li></ul>
  8. 8. Integrating Off-The-Shelf Software <ul><li>integrating off-the-shelf products in hospital information systems can be complex and require expensive adaptions </li></ul><ul><li>the plug-in concept enables the HIS to integrate specialized systems without modifications on their core implementation </li></ul><ul><li>the rule based message routing then allows a seamless integration of the sub-system into the work-flow of the HIS </li></ul><ul><li>a PACS (DCM4CHEE) as well as an ERP -System (OpenBravo) have been integrated in the prototype HIS. </li></ul>
  9. 9. Results and Discussion <ul><li>our system shows how specialized systems can be seamlessly integrated in the work-flow of a HIS </li></ul><ul><li>further research has to be conducted to examine further aspects of application integration in the hospital context </li></ul><ul><li>the proposed work is now part of a research HIS developed </li></ul>

×