IBM Information Integration Solutions, Healthcare Sector Claims Attachments Underpinning

Similar documents
WebSphere Transformation Extender

Introduction to WebSphere Process Server and WebSphere Enterprise Service Bus

IBM Enterprise Service Bus for Healthcare

Combined Insurance Company of America

Arkansas Blue Cross Blue Shield EDI Report User Guide. May 15, 2013

Xerox EDI Direct Claims Gateway Communication Document for ASC X12N 837 Health Care Claim Transaction Submission

Klarna Tech Talk: Mind the Data! Jeff Pollock InfoSphere Information Integration & Governance

Enterprise Service Bus Defined. Wikipedia says (07/19/06)

The Continuity of Care Document. Changing the Landscape of Healthcare Information Exchange

IBM Software Group. IBM WebSphere Process Integration Technical Overview

Communications and Connectivity

Purpose What is EDI X EDI X12 standards and releases Trading Partner Requirements EDI X12 Dissected... 3

Data Integration Checklist

SCA-based Enterprise Service Bus WebSphere ESB

Executive summary. Table of Contents. Benefits of an integration platform. Technical paper Infor Cloverleaf Integration Suite

Web based document management Simple, Yet Sophisticated Workflow HTML Forms. Business Process Automation A guide to capture tools for VisualVault

Managed File Transfer

Enterprise Information Integration (EII) A Technical Ally of EAI and ETL Author Bipin Chandra Joshi Integration Architect Infosys Technologies Ltd

How To Use Ansi X12N For A Business

XEROX EDI GATEWAY, INC.

How To Use An Electronic Data Exchange (Edi)

iway Service Manager A Foundation for Enterprise Integration iway Service Manager

Integration using IBM Solutions

IBM WebSphere application integration software: A faster way to respond to new business-driven opportunities.

HIPAA Compliance Tools: ANSI ASC X12N HIPAA Implementation Guides

CMS. Standard Companion Guide Transaction Information

Redbook Overview Patterns: SOA Design with WebSphere Message Broker and WebSphere ESB

The webmethods ESB. The Foundation of your SOA. Jean-Michel Ghyoot, Principal Solution Architect, March 28, 2013

Increasing IT flexibility with IBM WebSphere ESB software.

JOURNAL OF OBJECT TECHNOLOGY

BLUE CROSS AND BLUE SHIELD OF LOUISIANA DENTAL CLAIMS COMPANION GUIDE

WebSphere ESB Best Practices

276/277 Health Care Claim Status Request and Response Transactions

JOURNAL OF OBJECT TECHNOLOGY

OpenText Output Transformation Server

A standards-based approach to application integration

Improve business agility with WebSphere Message Broker

276/277 Health Care Claim Status Request and Response Transactions

Introduction. Companion Guide to X12 Transactions version 5010

Integration in Action using JBoss Middleware. Ashokraj Natarajan - Cognizant

Service Oriented Data Management

IBM WebSphere MQ File Transfer Edition, Version 7.0

HEALTH CARE CLAIM STATUS REQUEST AND RESPONSE

EII - ETL - EAI What, Why, and How!

Principles and Foundations of Web Services: An Holistic View (Technologies, Business Drivers, Models, Architectures and Standards)

Increasing IT flexibility with IBM WebSphere ESB software.

DeBruin Consulting. Key Concepts of IBM Integration Broker and Microsoft BizTalk

EAI OVERVIEW OF ENTERPRISE APPLICATION INTEGRATION CONCEPTS AND ARCHITECTURES. Enterprise Application Integration. Peter R. Egli INDIGOO.

TITLE: Enhance ESB and BPM solutions with complex data transformation and connectivity for System z

BUS05 The Evolution of Data Integration. John Motler Principal Sales Consultant Informatica

SOA REFERENCE ARCHITECTURE: SERVICE TIER

IBM WebSphere ESB V6.0.1 Technical Product Overview

uently Asked NextGen Questions Share Frequently Asked uently Asked Questions Frequently Asked FAQ Pre-General Release (April-June 2014)

Knowledgent White Paper Series. Developing an MDM Strategy WHITE PAPER. Key Components for Success

United Concordia. HIPAA Transaction Standard Companion Guide

Closer Look at Enterprise Service Bus. Deb L. Ayers Sr. Principle Product Manager Oracle Service Bus SOA Fusion Middleware Division

DATA INNOVATION. Pervasive Data Integrator Migrate, Connect and Integrate to Anything!

Master Data Management. Zahra Mansoori

MarkLogic Semantics in Healthcare and Life Sciences for LIDER COPYRIGHT 2015 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED.

For instance, consider a customer order process. Documents such as orders can originate from paper

837 Professional Health Care Claim Encounter. Section 1 837P Professional Health Care Claim Encounter: Basic Instructions

The ESB and Microsoft BI

