Presentation together with Lonneke Dikmans for UKOUG Tech16 about a real use case with Oracle SOA Suite for Healthcare Integration

2. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
ORACLE SOA INTEGRATION FOR
HEALTHCARE – 12C
HL7 real time integration – A Case Study
Lonneke Dikmans & Bruno Neves Alves

3. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
PROGRAM AGENDA
About us
The Use Case
Solution Architecture
Deployment Architecture
Exceeding Expectations
Future Challenges
Oracle SSHI12.2.1 – What’s New?
2
3
4
5
3
6
7
1

4. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
ABOUT US
4

5. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
Lonneke Dikmans
Consultant and Managing partner at eProseed
Specializing in SOA and BPM
Oracle Ace Director
Bruno Neves Alves
Partner and Technical Director at eProseed UK
Specializing in SOA and BPM
Oracle Middleware Consultant
5
ABOUT US

6. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
THE USE CASE
6

7. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
CHILDREN’S HOSPITAL OF PHILADELPHIA
• Founded in 1855
• Ranked one of the best Hospitals in US
• First hospital in US devoted exclusively to pediatric medicine
• Full Oracle Stack
– Exadata
– Database
– FMW
– Could Control
7

8. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
SSHI COMMON CUSTOMER’S CHALLENGES
• Integration across HC information silos
• Modernize based new market trends:
– Message Standard evolution (HL7 v3, CDA, CCD)
– Moving from a Hub and Spoke to a SOA Centric platform
– Introduction of various integration standards and patterns (webservices, etc)
• Service Oriented Architecture (SOA) integration introduction
• Improved cross system visibility
8

9. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
CHOP’S CHALLENGES
• Migration from Sun Java CAPS / SeeBeyond eGate to Oracle SOA
Healthcare
• Tightly-coupled, limited concurrency, exception handling
• Reduced Configurability
• Long development cycles and difficult to scale
–point to point, do not scale and difficult to maintain
• High cost of ownership
9

10. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
• Build an HL7 ADT message broker
• Connect > 200 Healthcare
Applications
• Process 3 M Msg/Day
• 100.000 Inbound -> Fan – Out
millions
• Reduce time-to-market for application
integration
• Frequent routing rules update
• Empower of business users to
configure routing and transformation
rules
THE UBER USE CASE

11. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
• ADT Messages Exchange
• Scheduling,
• Admissions,
• Transfers
• Discharges,
• Etc.
• HL7 ADT A05 Pre– Admission
• HL7 ADT A01 Patient Admission
• HL7 ADT A04 Patient Registration
• HL7 ADT A03 Patient Discharged
• HL7 Acknowledge Reply
A TYPICAL UBER USE CASE
Laboratory
Radiology
Pharmacy
Cardiology
Urgency

12. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
• ADT Message Processing
– Parsing and Construct
– Validation
• > 50 ADT Event Types
• HL7 Acknowledge
• ADT Message Sequencing
• MLLP Protocol
• Message Enrichment
• Content based message routing
– Department
– ADT Event Type
• Message Filtering Rules
– Event Type
– Department Confidentiality
– Any other content information
• Enhanced configurability
experience
12
UBER USE CASE REQUIREMENTS

13. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
• Demanding Performance
– 3M/day
– Max Processing time 3 sec
– Peak Time – 40% - 4h
– 65 Mps - Avg
• Maximum Reliability
– 0 message loss
• Large Document Processing
• System Availability
– Up-time Goal - 99.99% - 24/7
• Monitoring
– Endpoint Disconnection
– Message End-to-End Tracking
– Alerts
13
UBER USE CASE REQUIREMENTS

14. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
SOLUTION ARCHITECTURE
14

15. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |15
10 REASONS . WHY SSHI
1 Pit Stop for Healthcare System
Endpoints, Document
2 Multiple Document Protocol Support
including native support of HL7
4 Document Definition Tools
Available
7 Multiple Transport Protocols Support
3 Document Translation, Validation
and Construction
6 Oracle Fusion Middleware integration
platform
10
E2E Message Monitoring and Auditing
8 Supports Sequencing
5 Native MLLP support
9 Proactive and reactive fault handling

16. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
WHAT ABOUT ORACLE SOA SUITE – SCA/OSB?
• Composite layer for:
– Integration with SSHI (HC Adapter JMS Binding & In Memory)
– Orchestration
– Dynamic Routing and Transformation Rules by content
– Mapping for message normalization
– Enrichment
– Result Caching
– Integration with legacy systems
– Exception Handling
16

17. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
DESIGN PRINCIPLES (1)
1. Extensibility
– Add message types,
– Add or replace downstream applications
– Change the existing routing, filtering and transformation rules
2. Configurability
– Existing routing rules, transformations and filters should be configurable
– Change parameters of filters without having to change code or redeploy the solution
3. Reliability
– High Availability
– Store and Forward
– Disaster Recovery
– Zero Message Loss
17

18. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
DESIGN PRINCIPLES (2)
4. Performance
– Demanding performance without decorating reliability
5. Maintainability
– The solution should be easy to maintain
– New FMW developers should be able to understand the UBER solution quickly
– Best Practices and Governance principles
18

19. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
IMPLEMENTATION (1)
1. Internal Canonical Model (based in ADT Canonical)
– Reduced translations
– Dynamic transformations
2. Sequencing
– Interface Sequencing
– HC API discarding
3. Message Validation
– Protects Uber and Downstream Apps from invalid messages
19

20. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
IMPLEMENTATION (2)
4. Exception Handling
– Central and cross architecture exception handling (HC + SOA)
– Sequencing Management (No Routing, Exception, Filtering, etc.)
– Configurability (Notifications, etc.)
5. Healthcare Adapter
– OOB standard Integration (no boiler plate)
– Cross domain integration
6. Caching
– OOB OSB caching for Message Enrichment (Department Table)
20

21. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
IMPLEMENTATION (3)
7. Unique Inbound Composite
– Serves all Inbound Composite
8. Generic vs Specific Outbound
– Generic: configurable
– Specific: extendible
9. Oracle Business Rules
– Covers all (Routing, Handling, Exception) rules
– Standard and OOB
– Excel Import/Export
– Run time rules editor
21

22. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |22
HIGH LEVEL CONTEXT

23. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |23
COMPONENT ARCHITECTURE

24. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |25
MEDIATION AND DYNAMIC ROUTING

25. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |28
GENERIC OUTBOUND

26. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |29
SPECIFIC OUTBOUND

27. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
DEPLOYMENT ARCHITECTURE
30

28. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
DEPLOYMENT ARCHITECTURE DESIGN
(DOMAIN TOPOLOGY)
PRD primary DC
Healthcare DomainAdmin Server
port 7001
HC Cluster
(Active - Active)
Healthcare Server 1
port 7011
NodeManager
port5556
Healthcare Server 2
port 7011
NodeManager
port5556
Soa DomainAdmin Server
port 8001
SOACluster
(Active - Active)
Soa Server 1
port 8011
Soa Server 2
port 8011
OSB Cluster
(Active - Active)
Osb Server 1
port 9011
Osb Server 2
port 9011
NodeManager
port5556
NodeManager
port5556
RAC DB
Node n
Node 1
Node . .
31
NFS
Hitachi 4080 NAS

29. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
DEPLOYMENT ARCHITECTURE DESIGN
• Usage of shared storage for all pinned services
– TLOGs of servers, configured using File persist-stores
– JMS services, configured on migratable targets and using File persist-stores
– Performance gains vs JDBC
• Local storage usage for reducing I/O on the shared storage
– Log files
– Nodemanager
• Usage of Healthcare Adapter configured using JMS for integration between
domains
• Disaster Recovery
– Passive DataCenter available
32
General Considerations

30. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
HA AND DR CONSIDERATIONS
High Availability
– Cluster domain setup (Active-Active) of 2 servers on separate hosts
– All TLogs and Persist stores are on shared storage
– All JMS services are targeted to migratable targets
– Distributed Queues
– Gridlink Data-Sources
– B2B/HC HA Configurations
• b2b.HAInstance
• b2b.AcquiredStatePollingInterval
• b2b.MLLP_HA_Mode
• b2b.HAHeartBeatPing
• MLLP Load balancing and failover
33

31. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
EXCEEDING EXPECTATIONS
34

32. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
RELIABILITY, ACHIEVED
• Maximized reliability obtained by:
– Message persistence
• HC/B2B Tables
• Internal delivery queues
– JMS persistence
– Adequate B2B/SOA configuration
– Suitable exception handling
– Accurate purging and archiving strategy in place
– Reliable monitoring and alerting
– Continuous Integration strategy
35

33. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
• Composites
– OneWayDelivery = Sync
• OSB Result Cache
• Interface Sequencing
• Threads configuration
– B2B, JMS Pooling, Inbound
Composite
• SOA Work Managers
Configuration
• Weblogic tuning for production
• B2B/HC Configurations
– B2B.NIO = True
• Improved performance and scalability
using NIO Async API Protocol with MLLP
– b2b.docPluginList (HL7) – The
order matters
– Others….
• JMS
– File Store Persistence - Direct-
Write-With-Cache (all)
– Tuned Connection Pools
• JVM Tuning
36
PERFORMANCE, ACHIEVED

34. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |37
EXCEEDING EXPECTATIONS
• Standardization of messages and integration approach lead to
reduction of costs
• Flexibility with outbound generic and specific integration
• Agility adding new endpoints and ADT event types
• Normalization of messages eliminated point-to-point costly
conversions
• Performance requirements overcome with 75Mps (~6,5M msg/d.)
• Productivity enhanced using OOTB features as Business Rules

35. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
FUTURE CHALLENGES
38

36. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
CHOP’S CHALLENGES
•Decommission JCaps
•Smart Beds (IoT)
•Engaging patients
•Improved cross system visibility
39

38. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
SSHI 12.2.1 – WHAT’S NEW
41

39. Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |
• Performance Improvements
– In memory sequencing
– DB Load reduction (50% reduction)
– Reduced Memory footprint
– Multiplexed IO
– Coherence Caching usage maximized
• PGP Encryption
– Encrip/Decript Callouts
• New message patterns
– Synchronous Request/Reply over MLLP
– Custom ACKs for non-HL7 messaging
over MLLP
• Alta UI and Mobile Enablement
• Endpoint Cloning
42
ORACLE SSHI 12.2.1 – WHAT’S NEW