Skip to main content

Avatar PM 2022 Monthly Release 2022.03.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 19 Summary | Details
Enhanced internal utilities
Scenario 1: File Import - [Support Only] Appointment Scheduling/Mark Appointments Posted
Steps
  1. Internal Testing Only
Topics
• Appointment Management
Update 75 Summary | Details
File Import - Client Charge Input group services
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Ledger
Scenario 1: File Import Client Charge Input - Remove group # requirement on group services
Specific Setup:
  • Create a Client Input Charge import file that has a group service code with the group number omitted from field 7.
  • Create a Client Input Charge import file that has a group service code with the group number populated in field 7.
Steps
  1. Open the "File Import" form.
  2. Import a "Client Charge Input" type of file.
  3. Use the file that has a row for a group service and the group number is omitted form field 7 of the row.
  4. Select "Upload New File" and process that action.
  5. Browse to the location the file resides on the server and select the desired file to upload.
  6. Select the "Compile/Validation" action and process that action.
  7. Validate that a message indicating the file "Compiled" is received.
  8. Select the "Print File" action and validate the contents of the data in the file.
  9. Select the "Post" action to create new services based on data in the import file.
  10. Open the "Client Ledger" and validate the service created.
  11. Open the "File Import" form.
  12. Import a "Client Charge Input" type of file.
  13. Use the file that has a row for a group service and the group number is populated in field 7 of the row.
  14. Select "Upload New File" and process that action.
  15. Browse to the location the file resides on the server and select the desired file to upload.
  16. Select the "Compile/Validation" action and process that action.
  17. Validate that a message indicating the file "Compiled" is received.
  18. Select the "Print File" action and validate the contents of the data in the file.
  19. Select the "Post" action to create new services based on data in the import file.
  20. Open the "Client Ledger" and validate the service created.
Client Charge Input - Prolonged services
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Update (PM)
  • Admission
  • Client Charge Input
  • Client Ledger
Scenario 1: Client Charge Input - Service Duration < Duration Range in the Fee record.
Specific Setup:
  • Registry setting "Enable Multiple Add-On Code Per Primary" must be enabled.
  • Using "Dictionary Update", add an extended data dictionary element (295) Allow Multiple Add-On Code Definition" set to "Yes" to the Dictionary Code "5" in the "Other Tabled Files" file.
  • Using "Service Codes", add an add-on code. Set it up as "User Defined" code. Assign "Other" to the "Service Code Type".
  • Using "Service Codes", add a primary service code, set up as "User Defined". Assign "Other" to the "Service Type Code".
  • Using "Service Fee/Cross Reference", set up fees for the new service codes created for this test.
  • Admit a new client or select an existing one with one outpatient episode.
Steps
  1. Open the "Client Charge Input" form.
  2. Add a primary service for the test client.
  3. Set "Duration (Minutes)" to a value of "54" or less.
  4. Validate the primary code is populated with an add-on code in the "Selected Add-On Services" text field.
  5. Submit the service.
  6. Open the "Client Ledger" form.
  7. Validate one service was created.
Scenario 2: Client Charge Input - Service Duration > Duration Range in the Fee record.
Specific Setup:
  • Registry setting "Enable Multiple Add-On Code Per Primary" must be enabled.
  • Using "Dictionary Update", add an extended data dictionary element (295) Allow Multiple Add-On Code Definition" set to "Yes" to the Dictionary Code "5" in the "Other Tabled Files" file,
  • Using "Service Codes", add an add-on code. Set it up as "User Defined" code. Assign "Other" to the "Service Code Type".
  • Using "Service Codes", add a primary service code, set up as "User Defined". Assign "Other" to the "Service Type Code".
  • Using "Service Fee/Cross Reference", set up fees for the new service codes created for this test.
  • Admit a new client or select an existing one with one outpatient episode.
Steps
  1. Open the "Client Charge Input" form.
  2. Add a primary service for the test client.
  3. Set "Duration (Minutes)" to a value greater than or equal to "55".
  4. Validate the primary code has an add-on code in the "Selected Add-On Services" text field.
  5. Submit the service.
  6. Open the "Client Ledger" form.
  7. Validate two services were created. One for 54 units and the other for the number of units over 54.
Disclosure Management - Discharge data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Disclosure Management
  • Disclosure Management Configuration
  • Admission
  • Diagnosis
  • Discharge
  • Client Ledger
Scenario 1: Disclosure Management - Field Validations
Specific Setup:
  • Using the "Disclosure Management Configuration" form, set up the first page image, watermark, and forms to associate to set up Disclosure Management.
Steps
  1. Open the "Disclosure Management" form.
  2. Populate all required and desired fields in the request, authorization, and the disclosure sections.
  3. Select "Electronic" in the "Disclosure Method" field.
  4. Click the "Process" button.
  5. Validate the appropriate items are included in the disclosure packet.
  6. Click "Disclose".
  7. Click the PDF download icon.
  8. Browse to the location to store the file on the server.
  9. Provide the file name with a .pdf file extension.
  10. Click the "Cancel" button.
  11. Click "Submit".
Scenario 2: Disclosure Management - Discharged Client
Specific Setup:
  • Using the "Configuration Management Configuration" form, configure the disclosure management form.
  • Admit or select a test client.
