© 2014 IBM Corporation

How to Handle EDI (and

HIPAA) Processing in IBM

Integration Bus with the IBM

Standards Processing EngineBrian Wilson

Executive WebSphere Solution Architect/ Connectivity Team Lead, US North

brianwil@us.ibm.com

Please Note

IBM’s statements regarding its plans, directions, and intent are subject to change

or withdrawal without notice at IBM’s sole discretion.

Information regarding potential future products is intended to outline our general

product direction and it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a

commitment, promise, or legal obligation to deliver any material, code or

functionality. Information about potential future products may not be incorporated

into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

Performance is based on measurements and projections using standard IBM

benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including

considerations such as the amount of multiprogramming in the user’s job stream,

the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results

similar to those stated here.

Agenda

IBM Integration Bus

• Integration capabilities

What is IBM Standards Processing Engine

• IBM Standards Processing Engine for Healthcare Payer

• IBM Standards Processing Engine for Supply Chain EDI

Using IBM Standards Processing Engine with IBM Integration

Bus

• The nodes

• The patterns

2

IBM Integration Bus

Introducing IBM Integration Bus v9

IBM’s Strategic Integration Technology• Single engineered product for .NET, Java and fully heterogeneous integration

scenarios• DataPower continues to evolve as IBM’s integration gateway

A Natural Evolution for WebSphere Message Broker users• Significant innovation and evolution of WMB technology base• New features for Policy-based WLM, BPM integration, Business rules and .NET

Designed to incorporate WebSphere Enterprise Service Bus use cases• Capabilities of WESB are folded in to IBM Integration Bus over time• Conversion tools for initial use cases built in to IIB from day one• WESB technology remains in market, supported. Migrate to Integration Bus

when ready

4

Edge

IntegrationGateway Integration Bus

IBM Integration Bus – a Complete Solution

5

Advanced

Standard

Express Hypervisor

IBM Integration Bus

Simply connect FROM anywhere TO anywhere

Unparalleled range of protocols, routing, message formats and transformation options

Easy to install, learn, develop, deploy and manage, including patterns to simplify solution creation

High performing and scalable, with built-in failover support, optimized for high throughput

Connectivity Packs for Industry specific content (e.g. Healthcare, Retail)

IBM Integration Bus

6

Provides solutions to diverse integration requirements

• Diverse set of connectors

– e.g. MQ, JMS 1.1, HTTP(S), SOAP, REST, File (incl. FTP, FTE, Connect:Direct), DB, TCP/IP, Mobile, MQTT, CICS, IMS, SAP, SEBL, .NET, PeopleSoft, JDEdwards, SCA, CORBA, email

• Diverse set of data formats

– e.g. Binary (C/COBOL), XML, CSV, DFDL, JSON, Industry (SWIFT, EDI, HL7…), IDOCs, User

• Diverse set of operations

– e.g. Route, Filter, Enrich, Point-to-point, Pub/Sub, Sequencing, Timer, Aggregation, Security

– Custom Logic via Graphical Mapping, Java, JAXB, ESQL, XSL, PHP, C & .NET

• Diverse programming styles and orientations

– e.g. batch, real-time, service-oriented, event, data-oriented, resource CRUD access

• Patterns for best practice and quick time-to-value

• Added value through industry specific content

Flexible, dynamic, intelligent solution operation

• Fast, robust, scalable, lightweight architecture

• Various deployment options:

– Traditional OS, cloud, HVE, IWD, Pure and more

• Broad applicability for different operational requirements

– Web UI, MQ, WAS, command line, Java, REST

• Record and Replay, audit, technical / business monitoring

• Built-in caching and high availability for resilient, distributed workloads 6

Easy to Create Solutions

Built-in nodes encapsulate transports, technologies and applications• Makes common tasks easy, and the complex ones possible!

• Use the built-in nodes to reduce the amount of custom code required

• This makes best use of the built-in facilities like activity trace and resource statistics

7

Accelerating integration with Built-in Patterns

8

Reusable solutions that encapsulate a best practice approach to solving a common

architecture, design, or deployment task in a particular context

Can be quickly configured and deployed, and also extended to create new patterns

Service Enablement

Service Virtualization

Application Integration

