Testing for Successful Deployment: Roundtable Discussion HIPAA COW Spring Conference April 8, 2011.

Slides:



Advertisements
Similar presentations
1 Medicare HIPAA Issues October, 2002 Kathy Simmons Centers for Medicare & Medicaid Services.
Advertisements

Medicare Fee For Service (FFS) 5010 Are you ready???
TRANSITION TO CMS K.I.D.S. TCES Provider Information:
ADSoyerDO AAOS Practice Management Committee AAOS San Francisco February 10, 2012.
Electronic Submission of Medical Documentation (esMD) Face to Face Informational Session esMD Requirements, Priorities and Potential Workgroups – 2:00pm.
Lessons Learned from the 5010 Conversion to take into ICD-10
Medicare Fee For Service (FFS) 5010 and 837P. Purpose of Today’s Call Highlight differences Provide update on Medicare FFS activities Discuss Errata as.
Blue Cross and Blue Shield of Florida HIPAA 5010 Readiness, Transition and Status (“Open-Line Friday”) “A discussion with external trading partners; senders.
An Approach to 5010 My Experience Tim Bavosi, HRS.
Lesson 2 Preparing to Test the 837
1 Payables Efficiency Through… Access Online PAYMENT PLUS.
1 healthcare IT solutions Copyright Phoenix Health Systems, Inc All rights reserved. Countdown to Compliance For HIPAA Results of the Winter 2004.
Creating a Secured and Trusted Information Sphere in Different Markets Giuseppe Contino.
Electronic Data Interchange (EDI)
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.
Medicare Fee For Service (FFS) 5010 Moving Into Production.
Managing 5010 Migration: Roundtable Discussion HIPAA COW Spring Conference April 8, 2011.
Washington Health Benefit Exchange C ARRIER T ESTING O VERVIEW & 834 DRAFT C OMPANION G UIDE R EVIEW February 27, :00-3:00 PM.
Preparing for ICD-10 Transition Teleconference Hosted by Community Health Association of Mountain/ Plains States (CHAMPS) January 30, 2013, 12:00 PM –
WHAT'S AHEAD? Kathy Whitmire Dale Gibson February 15, 2011 HIPAA 5010, ICD-10, ACO's, VBP, HIGLAS, PECOS.
Welcome to the Learning Community 2015 Roll out webinar Hosted by the Family Institute for Education, Practice & Research The webinar will begin shortly.
ANSI 5010 Deidre Lawson Fryfogle- Product Manager.
Presented by Joan Kossow Data Compliance Manager The Changing Face of Claims Processing &
Case Study of a Large Provider System’s NPI Project Implementation Suzanne Stewart, EDI Coordinator Aurora Health Care Milwaukee, WI.
An EDI Testing Strategy Rosemary B. Abell Director, National HIPAA Practice Keane, Inc. HIPAA Summit IV April 24-26, 2002.
Medicare Fee For Service (FFS) 5010 Troubleshooting with your contractor.
Medicare Fee For Service (FFS) 5010 Late Push For Late Implementers.
Medicare Fee For Service (FFS) 5010 and 837I. Purpose of Today’s Call Highlight significant differences between the 4010A1 837I and the I Provide.
© 2015 TriZetto Corporation ICD-10: Ready, Set, Go! August 27, 2015.
MAC J5 and J8 EDI ACT (December 12, 2013). Purpose of Power Point Current issues MSP Claims 5010 ICD-10 Preparedness & Test Days Monitor Your Business.
MyFloridaMarketPlace Roundtable January 21, :00 a.m. – 12:00 p.m. MyFloridaMarketPlace.
Preparing an ASCA Compliance Plan. Then what? HIPAA Summit IV Washington DC, April 25, 2002 Kepa Zubeldia, M.D.
National Provider Identifier: Implementation Issues Presented by Andrea S. Danes September 25, 2006.
Facilitator: Kit Cairns, WIITTS 5010 Working Session It's Time to Get Techie.
Medicare Fee For Service (FFS) EDI ACT (August 8, 2013) Leader’s Line: Conference ID:
New York State Health Homes Implementation and Billing Update Statewide Webinar Presented by: New York State Department of Health January 12,
HIPAA--The Medicare Experience September, 2002 Kathy Simmons Technical Advisor OIS/Division of Data Interchange Standards.
HIPAA Vendor Readiness Siemens/HDX Audio Telecast July 24, 2002.
Medicare Fee For Service (FFS) EDI ACT (October 10, 2013) Leader’s Line: Conference ID:
© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1 If you cannot locate an individual in order to add Bill to ID(s) or enable.
Practical HIPAA Compliance Strategies for Medical Groups, IPAs and Clinicians The Sixth Annual National HIPAA Summit March 27, 2003 Robert M. Tennant Senior.
CAHABA MAC Conversion MAY-09 Kathy Whitmire Dale Gibson Preparing for the Transition from an FI/Carrier to a Medicare Administrative Contractor (MAC)
Larry Watkins Vice President & COO, Claredi Corporation Co-Chair, ASC X12N Health Care Task Group Co-Chair, WEDI Strategic National Impl. Process (SNIP)
Facilitators: Kit Cairns, Dean Health Greg Margrett, Netwerkes/Ingenix.
Standard Unique Health Identifier for Health Care Providers April 9, th Annual HIPAA Summit Gail Kocher Highmark.
National HIPAA Audioconference: Analysis of the National Provider Identifier Preparing for the NPI Transition January 11, 2006.
Welcome to WPS J8 Implementation - EDI Lisa Cuocci, EDI Sr. Analyst Med B JoEllen Fouts, EDI Sr. Analyst Med A.
TDTWG Update to RMS Wednesday January 14. TDTWG Update to RMS Scope Texas Data Transport Working Group (TDTWG) is responsible for creating and maintaining.
Electronic Submission of Medical Documentation (esMD)
Welcome to the Kansas User Group Meeting January 12, 2015 Please remember to place your phone on mute and do NOT place your phone on hold.
Suppliers on Contract Purchase Order for Services.
ASCA Transaction Extension and Resources to Help Extending Your Compliance Deadline for Transactions & Code Sets April 19, 2002 Steven S. Lazarus, PhD,
HIPAA X12 Transactions Testing and Certification HIPAA Summit Audioconference, May 9, 2002 Kepa Zubeldia, M.D.
The ASCA Compliance Plans, Testing, and Transactions Deployment The Sixth National HIPAA Summit March 27, 2003 Kepa Zubeldia, MD, Claredi.
3M Partners and Suppliers Click to edit Master title style USER GUIDE Supplier eInvoicing USER GUIDE The 3M beX environment: Day-to-day use.
ImmuNet 1 Maryland’s Immunization Information System.
RelayHealth 5010 / ICD-10 Education and Readiness 1 July 19, 2011 Scott Gardner, Director of Product Management Tammy Mrotz, Account Executive Laurie Scherger,
HIPAA Yesterday, Today and Tomorrow? Dianne S. Faup Office of HIPAA Standards Centers for Medicare & Medicaid Services.
Provider Perspective on Medicare’s COB Edits By George Arges.
Traveling into the Future with the 5010 Implementation Timeline HIPAA COW Spring 2009 Conference Presented by Laurie Burckhardt, WPS EDI Manager.
OptumInsight Training – Provider/Client
An EDI Testing Strategy
Sherry Thomas, CCP, CCP-AS CEO/Director of Education
HIPAA Transactions and Code Sets Implementation June 6, 2003
The Centers for Medicare & Medicaid Services
Are Stakeholders Prepared? Results from the WEDI Survey Conducted in
The Centers for Medicare & Medicaid Services
The Road to Compliance A HIPAA NPI National Landscape Presented by Walter G. Suarez, MD, MPH President and CEO Institute for HIPAA/HIT Education and.
Making Tax Digital for VAT
Presentation transcript:

