Author Archive

How to identify and deny duplicate claims within EZ-CAP

Thursday, May 19th, 2011

While SymKey’s Batch Processing module allows you to create virtually limitless custom scenarios to modify or process claims, there are also several pre-programmed scenarios built into the SymKey Professional and Hospital Claims modules.

Denying Hard Duplicates with SymKey for EZ-CAP

One of the most widely used SymKey for EZ-CAP scenarios automatically denies a list of hard (exact) duplicate claims in EZ-CAP by adding a user-defined adjustment code and adjustment amount, zeroing out the net pay on the line/claim, and forcing the claim to status 1 for release to payment. This scenario can also be used to zero out the contract value of each line.

How do I know which claims are duplicates?

SymKey’s built-in Hard Duplicates module (a.k.a. Duplicates Finder) generates a list of duplicate claims to deny based on your specific business rules’ definition of what constitutes a duplicate claim.

Identifying Duplicate Claims in the Hard Duplicates Module
After selecting whether to look at Professional or Hospital claims, select which demographic fields must match a previously received claim in order to categorize the new claim as a duplicate (matching Member ID, Provider ID, Vendor ID, Primary Diagnosis, and Place of Service are good indicators of a duplicate claim).

Identifying Duplicates at the Detail Claim Line Level
Similarly, you can search at the detail claim line level to match exactly between the new and previously received claim on “Date of Service From and To,” “Service Code,” “Billed Charges,” “Capitation Flag,” and each of the four line modifiers.

Additional Filter Criteria
There are additional filters to only look at claims that EZ-CAP has identified as duplicates with the P7 “DUP” pend flag, to only look for duplicates that are EDI claims, were received between certain dates, and/or match specified EZ-CAP statuses. Custom filters can be quickly configured within the module to target a duplicate claim list to specific members, providers, vendors, CPT codes and several other fields. You can also add your own custom SQL code to the custom filters as matching criteria.

What if the previous claim was denied or has not been paid yet?

The Hard Duplicates module gives you the option to identify claims as hard duplicates only if the previously received claim resulted in a payment (Net Pay > 0). This prevents duplicate claims from being denied if the original claim was also denied (so you can review the new claim and decide whether the initial denial was legitimate) or if the original claim has not been paid yet (so the initial claim and the new claim are not both identified as duplicates and subsequently denied).

How do I create lists of claims to process with other SymKey scenarios?

If you would like to auto-generate lists of claims to process with other SymKey scenarios, you can use an external application such as Crystal Reports, SQL, Microsoft Access or any other reporting tool that can perform a structured query on the EZ-CAP database(s) and produce either a list of claims for the standard SymKey scenarios or a list of claim numbers and other required fields as desired for Batch Processing. HCIM’s product support staff is available to help you design these reports based on your organization’s unique business rules.

HCIM to integrate FileBound’s document management solution into ScanClaims products

Wednesday, March 23rd, 2011

HCIM recently entered into a reseller agreement with FileBound® and will integrate their flagship browser based document management system into HCIM’s ScanClaims™ product line. FileBound will replace AnyDoc Software’s BROKERit™ product, which has been used since ScanClaims’ initial design. FileBound has become a strong leader in the image archive and retrieval industry, and the functionality available in FileBound’s optional workflow module will allow HCIM to take their Prior Authorization Workflow product line to the next level.

I recently attended a three day class at FileBound’s headquarters and passed their exam to become a FileBound Certified Professional. In this class I learned many of the extensive features of this application as well as many of the possible ways to configure FileBound to meet our clients’ unique operational workflows.

FileBound offers three different implementation models to suit clients in a variety of situations. FileBound Express is a complete document management solution in a self contained network appliance that is almost plug and play on a network. FileBound On-Demand is a full featured system in an outsourced hosted solution. FileBound On-Site is a more traditional document management solution deployed at the client site on your in-house IT infrastructure.

One of our biggest concerns in dealing with Protected Health Information (PHI) is maintaining privacy and security. FileBound takes advantage of state of the art security whether an internet or intranet option is deployed. It also maintains compliance reporting and governance which can be customized to allow read/add/delete/modify access at the user, project, document, or field level.

We will continue to use the OCR for AnyDoc® and AnyDoc®EXCHANGEit™ data mapping applications, which are leading products in their respective markets. The ScanClaims product line uses both full Optical Character Recognition (OCR) and Key From Image (KFI) where appropriate to maximize the productivity of the specific client need. Over the 10+ years that ScanClaims has been used to process CMS-1500 and UB04 claims our clients have processed in excess of 5 million claims.

Implementing Successful Health Care Payer Core Claims System Conversions

Monday, January 3rd, 2011