Encapsulating functionality and

presenting it through a service-

oriented interface

Loose coupling and mediation

between services

Enabling rapid integration of

applications across the enterprise

e.g. SAP

Message-based Integration

File Processing

Custom Patterns

Providing routing, transformation

and logging services for

messages

Managed runtime environment for

processing files such as shredding

into individual transaction records

Create your own patterns to re-

use across your organization

9

IBM Graphical Data Mapper (GDM)

• Visually map and transform source to target data

• GDM designed for whole IBM product set, e.g.

– Integration Bus V9, WebSphere Message Broker v8,

– InfoSphere Master Data Management v10, Integration Designer v7.5/v8

– Rational Application Developer for WebSphere Software v8.5

– Rational Software Architect v8.5, RSA for WebSphere Software v8.5

– Other products yet to announce

• Rich feature set and simplicity make this a good default transformation choice

Directly access stored procedures from within a map

• Complements existing database select, insert, update, delete

• Incorporate user-defined database functions into your graphical transforms

• All standard broker databases supported, e.g. Oracle, DB2, SQLServer…

Graphical TransformationsIBM Graphical Data Mapper

InfoSphere MDM RAD for WebSphere

IBM Integration Designer

IBM Integration Bus

Rational Software Architect

RSA for WebSphere

IBM Integration Bus Differentiators

Engineered for Performance – Advanced parsing capability of messages

– Only need to parse to the point where routing decision is made

Horizontal Scaling– Ability to scale linearly across

– Engineered to effectively utilize all available CPU resources

Superior Transactional– Ensures that a logical unit of work either completes successfully or provides compensation

Extensive .NET Integration Capability– .NET input node allows developers to initiate integration logic from any .NET system

Pre-built patterns to speed time to market– i.e. Multiple file merging with database update

Multiple Development Models available

– Supports XSLT, Java, ESQL, C++, .NET, WTX and 3rd Party integration nodes

Connectivity Model

– Very broad -- Integrates legacy systems, enterprise applications and Web Services (i.e. – ideal for heterogeneous architectures)

IBM Integration Bus Idle Standby (HA)– Standby broker instance can be started on a standby QM instance

Policy Defined Threshold Limits – Set thresholds for integration data flow throughput and specify actions

Built-in Caching – Improve mediation response times and dramatically reduce application load

10

APP APP

Service Mapping

App Server

Events

Integration Bus

0

20

40

60

80

100

120

140

160

180

200

The Wider Context…integrate to anything, anywhere

11

IBM Connectivity & Integration

•Sterling File Gateway for trading

partner B2Bfor API management

• IBM API Management

for API management

• IBM Integration Bus for integration backbone

•WebSphere MQ for messaging backbone

WebSphere MQTT •WebSphere MQTT for mobile, sensors

& device connectivity

•WebSphere Service Registry & Repository

for SOA governance

• IBM Business Monitor for business visualization

•Tivoli Composite Application Mgr for SOA for operational monitoring

•Cast Iron for cloud service

integration

integration gateway

•DataPowerfor security and

integration gateway

What is IBM Standards

Processing Engine

Introduction: What’s driving IBM’s B2B Strategy ?

Existing capabilitiesTraditional Requirements:

� Government, Industry and Regional Standards and

Mandates

� Performance and optimization

� Expanding trading partner

communities

� Feature/Function

enhancements

� Customer mandates

13

Emerging Capabilities

Emerging requirements:� Highly available and

geographically dispersed

environments

� New protocols� Smarter onboarding

� Increasing data volumes

� System & operational visibility

� Ease of deployment

Architecture: IBM’s Vision for B2B, Transformation &

Standards

14

Modularize our approach to

address complex integration

challenges

Address changing market

requirements including high

availability, real-time

processing, archival, and

standards processing

Provide a best of breed, end

to end experience focused

on customer excellence

Built on the strategic IBM

technologies enterprises can

use to grow their business

and improve operational

efficiencies

Managed File TransferP

erim

ete

r se

cu

rity

Industry Standards

Financial ServicesFinancial Services Supply ChainSupply ChainHealthcareHealthcare Customer DefinedCustomer Defined

Ad

ap

ters

Ad

ap

ters