MD Link Integration MDI Solutions Limited

ATHABASCA UNIVERSITY. Enterprise Integration with Messaging

Emerging Technologies Shaping the Future of Data Warehouses & Business Intelligence

Administrative Services of Kansas

Motivation Definitions EAI Architectures Elements Integration Technologies. Part I. EAI: Foundations, Concepts, and Architectures

POWERFUL CHANNEL PARTNER SOLUTIONS

What You Need to Know About Transitioning to SOA

TIBCO BusinessConnect EDI Protocol powered by Instream X12 Configuration

Altova partner OEMs MapForce to offer non-technical customers access to its powerful application development and integration technology.

ODEX Enterprise. Introduction to ODEX Enterprise 3 for users of ODEX Enterprise 2

DATA SHEET. Gain a Single Universal Connection. NetDirector HIE. Attorney. to all your trading partners... Laboratories.

Infinite Integration: Unlocking the Value of Enterprise Asset Management through Technology Integration May 2010

New York ehealth Collaborative. Health Information Exchange and Interoperability April 2012

ORACLE DATA INTEGRATOR ENTERPRISE EDITION

POTENTIAL DHH TECHNICAL ARCHITECTURE

SQL Server Master Data Services A Point of View

Combining Service-Oriented Architecture and Event-Driven Architecture using an Enterprise Service Bus

Tomáš Müller IT Architekt 21/04/2010 ČVUT FEL: SOA & Enterprise Service Bus IBM Corporation

Delivering a platform-independent based ESB for universal connectivity and transformation in heterogeneous IT environments.

Health Care Services Review Request for Review and Response

Real Time Adjudication Business Process Model

Relationship of HL7 EHR System Draft Standard to X12N

White paper. Planning for SaaS Integration

An Architecture to Deliver a Healthcare Dial-tone

Web Services Strategy

FMH Benefit Services, Inc.

Claim Status Request and Response Transaction Companion Guide

SOA Myth or Reality??

ecommerce: Oracle B2B 11g

EDI Acknowledgement Transactions 1.1 Strategy for Oregon Trading Partners

Hubspan White Paper: Beyond Traditional EDI

Leveraging Service Oriented Architecture (SOA) to integrate Oracle Applications with SalesForce.com

APEX BENEFITS SERVICES COMPANION GUIDE 837 Institutional Health Care Claims. HIPAA Transaction Companion Guide 837 Institutional Health Care Claim

270/271 Health Care Eligibility Benefit Inquiry and Response

Transcription:

Information Management II Session #4143 IBM Information Integration Solutions, Healthcare Sector Claims Attachments Underpinning Helen Gurevich - Director Healthcare & Insurance, Healthcare Sector February 13, 2006 IBM Software Group 2005 IBM Corporation

Agenda Information Management Claims Attachments Models Structures Human Decision Variant (HDV) vs. Computer Decision Variant (CDV) Standards: X12, HL7/CDA, LOINC Implementation Guides Additional Information Specification (AIS) Transactions Linkage Attachments Workflow Request for Additional Information Federal Register example IBM Information Integration Capabilities for Claims Attachments Implementation WebSphere DataStage TX Future Direction 2

Claims Attachments the road to adjudication automation and fast payment Additional information Payer receives a claim and needs more information Prescription for DME (e.g., wheelchair) Consent form signed by patient Rehabilitation Treatment Plan information X-rays (dental, spinal, etc.) Laboratory reports and/or results A mechanism to transmit clinical information in support of the administrative process Data content standardization will support claims adjudication automation More extensive collections of quality data will enhance medical management Fraud and Abuse prevention 3

Attachment Types Selected for HIPAA Recommendation 1. Ambulance 2. Emergency Department 3. Rehabilitative services 4. Lab results 5. Medications 6. Clinical notes 4

Attachment Models Unsolicited attachment sent with the claim Provider knows the attachment will be required e.g., consent form signed by patient Attachment sent to payer as response to a payer s request for additional information HIPAA Standard request for information 277 LOINC-codified request Attachment response 275 Non-structured, structured, codified LOINC matches answer to the question Entity to entity exchange of patient information 5

Unsolicited - electronic transmission from provider to payer 1 Request for payment by ASC X12N 837 & 275 / HL7 CDA attachment Provider Payer 2 Payment advice sent by ASC X12N 835 could be payment or denial 6

Solicited request - Electronic transmission between the provider & payer Request for payment by ASC X12N 837 1 Provider 3 Request for additional information by ASC X12N 277 Additional information by ASC X12N 275 / HL7 CDA 2 Payer 4 Payment advice sent by ASC X12N 835 could be payment or denial 7

