1 / 21

OCHIN Billing Workshop – Part I

OCHIN Billing Workshop – Part I. Learning Forum 2012. Charge Router Functionality Review and OCHIN Recommendations. What is the Charge Router?. Charge Router is a module sitting between EpicCare and Billing.

taran
Download Presentation

OCHIN Billing Workshop – Part I

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OCHIN Billing Workshop – Part I Learning Forum 2012

  2. Charge RouterFunctionality Review and OCHIN Recommendations

  3. What is the Charge Router? • Charge Router is a module sitting between EpicCare and Billing. • A powerful tool that can review, modify and distribute charges from multiple sources. • Charges from source applications such as EpicCare Ambulatory, Interface, etc. • Charges can be sent to Professional Billing, Hospital Billing or a 3rd party billing system

  4. What can the Charge Router do? • Charge Router Review WQs • Catch chart errors more upstream than Charge Review and Claim Edit Review WQ • Hold charges until the whole encounter is completed and ready for billing • Charge Handler Tasks • Data manipulation on the charges before they drop into billing (i.e. add/delete charges, add/delete modifiers, change procedure codes, add pricing contract, etc.)

  5. OCHIN Recommendations We have set up the following charge handler tasks for some OCHIN members, which might be beneficial for others as well: • MAR Visit Hold Setup • Lab Visit Hold Setup • Addendum Biller Review WQ • Deletion of External Interface Lab Charges • Immunization Administration Charge Coding • Venipuncture Coding • Modifiers Addition/Deletion

  6. Work with your OCHIN Revenue Cycle analyst to request more information or to implement any recommended set up for your organization • Questions?

  7. Billing WQ Routing & Automatic ActivitiesFunctionality Review and OCHIN Recommendations

  8. How are credits created & resolved? Created when a filed payment is: • A recoupment, • Left undistributed, or • Larger than the charge it’s matched to Completed and removed from the Credit WQs when the balance is zero.

  9. How are follow-up records created & resolved? • Follow-up = charge + coverage • Created when claim run is accepted. • Completed & removed when insurance balance = $0

  10. Organizing credit and follow-up records: Routing Setup • Time-based • Deferral tabs in credit and follow-up WQs • Credit deferral WQs • Rule-based • Self-pay vs. insurance credits • Payment types (co-pay, pre-payments) • Payor types • Many other options

  11. Resolving credit & follow-up records: Automatic Activities • Available per WQ or for entire SA • Can automatically perform: • Transfer to another WQ • Create an account note • Create an account letter • Send to System Deferred tab of a WQ • Perform auto-write offs, payment matching, and transfers

  12. Automatic Activities: Credit • Auto Debit Off Small Balance • Auto Transfer Self-Pay Balance to Insurance • Auto to Oldest Outstanding Charge • Over-posted Payments Auto-debit

  13. Automatic Activities: Follow-up Define rules that automatically perform actions based on time elapsed: • Defer • Write-off • Resubmit claims • Perform an Next Responsible Party (NRP) • Change account status

  14. Next steps • Review your current credit and follow-up WQ workflows and needs • Log a JIRA and meet with your Revenue Cycle Member Services analyst to discuss build requirements

  15. Remittance Code MappingFunctionality Review and OCHIN Recommendations

  16. Mapping of ANSI Codes Why is this important? • Electronic files will not load correctly if an EOB/Remit code is not currently in the system and/or mapped. How does a user know if this is the case? • Typically the Remittance is in a “Created” status. Please enter a JIRA and an analyst will be able to determine if this is the case. They may request your assistance to determine what ANSI code it should be mapped to, if non-HIPAA standard code.

  17. Mapping in Epic Consider:Review your Claims Research Follow-Up WQ. If there is a pattern of EOB codes that fall into that queue that do not need manual intervention, consider changing the mapping. When in doubt….send to Research for Biller review. Actions Taken: 1-Not Allowed Adjustment 2-Transfer to Self-Pay 3-Next Responsible Party 6-Write Off Insurance 9-Denied 14-Research

  18. Override Action/Assign Adjustment Code • The Action and Adjustment codes can be different depending on the Payor. • For example: The first screenshot can handle most if not all of your Commercial Payors, but maybe for your Family Planning Coverages/Payors you want a specific adjustment code stating “Family Planning Adj”.

  19. NAA Vs. Write-Off • Difference between the action of 1-NAA and 6-Write Off Insurance • Benefits of using 1 instead of 6 (streamline of manual payment posting)

  20. Other Recommendations • Remit files incoming with payor status of 4-Denial are mapped with action of 9-Denied • If CO45 is sent by payor with full charge amount, override action of write-off/NAA and send to Research for biller review • Identify patterns by code, by payor • Can map different actions at remittance code level by SA and payor lists

  21. Questions?

More Related