Ad

ap

ters

Orchestration & Infrastructure

Orchestration & Infrastructure

Orchestration, Routing &

Infrastructure

Community Management Visibility

Ma

ilbo

xin

g

Ed

ge

C

om

mu

nic

ation

s

Ed

ge

C

om

mu

nic

ation

s

Ed

ge

co

mm

unic

atio

ns

Modular: Universal Transformation and EDI

Processing• IBM Standards Processing Engine is the next evolution of the IBM

Universal Transformation strategy, providing a modular and more comprehensive solution for transforming documents based on industry standards

15

Validate and Acknowledge

Debulking

Enrichment

Mapping

Addressing

Encoding

De-envelope Transform Envelope

SPE Components & Packaging

SPE Core

• API’s for headless operation

• IIB nodes – primitives for creating IIB

flows

• Providers – TP info & app persistence

for runtime processing

• Engines – WTX, SBI, XSLT

• UI to specify enveloping data

Industry packs

• Drivers – execute doc processing

steps

• Mapping & validation assets

Design Tools

• WTX Design Studio

• GDM for XSLT

• SBI Map Editor

16

SPE core

Pro

vid

ers

En

gin

es

SBI WTX

XSLT

Designassets

SBI Map Editor

WTX Design Studio

Design Tools

SuperPack

TransformDriver

WTX

WTX Validation

Std. 2

Trees

WTX Validation

Std. 1

SBI

SBIValidation

Std. 2

MDB

SBIValidation

Std. 1Drivers – Std. 2

Unpackage

Package

Drivers – Std. 1

Deenvelope

Envelope

APIs IIB

No

de

s

Existing WTX packs

TP UI Assets

Limited TP UI

Defining Trading Partners

The user interface is designed to allow you to define a partner profile with

minimal required entries, taking common defaults for optional properties

“Advanced” properties changeable as needed

Automatic version control to version changes made

17

Modular: De-envelope Services

Inbound envelope definitions define the business meaning of incoming messages

Sender and Receiver and other Standard IDs associate incoming EDI data with partners

Control number sequence and duplicate checking is optional

Validation may be enabled, disabled or delegated to IBM WebSphere TX

Acknowledgements may be enabled and customized

Data is de-bulked and optionally transformed, allowing good transactions to be handled differently from transactions which contain errors

18

Modular: Envelope Services

Outbound envelope definitions

instruct the engine on how to process

outgoing data

Sender and Receiver and other

Standard IDs associate outgoing EDI

data with partners

Control numbers may be assigned,

either locally or globally

Outgoing data may be transformed

and validated allowing valid

transactions to be handled differently

from transactions which contain errors

Outgoing data may be enveloped and

delivered immediately or deferred for

later batch processing

19

Modular: Transformation Services

Transformation maps define the structure of input and output data and the rules for

transformation between fields

In its initial release IBM Standards Processing Engine supports multiple strategic

mappers: WebSphere Transformation Extender, Sterling B2B Integrator and XSLT

maps

20

� Maps may be persisted in

the provided map

repository, on a local file

system or stored in an

external repository and

passed to the engine in

memory

� A repository for XML

schemas and DTDs is

provided and may be used

by the engine for runtime

validation

Modular: Business Integrity

Business Integrity is enforced within the IBM Standards Processing

Engine through the persistence of three kinds of data:

• Trading Partner ManagementConfiguration data used to identify trading partners and establish the rules for B2B document processing. Managed through a browser based User Interface.

• State and processing dataRuntime data used to maintain state between transactions. Managed internally by the engine.

• AnalyticsEvents generated during B2B document processing. Managed by external visibility tools.

21

Benefits: Standards Processing Engine

1. Easy onboarding of Trading Partner.

2. Version Control.

3. Available to run in different platforms (Launcher, IIB and Java

program)

4. HIPAA Level 1 through 5 support

5. DeEnveloping and Enveloping simplified.

6. Ability to process WTX map, Sterling map and XSLT.

7. High performance throughput

22

Availability: IBM Standards Processing Engine

Editions

23

Includes SPE

Includes WTX (except Launcher)

Includes Design Studio

Includes Sterling Map Editor

IBM Standards Processing Engine for Healthcare Payer