Steps
  1. Using the "Diagnosis" form, give the client or validate the client has a diagnosis.
  2. Open the "Discharge" form and discharge the client.
  3. Ensure the "Discharge Remarks/Comments" is populated.
  4. Ensure the "Hospital Discharge Instructions" is populated.
  5. Submit the data.
  6. Open the "Disclosure Management" form.
  7. Populate the Request section, Authorization section and Disclosure sections.
  8. Populate the "Disclosure Date" and "Disclosure Time" fields.
  9. On the preview of the disclosure packet, view the Discharge form and validate the "Discharge Remarks/Comments" and "Hospital Discharge Instructions" is included in the output.
Disclosure Management - Request Information Specify Other
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Disclosure Management
  • Disclosure Management Configuration
  • Admission
Scenario 1: Disclosure Management - Field Validations
Specific Setup:
  • Using the "Disclosure Management Configuration" form, set up the first page image, watermark, and forms to associate to set up Disclosure Management.
Steps
  1. Open the "Disclosure Management" form.
  2. Populate all required and desired fields in the request, authorization, and the disclosure sections.
  3. Select "Electronic" in the "Disclosure Method" field.
  4. Click the "Process" button.
  5. Validate the appropriate items are included in the disclosure packet.
  6. Click "Disclose".
  7. Click the PDF download icon.
  8. Browse to the location to store the file on the server.
  9. Provide the file name with a .pdf file extension.
  10. Click the "Cancel" button.
  11. Click "Submit".
Scenario 2: Disclosure Management - Request Information - Specify Other
Specific Setup:
  • Using the "Disclosure Management Configuration" form, configure the "Disclosure Management" form.
  • Admit or select a test client.
Steps
  1. Open the "Disclosure Management" form.
  2. Populate the fields on the "Request" section of the form.
  3. Ensure to populate the "Request Information - Specify Other" has multiple lines of data in the text box.
  4. Click "Submit" to save the data.
  5. Return to the Pre-Display.
  6. Add an additional disclosure row for the same client.
  7. Populate the fields on the "Request" section of the form.
  8. Ensure to populate the "Request Information - Specify Other" has 1 line of data in the text box.
  9. Return to the Pre-Display.
  10. Edit the 2nd row added during this session.
  11. Validate the "Request Information - Specify Other" only has one row of data.
  12. Submit the form.
  13. Return to the Pre-Display.
  14. Edit the 1st row added during this session.
  15. Validate the "Request Information - Specify Other" only has multiple rows of data.
  16. Submit the form.
Topics
• Client Charge Input • File Import • Discharge • Disclosure
Update 118 Summary | Details
Avatar PM is modified to increase length of client name and allow spaces to be included.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Update Client Data
  • Chart View (Client Header)
  • Pre Admit Discharge
  • Cross Episode Financial Eligibility
  • Discharge
  • Financial Eligibility
Scenario 1: Admission - validate Registry setting 'Allow spaces in Client Name'.
Specific Setup:
  • Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form.
  • Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms.
Steps
  1. Open 'Admission (Outpatient)' form.
  2. Set the 'Last Name' on the 'Select Client' popup window to any name value.
  3. Set the 'First Name' on the 'Select Client' popup window to any name value.
  4. Select the gender in the 'Sex' drop down list.
  5. Click [Search].
  6. Click [OK] on the 'Search Results' popup window: 'No matches found'.
  7. Click [New Client].
  8. Click [Yes] on the 'Auto Assign Next ID Number' popup window.
  9. Click on the 'Demographics' section.
  10. Set the 'Client Last Name' to any name including one or more spaces. i.e.: 'Last Name'.
  11. Set the 'Client First Name' to any name including one or more spaces. i.e.: 'First Name'
  12. Set the 'Client Middle Name' to any name including one or more spaces. i.e.: 'Middle Name'.
  13. Complete any required fields.
  14. Click the 'Admission' section.
  15. Verify the 'Client Name' field contains the full name, including spaces.
  16. Click [Submit].
  17. Right click on the client name in the 'Recent Clients' section.
  18. Click 'Display Chart'.
  19. Verify the client name displays all characters entered in the 'Admission' form. Note that the user may need to place the cursor over the client name and review the 'hover help' as it will display the client name.
Scenario 2: Update Client Data - Validate client name allows spaces and client middle name displays up to 25 characters.
Specific Setup:
  • Avatar RADplus 2022 Update 126 is required for full functionality.
  • Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form.
  • Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms.
Steps
  1. Open 'Update Client Data' form for an existing client.
  2. Set the 'Client Last Name' field to a last name which includes spaces in the name i.e.: 'FRANKLIN MILLER MOTT'
  3. Set the 'Client First Name' field to a first name which includes spaces in the name i.e: 'BENJAMIN WALLY'
  4. Set the 'Client Middle Name' field to a middle name which includes spaces and is maximum of 25 characters i.e: 'BILL ED MIDDLE NAME LONG'
  5. Click [Submit].
  6. Right click on the client name in the 'Recent Clients' list.
  7. Select 'Display Chart'.
  8. Verify the name displays in the client banner, including all spaces and a maximum of 25 characters for the middle name.
  9. Close the client chart.
Scenario 3: Pre Admit Discharge web service validation
Specific Setup:
  • Existing 'Pre Admit' client whose full name is longer than 40 characters.
  • Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form.
  • Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms.
  • RADplus 2022 Update 126 is required for full functionality.
  • Access to, and understanding of, SoapUI or other Web Service tools.
