NORMAL BUSINESS ELIGIBILITY VERIFICATION CUST SERVICE ALLIANCE

Slides:



Advertisements
Similar presentations
A Quick Introduction to EDI Created 3/5/2002 American Electric Power.
Advertisements

What is EDI EDI is the application system to application system transfer of business data from one organization to another in a structured data format.
1 CALIFORNIA DIVISION OF WORKERS’ COMPENSATION MEDICAL DATA TRAINING WCIS Medical Data Collection.
02/03/2006EBT and EDI Overview1 Electronic Business Electronic Data Interchange (EDI) & Electronic Business Transactions (EBT) Standards.
Of X12 Standards Richard Bort Robert Dempsey Bort & Co., Inc. Southern California Edison (818) (626) Southern California e-Business Forum.
Presented by Elena Chan, UCSF Pharm.D. Candidate Tiffany Jew, USC Pharm.D. Candidate March 14, 2007 P HARMACEUTICAL C ONSULTANTS, I NC. P RO P HARMA HIPAA.
Presentation on HIPAA & EDI837 By Euclid Technologies.
EDI Section Outline What is EDI? What do we need (to use EDI)? What do we use EDI for? Advantages Disadvantages.
837 Professional and Institutional Changes 4010A1 to 5010 Presented by John Bock.
ASC X12 Acknowledgments EDI - Session 1 Spring Conference April 16, 2010 Gary Beatty President EC Integrity Senior Manager Deloitte. Vice Chair ASC X12.
Lesson 2 Preparing to Test the 837
Defense Logistics Management Standards (DLMS) Introductory Training
Lesson 4 Reading 837 Error Reports and Making Corrections.
Electronic Data Interchange (EDI)
11 Data Interface Standard for Accounting Software Project Progress Report China National Audit Office June, 2015.
Electronic Data Interchange Assessment Strategies Application Systems Trading Partners Business Associates Application Vendors The Standards Application.
5010 and ICD-10 Are you preparing?. Who are Covered Entities? Health care provider that conducts certain transactions in electronic format Clearinghouse.
©2008 TTW Where “Lean” principles are considered common sense and are implemented with a passion! Product Training Suppliers.
webMethods platform solutions
Customers Training Where “Lean” principles are considered common sense and are implemented with a passion!
E-Commerce User Meeting Click Here To End Show Click Here To End Show Presented by Deb Williams.
EDI FACT.  EDI standards facilitate electronic data interchange (EDI) by providing: Rules of syntax Definition of the data organization Editing rules.
How to Use DDE Professional Billing for Alternative Care Providers.
Washington Health Benefit Exchange C ARRIER T ESTING O VERVIEW & 834 DRAFT C OMPANION G UIDE R EVIEW February 27, :00-3:00 PM.
QAD Pitch Report QAD EDI. Introduction to EDI … the transfer of structured data, by agreed messaging standards, from one computer system to another without.
EDI to XML Using XML to take the headaches out of EDI processing Blair Schneider McKay Clareos, Inc. Clareos, Inc.
G.T.R. Data Inc. Welcome to our EDI Overview. G.T.R. Data Inc. EDI Demonstration This demonstration will take you on a guided tour of our software. After.
EDI Standards Development Pamela A. Grosze, Manager of Systems and Software Engineering, NDCHealth.
Chapter 7: Database Systems Succeeding with Technology: Second Edition.
Prepaid CCN Encounter Data April 18, 2011 Sharon Jackson Darlene White.
Facilitator: Kit Cairns, WIITTS 5010 Working Session It's Time to Get Techie.
EDI or DIE Stuart Richler President G.T.R. Data Inc.
Created by McLure-Moynihan Inc © 2002 MMI All rights reserved. March 14, 2002 Jim Moynihan McLure-Moynihan Inc. Agoura Hills, CA The Basics.
(Business) Process Centric Exchanges
EDI Project Adam Davie Clark Bedsole Tim Jansen Robert Jones.
Data Segmentation for Privacy Agenda All-hands Workgroup Meeting May 9, 2012.
MI Department of Community Health Medical Services Administration Tamara J. Warren- Provider Liaison.
GTR Data Inc. Welcome to our EDI Demonstration G.T.R. Data Inc. August 1997.
EsMD Harmonization Mapping Analysis for X & X
Introducing Python CS 4320, SPRING Lexical Structure Two aspects of Python syntax may be challenging to Java programmers Indenting ◦Indenting is.
By ENTRACK Inc ENTRACK tm GUI/400 EDI System Presentation §©Copyright 2001.
HIPAA Summit EDI Enrollment A Manual Process in the EDI Chain Marcallee Jackson ProxyMed, Inc.
Standard Unique Health Identifier for Health Care Providers April 9, th Annual HIPAA Summit Gail Kocher Highmark.
1 Encore Data Distribution Services Workshop February 19, 2004.
Testing for Successful Deployment: Roundtable Discussion HIPAA COW Spring Conference April 8, 2011.
HIPAA Implementation Guides Down and Dirty Dan Petrosky April 10, 2006 Who needs to understand them?
1 CALIFORNIA DIVISION OF WORKERS’ COMPENSATION MEDICAL DATA TRAINING WCIS Medical Data Collection.
Warfighter Workforce Stewardship Business Support Development Improvements Process Warfighter Workforce Stewardship Business Support Development Improvements.
Agenda 1.What EDI really is? 2.EDI vs. 3.Standards 4.Specifications 5.Transmission 6. Example 7. Advantages 8. Barriers 9. EDI in Poland.
PART 1 XML Basics. Slide 2 Why XML Here? You need to understand the basics of XML to do much with Android All of they layout and configuration files are.
California Health Care EDI ETL Nghia Phan CS 491B – Software Design Lab Fall 2009.
Module 2 1 DLMS Introductory Training Defense Logistics Management Standards (DLMS) Introductory Training Electronic Data Interchange (EDI) Basics and.
Complete Distribution Operations Automation
EDI 101.
Internet Data Exchange - General Navigation - View and Confirm Purchase Orders and Scheduling Agreements NOVEMBER2016 REV C.
HIPAA Implementation Guides Down and Dirty Dan Petrosky April 7,2005
Southern California e-Business Forum
Electronic Transactions Workshop
Eugenia Fernandez IUPUI
Electronic Transactions Workshop
Preparation for Avoiding a Wipeout! Gary Beatty President
Who needs to understand them?
Designing and Debugging Batch and Interactive COBOL Programs
EDI For Administration, Commerce and Transport
Tab Runs/Cost Audit Reports
HIPAA Implementation Guides Down and Dirty
MMA Implementation: Part D Data Implementation
State based or Graph based testing
Support for syntaxes (UBL and UN/CEFACT) Nicosia October 30, 2017
EDI.
Presentation transcript:

