Your SlideShare is downloading. ×
Connecting Clinical Applications with WebSphere Message Broker
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Connecting Clinical Applications with WebSphere Message Broker


Published on

An overview of the Message Broker Healthcare Connectivity Pack and how it connects HL7 clinical applications

An overview of the Message Broker Healthcare Connectivity Pack and how it connects HL7 clinical applications

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. © 2012 IBM CorporationHealthcare Connectivity PackConnecting Clinical ApplicationsAnt
  • 2. © 2012 IBM CorporationUse RestrictionsThe Program is capable of being used as a medical device data system to transfer, store, and convert data from oneformat to another. The Program may occasionally transmit data to bedside medical devices (e.g., for polling and telemetry).However, the Program itself is not a medical device.The following uses of the Program are prohibited:a. use to control any bedside medical device for clinical, therapeutic or treatment purposes (for example, but withoutlimitation, the administration of medication, anaesthetics, saline solutions and the like);b. use for active patient monitoring (i.e., where the Program is used as the sole means of monitoring life-critical patient data, e.g. heart rates);c. use for decision support (i.e., where the Program is used as the main basis to determine patient-specific treatment orimmediate clinical action); ord. use in any active monitoring that depends on the timeliness of data transmission.Indemnity to IBMLicensee will indemnify International Business Machines Corporation and its affiliated companies against any and all thirdparty claims and liability arising directly or indirectly from any use of the Program by or for Licensee for a use or purposethat is prohibited by the provisions of the foregoing section, "Use Restrictions".As of December 11th2012, WebSphere Message Broker Connectivity Pack for Healthcare is currently available for purchasethrough the Passport Advantage program only for use in the following specific countries :Australia; Austria; Canada; Chile; China; Colombia; Denmark, Finland; Germany; Italy; Malaysia, Mexico; Netherlands; New Zealand; Norway; Poland;Portugal, Singapore; Spain, Switzerland; Sweden, United Kingdom; United States of AmericaFor the current list of licensed geographies please see the following URL: Disclaimer and Availability InformationWebSphere Message Broker Connectivity Pack for Healthcare
  • 3. © 2012 IBM CorporationWhere Does It Fit?3
  • 4. © 2012 IBM Corporation4Patterns for Simplified Development Creates top-down, parameterized connectivity solutions Reduces common problems in flow development Communicates best practices to the broker community Reduces time-to-value for solution development Complements regular solution development in broker
  • 5. © 2012 IBM Corporation5Connecting Clinical Applications Ensure data is consistent across healthcare applications– Consistent regardless of the patient’s point of entry– Ensure data is entered once and only once!– For example, admissions are reflected across all interested systems Reduce effort on clinical and administrative staff– Changes to demographics are reflected in all interested systems– Reduces human error from duplicate data entry Integration done using good practice and architectural principles– Enterprise service bus abstracts away point-to-point integrations– Facilitates better reuse and faster time-to-value for new projects
  • 6. © 2012 IBM CorporationConnecting Clinical Applications Production ready pattern based on HL7 MLLP v2.x Mediates between HL7 clinical applications (1:1 and 1:many)– Focus on ADT, ORU and ORM messages from HL7 standard Easy to extend with custom transformation logic Pattern has excellent multi-threaded performance characteristics– Sender and receiver message flows decoupled by WebSphere MQ queues Supports message validation, duplicate detection, sequencing, and retry6
  • 7. © 2012 IBM CorporationDuplicate Detection Message control identifier (MSH.10) used as key for duplicate detectionMSH|^~&|ADT1|MCM|LABADT|MCM|198808181126|SECURITY|ADT^A01^ADT_A01|MSG00001-|P|2.57MSH|^~&|MB7BROKER.RECEIVER| |ADT1|MCM|201012340084041||ACK|460f99f3a25ca40bd50f|P|2.5
  • 8. © 2012 IBM CorporationSegment Filtering8 Segment filtering removes segments on a per destination basisMSH|^~&|LABORM||||200603081747|security|ORM^O01^ORM_O01|1|P^I|2.5BLG|D|CH|accountid|01CTI|sponsorstudyID|studyphaseidisDE|schedultimepointisCE
  • 9. © 2012 IBM CorporationJournaling9 Journaling writes a copy of every inbound HL7 message to a queue
  • 10. © 2012 IBM CorporationRemainder Processing10 Additional fields and segments not in the model can be saved to a queue
  • 11. © 2012 IBM CorporationSiemens Invision (ADT, BAR, ORU) IMPAC IntelliLab (ADT) Chartlinc (ADT, BAR, ORU)Emtek (ADT, ORU, ORM) PCN (ADT, SIU) Cerner Pathnet (ADT, ORM, ORU)IMS (different customtranscriptions)GE Logician (ADT, SIU) Xtend (ADT)APOLLO (ADT) BEDTRACKING (ADT) RehabManager (ADT)DOMINATOR (ORM) Millbrook (ORU) Cerner RadNet (ADT, ORM, ORU)Omnicell (ADT) Midas (ADT) MedTrack (ADT)EPIC (ADT, ORU, ORM, MDM) Meditech (ADT, ORU) McKessonGE IDX FUJI Cerner MillenniumPower Scribe PineStar AllScriptsSelection of applications integrated using IBM Integration Bus and HL7:A11Connecting Clinical Applications
  • 12. © 2012 IBM CorporationReport Generation
  • 13. © 2012 IBM CorporationReport Generation Production ready pattern to generate reports from HL7 MLLP v2.x– Out-of-the-box solution for text-based reports and file distribution– Easily customised for different destinations (FTP/sFTP/email)– Inbound HL7 message used as the input data for a report template Standard set of connectivity options for the inbound HL7 MLLP– Transport options including leading/trailing bytes, port number and timeout– Acknowledgments, duplicate checking and journaling (audit)– Source feed provided either direct to queue, or published to topic13
  • 14. © 2012 IBM CorporationReport Generation Flexible text based report creation using PHP templates– Complete access to the HL7 message within the template– Fully featured PHP 5.2 runtime embedded within IBM Integration Bus– Enables access to the most popular scripting language worldwide Hundreds of extension functions provided in the PHP runtime– Can be combined with database nodes for table lookups– Easy to break down complex problems into reusable scripts– Deployment to any platform supported by IBM Integration Bus14
  • 15. © 2012 IBM CorporationHL7 Processing Nodes
  • 16. © 2012 IBM CorporationHL7 MLLP Nodes16 These nodes encapsulate the MLLP protocol and HL7 message parsing– Nodes handle de-duplication, validation, acknowledgments and timeout handling– Easy to use nodes enable new HL7 message processing scenarios– Examples include HL7 to data warehouse and HL7 device aggregator integration
  • 17. © 2012 IBM CorporationIBM Integration Bus Built-In Nodes17The HL7 patterns use a variety of IBM Integration Bus built-in nodesHL7 v2 MLLP protocol is built on top of TCP/IP connectionsMessages must be kept in order as they are transformed and routed– Sequencing nodes enable high performance multi-threaded processingPersistent messages ensure data is kept safe and secureHL7 pattern instances can be extended in many different ways!
  • 18. © 2012 IBM Corporation▪IBM Integration Bus has several transformation options:▪ Mapping▪ XSLT▪ ESQL▪ Java▪ PHP▪ .NET▪Reflects the importance of transformation in connectivity solutions▪ User-defined nodes supported for Java and C/C++▪Every transformation option has strengths and weaknesses!– Performance and scalability– Backend integration– Skill sets and learning curve– Developer usability– Portability and maintenance Use a transformation technology appropriate to the problem at hand!18Transformation Options
  • 19. © 2012 IBM Corporation
  • 20. © 2012 IBM Corporation Enable record and replay of in-flight data– Comprehensive audit of messages, web, ERP, file and other data– Completely dynamic configuration requiring no application changes Data recording, capture and store to database– Graphically configure binary, text, XML payload capture– Includes whole, partial and multi-field data from any message Web tooling to view and query data– Search and filtering to identify important messages Replay for redelivery or flow reprocessing– Replay selected data to flows or applications– User selects destinations from auto-populated drop-down list20Record and Replay
  • 21. © 2012 IBM Corporation21 IBM Integration Bus Explorer is our rich client administration application– Provides a secure broker administration and monitoring environment Enhancements provide insight into the healthcare environment– How many HL7 MLLP messages have been processed?– Are my clinical applications connected and working?– What status messages have been sent from my medical devices?– When were the TCP/IP connections last created and dropped?– Visual warnings when queues approach limits and applications disconnectOperational Monitoring
  • 22. © 2012 IBM Corporation22Resource Monitoring▪IBM Integration Bus Explorer has a wealth of monitoring tools!▪ Statistics monitor resource usage across execution groups▪ Range of options to update and visualise the resource statistics
  • 23. © 2012 IBM Corporation23Performance Monitoring▪Monitoring also provided on individual message flows▪ Quick and easy way to identify hot spots in your solutions!
  • 24. © 2012 IBM CorporationMonitoring Clinical Applications24 Displays the current state of all clinical application connections– Warning visuals highlight when connectivity is lost to a clinical application– Monitoring automatically updates when new pattern instances are deployed– Filtering provides fast access to applications of interest based on search terms
  • 25. © 2012 IBM CorporationQueue Monitoring25 Queues ensure data is never lost as it flows through IBM Integration Bus– Warning visuals highlight when queues approach their maximum depth limit– Quick health check provided by the queue depth and last message received time– Queue messages can be encrypted if strong security is required for data-at-rest
  • 26. © 2012 IBM CorporationHL7 Message Definitions
  • 27. © 2012 IBM CorporationHL7 Message Set27 Message set models the HL7 specification and the chapter definitions:
  • 28. © 2012 IBM CorporationCustomizing the HL7 Pattern Customisation points for every destination and source system– Graphical mapper provides an intuitive option for customising messages28
  • 29. © 2012 IBM CorporationUnit Test and Debug
  • 30. © 2012 IBM CorporationTesting the HL7 Pattern Test application makes it easy to send messages to IBM Integration Bus– Wide range of HL7 test messages also provided as resources for the pattern30
  • 31. © 2012 IBM CorporationTesting the HL7 Pattern Healthcare receiver acts as an HL7 destination clinical application– Range of acknowledgment options provided (file, none and auto)– Message framing options also available for custom HL7 MLLP messages31
  • 32. © 2012 IBM CorporationTesting the HL7 Pattern Results display HL7 messages as they are sent and received– Batch sending of messages useful for regression testing scenarios– Messages received and acknowledgments can be copied to the clipboard32
  • 33. © 2012 IBM CorporationDebugging the HL7 Pattern IBM Integration Bus has excellent real time debugging facilities built-in:33
  • 34. © 2012 IBM CorporationUnit Test Client34
  • 35. © 2012 IBM CorporationHealthcare Connectivity Pack35