Steps
  1. Using 'SoapUI' or another web service tool, consume the WSDL for the 'Pre Admit Discharge' form.
  2. Set the 'SystemCode' code to the agency system code for testing.
  3. Set the 'UserName' to the logged in user name.
  4. Set the 'Password' to the logged in user password.
  5. Set the 'DateOfDischarge' to the discharge date.
  6. Set the 'DischargeTime' to the time of discharge.
  7. Set the 'Discharge Practitioner' to a practitioner code (not the practitioner name).
  8. Set the 'Client ID' to the ID for the client to be discharged.
  9. Set the 'EpisodeNumber' to the client episode to be discharged.
  10. Click [Send].
  11. Review the response and verify the response message displays: <Message>Client Pre-Admit Discharge web service has been filed successfully.</Message>
  12. Open 'Pre Admit Discharge' in Avatar.
  13. Select the client discharged in the Web Service.
  14. Verify the 'Date of Discharge' is set to the date entered in the Web Service.
  15. Verify the 'Time of Discharge' is set to the time entered in the Web Service.
  16. Verify the 'Discharge Practitioner' is set to the practitioner entered in the Web Service.
  17. Click [Close Form].
Scenario 4: Cross Episode Financial Eligibility - validate client name display with spaces and up to 100 characters in the name
Specific Setup:
  • A client (Client A) is admitted where the first name, middle name, and last name combined is up to 100 characters and spaces are included in the name. Note that a space will count as a character.
  • Avatar PM 2022 Update 118 is required for full functionality.
  • RADplus 2022 Update 126 is required for full functionality.
Steps
  1. Open 'Cross Episode Financial Eligibility' form for Client A.
  2. Click 'Guarantor Selection' section.
  3. Click [Add New Item].
  4. Select any value in the 'Guarantor #' field.
  5. Click [OK] on the 'Selecting This Guarantor Will Over-Write Any Previous Plan Information' pop up window.
  6. Complete remaining required fields as needed.
  7. Select 'Self' in the 'Client's Relationship to Subscriber' field.
  8. Verify the 'Subscriber's Last Name' field is populated with up to 40 characters.
  9. Verify the 'Subscriber's First Name' field is populated with up to 40 characters.
  10. Verify the 'Subscriber's Middle Name' field is populated with up to 25 characters.
  11. Click 'Cross Episode Financial Eligibility' section.
  12. Select a value from the 'Guarantor #1' drop down list.
  13. Click [Submit].
Scenario 5: Client Discharge web service
Specific Setup:
  • SoapUI or other web service tool.
  • Client admitted with a long first and last name of up to 40 characters, and middle name of up to 25 characters. Spaces can be included.
  • Avatar RADplus 2022 Update 126 is required for full functionality.
  • Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form.
  • Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms.
Steps
  1. Open SoapUI or another web service tool.
  2. Consume the WebSvc.ClientDischarge.cls wsdl.
  3. Set the 'SystemCode', 'UserName', and 'Password' to correct values.
  4. Set 'DateofDischarge' field to the client discharge date.
  5. Set 'DischargePractitioner' to the discharging practitioner ID.
  6. Set 'DischargeReferral Type' to the Type code for the discharge.
  7. Set 'DischargeTime' to the time of the discharge.
  8. Set 'ClientID' to the client id to be discharged. This client should have a long last name and first name of up to 40 characters.
  9. Set 'EpisodeNumber' to the client episode to be discharged.
  10. Click 'Send' request.
  11. Validate the response displays 'Client Discharge web service has been filed successfully'.
  12. Open the 'Discharge' form in Avatar PM.
  13. Select the client discharged in the web service.
  14. Verify the data entered in the web service is correct.
  15. Close the form.
Scenario 6: Validate Client Demographics web service updates the Update Client Data fields.
Specific Setup:
  • SoapUI or other web service tool.
  • Client admitted with a long first and last name of up to 40 characters, and middle name of up to 25 characters. Spaces can be included.
  • Avatar RADplus 2022 Update 126 is required for full functionality.
  • Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form.
  • Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms.
Steps
  1. Open SoapUI or another web service tool.
  2. Consume the WebSvc.ClientDemographics.cls wsdl.
  3. Set the 'SystemCode', 'UserName', and 'Password' to correct values.
  4. Set 'ClientFirstName' to the first name of the client with a long first name, up to 40 characters.
  5. Set 'ClientMiddleName' to the middle name of the client with a long middle name, up to 25 characters.
  6. Set 'ClientName' to the <client last name,client first name>.
  7. Set 'ClientID' to the client id for the test client.
  8. Set any other field to the appropriate data such as ClientEmailAddress.
  9. Click 'Send'.
  10. Review the Response.
  11. Verify the message displays: <Message>Client Demographics web service has been filed successfully.</Message>
  12. Open the 'Update Client Data' form for the same client.
  13. Verify the data filed in the web service displays as entered.
  14. Close the form.
Scenario 7: Financial Eligibility web service - validate client names with spaces and the name contains a maximum of 100 characters.
Specific Setup:

UP / PERMISSIONS

  • Access to, and a working understanding of, SoapUI or other web service tool.
  • Avatar RADplus 2022 Update 126 is required for full functionality.
  • Client admitted where the client last and first names are maximum of 40 characters, including space(s). The client middle name should be a maximum of 25 characters, including spaces(s).
  • Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form.
  • Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms.
