The Open eHealth Integration Platform

Open eHealth Integration Platform (IPF)

ICW Developer Conference

Martin Krasser / May 5, 2009

ICW Developer ConferenceMay 5, 20092

Martin Krasser

Position

• Software architect and engineer

Focus

• Distributed systems

• Application integration

• Application security

• ...

Open source projects

• Open eHealth Integration Platform (Founder) http://gforge.openehealth.org/gf/project/ipf

• Security Annotation Framework (Founder) http://www.sourceforge.net/projects/safr

• Apache Camel (Contributor) http://camel.apache.org


Agenda

Part 1

• IPF Introduction

• Programming IPF

• Demo

Part 2

• OSGi Support

• IPF Services

• Demos

Part 3

• Outlook


IPF Introduction (1/5)

Framework for implementing integration logic

• Healthcare domain

• General-purpose

Platform to deploy and run integration solutions

• OSGi-based with IPF services in service registry

• Embedded, standalone and distributed deployments

Based on Apache Camel

• Routing and mediation engine

• Enterprise Integration Patterns (EIPs)

• Domain-specific language (DSL)



Project

• Hosted at the Open eHealth Foundation

• Open source under Apache License, Version 2

• Latest release – IPF 1.6.0 (April 2009)

• http://gforge.openehealth.org/gf/project/ipf/

- Subversion repository

- Release filesystem

- Issue tracker

- Mailing lists

• http://repo.openehealth.org

- Reference documentation

- Contribution guidelines

- Build server and build reports

- Maven and OSGi bundle repository



Technologies

• Java and Groovy

• Springframework

• Apache ActiveMQ (optional)

• „Camel components“ (for connectivity)

Connectivity

• Protocols (HTTP, SOAP, FTP, SMTP, MLLP ...)

• Interfaces (JMS, JPA, JDBC ...)

• More than 70 Camel (connectivity) components!



Development

• Focus on programming (internal DSL)

• DSL is easy to extend

• Platform is easy to extend

• No graphical route designer

• ...

IPF applications @ ICW

• Medical Service Bus (MSB)

• IHE profiles (PIX, PDQ, XDS)

• Device connectivity server (DCS)

• LifeSensor adapter (LSA)

• IPF inside eHF

• ...



Apache Camel

IPF Core

HL7 support

CDA support

IHE support Code mapping

Large message support

Event infrastructure

OS

Gi s

upp

ort

Develo

pm

en

t tools

Flow management

Ma

na

ge

me

nt c

onsole

sSystem overview

Core processors

Pe

rform

an

ce

test s

up

po

rt

Part of presentation and demos


Programming with Camel

Overview

• Components Connectivity to external systems or resources

• Endpoints Send/receive messages to/from external systems

• Processors Transform, validate, filter, route, etc. messages

• Routes Endpoints connected by processors using DSL

Route example

HTTP

Endpoint(inbound)

HTTP

Endpoint(outbound)

XPath

Filter

from("jetty:http://0.0.0.0:8090/subscribers") // inbound HTTP endpoint

.filter().xpath("/person[@name='Martin']") // XPath filter

.to("http://localhost:8080/log"); // outbound HTTP endpoint

Camel DSL (Java)


Programming with IPF

Overview

• All Camel features available

• Dynamic language support (Groovy)

• DSL extension mechanism (Groovy meta-programming)

• Predefined DSL extensions (Contribution from modules)

Route example

?

HTTPEndpoint(inbound)

HTTPEndpoint

(outbound)

HL7Filter

HL7Validator

from('jetty:http://0.0.0.0:8090/admissions') // inbound HTTP endpoint

.unmarshal().ghl7() // HL7 parser

.validate().ghl7() // HL7 validator

.filter {it.in.body.PID[8].value == 'F'} // HL7 filter

.to('http://localhost:8080/log') // outbound HTTP endpoint

IPF DSL (Groovy)


Demo

Implement example route starting from scratch

• HTTP endpoints

• HL7 validation

• HL7 filtering

• HL7 transformation

?


HTTPEndpoint

(outbound)

HL7Filter

HL7Validator

HL7Transformer


Agenda

Part 1


• Programming IPF

• Demos

Part 2

• OSGi Support

• IPF Services

• Demos

Part 3

• Outlook

• Q&A


OSGi Support (1/3)

IPF components are OSGi bundles

• Deployable to any OSGi R4 platform

• Tested with Eclipse Equinox 3.4.1

IPF bundles register platform services

• Flow manager, mapping service ...

• Consumed by IPF applications

IPF extender bundles activate DSL extensions

• DSL extensions contributed by platform and application bundles


OSGi Support (2/3)

Technologies

• Eclipse Equinox 3.4.1

• Spring Dynamic Modules (DM)

Tooling

•maven-bundle-plugin to generate MANIFEST.MF

