progress data integration in healthcare

Progress Data Integration in Healthcare

A quick overview

October 2009

Martin van Middelkoop

Business Development Manager

© 2009 Progress Software Corporation2

Mijn passie


Architectural Vision for Healthcare


Problem - Integration Technology Gap

QueuingQueuing

MOMMOM

ESBESB

Hand codingHand coding

Hub-and-SpokesHub-and-Spokes

Common ModelCommon Model

Number of Integrated Resources

Number of Integrated Resources

YearsYears

Integration InfrastructureIntegration Infrastructure

Data IntegrationData Integration

SemanticIntegrationSemanticIntegration


Technology Vision for Healthcare

Open Health Tools, Architectural VisionOpen Health Tools, Architectural Vision


Enabling Plug-n-Play in Healthcare


Progress Software

Headquarters: Bedford, MAOffices: 90 Worldwide Employees: 1,600 Revenues: $512 millionNASDAQ: PRGSFounded: 1981

GLOBAL

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

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

#1 Enterprise Service Bus – Sonic ESBGartner 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

MISSION

EXPERIENCE


Data Services

EnterpriseService

Bus

Governance&

Management

Adding value to any infrastructure

EventProcessing

MainframeConnectivity

Data Access

ApplicationPlatform


Data Services

EnterpriseService

Bus

Governance&

Management

Technology Map

EventProcessing

MainframeConnectivity

Data Access

ApplicationPlatform Apama

DataDirectObjectStore

Shadow

OpenEdge

SonicFUSE

DataXtend

Orbix

Actional


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


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).


Various products and solutions

Captiva eInput PACS imaging/storage Documentum

• xDB + XML Store

• XForms engine, XProc engine

• Dynamic Delivery Services Virtual Patient Record


Virtual Patient Record


SOA for Healthcare


Data Integration Terminology


Cross-enterprise Data Integration Concepts

PHRPHR

ProviderProvider

PharmacyPharmacy

Primary Care PhysicianPrimary Care Physician

Health Plan, ClaimsHealth Plan, Claims

GovernmentGovernment

NCPDP/X12NCPDP/X12

HL7HL7

HIPAAHIPAA

HL7HL7

HL7HL7

CCRCCR

EMREMR

Record Locator ServiceMaster Patient IndexSecuritySemantic Integration

Record Locator ServiceMaster Patient IndexSecuritySemantic Integration

PaymentsPayments


Conceptual Enterprise Architecture in Healthcare

B2BGateway

B2BGateway

WebPortalWeb

Portal

COTSApplications

COTSApplications

ODSODS DataWarehouse

DataWarehouse

Business LogicBusiness Logic

ESBESB

PatientMaster Index

PatientMaster Index

PatientAdminPatientAdmin

Electronic Medical Records

Electronic Medical Records

PDQ, PIX, HL7PDQ, PIX, HL7HL7HL7

HL7HL7

XMLXMLXMLXMLHL7HL7

XMLXMLXMLXML

HL7, CCR, CDA, DICOM, HIPAA, NCPDP,…

HL7, CCR, CDA, DICOM, HIPAA, NCPDP,…

Forms, emails, documentsForms, emails, documents


Data Integration Strategies

Point-to-Point integration

Finances

PatientLocator

Patients

Radiology

Pharmacy

EMR

Emergency

DataW/house

Messaged Oriented Middleware

Patients Pharmacy

FinancesPatientLocator

Radiology

Emergency

EMR

DataW/house

ESB with Point-to-Point integration

Patients Pharmacy

FinancesPatientLocator

Radiology EMR

Emergency DataW/house

ESB with Common Messaging Model

Finances

PatientLocator

Patients

Radiology

Pharmacy

EMR

Emergency

Common Messaging Model

DataW/house


Evolving Approach to Data Integration in Healthcare (internal/global)

Patients Claims Emergency

Common Messaging Model

B2B Gateway

EMR PatientLocator

Finances Radiology

Data Services

Business Processes

Services

Hospital

Government Physician

A industry-standard HL7-based Information Model enables a large-scale data integration through common semantics

semantics capture the formal meaning of data. It is achieved by mapping (or rationalizing) the data source schemas to the

Information Model

Lab

Semantic Data IntegrationSemantic Data Integration

Run-timeRun-time DesignDesign

Pat

ien

tsP

atie

nts

EM

RE

MR

Lo

cato

rL

oca

tor


Conceptual Data Integration Stack

ApplicationsJava, C#, C++J2EE, .NET

ApplicationsJava, C#, C++J2EE, .NET

MessagesHL7, DICOM,CDA

MessagesHL7, DICOM,CDA

Web ServicesWeb Services Data ServicesData Services DatabasesDatabases

Data Architecture – format conversion, technical mappingData Architecture – format conversion, technical mapping