Steps
  1. Open SoapUI or another web service tool.
  2. Consume the Websvc.FinancialEligibility.cls wsdl.
  3. Expand the WEBSVC.FinancialEligibility item.
  4. Expand FinancialEligibilitySoap item.
  5. Expand 'AddFinancialElig' item.
  6. Double click on 'Request 1'.
  7. Set the 'SystemCode', 'UserName', and 'Password' to correct values.
  8. Set 'ClientsRelationship' to any value such as '1'.
  9. Set 'CoverageEffectiveDate' to the date coverage started for the client.
  10. Set 'CustomizeGuarantorPlan' to '1'.
  11. Set 'GuarantorName' to the name of the guarantor being assigned.
  12. Set 'GuarantorNumber' to the ID number of the guarantor.
  13. Set 'GuarantorOrderNumber' to the number where the guarantor is to be listed. Use '1' if there is just one guarantor.
  14. Set 'GuarantorPlan' to any value such as '1'.
  15. Set 'EligibilityVerified' to 'Y'.
  16. Set 'MaximumCoveredDollars' to any dollar value.
  17. Set 'SubscribersName' to the full name of the client, up to 100 characters. Format is 'LastName,FirstName'.
  18. Set 'ClientID' to the ID number for the test client.
  19. Click 'Send'.
  20. Review the Response text.
  21. Complete any additional required fields.
  22. Click 'Send' again.
  23. Verify the Response states : <Message>Financial Eligibility web service has been filed successfully.</Message>
  24. Open 'Financial Eligibility' form in Avatar PM for the same client.
  25. Verify 'Guarantor #1' field is populated with the guarantor submitted in the web service.
  26. Click 'Guarantor Selection' tab.
  27. Verify the information sent thru the web service is populated correctly.
  28. Close the form.
Scenario 8: Cross Episode Financial Eligibility web service - validate client names with spaces and the name contains a maximum of 100 characters.
Specific Setup:
  • Access to, and a working understanding of, SoapUI or other web service tool.
  • Avatar RADplus 2022 Update 126 is required for full functionality.
  • Client admitted where the client last and first names are maximum of 40 characters, including space(s). The client middle name should be a maximum of 25 characters, including spaces(s).
  • Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form.
  • Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms.
Steps
  1. Open SoapUI or another web service tool.
  2. Consume the Websvc.CrossFinancialEligibility.cls wsdl.
  3. Expand the WEBSVC.CrossEpisodeFinancialEligibility item.
  4. Expand CrossEpisodeFinancialEligibilitySoap item.
  5. Expand 'AddCrossEpisodeFinancialElig' item.
  6. Double click on 'Request 1'.
  7. Set the 'SystemCode', 'UserName', and 'Password' to correct values.
  8. Set 'ClientsRelationship' to any value such as '1'.
  9. Set 'CoverageEffectiveDate' to the date coverage started for the client.
  10. Set 'CustomizeGuarantorPlan' to '1'.
  11. Set 'GuarantorName' to the name of the guarantor being assigned.
  12. Set 'GuarantorNumber' to the ID number of the guarantor.
  13. Set 'GuarantorOrderNumber' to the number where the guarantor is to be listed. Use '1' if there is just one guarantor.
  14. Set 'GuarantorPlan' to any value such as '1'.
  15. Set 'EligibilityVerified' to 'Y'.
  16. Set 'MaximumCoveredDollars' to any dollar value.
  17. Set 'SubscribersName' to the full name of the client, up to 100 characters. Format is 'LastName,FirstName'.
  18. Set 'ClientID' to the ID number for the test client.
  19. Click 'Send'.
  20. Review the Response text.
  21. Complete any additional required fields.
  22. Click 'Send' again.
  23. Verify the Response states : <Message>Cross Episode Financial Eligibility web service has been filed successfully.</Message>
  24. Open 'Cross Episode Financial Eligibility' form in Avatar PM for the same client.
  25. Verify 'Guarantor #1' field is populated with the guarantor submitted in the web service.
  26. Click 'Guarantor Selection' tab.
  27. Verify the information sent thru the web service is populated correctly.
  28. Close the form.
Topics
• Admission (Outpatient) • Cross Episode Financial Eligibility • Financial Eligibility • NX • Registry Settings • Update Client Data
Update 119 Summary | Details
Client Ledger - Re-billed claims
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Posting/Adjustment Codes Definition
  • Admission
  • Financial Eligibility
  • Diagnosis
  • Create Interim Billing Batch File
  • Electronic Billing
  • Client Ledger
  • Individual Cash Posting (PM)
  • Client Charge Input
  • Electronic Re-Billing Service Assignment
Scenario 1: Client Ledger - Validating 'Claim' crystal report for payment/adjustments /transfers posted to client account
Specific Setup:
  • Posting/Adjustment Codes Definition:
  • Identify an existing payment, adjustment and/or transfer codes. Note the codes/values for further testing.
  • Admission:
  • A new client is admitted in the inpatient program. Note the client's id/name, admission program, admission date.
  • Guarantor/Payors:
  • An existing guarantor is identified to assign to the client.
  • Financial Eligibility:
  • The existing guarantor is assigned to the client. Note the Guarantor code/value.
  • Service Codes:
  • An existing room and board service code is identified to render services to the client. Note the service code.
  • Client Charge Input:
  • 5-6 days of the room and board services are rendered to the client.
  • Close Charges:
  • The charges rendered to the client are closed.