IBM Standards Processing Engine for Supply Chain EDI

IBM Standards Processing Engine Pack for Healthcare Payer

IBM Standards Processing Engine Pack for Supply Chain EDI

Changing Requirements: Healthcare Payer

New US “Administrative Simplification” mandates will significantly increase transaction complexity and transaction volumes for payers and providers.

24

Claim/Clinical Attachments: Additional Information to support a Claim or Service. Expected to be mandated 2014

PACDR: Post Adjudicated Claim version for 837P, 837I, 837D – new transactions possible mandate post 2014

Acknowledgments: partner based TA1, 999 and WEDI/SNIP settings

Claim Level rejection and reporting capabilities (277CA)

5010 Errata: incorporating most recent updates

WEDI/SNIP: types 1 to 5 (including external code sets)

Configurable Rules : ability to disable WEDI/SNIP 3 & 4 rules

HIX: support for HIX messages needed for ACA

Changing Requirements: Supply Chain

Standards Process Engine combines two EDI

validation technologies used by thousands of

supply chain organizations

WTX Design Studio and SBI Map Editor combined

bring 30+ years of EDI mapping & validation

expertise

Out of the box support for sequencing of bulk / de-

bulk, transformation, validation and automated

generation of acknowledgements with no process

orchestration dependency

25

Standards Process Engine for Supply Chain offers a rich array of X12 and EDIFACT

envelope parameters and provides EDI control number checking and nonrepudiation

functions

Correlations support operational visibility and message reconciliation

Data from Interchange Compliance Reports powers business reporting and

downstream analytics

WTX Design Studio – Deploy to SPE

26

Assets are under version control

27

Using IBM Standards

Processing Engine with IBM

Integration Bus

Strategic Technology: IBM Integration Bus

� The Standards Processing

Engine has been designed to

leverage the connectivity and

orchestration capabilities

provided by IBM Integration

Bus

� Patterns are provided to quick

start the development of

inbound, outbound or

transformation Message Flows

� Events generated by the engine

may be published to a

WebSphere MQ queue for

consumption by external

visibility and analytics tools

29

Transform Node

Wraps calls to the

Standards Processing

Engine’s transform

function to run a

WebSphere TX, Sterling

B2B Integrator or XSLT

map

Envelope Node

Encodes input data and

either prepares

documents for deferred

enveloping, envelopes

previously prepared

documents or envelopes

documents immediately

De-envelope Node

De-envelopes input data

and returns de-

enveloped transactions,

acknowledgements and

transactions in error

• Note: Requires IBM Integration Bus v9

Strategic Technology: IBM Integration Bus –

De-envelope NodeUse the De-envelope Node to de-envelope input data

Send enveloped data to the in terminal

There are three output terminals and a failure terminal

Transactions which pass validation are sent, one at a time, to the out terminal

Transactions which fail validation are sent, one at a time, to the error terminal

Acknowledgements are sent to the ackterminal

Exceptions are routed to the failure terminal

The De-envelope Node has no basic properties, but it can be configured to output intermediate documents and a storage payload threshold can be optionally specified

30

Correlations and ProcessData are written to the LocalEnvironment

An Interchange Compliance Report may be written to the LocalEnvironment for transactions that are in error

De-envelope example – inbound X12 document

31

There are 4 terminals:

Terminal 1 – OUT writes the translated output to queue Output and then is written to a FTPserver. It also writes out the Correlation and Process Data.

Terminal 2 – ACK writes out the acknowledgement (997, 999)

Terminal 3 – ERROR writes out the error along with the Compliance Report which is thenformatted by a WTX map to remove some characters that interrupts the XML output.

Terminal 4 – FAILURE writes out any failure information or data

Strategic Technology: IBM Integration Bus –

Envelope Node

Use the Envelope Node to encode input data

Send enveloped data to the in terminal

• Documents may be sent individually or sent together using a Collector Node

There are two output terminals and a failure terminal

• Enveloped transactions which pass validation are sent to the out terminal

• Transactions which fail validation are sent, one at a time, to the error terminal

• Exceptions are routed to the failure terminal

A SenderID, ReceiverID, AccepterLookupAlias and optionally an InterchangeID must