Data Integration Architecture – point-to-point, transformation hub, common modelData Integration Architecture – point-to-point, transformation hub, common model

Information Model – business “lingua franca”; openEHR, HL7 RIM Information Model – business “lingua franca”; openEHR, HL7 RIM

Semantic Mapping Semantic Mapping

Business Architecture – business Dictionary, business Business Processes; SNOMED

Business Architecture – business Dictionary, business Business Processes; SNOMED

Info

rmat

ion

Arc

hite

ctur

eIn

form

atio

n A

rchi

tect

ure


Types of Mappings

HL7 V2.3HL7 V2.3 HL7 V3.0HL7 V3.0

Common Messaging

Model

Common Messaging

Model

Technical MappingsTechnical Mappings

Semantic MappingsSemantic Mappings

Information ModelInformation Model

CommonMessaging

Model

CommonMessaging

Model

HL7 V2.3HL7 V2.3 HL7 V3.0HL7 V3.0

HL7 V2.3HL7 V2.3 HL7 V3.0HL7 V3.0


Data Integration in Healthcare


Classes of Data Resources in Healthcare

HL7 2.xHL7 2.x

HIPAAHIPAA

COBOLCOBOL

HL7 3.0HL7 3.0

openEHREN 13606

openEHREN 13606

DICOMDICOM

XMLXML

Fixed lengthDelimitedMixed

Fixed lengthDelimitedMixed

PDFPDF

ExcelExcel

InformationModel

InformationModel

Non-XML StandardsNon-XML Standards

XML StandardsXML Standards

Internal Machine ReadableInternal Machine Readable

Internal Human ReadableInternal Human Readable


A Typical Project

RadiologyRadiology PharmacyPharmacy EmergencyEmergency

EMREMR

LabsLabsClinicsClinics

PatientAdminPatientAdmin BillingBilling

BusBus

ClaimsClaimsGWGW

Radiology DICOMRadiology DICOM

Billing XMLBilling XML

EMR HL7EMR HL7

Patient XMLPatient XML

Emergency CSVEmergency CSV

Pharmacy HL7Pharmacy HL7

Cen

tral

Des

ign

-tim

eC

entr

alD

esig

n-t

ime

Dis

trib

ute

dR

un

-tim

eD

istr

ibu

ted

Ru

n-t

ime

InformationModel

InformationModel

Claims HIPAAClaims HIPAA

Lab1 HL7 v2.3Lab1 HL7 v2.3

Lab2 COBOLLab2 COBOL

Clinic1 HL7 v2.3Clinic1 HL7 v2.3

Clinic2 HL7 v2.5Clinic2 HL7 v2.5


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?


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


Use-case 1 – Standard to Standard

HL7 2.xHL7 2.x HL7 3.0HL7 3.0HL7RIMHL7RIM

ConceptualConceptual

In Semantic IntegratorIn Semantic Integrator

POLB_IN224200POLB_IN224200

ORU_R01ORU_R01

ORU_R01ORU_R01

POLB_IN224200POLB_IN224200


HL7 RIM Core


Navigating the Model


Guiding through the Structure and Documentation


Semantic Mapping to Information Model


Integrated Testing

HL7 v2.5 ORU_R01 HL7 v2.5 ORU_R01 HL7 RIM HL7 RIM HL7 v3 POLB_IN224200 HL7 v3 POLB_IN224200

Patient InfoPatient InfoPatient InfoPatient Info

Patient InfoPatient Info


Use-case 2 - Pathology of a Translation

HL7 2.xHL7 2.xInformation

ModelInformation

ModelDICOMDICOM

FormatNeutralizationFormatNeutralization

FormatNeutralizationFormatNeutralization

Semantic MappingSemantic Mapping

Semantic MappingSemantic Mapping


Custom Format Conversion


Formal HL7 Extension Mechanism

SEF – Standard Exchange Format Generated through visual UI Allows formal extensions of HL7 and

X12 grammar

HL7 SampleHL7 Sample

SEF DefinitionSEF Definition


Creating Format Extensions


Use-case 3 – Legacy Connectivity

COBOLCOBOLHL7RIMHL7RIM

ConceptualConceptual

CopybookCopybook COBOL DataCOBOL Data


Use-case 3 – Legacy Connectivity Results


Use-case 4 – openEHR Information Model Browser


For more information

Visit www.xmlconverters.com/solutions/healthcare Visit www.dataxtend.com Visit http://www.emc.com/solutions/industry/healthcare-

life-sciences/index.htm E-mail me:

Martin van [email protected] (up to November 30th, 2009)

My US colleagues working on DXSI and HL7 are • Bill Gino – [email protected]• Boris Bulanov – [email protected]

You can reach me after November 30th, 2009 at [email protected]

progress data integration in healthcare

Documents