By Suresh Sharma on Mar 05, 2012
Oracle announces SOA Suite 11g R1(126.96.36.199.0) Healthcare Add On. It can be downloaded from SOA Suite for healthcare integration OTN download page. Some of main highlight for this healthcare release includes:
Ease of Installation : One of the main focus for the 11g R1 (188.8.131.52.0) healthcare release is to ensure the ease of installation for all healthcare components (through automated scripts) on top of standard SOA Suite 11g R1(184.108.40.206.0) install.
Performance Improvements: This 11g R1 (220.127.116.11.0) healthcare release brings huge performance improvement for typical HL7 MLLP provider use cases. Apart from the code level optimization we have introduced a bunch of tuning knobs -- at application, composite and database level to achieve high throughput.
Additional Protocol Support: This release supports HL7 Version 3 message structures. We have added supports for File, FTP, SFTP, JMS, and HLLP protocols in additions to MLLP 1.0, MLLP 2.0 and TCP/IP support that we had in our earlier release.
Alert and Contact : The alert notification feature for SOA Suite for healthcare integration works in conjunction with the built-in notification framework of Oracle User Messaging Service (UMS), Oracle SOA Suite human workflow services and Enterprise Manager. It is extended for some of specific healthcare events like error occurred in specific endpoints e.g: Creating alerts for an error occurs during inbound or outbound message processing, delivery to endpoints, or delivery to internal delivery channels.
Endpoint Pair: Endpoint Pair is a concept that ties 2 related HL7 endpoints (1 for sending and 1 for receiving messages) as a unit for management and monitoring. This will allows enabling / disabling the related endpoint pair at the same time, visualizing supported documents for the pair intuitively, and displaying related monitoring data (message counts and actual messages) together.
Sequencing View: In typical healthcare systems the message can be in waiting or stuck in the waiting state because of sequencing and error conditions or message processing delays. The sequencing view will help drill down into the endpoint dashboard where the entire message queue can be seen.