be specified in the LocalEnvironment before the Envelope Node is invoked

The Envelope Node has only one basic property which controls whether it prepares

documents for deferred enveloping, envelopes previously prepared documents or

envelopes documents immediately

It can also be configured to output intermediate documents, halt on error and a storage

payload threshold can be optionally specified

Correlations and ProcessData are written to the LocalEnvironment

32

Strategic Technology: IBM Integration Bus –

Envelope Node

33

Prepare documents for later enveloping

Envelope previously prepared documents (batching)

Envelope documents immediately

Envelope example – immediate HIPAA document

SET OutputLocalEnvironment.SPE.SenderID = 'MYCOMPANY';

SET OutputLocalEnvironment.SPE.ReceiverID = 'YOURCOMPANY';

SET OutputLocalEnvironment.SPE.AccepterLookupAlias = '850';

34

Strategic Technology: IBM Integration Bus –

Transform NodeUse the Transform Node to call the Standards Processing Engine’s transform function and run a WebSphere TX, Sterling B2B Integrator or XSLT map

Send input data to the in terminal• Documents may be sent individually or sent together using a Collector Node when a

WebSphere TX map is used• Messages in the MessageCollection are routed to similarly named input cards (in1, in2, etc.)

There is always one failure terminal, but output terminals can be created as needed• Sterling and XSLT maps only produce one output, sent to the default out1 terminal• Output cards from WebSphere TX maps are routed to similarly numbered out terminals (out1,

out2, etc)• Exceptions are routed to the failure terminal along with a Translation Report in the

ExceptionList

The Transform Node has one basic property – the map name• It can be configured with a storage payload threshold

35

The map may be specified in the LocalEnvronment

• MapName – specifies a map in theSPE repository

• MapServerLocation – specifies thepath to a map on a local file system

• DynamicMap – passes a map toSPE as an array of bytes

Correlations and ProcessData are written to the LocalEnvironment

Transform example – Use of Sterling map

36

Creating a New De-envelope Pattern Instance

37

Creating a New Instance – cont'd

38

Deenvelope Message Flow - Raw

39

LocalEnvironment Message Flow - Raw

40

Deenvelope Message Flow - Configured

41

LocalEnvironment Message Flow - Configured

42

Deploying De-envelope Message Flows /

Getting Data out from the Local Environment -

Review

43

Creating a New Envelope Pattern Instance

44

ImmediateEnvelope Message Flow - Configured

45

DeferredEnvelope Message Flow - Configured

46

GetDeferredEnvelope Message Flow - Configured

47

Deploying Envelope Message Flows

48

Setting Envelope Parameters in the Local

Environment - Review

49

Creating a New Transform Pattern Instance

50

Transform Message Flow - Configured

51

ComplexTransform Message Flow - Configured

52

Deploying Transform Message Flows / Setting a

Dynamic Map - Review

53

Example solution architecture

54

Demo

55

Questions?

We Value Your Feedback

Don’t forget to submit your Impact session and speaker

feedback! Your feedback is very important to us – we use it to

continually improve the conference.

Use the Conference Mobile App or the online Agenda Builder to

quickly submit your survey

• Navigate to “Surveys” to see a view of surveys for sessions you’ve attended

57

Thank You

Legal Disclaimer

• © IBM Corporation 2014. All Rights Reserved.• The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained

in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.

• References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.

• If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete:Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

• If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete:All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer.

• Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus® Sametime® Unyte™). Subsequent references can drop “IBM” but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server). Please refer to http://www.ibm.com/legal/copytrade.shtml for guidance on which trademarks require the ® or ™ symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both.

• If you reference Adobe® in the text, please mark the first use and include the following; otherwise delete:Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

• If you reference Java™ in the text, please mark the first use and include the following; otherwise delete:Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

• If you reference Microsoft® and/or Windows® in the text, please mark the first use and include the following, as applicable; otherwise delete:Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

• If you reference Intel® and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete:Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

• If you reference UNIX® in the text, please mark the first use and include the following; otherwise delete:UNIX is a registered trademark of The Open Group in the United States and other countries.

• If you reference Linux® in your presentation, please mark the first use and include the following; otherwise delete:Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.

• If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration purposes only.