john moriarty [email protected] 12/09/08

John [email protected]/09/08

Solve problems faced by mostorganizations and application vendors… Integration and connectivity of disparate

applications and data Enablement of legacy systems Leverage information from Heterogeneous

systems

Copyright © 2008 BridgeForward Software


BridgeForward is a proven and trusted

leader for integration

A Windows based Integration Engine Connectivity to a wide variety of applications Specializes in connectivity to legacy systems

Edge4 is the embeddable, private-label version of ClearSpan Server


A highly scalable architecture allowing Enterprise level integration deployment Departmental deployment Federated deployment Lightweight embeddable OEM deployment

ClearSpan is designed to leverage the functionality of existing applications


Acquire data from disparate sources Validate data to ensure quality content Transform data into required structures and

formats Route data to target applications Transmit data when and where required


Copyright © 2008BridgeForward Software

Customer Goal•To provide seamless connectivity to and from the hospital’s installed PAS and a multitude of disparate, standalone departmental systems in a fast, cost-effective, standardised and supportable manner using limited internal technical expertise

Highlights•Fast, Reliable Information-Sharing Across Applications.

•Improved Caregiver Workflow. •Increased Speed and Patient Data Accuracy.•Increased Connectivity to the NHS.


Customer Goal• Implement a new web-based patient scheduling system• Establish a enterprise master patient index (EMPI) to provide a master patient identifier for every patient system-wide.• Provide two-way, real-time connectivity to the incumbent PAS in each of BMI’s 50 hospitals.• Provide real-time connectivity to a series of NHS services.

HighlightsSimplified Data Access Improved Caregiver WorkflowIncreased Speed and Accuracy Increased Connectivity to the NHS


Customer Goal•SCI (Scottish Care Information) is a key national IM&T programme to support the entire patient journey by developing and making available consistent IT systems and standards, which are owned collectively, developed and facilitated centrally. SCI supports clinical communication; Electronic Patient Record (EPR); and Electronic Health Record (EHR) Development.

Highlights•To create a seamless service which gives patients continuity of care•More appropriate diagnosis and referral•Improved Outpatient booking process•Improved administrative handling of patient in hospital•Many more…

Confidential and Copyright © BridgeForward Software 2007 20

Writing to proprietary APIs (or screen-scrape)

Procedural Programming (1960’s) Remote Procedures calls Adapters (common set of function calls) Web Services


Massive re-use of existing IT investment Cost savings High degree of flexibility Rapid solution development thru re-use “Mashing-up” : assemble to order


Could be Depends on approach


Lack of concept maturity (SOA not well understood) Expectation that it will be expensive Confused with business transformation Design & operational skills scarce Getting S/W infrastructure to match SOA needs


Existing EAI tools: message-based, hub & spoke

New SOA paradigm: Processed-based, all new

Hybrid Approach: Message-driven SOA Assemble order from incompatible technologies

by “enabling” existing (legacy) applications


Incremental approach Tactical Bottom-up approach


A service oriented, process-based integration suite Multi-Platform Highly Scalable High Performance


Take integration to a new level that’s scalable from device to mainframe

A component based architecture and a business model which will appeal to OEMs

A transition technology that will support SOA while offering the same robustness as EAI


Current EAI integration products provide a largely antiquated centralized enterprise view, not geared toward a distributed integration platform

Service enablement is key to protect organization’s major investments and assets in this area and to support an SOA

Current products not geared to support scalability with small footprint – next generation integration will require “device to mainframe”


Two ways to approach integration Message oriented

Broker based, hub and spoke or federated message passing infrastructure

i.e ClearSpan Process oriented

Orchestrated process based integration i.e Viaduct


Easy integration of disparate applications Allow reuse of existing information assets

reducing cost and time to implementation Expose business logic as a reusable

service Organizations retain their investment in

applications and infrastructure


Service-enable legacy systems and data Brings older applications and data into the world

of SOA without having to apply an enterprise architecture

Easily learn/build/maintain multiple interfaces Reduced implementation and maintenance

costs both in terms of manpower and skills required


Rapid Interface Development & Deployment Highly productive development and

configuration tools Deployment into virtually any

environment from device to mainframe


Enables full reuse of all processes & models

Functionality and productivity enhancement IBM Websphere, Oracle Fusion, BEA WebLogic

and others Available as software only or as an

appliance


Perhaps it is in the eyes of the beholder By web enabling legacy apps under an

SOA structure, real value is achieved at reasonable cost and minimal risk

Also, the incremental. tactical, message-driven approach is surprisingly more scalable than the process-driven model due to its loosely coupled nature.

john moriarty [email protected] 12/09/08

Documents

patient data accuracy

realtime connectivity

formatsroute data

applicationstransmit

seamless connectivity

disparate sourcesvalidate

patient systemwide

quality contenttransform