Testing for Successful Deployment: Roundtable Discussion HIPAA COW Spring Conference April 8, 2011

Rick Hammes, WEA Trust Greg Margrett, Ingenix Barb Pretasky, Franciscan Skemp Healthcare

What is Level I Testing and Compliance? Level I testing is the period when covered entities perform all of their internal readiness activities to prepare for testing the new versions of the standards with their trading partners. Level I Compliance means a covered entity can create and receive compliant transactions that result from the completion of all internal activities and testing. Covered entities should have been prepared to meet Level I compliance by December 31, 2010.

What is Level II Testing and Compliance? Level II testing activities involves external testing with trading partners and should begin by January 1, However, covered entities must be compliant with Level I activities before they can prepare for Level II testing. Level II compliance means that a covered entity has completed end-to- end testing with each of its trading partners, and is able to operate in production mode with versions 5010 and D.O. Covered entities must be Level II compliant by January 2012.

What should already be done? You should have the Technical Report Type 3 (TR3s) from Washington Publishing Company ( these are the “implementation guides” for System upgrades should either be completed or underway. If not, you should already know when your vendor(s) will be ready for 5010 and when upgrades will be available. Your list of most-important payers and their testing requirements and methodologies should be complete. You should know when your clearinghouse(s) will be testing with your most important payers, and if your data can be included for testing.

Are you communicating? You should be! Identify internal and external stakeholders and trading partners and engage them in the process. Coordinate and manage direct connection with trading partners throughout the transition. Contact application vendors to learn of their delivery schedule for the system upgrade(s). Contact clearinghouse vendors to learn of their testing schedule for payers of key interest to the provider. Contact key payers to learn of EDI exchange modifications (e.g., will a new Submitter ID be required for the 5010 version versus the current 4010 version; will telecommunication connectivity changes be required).

Are you training? You should be! Provide training for business and technical staff on the changes identified through your 5010 gap analysis. Training should focus on the following: Understanding the transaction changes. Learning the practice management system (software) changes. Learning new workflow processes.

DON’T WAIT!!! There is only a little over 75% of the year left in which to test with your trading partners. If you go direct to any trading partners, you MUST test with them! If you use a clearinghouse or other intermediary, you MUST test with them! Even providers that have non-ANSI systems must still test with their vendor and/or clearinghouse to ensure that their data that ultimately reaches the payer is compliant in 5010 format!

Things you can do to help your testing work Perform some kind of HIPAA validation on your test files before sending them to your trading partners – don’t use your partners as a validation tool! Verify if your trading partners are using/accepting the 5010 errata version for testing; if not, will they require it in the future? Remember that there are changes in 5010 that will require you to alter how you may be doing things today: PO Boxes and Lock Box Addresses are not allowed in the Billing Provider loop (2010AA); only a physical address is allowed. You cannot combine both a physical address and a PO Box/Lock Box Address in the Billing Provider loop (2010AA).

Things you can do to help your testing work If you have multiple locations that get paid to a Lock Box or PO Box, enter the physical building address in the Billing Loop and enter the PO Box or Lock Box in the Pay To Loop. If you do additional sub-parting of your locations and don't put the PO Box or Lock Box in the Pay To Loop, you will get payments sent to each location that is in the billing loop.

Provider concerns and experiences Payer concerns and experience Vendor concerns and experiences What have you experienced so far?

The HIPAA COW EDI Workgroup has its calls on the second and fourth Tuesday of each month from 2pm to 3pm CST. If you are not on the workgroup list, please sign up at the back of the room so that you can receive the meeting invites. THANK YOU!