Attachment Structures Non-codified, Structured Non-Structured Scanned image (fax, pdf, rtf, html, or jpeg) <section> Codified, Structured <caption>ems TRANSPORT, DESTINATION SITE INFORMATION <caption_cd V="15512-7"/> </caption> <paragraph> <caption>ems TRANSPORT DESTINATION SITE NAME <caption_cd V="18582-7"/> </caption> <content>alfred Newman Neurological Institute</content> </paragraph> <paragraph> <caption>ems TRANSPORT, DESTINATION SITE ADDRESS <caption_cd V="18583-5"/> </caption> <content>123 Main St; Anytown, UT 85912 <local_markup descriptor="ad"> <local_attr name="lit" value= 123 Main St"/> <local_attr name="cty" value= Anytown"/> <local_attr name="sta" value="ut"/> <local_attr name="zip" value="85912"/> </local_markup> </content> </paragraph> </section> HL7 CDA codified (HL7 v3 XML CDA mark-up) <section> <caption>history of Present Illness</caption> <paragraph> <content> Henry Levin, the 7th is a 67 year old male referred for further asthma management. Onset of asthma in his teens. He was h twice last year, and already twice this year. He has not been be weaned off steroids for the past several months. </content> </paragraph> </section> <section> <caption>past Medical History</caption> Marked-up Text (HL7 v3 XML CDA mark-up) Submitter (Provider) Information (Name, ID) Receiver (Payer) Information (Name, ID) Patient Information (Name, ID) Claim Information (Date, type, reference, control number) Attachment type Question that was asked by payer (LOINC) Response from provider (LOINC) 8

Human Decision Variant (HDV) vs. Computer Decision Variant (CDV) Human Decision Matches the most prevalent workflow: a person reviewing the information to make a decision low-impact on health plans (easy to display using common tools) low-impact on providers (supports low-cost document preparation and fax-like use of existing paper or document images) Computer Decision Permits computer-assisted adjudication or autoadjudication Includes specifications for breaking data down into computer-accessible elements Includes LOINC codes to identify the questions Includes answer codes suitable to the question Processable in humandecision mode by health plans that have not adopted a computer decision approach Can be applied selectively, one attachment at a time 9

10

Linking the Transactions in the same transmission Attachment submitted with Claim (837 + 275) ISA Interchange Control Header GS Functional Group Header ST 837 Transaction Set Header: Claim PWK Contains provider s control number SE Transaction Set Trailer GE Functional Group Trailer GS Functional Group Header ST 275 Transaction Set Header: Add l Info TRN contains provider s control number SE Transaction Set Trailer GE Functional Group Trailer IEA Interchange Control Trailer 11

CDA Attachment within BIN X12 wrapper BIN segment (BIN02) in the X12N-275 transaction set Start ST*275* BIN*1234* Attachment Information ~SE*16*1001~ End This is the XMLbased CDA document instance that describes an attachment in this case, an ambulance service attachment. <?xml version=*1.0*?> <levelone * * * > <clinical_document_header> * * * <document_type_cd V=*18682-5 DN=* AMBULANCE SERVICE CLAIMS ATTACHMENT */> * * * <patient> * * * (identifies the patient by name, number, etc.) </patient> </clinical_document_header> <body> <section> <paragraph> <caption>ems TRANSPORT, DISTANCE TRANSPORTED<caption_cd V=*15510-1*/></caption> <content>7</content> <content>mi<coded_entry.value V=*mi* S=*2.16.840.1.113883.5.141*/></coded_entry> </content></paragraph></section> <section><paragraph> <caption>ems TRANSPORT, ORIGINATION SITE ADDRESS<caption_cd V=*18581-9*/></caption> <content>124 Elm St, Elmo, UT 85912</content> </paragraph></section> * * * </body> </levelone> LOINC description and code 12

Request for Additional Information Provider Payer Deliver a service Provider submits a claim X12N 837 Need more info to pay? NO Assemble supporting documentation X12N 277 Request for Additional Information Request additional documentation Pay the claim Yes X12N 275 Additional Information Sufficient to pay? NO Deny the claim 13

Federal Register / Vol. 70, No. 184 / Friday, September 23, 2005 / Proposed Rules. p. 56011 Provider Billing Application Conversion utility translates X12N 275 data for Payer Application Auto Adjudicate? Yes Payment criteria met? NO Yes NO X12N 275 with Attachment as Structured data Utility splits X12N 275 away from CDA based attachment Conversion utility translates CDA attachment data for Payer application Make claim and attachment available for manual adjudication Adjudicating staff views attachment via a web browser (using XSL style sheet) Notify provider of reason for denial Pay provider 14

Effective Information Integration is vital for Claims Attachments realization Payer Clearing Houses Providers Institutional /Professional Pharmacy Benefit Managers & Third Party Administrators Employers Subscribers Information Integration Capabilities 1. Integrate Administration and Financials SOA enablement Event driven processing Content based routing Complex transformation 2. Master Data Integration Data search, validation, audit Standardization Matching & survivorship Content integration Federated information access 3. Underpin Analytical Services Parallel execution Metadata management Data transformation Connectivity Federated access UIMA support Replication 15