Over the span of my career, I have led or been involved in numerous system installations and conversions. It seems like each project involves an out of date or unsupported primary/legacy system that needs to be replaced, which means that a new and exciting system is waiting out there to improve the client’s productivity.

As Director of Product Integration at HCIM, it is one of my primary job functions to implement new product installations and conversions, but I also get to lead and consult on projects for existing and new clients on core system conversions. About five years ago I was a primary influence in the conversion of providers, contracts, claims, auths, and members for a large client that was converting from Amisys C/S to Facets. I was involved in the data conversion mapping for all major modules and directly mapped much of the data myself. This included both the field level mapping from and to the legacy and new systems as well as conditional field and lookup table designs. I was a key member of the team, deciding what fields could be carried directly from system to system and what needed to be mapped to new values, in addition to what couldn’t be converted due to system limitations, changed workflow, or configuration design and needed to be fully recreated from scratch.

I recently led two historical data conversion projects for clients converting to ikaSystems’ ikaClaims and other ikaEnterprise modules. My team and I worked together to design a proprietary platform that imports legacy data, maps or converts it to the new database import schema, and validates each data field against individual field types, relational lookup values, industry standards, and system requirements. This process produced a clean file in the ikaSystems’ standard format. ikaSystems’ platform is flexible enough to allow for customization to accommodate each individual client’s business rules and policies so the converted data is both technically accurate and operationally functional for historical reference.

For the ikaSystems conversion we were called upon to convert historical system data for the member, provider, authorization, claims, payment, benefit plans, and accumulators. The task demanded a thorough understanding of business processes, system functionality, and technical rules to successfully accomplish an undertaking of this magnitude. It also required a good team and LOTS of communication in all directions.

If your organization is due for a new claims system and is looking for help selecting a new core claims transaction system or needs assistance with the historical data conversion or data clean up (i.e. duplicate provider or vendor records), contact me at 888-454-0202, option 5. I look forward to hearing from you.

FAQ: The 2010 CMS Fee Schedule was released and is effective retroactively. We have already paid claims for the last several months that now need to be repriced. Can SymKey automatically reprice them?

Friday, September 24th, 2010

Yes, SymKey’s “Reprocess/Pend” standard scenario is a perfect automated solution for repricing paid claims and is very simple to use for EZ-CAP status 9 claims.

  1. Create a .txt file with a list of the paid claim numbers that need to be repriced
  2. Open the SymKey Professional Claims module
  3. Check the “Reprocess/Pend” checkbox about ¾ the way down on the left side
    Note: most of the screen will be grayed out and Source Claim Status 9 will automatically be selected.
  4. In the “Global Options” section at the top of the Professional Claims module:
    – Check the “Reprice Claim Lines” checkbox
    – Check the “Adjustment Code” checkbox
    – Select an adjustment reason from the drop-down list
    – Check the “Adjust All Lines” checkbox
  5. Click the “Process Batch” button

SymKey will automatically perform the following:

  1. Create a set of new claims in EZ-CAP status 3
  2. Duplicate the demographic and line detail for each claim in the input file
  3. Reprice each line to the new fee schedule
  4. Subtract the original payment from the amount due, resulting in a net pay of the difference in fee schedule amounts

Example:
The original claim paid $45.50 for a particular claim line.
Under the new retroactive fee schedule, the payment should have been $48.90.
Using the “Reprocess/Pend” scenario, SymKey will create a new claim with:
Claim Line Contract Value: $48.90
Negative Adjustment: $45.50, with the Adjustment Reason Code specified by the user
Claim Line Net Pay: $3.40

If you’re interested in more of the automatic benefits administration solutions that HCIM has to offer, call 888-454-0202, option 5 or e-mail us at sales@hcim.com.

FAQ: I see the Batch Processing module is included in my license. Where do we start?

Thursday, August 26th, 2010

Answer: In SymKey for EZ-CAP v. 1.30 and higher, click the “Documentation” link in the “Help” section on the left side of the SymKey main menu. Select the “Batch Processing Technical Procedure Guide” from the “Documentation” sub menu. The guide provides a detailed overview of the available functionality as well as instructions on how to build and use a Batch Processing input file.

As always, HCIM is here to help however we can. If you have any questions, contact HCIM Product Support at support@hcim.com or 888-454-0202, option 2.

Wildcard Searches in AnyDoc BROKERit

Wednesday, August 25th, 2010

The BROKERit product from AnyDoc Software is normally included with the base ScanClaims software suite when purchased with scanning and OCR for AnyDoc.  This is a very powerful tool to search for archived documents that are properly indexed using either verified Optical Character Recognition (OCR), customized Key From Image (KFI) screens, or when linked to external databases.

