Common errors on released visits to Tellus and how to fix them.

In this article we will be explaining the possible reasons for the two most common errors found on visits released to Tellus and how to fix them.

Error #1:

"Invalid Recipient-Does-Not-Exist-In-System"

When this error is received, it means that some of the key information in the patient's profile coming from InMyTeam does not match the information of the patients registered in Tellus. In this case, we need to go to the patient's profile information in InMyTeam and compare the data with the one in Tellus.

Bellow we will explain the possible case scenarios and how to fix them:

•  The Medicaid ID in Tellus does not match the Medicaid ID in InMyTeam patient's profile.

1. Go to the patient's profile in Tellus portal 
2. Go to "Internal Recipient Reference"
3. Go to "Jurisdiction #"
4. You will find a long combined number divided by (-) 
5. Take the 1st number  and paste in the patient's Medicaid ID in InMyTeam
6. Take the 2nd number and paste in the patient's Member ID in InMyTeam
7. Hit the save button

• The Patient's date of birth in InMyTeam does not match the one listed in Tellus.

1. Change the patient's date of birth in InMyTeam to the one shown in Tellus
2. Hit the save button

• The Insurance associated to this patient in InMyTeam does not match the one shown in Tellus

1. Go to the Patient's profile in InMyTeam
2. Go to Authorizations in the Patient Profile
3. Edit the existing authorization and change the Insurance, or create a new authorization with the new insurance whether case applies.
4. Hit the save button

Error #2:

"Invalid Diagnose Code"

Typically the diagnosis codes for Long Term Care are R54, R69, R68.69 (depending on the payer), these codes means "undetermined, undefined etc". This error means that you have in your contracts in InMyTeam a different code that the one accepted by the aggregator. (You can see it when you right click on the visits and click Billing Information, or when you click on the billed amount or on when you edit the visits, billing information.)

You can edit each of the visits and correct the diagnosis code, or you can edit the authorizations involved for this patient and put "R69" on the diagnosis code 1 and that change will propagate to the visits.

To avoid this error, is recommended to set a default diagnose code in the Contracts section in settings, tis way, the code will come to the authorization automatically from  the contract. Avoid setting  diagnosis codes for LTC authorizations preferably. and try to use the default one which is suggested.

Once you have determined the errors and fixed them, all you need to do is to re-send those visits. To resend those visits you have two options:

• Re-send each visit one by one:

1. Go to "Actions"
2. Select " Re-send"

• Re-send all visit sin bulk:

1. Select all the visits
2. Go to "Bulk Actions"
3. Select "Re-send Matched Records in Errors"