Skip to main content

Avatar MSO 2022 Update 3

Product Requirements / Recommendations

Avatar MSO required
RADplus required

Recommended Update Level

Avatar MSO 2021 Update 18

Product Update Form Description

The "<PROPERTY DOES NOT EXIST>ProcessFields+23^MSOWebServiceClaimEntryAPI" issue which could occur when the 'WEBSVC.ClaimPreAdjuication' web service is used to pre-adjudicate claims is resolved.

Included Updates

None

Required Updates

None

Details

NEW0 CHANGED0 FIXED1
Fixed (1)
'Claim PreAdjudication' Web Service
An issue is resolved to ensure the 'WEBSVC.ClaimPreAdjudication' web service correctly updates the adjudication status of submitted claims.
Topics
• Claims Processing
 
Acceptance Tests

AV-78031 Summary | Details
'Claim PreAdjudication' Web Service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Claim Pre-Adjudication Web Service
Scenario 1: 'Claim Pre-Adjudication' Web Service - Receipt and processing of claim/service data from ProviderConnect
Specific Setup:
  1. Client record eligible for Claim/Service entry in Avatar MSO and Netsmart ProviderConnect
  2. Netsmart ProviderConnect (or other application utilizing the Avatar MSO 'Claim Pre-Adjudication' web service)
  3. 'Crystal Reports' or other SQL reporting tool
Steps
  1. Enter one or more services via Netsmart ProviderConnect 'Treatment' service entry.
  2. Navigate to ProviderConnect 'Billing' menu.
  3. Click 'Generate Bill' button for selected criteria.
  4. Click 'Click 'Submit Bill for Pre-adjudication' button for ProviderConnect billing transaction (or via other application utilizing the Avatar MSO 'Claim Pre-Adjudication' web service).
  5. Within 'Unsubmitted Bills' section of ProviderConnect 'Billing' menu, navigate to bill created above which was submitted for Pre-Adjudication.
  6. Click 'View Pre-adjudication Results' button for unsubmitted bill.
  7. For all services in bill submitted for Pre-Adjudication but not yet processed by Avatar MSO, ensure 'Status' value is 'Queued'.
  8. The Avatar MSO Pre-Adjudication processing will be performed by a system background process automatically, starting every 30 minutes and processing any new/previously unprocessed services; accordingly, wait for sufficient time frame for Pre-Adjudication to be performed by Avatar MSO.
  9. Click the 'Refresh Bill Pre-adjudication Results' button.
  10. Following Avatar MSO Pre-Adjudication processing of services, ensure that 'Status' value in ProviderConnect is updated from 'Queued' to either 'Passed Edit' or 'Failed Edit'. ('Passed Edit' or 'Failed Edit' Pre-Adjudication status for each service will be determined by Avatar MSO using the same configurations/criteria/logic as standard Claim Processing service adjudication for 'Approved' and 'Denied'/'Pending' claim status (respectively).)
  11. Following Avatar MSO Pre-Adjudication processing of services, ensure that services with 'Status' value of 'Failed Edit' also include data for 'Pre-Adjudication Edit Failed Reason' in ProviderConnect display. ('Pre-Adjudication Edit Failed Reason values for 'Failed Edit' services will be determined by Avatar MSO using the same configurations/criteria/logic as standard Claim Processing service adjudication for the 'Explanation of Coverage' detailed message.)
  12. Open 'Crystal Reports' or other SQL reporting tool.
  13. In Avatar MSO SQL table 'SYSTEM.claims_pre_adj table' - ensure new single row is present for each service submitted/processed by Claim Pre-Adjudication web service/background process.
  14. In Avatar MSO SQL table 'SYSTEM.claims_pre_adj table' - for each service submitted/processed, confirm 'Queued', 'Passed Edit' or 'Failed Edit' status in field 'status' (value 'Q', '1' or '0', respectively).
  15. In Avatar MSO SQL table 'SYSTEM.claims_pre_adj table' - for each service submitted/processed with 'Failed Edit' status, confirm 'Pre-Adjudication Edit Failed Reason' values in field 'pre_adj_edit_failed_reason'.
Topics
• Claims Processing

 

  • Was this article helpful?