EDI Project Adam Davie Clark Bedsole Tim Jansen Robert Jones.

Slides:



Advertisements
Similar presentations
Overview – Version 2.50 New Program - OrthoProLogic Insurance Insurance Queue Insurance Form Electronic claim submission Reporting Moved from separate.
Advertisements

SFA Inventory Scanning Fortune 500 client Footwear and Apparel Company in US Currently running Next Gen SFA Application which is a full fledged web based.
Easy DCR Development Control Regulation Online Building Permission System.
© 2009 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Career Education Chapter 7: Creating Claims Computers in the Medical Office.
Health Care Claim Preparation & Transmission Chapter 8 OT 232 Lecture 2 1OT 232 Ch 8 lecture 1.
CHAPTER © 2012 The McGraw-Hill Companies, Inc. All rights reserved. 8 Health Care Claim Preparation and Transmission.
CHAPTER © 2011 The McGraw-Hill Companies, Inc. All rights reserved. 2 The Use of Health Information Technology in Physician Practices.
© 2011 The McGraw-Hill Companies, Inc. All rights reserved. 2.5 HIPAA Legislation and its Impact on Physician Practices 2-15 The Health Insurance Portability.
An Approach to 5010 My Experience Tim Bavosi, HRS.
The Database Environment
Click a NOTUS Suite- product for a short description NOTUS REGIONAL NOTUS Regional helps regions perform the tasks related to the reimbursement of providers.
1 Introduction to XML. XML eXtensible implies that users define tag content Markup implies it is a coded document Language implies it is a metalanguage.
7 Creating Claims. Learning Outcomes When you finish this chapter, you will be able to: 7.1 Describe the role of claims in the billing process. 7.2 Discuss.
7 Creating Claims.
2 The Use of Health Information Technology in Physician Practices.
Background Info The UK Mirror Service provides mirror copies of data and programs from many sources all over the world. This enables users in the UK to.
Integration case study Week 8 – Lecture 1. Enrolment request (Workstation) Application server Database server Database New University Student Record System.
Microsoft Office 2000 Introducing the Suite. Microsoft Word Key Features of Word: create & edit documents apply formatting features add visual elements.
Mgt 240 Lecture Website Construction: Software and Language Alternatives March 29, 2005.
Presented by Mina Haratiannezhadi 1.  publishing, editing and modifying content  maintenance  central interface  manage workflows 2.
Feeds Computer Applications to Medicine NSF REU at University of Virginia July 27, 2006 Paul Lee.
Chapter 10 Publishing and Maintaining Your Web Site.
Project Implementation for COSC 5050 Distributed Database Applications Lab1.
PCLaw & Electronic Billing
File-Mate 1500 Design Review 1 November 19, 2013 KEVEN ABBOTT, ARCHITECT TYLER CROUSE, SPONSOR LIASON KIANA DELVENTHAL, TEAM LEADER, RECORDER LIAM WESTBY,
Web Design, 4 th Edition 7 Promoting and Maintaining a Web Site.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
The Use of Health Information Technology in Physician Practices
MAHI Research Database Data Validation System Software Prototype Demonstration September 18, 2001
What is SharePoint? Module 1. Module Overview  Defining SharePoint  Understanding How SharePoint is Used  Interacting with SharePoint.
File-Mate 1500 Design Review II
Information Technology for the Health Professions, Third Edition Lillian Burke and Barbara Weill Copyright ©2009 by Pearson Education, Inc. Upper Saddle.
EDI Standards Development Pamela A. Grosze, Manager of Systems and Software Engineering, NDCHealth.
Query Health Operations Workgroup HQMF & QRDA Query Format - Results Format February 9, :00am – 12:00am ET.
Electronic Data Interchange (EDI) Invoices Kim Seagraves February 21, 2007 Oklahoma State University - Stillwater.
Reiman Gardens Plant Collections Database (Dec 0806) Reiman Gardens, one of the largest public gardens in Iowa, occupies 14-acres on the Iowa State campus.
CHAPTER © 2011 The McGraw-Hill Companies, Inc. All rights reserved. 7 Creating Claims.
Introduction  Client/Server technology is seen by many as the solution to the difficulty of linking together the various departments of corporation.
13-1 Application Architecture Application architecture – a specification of the technologies to be used to implement information systems. The blueprint.
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 1: The Database Environment Modern Database Management 9 th Edition Jeffrey A. Hoffer,
1 Chinese Information Processing : Using Computers to Teach and Learn Chinese Week 6 and 7: Creating and maintaining web pages - html and ftp.
File-Mate 1500 Design Review III Keven Abbott Tyler Crouse Kiana Delventhal Liam Westby.
PROGRESS UPDATE CRCCF SYSTEM DEVELOPMENT Container Royalty Central Collection Fund Project 1 July 2014.
Chapter 9 Publishing and Maintaining Your Site. 2 Principles of Web Design Chapter 9 Objectives Understand the features of Internet Service Providers.
An application architecture specifies the technologies to be used to implement one or more (and possibly all) information systems in terms of DATA, PROCESS,
HIPAA Transactions Testing Update Kepa Zubeldia, M.D. September 13, 2004.
NEW YORK REVIEW MODULE & CNPXPRESS New York State Department of Health Child and Adult Care Food Program Karen Trbovich, MS, RD, CDN Public Health.
Experiment Management System CSE 423 Aaron Kloc Jordan Harstad Robert Sorensen Robert Trevino Nicolas Tjioe Status Report Presentation Industry Mentor:
Module 8 : Configuration II Jong S. Bok
1 Service Creation, Advertisement and Discovery Including caCORE SDK and ISO21090 William Stephens Operations Manager caGrid Knowledge Center February.
SelectStar Dblab 석사 1 학기 김지현. 목 차 1. 1.SelectStar Company 의 소개 2.SelectStar Services 3. IBuilder 3.1 Ibuilder Architecture 3.2 IBuilder benefits.
Medical Manager Unit 6 ICBS 170. Medical Manager  Billing Routines Generation of bills and statements sent to guarantors and insurance companies Patient.
IBM Global Services © 2005 IBM Corporation SAP Legacy System Migration Workbench| March-2005 ALE (Application Link Enabling)
DATA MANAGEMENT AND DATABASES. Data Management Data management is the process of controlling the information generated during a research project or transaction.
2) Database System Concepts and Architecture. Slide 2- 2 Outline Data Models and Their Categories Schemas, Instances, and States Three-Schema Architecture.
Evolution of Data Exchange with the New York Citywide Immunization Registry: From Paper to Electronic Messaging Amy Metroka, Vikki Papadouka, Paul Schaeffer,
1 © Charles Schwab & Co., Inc. All rights reserved. Member SIPC ( ). Electronic Trading The Charles Schwab Corporation (Schwab) provides services.
PROJECT SECME Carthik A. Sharma Juan Carlos Vivanco Majid Khan Santhosh Kumar Grandai. Software Engineering Fall 2002.
Oracle HFM Implementation Boot Camp Presented by Saravanan Singaravadivelan Developed by Saravanan Singaravadivelan Senior Consultant Qubix International.
REMI Database Antall Fernandes. REMI ● A relational database to facilitate data - metadata organization of various research studies. ● Interface into.
Qualifacts EDI Project
Electronic Data Interchange (EDI)
Electronic Transactions Workshop
Electronic Transactions Workshop
Databases and Information Management
SharePoint Foundation 2010
Databases and Information Management
Electronic Data Interchange: Transactions and Security
Electronic Data Interchange: Transactions and Security
SDMX IT Tools SDMX Registry
Presentation transcript:

