Advanced TouchWorks™ EHR Charge Configuration
Is your organization still billing on paper? Are you tired of losing money because of billing mistakes and would you rather see faster reimbursement? In this webcast we’ll briefly discuss some of the benefits that come with implementing the TouchWorks™ EHR Charge Module and its workflows. We’ll also take a deep dive into configuration considerations and the build work that will allow you to customize a solution for your organization.
Originally aired: Friday, December 18th, 2015
Presenters: Jason King and Tracy Kimble
Q: What is the compliant code box that was displayed under provider field?
A: The Compliance Code field is actually a Charge Enterprise Preference we discussed a little later in the presentation. There are three Compliance Codes preferences and all are utilized in conjunction with the display on the encounter form to help capture information pertinent to resident and attending providers.
The ADBR describes the compliance code as the following: Select the appropriate compliance code level for the encounter from the drop-down list. The compliance code indicates whether a resident was involved in providing care during the visit/procedure. The codes are primarily used by academic facilities with resident providers. The Compliance Code Field Turned On preference determines whether Compliance Code is enabled. The Compliance Code Required preference determines whether Compliance Code is required. The default code level that displays is set using the Compliance Code Default Entry preference. Based on the code level selected, the GE or GC modifier is applied automatically to the charge. The code levels and modifiers for the levels are set up in Compliance Code Setup through TW Admin > Charge Admin > Comp Code Setup. CPT-4 code modifier can also be set up for a specific level in Compliance Code Details.
Q: How do you make fields in aehr to inactivate codes? When a code is inactive, can we still use it for old claims? We are having issues where if a date is put ppms (future date) it is automatically inactivating the code in aehr.
A: This is a bit of a tricky situation. Codes are inactivated in the EHR in the various dictionaries. Problem dictionaries should be updated via medcin updates. Other dictionary updates could be done manually, via SSMT or with interface messaging from the PMS to keep codes in synch between the two environments. My recommendation for that cut off period would be to really push providers to get all encounter forms submitted prior to the deactivation of codes that may no longer be utilized. Coordination with the billing/coding office is going to be key to a successful transition. If your organization uses any sort of Transaction Editing Software, this would be a perfect situational use of said software. Again, this is definitely a tricky situation, so knowing your workflows, software options and organizational specifics would be needed to provide more specific instructions.
Q: Why cannot we not send tasks to coders via provider? Not all tasks have enough fields to provide that option.
A: This is another fairly complicated situation. You could definitely set up task views for Review Encounter Form tasks that were provider specific by incorporating the Created By filter. However, views to capture Mng Chg Edit tasks may need to be reworked and use the Assigned To filter instead. Task view creation and management is a matter of creativity and thorough testing.
Q: Why is there only a limit of 10 dx to cross on a claim to billing system?
A: This is going to depend completely upon your organizational set up and payor preferences. It may be that your interface messaging can only handle 10 diagnosis per claim. It could also be possible that this is a preference specific to your billing office as many payors will only accept a set level of diagnosis codes per claim. This may be the workflow they have established to control claim rejections and reworks. I would recommend in-depth discussions, it could be a series of meetings, with your billing/coding offices to become more familiar with their workflows and the underlying reasons for these processes.
If you will be upgrading to Version 15.1 the maximum diagnosis has increased allowing the application to send up to 24 diagnosis. Versions prior to 15.1 have a maximum diagnosis limit of 12.