1 / 41

Progress Data Integration in Healthcare

Progress Data Integration in Healthcare. A quick overview. Martin van Middelkoop Business Development Manager. October 2009. Mijn passie. Architectural Vision for Healthcare. Problem - Integration Technology Gap. Number of Integrated Resources. ESB. Integration Infrastructure.

pilis
Télécharger la présentation

Progress Data Integration in Healthcare

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Progress Data Integration in Healthcare A quick overview Martin van Middelkoop Business Development Manager October 2009

  2. Mijn passie

  3. Architectural Vision for Healthcare

  4. Problem - Integration Technology Gap Number of Integrated Resources ESB Integration Infrastructure MOM Semantic Integration Queuing Data Integration Common Model Hub-and-Spokes Hand coding Years

  5. Technology Vision for Healthcare Open Health Tools, Architectural Vision

  6. Enabling Plug-n-Play in Healthcare

  7. Progress Software GLOBAL MISSION Headquarters: Bedford, MA Offices: 90 Worldwide Employees: 1,600 Revenues: $512 million NASDAQ: PRGS Founded: 1981 To deliver superior software products and services that empower our partners and customers to dramatically improve their development, deployment, integration and management of quality applications worldwide. INNOVATION EXPERIENCE • #1 Enterprise Service Bus – Sonic ESB Gartner Dataquest • Market Leading Event Processing Platform – Apama Bloor Research • Award winning Semantic Data Integration Product – DataXtend SI Telstra, Telecom Italia, BT, DT • Leading Business Transaction Assurance Product - Actional • Deployed at 120,000 customer sites in 140 countries • 2,000 Partners deliver 5,000 unique business applications • Over 600,000 new users acquire Progress-based technology annually

  8. Adding value to any infrastructure ApplicationPlatform Governance&Management EventProcessing EnterpriseServiceBus Data Services Data Access MainframeConnectivity

  9. Technology Map Actional OpenEdge ApplicationPlatform Apama Governance&Management EventProcessing EnterpriseServiceBus SonicFUSE Data Services Data Access MainframeConnectivity DataDirectObjectStore DataXtendOrbix Shadow

  10. The Progress ecosystemA sample of Progress’ OEM customers • 9 of the top 10 app infrastructure vendors • 8 of the top 10 system infrastructure vendors • 8 of the top 10 packaged application vendors

  11. Our strategic partnership with • EMC uses many parts of Progress portfolio • Healthcare is an important, growing market • Both working closely with healthcare standards bodies and integration groups (e.g., HL7, IHE) to address the challenges of information management and integration in healthcare. • EMC and Progress are working together to identify and advance the capabilities of integration technologies that will be critical to the future of healthcare IT (e.g., Web Services, ESBs, and RESTful Web Services).

  12. Various products and solutions • Captiva eInput • PACS imaging/storage • Documentum • xDB + XML Store • XForms engine, XProc engine • Dynamic Delivery Services • Virtual Patient Record

  13. Virtual Patient Record

  14. SOA for Healthcare

  15. Data Integration Terminology

  16. Cross-enterprise Data Integration Concepts Payments HL7 HL7 Government PHR CCR Record Locator Service Master Patient Index Security Semantic Integration HIPAA Health Plan, Claims Provider HL7 Primary Care Physician EMR NCPDP/X12 Pharmacy

  17. Conceptual Enterprise Architecture in Healthcare Business Logic B2B Gateway HL7, CCR, CDA, DICOM, HIPAA, NCPDP, … Electronic Medical Records Web Portal XML XML HL7 Forms, emails, documents ESB PDQ, PIX, HL7 HL7 HL7 XML XML Patient Master Index COTS Applications ODS Data Warehouse Patient Admin

  18. Data Integration Strategies Messaged Oriented Middleware ESB with Common Messaging Model Patient Locator Radiology Patient Locator Finances Radiology EMR EMR Finances Common Messaging Model DataW/house Pharmacy Patients Emergency Data W/house Patients Pharmacy Emergency Point-to-Point integration ESB with Point-to-Point integration Patient Locator Patient Locator Radiology EMR Finances Radiology EMR Finances Pharmacy DataW/house DataW/house Patients Emergency Patients Pharmacy Emergency

  19. Evolving Approach to Data Integration in Healthcare (internal/global) Patients Locator EMR A industry-standard HL7-based Information Model enables a large-scale data integration through common semantics Hospital Run-time Lab Design Semantic Data Integration B2B Gateway Data Services Business Processes Services Common Messaging Model Patients Claims Emergency Government Physician EMR Finances Radiology Patient Locator semantics capture the formal meaning of data. It is achieved by mapping (or rationalizing) the data source schemas to the Information Model

  20. Conceptual Data Integration Stack Business Architecture – business Dictionary, business Business Processes; SNOMED Information Model – business “lingua franca”; openEHR, HL7 RIM Semantic Mapping Information Architecture Data Integration Architecture –point-to-point, transformation hub, common model Data Architecture –format conversion, technical mapping Applications Java, C#, C++ J2EE, .NET Messages HL7, DICOM, CDA Web Services Data Services Databases

  21. Types of Mappings Technical Mappings HL7 V3.0 HL7 V2.3 Common Messaging Model HL7 V2.3 HL7 V3.0 Semantic Mappings Information Model Common Messaging Model HL7 V2.3 HL7 V3.0

  22. Data Integration in Healthcare

  23. Classes of Data Resources in Healthcare Internal Human Readable PDF Excel Internal Machine Readable Non-XML Standards HL7 2.x COBOL Information Model HIPAA XML Fixed length Delimited Mixed DICOM HL7 3.0 openEHR EN 13606 XML Standards

  24. A Typical Project Radiology DICOM Claims HIPAA Billing XML Lab1 HL7 v2.3 Information Model Central Design-time EMR HL7 Lab2 COBOL Patient XML Clinic1 HL7 v2.3 Emergency CSV Clinic2 HL7 v2.5 Pharmacy HL7 Clinics Labs Claims Radiology Pharmacy Emergency GW Distributed Run-time Bus EMR Patient Admin Billing

  25. Common Data Integration Issues • Speed and quality of transformation development • Life-cycle – changes, merges, impact analysis, reports • Collaboration between analysts and developers • Non-standard formats • “Just like that one, but a little bit different…” • Obscure semantics • “Which HL7 v3 structure does my element go to?” • Message enrichment • How does one generate and maintain message control envelopes?

  26. Use-case Outline • Use-case 1 – HL7 2.x to 3.0 mapping demo • Use-case 2 – DICOM to HL7 2.x discussion • Use-case 3 – COBOL to HL7 RIM mapping demo • Use-case 4 – openEHR Information Model browser demo • Points • Information Model as a common • Designed to handle size/complexity of models, formats, schemas and mappings • Meta-data driven

  27. Use-case 1 – Standard to Standard Conceptual HL7 RIM HL7 2.x HL7 3.0 In Semantic Integrator POLB_IN224200 POLB_IN224200 ORU_R01 ORU_R01

  28. HL7 RIM Core

  29. Navigating the Model

  30. Guiding through the Structure and Documentation

  31. Semantic Mapping to Information Model

  32. Integrated Testing HL7 v2.5 ORU_R01 HL7 RIM HL7 v3 POLB_IN224200 Patient Info Patient Info Patient Info

  33. Use-case 2 - Pathology of a Translation Information Model DICOM HL7 2.x Format Neutralization Format Neutralization Semantic Mapping Semantic Mapping

  34. Custom Format Conversion

  35. SEF – Standard Exchange Format Generated through visual UI Allows formal extensions of HL7 and X12 grammar Formal HL7 Extension Mechanism HL7 Sample SEF Definition

  36. Creating Format Extensions

  37. Use-case 3 – Legacy Connectivity Conceptual HL7 RIM COBOL Copybook COBOL Data

  38. Use-case 3 – Legacy Connectivity Results

  39. Use-case 4 – openEHR Information Model Browser

  40. For more information • Visit www.xmlconverters.com/solutions/healthcare • Visit www.dataxtend.com • Visithttp://www.emc.com/solutions/industry/healthcare-life-sciences/index.htm • E-mail me: • Martin van Middelkoop • mmiddelk@progress.com (upto November 30th, 2009) • My US colleaguesworkingon DXSI and HL7 are • Bill Gino – bgino@progress.com • Boris Bulanov – bbulanov@progress.com • Youcanreach me after November 30th, 2009 at mgvanmiddelkoop@medischegegevens.nl

More Related