NORMAL BUSINESS ELIGIBILITY VERIFICATION CUST SERVICE ALLIANCE DETROIT MI SERVICE CLAIMS CLAIMS PROCESSING ALLIANCE DETROIT MI CUST SERVICE ENROLLMENT

PAPER vs EDI Document - Transaction Little Envelope Functional Group Big Envelope Interchange Postal Service VAN Courier Delivery Point-to-Point Human Audit Machine Audit

EDI Delivery 270 837 834 FUNCTIONAL GROUP EDI INTERCHANGE VAN

Standards Language Claim Document - Transaction Line - Segment Phrase Composite Element Word - Simple Element Code - Identifier Punctuation - Delimiters Grammar - Syntax

SIMPLE AND COMPOSITE DATA ELEMENTS N1*PR*ABC INS CO*PI*ABC47~ TOO*JP*8*F:L~

Levels of Standards Documentation ANSI X12 Standards Documentation Industry Implementation Guidelines Trading Partner Profiles

Section I - Transaction Set Tables ST Table 1 BHT Header Related information usually appears together. HL Table 2 Detail Table 3 Summary SE

Functional Group ID: HC 837 Health Care Claim Table 1 – Header POS# SEG ID NAME REQ. DES MAX USE LOOP REPEAT 005 ST Transaction Set Header M 1 010 BHT Beginning of Hierarchical Transaction M 1 LOOP ID – 1000 10 020 NM1 Individual or Organization Name O 1 045 PER Administration Communication Contact O 2 Table 2 – Detail POS# SEG ID NAME REQ. DES MAX USE LOOP REPEAT LOOP ID – 2000 >1 001 HL Hierarchical Level M 1 003 PRV Provider Information O 1 LOOP ID – 2010 10 015 NM1 Individual or Organization Name O 1 040 PER Administration Communication Contact O 2 555 SE Transaction Set Trailer M 1

837 Health Care Claim: Professional Table 1 – Header PG POS# SEG ID NAME USAGE REPEAT LOOP REPEAT 62 005 ST Transaction Set Header R 1 63 010 BHT Beginning of Hierarchical Transaction R 1 LOOP ID – 1000A SUBMITTER NAME 1 67 020 NM1 Submitter Name R 1 71 045 PER Submitter EDI Contact Information R 2 Table 2 – Detail – Billing/Pay-To Provider PG POS# SEG ID NAME USAGE REPEAT LOOP REPEAT LOOP ID – 2000A BILLING/PAY-TO-PROVIDER >1 77 001 HL Billing/Pay-to-Provider Hierarchical Level R 1 LOOP ID – 2010AA BILLNG PROVIDER NAME 1 84 015 NM1 Billing Provider Name R 1 Table 2 – Detail – Subscriber 573 555 SE Transaction Set Trailer R 1