Queries can be performed on either single or multiple folders using the “Query Module” interface. Simply right-click on the desired level folder on the left side of the screen, then select either “Quick Folder Query,” “New Folder Query,” or “New Multiple Folder Query,” depending on whether you would like to search across multiple folders or in a single folder. The “Quick Folder Query” is generally the most utilized option because users can set up archive folders with different forms having different indexes.

A list of all the indexed fields for that folder will be displayed on the right side of the screen. The “Operator” column features a drop-down list that allows the user to specify which operator to use (=, >, <, >=, <=, <>, Like, List, Between, Null, and Not Null). The default operator is “=.”

When the user selects “Like” as the operator, the “Field Value” column can be used in conjunction with the wildcard character “%.” For instance, when searching the “Document Number” field for all images scanned on 8/10/2010, the user can enter S20100810 with the “%” wildcard character (S20100810%) in the appropriate “Field Value” field.

The “%” wildcard character can be used to match any number of characters up to the size of the field. The underscore character (_) can also be used in combination with the partial contents of an index field to search for values by length with each “_” representing a single character. In this case, the “Field Value” column of S____ (four underscore characters) would return names like “Smith,” but not “Sampson.”

The mathematical operators >, <, <=, and >= can also be used to return the desired results. In the above document number example, the operator “>=” could be used with S20100810 (no wildcard character) to return all document numbers scanned on or after that date.

For more information on AnyDoc® BROKERit, click here.

FAQ: We only have a handful of claims to run in a special batch. How can we create a source file?

Thursday, August 12th, 2010

Answer: To easily create a standard scenario processing batch file, all you need is a column of claim numbers in a text file:

  1. In either Windows Notepad or an Excel spreadsheet, simply enter the column of claim numbers and save the file:
    File Type: *.txt
    Destination: SymKey\Files\Source directory
  2. Browse for the file as usual within the SymKey Professional or Hospital Claims module.

FAQ: How can we expand our use of SymKey to handle more claims?

Wednesday, July 28th, 2010

Answer: This is a four-step process:

  1. Identify the type of claims that you would like to target (i.e. denying claims that exceed a timely filing threshold).
  2. Define what claims fall into this scenario (i.e. timely filing claims may be in-network providers as defined by the “ZZZ” in the Provider Contract field, where the date received is more than 180 days after the DOS).
  3. Create a report of claims for input into a SymKey scenario or Batch Processing.
  4. Test the report and scenario configuration in SymKey.

 

At any step along the way, HCIM’s expert Product Support team is available to field questions, offer advice, or work with you to complete the entire process. Contact HCIM Product Support at support@hcim.com or 888-454-0202, option 2.

FAQ: Can SymKey perform multiple scenarios during the same batch?

Thursday, July 15th, 2010

Answer: Yes, SymKey can perform certain scenarios in combination with others, combining multiple single-action batches into one complex batch. When a scenario is selected in the Professional or Hospital Claims module, other scenarios may become disabled, indicating that the disabled scenario actions cannot be combined with the selected scenario action. The scenarios that are still selectable can be performed along with the scenario action that was initially selected. Simply select the actions to be performed and SymKey will process them in the correct order once the “Process Batch” button is clicked. In SymKey v. 1.31 and above, you can verify the scenario action processing order prior to running the batch by clicking the “Scenario Summary” button – a summary of the actions that SymKey is configured to perform and the order that SymKey will perform them in will be displayed.

In addition to SymKey’s standard scenarios in the Professional and Hospital Claims modules, the Batch Processing module allows users to configure their own batches with more control and flexibility.

If you have questions about setting up multiple scenarios or utilizing batch processing for your business needs, please contact HCIM Product Support at support@hcim.com or 888-454-0202, option 2.

FAQ: Can SymKey move claims within EZ-CAP to a status beyond 3?

Thursday, July 8th, 2010

Answer: SymKey for EZ-CAP is designed to work within EZ-CAP’s Professional and Hospital claims modules. As a result, it is able to automate the moving of claims that are in status 1-7 to a status 1 or 3. It can also reprocess status 9 claims by creating a new claim number, entering all related detail line information, and placing them in a status 3. Moving a claim to a status 5 or beyond, however, requires the use of EZ-CAP’s Payment Processing module. Although SymKey is not designed for the EZ-CAP Payment Processing module, HCIM developed the SymKey for EZ-CAP Move 1 to 5 Kwik Utility, which automates the moving of a list of claim numbers from a status 1 to a status 5.

If you do not already have the SymKey Move 1 to 5 Kwik Utility and would like more information, please contact HCIM Product Support at support@hcim.com or 888-454-0202, option 2.