EDI Project Adam Davie Clark Bedsole Tim Jansen Robert Jones

CareLogic Web-based application created by Qualifacts and used by health services organizations Automates the process of sending patient claims from health service organizations to payers (insurance companies, government organizations, etc.) for approval

CareLogic Interface

Electronic Data Interchange (EDI) A standardized method of structuring and formatting the data exchanged between two entities Each payer specifies the EDI file format that health service organizations must use when sending patient claims for approval Different payers want different information about the claim

EDI File Transfer A batch of claims is assembled by the billing manager at the health service organization using CareLogic CareLogic generates an EDI file of the correct format from the batch The billing manager downloads the EDI file from CareLogic and then uploads it to the payer’s system

EDI File Transfer

EDI File Format The file is broken down into segments and elements Segments represent a collection of information Elements are parts of segments and contain information about the claim

EDI File Format Example NM1*IL*1*SMITH*JOHN****MI* A~ SV2*0550*HC>G0154*87*UN*2~ HI*BE:61:::9916~ PER|IC|KATHY|TE| ~ SegmentElementQualifierDescription NM10141Name of Submitter NM10140Name of Receiver (Medicare) NM101ILName of Subscriber (Medicare Bene/Patient) NM10171Name of Doctor (Attending Physician) DTP01435Admission Date/Time REF011CMedicare Provider Number Segment Terminator~ Element Separator* Sub-Element Separator:

System Architecture Qualifacts hosts client servers in a data center Each server contains a database comprising: Patient records EDI file formats Client accesses database via web interface Each client maintains an individual collection of EDI file format records that reflect the requirements of payers in their specific locale Each client can add, edit, and remove EDI file formats from its own database

Project Requirements Create master library of EDI file formats used by various health care claim payers Create mechanism that enables Qualifacts to apply changes to the master EDI library Add, edit, and delete EDI file formats

Project Requirements (cont.) Propagate updated versions of the master EDI library to each client system Master EDI library must be periodically updated EDI format specifications change New payers with different format requirements are encountered at client sites

Analysis - Use Case Diagram

Construct Master EDI Library Collect EDI file formats from existing client databases Design table structure Each EDI file format is associated with a payer Create tables and fill with EDI file format data Segments & Elements Separators

Deploy & Update Master EDI Library Deploy Design mechanism to deploy updated master EDI library database tables to client systems Integrate into CareLogic software build process Update Design code modules that update master EDI library tables in client databases Implement code modules in PL/SQL

EDI Library Deployment System

Manage Master EDI Library Design code modules that enable CareLogic to interface with the master EDI library database Add, edit, and delete payers and their EDI file format requirements Implement code modules in PL/SQL Integrate new functionality into existing CareLogic code