Skip to main content

Avatar CWS 2023 Update 7

Product Requirements / Recommendations

Avatar CWS required
RADplus required

Recommended Update Level

Avatar PM 2023 Update 16
Avatar PM 2022 Update 139

Product Update Form Description

The hard error '[SUBSCRIPT]AuthResult+36^HRADAuthCheck^PAYAUTH' that may occur in the 'Progress Notes (Group and Individual)' form is resolved.

Included Updates

None

Required Updates

None

Details

NEW0 CHANGED0 FIXED1
Fixed (1)
Progress Notes (Group and Individual)
A modification has been made to Progress Notes (Group and Individual) to ensure that the following error is not received upon submission of notes: '[SUBSCRIPT]AuthResult+36^HRADAuthCheck^PAYAUTH'.
Topics
• Progress Notes
 
Acceptance Tests

AV-86177 Summary | Details
Progress Notes (Group and Individual)
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission
  • Ambulatory Progress Notes
  • Client Charge Input
  • Client Ledger
  • Create Interim Billing Batch File
  • Diagnosis
  • Dictionary Update (PM)
  • Electronic Billing
  • Financial Eligibility
  • Guarantors/Payors
  • Payor Based Authorizations
  • Program Maintenance
  • Progress Notes (Group and Individual)
  • Registry Settings (PM)
  • Review To Do Item
  • User Definition
Scenario 1: PM - Payor Based Authorization - Location - Progress Notes
Specific Setup:
  • Registry Settings:
  • Enable Payor Based Authorizations = 'Y'.
  • Enable CPT Based Payor Authorizations = desired value.
  • Require Authorizations At Guarantors/Payors Level = desired value.
  • Dictionary Update:
  • Client File (10006) Location = note active locations.
  • Staff File (79) Practitioner Category = note active categories.
  • Guarantors/Payors:
  • Guarantor A: Identify a guarantor to be used with 'Payor Based Authorizations'.
  • Note the values in the 'Authorization Section'.
  • Verification Level For Authorizations For Client Charge Input and Verification Level For Authorizations For Appointment Scheduling:
  • 'Disallow Service If Authorization Is Missing' will not allow the service to be submitted.
  • 'Warn User If Authorization Is Missing' will allow the service to be submitted.
  • Verification Level For Authorizations For 837 Electronic Billing:
  • 'None' will allow services that were submitted and closed to be billed.
  • 'Report As Error And Include On Bill' will allow services that were submitted and closed to be billed. An error message will be included in the 837 Billing report.
  • 'Report As Error And Do Not Include On Bill' will not allow services that were submitted and closed to be billed
  • Client A: Identify an active client that is assigned to the guarantor above.
  • Payor Based Authorizations: Create or edit a definition to not include a 'Locations' and any other desired fields. An error message will be included in the 837 Billing report. Note the value of each field.
Steps
  1. Open 'Payor Based Authorizations'.
  2. Create a new record for the client that matches the record from setup.
  3. Validate that the following message displays: An authorization already exists for this date range. Overlapping authorizations are not allowed.
  4. Remove the 'Expiration Date'.
  5. Select a 'Location'.
  6. Enter an 'Expiration Date'.
  7. Submit the form and validate that it files successfully.
  8. Open 'Progress Notes (Group and Individual)'.
  9. Create a note for a new service for the client without the selected location, that will pass the setup payor authorization definition.
  10. Validate that the note files successfully.
  11. Create a note for a new service for the client with the selected location, that will pass the payor authorization definition added above.
  12. Validate that the note files successfully.
  13. If desired, test other progress note types for successful filing.
  14. If desired, disable the 'Enable Payor Based Authorizations' registry setting test progress notes for successful filing.
Topics
• Progress Notes

 

  • Was this article helpful?