Steps
  1. Open the 'Electronic Billing' form.
  2. Run an 837 Institutional bill for the client.
  3. Verify the bill compiles successfully.
  4. Claim the services.
  5. Verify the bill compiles successfully.
  6. Open the 'Client Ledger' form.
  7. Process the report using 'Claim' ledger type and validate that the claim based report displays all the claim specific information.
  8. Open the ‘Individual Cash Posting’ form.
  9. Select the ‘Client’.
  10. Select desired value in the ‘Post By’ field.
  11. Click [Select Item(s) To Post Against].
  12. A grid opens containing a row for all services.
  13. Select a desired row.
  14. Click [OK] when all desired rows have been selected.
  15. Note the ‘Information’ message and the current balance for the guarantor.
  16. Click [OK].
  17. Enter desired value in ‘Posting Date’.
  18. Enter desired value in ‘Date of Receipt’.
  19. Validate that the ‘Guarantor’ defaulted to the guarantor in the current balance message.
  20. Enter desired value in ‘Dollar Amount To Be Posted’. Amount entered can be the full amount due or a partial amount due.
  21. Enter desired value in ‘Posting Code’.
  22. If desired, enter a value in ‘Check #’.
  23. Enter desired value in ‘Action For Remaining Balance If Applicable’.
  24. Click [Update Temporary File].
  25. If desired, continue to add payment/adjustments/transfers using the steps above for all other services.
  26. Click [Submit] when all payment/adjustments/transfers have been completed.
  27. Open ‘Client Ledger’ for the client’.
  28. Process the report using ‘Simple' ledger type and validate that the payment/adjustments/transfers posted correctly.
  29. Process the report using ‘Claim' ledger type and validate that the payment/adjustments/transfers posted correctly specific to claim.
  30. Close the form.
Scenario 2: Client Ledger - Validating Simple/ Crystal/ Claim types of the ledger for Re-bill claims
Specific Setup:
  • Admission:
  • A new client is admitted, or an existing client is identified. Note the client's id/name, admission program, admission date.
  • Guarantor/Payors:
  • An existing guarantor is identified to assign to the client.
  • Financial Eligibility:
  • The existing guarantor is assigned to the client. Note the Guarantor code/value.
  • Service Codes:
  • An existing service code is identified to render services to the client. Note the service code.
  • Client Charge Input:
  • A service is rendered to the client.
  • Client Ledger:
  • The service distributed to the guarantor assigned to the client in the financial eligibility.
  • Close Charges:
  • The service rendered to the client is closed.
  • Create Interim Billing Batch File:
  • An interim file is created which covers client, guarantor and service distributed to the guarantor. Note the batch file number/name.
  • Electronic Billing:
  • An 837 bill is created and claimed for the service. Note the claim number.
  • Electronic Re-Billing Assignment:
  • The claim created above is re-billed.
  • Electronic Billing:
  • An 837 bill is created and claimed for the re-bill service created in above step.
Steps
  1. Open the 'Client Ledger' form.
  2. Enter desired client in the 'Client ID' field.
  3. Select 'Claim' from the 'Claim/Episode/All Episodes' field.
  4. Select desired claim # created in the setup section.
  5. Click [Process].
  6. The crystal report launched successfully.
  7. Verify the report displays correct re-bill information.
  8. Close the report.
  9. Select 'Crystal' from the 'Claim/Episode/All Episodes' field.
  10. Select desired claim # created in the setup section.
  11. Click [Process].
  12. The crystal report launched successfully.
  13. Verify the report displays correct re-bill information.
  14. Close the report.
  15. Select 'Simple' from the 'Claim/Episode/All Episodes' field.
  16. Select desired claim # created in the setup section.
  17. Click [Process].
  18. The crystal report launched successfully.
  19. Verify the report displays correct re-bill information.
  20. Close the report.
Topics
• Client Ledger • NX
Update 120 Summary | Details
Dictionary Update - 'Location' dictionary
Internal Test Only
 
Program Maintenance - 'Time Zone' field
Internal Test Only
 
Avatar PM is enhanced to support future functionality
Internal Test Only
Topics
• Dictionary • Program Maintenance • Registry Settings
Update 125 Summary | Details
Dictionary Update - Client file
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Update (PM)
Scenario 1: Dictionary Update - Client file - Add/Edit/Print dictionary
Steps
  1. Open the 'Dictionary Update' form.
  2. Select 'Client' in the 'File' field.
  3. Select 'Claim Follow-Up Status' in the 'Data Element' field.
  4. Enter desired code to the 'Dictionary Code' field. Note the code.
  5. Enter desired value to the 'Dictionary Value' field. Note the value.
  6. Click [Apply Changes].
  7. Validate that the 'Information' dialog contains 'Filed!'.
  8. Click [OK].
  9. Enter desired code to the 'Dictionary Code' field. Note the code.
  10. Enter desired value to the 'Dictionary Value' field. Note the value.
  11. Click [Apply Changes].
  12. Validate that the 'Information' dialog contains 'Filed!'.
  13. Click [OK].
  14. Select 'Print Dictionary' section.
  15. Select 'Client' in the 'File' field.
  16. Select 'Individual Data Element' radio button.
  17. Select 'Claim Follow-Up Status' from the 'Data Element' field.
  18. Click [Print Dictionary].
  19. Review the report.
  20. Verify the dictionary codes / values added in previous step display correctly.
  21. Close the report.
  22. Select 'Input Dictionary Code(s)' section.
  23. Verify the 'File' field contains 'Client'.
  24. Verify the 'Data Element' is set to the 'Claim Follow-Up Status'.
  25. Select desired code which is added in previous step in the 'Dictionary Code' field.
  26. Verify the correct 'Dictionary Value' displays for the selected code.
  27. Update the value in the 'Dictionary Value' field.
  28. Click [Apply Changes].
  29. Validate that the 'Information' dialog contains 'Filed!'.
  30. Click [OK].
  31. Select 'Print Dictionary' section.
  32. Select 'Client' in the 'File' field.
  33. Select 'Individual Data Element' radio button.
  34. Select 'Claim Follow-Up Status' from the 'Data Element' field.
  35. Click [Print Dictionary].
  36. Review the report.
  37. Verify the dictionary codes / values updated in previous step display correctly.
  38. Close the report.
  39. Close the form.
