HCIM

Answer: No, SymKey is not broken. There is likely an issue within EZ-CAP’s claim structure, where the UB04 claims that you are trying to open are labeled as UB92 claims in EZ-CAP’s tables. Before SymKey opens a claim, it queries EZ-CAP’s tables on the backend to determine which module it should use to open the claims. Since EZ-CAP is telling SymKey that the claims are UB92 claims, SymKey will not open them in EZ-CAP’s UB04 module. While you are able to manually open UB92 claims in the EZ-CAP UB04 module, SymKey will not do so because once the claims are saved in the UB04 module, they can no longer be opened in the UB92 module. For this reason, SymKey will only attempt to open UB92 claims in the UB92 module. When the UB92 module is disabled for the SymKey user, SymKey will fail against user rights in EZ-CAP.

If you would like to process claims labeled as UB92 in the UB04 module, you can manually open each claim in the UB04 module and save them as UB04 claims. Alternately, you can modify the SymKey user security in EZ-CAP to enable the UB92 module so SymKey can process the claims as they are.

Answer: SymKey^® can be interrupted in the middle of a batch for a number of reasons, either by the user pausing the batch or by network issues creating a communication error between it and EZ-CAP^®. It can be restarted very easily. When an interruption occurs, providing that you are still logged into SymKey, a message will be displayed asking if you would like to continue the batch. If you click “Yes,” SymKey will start the batch up again. Clicking “No” will close out the batch and SymKey will consider it completed.

It should be noted that when the batch is continued, SymKey will skip the claim that was interrupted. This is designed to avoid another possible interruption, since the issue may have been caused by a problem with that particular claim. SymKey will continue, starting with the next claim down in the batch file. The skipped claim will be listed in the “Unprocessed Claims” tab in the batch reports, along with the reason why it was skipped.

Answer: If you receive an error when SymKey is attempting to import a batch file, there is most likely an error in the format of the file. When SymKey imports batch files, it invokes error-checking logic that validates whether or not the batch file has the required or correct information for the selected batch. For example, if your scenario is set for specified lines and you are missing line numbers in your batch file, SymKey will display an error stating such.

If you are using the Batch Processing module, SymKey will validate each header row to ensure that they match fields in EZ-CAP, as well as check to see if the values listed below that row match possible or required values in SymKey.

Example
If your input file contains a typo (i.e. “statsu” instead of “status”):
claimno,sequence,statsu
2010021099900001,1,3

SymKey will note that there is no header definition for “statsu” and display a message to that effect.

Answer: SymKey^® modules are activated/deactivated based on a licensing agreement between HCIM and your company. If you require access to a module that is not available, your licensing file must be updated and a new licensing agreement signed. If you see that a module that used to be active is now unavailable, the terms of that agreement may have changed. Please consult your manager or e-mail us at support@hcim.com for more information.