Claims processing requires timely synchronization of complex information, inside and outside the healthcare enterprise EDI Document (837D, 837P, 837I,275) Healthcare HUB EDI Document (997, 277, 824, 835) 1. Integrate Administration & Financials Load ODS WebSphere DataStage TX HIPAA & EDI Pack Retrieve original Claim Data Update Claims System Claims Adjudication System Return Result Route Dental Claims Dental Adjudication System 16

Synchronized claims processing information can be integrated with member master data in real time Member Information Management Jerry O Donnell 2. Master Data Integration EDI Document (997, 277, 824, 835) EDI Document (837D, 837P, 837,275) Load ODS Healthcare HUB Internal: 567-5599-5 J. O Donnel Dependent: JJ-99-87 Internal: 567-5599-5 Patient: 78654-A1 Dependent: JJ-99 Finance: ABC 123 Patient: 78654-A Finance: ABC 123 Integrate Structured & Unstructured Information Update Claims System DataStage TX HIPAA & EDI Pack Retrieve original Claim Data On Demand Check Master Member Index Consolidated EHR Claims Adjudication System Return Result Route Dental Claims Dental Adjudication System SOA Edition QualityStage & Content Edition 17

IBM Information Integration Solutions provide a mechanism for effective information integration for Healthcare IT initiatives Migrate and consolidate applications Claims processing streamlining Disease management Fraud detection and control Harvest research and clinical data Health and wellness management Single view of the member/ patient Market to the individual IBM WebSphere Information Integration platform Service-Oriented Architecture Understand Cleanse Transform Federate Discover, define, model, and govern information quality and structure Data Standardize, merge, and correct information Transform and enrich information Integrated Metadata Management Parallel Processing Connect Virtualize access to disparate information Content Access, publish, and replicate information 18

WebSphere Business Integrator Message Broker with WebSphere DataStage TX: Unparalleled Capabilities, Unparalleled Value Complex, Hierarchical Data Transformation and additional support for industry standards + Powerful Enterprise Services Bus Solution Industry Packs (SWIFT, EDI, HIPAA, HL7) optional WebSphere DataStage TX Complex Transformation Engine WebSphere DataStage TX Plug-in for WebSphere Message Broker WebSphere Business Integrator Message Broker The Most Powerful Any-to-Any Integration Broker in the Market XSLT transformation Compute ESQL transformation Compute Java transformation Mapping transformation 19

Enhance the Transformation Capabilities of your ESB Scenario Customer needs to enhance existing transformation capabilities for complex, hierarchical data processing Customer needs broad industrystandard data format libraries and support Value Reduce your hand-coding and development time for new applications and complex integrations Extends your current MQ & Broker investments Common, codeless method for all transformation types WebSphere Offerings Core: WebSphere Business Integration Message Broker WebSphere DataStage TX Extended: Industry Packs, Adapters 20

HIPAA Data Integration Ingredients Hospitals Partner administration Transaction validation Auditing / error handling Alert generation Message routing Logging / archiving Partner Profiles Doctors VAN / PRIVATE NETWORK HTTP FTP Email VANs Trading Manager Applications Resource Integration Patients HC Data services INTERNET Output marshalling Target resolution Adapter invocation Routing and Distribution IBM WebSphere DataStage TX File System Clearing Houses Semantic Transformation UB92 to HIPAA NSF & CMS flat files XML to HIPAA Adjudication API to HIPAA Message queues Databases File directories Event Manage -ment Resource Integration Applications Middleware DBMSs File systems System services Message Queue Database 21

The IBM WebSphere DataStage TX Healthcare products and services Pack for HL7 Ver. 2.1, 2.2, 2.3 Ver. 3.0 XML DTDs & Schemas Importers and adapters CDA Schemas Importers Pack for NCPDP Batch 1.1, Communication 5.1 Pack for HIPAA EDI All X12, NSF, UB92, CMS Flat Files Trading Manager X12, HIPAA, EDIFACT Healthcare HUB Solution 22

The Benefits of a Standards-based Approach to Information Integration Healthcare compliance solutions leveraging a standards-based approach to enterprise data integration provide: The Fastest Time to market and Highest Value impact The Easiest to maintain and most Responsive to changes The Highest ROI in terms of technology, hardware and personnel Extremely Scalable and Reliable solutions adaptable to existing IT infrastructures Support for the Complexity of integration paradigms LOWEST COST OF OVERALL OWNERSHIP LOWEST-RISK INTEGRATION APPROACH GREATEST OPPORTUNITY FOR SUCCESS 23

Information Management Thank You IBM Software Group 2005 IBM Corporation