Quick Billing Rule Definition - Include "errors.txt" File
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
  • Diagnosis
  • Financial Eligibility
  • Quick Billing Rule Definition
  • Client Charge Input
  • Quick Billing
  • Authorization Warning
  • Client Ledger
Scenario 1: Qucik Billing Rule Definition - 'Include "errors.txt" File' and 'File Location' for "errors.txt".
Specific Setup:
  • Registry Setting:
  • The 'Enable New Quick Billing Format' registry setting is set to 'Y'.
  • Facility Defaults:
  • Set the path to store the quick billing file in the 'Output Path On Server For Electronic Files' field. Note the path. Please note: This path will be used in the 'File Location' field of the 'Quick Billing Rule Definition' form.
  • File Explorer:
  • A physical location is created in the system which is defined in the 'Facility Defaults' form.
  • Another location is created under the folder which is defined for the 'File Location'.
  • Guarantors/Payors:
  • An existing guarantor is identified. Note the guarantor code/value.
  • Client:
  • Select a client that has missing data that will prevent it from being billed or create a new client.
  • This example will use a missing ‘Policy Number’ in Financial Eligibility’. Note the guarantor.
  • Financial Eligibility:
  • A guarantor is assigned to the client identified above.
  • Client Charge Input:
  • Rendered services that distributed to guarantor.
  • Client Ledger:
  • Verify all the charges distributed to the guarantor identified above.
  • Quick Billing Rue Definition:
  • A quick billing rule definition is defined that will include the guarantor, service code, and program.
  • ‘Send Generated Bill To' = File.
  • Note the ‘File Location’ value.
  • ‘Include “errors.txt” File’ = ‘No’.
Steps
  1. Open ‘Quick Billing’.
  2. Select ‘Add’ in ‘Add New Or Edit Existing Quick Billing Batch’.
  3. Enter desired ‘First Date Of Service To Include’.
  4. Enter desired ‘Last Date Of Service To Include’.
  5. Select desired ‘Billing Rule To Execute’.
  6. Select ‘Create Batch’, ‘Close Charges ’, and ‘Generate Bills’ in ‘Quick Billing Tasks to Execute’.
  7. Enter desired ‘Date Of Claim‘.
  8. Validate that the file does not compile successfully because of the missing policy number in the financial eligibility.
  9. Close the form.
  10. Go to the ‘File Location’ and verify that no error file was created.
  11. Open ‘Quick Billing Rule Definition’ and edit the rule from ‘Setup’.
  12. Change the ‘Include “errors.txt” File’ to ‘Yes’.
  13. Submit the form.
  14. Open ‘Quick Billing’.
  15. Select ‘Add’ in ‘Add New Or Edit Existing Quick Billing Batch’.
  16. Enter desired ‘First Date Of Service To Include’.
  17. Enter desired ‘Last Date Of Service To Include’.
  18. Select desired ‘Billing Rule To Execute’.
  19. Select ‘Create Batch’, ‘Close Charges’, and ‘Generate Bills’ in ‘Quick Billing Tasks to Execute’.
  20. Enter desired ‘Date Of Claim‘.
  21. Validate that the file does not compile successfully because of the missing policy number in the financial eligibility.
  22. Close the form.
  23. Go to the ‘File Location’ and verify that the error file was created.
  24. Open ‘Quick Billing Rule Definition’ and edit the rule from ‘Setup.
  25. Change the ‘Include “errors.txt” File’ to ‘In Separate Location’.
  26. Enter a value in ‘File Location for "errors.txt" File’ that differs from the ‘File Location’ value’.
  27. Submit the form.
  28. Open ‘Quick Billing’.
  29. Select ‘Add’ in ‘Add New Or Edit Existing Quick Billing Batch’.
  30. Enter desired ‘First Date Of Service To Include’.
  31. Enter desired ‘Last Date Of Service To Include’.
  32. Select desired ‘Billing Rule To Execute’.
  33. Select ‘Create Batch’, ‘Close Charges’, and ‘Generate Bills’ in ‘Quick Billing Tasks to Execute’.
  34. Enter desired ‘Date Of Claim‘.
  35. Validate that the file does not compile successfully because of the missing policy number in the financial eligibility.
  36. Close the form.
  37. Go to the ‘File Location for "errors.txt" File’ and verify that the error file was created.
  38. Fix the client data, in this example the missing ‘Policy Number’ in Financial Eligibility’.
  39. Open ‘Quick Billing’.
  40. Select ‘Add’ in ‘Add New Or Edit Existing Quick Billing Batch’.
  41. Enter desired ‘First Date Of Service To Include’.
  42. Enter desired ‘Last Date Of Service To Include’.
  43. Select desired ‘Billing Rule To Execute’.
  44. Select ‘Create Batch’, ‘Close Charges’, ‘Generate Bills’, and 'Create Claims' in ‘Quick Billing Tasks to Execute’.
  45. Enter desired ‘Date Of Claim‘.
  46. Validate that the ‘Compile Complete’ message indicates that no errors were found.
  47. Go to the ‘File Location’ and verify that the billing file was created.
  48. Open 'Client Ledger' for the client and validate that the claim number displays.