Transaction Set Tables Permitted segments Required order Presence requirement How many Loops

* * * * * * * * ~ * * * RECEIVER NAME NM1 NM1 Individual or Organization Name Level: Header Syntax: 1. P0809 If either NM108 or NM109 is present, then the other is required. NM101 98 Entity ID Code M ID 2/3 NM102 1065 Entity Type Qualifier M ID 1/1 NM103 1035 Name Last/ Org Name O AN 1/35 NM104 1036 Name First O AN 1/25 NM1 * * * * NM105 1037 Name Middle O AN 1/25 NM106 1038 Name Prefix O AN 1/10 NM107 1039 Name Suffix O AN 1/10 NM108 66 ID Code Qualifier X ID 1/2 * * * * NM109 67 ID CODE X AN 2/80 NM110 706 Entity Relat Code X ID 2/2 NM111 98 Entity ID Code O ID 2/3 ~ * * *

* * * * * * * * ~ * * * BILLING PROVIDER NAME NM1 NM1 Individual or Organization Name Level: Header Syntax: 1. P0809 If either NM108 or NM109 is present, then the other is required. NM101 98 Entity ID Code M ID 2/3 NM102 1065 Entity Type Qualifier M ID 1/1 NM103 1035 Name Last/ Org Name O AN 1/35 NM104 1036 Name First O AN 1/25 NM1 * * * * NM105 1037 Name Middle O AN 1/25 NM106 1038 Name Prefix O AN 1/10 NM107 1039 Name Suffix O AN 1/10 NM108 66 ID Code Qualifier X ID 1/2 * * * * NM109 67 ID CODE X AN 2/80 NM110 706 Entity Relat Code X ID 2/2 NM111 98 Entity ID Code O ID 2/3 ~ * * *

~ * N1 SEGMENT · An ordered collection of elements Elements are variable length Elements are delimited by element separators Segment ends with segment terminator * ~ N1

Data Element Dictionary Listed numerically Same in all segments Data & position vary Length min & max Code lists Type of data

~ * * * * HL HL Hierarchical Level HL01 628 Hierarchical ID Number M AN 1/12 HL02 734 Hierarch Parent ID O AN 1/12 HL03 735 Hierarch Level Code M ID 1/2 HL04 736 Hierarch Child Code O ID 1/1 ~ HL * * * * HL01 628 Hierarchical ID Number The first HL01=1, in subsequent HL segments the value is incremented by 1. HL02 734 Hierarchical Parent Number The HL02 identifies the HL01 that is the parent of this HL segment. HL03 735 Hierarchical Level Code “20” = Billing Provider “22” = Subscriber – Child to Billing Provider “23” = Dependent – Child to Subscriber HL04 736 Hierarchical Child Code “0” No Subordinate HL Segment “1” Additional Subordinate HL Data Segment

Hierarchical Levels in Health Care Claims Billing Provider HL*1**20*1~ Subscriber #1 HL*2*1*22*0~ Subscriber #2 HL*3*1*22*1~ Subscriber #3 HL*7*1*22*0~ Claim Information Service Lines Subscriber #4 HL*8*1*22*1~ Claim Information Service Lines Claim Information Service Lines Dependent #1 HL*4*3*23*0~ Dependent #2 HL*5*3*23*0~ Dependent #3 HL*6*3*23*0~ Claim Information Service Lines Dependent #1 HL*9*8*23*0~ Claim Information Service Lines

Valid Element Types AN - Alphanumeric B - Binary Nn - Numeric (n decimals) R - Decimal (explicit) ID - Code DT - Date TM - Time

LENGTH AN 6/6 - Exactly 6 characters long R 7/10 From 7 to 10 digits long Sign & decimal are not counted in length.

QUALIFIER & VALUE Reese Pairs elements (qualifier & value) · Flexible transaction definitions Reuse elements Sally Peterson CHIEF FINANCIAL OFFICER Reese Supply Company PO Box 1432 Miamitown OH 45432-1432 Phone (513) 725-7543 Fax (513) 725-9876 sally@ohio.net Reese

STANDARDS EVOLVE Working papers · Three times a year Draft standards ANSI standards Version & release 001000 ANSI - 1983 002000 ANSI - 1986 002040 Draft X12 May 89 003000 ANSI - 1992 003020 Draft X12 Oct 91 003021 Draft X12 Feb 92 004000 ANSI - 1997 004010 Draft X12 Oct 97

INVOICE CHANGES Simplify data. · Eliminate transactions. Utilize status information rather than batch data. Reengineer business processes. Exchange information more frequently. INVOICE

Session Summary Standards are based on business requirements. There are multiple details to coordinate. One person should not make all decisions. The business process will change over time.