• Eclipse Plugin Development Environment (PDE)


OSGi Support (3/3)

IPF runtime

• OSGi platform for IPF applications


Implement example route as IPF OSGi application

• Two OSGi bundles

• Deploy to IPF runtime

• Change service implementation at runtime

OSGi Service Registry

Demo

?


HTTPEndpoint

(outbound)

HL7

Filter

HL7

Validator

HL7Transformer

Proxy

Processor

route

bundle

service

bundle


Flow management (1/2)

Purpose

• Monitor messages processed by IPF applications

• Support manual redelivery (replay) of messages

Monitoring

• Successful flows

• Failed flows

• Active flows

• Flow duration

• Message content

• ...

Replay

• Recovery from delivery failures

• Recovery from system failures

• Recovery of application state

• ...

Complements automated

(failure) recovery mechanisms


Flow management (2/2)

User interfaces

• Any JMX client

- JConsole

- ...

• Platform manager

- Eclipse RCP application


Enable flow management for example route


Demo

?


HTTPEndpoint

(outbound)

HL7Filter

HL7Validator

HL7Transformer

Proxy

Processor

route

bundle

service

bundle

platform-camel-flow

bundle

Flow Manager

B E

Replay Strategy

Flow Manager

D


Message Buffering for Delivery Failure Recovery

Compensate unavailability of destinations

• Automated redelivery of messages

• Number of redelivery attemps given by redelivery policy

Implemented with transacted JMS queue

• Transaction rolled back if destination unavailable

• Transaction rollback causes message redelivery

Manual replay of messages using flow manager

• When automated redelivery gives up


Add a message buffer to example route


Demo

?


HTTPEndpoint

(outbound)

HL7Filter

HL7Validator

HL7Transformer

Proxy

Processor

route

bundle

service

bundle

platform-camel-flow

bundle

Flow Manager

B E

Replay Strategy

Flow Manager

JMS Queue

camel-activemq

JMS Component

Proxy

D

osgi-config-jms

bundle


Mapping Service

Mapping between codes from different code systems

• Often needed for HL7 message processing

• Gender codes, encounter type codes ...

Default mapping service

• Accessed via mapping DSL

• Configurable with mapping tables


Demo

mappings = {

gender (

F : 'W',

(ELSE) : { it }

)

}

// Extension to java.lang.String

assert 'F'.mapGender() == 'W'

// Extension to HL7 DSL

assert msg.PID[8].mapGender() == 'W'

Mapping definition Mapping service usage

Gender code mapping


Implement code mapping for example route


Demo

?


HTTPEndpoint

(outbound)

HL7Filter

HL7Validator

HL7Transformer

Proxy

Processor

route

bundle

service

bundle

platform-camel-flow

bundle

Flow Manager

B E

Replay Strategy

Flow Manager

JMS Queue

camel-activemq

JMS Component

D

osgi-config-jms

bundle

Mapping

Service

Mapping

Definition

modules-hl7

bundle

BidiMappingService

mapping

fragment

use via DSL


Resources

Demo source code

• http://repo.openehealth.org/sites/ipf/demo/20090505/demo-osgi.zip

IPF runtime with demo bundles

• http://repo.openehealth.org/sites/ipf/demo/20090505/demo-runtime.zip


Agenda

Part 1


• Programming IPF

• Demos

Part 2

• OSGi Support

• IPF Services

• Demos

Part 3

• Outlook

• Q&A


Outlook (1/4)

DSL for HL7v3 messages and CDA/CCD documents

// Create a CDA builder

CDABuilder builder = new CDABuilder()

// Create a new CDA document

def document = builder.build {

clinicalDocument {

id(root:'2.16.840.1.113883.19.4', extension:'c266')

code(

code:'11488-4',

codeSystem:'2.16.840.1.113883.6.1',

...

)

title('Good Health Clinic Consultation Note')

recordTarget {

...

}

...

}

...

}

// Write document XML to stdout

System.out << document


Outlook (2/4)

DSL for implementing IHE actor interfaces and transactions

from('ihe:xds.b:iti-41?port=8080')

.process { exchange ->

def document = exchange.in.body

// do further document processing here ...

}

// communicate with your document management system

.to('http://...')

// notify about availability of new document

.to('ihe:nav:iti-25:[email protected]')


Outlook (3/4)

IPF as a Service

• Central operation of IPF runtime and applications

• High-availability and scalability are part of service

• IPF application deployment via IPF Eclipse plugins

• Research in progress on scalable data stores

• Experiments with IPF on Google AppEngine


Outlook (4/4)

Performance testing framework

• Instrumentation DSL

• Processing statistics

Grails integration

• IPF plugin for Grails

IPF on ICW connector

• Prototype exists

Thank you for your attention!

[email protected]

The Open eHealth Integration Platform

Technology

Transcript of The Open eHealth Integration Platform