Topics
• Dictionary • Quick Billing
Update 137 Summary | Details
Avatar PM is enhanced to capture additional information
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Practitioner Enrollment
  • Practitioner Enrollment (Brief)
  • Dictionary Update (PM)
Scenario 1: 'Facility Defaults' form - field validations
Steps
  1. Access the 'Facility Defaults' form.
  2. Populate any desired fields.
  3. Click [Submit].
  4. Access Crystal Reports or other SQL Reporting tool.
  5. Create a report using the 'SYSTEM.table_facility_defaults' SQL table.
  6. Validate a row is displayed for the data on file.
  7. Validate the following audit fields are displayed and are populated accordingly:
  8. data_entry_by
  9. data_entry_by_option
  10. data_entry_date
  11. data_entry_time
  12. data_entry_user_id
  13. data_entry_user_name
  14. option_id
  15. option_desc
  16. The following audit fields will only be populated in a UTC enabled system:
  17. data_entry_utc
  18. data_entry_timezone_info_all
  19. data_entry_time_j
  20. data_entry_offset
  21. data_entry_timezone_short
  22. Close the report.
Scenario 2: 'PractitionerRegister' Web Service - Verification Of 'PractitionerRegister' Filing
Steps
  1. Using the 'PractitionerRegister' web service, submit a request using the 'PractitionerRegister' method to create a new 'Practitioner Enrollment' record, including a value for the 'OfficeAddressDate' field/segment.
  2. Confirm the 'PractitionerRegister' web service responds with confirmation data/ID on successful filing of 'PractitionerRegister' method.
  3. Example:"<Confirmation>Unique ID : 000056</Confirmation>"
  4. Confirm the 'PractitionerRegister' web service responds with confirmation message on successful filing of 'PractitionerRegister' method.
  5. Example:"<Message>Practitioner Enrollment web service has been filed successfully.</Message>"
  6. Confirm the 'PractitionerRegister' web service responds with successful status value on successful filing of 'PractitionerRegister' method.
  7. Example:" <Status>1</Status>"
  8. Access the 'Practitioner Enrollment' form and select the 'Practitioner Enrollment' record filed via web service for view/update.
  9. Confirm new Practitioner/Practitioner Enrollment record is created in Avatar PM, with values/data submitted via web service including 'Office Address - Start Date' field value.
Scenario 3: 'PractitionerRegister' Web Service - Verification Of 'EditPractitionerRegister' Filing
Specific Setup:
  • A practitioner must be defined in 'Practitioner Enrollment'.
Steps
  1. Using the 'PractitionerRegister' web service, submit a request using the 'EditPractitionerRegister' method to edit/update a 'Practitioner Enrollment' record, including a value for the 'OfficeAddressDate' field/segment.
  2. Confirm the 'PractitionerRegister' web service responds with confirmation data/ID on successful filing of 'EditPractitionerRegister' method.
  3. Example:"<Confirmation>Unique ID : 000056</Confirmation>"
  4. Confirm the 'PractitionerRegister' web service responds with confirmation message on successful filing of 'EditPractitionerRegister' method.
  5. Example:"<Message>Practitioner Enrollment web service has been filed successfully.</Message>"
  6. Confirm the 'PractitionerRegister' web service responds with successful status value on successful filing of 'EditPractitionerRegister' method.
  7. Example:" <Status>1</Status>"
  8. Access the 'Practitioner Enrollment' form and select the 'Practitioner Enrollment' record filed via web service for view/update.
  9. Confirm Practitioner/Practitioner Enrollment record is updated in Avatar PM, with values/data submitted via web service including the 'Office Address - Start Date' value.
Scenario 4: 'Practitioner Enrollment' - Form Verification
Specific Setup:
  • Crystal Reports or other SQL Reporting Tool.
Steps
  1. Access the 'Practitioner Enrollment' form.
  2. Select any existing practitioner for view/update.
  3. Validate the 'Office Address - Start Date' field is displayed.
  4. Enter any value in the 'Office Address - Start Date' field.
  5. Populate any other required and desired fields.
  6. Click [Submit].
  7. Access the 'Practitioner Enrollment' form.
  8. Select the same practitioner from the previous steps.
  9. Validate the 'Office Address - Start Date' field contains the value filed in the previous steps.
  10. Validate any other previously field data is displayed.
  11. Close the form.
  12. Access Crystal Reports or other SQL Reporting Tool.
  13. Create a report using the 'SYSTEM.staff_enrollment_history' SQL table.
  14. Navigate to the row for the practitioner used in the previous steps.
  15. Validate the 'office_add_date' field contains the value field in the previous steps.
  16. Close the report.
  17. Create a report using the 'SYSTEM.staff_current_demographics' SQL table.
  18. Navigate to the row for the practitioner used in the previous steps.
  19. Validate the 'office_add_date' field contains the value field in the previous steps.
  20. Close the report.
Scenario 5: 'Practitioner Enrollment (Brief)' - Form Verification
Specific Setup:
  • Crystal Reports or other SQL reporting tool.
