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.

Apollo orion ihic2008_final

1,528 views

Published on

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

  • Be the first to like this

Apollo orion ihic2008_final

  1. 1. Approaches to Hospital Integration Clinical Portal and Interface Engine Brendon McAlevey Senior Consultant Orion Health/Apollo
  2. 2. Hospital Systems Integration • This presentation examines tools for two separate aspects of integration: • Integration of Systems at Back-End / Messaging Level • Requirements for Interface Engine - Rhapsody • Integration of Applications into a “Unified View” for Clinical Users • How a Clinical Portal helps achieve integration - Concerto • Illustrated with two case studies • eThekwini Hospital and Heart Centre (South Africa) • Hospital Son Dureta (Spain)
  3. 3. Rhapsody Integration Engine What should an Interface Engine Do? - Connect together multiple hospital I.T. Systems - Handle complex format translations (eg. HL7 v.2 -> XML) - Make it easy to create/edit interfaces - Allow real-time monitoring and alerts of faults & errors
  4. 4. Interface Engine : Creating Routes • Avoid hand-coding new interfaces • Easily edit/update existing interfaces • Work collaboratively across I.T. team • Automatically create documentation for interfaces
  5. 5. Interface Engine: Mapping Formats • Create custom mappings • Use/edit standard mappings • Reduce hand-coded mappings • Avoid proprietary code
  6. 6. Interface Engine: Monitoring • Monitor status of routes, communication points, message queues, error logs • Access archived messages • Stop/start routes • Remote access
  7. 7. Rhapsody at eThekwini HospitalDurban, South Africa
  8. 8. Interface Engine at eThekwini Hospital • 250 Bed Private Hospital • Specialist Cardiology Unit • Maternity Unit • Paediatric Unit • 7 Operating Theatres• Brand New Facility – built 2007, opened 2008• SAP-based Hospital Information System• Clinical Systems by GE• Integration to SAP systems using Rhapsody• Rhapsody Integration Engine
  9. 9. Concerto Clinical PortalPatient information is typically stored in separate clinicalsystems, each with its own login and password.A Clinical Portal withSingle Sign-On canmanage a user’s accesscredentials so that theyonly need to sign-in once. Once a patient is selected, the clinical user has immediate one-click access to all integrated clinical applications
  10. 10. Clinical Portal Single Sign-on Centralised enforcement of patient privacy and user security Single Complete Source of Information Unified View of Data from Multiple Sources Supports incremental implementation across a hospital/ enterprise “Best of Breed” – not “Big Bang”
  11. 11. Clinical Portal : “Dynamic Patient Summary” • Assembled in real-time from multiple sources • Alerts, Recent Results/Orders • Document + Results Tree • Click-Through to further information
  12. 12. Clinical Portal : Results Reporting Web-based view of individual and cumulative numerical data, such as laboratory results
  13. 13. Concerto Portal at Hospital Son Dureta, Spain Spain
  14. 14. Hospital Son Dureta Palma de Mallorca Balearic Islands, Spain 900 beds Regional reference hospital 50 year-old infrastructure Urban population 375,000 (Palma) Clinical Portal Solution providing: Lab Results Reporting Clinical Notes Emergency Whiteboard Electronic Clinical Orders
  15. 15. Clinical Portal: Phase OneFocus on ED dept where all specialties closely interactGo-Live November 2006Oracle HTB as Clinical Data Repository Rhapsody™ provides HL7 v.3 conversion for data from legacy source systemsConcerto™ provides Unified UI • ED Whiteboard • Results reporting • Electronic clinical orders
  16. 16. Clinical Portal: Electronic Whiteboard • electronic version of the traditional ED whiteboard • Integrated to existing PAS & ED System • Patient status data pulled from multiple systems, eg: -location -responsible clinician -availability of lab results • Updated in real time
  17. 17. Clinical Portal: Phase Two Go-Live April 2007 Second Electronic Whiteboard deployed - Paediatric ED Web-based Clinical Notes for both Emergency Departments Discharge Summaries, automatically populated from Clinical Notes Alerts for Frequently Admitted Patients (notification to clinicians when apatient who is a “frequent flyer” presents again in the ED) Expanded Dynamic Patient Summary and Patient Search Searchable History Report for ED
  18. 18. Clinical Portal: Future Plans• Expansion of solution beyond the Emergency Departments• Deployment of Electronic Whiteboard on wards• Deployment in specialist departments• Expanded capabilities for Clinical Orders, ResultsReporting
  19. 19. Summary Back-end integration -A interface engine is the “beating heart” of an integrated hospital IT framework - A well-designed interface engine can make integration simpler for hospital I.T. Teams – allowing them to focus on more “high value” projects Front-end integration - A clinical portal approach can deliver the benefits of integrated data to clinical users - Using the integrated infrastructure to support better processes, better care
  20. 20. More Information? Apollo SA www.apollo.gr Orion Health www.orionhealth.com

×