Steps
  1. Access the 'Practitioner Enrollment (Brief)' form.
  2. Select any existing practitioner for view/update.
  3. Validate the 'Office Address - Start Date' field is displayed.
  4. Enter any value in the 'Office Address - Start Date' field.
  5. Populate any other required and desired fields.
  6. Click [Submit].
  7. Access the 'Practitioner Enrollment (Brief)' form.
  8. Select the same practitioner from the previous steps.
  9. Validate the 'Office Address - Start Date' field contains the value filed in the previous steps.
  10. Validate any other previously field data is displayed.
  11. Close the form.
  12. Access Crystal Reports or other SQL Reporting Tool.
  13. Create a report using the 'SYSTEM.staff_enrollment_history' SQL table.
  14. Navigate to the row for the practitioner used in the previous steps.
  15. Validate the 'office_add_date' field contains the value field in the previous steps.
  16. Close the report.
  17. Create a report using the 'SYSTEM.staff_current_demographics' SQL table.
  18. Navigate to the row for the practitioner used in the previous steps.
  19. Validate the 'office_add_date' field contains the value field in the previous steps.
  20. Close the report.
Scenario 6: Dictionary Update - Validate the 'Treatment Service' dictionary
Steps
  1. Access the 'Dictionary Update' form.
  2. Select "Client" in the 'File' field.
  3. Select "(101) Treatment Service" in the 'Data Element' field.
  4. Enter an existing code in the 'Dictionary Code' field.
  5. Validate the 'Dictionary Value' field populates accordingly.
  6. Validate the 'Extended Dictionary Data Element' field contains "(742) Encounter Code (FHIR)".
  7. Select "(742) Encounter Code (FHIR)" in the 'Extended Dictionary Data Element' field.
  8. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field.
  9. Click [Apply Changes].
  10. Validate a message is displayed stating: Filed!
  11. Click [OK].
  12. Select the "Print Dictionary" section.
  13. Select "Client" in the 'File' field.
  14. Select "Individual Data Element" in the 'Individual or All Data Elements' field.
  15. Select "(101) Treatment Service" in the 'Data Element' field.
  16. Click [Print Dictionary].
  17. Validate the report displays the updated dictionary with the "Encounter Code (FHIR)" extended dictionary value populated.
  18. Close the report and the form.
Topics
• Dictionary • Facility Defaults • Practitioner • Query/Reporting • Web Services
Update 139 Summary | Details
Payor Based Authorizations
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
  • Program Maintenance
  • Service Codes
  • Dictionary Update (PM)
  • Payor Based Authorizations
  • Admission
  • Diagnosis
  • Financial Eligibility
  • Client Charge Input
  • Client Ledger
  • Practitioner Numbers By Guarantor And Program
  • Electronic Billing
  • Authorization Warning
Scenario 1: PM - File Import - Payor Based Authorizations
Specific Setup:
  • Registry Settings:
  • Enable Payor Based Authorizations = 'Y'
  • Enable CPT Based Payor Authorizations = desired value.
  • Require Authorizations At Guarantors/Payors Level = desired value.
  • File Import: A file has been created for testing.
  • Note the values of all fields in the file for later comparison
  • The 'Avatar_PM_File_Import_Record_Layouts' is included in the update zip file to assist in creating the file.
Steps
  1. Open ‘File Import’ form.
  2. Select ‘Payor Based Authorizations’ in ‘File Type’.
  3. Upload the file.
  4. Compile the file.
  5. Print the file and validate the data.
  6. Post the file.
  7. Close the form.
  8. Open ‘Payor Based Authorizations’ form.
  9. Select ‘Edit’ in ‘Add/Edit/Delete’.
  10. Select the ‘Guarantor’ that was used in the import file.
  11. Click [Select Authorization To Edit/Delete].
  12. Select the desired row in the ‘Edit Entry’ table.
  13. Click [OK].
  14. Validate that ‘Effective Date’ contains the value in the import file.
  15. Validate that ‘Expiration Date’ contains the value in the import file.
  16. Validate that ‘Practitioner Category’ contains the value(s) in the import file.
  17. Validate that ‘Location’ contains the value(s) in the import file.
  18. Validate that ‘Authorization Group’ contains the value in the import file.
  19. Validate that ‘Service Code(s) ’ contains the value(s) in the import file.
  20. Validate that ‘Authorization Number’ contains the value in the import file.
  21. Close the form.
Scenario 2: PM - Payor Based Authorization - Location
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
  • Payor Based Authorizations: Create or edit a definition to include desired 'Locations' and any other desired fields. An error message will be included in the 837 Billing report.
  • Client A: Identify an active client that is assigned to the guarantor above.
Steps
  1. Open ‘Scheduling Calendar’.
  2. Create an appointment for Client A.
  3. Validate that the appropriate submission event occurs based on the values in the ‘Guarantors/Payors’, 'Authorization Section'.
  4. Close the form.
  5. Open ‘Client Charge Input’.
  6. Create a service for Client A.
  7. Validate that the appropriate submission event occurs based on the values in the ‘Guarantors/Payors’, 'Authorization Section'.
  8. Close the form.
  9. Open 'Close Charges’ and close charges for Client A if submission was allowed.
  10. Close the form.
  11. Open ‘Electronic Billing’ if submission was allowed.
  12. Create the bill for Client A and validate that the appropriate billing action occurs based on the values in the ‘Guarantors/Payors’, 'Authorization Section'.
  13. Close the form.
  14. Open ‘Client Ledger’ for Client A if submission was allowed.
  15. Review the ‘Simple’, ‘Ledger Type’ to confirm the billing activity.
  16. Close the form.
Topics
• Client Charge Input • File Import • NX • Payor Based Authorizations