Skip to main content

Avatar PM 2024 Quarterly Release 2024.01 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 1 Summary | Details
2024 Update installation
Scenario 1: Validate Upgrading Avatar PM 2023 to 2024 is successful when 2023.04.00 is loaded
Steps
  1. Open the "Product Updates" form.
  2. Select the appropriate [Namespace] from the Application dropdown list
  3. Click [Select Update/Customization Pack].
  4. Browse to the location for the updates and select the Update 1.
  5. Click [OK] on the "File Upload Complete" window.
  6. Click [Review Update/Customization Pack Contents].
  7. Verify Update 1 is included.
  8. Click [Install Update/Customization Pack].
  9. Click [OK] when the install completes.
  10. Click [Close Form].
Topics
• Upgrade
Update 2 Summary | Details
CPT Codes Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CPT Code Definition (PM)
Scenario 1: CPT Codes: Annual code update
Steps
  1. Open Avatar PM 'CPT Code Definition' form.
  2. Click [Print CPT Codes].
  3. A list of the current CPT Codes will display.
  4. Review the list to assure new codes have been added.
  5. Click [Close].
Topics
• CPT Codes • NX
Update 5 Summary | Details
Internal Utilities
Scenario 1: 'Support Utilities' Form (Internal only) - Validate Export 'Envelope' and Export 'Report' Attributes functionality
Steps
  1. Internal Testing Only
Topics
• Modeling
Update 6 Summary | Details
Client Lookup - Sub-System Codes
Internal Test Only
Topics
n/a
Update 7 Summary | Details
Site Specific Section Modeling - Disclosure Management
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Site Specific Section Modeling (PM)
Scenario 1: Site Specific Section Modeling - Validating field add/remove - PATIENT40000 (Disclosure Management) - Request, Authorization, Disclosure section
Steps
  1. Open the 'Site Specific Section Modeling' form.
  2. Select the 'PATIENT40000 (Disclosure Management) Request' from the list.
  3. Select the 'Prompt Definition' section.
  4. Click [Add New Item].
  5. Select desired items from the 'Site Specific Field'.
  6. Verify the 'Prompt Definition' table contains the selected item.
  7. Click [Submit].
  8. Open the 'Site Specific Section Modeling' form.
  9. Select the 'PATIENT40000 (Disclosure Management) Request' from the list.
  10. Select the 'Prompt Definition' section.
  11. Select recently added item from the 'Prompt definition' table.
  12. Click [Edit Selected Item].
  13. Click [Delete Selected Item].
  14. Verify the 'Are you sure' prompt exists.
  15. Click [Yes].
  16. Verify the selected item is deleted from the 'Prompt Definition' table.
  17. Click [Discard].
  18. Open the 'Site Specific Section Modeling' form.
  19. Select the 'PATIENT40000 (Disclosure Management) Authorization' from the list.
  20. Select the 'Prompt Definition' section.
  21. Click [Add New Item].
  22. Select desired items from the 'Site Specific Field'.
  23. Verify the 'Prompt Definition' table contains the selected item.
  24. Click [Submit].
  25. Open the 'Site Specific Section Modeling' form.
  26. Select the 'PATIENT40000 (Disclosure Management) Authorization' from the list.
  27. Select the 'Prompt Definition' section.
  28. Select recently added item from the 'Prompt definition' table.
  29. Click [Edit Selected Item].
  30. Click [Delete Selected Item].
  31. Verify the 'Are you sure' prompt exists.
  32. Click [Yes].
  33. Verify the selected item is deleted from the 'Prompt Definition' table.
  34. Click [Discard].
  35. Open the 'Site Specific Section Modeling' form.
  36. Select the 'PATIENT40000 (Disclosure Management) Disclosure' from the list.
  37. Select the 'Prompt Definition' section.
  38. Click [Add New Item].
  39. Select desired items from the 'Site Specific Field'.
  40. Verify the 'Prompt Definition' table contains the selected item.
  41. Click [Submit].
  42. Open the 'Site Specific Section Modeling' form.
  43. Select the 'PATIENT40000 (Disclosure Management) Disclosure' from the list.
  44. Select the 'Prompt Definition' section.
  45. Select recently added item from the 'Prompt definition' table.
  46. Click [Edit Selected Item].
  47. Click [Delete Selected Item].
  48. Verify the 'Are you sure' prompt exists.
  49. Click [Yes].
  50. Verify the selected item is deleted from the 'Prompt Definition' table.
  51. Click [Discard].
  52. Open the 'Site Specific Section Modeling' form.
  53. Select the 'PATIENT40000 (Disclosure Management) Request' from the list.
  54. Select the 'Prompt Definition' section.
  55. Double click on the desired field in the 'Prompt Definition' table.
  56. Verify that all the information of the field populated correctly.
  57. Submit the form.
  58. Verify the form submitted successfully.
  59. Repeat steps from 53 through 58 for 'PATIENT40000 (Disclosure Management) Authorization' and 'PATIENT40000 (Disclosure Management) Disclosure' option.
837 Dental - Validating Re-Bill Services - Restrict to date range
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Fee/Cross Reference Maintenance
  • Guarantors/Payors
  • Financial Eligibility
  • Client Charge Input
  • Client Ledger
  • Create Interim Billing Batch File
  • Electronic Billing
  • Electronic Re-Billing Service Assignment
Scenario 1: 837 Dental - Compile re-bill claims for all clients - Restrict to date range
Specific Setup:
  • Registry Setting:
  • Avatar PM Registry Setting 'Enable Dental Billing' must be enabled/set to value 'Y'.
  • Guarantors/Payors:
  • An existing guarantor is identified to be used. Note the guarantor's code/name.
  • Populated all the required fields to run the 837 Dental claim.
  • Guarantor/Program Billing defaults:
  • Select desired template that includes desired guarantor and program. Note the program/guarantor.
  • Populated all the required fields to run the 837 Dental claim in the '837 Dental' section.
  • Service codes:
  • An existing dental service code is identified to be used. Note the service code/description.
  • The 'Is This A Dental Service' is set to 'Yes'.
  • Service Fee/ Cross Reference Maintenance:
  • A fee definition is created for the service code identified in the ' Service Codes' form.
  • Admission:
  • An existing client is identified, or a new client is admitted. Note client id, admission program, admission date.
  • Financial Eligibility:
  • The guarantor identified in the 'Guarantors/Payors' form is assigned to the client as a primary guarantor.
  • Set subscriber assignment of benefits to 'No' for the primary guarantor but 'Yes' to the secondary guarantor.
  • Client Charge Input:
  • A dental service is rendered to the client. Note service date, service code.
  • Client Ledger:
  • A service distributed correctly to the primary guarantor.
  • Close Charges:
  • Close the charges distributed to the client and guarantor.
  • Create Interim Billing Batch File:
  • Create an interim billing batch file that covers the services distributed to the primary guarantor of the client. Note the batch number.
Steps
  1. Open the 'Electronic Billing' form.
  2. Select '837-Dental' from the 'Billing Form' dropdown list.
  3. Select desired guarantor from the 'Type Of Bill' dropdown list.
  4. Select desired value from the 'Individual Or All Guarantors' field.
  5. Select desired guarantor from the 'Guarantor' dropdown list.
  6. Select desired 'Billing Type'.
  7. Select the 'Sort File' from the 'Billing Options' field.
  8. Set the 'File Description' field to desired value.
  9. Select the 'Interim Billing' in the 'Select All Clients Or Interim Batch' field.
  10. Select the interim billing batch file created in the setup section.
  11. Populate all the required fields.
  12. Compile the bill for the primary guarantor.
  13. Verify the bill compiles successfully.
  14. Claim the bill for the primary guarantor.
  15. Verify the bill compiles successfully.
  16. Review the dump file. Note the claim Number.
  17. Close the file.
  18. Close the form.
  19. Open the 'Electronic Re-Billing Service Assignment' form.
  20. Flag the claim from above step for rebill.
  21. Note the following values in the form: 'Billing Form'; 'Claim Submission Reason Code; and 'Claim Original Reference Number'.
  22. Submit the form.
  23. Open the 'Electronic Billing' form.
  24. Select '837-Dental' from the 'Billing Form' dropdown list.
  25. Select desired guarantor from the 'Type Of Bill' dropdown list.
  26. Select desired value from the 'Individual Or All Guarantors' field.
  27. Select desired guarantor from the 'Guarantor' dropdown list.
  28. Select desired 'Billing Type'.
  29. Select the 'Sort File' from the 'Billing Options' field.
  30. Set the 'File Description' field to desired value.
  31. Select the 'Interim Billing' in the 'Select All Clients Or Interim Batch' field.
  32. Select the interim billing batch file created in the setup section.
  33. Select either 'All Clients (Restrict to Date Range)' or 'All Clients (only compile re-bill services)(Restrict to Date Range)' in the 'Include Services Assigned For Re-Bill' field.
  34. Select a date range that falls outside the service included in the claim from above steps.
  35. Compile the bill.
  36. Verify that the file does not compile successfully.
  37. Verify the 'No Information Found' message.
  38. Compile the bill with a date range that is inclusive of services in the claim.
  39. Verify the bill compiles successfully.
  40. Review the dump file.
  41. Verify the service is included in the bill.
  42. Close the file.
  43. Close the form.
Topics
• Site Specific Section Modeling • Disclosure • 837 Dental
Update 8 Summary | Details
File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
Scenario 1: File Import - Guarantors/Payors - 834 Submission section
Specific Setup:
  • File Import:
  • The 'Guarantors/Payors 834 Submission file type is added to the File Import. "File A".
  • Create an import file to add 834 Submission details to a valid Guarantor.
Steps
  1. Open the "File Import" form.
  2. Select the "Guarantors/Payors 834 Submission" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Select the "File A".
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select the "File A" in the Files(s) field.
  8. Click [Process Action].
  9. Validate an Information message is displayed stating: Compiled
  10. Click [OK].
  11. Select "Print File" in the 'Action' field.
  12. Select the "File A" in the Files(s) field.
  13. Click [Process Action].
  14. Validate the Report Viewer displays the contents of the file.
  15. Click [Close Report].
  16. Select "Post File" in the 'Action' field.
  17. Click [Process Action].
  18. Select the "File A".
  19. Validate an Information message is displayed stating: Posted.
  20. Click [OK] and close the form.
  21. Open the "Guarantors/Payors" form.
  22. Click [Edit].
  23. Select the Valid Guarantor given in File A.
  24. Validate the form is filed with the data based on the uploaded file.
  25. Close the form.
Topics
• File Import
Update 9 Summary | Details
File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
Scenario 1: File Import: Guarantors Payors 835
Specific Setup:
  • File Import:
  • The 'Guarantors/Payors 835 Submission' file type is added to "File Import"
  • Create an import file to add 835 details to a valid Guarantor. 'File A'
Steps
  1. Open the "File Import" form.
  2. Select the "Guarantors/Payors 835" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Select "File A".
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select "File A" in the 'Files(s)' field.
  8. Click [Process Action].
  9. Validate an Information message is displayed stating: Compiled
  10. Click [OK].
  11. Select "Print File" in the 'Action' field.
  12. Select "File A" in the 'Files(s)' field.
  13. Click [Process Action].
  14. Validate the Report Viewer displays the contents of the file.
  15. Click [Close Report].
  16. Select "Post File" in the 'Action' field.
  17. Click [Process Action].
  18. Select "File A".
  19. Validate an Information message is displayed stating: Posted.
  20. Click [OK] and close the form.
  21. Open the "Guarantors/Payors" form.
  22. Click [Edit].
  23. Select the guarantor in "File A".
  24. Select the '835' section.
  25. Validate the form is filed with the data based on the uploaded file.
  26. Close the form.
Topics
• File Import • NX
Update 10 Summary | Details
Return From Leaves
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
  • Leaves
Scenario 1: Return From Leaves-Submission
Specific Setup:
  • Registry Setting:
  • The registry setting ‘Default Last Bed On Return From Leave’ set it to 'y'.
  • Admission:
  • An existing In-Patient is identified, or a new Patient is admitted. Note the Patient's id/name, episode number, admission program.
Steps
  1. Open the "Leaves" form.
  2. Enter the "Leave Date"
  3. Select the desired value from the "Type of Leave From" drop down list.
  4. Select the desired value from the "Reason for Leave" drop down list.
  5. Click [Submit].
  6. Open the "Return From Leaves " form.
  7. Verify that the 'Unit' defaults in the "Unit" drop down list.
  8. Verify that the 'Room' defaults in the "Room" drop down list.
  9. Verify that the 'Bed' defaults in the "Bed" drop down list.
  10. Enter the "Return Date".
  11. Select the desired value from the "Reason for Closure of Leave" drop down list.
  12. Click [Submit].
  13. Validate the Error Message.
  14. Click OK.
  15. Select the unit assigned in Program Maintenance.
  16. Select a room from "Room" drop down list.
  17. Select a bed from "Bed" drop down list.
  18. Click [Submit].
  19. Verify the form files successfully.
Topics
• Leaves • NX
Update 12 Summary | Details
Dictionary Update - 'Unit' dictionary
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 - Validate the 'Unit' dictionary
Steps
  1. Access the 'Dictionary Update' PM form.
  2. Select "Client" in the 'File' field.
  3. Select "Data Element Number" in the 'Data Element' field.
  4. Select "(202) Unit" in the 'Data Element' field.
  5. Enter the desired value in the 'Dictionary Code' field.
  6. Enter the desired value in the 'Dictionary Value' field.
  7. Validate the 'Extended Dictionary Data Element' field contains the following new values:
  8. (22055) Facility Abbreviation
  9. (22056) Level of Care
  10. Select "(22055) Facility Abbreviation" in the 'Extended Dictionary Data Element' field.
  11. Validate the 'Extended Dictionary Value (Free Text)' field is now enabled. Enter the desired value.
  12. Select "(22056) Level of Care" in the 'Extended Dictionary Data Element' field.
  13. Validate the 'Extended Dictionary Value (Single Dictionary)' field is now enabled and contains the following values:
  14. Inpatient
  15. Observation
  16. Outpatient
  17. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field.
  18. Click [Apply Changes].
  19. Select the "Print Dictionary" section.
  20. Select "Client" in the 'File' field.
  21. Select "Data Element Number" in the 'Data Element' field.
  22. Select "(202) Unit" in the 'Data Element' field.
  23. Click [Print Dictionary].
  24. Validate the unit dictionary is displayed with the 'Facility Abbreviation' and 'Level of Care' values filed in the previous steps.
  25. Click [Close] and close the form.
Topics
• Dictionary
Update 13 Summary | Details
Financial Eligibility - Comments Section
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
Scenario 1: Financial Eligibility - Comments - Merged Clients
Specific Setup:
  • "Client A" and "Client B" must be enrolled in an existing episode.
Steps
  1. Select "Client A" and access the 'Financial Eligibility' form.
  2. Select the 'Guarantor Selection' tab.
  3. Click [Add New Item].
  4. Enter any value in the 'Guarantor #' field.
  5. Select any value in the 'Guarantor Plan' field.
  6. Select "No" in the 'Customize Guarantor Plan' field.
  7. Validate a "Confirm" message is displayed stating: This Will Delete Any Information Previously Filed In 'Customize Plan'.
  8. Click [OK].
  9. Select ''Yes'' in the 'Eligibility Verified' field.
  10. Enter the current date in the 'Coverage Effective Date' field.
  11. Select any value in the 'Client's Relationship To Subscriber' field.
  12. Enter any value in the format of Last Name, First Name in the 'Subscriber's Name' field.
  13. Enter any value in the 'Subscriber Address - Street Line 1' field.
  14. Enter any value in the 'Subscriber's Address - Zip code' field.
  15. Enter any value in the 'Subscriber's Social Security #' field.
  16. Select any value in the 'Subscriber Sex' field.
  17. Select any value in the 'Coordination of Benefits' field.
  18. Select any value in the 'Subscriber Assignment of Benefits' field.
  19. Select any value in the 'Subscriber Release Of Info' field.
  20. Select the 'Financial Eligibility' tab.
  21. Select the guarantor selected in the previous steps in the 'Guarantor #1' field.
  22. Select the 'Coverage Comments' text area and add any comment.
  23. Submit the form.
  24. Repeat the above steps 1 -23 for "Client B".
  25. Open the 'Client Merge' form.
  26. Select "Client B" in 'Source Client'.
  27. Select "Client A" in 'Target Client.
  28. Click Yes - Merge All Client Data Through Single Filing.
  29. Close the form.
  30. Search for "Client B", the 'Source Client' and verify that no search results are returned.
  31. Open 'Financial Eligibility' for "Client A".
  32. Validate the comments.
  33. Close the form.
  34. Right-Click on "Client A" in the "My Clients" widget
  35. Click "Display Chart"
  36. On the "Chart" screen, click the "Customize Forms" icon
  37. Click the "Add New Form Group" icon in the right corner
  38. Populate the "Name of new form group" text box
  39. Click [OK]
  40. Click the "Add New Form to this Group" icon
  41. In the "Search Forms" text box, search for financial eligibility and double-click to add the form
  42. Validate the form displays in the forms list text box.
  43. Click [Submit]
  44. Validate the form is listed under the new group name on the left side panel
  45. Click the "Refresh" button.
  46. Double click on Financial Eligibility to view chart.
  47. Validate the chart view shows comments for the merged target - "Client A".
  48. Close the form.
Financial Eligibility - Guarantor Selection
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
Scenario 1: Financial Eligibility - Guarantor Selection
Specific Setup:
  • "Client A" must be enrolled in an existing episode.
Steps
  1. Open the 'Financial Eligibility' form.
  2. Select the "Client A".
  3. Select the 'Guarantor Selection' tab.
  4. Click [Add New Item].
  5. Enter any value in the 'Guarantor #' field.
  6. Select any value in the 'Guarantor Plan' field.
  7. Select "No" in the 'Customize Guarantor Plan' field.
  8. Validate a "Confirm" message is displayed stating: This Will Delete Any Information Previously Filed In 'Customize Plan'.
  9. Click [OK].
  10. Select "Yes" in the 'Eligibility Verified' field.
  11. Enter the current date in the 'Coverage Effective Date' field.
  12. Select any value in the 'Client's Relationship To Subscriber' field.
  13. Enter any value in the format of Last Name, First Name in the 'Subscriber's Name' field.
  14. Enter any value in the 'Subscriber Address - Street Line 1' field.
  15. Enter any value in the 'Subscriber's Address - Zip code' field.
  16. Enter any value in the 'Subscriber's Social Security #' field.
  17. Enter any value in the 'Subscriber Sex' field.
  18. Select any value in the 'Coordination of Benefits' field.
  19. Select any value in the 'Subscriber Assignment of Benefits' field.
  20. Select any value in the 'Subscriber Release Of Info' field.
  21. Select the 'Financial Eligibility' tab.
  22. Select the guarantor selected in the previous steps in the 'Guarantor #1' field.
  23. Click [Submit].
  24. Open the 'Financial Eligibility' form.
  25. Select the "Client A".
  26. Select the 'Guarantor Selection' tab.
  27. Click [Edit Selected Item].
  28. Edit coverage Effective Date.
  29. Edit Subscriber Zip Code.
  30. Select any value in the 'Subscriber Release Of Info' field.
  31. Select the guarantor selected in the previous steps in the 'Guarantor #1' field.
  32. Click [Submit].
  33. Open the 'Financial Eligibility' form.
  34. Select the "Client A".
  35. Select the 'Guarantor Selection' tab.
  36. Validate the fields are edited.
  37. Click [Submit].
Topics
• Financial Eligibility • Client Merge • NX
Update 14 Summary | Details
Site Specific Section Modeling - 'Admission' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Site Specific Section Modeling (PM)
  • Discharge
Scenario 1: Avatar PM - Site Specific Section Modeling - Admission
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access the 'Site Specific Section Modeling' PM form.
  2. Validate the 'Site Specific Section' field contains only the following options for the 'Admission' form:
  3. PATIENT510 (Admission) Site Specific Admission
  4. PATIENT510 (Admission) Demographics
  5. Select "PATIENT510 (Admission) Site Specific Admission" in the 'Site Specific Section' field.
  6. Click [OK].
  7. Validate the 'Site Specific Section Modeling' form is displayed as expected.
  8. Select "Yes" in the 'Enable Site Specific Section' field.
  9. Navigate to the "Prompt Definition" section.
  10. Click [Add New Item].
  11. Select the desired SS field in the 'Site Specific Field', for example "SS Admission Date 1".
  12. Select "No" in the 'Initially Required' field.
  13. Select the desired value in the 'Display Future Date Warning' field.
  14. Submit the form.
  15. Select "Client A" and access the 'Admission' form.
  16. Select any existing episode and click [Edit].
  17. Validate the "Site Specific Admission" section is displayed and select it.
  18. Validate the SS field selected in the previous steps is displayed, for example "SS Admission Date 1".
  19. Close the form.
Topics
• Site Specific Section Modeling
Update 15 Summary | Details
'Update Client Data' quick action
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Quick Actions Page
Scenario 1: Validate the 'Update Client Data' quick action
Specific Setup:
  • Please note: this is for Avatar NX only.
  • The 'Update Client Data' Quick Action must be assigned to the user's myDay view in the 'NX View Definition' form.
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and navigate to the 'Quick Actions' widget.
  2. Click [Update Client Data - Add].
  3. Populate all required and desired fields.
  4. Enter "1" in the 'Home Phone' field.
  5. Validate a message is displayed stating: Invalid phone format specified. Valid phone formats are: '000-0000', '000-0000 X 0000', '000-000-0000', '000-000-0000 X - 0000'.
  6. Click [OK].
  7. Validate the 'Home Phone' field is cleared out.
  8. Enter "111-111-1111" in the 'Home Phone' field.
  9. Enter "abcdefg" in the 'Work Phone' field.
  10. Validate a message is displayed stating: Invalid phone format specified. Valid phone formats are: '000-0000', '000-0000 X 0000', '000-000-0000', '000-000-0000 X - 0000'.
  11. Click [OK].
  12. Validate the 'Work Phone' field is cleared out.
  13. Enter "222-2222" in the 'Work Phone' field.
  14. Enter "555" in the 'Cell Phone' field.
  15. Validate a message is displayed stating: Invalid phone format specified. Valid phone formats are: '000-0000', '000-0000 X 0000', '000-000-0000', '000-000-0000 X - 0000'.
  16. Click [OK].
  17. Validate the 'Cell Phone' field is cleared out.
  18. Enter "333-3333 X - 3333" in the 'Cell Phone' field.
  19. Click [Save].
  20. Select "Client A" and access the 'Update Client Data' form.
  21. Validate the 'Home Phone' field contains "111-111-1111".
  22. Validate the 'Work Phone' field contains "222-2222".
  23. Validate the 'Cell Phone' field contains ""333-3333 X - 3333".
  24. Validate all other previously filed data is displayed.
  25. Close the form.
  26. Select "Client A" and navigate to the 'Quick Actions' widget.
  27. Click [Update Client Data - Add].
  28. Validate all previously filed data is displayed.
  29. Clear out the value in the 'Home Phone' field.
  30. Clear out the value in the 'Cell Phone' field.
  31. Clear out the value in the 'Work Phone' field.
  32. Click [Save].
  33. Select "Client A" and access the 'Update Client Data' form.
  34. Validate the 'Home Phone' field does not contain any value.
  35. Validate the 'Work Phone' field does not contain any value.
  36. Validate the 'Cell Phone' field does not contain any value.
  37. Close the form.
Topics
• Update Client Data • NX
Update 16 Summary | Details
Future Functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Create Interim Billing Batch File
  • Remittance Processing Widget
Scenario 1: Remittance Processing Widget - Validating ability to scroll or load info when remittance grid contains large volume of rows
Specific Setup:

N/A

Steps

Internal testing only.
Topics
• NX
Update 17 Summary | Details
Service Codes - Medication Management Procedure Type
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Finalize
  • Medical Note
  • Medication Inventory Management
  • Service Code Upload Process
  • Lot Number Manager
  • Adjust Inventory
  • Client Health Maintenance
Scenario 1: Medical Note - Inventory Management Disabled - Full Note Workflow
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • Two 'Vaccination/Immunization' procedure-type service codes must be configured in the 'Service Codes' form. (Immunization A) (Immunization B)
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • A procedure-type service code that is not a "Vaccination/Immunization" nor "Medication Administration" must be configured in the 'Service Codes' form. (Procedure A)
  • An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and access 'Medical Note'.
  2. Click [Add Note] and create a new "Primary Care" Note.
  3. In the Facesheet:
  4. Select the ‘Vitals’ section and enter Blood Pressure, Height, Weight, and Temperature information, click [Save], and pull to note.
  5. Select the ‘Immunization’ section and enter a “Historical Immunization” record for yesterday.
  6. Select the ‘Allergies’ section and enter an allergy to “Shellfish” and pull to note.
  7. Select the ‘Document’ tab.
  8. Complete the 'Chief Complaint', 'HPI', 'Physical Exam' and 'Diagnosis' sections as necessary.
  9. Select the ‘Immunizations’ section.
  10. Expand the ‘Immunization History’ section and validate the Historical Immunization Record for the precious day is correctly shown.
  11. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  12. Fill in any required fields and click [Order].
  13. Click [Add] and then [Order Immunizations], select "Immunization B" from the 'Immunization Search' field and click [Continue].
  14. Fill in any required fields and click [Administer].
  15. Validate "Immunization A" is listed under the 'Pending Administrations' section and " Immunization B" is listed under the 'Immunization History' section.
  16. Populate all required fields and click [Save].
  17. Select the ‘Procedures’ section and click [Add].
  18. Select "Procedure A" from the 'Procedure' field.
  19. Select "Complete" from the 'Status' field.
  20. Set the 'Completion Date' field to "Today's Date.
  21. Populate any remaining required fields and click [Save].
  22. Validate "Procedure A" is listed under the 'Current Procedures' Section.
  23. Select the ‘In Office Administrations’ section.
  24. Click [Add], select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  25. Populate all required fields and click [Administer].
  26. Populate all required fields and click [Save].
  27. Click [Add], select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  28. Populate all required fields and click [Order].
  29. Validate "Medication A" is listed under the 'Pending Administrations' section and " Medication A" is listed under the 'Administration History' section.
  30. Select the ‘Finalize’ tab.
  31. Populate all required fields and click [Generate Note].
  32. Validate the ‘Note Summary’ is displayed and contains the appropriate information:
  33. The populated sections of the 'Facesheet' tab that were pulled into the note. (Allergies and Vitals)
  34. The required and populated sections of the 'Document' tab. (Chief Complaint, HPI, Physical Exam, Diagnosis)
  35. The 'Immunizations' section shows "Immunization A" in the 'Ordered (Pending)' section and "Immunization B" in the 'Administered In-Office' section.
  36. The 'Procedures' section shows "Procedure A" as complete.
  37. The 'In-Office Administrations' section shows "Medication A" in the 'Ordered (Pending)' section and "Medication B" in the 'Administered In-Office' section.
  38. Click [Sign Off] validate the Document is displayed and click [Accept], set the ‘Password’ field to the appropriate value and click [Verify].
Scenario 2: Medical Note - Inventory Management Enabled - In-Office Administration - Full Note Workflow
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A generic 'Evaluation Management' service code must be configured in the 'Service Codes' form. (Service Code A)
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • "Medication A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form inventory for "Template A" must be received to "Location A". (Inventory A)
  • An outpatient program must exist. (Program A)
  • In the 'Assign Services To Program' section of the 'Program Maintenance' form "Service Code A" must be associated to "Program A".
  • A client must have an active episode associated with "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Psychiatry' note.
  4. Select the ‘Document’ tab.
  5. Populate all required sections in the 'Document' tab.
  6. Click the 'In-Office Administration' section.
  7. Click [Add] and select "Medication A" from the 'In-Office Administration Search' field.
  8. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A"
  9. Fill in any remaining required fields and click [Order].
  10. Validate the 'Pending Administrations' field contains a row for "Medication A".
  11. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  12. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  13. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  14. Select the row for "Inventory A" and click [Select].
  15. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC" are all correctly populated and disabled.
  16. Fill in any remaining required fields and click [Save].
  17. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  18. Click the ellipses under the 'Action' column for "Medication A" and click [Document Reaction].
  19. Select any value for the 'Reaction' field and click [Save].
  20. Click the ellipses under the 'Action' column for "Medication A" and click [View Details].
  21. Validation the 'Reaction' field contains the correct value and click [Close]
  22. Select the ‘Finalize’ tab.
  23. Populate all required fields and click [Generate Note].
  24. Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
  25. Validate the Document is displayed and click [Accept], set the ‘Password’ field to the appropriate value and click [Verify].
Scenario 3: Medical Note - Administering a medication order under the 'In-Office Administration' section when 'Inventory Management' is disabled - Pediatric
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • An outpatient program that is configured in the 'Program Maintenance' form to be a 'Primary Care' program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab.
  4. Navigate to the 'Diagnosis' section.
  5. Add a new diagnosis for "Client A".
  6. Navigate to the 'In-Office Administrations' section.
  7. Click [Add] and select "Medication A" from the 'In-Office Administrations Search' field.
  8. Validate the new diagnosis is listed under the 'Diagnosis' dropdown and select it.
  9. Fill in any remaining required fields and click [Order].
  10. Validate the 'Pending Administrations' field contains a row for "Medication A"
  11. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  12. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and that all fields are disabled.
  13. Fill in all required fields and click [Save].
  14. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  15. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
Scenario 4: Medical Note - Administering a medication under the 'Pending Administration' sub-section of 'In Office Administration' and voiding the medications under the 'Administration History' section
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • Two 'Medication Administration' procedure-type service codes must be configured in the 'Service Codes' form. (Medication A)(Medication B)
  • An Outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
  4. Click [Add], select "Medication A" from the 'In-Office Administration Search' field and click [Continue].
  5. Populate all required fields and click [Order].
  6. Validate the 'Pending Administrations' field contains a row for "Medication A".
  7. Click [Add], select "Medication B" from the 'In-Office Administration Search' field and click [Continue].
  8. Populate all required fields and click [Order].
  9. Validate the 'Pending Administrations' field contains a row for "Medication A" and one for "Medication B".
  10. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  11. Populate all required fields and click [Save].
  12. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  13. Click the ellipses under the 'Action' column for "Medication B" and click [Refuse].
  14. Set the 'Refusal Reason' field to any value and click [Save].
  15. Validate the 'Administration History' field contains a row for "Medication A" and the status shows as "Administered".
  16. Validate the 'Administration History' field contains a row for "Medication B" and the status shows as "Refused".
  17. Click the ellipses under the 'Action' column for "Medication B" and click [Void].
  18. Set the 'Comments' field to any value and click [Save].
  19. Validate the 'Administration History' field contains a row for "Medication B" and the status shows as "Voided".
Scenario 5: Medical Note - Edit a medication that is listed under the 'Pending Medications' sub-section in the 'In-Office Administrations' section
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • "Medication A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A". (Inventory A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add] and select "Medication A" from the 'In-Office Administrations Search' field.
  5. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  6. Fill in any remaining required fields and click [Order].
  7. Validate the 'Pending Administrations' field contains a row for "Medication A".
  8. Click the ellipses under the 'Action' column for "Medication A" and click [Edit].
  9. Set the 'Dose' and 'Unit' fields to any other values and click [Update].
  10. Validate the row for "Medication A" in the 'Pending Administrations field reflects the updated values.
  11. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  12. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  13. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  14. Select the row for "Inventory A" and click [Select].
  15. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC" are all correctly populated and disabled.
  16. Fill in any remaining required fields and click [Save].
  17. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  18. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
Scenario 6: Medical Note - Order an In-Office Administration as "Provider" - Edit/Administer as "Nurse"
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • "Medication A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A". (Inventory A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
  • Two users must exist. (User A) (User B).
  • "User A" who is configured as a "Provider".
  • "User B" who is configured as a "Nurse".
Steps
  1. Log into the application as "User A".
  2. Search for and select "Client A" and navigate to 'Medical Note'.
  3. Click [Add Note] and create a new note.
  4. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  5. Click [Add], search for and select "Medication A" from the 'In-Office Administrations Search' field, and click [Continue].
  6. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  7. Populate any remaining required fields and click [Order].
  8. Validate the 'Pending Administrations' field contains a row for "Medication A" and click [Save Draft].
  9. Log out of the application and then log in as "User B".
  10. Search for and select "Client A" and navigate to the 'Medical Note'.
  11. Click [Select Note] and select the newly created note.
  12. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  13. Validate the 'Pending Administrations' field contains a row for "Medication A".
  14. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  15. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and that all fields are disabled.
  16. Validate the 'Entered By' and 'Ordered By' fields contain "User A" and the 'Administered By' field contains "User B".
  17. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  18. Select the row for "Inventory A" and click [Select].
  19. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC" are all correctly populated and disabled.
  20. Populate all remaining required fields and click [Save].
  21. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  22. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  23. Log out of the application and then log in as "User A".
  24. Search for and select "Client A" and navigate to the 'Medical Note'.
  25. Click [Select Note] and select the newly created note.
  26. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  27. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  28. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
Scenario 7: Medical Note - Immunizations - Edit; Cancel; Grouping
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • Two 'Vaccination/Immunization' procedure type service codes must be configured in the 'Service Codes' form. (Immunization A)(Immunization B).
  • "Immunization A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A" and the 'Manufacturer of Vaccine (MVX)' and 'Vaccine Code (CVX)' fields must be populated. (Inventory A)
  • An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  4. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  5. Fill in any required fields and click [Order].
  6. Click [Add] and then [Order Immunizations], select "Immunization B" from the 'Immunization Search' field and click [Continue].
  7. Fill in any required fields and click [Order].
  8. Click the ellipses under the 'Action' column for "Immunization A" and click [Edit].
  9. Change the values for the 'Dose' and 'Route' fields and click [Update].
  10. Click the ellipses under the 'Action' column for "Immunization B" and click [Cancel].
  11. Validate the 'Cancel Pending Administration' dialog appears and contains: "Are you sure you want to cancel this pending administration? Canceling this will permanently remove this pending administration."
  12. Click [Continue], populate the 'Comments' field and click [Save].
  13. Validate the 'Pending Immunizations' section only contains a row for "Immunization A".
  14. Click the ellipses under the 'Action' column for "Immunization A" and click [Administer].
  15. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated according to the edited values, and that all fields are disabled.
  16. Select "Facility" from the 'Provided By' field.
  17. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  18. Select the row for "Inventory A" and click [Select].
  19. Validate all fields in the "Administration Details' section are populated correctly.
  20. Populate any remaining required fields and click [Save].
  21. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and all columns are correctly populated.
  22. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  23. Populate any required fields and click [Administer].
  24. Set the 'Provided By' field to "Facility".
  25. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  26. Select the row for "Inventory A" and click [Select].
  27. Validate all fields in the "Administration Details' section are populated correctly.
  28. Populate any remaining required fields and click [Save].
  29. Click [Group By Vaccine] in the 'Immunization History' section.
  30. Validate that the 2 immunization administrations for "Immunization A" are grouped together.
Scenario 8: Medical Note - Order/Administer an Immunization in Single Workflow - Void Administration - Reconcile Inventory
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Immunization A)
  • "Immunization A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A" and the 'Manufacturer of Vaccine (MVX)' and 'Vaccine Code (CVX) fields but be populated. (Inventory A)
  • An outpatient program that is configured to be a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  4. Click [Add], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  5. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  6. Fill in any remaining required fields and click [Administer].
  7. Select "Facility" from the 'Provided By' field.
  8. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  9. Select the row for "Inventory A" and click [Select].
  10. Validate the fields in the 'Administration Details' section are all accurately populated.
  11. Fill in any remaining required fields and click [Save].
  12. Validate the 'Pending Administrations' field does not contain a row for "Immunization A".
  13. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
  14. Click the ellipses under the 'Action' column for "Immunization A" and click [Void].
  15. Populate the 'Comments' field and click [Save].
  16. Validate the 'Immunization History' field still contains a row for "Immunization A" and that the 'Status' column shows "Voided".
  17. Access the 'Medication Inventory Management' form.
  18. Click [Adjust Inventory] and select the row for "Inventory A" from the 'Select Row' field.
  19. Validate that the 'Event Log' field contains a row for the previously given administration.
  20. Validate the 'Current Balance' is correctly calculated.
  21. Select 'Add to inventory' from the 'Event Type' field.
  22. Set the 'Quantity' field, such that when added to the current balance, the total is equal to the amount originally added to inventory.
  23. Click [Submit].
Scenario 9: Medical Note - Complete a Pending Immunization After a Note Is Finalized - Pediatric Full Workflow
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • The Other CWS Tabled Files '(74101) Inventory Location’ dictionary must contain at least one value. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • Two "Vaccination/Immunization" procedure-type service codes must be configured in the 'Service Codes' form. (Medication A and Medication B)
  • "Medication A" and "Medication B" must have a template defined in the 'Medication Inventory Management' form. (Template A and Template B)
  • In the 'Medication Inventory Management' form inventory for "Template A" and "Template B" must be received to "Location A". (Inventory A and Inventory B)
  • An outpatient program must exist that is configured as a "Primary Care Program". (Program A)
  • A client must have an active episode that is associated with "Program A" and is a pediatric patient. (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Primary Care' note.
  4. Select the ‘Document’ tab.
  5. Select ‘Immunizations’.
  6. Click [Add] and select "Medication A" from the 'Immunization Search' field.
  7. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  8. Fill in any remaining required fields and click [Order].
  9. Validate the 'Pending Administrations' field contains a row for "Medication A"
  10. Click [Add] and select "Medication B" from the 'Immunization Search' field.
  11. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template B".
  12. Fill in any remaining required fields and click [Administer].
  13. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  14. Select "Yes" for the 'Consent Obtained' radio button.
  15. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  16. Select "Facility" from the 'Provided By' field.
  17. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  18. Select the row for "Inventory B" and click [Select].
  19. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  20. Fill in any remaining required fields and click [Save].
  21. Expand the 'Immunization History' field and validate it contains a row for "Medication B" and that all columns are accurate.
  22. Populate any remaining required sections in the 'Document' tab.
  23. Select the ‘Finalize’ tab.
  24. Populate all required fields and click [Generate Note].
  25. Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
  26. Validate the 'Progress Note' is displayed and click [Accept], set the ‘Password’ field to the appropriate value, and click [Verify].
  27. Refresh Medical Note.
  28. Click [Add Note].
  29. Create a 'Primary Care' note.
  30. Select the 'Document' tab and navigate to the 'Immunization' section.
  31. Validate the 'Pending Administrations' field contains a row for "Medication A"
  32. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  33. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  34. Select "Yes" for the 'Consent Obtained' field.
  35. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  36. Select "Facility" from the 'Provided By' field.
  37. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  38. Select the row for "Inventory A" and click [Select].
  39. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  40. Populate all remaining required fields and click [Save].
  41. Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
Scenario 10: Medical Note - Administering an immunization when 'Inventory Management' is disabled
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Immunization A)
  • An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new 'Primary Care' note.
  3. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  4. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunization Search' field and click [Continue].
  5. Fill in any required fields and click [Administer].
  6. Select "Facility" from the 'Provided By' field.
  7. Fill in any remaining required fields and click [Save].
  8. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and all columns are correctly populated.
  9. Complete any remaining required sections in the 'Document' tab.
  10. Select the 'Finalize' tab and click [End Face-to-Face Time].
  11. Choose one of the options in the 'CPT Code Selected' field and click [Generate Note].
  12. Validate the 'Note Summary' field shows the correct information.
  13. Set the 'Completion Status' field to "Completed" and sign off on the note.
Scenario 11: Medical Note - Service Code Upload - Medication Administration and Vaccine/Immunization Procedure Types
Specific Setup:
  • A service code upload file must exist that contains two new service codes, one with "Vaccination/Immunization" and one with "Medication Administration" selected in the 'Procedure Type' field, and must be placed on the server where the application resides. (File A)
Steps
  1. Access the 'Service Code Upload Process' form.
  2. Click [Select File].
  3. Select and open "File A".
  4. Select "Compile" in the 'Compile or Post' field.
  5. Select "Yes" in the 'Override Existing Service Codes' field.
  6. Click [Submit].
  7. Validate a "Compiled completed" message is displayed and click [OK].
  8. Select "Post" in the 'Compile or Post' field and click [Submit].
  9. Validate a "Post completed" message is displayed and click [OK].
  10. Access the 'Service Codes' form.
  11. Select "Edit" in the 'Add New or Edit Existing' field.
  12. Search for and select the first service code created and ensure that "Yes" is selected in the 'Is This Service A Procedure' field and that "Vaccination/Immunization" is selected in the 'Procedure Type' field.
  13. Search for and select the second service code created and ensure that "Medication Administration" is selected in the 'Procedure Type' field.
Scenario 12: Medical Note - Receiving new inventory - Administering an In-Office Administration - Entering a 'Reaction'
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Access the 'Medication Inventory Management' form.
  2. Click [Template Definition] and select "Add New" from the 'Select Template Definition' field.
  3. Set the 'Service Code' field to "Medication A".
  4. Populate any remaining required fields and click [Submit].
  5. Click [Medication Definition] and select the previously made template from the 'Select Template' field.
  6. Select "Location A" from the 'Inventory Location' field.
  7. Set the 'Lot #' field to "72293".
  8. Set the 'Expiration Date' field to a future date.
  9. Set the 'Container Size' field to 50.
  10. Populate any remaining required fields and click [Submit].
  11. Click [Adjust Inventory] and set the 'Lot #' field to "72293"
  12. Validate the new medication definition is shown in the 'Inventory Items' field.
  13. Select the new medication definition from the 'Select Row' field.
  14. Select "Add to inventory" from the 'Event Type' field.
  15. Validate "Add (A)" is selected from the 'Impact' field and that the field is disabled.
  16. Set the 'Quantity' field to "50" and click [Submit] and close the form.
  17. Search for and select "Client A" and navigate to the 'Medical Note'.
  18. Click [Add Note] and create a new note.
  19. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  20. Click [Add], search for and select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  21. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on selections made in the "Template Definition" section of the 'Medication Inventory Management' form.
  22. Fill in any remaining required fields and click [Administer].
  23. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  24. Select the row for new medication definition and click [Select].
  25. Validate the 'Administration Details' section is correctly populated based on selections made in the "Medication Definition" section of the 'Medication Inventory Management' form.
  26. Populate any remaining required fields and click [Save].
  27. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  28. Click the ellipses under the 'Action' column for "Medication A" and click [Document Reaction].
  29. Set the 'Reaction' field to any value and click [Save].
  30. Click the ellipses under the 'Action' column for "Medication A" and click [View Details].
  31. Validate the details are read-only, that all fields are correctly populated and then click [Cancel].
  32. Access the 'Medication Inventory Management' form.
  33. Click [Adjust Inventory] and select the new medication definition from the 'Select Row' field.
  34. Validate that the 'Event Log' field contains a row for the previously given administration.
  35. Validate the 'Current Balance' is correctly calculated.
Scenario 13: Medical Note - Refuse medications that are listed in under the 'Pending Medications' sub-section of the 'In-Office Administrations' section. Confirm details in Progress Note.
Specific Setup:
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode associated with "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add], select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  5. Populate any required fields and click [Order].
  6. Validate the 'Pending Administrations' field contains a row for "Medication A".
  7. Click the ellipses under the 'Action' column for "Medication A" and click [Refuse].
  8. Select any value from the 'Refused Reason' field and click [Save].
  9. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  10. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that "Refused" is shown in the 'Status' column.
  11. Click the ellipses under the 'Action' column for "Medication A" and click [View Details].
  12. Validate the 'Refused Reason' field matches to what was previously selected and click [Cancel].
  13. Select the 'Finalize' tab and click [Generate Note].
  14. Validate that the 'Note Summary' field contains a section for In-Office Administrations and "Medication A" is listed and shows as "Refused".
Scenario 14: Medical Note - Cancel a medication that is listed in under the 'Pending Medications' sub-section of the 'In-Office Administrations' section.
Specific Setup:
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode associated with "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
  4. Click [Add], search for and select "Medication A" from the 'In-Office Administration Search' field and click [Continue].
  5. Populate any required fields and click [Order].
  6. Validate that a row for "Medication A" is listed in the 'Pending Immunizations' section.
  7. Click the ellipses under the 'Action' column for "Medication A" and click [Cancel].
  8. Validate the 'Cancel Pending Administration' dialog contains "Are you sure you want to cancel this pending administration? Canceling this will permanently remove this pending administration." and click [Continue].
  9. Populate the 'Comments' field and click [Save].
  10. Validate the 'Pending Administrations' field no longer contains a row for "Medication A".
  11. Expand the 'Administration History' field and validate it does not contain a row for "Medication A".
  12. Click [Select Note] and then click [Delete] for the newly created note.
  13. Validate the 'Delete Note' dialog contains "Are you sure you want to delete this draft note? Please make sure to void any administrations or procedures completed during the visit, as necessary."
  14. Click [Delete Note] and validate a 'Start' button now shows for the newly created note.
Scenario 15: Medical Note - Complete In-Office Administration - Delete Note - Void Administration - Reconcile Inventory
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • "Medication A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A". (Inventory A)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  4. Click [Add], search for and select "Medication A" from the 'In-Office Administrations Search' field and click [Continue].
  5. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  6. Fill in any remaining required fields and click [Administer].
  7. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  8. Select the row for "Inventory A" and click [Select].
  9. Populate any remaining required fields and click [Save].
  10. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  11. Click [Select Note] and then click [Delete] for the newly created note.
  12. Validate the 'Delete Note' dialog contains "Are you sure you want to delete this draft note? Please make sure to void any administrations or procedures completed during the visit, as necessary.".
  13. Click [Delete Note] and validate an error message is displayed at the top of the medical note stating "Completed procedures/administrations that updated medication inventory must be voided first before the visit can be deleted.".
  14. Select the 'Document' tab and then navigate to the 'In-Office Administrations' section.
  15. Expand the 'Administration History' field, click the ellipses under the 'Action' column for "Medication A" and click [Void].
  16. Populate the 'Comments' field and click [Save].
  17. Validate a passive alert is displayed at the top of the document tab stating "Void Administration: Voiding an administration does not update inventory. Please reconcile your inventory as needed."
  18. Validate the 'Status' column shows "Voided" for "Medication A".
  19. Click [Select Note] and then click [Delete] for the newly created note.
  20. Validate the 'Delete Note' dialog contains "Are you sure you want to delete this draft note? Please make sure to void any administrations or procedures completed during the visit, as necessary." and click [Delete Note].
  21. Access the 'Medication Inventory Management' form.
  22. Click [Adjust Inventory] and select the row for "Inventory A" from the 'Select Row' field.
  23. Validate that the 'Event Log' field contains a row for the previously given administration.
  24. Validate the 'Current Balance' is correctly calculated.
  25. Select 'Add to inventory' from the 'Event Type' field.
  26. Set the 'Quantity' field, such that when added to the current balance, the new balance will be equal to the amount prior to the administration and click [Submit].
Scenario 16: Medical Note - Administering a Pediatric Immunization when 'Inventory Management' is enabled
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • Two 'Vaccination/Immunization' procedure-type service codes must be configured in the 'Service Codes' form. (Immunization A) (Immunization B)
  • "Immunization A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A" and the 'Manufacturer of Vaccine (MVX)' and 'Vaccine Code (CVX)' fields must be populated. (Inventory A)
  • An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
  • "Client A" must be under the age of 19.
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Navigate to the 'Immunizations' section of the Facesheet.
  3. Click [Add] and then [Historical Immunization Record].
  4. Select any immunization listed in the 'Historical Immunization Record Search' field.
  5. Fill out any required fields and click [Save].
  6. Validate the 'Immunization History' section contains a row for the new historical immunization record.
  7. Click [Add Note] and create a 'Primary Care' note.
  8. Select the 'Document' tab and then navigate to the 'Immunization' section.
  9. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunizations Search' field and click [Continue].
  10. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  11. Fill in any remaining required fields and click [Order].
  12. Validate the 'Pending Immunizations' field contains a row for "Immunization A"
  13. Click the ellipses under the 'Action' column for "Immunization A" and click [Edit].
  14. Clear the 'Diagnosis' field, enter in a new value and click [Update].
  15. Click the ellipses under the 'Action' column for "Immunization A" and click [Administer].
  16. Validate the 'Diagnosis' field contains the updated value.
  17. Validate the following fields, restricted to pediatric clients only, show and are required:
  18. 'Consent Obtained'.
  19. 'VFC Eligibility Code'.
  20. 'Funding Source'.
  21. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  22. Select the row for "Inventory A" and click [Select].
  23. Fill in any remaining required fields and click [Save].
  24. Validate the 'Pending Immunizations' field no longer contains a row for "Immunization A".
  25. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
  26. Click the ellipses under the 'Action' column for "Immunization A" and click [Document Reaction].
  27. Populate the 'Reaction' field and click [Save].
  28. Click the ellipses under the 'Action' column for "Immunization A" and click [View Details].
  29. Validate all fields are correctly populated and disabled and click [Cancel].
  30. Click [Add] and then [Order Immunizations], select "Immunization B" from the 'Immunizations Search' field and click [Continue].
  31. Populate all required fields and click [Order].
  32. Select the 'Finalize' tab and click [Generate Note].
  33. Validate the 'Note Summary' field contains a section for pending immunizations and has "Immunization B" listed.
  34. Validate the 'Note Summary' field contains a section for administered in-office immunizations and has "Immunization A" listed.
  35. Validate the 'Note Summary' field does not contain the new Historical Immunization Record.
  36. Select the 'Document' tab and then navigate to the 'Immunization' section.
  37. Click the ellipses under the 'Action' column for "Immunization B" and click [Cancel].
  38. Validate the 'Cancel Pending Administration' dialog appears and contains: "Are you sure you want to cancel this pending administration? Canceling this will permanently remove this pending administration."
  39. Click [Continue], populate the 'Comments' field and click [Save].
  40. Select the 'Finalize' tab and click [Generate Note].
  41. Validate the 'Note Summary' field does not contain a section for pending immunizations.
Scenario 17: Medical Note - Administering a Pediatric Immunization when 'Inventory Management' is disabled
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • An Outpatient program must exist that is configured as a 'Primary Care' program. (Program A)
  • A client must have an active episode associated with "Program A". (Client A)
  • "Client A" must be 18 years of age or younger.
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Primary Care' note.
  4. Select the 'Document' tab and then navigate to the 'Immunization' section.
  5. Populate all required fields and click [Order].
  6. Validate the 'Pending Administrations' field contains a row for "Medication A".
  7. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  8. Select "Yes" for the 'Consent Obtained' radio button.
  9. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  10. Select "Other" from the 'Provided By' field.
  11. Populate all required fields and click [Save].
  12. Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  13. Click the ellipses under the 'Action' column for "Medication B" and click [Document Reaction].
  14. Select any value for the 'Reaction' field and click [Save].
  15. Click the ellipses under the 'Action' column for "Medication B" and click [View Details].
  16. Validate the 'Reaction' field contains the correct value and click [Close]
Scenario 18: Medical Note - Add Historical Immunization Record - Validate through 'Client Health Maintenance' form
Specific Setup:
  • A client must have an active episode. (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Navigate to the 'Immunizations' section of the Facesheet.
  3. Click [Add] and then [Historical Immunization Record].
  4. Select any immunization listed in the 'Historical Immunization Record Search' field.
  5. Fill out any required fields and click [Save].
  6. Validate the 'Immunization History' section contains a row for the new historical immunization record.
  7. Access the 'Client Health Maintenance' form.
  8. Search for and select "Client A" from the 'Client ID' field.
  9. Click [List Immunizations] and validate the 'Immunizations History and Alerts' report is launched.
  10. Validate the 'Immunization History' section contains data for the new historical immunization record and click [Close Report].
  11. Click [Update] and then [New Row].
  12. Populate the 'Vaccine', 'Dose', 'Provided By' and 'Date' cells and click [Save].
  13. Navigate to the 'Medical Note'.
  14. Navigate to the 'Immunizations' section of the Facesheet.
  15. Validate the 'Immunization History' section contains a row for both new immunization records.
Scenario 19: Medical Note - Add Historical Records - In Office Administration
Specific Setup:
  • A procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • An Outpatient program must exist. (Program A)
  • A client must have an active episode associated with "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Psychiatry' note.
  4. Select the 'Document' tab and then navigate to the 'Procedure' section.
  5. Click [Add] and select "Medication A" from the 'Procedure Search' field.
  6. Select ‘Diagnosis’ and enter a diagnosis.
  7. Click 'Complete' field.
  8. Click 'Routine' field.
  9. Populate all remaining required fields and click [Save].
  10. Validate the 'Current Procedures' field contains a row for "Medication A".
  11. Access the 'Service Codes' form.
  12. Select "Edit" in the 'Add New or Edit Existing' field.
  13. Search for and select "Medication A" and select "Medication Administration" in the 'Procedure Type' field.
  14. Click [Submit].
  15. Validate a message is displayed stating "Service Codes has completed. Do you wish to return to form?" and click [Yes].
  16. Refresh 'Medical Note'.
  17. Click [Select Note] and click [Edit].
  18. Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
  19. Expand the 'Administration History' field.
  20. Validate the 'Historical Records' section is displayed and contains "Medication A".
Scenario 20: Medical Note - In-Office Administration - ToDo's - Administer and refusal
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • Two 'Medication Administration' procedure-type service codes must be configured in the 'Service Codes' form. (Medication A and Medication B)
  • An outpatient program must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
  • Two users must exist in the application. (User A and User B)
  • "User A" is configured as a "Nurse" and "User B" is configured as a "Provider".
  • "User A" must be logged into the application.
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a new note.
  3. Select the 'Document' tab and then navigate to the 'In-Office Administration' section.
  4. Click [Add] and select "Medication A" from the 'In-Office Administration Search' field.
  5. Populate any required fields and click [Order].
  6. Validate the 'Pending Administrations' field contains a row for "Medication A".
  7. Click [Add] and select "Medication B" from the 'In-Office Administration Search' field.
  8. Populate any required fields and click [Order].
  9. Validate the 'Pending Administrations' field contains a row for "Medication B".
  10. Click [Send To Do].
  11. Set "User B" in the 'To-Do Recipient'.
  12. Set the 'Notes' field to any value and click [Send].
  13. Log out of the application and log back in as "User B".
  14. Access the 'My To Do's' widget.
  15. Select "Client A" from the 'Additional ToDos' list and click [Review To Do Item].
  16. Click 'In-Office Administrations'.
  17. Validate the 'Pending Administrations' field contains a row for "Medication A".
  18. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  19. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and disabled.
  20. Populate any required fields and click [Save].
  21. Expand the 'Administration History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  22. Click the ellipses under the 'Action' column for "Medication B" and click [Refuse].
  23. Select any value in the 'Refused Reason' field and click [Save].
  24. Expand the 'Administration History' field and validate it contains a row for "Medication B" with a status of 'Refused'.
Scenario 21: Medical Note - Inventory Management Enabled - Full Immunization Work Flow
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • Two 'Vaccination/Immunization' procedure-type service codes must be configured in the 'Service Codes' form. (Medication A and Medication B)
  • "Medication A" and "Medication B" must have a template defined in the 'Medication Inventory Management' form. (Template A and Template B)
  • In the 'Medication Inventory Management' form inventory for "Template A" and "Template B" must be received to "Location A". (Inventory A and Inventory B)
  • An Outpatient program must exist that is configured as a primary care program. (Program A)
  • A client must have an active episode associated with "Program A". (Client A)
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note] and create a 'Primary Care' note.
  3. Select the ‘Document’ tab.
  4. Enter a value in the ‘Chief Complaint’ field.
  5. Select ‘HPI’ and add a value along with symptoms.
  6. Select ‘Physical Exam’ and select the ‘Constitutional’ tab.
  7. Check off the appropriate values.
  8. Select ‘Diagnosis’ and enter a diagnosis.
  9. Select ‘Immunizations’.
  10. Click [Add] and select "Medication A" from the 'Immunization Search' field.
  11. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  12. Fill in any remaining required fields and click [Order].
  13. Validate the 'Pending Administrations' field contains a row for "Medication A"
  14. Click [Add] and select "Medication B" from the 'Immunization Search' field.
  15. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template B".
  16. Fill in any remaining required fields and click [Administer].
  17. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  18. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  19. Select the row for "Inventory B" and click [Select].
  20. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  21. Fill in any remaining required fields and click [Save].
  22. Expand the 'Immunization History' field and validate it contains a row for "Medication B" and that all columns are accurate.
  23. Click the ellipses under the 'Action' column for "Medication B" and click [Document Reaction].
  24. Select any value for the 'Reaction' field and click [Save].
  25. Click the ellipses under the 'Action' column for "Medication B" and click [View Details].
  26. Validate the 'Reaction' field contains the correct value and click [Close].
  27. Select the ‘Finalize’ tab.
  28. Populate all required fields and click [Generate Note].
  29. Validate the ‘Note Summary’ is displayed and contains the appropriate information and click [Sign Off].
  30. Validate the Document is displayed and click [Accept], set the ‘Password’ field to the appropriate value and click [Verify].
  31. Refresh Medical Note.
  32. Click [Add Note].
  33. Select "Primary Care" from the 'Appointment/Note Workflow' field.
  34. Select "Main Street Center" from the 'Site' field.
  35. Select "Program A" from the 'Service Program' field.
  36. Search for and select "Service Code A" from the 'Service Code' field.
  37. Fill out any remaining required fields and click [Save].
  38. Select the 'Document' tab and then navigate to the 'Immunization' section.
  39. Validate the 'Pending Administrations' field contains a row for "Medication A"
  40. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  41. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  42. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  43. Select the row for "Inventory A" and click [Select].
  44. Validate the 'Lot Number', 'Manufacturer', 'Expiration Date', and 'NDC' are all correctly populated and disabled.
  45. Fill in any remaining required fields and click [Save].
  46. Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  47. Select the 'Facesheet' tab and then navigate to the 'Immunization' section.
  48. Validate "Medication A" and "Medication B" are displayed.
  49. Select the 'Document' tab and then navigate to the 'Immunization' section.
  50. Void the administrations of "Medication A" and "Medication B".
  51. Refresh Medical Note.
  52. Click [Select Note] and click [Delete].
  53. Validate the 'Delete Note' dialog is displayed and contains "Are you sure you want to delete this draft note. Please make sure to void any administrations or procedures completed during the visit, as necessary."
  54. Click [Delete Note].
Scenario 22: Medical Note - Order an Immunization as "Provider" - Edit/Administer as "Nurse"
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "Y".
  • There must be at least one value in the Other CWS Tabled Files ‘(74101) Inventory Location’ dictionary. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Immunization A)
  • "Immunization A" must have a template defined in the 'Medication Inventory Management' form. (Template A)
  • In the 'Medication Inventory Management' form, inventory for "Template A" must be received to "Location A" and the 'Manufacturer of Vaccine (MVX)' and 'Vaccine Code (CVX)' fields must be populated. (Inventory A)
  • An outpatient program configured as a 'Primary Care' program in the 'Program Maintenance' form must exist. (Program A)
  • A client must have an active episode in "Program A". (Client A)
  • Two users must exist. (User A) (User B).
  • "User A" who is configured as a "Provider".
  • "User B" who is configured as a "Nurse".
Steps
  1. Log into the application as "User A".
  2. Search for and select "Client A" and navigate to the 'Medical Note'.
  3. Click [Add Note] and create a 'Primary Care' note.
  4. Select the 'Document' tab and then navigate to the 'Immunization' section.
  5. Click [Add] and then [Order Immunizations], select "Immunization A" from the 'Immunizations Search' field and click [Continue].
  6. Validate the 'Dose', 'Unit', and 'Route' fields automatically populate based on the entries made in "Template A".
  7. Fill in any remaining required fields and click [Order].
  8. Validate the 'Pending Immunizations' field contains a row for "Immunization A" and click [Save Draft].
  9. Log out of the application and then log in as "User B".
  10. Search for and select "Client A" and navigate to the 'Medical Note'.
  11. Click [Select Note] and select the newly created 'Primary Care' note.
  12. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  13. Validate the 'Pending Immunizations' field contains a row for "Immunization A".
  14. Click the ellipses under the 'Action' column for "Immunization A" and click [Administer].
  15. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated and that all fields are disabled.
  16. Validate the 'Entered By' and 'Ordered By' fields contains "User A" and the 'Administered By' field contains "User B".
  17. Select "Facility" from the 'Provided By' field.
  18. Click the 'Lot Number Search' button and validate the 'Lot Number Manager' dialog is launched.
  19. Select the row for "Inventory A" and click [Select].
  20. Validate all fields in the 'Administration Details' section are populated correctly.
  21. Fill in any remaining required fields and click [Save].
  22. Validate the 'Pending Immunizations' field no longer contains a row for "Immunization A".
  23. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
  24. Log out of the application and then log in as "User A".
  25. Search for and select "Client A" and navigate to the 'Medical Note'.
  26. Click [Select Note] and select the 'Primary Care' note.
  27. Select the 'Document' tab and then navigate to the 'Immunizations' section.
  28. Validate the 'Pending Immunizations' field no longer contains a row for "Immunization A".
  29. Expand the 'Immunization History' field and validate it contains a row for "Immunization A" and that all columns are accurate.
Scenario 23: Medical Note - Pediatric Immunization - ToDo's - Administer and refusal
Specific Setup:
  • The 'Avatar CWS->Medication Inventory Management->->->->Enable Medication Inventory Management' registry setting must be set to "N".
  • The Other CWS Tabled Files '(74101) Inventory Location’ dictionary must contain at least one value. (Location A)
  • Please log out of the application and log back in after completing the above configuration.
  • A generic 'Evaluation Management' service code must be configured in the 'Service Codes' form. (Service Code A)
  • A 'Medication Administration' procedure-type service code must be configured in the 'Service Codes' form. (Medication A)
  • A 'Vaccination/Immunization' procedure-type service code must be configured in the 'Service Codes' form. (Medication B)
  • An outpatient program must exist that is configured as a 'Primary Care' program. (Program A)
  • A client must have an active episode associated with "Program A" and is pediatric patient. (Client A)
  • Two users must exist in the application: One who is configured as a "Nurse" (User A) and one who is configured as a "Provider". (User A and User B).
  • "User A" must be logged into the application.
Steps
  1. Search for and select "Client A" and navigate to the 'Medical Note'.
  2. Click [Add Note].
  3. Create a 'Primary Care' note.
  4. Select the 'Document' tab and then navigate to the 'Immunization' section.
  5. Click [Add] and select "Medication A" from the 'Immunization Search' field.
  6. Populate all required fields and click [Order].
  7. Validate the 'Pending Administrations' field contains a row for "Medication A".
  8. Click [Add] and select "Medication B" from the 'Immunization Search' field.
  9. Populate all required fields and click [Order].
  10. Validate the 'Pending Administrations' field contains a row for "Medication B".
  11. Click [Send To Do].
  12. Set "User A" in the 'To-Do Recipient'.
  13. Set the 'Notes' field to any value and click [Send].
  14. Log out of the application and log back in as "User B".
  15. Access the 'My To Do's' widget.
  16. Select "Client A" from the 'Additional ToDos' list and click [Review To Do Item].
  17. Select the 'Immunization' section.
  18. Validate the 'Pending Administrations' field contains a row for "Medication A".
  19. Click the ellipses under the 'Action' column for "Medication A" and click [Administer].
  20. Validate, in the first section, the 'Dose', 'Unit', and 'Route' fields are correctly populated with the updated values and that all fields are disabled.
  21. Select "Yes" for the 'Consent Obtained' radio button.
  22. Select "Not VFC eligible" from the 'VFC Eligibility Code' field.
  23. Select "Facility" from the 'Provided BY' field.
  24. Populate all required fields and click [Save].
  25. Expand the 'Immunization History' field and validate it contains a row for "Medication A" and that all columns are accurate.
  26. Click the ellipses under the 'Action' column for "Medication B" and click [Refuse].
  27. Select any value for the 'Refused Reason' field and click [Save].
  28. Expand the 'Immunization History' field and validate it contains a row for "Medication B" with a status of "Refused".
Topics
• Medical Note • NX • Service Code • To Dos
Update 18 Summary | Details
Pro-Rated Feed
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
  • Service Fee/Cross Reference Maintenance
  • Dictionary Update (PM)
  • Post Residential/Inpatient Worklist
  • Client Ledger
  • Discharge
  • Financial Eligibility
  • Leaves
  • Guarantors/Payors
Scenario 1: Validate Pro-Rated Fees Calculation - Client without leave or discharge
Specific Setup:
  • Registry Settings:
  • The following registry setting has a value of '2', at a minimum: Avatar PM->System Maintenance->Service Code Maintenance->->->Additional Service Fee Configuration Fields.
  • The following registry setting has a value of '5': Avatar PM->Services->Inpatient/Residential->->->Number Of Daily Charge Codes.
  • Guarantors/Payors 1 is an active guarantor.
  • Service Codes:
  • Service Code 1: Is an active service code that will be used for pro-rated services room and board charges.
  • Service Code 2: Is an active service code that will be used for pro-rated services daily charge (1).
  • Service Code 3: Is an active service code that will be used for pro-rated services daily charge (2).
  • Service Code 4: Is an active service code that will be used for pro-rated services daily charge (3).
  • Service Code 5: Is an active service code that will be used for pro-rated services daily charge (4).
  • Service Code 6: Is an active service code that will be used for pro-rated services daily charge (5).
  • Service Fee/Cross Reference Maintenance:
  • Service Code 1 - Service Code 6:
  • From Date = desired date.
  • Fee = desired amount, which is distributed across the monthly services. Note each value.
  • UB-94 Revenue Code = desired value.
  • Fee type = Monthly.
  • Pro-Rate Fee For = desired values.
  • Pro-Rated Fee Calculation = Fee/Monthly Days.
  • Client:
  • Is admitted to an inpatient program on or after the earliest 'Service Fee/Cross Reference Maintenance', 'From Date'. Note the ‘Unit’ the client is assigned to. Client has not been placed on leave or discharged during the month.
  • Has a 'Financial Eligibility' record for Guarantors/Payors 1.
  • Equations are used for fee verification based on the value in 'Pro-Rated Fee Calculation'.
  • The value of 'Pro-Rated Fee Calculation' is 'Fee/Monthly Days'. The equation is: the 'Fee' divided by the number of days in the month, times the number of valid days, divided by the number of days in the month.
  • Example 1: Fee is 350.00. Days in month = 31. Valid days = 31. 350/31 = 11.29 for days 1-30, and 11.30 for day 31.
  • Example 2: Fee is 120.00. Days in month = 30. Valid days = 15. 120.00/30x15/30 = 2.00 for the valid days.
Steps
  1. Open ‘Compile Residential/Inpatient Charges’.
  2. Select ‘Individual’ in ‘Individual Or All Units’.
  3. Select desired Unit in ‘Select Unit(s)’.
  4. Set the ‘Compile Charges From Date’ to desired value.
  5. Set the ‘Compile Charges Through Date’ to desired value.
  6. Select ‘Yes’ in ‘Do You Wish To Recreate The Residential/Inpatient Worklist’
  7. Click [Process].
  8. Validate that the report fees are correct for each service code, ensuring that at a minimum the first and last page of the report are verified. Calculate the fees to verify that the fee in ‘Service Fee/Cross Reference Maintenance’ is correct for the valid number of days in the month.
  9. Open ‘Post Residential/Inpatient Worklist’.
  10. Select ‘Individual’ in ‘Individual Or All Units’.
  11. Select desired Unit in ‘Select Unit(s)’.
  12. Set the ‘Post Charges From Date’ to desired value.
  13. Set the ‘Post Charges Through Date’ to desired value.
  14. Click [Process].
  15. Validate that the report fees are the same as above.
  16. If desired, open ‘Client Ledger’ for the client and verify the fees for the date range and services.
Scenario 2: Validate Pro-Rated Fees Calculation - Client with leave only & Client with leave & discharge
Specific Setup:
  • Registry Settings:
  • The following registry setting has a value of '2', at a minimum: Avatar PM->System Maintenance->Service Code Maintenance->->->Additional Service Fee Configuration Fields.
  • The following registry setting has a value of '5': Avatar PM->Services->Inpatient/Residential->->->Number Of Daily Charge Codes.
  • Guarantors/Payors 1 is an active guarantor.
  • Service Codes:
  • Service Code 1: Is an active service code that will be used for pro-rated services room and board charges.
  • Service Code 2: Is an active service code that will be used for pro-rated services daily charge (1).
  • Service Code 3: Is an active service code that will be used for pro-rated services daily charge (2).
  • Service Code 4: Is an active service code that will be used for pro-rated services daily charge (3).
  • Service Code 5: Is an active service code that will be used for pro-rated services daily charge (4).
  • Service Code 6: Is an active service code that will be used for pro-rated services daily charge (5).
  • Service Fee/Cross Reference Maintenance:
  • Service Code 1 - Service Code 6:
  • From Date = desired date.
  • Fee = desired amount, which is distributed across the monthly services. Note each value.
  • UB-94 Revenue Code = desired value.
  • Fee type = Monthly.
  • Pro-Rate Fee For = desired values. If 'Missing Service Code' is not selected in the field, leave days will be counted as valid days.
  • Pro-Rated Fee Calculation = Fee/Monthly Days.
  • Dictionary Update:
  • Client - Type of Leave From (757):
  • Extended Dictionaries:
  • Chargeable Leave Y/N = Y.
  • Room And Board Billing Code Override = a Room & Board Code that is not Service Code 1.
  • Client:
  • Is admitted to an inpatient program on or after the earliest 'Service Fee/Cross Reference Maintenance', 'From Date'. Note the ‘Unit’ the client is assigned to. The service codes noted above are used in the 'Inpatient/Partial/Day Treatment' section of the form.
  • Client has a billable leave during the month. Note the number of leave days. The client has not been discharged during the month.
  • Has a 'Financial Eligibility' record for Guarantors/Payors 1.
  • Equations are used for fee verification based on the value in 'Pro-Rated Fee Calculation'.
  • The value of 'Pro-Rated Fee Calculation' is 'Fee/Monthly Days'. The equation is: the 'Fee' divided by the number of days in the month, times the number of valid days, divided by the number of days in the month.
  • Example 1: Fee is 350.00. Days in month = 31. Valid days = 31. 350/31 = 11.29 for days 1-30, and 11.30 for day 31.
  • Example 2: Fee is 120.00. Days in month = 30. Valid days = 15. 120.00/30x15/30 = 2.00 for the valid days.
Steps
  1. Open ‘Compile Residential/Inpatient Charges’.
  2. Select ‘Individual’ in ‘Individual Or All Units’.
  3. Select desired Unit in ‘Select Unit(s)’.
  4. Set the ‘Compile Charges From Date’ to desired value.
  5. Set the ‘Compile Charges Through Date’ to desired value.
  6. Select ‘Yes’ in ‘Do You Wish To Recreate The Residential/Inpatient Worklist’
  7. Click [Process].
  8. Validate that the report fees are correct for each service code, ensuring that at a minimum the first and last page of the report are verified. Calculate the fees to verify that the fee in ‘Service Fee/Cross Reference Maintenance’ is correct for the valid number of days in the month.
  9. Open ‘Post Residential/Inpatient Worklist’.
  10. Select ‘Individual’ in ‘Individual Or All Units’.
  11. Select desired Unit in ‘Select Unit(s)’.
  12. Set the ‘Post Charges From Date’ to desired value.
  13. Set the ‘Post Charges Through Date’ to desired value.
  14. Click [Process].
  15. Validate that the report fees are the same as above.
  16. If desired, open ‘Client Ledger’ for the client and verify the fees for the date range and services.
  17. In the next month, place the client on a billable leave on desired date. Return the client from leave on desired date. Discharge the client at least one day after returning from leave.
  18. Repeat steps 1-17 for the new month of services.
Topics
• Pro Rated Fee
Update 22 Summary | Details
Payment Acknowledgement-check/EFT
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Payment Acknowledgement
Scenario 1: Payment Acknowledgement - With a particular check/EFT - 835
Specific Setup:
  • Registry Setting:
  • ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
  • "Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged" has a 'Registry Setting Value that contains '1,4,5,7'
  • Dictionary Update:
  • Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
  • Other Table Files: (5522) Account - contains dictionary codes, dictionary values, and extended dictionary values.
  • For the specific Dictionary code (101), set the value for the Extended dictionary value- 'Show in Various Client posting Screens' as 'YES'.
  • Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
  • Posting/Adjustment Codes Definitions: Definitions exist for ‘Payment’.
  • The definitions may have a value in the ‘Payment Acknowledgement Type’ field.
  • All ‘Payment’ definitions will be available in the ‘Payment Acknowledgement’ form.
  • 835 file setup:
  • For any Clients, create an 835 file (File A) to be used for compiling in the '835 Health Care Claim Payment/Advice' form.
  • Save the 835 file in the network location which is configured in the 'Facility Defaults' - '835 Import/Export File Configuration' - 'Process File Path' field.
  • Using the '835 Health Care Claim Payment/Advice' form, Load and Compile the 835 file.
Steps
  1. Open the '835 Health Care Claim Payment/Advice' form.
  2. Set the ‘Options’ field to ‘Post File’.
  3. Select the 'Posting Date'.
  4. Select the 'Date of Receipt'.
  5. Select the Compiled 835 file (File A) from the 'Select File' dropdown.
  6. Validate that the field 'File Description' is shown with the correct value from the file.
  7. Validate that the 'Check / EFT #' field is shown with all the related records along with the check/EFT numbers and the status.
  8. Verify that all the rows are shown with the status tag "Unacknowledged".
  9. Select [Discard].
  10. Open the ‘Payment Acknowledgement’ form.
  11. Verify that ‘Action’ defaults to ‘New’.
  12. Verify that ‘Transaction Number’ is read-only.
  13. Verify that ‘Entered By’ is read-only and defaults to the signed-in user.
  14. Enter the desired value in ‘Batch Number’.
  15. Select the desired ‘Posting Code’. All payment posting codes will be displayed.
  16. Enter a value in ‘Check/EFT Number’ that is different from the one in the 835 file record.
  17. Enter the desired value in ‘Amount’.
  18. Select the same Guarantor used in the 835 file in the ‘Guarantor’ field.
  19. Enter the desired value in ‘Name/Source’.
  20. Enter the desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
  21. Enter the desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
  22. Enter the desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
  23. Select the desired ‘Treatment Service’.
  24. Select the ‘Category’ that we configured with the extended dictionary value.
  25. Enter the desired value in ‘Bank Ref #’.
  26. Enter the desired value in ‘Comments’.
  27. Click [File].
  28. Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is <number>. Do you need to continue to Post Payment Accounting Entry?.
  29. Note down the Transaction Number.
  30. Clicking [Yes] will continue to the Post Payment Accounting Entry section or selecting [No] will remain in the ‘Payment Acknowledgement’ section.
  31. Click [Yes].
  32. Click [New Row] in ‘Post Payment Accounting Entry’.
  33. Validate that the grid becomes enabled.
  34. Select the desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
  35. Select the desired ‘Program’.
  36. Select the ‘Account 1’ that we configured with the extended dictionary value.
  37. Select the desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
  38. Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgement’.
  39. Select the desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’ or the ‘Deposit Date’.
  40. If desired, enter a ‘Comment’.
  41. Click [File].
  42. The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
  43. Click [No].
  44. Select [Discard].
  45. Open the '835 Health Care Claim Payment/Advice' form.
  46. Set the ‘Options’ field to ‘Post File’.
  47. Select the 'Posting Date'.
  48. Select the 'Date of Receipt'.
  49. Select the Compiled 835 file (File A) from the 'Select File' dropdown.
  50. Validate that the field 'File Description' is shown with the correct value from the file.
  51. Validate that the 'Check / EFT #' field is shown with all the related records along with the check/EFT numbers and the status.
  52. Verify that still all the rows are shown with the status tag "Unacknowledged".
  53. Select [Discard].
  54. d
  55. Open the ‘Payment Acknowledgement’ form.
  56. Verify that ‘Action’ defaults to ‘New’.
  57. Verify that ‘Transaction Number’ is read-only.
  58. Verify that ‘Entered By’ is read-only and defaults to the signed-in user.
  59. Enter the desired value in ‘Batch Number’.
  60. Select the desired ‘Posting Code’. All payment posting codes will be displayed.
  61. Enter the value in ‘Check/EFT Number’ that is the same as the 835 file record.
  62. Enter the desired value in ‘Amount’.
  63. Select the same Guarantor used in the 835 file in the ‘Guarantor’ field.
  64. Enter the desired value in ‘Name/Source’.
  65. Enter the desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
  66. Enter the desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
  67. Enter the desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
  68. Select the desired ‘Treatment Service’.
  69. Select the ‘Category’ that we configured with the extended dictionary value.
  70. Enter the desired value in ‘Bank Ref #’.
  71. Enter the desired value in ‘Comments’.
  72. Click [File].
  73. Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is <number>. Do you need to continue to Post Payment Accounting Entry?.
  74. Note down the Transaction Number.
  75. Clicking [Yes] will continue to the Post Payment Accounting Entry section or selecting [No] will remain in the ‘Payment Acknowledgement’ section.
  76. Click [Yes].
  77. Click [New Row] in ‘Post Payment Accounting Entry’.
  78. Validate that the grid becomes enabled.
  79. Select the desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
  80. Select the desired ‘Program’.
  81. Select the ‘Account 1’ that we configured with the extended dictionary value.
  82. Select the desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
  83. Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgement’.
  84. Select the desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’ or the ‘Deposit Date’.
  85. If desired, enter a ‘Comment’.
  86. Click [File].
  87. The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
  88. Click [No].
  89. Select [Discard].
  90. Open the '835 Health Care Claim Payment/Advice' form.
  91. Set the ‘Options’ field to ‘Post File’.
  92. Select the 'Posting Date'.
  93. Select the 'Date of Receipt'.
  94. Select the Compiled 835 file (File A) from the 'Select File' dropdown.
  95. Validate that the field 'File Description' is shown with the correct value from the file.
  96. Validate that the 'Check / EFT #' field is shown with all the related records along with the check/EFT numbers and the status.
  97. Verify that the row with the respective check/EFT number used in Step 61 is now shown with the status tag "Acknowledged".
  98. Select [Discard].
Payment Acknowledgement-Acknowledging payments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Deposit Entry
  • Close Accounting Period
  • Payment Acknowledgement
  • Client Ledger
Scenario 1: Payment Acknowledgement : Post Front Office and myHP Payments section
Specific Setup:
  • Registry Settings:
  • Enable Payment Acknowledgement Registry Setting Value: Y.
  • Prevent Posting Payments Unless Payment: 5.
  • Admission:
  • Create a client with an active diagnosis and financial eligibility. (Client A)
  • Client charge input:
  • Assign a few services to Client A.
  • Closed Accounting Period: Note the last closed accounting period.
Steps
  1. Open 'Deposit Entry.
  2. Enter 'Date of receipt or adjustment'.
  3. Select 'Client A' in 'Client id'.
  4. Select 'Episode number'.
  5. Select 'Service code'.
  6. Select 'Guarantor'.
  7. Enter 'Amount to post'.
  8. Select 'Posting code'.
  9. Click 'Submit'.
  10. Verify the crystal report is generated
  11. Query the system table "SYSTEM.unacknowledged_payments" and validate that there is a value captured and stored for the column(s) 'data_entry_date' and 'data_entry_time' for 'Client A'.
  12. Open 'Close Accounting Period'.
  13. Validate the date of 'Month/Year Of Close For Charge/Payment Postings'.
  14. Open 'Payment Acknowledgement'.
  15. Click on the 'Post Front Office and myHP Payments' item.
  16. Enter 'Payment Collection Date'.
  17. Select 'Treatment Service'.
  18. Select 'Type' as 'Both'.
  19. Click on the 'Review button'.
  20. Select the record that we created by using the Deposit entry form.
  21. Enter today's date in 'Deposit date'.
  22. Enter desired values in all required fields.
  23. Click on the 'Post' button.
  24. Open 'Client ledger'.
  25. Validate the posted amount displayed in the crystal report.
  26. Open 'Payment Acknowledgement'.
  27. Click on the 'Post Front Office and myHP Payments' item.
  28. Enter 'Payment Collection Date'.
  29. Select 'Treatment Service'.
  30. Select 'Type' as 'Both'.
  31. Click on the 'Review button'.
  32. Update the record's posting code from the one which is on file to anything designated to 'Credit Card Payment'.
  33. Leave the 'Name On Card' field blank.
  34. Select [Save].
  35. Select [Yes].
  36. Validate that the confirm popup shows up to warn that 'Name on Card is required for Credit Card Posting Code. You can re-enter the grid to update the above rows. Or, if you choose to continue and click 'Post' the above rows will not be posted. All other rows without issues will post.'
  37. Select [OK].
  38. Select [Discard].
  39. Click [Yes].
Payment Acknowledgement-Post Front Office and myHP Payments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • NX Credit Card
  • Dynamic Form - CardConnect Payment
  • Payment Acknowledgement
  • Client Ledger
Scenario 1: Payment Acknowledgement - 'Check In' process of the Scheduling Calendar - 'Name on Card' field validation
Specific Setup:
  • Registry Setting:
  • The 'Enable Payment Acknowledgement' registry setting is enabled.
  • The 'Prevent Posting Payments Unless Payment has been Acknowledged' registry setting includes a value of '4' at minimum.
  • User Definition:
  • The user has access to the 'Payment Acknowledgement' form.
  • Admission:
  • The existing client is identified or newly admitted into the system. Note the client ID and admission program.
  • Client A.
  • Practitioner:
  • An existing active practitioner is identified.
  • Practitioner A.
  • Financial Eligibility:
  • An existing guarantor is assigned to the client.
  • Dictionary Update:
  • File: Payor
  • (1500) System Financial Class - the 'System Financial Class' dictionary of the guarantor assigned to Client A is not set up.
  • Posting/Adjustment Code Definition:
  • Two payment posting codes are identified or new codes are added.
  • One of the codes is designated as a 'Credit Card Posting Code'.
  • Posting Code 1.
  • Other one designated to a different type,
  • Posting Code 2.
  • Dictionary Update:
  • File: Other Table Files:
  • (5522) Account - contains dictionary codes, dictionary values, and extended dictionary values.
  • Set the 'Show in Various Client Posting Screens' as 'YES'.
Steps
  1. Open the 'Scheduling Calendar' form.
  2. Create an appointment for 'Client A' with 'Practitioner A'.
  3. Access the appointment scheduled for 'Client A' in the setup section.
  4. Right-click on the appointment.
  5. Select the 'Check-In' option.
  6. Verify the 'Expected Self-pay Amount' field displays the correct amount.
  7. Enter the desired amount in the 'Amount Received At Check In'
  8. Select the 'Posting Code 1' that is designated as a 'Credit Card Posting Code'.
  9. Verify the 'Name on Card' field displays as a required field.
  10. Select the 'Posting Code 2' that is designated as an Other Posting Code type.
  11. Verify the 'Name on Card' field displays as an optional field.
  12. Select back the 'Posting Code 1'.
  13. Enter the desired name in the 'Name on Card' field.
  14. Select 'Manual Entry' in the 'Transaction Type field.
  15. Validate that the field 'Select Credit Card Device' is set as disabled and set as read-only.
  16. Click [Pay With Credit Card].
  17. Enter the Credit Card details.
  18. Click [Send].
  19. Validate that we see the success message 'Credit card payment posted and client checked in.'
  20. Click [OK].
  21. Validate that the report opens with the details.
  22. Close the report.
  23. Click [Dismiss].
  24. Open the ‘Payment Acknowledgment’ form.
  25. Select the ‘Post Front Office and myHP Payments’ section.
  26. Enter the desired ‘Payment Collection Date’ for the first client.
  27. If desired, select a ‘Treatment Service’.
  28. Select the desired ‘Type’.
  29. Click [Review].
  30. Validate that the grid contains a row for the client and the correct data for the appropriate columns.
  31. Verify the 'Name on Card' is included in the grid.
  32. Verify the 'Name on Card' field is populated correctly with the value from the 'Name on Card' field of the 'Check In' form.
  33. Clear the 'Name on Card' field value.
  34. Click the checkbox for the row.
  35. Click [Save].
  36. Verify that we get the Success message.
  37. Click [Yes].
  38. Validate the confirm popup shows up with the message- 'Name on Card is required for Credit Card Posting Code. You can re-enter the grid to update the above rows. Or, if you choose to continue and click 'Post' the above rows will not be posted. All other rows without issues will post.'
  39. Click [OK].
  40. Click [Review].
  41. Verify the 'Name on Card' is included in the grid.
  42. Verify the 'Name on Card' field is blank at this point.
  43. Enter any desired value for the 'Name on Card' field.
  44. Click the checkbox for the row.
  45. Click [Save].
  46. Verify that we get the Success message.
  47. Click [Yes].
  48. Enter desired ‘Batch Number’.
  49. Enter desired ‘Deposit Date’.
  50. Select the ‘Category’.
  51. Enter desired ‘Bank Ref #’.
  52. If desired, enter ‘Comments’.
  53. Click [Post].
  54. Validate that a ‘Conform’ message is received stating ‘Filed successfully’.
  55. Click [OK].
  56. Click [Discard].
  57. Open the 'Client Ledger' form.
  58. Search and select Client A and run the report.
  59. Validate that the posted transaction is showing correctly.
  60. Close the report.
  61. Click [No].
  62. Select [Discard].
Payment Acknowledgement-Post Payment Accounting Entry
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Payment Acknowledgement
Scenario 1: Payment Acknowledgement - Post Payment Accounting Entry
Specific Setup:
  • Registry Setting:
  • ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
  • "Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged" has a 'Registry Setting Value that contains '1,4,5,7'
  • Dictionary Update:
  • Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
  • Other Table Files: (5522) Account - contains dictionary codes, dictionary values, and extended dictionary values.
  • Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
  • Posting/Adjustment Codes Definitions: Definitions exist for ‘Payment’.
  • The definitions may have a value in the ‘Payment Acknowledgement Type’ field.
  • All ‘Payment’ definitions will be available in the ‘Payment Acknowledgement’ form.
  • Clients:
  • Identify one or more clients that have a balance due to a self-pay guarantor. Note the balance due amounts.
  • Note the 'Treatment Setting' of the client's program.
Steps
  1. Open the ‘Payment Acknowledgement’ form.
  2. Verify that ‘Action’ defaults to ‘New’.
  3. Verify that ‘Transaction Number’ is read-only.
  4. Verify that ‘Entered By’ is read-only and defaults to the signed-in user.
  5. Enter the desired value in ‘Batch Number’.
  6. Select the desired ‘Posting Code’. All payment posting codes will be displayed.
  7. Enter the desired value in ‘Check/EFT Number’.
  8. Enter the desired value in ‘Amount’.
  9. Select Guarantor 1 in the ‘Guarantor’ field. If a ‘Self-Pay' guarantor is selected, the ‘Client’ field will be enabled.
  10. Enter the desired value in ‘Name/Source’.
  11. Enter the desired value in ‘Client 1’ if enabled. The field is only available for ‘Self-Pay' guarantors.
  12. Enter the desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
  13. Enter the desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
  14. Enter the desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
  15. Select the desired ‘Treatment Service’.
  16. Select the desired ‘Category’. Inactive dictionary codes will not display in this field.
  17. Enter the desired value in ‘Bank Ref #’.
  18. Enter the desired value in ‘Comments’.
  19. Click [File].
  20. Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is <number>. Do you need to continue to Post Payment Accounting Entry?.
  21. Note down the Transaction Number.
  22. Clicking [Yes] will continue to the Post Payment Accounting Entry section or selecting [No] will remain in the ‘Payment Acknowledgement’ section.
  23. Click [No].
  24. Set ‘Action’ defaults to ‘Edit or View’.
  25. Enter the Transaction number noted down in Step 21 in the 'Transaction Number' field of the 'Payment Acknowledgement Search' section.
  26. Select [Search].
  27. Validate that the 'Payment Acknowledgement' selection window is shown with the respective record.
  28. Select the record and click [OK].
  29. Validate that all the fields in the ‘Payment Acknowledgement’ section are populated with the saved values and disabled.
  30. Validate that the Comments field is enabled.
  31. Update the value in the Comments field of the ‘Payment Acknowledgement’ section.
  32. Validate that the grid is not enabled.
  33. Click [New Row] in ‘Post Payment Accounting Entry’.
  34. Validate that the grid becomes enabled.
  35. Select the desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
  36. Select the desired ‘Program’.
  37. Select the desired ‘Account’.
  38. Select the desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
  39. Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgement’.
  40. Select the desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’ or the ‘Deposit Date’.
  41. If desired, enter a ‘Comment’.
  42. Validate that the ‘Posting Summary’ is correct.
  43. If desired, click [New Row] and repeat the steps.
  44. If desired, click [Delete Row]. A ‘Confirm Delete’ message will be displayed. Select the desired value.
  45. Click [File].
  46. The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
  47. Click [No].
  48. Set ‘Action’ defaults to ‘Edit or View’.
  49. Enter the Transaction number noted down in Step 21 in the 'Transaction Number' field of the 'Payment Acknowledgement Search' section.
  50. Select [Search].
  51. Validate that the 'Payment Acknowledgement' selection window is shown with the respective record.
  52. Select the record and click [OK].
  53. Validate that all the fields in the ‘Payment Acknowledgement’ section are populated with the saved values and disabled.
  54. Validate that the Comments field is enabled and shown with the recently updated/filed value.
  55. Validate that the grid has the records filed so far.
  56. Select any row and validate that the fields under the 'Post Payment Accounting Entry' section are disabled and read-only.
  57. Update the value in the Comments field of the ‘Payment Acknowledgement’ section.
  58. Click [File].
  59. The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
  60. Click [Yes].
  61. Select any row and validate that the fields under the 'Post Payment Accounting Entry' section are still disabled and read-only.
  62. Close the form.
Topics
• 835 • NX • Payment Acknowledgement • Scheduling Calendar
Update 23 Summary | Details
Service Fee/Cross Reference
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Fee/Cross Reference Maintenance
  • CPT Code Definition (PM)
Scenario 1: File Import - Service Fee/Cross Reference - Import Process Type = FU&GU
Specific Setup:
  • Registry Setting:
  • Set the registry setting 'Import Process Type' to 'FU&GU'.
  • Set the registry setting 'Disable Full Table Backups Prior To File' to 'F'.
  • Service Codes:
  • Add a new service code for testing purposes. Note the service code/name.
  • File Import:
  • Create an import file to add Service Fee/Cross Reference details (File A),
Steps
  1. Open the 'File Import' form.
  2. Select the 'Service Fee/Cross Reference' in the 'File Type' field.
  3. Select 'Upload New File' in the 'Action' field.
  4. Click [Process Action].
  5. Select the 'File A'.
  6. Select 'Compile/Validate File' in the 'Action' field.
  7. Select the 'File A' in the Files(s) field.
  8. Click [Process Action].
  9. Validate an Information message is displayed stating: Compiled
  10. Click [OK].
  11. Select 'Print File' in the 'Action' field.
  12. Select the 'File A' in the Files(s) field.
  13. Click [Process Action].
  14. Validate the Report Viewer displays the contents of the file.
  15. Click [Close Report].
  16. Select 'Post File' in the 'Action' field.
  17. Click [Process Action].
  18. Select the 'File A'.
  19. Validate an Information message is displayed stating: Posted.
  20. Click [OK] and close the form.
  21. Open the 'Service Fee/Cross Reference Maintenance' form.
  22. Click [Edit].
  23. Enter the filed 'Service Code'.
  24. Enter the filed 'From Date'.
  25. Click [Select Fee/Cross Ref To Edit/Default From Existing Row].
  26. Select a valid Row.
  27. Click [OK].
  28. Validate the form is filed with the data based on the uploaded file.
  29. Click [Submit].
  30. Click [No].
Scenario 2: Add/Edit a new Service Code-Service Code
Steps
  1. Open "Service Codes" Form.
  2. Click [Add] in 'Add new or Edit Existing item'.
  3. Enter desired 'Service Code'.
  4. Select any value in 'Service Code Category'.
  5. Select any value in 'Service Code Type'.
  6. Click [No] in 'Inactive Service Code'.
  7. Enter any value in 'Service Code Definition'.
  8. Select any value in 'Service Required By'
  9. Select any value from 'Type Of Service dropdown'.
  10. Select any value in 'Type of Fee'.
  11. Enter any value in 'Minutes Per Unit.'
  12. Select any value in Unit Rounding Logic.
  13. Select any value in 'Degree of Rounding'.
  14. Select any value from 'Group Code' dropdown list.
  15. Select any value from 'Covered Charge Category' dropdown list.
  16. Select any value from 'Is This A Balance Forward Service Code'.
  17. Select any value from 'Is This Service a Procedure'.
  18. Select any value from 'Emergency Indicator'.
  19. Select any value from 'Does This Code Have A Professional Component'.
  20. Select any value from 'Is This Service A Visit'.
  21. Select any value from 'Is This Service An Intervention?'
  22. Click Submit.
  23. Click[Yes].
  24. Click [Edit] in 'Add new or Edit Existing item'.
  25. Enter desired Service Code'.
  26. Verify 'Service Code Category' value.
  27. Verify 'Service Code Type' value.
  28. Verify 'Inactive Service Code' value.
  29. Verify 'Service Code Definition' value.
  30. Verify 'Service Required By' value.
  31. Verify 'Type Of Service' dropdown list value.
  32. Verify 'Type of Fee' value.
  33. Verify 'Minutes Per Unit' value.
  34. Verify 'Unit Rounding Logic' value.
  35. Verify 'Degree of Rounding' value.
  36. Verify 'Group Code dropdown list' value.
  37. Verify 'Covered Charge Category' dropdown list value.
  38. Verify Is 'This A Balance Forward Service Code' value.
  39. Verify 'Is This Service a Procedure' value.
  40. Verify 'Emergency Indicator' value.
  41. Verify 'Does This Code Have A Professional Component' value.
  42. Verify 'Is This Service A Visit' value.
  43. Verify 'Is This Service An Intervention?' value.
  44. Click Submit.
  45. Click [No].
Post Staff Activity
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Appointment Management
  • Scheduling Calendar
  • Post Staff Activity Log
  • Client Ledger
Scenario 1: Appointment Management - Individual and Group scheduling
Specific Setup:
  • Sites must be defined.
  • Create or identify two practitioners using 'Practitioner Enrollment'. This is Practitioner A and Practitioner B.
  • Using the 'Staff Members Hours and Exceptions' form, enter in hours for the site/practitioners.
  • A group must exist that contains at least two or more clients (Group A).
  • Identify an active existing client (Client A).
Steps
  1. Access the 'Scheduling Calendar' form.
  2. Select 'Practitioner A' on the left-hand side.
  3. Right click on any available time slot for 'Practitioner A'.
  4. Click [Add Appointment].
  5. Verify the 'Add New Appointment' window exists.
  6. Enter any individual service code in the 'Service Code' field.
  7. Enter 'Client A' in the 'Client' field.
  8. Select any value from the 'Episode Number' field.
  9. Select any value from the 'Program' field.
  10. Click [Submit].
  11. Right click on the appointment created in the previous step for 'Client A'.
  12. Click [Copy].
  13. Right click in any available time slot for 'Practitioner A.
  14. Click [Paste Appointment].
  15. Validate a "Warning- Same Day Existing Appointments" message is displayed for ;Client A'.
  16. Click [OK].
  17. Validate that 'Client A' now has two appointments listed.
  18. Right click on the appointment just pasted for 'Client A'.
  19. Click [Delete].
  20. Validate a "Delete Appointment" message is displayed: Are you sure?
  21. Click [Yes] and [Dismiss].
  22. Access the 'Appointment Management' form.
  23. Enter 'Practitioner A' in the 'Practitioner' field.
  24. Enter the current date in the 'Appointment Start Date' field.
  25. Enter the current date in the 'Appointment End Date' field.
  26. Click [Print].
  27. Validate an 'Appointment Management' report is displayed with the appointment for 'Client A'.
  28. Click [Add/Edit Appointments].
  29. Validate the appointment for 'Client A' is displayed.
  30. Select the 'End' field and change the end time to any other value.
  31. Click [Save].
  32. Close the form.
  33. Access the 'Scheduling Calendar' form.
  34. Validate the 'Scheduling Calendar' has been updated to reflect 'Client A's' appointment with the new 'End' time entered in previous step.
  35. Click [Refresh].
  36. Right click on the appointment for 'Client A'
  37. Click [Check In].
  38. Validate an "Information" message is displayed stating: Invalid or no 'Pre Payment Service Code' defined in the registry. All payments must be filed at check out.
  39. Click [OK].
  40. Validate the 'Check In' window is displayed.
  41. Click [Submit].
  42. Right click on the appointment for 'Client A'.
  43. Click [Check Out].
  44. Validate a 'Check Out' window is displayed.
  45. Click [Submit].
  46. Right click on any available time slot for 'Practitioner A'.
  47. Click [Add Appointment].
  48. Verify the 'Add New Appointment' window exists.
  49. Enter any group service code in the 'Service Code' field.
  50. Enter 'Group A' in the 'Group #' field.
  51. Select any value from the 'Program' field.
  52. Select the 'Group Members' tab.
  53. Select "Add" from the 'Add / Edit / Remove Group Members' field.
  54. Enter any client that is not in 'Group A' in the 'Client' field.
  55. Click [Update Members].
  56. Validate the client selected in the previous step is displayed in the 'Current Group Appointment Members' field.
  57. Select "Remove" from the 'Add / Edit / Remove Group Members' field.
  58. Select the client added in the previous steps from the 'Edit / Remove Multiple Group Members' field.
  59. Click [Update Members].
  60. Validate the client added in the previous steps is no longer displayed in the 'Current Group Appointment Members' field.
  61. Click [Submit] and [Dismiss].
  62. Access the 'Appointment Management' form.
  63. Enter 'Practitioner A' in the 'Practitioner' field.
  64. Enter the current date in the 'Appointment Start Date' field.
  65. Enter the current date in the 'Appointment End Date' field.
  66. Click [Add/Edit Appointments].
  67. Validate the appointment for 'Group A' is displayed.
  68. Check the 'Post' checkbox.
  69. Click [Save].
  70. Close the form.
  71. If desired, repeat step for 'Practitioner B'.
Scenario 2: Post Appointment - Post Staff Activity Log
Specific Setup:
  • Group with 4-5 Clients must have an appointment for (Service A) scheduled with Practitioner A and Practitioner B.
Steps
  1. Access the 'Post Staff Activity Log' form.
  2. Enter the desired practitioner from the Pre-Conditions in the 'Select Staff' field.
  3. Click [Select].
  4. Enter the date of the appointment in the 'Appointment Date' field.
  5. Select the site of the appointment in the 'Appointment Site' field.
  6. Click [Submit].
  7. Validate that a "Pre-Display Confirmation" message is displayed stating: Do you want to return to Pre-Display?.
  8. Click [No].
  9. Access the 'Post Staff Activity Log' form.
  10. Enter 'Practitioner A' from the Pre-Conditions in the 'Select Staff' field.
  11. Click [Select].
  12. Enter the date of the appointment in the 'Appointment Date' field.
  13. Select the site of the appointment in the 'Appointment Site' field.
  14. Enter the 'Group #'.
  15. Click [Submit].
  16. Validate that a "Pre-Display Confirmation" message is displayed stating: Do you want to return to Pre-Display?.
  17. Click [No].
  18. Access the 'Client Ledger' form.
  19. Enter 'Client A' in the 'Client ID' field.
  20. Select 'Episode' from the 'Claim/Episode/All Episodes' field.
  21. Select the episode the appointment was created for from the 'Episode Number' field.
  22. Select 'Simple' in the 'Ledger Type' field.
  23. Click [Process].
  24. Verify that the ledger displays the service code from the posted appointment.
  25. Click [Dismiss].
  26. Validate that a "Form Return" message is displayed stating: Processing report has completed. Do you wish to return to form?
  27. Click [No].
  28. Access the 'Scheduling Calendar' form.
  29. Validate that "Client A's" appointment displays the posted disposition icon: green arrow.
  30. Click [Dismiss].
  31. Access Crystal Reports or other SQL Reporting tool.
  32. Select the PM namespace.
  33. Create a report using the 'SYSTEM.billing_tx_history' table.
  34. Validate a row is displayed for the service created for 'Client A'.
  35. Validate the 'PATID' field contains 'Client A's' ID.
  36. Validate the 'PROVIDER_ID' field contains the practitioner for the appointment.
  37. Validate the 'co_staff_member' field is null.
  38. Validate the 'co_staff_member_2' field contains the Second Co-Practitioner.
  39. Validate the 'co_staff_2_duration' field contains the duration filed for the Second Co-Practitioner.
  40. Validate the 'co_staff_duration' field is null.
  41. Close the report.
Topics
• Service Fee/Cross Reference Maintenance • Service Fee/Cross Reference and Guarantor Definition Export • Service Codes • Scheduling Calendar • Appointment Management • NX • Post Staff Activity Log
Update 24 Summary | Details
Quick Billing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
  • Client Charge Input
  • Client Ledger
  • Quick Billing Rule Definition
  • Quick Billing
Scenario 1: Creating and Editing a Quick Billing Batch
Specific Setup:
  • Quick Billing Rule Definition is created and the rule criteria is noted.
  • Admission:
  • Select an existing client, or admit a new client. The client must be in a program that meets the Quick Billing Rule Definition criteria.
  • Client Charge Input:
  • 1-2 days of professional charges are rendered to the clients. Please note the service codes used during rendering services.
Steps
  1. Open the 'Quick Billing' form.
  2. Select 'Add New' in 'Add New Or Edit Existing Quick Billing Batch'.
  3. Select the desired rule in 'Billing Rule To Execute'.
  4. Use a date range spanning services entered.
  5. Select the following in 'Quick Billing Tasks To Execute' :Create Batch.
  6. Click [T] on 'Date of Claim'.
  7. Click [Submit].
  8. Click [OK].
  9. Click [Yes].
  10. Select 'Edit' in 'Add New Or Edit Existing Quick Billing Batch'.
  11. Select the desired 'File'.
  12. Click [Launch Workscreen].
  13. Select a row and note the 'Service Date'
  14. Click [Delete Row].
  15. Click [Yes].
  16. Click [Save].
  17. Click [Yes].
  18. Click [Launch Workscreen].
  19. Verify that service row was deleted.
  20. Click [Close/Cancel].
  21. Click [Submit].
  22. Click [OK].
  23. Close the form.
Topics
• Quick Billing • NX
Update 27 Summary | Details
Credit Card Processing - Deposit Entry
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Credit Card Configuration
  • Deposit Entry
  • Client Ledger
Scenario 1: Deposit Entry - Credit Card - Manual Entry
Specific Setup:
  • Please contact your Netsmart representative for assistance to enable credit card functionality.
  • The following registry setting has a value of 'Y': Avatar PM--->Billing->Remittance Processing->->->Enable Credit Card Processing.
  • The system must be configured to send production data through CareFabric.
  • 'Service Code 1: is a non-billable code used to make payment deposits to client accounts.
  • Posting/Adjustment Codes Definition 1: configure a payment posting code with a value of 'Credit Card Posting Code' in 'Is this a Credit Card or ACH Code'.
  • 'Posting/Adjustment Codes Definition 2': configure a payment posting code with no value in 'Is this a Credit Card or ACH Code'.
  • The following registry setting has a value of 'Service Code 1': Avatar PM->Services->Ancillary/Ambulatory Services->Deposit Entry->->Default Service Code.
  • The following registry setting has a value of 'Posting/Adjustment Codes Definition 2': Avatar PM->Scheduling->Front Desk->->->Pre Payment Default Posting Code.
  • The following registry setting has a value of 'Y': Avatar PM--->Billing->Remittance Processing->->->Enable Credit Card Processing.
  • Credit Card Configuration:
  • Has a value of 'Yes' in 'Populate Receipt Number with Credit Card Payment Reference Number'.
  • Enter desired values for the other fields.
  • In the 'Credit Card Device Setup' section:
  • 'Credit Card Device 1':
  • Has a value of 'No' in 'Is this a Back Office MID?'. Note the device name.
  • Enter desired values for the other fields.
  • 'Credit Card Device 2':
  • Has a value of 'Yes' in 'Is this a Back Office MID?'. Note the device name.
  • Enter desired values for the other fields.
  • 'Guarantors/Payors 1': Has a 'Financial Class' of 'Self Pay'.
  • 'Client 1':
  • Is assigned Guarantors/Payors 1 in 'Financial Eligibility.
  • Using 'Client Ledger' client has a positive amount for Guarantors/Payors 1 in 'TOTAL BALANCE BY GUARANTOR.
Steps
  1. Open 'Deposit Entry'.
  2. Enter desired value in 'Client ID'.
  3. Enter desired value in 'Episode Number.
  4. Select 'Guarantors/Payors 1' in 'Guarantor'.
  5. Enter desired value in 'Date of Receipt or Adjustment'.
  6. Enter 'Service Code 1' in 'Service Code'.
  7. Enter desired value in 'Amount To Post'.
  8. Select 'Posting/Adjustment Codes Definition 1' in 'Posting Code'.
  9. Note that 'Transaction Type' is enabled, required and defaults to 'Insert/Swipe Card'.
  10. Note that 'Select Credit Card Device' is enabled and required.
  11. Select 'Manual Entry' in 'Transaction Type'.
  12. Validate that the device is 'Credit Card Device 2'.
  13. Click [Pay With Credit Card].
  14. If the system is not configured to send production data through CareFabric, the following message will be received: 'This functionality is not supported in a non-production environment'.
  15. If the system is configured to send production data through CareFabric, enter the credit card information, consisting of the 'Card Number', 'Expiration Date' and 'CVV', in the popup window.
  16. Click [Send].
  17. A message will be received in the form. Possible messages are: 'Credit card payment posted.' and 'Payment was not approved.'.
  18. Click [OK].
  19. Validate that the receipt is received and is correct.
  20. Close the receipt.
  21. Click [X].
  22. Click [Yes].
  23. If desired, use 'Client Ledger' to validate the payment.
Topics
• Deposit Entry • Credit Card Processing
Update 28 Summary | Details
File Import -
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Update Demographics
  • Guarantors/Payors
Scenario 1: File Import: Guarantors Payors Add/Edit
Specific Setup:
  • File Import:
  • The 'Guarantors/Payors' file type is added to the File Import.
  • Create an import file to add a new 'Guarantors/Payors', "File A".
  • Create an import file to edit above 'Guarantors/Payors', "File B".
Steps
  1. Open the "File Import" form.
  2. Select the "Guarantors/Payors" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Select "File A".
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select "File A" in the 'Files(s)' field.
  8. Click [Process Action].
  9. Validate an Information message is displayed stating: Compiled
  10. Click [OK].
  11. Select "Print File" in the 'Action' field.
  12. Select "File A" in the 'Files(s)' field.
  13. Click [Process Action].
  14. Validate the Report Viewer displays the contents of the file.
  15. Click [Close Report].
  16. Select "Post File" in the 'Action' field.
  17. Click [Process Action].
  18. Select "File A".
  19. Validate an Information message is displayed stating: Posted.
  20. Click [OK].
  21. Close the form.
  22. Open the "Guarantors/Payors" form.
  23. Click [Edit].
  24. Select the guarantor in "File A".
  25. Validate the form contains the data based on the uploaded file.
  26. Close the form.
  27. Follow steps 1-25 for "File B" to edit the guarantor through file import.
Topics
• Guarantor/Payors • File Import • NX
Update 29 Summary | Details
Remittance Processing Widget - Future Functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
  • Client Ledger
  • Create Interim Billing Batch File
  • Electronic Billing
  • Remittance Processing Widget
  • Quick Billing Rule Definition
  • Quick Billing
Internal Test Only
Topics
• Remittance Processing • NX • Remittance Processing Widget
Update 30 Summary | Details
Delete Service/Delete Service (Open Services Only) - Auto Append Document Image in Delete Service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Delete Service
  • Service Delete
  • Client Ledger
  • Delete Service (Open Service Only)
  • Clinical Document Viewer
  • Client Charge Input
  • Create New Progress Notes Form
  • Document Routing Setup (PM)
  • Progress Notes (Group and Individual) 6
Scenario 1: Delete Service - Validation
Specific Setup:
  • Select a test client and enter charges by using the "Client Charge Input" form.
Steps
  1. Open the "Delete Service" form.
  2. Delete a service for the test client from Setup.
  3. Open the "Client Ledger" form.
  4. Validate the service has been removed from the system.
Scenario 2: Delete Service (Open Service Only) - Delete an open service
Specific Setup:
  • Select a test client and enter charges by using the "Client Charge Input" form.
Steps
  1. Open the "Delete Service (Open Service Only)" form.
  2. Delete a service for the test client from Setup.
  3. Open the "Client Ledger" form.
  4. Validate the service has been removed from the system.
Scenario 3: Registry Setting - Auto Append Document Image in Delete Service
Steps
  1. Open the "Registry Settings" form.
  2. Search for the registry setting "Auto Append Document Image in Delete Service".
  3. Set the "Value" to "N".
  4. Click "Submit" to file.
  5. Open the "Delete Service" form.
  6. Select a client and date range.
  7. Click "Display Client".
  8. Validate there is no column called "Document" on the form.
  9. Exit the form.
  10. Open the "Registry Settings" form.
  11. Search for the registry setting "Auto Append Document Image in Delete Service".
  12. Set the "Value" to "Y".
  13. Click "Submit" to file.
  14. Open the "Delete Service" form.
  15. Select a client and date range.
  16. Click "Display Client".
  17. Validate there is a column called "Document" on the form.
  18. Exit the form.
Scenario 4: Delete Service - Allow Auto Append of Document Image in Delete Service
Specific Setup:
  • Registry setting "Auto Append Document Image in Delete Service" must be enabled.
  • Using "Client Charge Input", enter 3 charges for a client.
  • Using "Create New Progress Note" form, create a new progress note for testing.
  • Give the Avatar user access to the newly created Progress note form.
  • Refresh menus to add the new form to the user's menu.
  • Using "Document Routing Setup", enable document routing for the newly created progress note form.
Steps
  1. Open the progress note copy that was created for this test.
  2. Generate a progress note for an existing service (select one of the services entered in Setup).
  3. Finalize the progress note.
  4. Sign/Accept the document.
  5. Return to the form.
  6. Generate a progress note for an existing service (select one of the services entered in Setup).
  7. Finalize the progress note.
  8. Sign and Route or Accept and Route the document to an approver.
  9. Exit the form.
  10. Open the "Delete Service" form.
  11. Select the client and date range and click "Display Client".
  12. Note the presence of a new column called "Document".
  13. The new column will indicate the state the document is in, It could be "Final" or "Pending" or blank depending on the status of the form. Final means it's been finalized and stored. Pending means it's waiting to be finalized by approver(s). Blank means there is no document attached to the service.
  14. Services that have the word "Final" next to them cannot be deleted with any other service. "Final" means the service has a finalized document attached to it. If you do try several services together, you will receive the following message: "There are one or more services selected that are associated with a document. These services must be deleted separately.".
  15. Services that have the word "Pending" in the "Document" column can't be deleted until they have been finalized by all approvers and this column value is changed to "Final". If you try to remove a service with a pending document, you will receive the following message: "The selected service is associated with a document that is not "Final". The service cannot be deleted until the document is finalized."
  16. Select a document that has the word "Final" in the "Document" column.
  17. The message "Delete Service No Yes The selected service is associated with a finalized document, continuing will append the document. Would you like to continue?" pops up.
  18. Respond by clicking "Yes" to continue".
  19. Click "Delete" button.
  20. Validate the document that displays includes an appended page that states the "Service has been deleted!!!".
  21. Click "Sign".
  22. Open "Client Ledger".
  23. Validate the service has been removed from the system.
  24. Open "Clinical Document Viewer".
  25. Locate and open the document that was attached to the now deleted service.
  26. Validate the stored document has the appended page attached.
  27. Navigate to the "myToDo" widget.
  28. Accept and Sign the document to approve it.
  29. Open the "Delete Service" form.
  30. Validate the service that was once "Pending" is now "Final".
  31. Delete the service with the finalized document attached.
  32. Validate the document that displays includes an appended page that states the "Service has been deleted!!!".
  33. Click "Sign".
  34. Open "Client Ledger".
  35. Validate the service has been removed from the system.
  36. Open "Clinical Document Viewer".
  37. Locate and open the document that was attached to the now deleted service.
  38. Validate the stored document has the appended page attached.
Scenario 5: Delete Service (Open Services Only) - Allow Auto Append of Document Image in Delete Service
Specific Setup:
  • Registry setting "Auto Append Document Image in Delete Service" must be enabled.
  • Using "Client Charge Input", enter 3 charges for a client.
  • Using "Create New Progress Note" form, create a new progress note for testing.
  • Give the Avatar user access to the newly created Progress note form.
  • Refresh menus to add the new form to the user's menu.
  • Using "Document Routing Setup", enable document routing for the newly created progress note form.
Steps
  1. Open the progress note copy that was created for this test.
  2. Generate a progress note for an existing service (select one of the services entered in Setup).
  3. Finalize the progress note.
  4. Sign/Accept the document.
  5. Return to the form.
  6. Generate a progress note for an existing service (select one of the services entered in Setup).
  7. Finalize the progress note.
  8. Sign and Route or Accept and Route the document to an approver.
  9. Exit the form.
  10. Open the "Delete Service (Open Service Only)" form.
  11. Select the client and date range and click "Display Client".
  12. Note the presence of a new column called "Document".
  13. The new column will indicate the state the document is in, It could be "Final" or "Pending" or blank depending on the status of the form. Final means it's been finalized and stored. Pending means it's waiting to be finalized by approver(s). Blank means there is no document attached to the service.
  14. Services that have the word "Final" next to them cannot be deleted with any other service. "Final" means the service has a finalized document attached to it. If you do try several services together, you will receive the following message: "There are one or more services selected that are associated with a document. These services must be deleted separately.".
  15. Services that have the word "Pending" in the "Document" column can't be deleted until they have been finalized by all approvers and this column value is changed to "Final". If you try to remove a service with a pending document, you will receive the following message: "The selected service is associated with a document that is not "Final". The service cannot be deleted until the document is finalized."
  16. Select a document that has the word "Final" in the "Document" column.
  17. The message "Delete Service No Yes The selected service is associated with a finalized document, continuing will append the document. Would you like to continue?" pops up.
  18. Respond by clicking "Yes" to continue".
  19. Click "Delete" button.
  20. Validate the document that displays includes an appended page that states the "Service has been deleted!!!".
  21. Click "Sign".
  22. Open "Client Ledger".
  23. Validate the service has been removed from the system.
  24. Open "Clinical Document Viewer".
  25. Locate and open the document that was attached to the now deleted service.
  26. Validate the stored document has the appended page attached.
  27. Navigate to the "myToDo" widget.
  28. Accept and Sign the document to approve it.
  29. Open the "Delete Service (Open Service Only)" form.
  30. Validate the service that was once "Pending" is now "Final".
  31. Delete the service with the finalized document attached.
  32. Validate the document that displays includes an appended page that states the "Service has been deleted!!!".
  33. Click "Sign".
  34. Open "Client Ledger".
  35. Validate the service has been removed from the system.
  36. Open "Clinical Document Viewer".
  37. Locate and open the document that was attached to the now deleted service.
  38. Validate the stored document has the appended page attached.
Topics
• NX • Delete Services
Update 33 Summary | Details
Benefit Enrollment and Maintenance (834)
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
  • Pre-Fill Financial Eligibility Data (834) Setup
  • Benefit Enrollment and Maintenance (834)
  • Cross Episode Financial Eligibility
Scenario 1: Benefit Enrollment and Maintenance (834) - Load/ Compile/ Post File
Specific Setup:
  • Registry Settings:
  • 'Enable 834 Transaction Set' = Y.
  • 'Pre-Fill Financial Data (834/271)' = Y.
  • 'Update Demographic Data When Posting Eligibility File' = Y.
  • Tester has access to the 'Benefit Enrollment and Maintenance (834)', 'Pre-Fill Financial Eligibility Data (834/271) Setup', 'Guarantors/Payors', 'Update Client Data' and 'Cross Episode Financial Eligibility'' forms.
  • Guarantors/Payors:
  • Select a guarantor to use for 270 / 271 / 834 activity. Note the 'Financial Class' and 'Default Guarantor Plan'.
  • 270 / 271 / 834 section:
  • Insurer Identifier Code Qualifier (1000B-N1-03) = Code Assigned By Organization That Is Destination Of Transaction Set.
  • Insurer Identifier Code (1000B-N1-04) = desired value, noting the value.
  • Pre-Fill Financial Eligibility Data (834/271) Setup:
  • 'Guarantor = above guarantor.
  • Benefit Plan = above 'Default Guarantor Plan'.
  • Insert Guarantor Before or After Financial Classes = desired value.
  • Financial Class = above 'Financial Class'.
  • Client:
  • 'Client 1' is enrolled with no demographic data, no cross episode financial eligibility data, and no 'Benefit Enrollment and Maintenance (834)' submission.
  • 'Client 2' is enrolled with no demographic data, no cross episode financial eligibility data, and no 'Benefit Enrollment and Maintenance (834)' submission.
  • Benefit Enrollment and Maintenance (834)
  • A file exists for 'Client 1' only, that contains the above guarantor, the 'Insurer Identifier Code (1000B-N1-04)' value, and demographic data. 'File 1'.
  • A file exists for 'Client 1' and 'Client 2', that contains the above guarantor, the 'Insurer Identifier Code (1000B-N1-04)' value, and demographic data. 'File 2'. Update at least one field of demographic data for 'Client 1', noting the value.

Steps
  1. Open 'Benefit Enrollment and Maintenance (834)'.
  2. Load, compile, and post 'File 1'.
  3. Open 'Update Client Data' for 'Client 1'.
  4. Validate that the demographic data displays correctly.
  5. Close the form.
  6. Open 'Cross Episode Financial Eligibility' for 'Client 1'.
  7. Validate that the guarantor information displays correctly.
  8. Close the form.
  9. Open 'Benefit Enrollment and Maintenance (834)'.
  10. Load, compile, and post 'File 2'.
  11. Open 'Update Client Data' for 'Client 1'.
  12. Validate that the demographic data that was edited displays correctly.
  13. Close the form.
  14. Open 'Cross Episode Financial Eligibility' for 'Client 1'.
  15. Validate that the guarantor information did not change.
  16. Close the form.
  17. Open 'Update Client Data' for 'Client 2'.
  18. Validate that the demographic data displays correctly.
  19. Close the form.
  20. Open 'Cross Episode Financial Eligibility' for 'Client 2'.
  21. Validate that the guarantor information displays correctly.
  22. Close the form.
Topics
• Update Client Data • Cross Episode Financial Eligibility • Benefit Enrollment and Maintenance (834)
Update 34 Summary | Details
File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
Scenario 1: File Import - Guarantors/Payors -270/271/834 Section
Specific Setup:
  • File Import:
  • The ''Guarantors/Payors 270/271/834'' file type is added to 'File Import'.
  • Create an import file to add 270/271/834 details to a valid Guarantor. ''File A''.
Steps
  1. Open the "File Import" form.
  2. Select "Guarantors/Payors 270/271/834" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Select "File A".
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select "File A" in the 'Files(s)' field.
  8. Click [Process Action].
  9. Validate an Information message is displayed stating: Compiled
  10. Click [OK].
  11. Select "Print File" in the 'Action' field.
  12. Select "File A" in the 'Files(s)' field.
  13. Click [Process Action].
  14. Validate the Report Viewer displays the contents of the file.
  15. Click [Close Report].
  16. Select "Post File" in the 'Action' field.
  17. Click [Process Action].
  18. Select "File A".
  19. Validate an Information message is displayed stating: Posted.
  20. Click [OK].
  21. Close the form.
  22. Open the "Guarantors/Payors" form.
  23. Select 'Edit' in 'Add New or Edit Existing Guarantor'.
  24. Select desired guarantor.
  25. Select the "270/271/834" section.
  26. Validate the data is populated as per imported file.
  27. Close form.
Topics
• File Import • NX
Update 37 Summary | Details
The 'Alternate Lookup By Room' registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Ledger
  • Appointment Management
Scenario 1: Validate the 'Alternate Lookup By Room' registry setting
Specific Setup:
  • A practitioner is defined (Practitioner A).
  • Two clients (Client A & Client B) must be admitted into inpatient episodes in the same room (Room A).
  • The registry setting "Include Active Room Number with Client" is set to "1".
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Alternate Lookup By Room" in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings].
  4. Validate the 'Registry Setting' field contains: Avatar PM->Client Information->Client Lookup->->->Alternate Lookup By Room.
  5. Validate the 'Registry Setting Detail' field contains: Selecting 'Y' will add an alternate search for clients by room number in the My Clients widget and Client Search. This must be an exact match and will look at the 'Include Active Room Number With Client Name' registry setting to potentially parse the room number. Select 'N' to disable this functionality.
  6. Enter "Y" in the 'Registry Setting Value' field.
  7. Click [Submit] and close the form.
  8. Search for "Room A" in the 'Search Clients' field.
  9. Validate both "Client A" and "Client B" are displayed.
  10. Access the 'Progress Notes (Group and Individual)' form.
  11. Enter "Room A" in the 'Select Client' field.
  12. Validate "Client A" and "Client B" are displayed.
  13. Close the form.
  14. Access the 'Client Ledger' form.
  15. Enter "Room A" in the 'Client ID' field.
  16. Validate "Client A" and "Client B" are displayed.
  17. Close the form.
  18. Access the 'Account Registration' form.
  19. Enter "Room A" in the 'Select Client' dialog.
  20. Validate "Client A" and "Client B" are displayed.
  21. Click [Cancel].
  22. Access the 'Service Authorization' form.
  23. Enter "Room A" in the 'Select Client' dialog.
  24. Validate "Client A" and "Client B" are displayed.
  25. Click [Cancel].
  26. Access the 'Appointment Management' form.
  27. Enter "Room A" in the 'Practitioner' field.
  28. Validate no clients are displayed.
  29. Enter "Practitioner A" in the 'Practitioner' field.
  30. Validate "Practitioner A" is displayed.
  31. Close the form.
  32. Access the 'Registry Settings' form.
  33. Enter "Alternate Lookup By Room" in the 'Limit Registry Settings to the Following Search Criteria' field.
  34. Click [View Registry Settings].
  35. Validate the 'Registry Setting' field contains: Avatar PM->Client Information->Client Lookup->->->Alternate Lookup By Room.
  36. Enter "N" in the 'Registry Setting Value' field.
  37. Click [Submit] and close the form.
  38. Search for "Room A" in the 'Search Clients' field.
  39. Validate "Client A" and "Client B" are not displayed.
  40. Access the 'Progress Notes (Group and Individual)' form.
  41. Enter "Room A" in the 'Select Client' field.
  42. Validate "Client A" and "Client B" are not displayed.
  43. Close the form.
  44. Access the 'Client Ledger' form.
  45. Enter "Room A" in the 'Client ID' field.
  46. Validate "Client A" and "Client B" are not displayed.
  47. Close the form.
  48. Access the 'Account Registration' form.
  49. Enter "Room A" in the 'Select Client' dialog.
  50. Validate "Client A" and "Client B" are not displayed.
  51. Click [Cancel].
  52. Access the 'Service Authorization' form.
  53. Enter "Room A" in the 'Select Client' dialog.
  54. Validate "Client A" and "Client B" are not displayed.
  55. Click [Cancel].
Topics
• Registry Settings
Update 38 Summary | Details
Program Transfer - Pre Admit programs
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Transfer
  • Program Transfer (OutPatient)
  • Dictionary Update (PM)
Scenario 1: Program Transfer - Validate 'Pre Admit' program transfers
Specific Setup:
  • Two Pre Admit programs must be defined in 'Program Maintenance' (Program A & Program B).
  • The 'Allow Admission To File/Edit Pre-Admits' registry setting is set to "Y".
  • The 'Allow Transfers Among Pre-Admit Programs' registry setting is set to "Y".
Steps
  1. Access the 'Pre Admit' form.
  2. Add a pre-admission for a new client. This will be referred to as "Client A".
  3. Enter the desired date in the 'Preadmit/Admission Date' field.
  4. Enter the desired time in the 'Preadmit/Admission Time' field.
  5. Select "Program A" in the 'Program' field.
  6. Select the desired practitioner in the 'Admitting Practitioner' field.
  7. Populate all other required and desired fields.
  8. Click [Submit].
  9. Select "Client A" and access the 'Program Transfer' form.
  10. Select "Program B" in the 'Program' field.
  11. Enter the desired date in the 'Date Of Transfer' field.
  12. Enter the desired time in the 'Time Of Transfer' field.
  13. Click [Submit].
  14. Select "Client A" and access the 'Pre Admit' form.
  15. Select the existing episode and click [Edit].
  16. Click [Submit].
  17. Validate successful submission.
  18. Select "Client A" and access the 'Admission' form.
  19. Select the existing episode and click [Edit].
  20. Click [Submit].
  21. Validate a message is displayed stating: "Pre-Admission Program has not been changed to an Admission Program, and there are pre-admission transfers associated with this episode. Please edit with the 'Pre-Admission' or 'Program Transfer' form."
  22. Click [OK].
  23. Select any outpatient admission program in the 'Program' field.
  24. Click [Submit].
  25. Validate successful submission.
  26. Select "Client A" and access the 'Admission' form.
  27. Select the existing episode and click [Edit].
  28. Validate the 'Program' field contains the outpatient admission program selected in the previous steps.
  29. Close the form.
Topics
• Pre Admit • Program Transfer
Update 39 Summary | Details
'Client's Email Address' validations
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Discharge
  • SoapUI - ClientDemographics
  • SoapUI - UpdateAdmission
  • SQL Query/Reporting
  • Pre Admit Discharge
Scenario 1: The 'ClientAdmission' - 'AddAdmission' web service: Admission of a new client
Specific Setup:
  • The user has access to a Web services tool.
Steps
  1. Access the Web services tool and select the WSDL for the 'ClientAdmission' - 'AddAdmission' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter the desired date in the 'AdmissionDate' field.
  6. Enter the desired time in the 'AdmissionTime' field.
  7. Enter the desired practitioner in the 'AdmittingPractitioner' field.
  8. Enter the desired value in the 'ClientFirstName' field.
  9. Enter the desired value in the 'ClientLastName' field.
  10. Enter the desired value in the 'ClientMiddleName' field.
  11. Enter the corresponding name in the 'ClientName' field.
  12. Enter the desired value in the 'ESignatureConsentOnFile' field. Note: "Y" and "N" are accepted values.
  13. Enter the desired value in the 'Program' field.
  14. Enter the desired value in the 'Sex' field.
  15. Enter the desired value in the "Time Zone for Appointment Reminders" field.
  16. Set the "PreferredAppointmentSite" to the desired site.
  17. Populate any other required and desired fields.
  18. Enter the desired value in the 'Address Type' field.
  19. Enter "test@gmailcom" in the 'ClientEmailAddress' field.
  20. Click [Run].
  21. Validate a message is displayed stating: Please enter a valid email address.
  22. Enter "test@gmail.com" in the 'ClientEmailAddress' field.
  23. Click [Run].
  24. Validate the 'Confirmation' field contains a value such as: "Client Unique ID: # Unique ID: #".
  25. Validate the 'Message' field contains: "Client Admission web service has been filed successfully".
  26. Select the client filed in the previous steps and access the 'Admission' form.
  27. Select the record filed in the previous steps and click [Edit].
  28. Validate all populated fields are displayed.
  29. Select the "Demographics" section.
  30. Validate the 'Client Last Name' field contains the value filed in the previous steps.
  31. Validate the 'Client First Name' field contains the value filed in the previous steps.
  32. Validate the 'Client Middle Name' field contains the value filed in the previous steps.
  33. Validate the 'Consent On File For Use of Integrated eSignature' field contains the value filed in the previous steps.
  34. Validate 'Time Zone for Appointment Reminders' field contains the value filed in the previous steps.
  35. Validate the 'Preferred Appointment Site' field contains the value filed in the previous steps.
  36. Validate the 'Address Type' field contains the value filed in the previous steps.
  37. Validate the 'Client's Email Address' field contains "test@gmail.com".
  38. Close the form.
Scenario 2: Validate the 'Admission' form for a new client
Steps
  1. Access the 'Admission' form.
  2. Admit a new client into any episode.
  3. Populate all required and desired fields.
  4. Select the "Demographics" section.
  5. Enter "testgmailcom" in the 'Client's Email Address' field.
  6. Validate a message is displayed stating: Please enter a valid email address.
  7. Click [OK].
  8. Enter "testgmail.com" in the 'Client's Email Address' field.
  9. Validate a message is displayed stating: Please enter a valid email address.
  10. Click [OK].
  11. Enter "testgmail@com" in the 'Client's Email Address' field.
  12. Validate a message is displayed stating: Please enter a valid email address.
  13. Click [OK].
  14. Enter "test@gmail.com" in the 'Client's Email Address' field.
  15. Please note: a valid email address should contain '@' that separates the name and address. The name should be the first piece and the address should be the second piece. The address must have a '.' which separates the domain name.
  16. Click [Submit].
  17. Access the 'Admission' form for the client admitted in the previous steps.
  18. Click [Edit] for the episode added in the previous steps.
  19. Validate the previously filed data is displayed.
  20. Select the "Demographics" section.
  21. Validate the 'Client's Email Address' field contains "test@gmail.com".
  22. Close the form.
Scenario 3: 'Update Client Data' - Verification of form filing
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Enter "testgmailcom" in the 'Client's Email Address' field.
  3. Validate a message is displayed stating: Please enter a valid email address.
  4. Click [OK].
  5. Enter "testgmail.com" in the 'Client's Email Address' field.
  6. Validate a message is displayed stating: Please enter a valid email address.
  7. Click [OK].
  8. Enter "testgmail@com" in the 'Client's Email Address' field.
  9. Validate a message is displayed stating: Please enter a valid email address.
  10. Click [OK].
  11. Enter "test@gmail.com" in the 'Client's Email Address' field.
  12. Please note: a valid email address should contain '@' that separates the name and address. The name should be the first piece and the address should be the second piece. The address must have a '.' which separates the domain name.
  13. Click [Submit].
  14. Select "Client A" and access the 'Update Client Data' form.
  15. Validate the previously filed data is displayed.
  16. Validate the 'Client's Email Address' field contains "test@gmail.com".
  17. Close the form.
Scenario 4: 'Discharge' form - Field Validation
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Discharge' form.
  2. Select an existing episode and click [Edit].
  3. Enter the desired date in the 'Date Of Discharge' field.
  4. Enter the desired time in the 'Discharge Time' field.
  5. Select the desired value in the 'Type Of Discharge' field.
  6. Select the desired practitioner in the 'Discharge Practitioner' field.
  7. Select the "Demographics" section.
  8. Enter "testgmailcom" in the 'Client's Email Address' field.
  9. Validate a message is displayed stating: Please enter a valid email address.
  10. Click [OK].
  11. Enter "testgmail.com" in the 'Client's Email Address' field.
  12. Validate a message is displayed stating: Please enter a valid email address.
  13. Click [OK].
  14. Enter "testgmail@com" in the 'Client's Email Address' field.
  15. Validate a message is displayed stating: Please enter a valid email address.
  16. Click [OK].
  17. Enter "test@gmail.com" in the 'Client's Email Address' field.
  18. Please note: a valid email address should contain '@' that separates the name and address. The name should be the first piece and the address should be the second piece. The address must have a '.' which separates the domain name.
  19. Click [Submit].
  20. Select "Client A" and access the 'Discharge' form.
  21. Select the discharged episode and click [Edit].
  22. Validate all previously filed data is displayed.
  23. Select the "Demographics" section.
  24. Validate the 'Client's Email Address' field contains "test@gmail.com".
  25. Close the form.
Scenario 5: 'Pre Admit' form - Field Validation
Specific Setup:
  • A client is enrolled in an existing Pre Admit episode (Client A).
Steps
  1. Select "Client A" and access the 'Pre Admit' form.
  2. Select an existing episode and click [Edit].
  3. Select the "Demographics" section.
  4. Enter "testgmailcom" in the 'Client's Email Address' field.
  5. Validate a message is displayed stating: Please enter a valid email address.
  6. Click [OK].
  7. Enter "testgmail.com" in the 'Client's Email Address' field.
  8. Validate a message is displayed stating: Please enter a valid email address.
  9. Click [OK].
  10. Enter "testgmail@com" in the 'Client's Email Address' field.
  11. Validate a message is displayed stating: Please enter a valid email address.
  12. Click [OK].
  13. Enter "test@gmail.com" in the 'Client's Email Address' field.
  14. Please note: a valid email address should contain '@' that separates the name and address. The name should be the first piece and the address should be the second piece. The address must have a '.' which separates the domain name.
  15. Click [Submit].
  16. Select "Client A" and access the 'Pre Admit' form.
  17. Select an existing episode and click [Edit].
  18. Select the "Demographics" section.
  19. Validate the 'Client's Email Address' field contains "test@gmail.com".
  20. Close the form.
Scenario 6: 'Call Intake' form - Field Validation
Specific Setup:
  • The 'Add Demographics To Call Intake' registry setting must be set to "Y".
  • A client is enrolled in an existing Call Intake program (Client A).
Steps
  1. Select "Client A" and access the 'Call Intake' form.
  2. Select the existing call intake record and click [Edit].
  3. Select the "Demographics" section.
  4. Enter "testgmailcom" in the 'Client's Email Address' field.
  5. Validate a message is displayed stating: Please enter a valid email address.
  6. Click [OK].
  7. Enter "testgmail.com" in the 'Client's Email Address' field.
  8. Validate a message is displayed stating: Please enter a valid email address.
  9. Click [OK].
  10. Enter "testgmail@com" in the 'Client's Email Address' field.
  11. Validate a message is displayed stating: Please enter a valid email address.
  12. Click [OK].
  13. Enter "test@gmail.com" in the 'Client's Email Address' field.
  14. Please note: a valid email address should contain '@' that separates the name and address. The name should be the first piece and the address should be the second piece. The address must have a '.' which separates the domain name.
  15. Click [Submit].
  16. Select "Client A" and access the 'Call Intake' form.
  17. Select the existing call intake record and click [Edit].
  18. Validate the 'Client's Email Address' field contains "test@gmail.com".
  19. Close the form.
Scenario 7: Discharge a client via the 'ClientDischarge' web service
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access SoapUI for the 'ClientDischarge' - 'DischargeClient' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter the desired date in the 'DateOfDischarge' field.
  6. Enter the desired practitioner in the 'DischargePractitioner' field.
  7. Enter the desired time in the 'DischargeTime' field.
  8. Enter the desired value in the 'TypeOfDischarge' field.
  9. Enter the desired value in the 'AddresType' field.
  10. Enter "Client A" in the 'ClientID' field.
  11. Enter the episode number to be discharged in the 'EpisodeNumber' field.
  12. Enter "test.gmailcom" in the 'ClientEmailAddress' field.
  13. Click [Run].
  14. Validate a message is displayed stating: Please enter a valid email address.
  15. Enter "test@gmail.com" in the 'ClientEmailAddress' field.
  16. Click [Run].
  17. Validate the 'Message' field contains: Client Discharge web service has been filed successfully.
  18. Select "Client A" and access the 'Discharge' form.
  19. Validate all populated fields are displayed as entered in the web service.
  20. Select the "Demographics" section.
  21. Validate the 'Client's Email Address' field contains "test@gmail.com".
  22. Close the form.
Scenario 8: Client Demographic Web Service validation
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access SoapUI for the 'ClientDemographics' - 'UpdateClientDemographics' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Populate any other desired fields.
  6. Enter "Client A" in the 'ClientID' field.
  7. Enter "test@gmailcom" in the 'ClientEmailAddress' field.
  8. Click [Run].
  9. Validate a message is displayed stating: Please enter a valid email address.
  10. Enter "test@gmail.com" in the 'ClientEmailAddress' field.
  11. Click [Run].
  12. Validate the 'Message' field contains: Client Demographics web service has been filed successfully.
  13. Select "Client A" and access the 'Update Client Data' form.
  14. Validate all populated fields are displayed.
  15. Validate the 'Address Type' field contains the value entered via web service.
  16. Validate the 'Client's Email Address' field contains "test@gmail.com".
  17. Close the form.
Scenario 9: The 'ClientAdmission' - 'UpdateAdmission' web service: Update Admission for an existing client
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Access SoapUI for the 'ClientAdmission' - 'UpdateAdmission' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Populate all required and desired fields.
  6. Enter "Client A" in the 'ClientID' field.
  7. Enter "Client A's" episode in the 'Episode' field.
  8. Enter "test@gmailcom" in the 'ClientEmailAddress' field.
  9. Click [Run].
  10. Validate a message is displayed stating: Please enter a valid email address.
  11. Enter "test@gmail.com" in the 'ClientEmailAddress' field.
  12. Click [Run].
  13. Validate the 'Confirmation' field contains a value such as: "Client Unique ID: # Unique ID: #".
  14. Validate the 'Message' field contains: "Client Admission web service has been filed successfully".
  15. Select "Client A" and access the 'Admission' form.
  16. Select the admission updated in the previous steps and click [Edit].
  17. Validate all populated fields are displayed.
  18. Validate the 'Client's Email Address' field contains "test@gmail.com".
  19. Close the form.
Scenario 10: Call Intake Web Service validation - ClientCallIntake
Steps
  1. Using Avatar PM 'ClientCallIntake' web service, submit an Intake record for a 'Call Intake' client:
  2. Populate all required fields.
  3. Enter "test@gmailcom" in the 'ClientEmailAddress' field.
  4. Click [Run].
  5. Validate a message is displayed stating: Please enter a valid email address.
  6. Enter "test@gmail.com" in the 'ClientEmailAddress' field.
  7. Click [Run].
  8. Click [Run].
  9. Ensure that Call Intake record returns 'Client Call Intake web service has been filed successfully' message.
  10. Ensure that 'Call Intake' record/episode filed via web service is present with values filed via the web service, including the 'Client's Email Address' field.
Scenario 11: 'Admission (Outpatient)' - Verification of form filing
Steps
  1. Access the 'Admission (Outpatient)' form.
  2. Admit a new client.
  3. Populate all required and desired fields.
  4. Select the "Demographics" section.
  5. Enter "testgmailcom" in the 'Client's Email Address' field.
  6. Validate a message is displayed stating: Please enter a valid email address.
  7. Click [OK].
  8. Enter "testgmail.com" in the 'Client's Email Address' field.
  9. Validate a message is displayed stating: Please enter a valid email address.
  10. Click [OK].
  11. Enter "testgmail@com" in the 'Client's Email Address' field.
  12. Validate a message is displayed stating: Please enter a valid email address.
  13. Click [OK].
  14. Enter "test@gmail.com" in the 'Client's Email Address' field.
  15. Please note: a valid email address should contain '@' that separates the name and address. The name should be the first piece and the address should be the second piece. The address must have a '.' which separates the domain name.
  16. Click [Submit].
  17. Access the 'Admission (Outpatient)' form for the client admitted in the previous steps.
  18. Click [Edit] for the episode added in the previous steps.
  19. Validate the previously filed data is displayed.
  20. Select the "Demographics" section.
  21. Validate the 'Client's Email Address' field contains "test@gmail.com".
  22. Close the form.
Scenario 12: 'Pre Admit Discharge' - Verification of form filing
Specific Setup:
  • A client is enrolled in an existing Pre Admit episode (Client A).
Steps
  1. Select "Client A" and access the 'Pre Admit Discharge' form.
  2. Select an existing episode and click [OK].
  3. Enter the desired date in the 'Date Of Discharge' field.
  4. Enter the desired time in the 'Time Of Discharge' field.
  5. Select the desired value in the 'Type Of Discharge' field.
  6. Select the desired practitioner in the 'Discharge Practitioner' field.
  7. Select the "Demographics" section.
  8. Enter "testgmailcom" in the 'Client's Email Address' field.
  9. Validate a message is displayed stating: Please enter a valid email address.
  10. Click [OK].
  11. Enter "testgmail.com" in the 'Client's Email Address' field.
  12. Validate a message is displayed stating: Please enter a valid email address.
  13. Click [OK].
  14. Enter "testgmail@com" in the 'Client's Email Address' field.
  15. Validate a message is displayed stating: Please enter a valid email address.
  16. Click [OK].
  17. Enter "test@gmail.com" in the 'Client's Email Address' field.
  18. Please note: a valid email address should contain '@' that separates the name and address. The name should be the first piece and the address should be the second piece. The address must have a '.' which separates the domain name.
  19. Click [Submit].
  20. Select "Client A" and access the 'Pre Admit Discharge' form.
  21. Select the discharged episode and click [OK].
  22. Validate the previously filed data is displayed.
  23. Select the "Demographics" section.
  24. Validate the 'Client's Email Address' field contains "test@gmail.com".
  25. Close the form.
Topics
• Admission • Update Client Data • Discharge • Pre Admit • Call Intake • Admission (Outpatient) • Pre Admit Discharge
2023 Update 145 Summary | Details
Rule Based Routing - 'Routing Admin Dashboard' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Rule Based Routing
  • Routing Worklist Item
  • Routing Admin Dashboard
Scenario 1: Routing Admin Dashboard - View/Edit Form
Specific Setup:
  • The system is configured for Rule Based Routing.
  • A document must exist that has passed through the 'Coding QA' form.
Steps
  1. Open the 'Routing Admin Dashboard' form.
  2. Select "Coding" from the 'Queue' field.
  3. Click [Search].
  4. Select any row from the 'Results' grid.
  5. Click [View Summary].
  6. Select a row.
  7. Click [View/Edit Form].
  8. Add a new row to the 'Diagnoses' Table.
  9. Add a new row to the 'Services' table pointing to a valid Diagnoses Row ID.
  10. Click [Save] and [Close].
  11. Select the same row from the "Results" Table.
  12. Click [View Summary].
  13. Select the desired row from the "Document Summary" table.
  14. Click [View/Edit Form].
  15. Validate the form displays as it was entered.
  16. Click [Cancel], [Close] and [Exit Form].
Topics
• Rule Based Routing
2023 Update 152 Summary | Details
Program Maintenance - Day Program support
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
  • Day Program Attendance Widget
Scenario 1: Program Maintenance - Day Program validations
Steps
  1. Access the 'Program Maintenance' form.
  2. Select "Add" in the 'Add or Edit Program' field.
  3. Enter the desired value in the 'Program Code' field.
  4. Enter the desired value in the 'Description' field.
  5. Populate all required and desired fields.
  6. Validate the 'Is This A Day Program' field is displayed.
  7. Validate the 'Day Program Missed Visit Service Code' field is displayed and initially disabled.
  8. Select "No" in the 'Is This A Day Program' field.
  9. Validate the 'Day Program Missed Visit Service Code' field remains disabled.
  10. Select the "Day Program Services" section.
  11. Validate a message is displayed stating: This is not a Day Program, please select "Yes" to the 'Is This A Day Program?' prompt.
  12. Click [OK].
  13. Select the "Day Program Schedule" section.
  14. Validate a message is displayed stating: This is not a Day Program, please select "Yes" to the 'Is This A Day Program?' prompt.
  15. Click [OK].
  16. Select the "Day Program Schedule Exceptions" section.
  17. Validate a message is displayed stating: This is not a Day Program, please select "Yes" to the 'Is This A Day Program?' prompt.
  18. Click [OK].
  19. Select "Yes" in the 'Is This A Day Program' field.
  20. Validate the 'Day Program Missed Visit Service Code' field is now enabled and required.
  21. Select the desired value in the 'Day Program Missed Visit Service Code' field.
  22. Select the "Day Program Services" section.
  23. Select "Add" in the 'Add/Edit/Delete' field.
  24. Select the desired service code in the 'Service' field.
  25. Enter the desired date in the 'Effective Date' field.
  26. Click [Save].
  27. Validate the 'Service' field contains the service added with all populated details.
  28. Select "Edit" in the 'Add/Edit/Delete' field.
  29. Select the service filed in the previous steps in the 'Select Existing' field.
  30. Validate all previously populated data is displayed.
  31. Enter the desired value in the 'Effective End Date' field.
  32. Click [Save].
  33. Validate the 'Service' field contains the updated service details.
  34. Select "Add" in the 'Add/Edit/Delete' field.
  35. Select a different service code in the 'Service' field.
  36. Enter the desired date in the 'Effective Date' field.
  37. Click [Save].
  38. Validate the 'Service' field contains the second service added with all populated details.
  39. Select "Delete" in the 'Add/Edit/Delete' field.
  40. Select the second service in the 'Select Existing' field.
  41. Validate all previously populated data is displayed and fields are disabled.
  42. Click [Save].
  43. Validate the 'Service' field no longer contains the second service.
  44. Select the "Day Program Schedule" section.
  45. Select "Add" in the 'Add/Edit/Delete' field.
  46. Enter the desired date in the 'Hours Effective Date' field.
  47. Select the desired day in the 'Day' field.
  48. Enter the desired time in the 'Start Time' field.
  49. Enter the desired time in the 'End Time' field.
  50. Click [Save Schedule].
  51. Validate the 'Program Schedule' field contains the schedule added with all populated details.
  52. Select "Edit" in the 'Add/Edit/Delete' field.
  53. Select the schedule filed in the previous steps in the 'Select Existing' field.
  54. Validate all previously populated data is displayed.
  55. Enter the desired date in the 'Effective End Date' field.
  56. Click [Save].
  57. Validate the 'Program Schedule' field contains the updated schedule details.
  58. Select "Add" in the 'Add/Edit/Delete' field.
  59. Enter the desired date in the 'Hours Effective Date' field.
  60. Select a different day in the 'Day' field.
  61. Enter the desired time in the 'Start Time' field.
  62. Enter the desired time in the 'End Time' field.
  63. Click [Save Schedule].
  64. Validate the 'Program Schedule' field contains the second schedule added with all populated details.
  65. Select "Delete" in the 'Add/Edit/Delete' field.
  66. Select the second schedule in the 'Select Existing' field.
  67. Validate all previously populated data is displayed and fields are disabled.
  68. Click [Save].
  69. Validate the 'Program Schedule' field no longer contains the second schedule.
  70. Select the "Day Program Schedule Exceptions" section.
  71. Select "Add" in the 'Add/Edit/Delete' field.
  72. Enter the desired date in the 'Exception Date' field.
  73. Click [Save].
  74. Validate the 'Exception Dates' field contains the exception added with all populated details.
  75. Select "Edit" in the 'Add/Edit/Delete' field.
  76. Select the exception filed in the previous steps in the 'Select Existing' field.
  77. Change the date in the 'Exception Date' field.
  78. Click [Save].
  79. Validate the 'Exception Dates' field contains the updated exception date.
  80. Select "Add" in the 'Add/Edit/Delete' field.
  81. Enter a new date in the 'Exception Date' field.
  82. Click [Save].
  83. Validate the 'Exception Dates' field contains the exception added with all populated details.
  84. Select "Delete" in the 'Add/Edit/Delete' field.
  85. Select the second exception filed in the previous steps in the 'Select Existing' field.
  86. Validate all previously populated data is displayed and fields are disabled.
  87. Click [Save].
  88. Validate the 'Exception Dates' field no longer contains the second exception date.
  89. Select the "Program Maintenance" section.
  90. Click [File Program].
  91. Select "Edit" in the 'Add Or Edit Program' field.
  92. Select the program filed in the previous steps in the 'Program' field.
  93. Validate all previously filed data is displayed.
  94. Close the form.
Scenario 2: File Import - Program Maintenance - Day Program validations
Specific Setup:
  • Must have valid import files for the following file types:
  • Program Maintenance (File A)
  • "Yes" must be selected in the 'Is This A Day Program?' field and must have a value entered in the 'Day Program Missed Visit Service Code' field.
  • Day Program Services (File B)
  • Day Program Schedule (File C)
  • Day Program Schedule Exception (File D)
Steps
  1. Access the 'File Import' form.
  2. Select "Program Maintenance" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Navigate to "File A" and select it for upload.
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select "File A" in the 'File(s)' field.
  8. Click [Process Action].
  9. Validate a message stating: Compiled.
  10. Click [OK].
  11. Select "Post File" in the 'Action' field.
  12. Select "File A" in the 'File(s)' field.
  13. Click [Process Action].
  14. Validate a message stating: Posted.
  15. Click [OK].
  16. Select "Day Program Services" in the 'File Type' field.
  17. Select "Upload New File" in the 'Action' field.
  18. Click [Process Action].
  19. Navigate to "File B" and select it for upload.
  20. Select "Compile/Validate File" in the 'Action' field.
  21. Select "File B" in the 'File(s)' field.
  22. Click [Process Action].
  23. Validate a message stating: Compiled.
  24. Click [OK].
  25. Select "Post File" in the 'Action' field.
  26. Select "File B" in the 'File(s)' field.
  27. Click [Process Action].
  28. Validate a message stating: Posted.
  29. Click [OK].
  30. Select "Day Program Schedule" in the 'File Type' field.
  31. Select "Upload New File" in the 'Action' field.
  32. Click [Process Action].
  33. Navigate to "File C" and select it for upload.
  34. Select "Compile/Validate File" in the 'Action' field.
  35. Select "File C" in the 'File(s)' field.
  36. Click [Process Action].
  37. Validate a message stating: Compiled.
  38. Click [OK].
  39. Select "Post File" in the 'Action' field.
  40. Select "File C" in the 'File(s)' field.
  41. Click [Process Action].
  42. Validate a message stating: Posted.
  43. Click [OK].
  44. Select "Day Program Schedule Exception" in the 'File Type' field.
  45. Select "Upload New File" in the 'Action' field.
  46. Click [Process Action].
  47. Navigate to "File D" and select it for upload.
  48. Select "Compile/Validate File" in the 'Action' field.
  49. Select "File D" in the 'File(s)' field.
  50. Click [Process Action].
  51. Validate a message stating: Compiled.
  52. Click [OK].
  53. Select "Post File" in the 'Action' field.
  54. Select "File D" in the 'File(s)' field.
  55. Click [Process Action].
  56. Validate a message stating: Posted.
  57. Close the form.
  58. Access the 'Program Maintenance' form.
  59. Select "Edit" in the 'Add Or Edit Program' field.
  60. Select the program imported in the previous steps in the 'Program' field.
  61. Validate all previously imported data is displayed.
  62. Validate "Yes" is selected in the 'Is This A Day Program?' field.
  63. Validate the 'Day Program Missed Visit Service Code' field contains the imported value.
  64. Select the "Day Program Services" section.
  65. Validate all imported data is displayed as expected.
  66. Select the "Day Program Schedule" section.
  67. Validate all imported data is displayed as expected.
  68. Select the "Day Program Schedule Exceptions" section.
  69. Validate all imported data is displayed as expected.
  70. Close the form.
Single Program Maintenance - Day Program support
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
  • Day Program Attendance Widget
Scenario 1: Single Program Maintenance - Day Program validations
Steps
  1. Access the ' Single Program Maintenance' form.
  2. Enter any new value in the 'Select Program' field and click [New Program].
  3. Populate all required and desired fields.
  4. Validate the 'Is This A Day Program' field is displayed.
  5. Validate the 'Day Program Missed Visit Service Code' field is displayed and initially disabled.
  6. Select "No" in the 'Is This A Day Program' field.
  7. Validate the 'Day Program Missed Visit Service Code' field remains disabled.
  8. Select the "Day Program Services" section.
  9. Validate a message is displayed stating: This is not a Day Program, please select "Yes" to the 'Is This A Day Program?' prompt.
  10. Click [OK].
  11. Select the "Day Program Schedule" section.
  12. Validate a message is displayed stating: This is not a Day Program, please select "Yes" to the 'Is This A Day Program?' prompt.
  13. Click [OK].
  14. Select the "Day Program Schedule Exceptions" section.
  15. Validate a message is displayed stating: This is not a Day Program, please select "Yes" to the 'Is This A Day Program?' prompt.
  16. Click [OK].
  17. Select "Yes" in the 'Is This A Day Program' field.
  18. Validate the 'Day Program Missed Visit Service Code' field is now enabled and required.
  19. Select the desired value in the 'Day Program Missed Visit Service Code' field.
  20. Select the "Day Program Services" section.
  21. Select "Add" in the 'Add/Edit/Delete' field.
  22. Select the desired service code in the 'Service' field.
  23. Enter the desired date in the 'Effective Date' field.
  24. Click [Save].
  25. Validate the 'Service' field contains the service added with all populated details.
  26. Select "Edit" in the 'Add/Edit/Delete' field.
  27. Select the service filed in the previous steps in the 'Select Existing' field.
  28. Validate all previously populated data is displayed.
  29. Enter the desired value in the 'Effective End Date' field.
  30. Click [Save].
  31. Validate the 'Service' field contains the updated service details.
  32. Select "Add" in the 'Add/Edit/Delete' field.
  33. Select a different service code in the 'Service' field.
  34. Enter the desired date in the 'Effective Date' field.
  35. Click [Save].
  36. Validate the 'Service' field contains the second service added with all populated details.
  37. Select "Delete" in the 'Add/Edit/Delete' field.
  38. Select the second service in the 'Select Existing' field.
  39. Validate all previously populated data is displayed and fields are disabled.
  40. Click [Save].
  41. Validate the 'Service' field no longer contains the second service.
  42. Select the "Day Program Schedule" section.
  43. Select "Add" in the 'Add/Edit/Delete' field.
  44. Enter the desired date in the 'Hours Effective Date' field.
  45. Select the desired day in the 'Day' field.
  46. Enter the desired time in the 'Start Time' field.
  47. Enter the desired time in the 'End Time' field.
  48. Click [Save Schedule].
  49. Validate the 'Program Schedule' field contains the schedule added with all populated details.
  50. Select "Edit" in the 'Add/Edit/Delete' field.
  51. Select the schedule filed in the previous steps in the 'Select Existing' field.
  52. Validate all previously populated data is displayed.
  53. Enter the desired date in the 'Effective End Date' field.
  54. Click [Save].
  55. Validate the 'Program Schedule' field contains the updated schedule details.
  56. Select "Add" in the 'Add/Edit/Delete' field.
  57. Enter the desired date in the 'Hours Effective Date' field.
  58. Select a different day in the 'Day' field.
  59. Enter the desired time in the 'Start Time' field.
  60. Enter the desired time in the 'End Time' field.
  61. Click [Save Schedule].
  62. Validate the 'Program Schedule' field contains the second schedule added with all populated details.
  63. Select "Delete" in the 'Add/Edit/Delete' field.
  64. Select the second schedule in the 'Select Existing' field.
  65. Validate all previously populated data is displayed and fields are disabled.
  66. Click [Save].
  67. Validate the 'Program Schedule' field no longer contains the second schedule.
  68. Select the "Day Program Schedule Exceptions" section.
  69. Select "Add" in the 'Add/Edit/Delete' field.
  70. Enter the desired date in the 'Exception Date' field.
  71. Click [Save].
  72. Validate the 'Exception Dates' field contains the exception added with all populated details.
  73. Select "Edit" in the 'Add/Edit/Delete' field.
  74. Select the exception filed in the previous steps in the 'Select Existing' field.
  75. Change the date in the 'Exception Date' field.
  76. Click [Save].
  77. Validate the 'Exception Dates' field contains the updated exception date.
  78. Select "Add" in the 'Add/Edit/Delete' field.
  79. Enter a new date in the 'Exception Date' field.
  80. Click [Save].
  81. Validate the 'Exception Dates' field contains the exception added with all populated details.
  82. Select "Delete" in the 'Add/Edit/Delete' field.
  83. Select the second exception filed in the previous steps in the 'Select Existing' field.
  84. Validate all previously populated data is displayed and fields are disabled.
  85. Click [Save].
  86. Validate the 'Exception Dates' field no longer contains the second exception date.
  87. Select the "Program Maintenance" section.
  88. Click [Submit].
  89. Access the 'Single Program Maintenance' form.
  90. Select the program added in the previous steps in the 'Select Program' field and click [OK].
  91. Select the program filed in the previous steps in the 'Program' field.
  92. Validate all previously filed data is displayed.
  93. Close the form.
'Client Program Schedule Exceptions' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • View Definition
  • Day Program Attendance Widget
  • Program Maintenance
  • Client Program Schedule Exceptions
Scenario 1: Patient Calendar - Validate Day Program Attendance placeholders
Specific Setup:
  • Please note: This is for Avatar NX only. Avatar PM 2023 Update 152, Avatar Appointment Scheduling 2023 Update 32, and Avatar NX Release 2024.01.00 are required for this functionality.
Steps
  1. Access the 'Program Maintenance' form.
  2. Select "Add" in the 'Add Or Edit Program' field.
  3. Enter the desired value in the 'Program Code' field. Note: this will now be referred to as "Program A".
  4. Enter the desired value in the 'Description' field.
  5. Populate all other required fields.
  6. Select “Both” in the ‘Usage Type’ field.
  7. Select “Yes” in the ‘Is This A Day Program?’ field.
  8. Select the desired value in the 'Day Program Missed Visit Service Code' field.
  9. Navigate to the 'Day Program Services' section.
  10. Select "Add" in the 'Add/Edit/Delete' field.
  11. Select the desired value in the 'Service' field.
  12. Enter "01/01/2024" in the 'Effective Date' field.
  13. Click [Save].
  14. Navigate to the 'Day Program Schedule' section.
  15. Select "Add" in the 'Add/Edit/Delete' field.
  16. Enter "01/01/2024" in the 'Hours Effective Date' field.
  17. Enter "01/02/2025" in the 'Hours End Date' field.
  18. Select "Monday" in the 'Day' field.
  19. Enter "9:00 AM" in the 'Start Time' field.
  20. Enter "12:00 PM" in the 'End Time' field.
  21. Click [Save Schedule].
  22. Repeat steps 1n-1t for the remaining week days.
  23. Navigate to the 'Day Program Schedule Exceptions' section.
  24. Select "Add" in the 'Add/Edit/Delete' field.
  25. Enter "01/10/2024" in the 'Exception Date' field.
  26. Click [Save].
  27. Navigate to the 'Program Maintenance' section.
  28. Click [File Program] and close the form.
  29. Access the 'Admission' form.
  30. Admit a new client into "Program A". This will now be referred to as "Client A".
  31. Populate all required and desired fields.
  32. Click [Submit].
  33. Access the 'Scheduling Calendar' form.
  34. Select "Patient" in the calendar 'Filter' field.
  35. Search for and select "Client A" in the 'Patient Search' field.
  36. Validate the 'Recent' list now contains "Client A".
  37. Select the current date.
  38. Validate a "Program" placeholder is displayed on the calendar for the day program from 9:00 AM to 12:00 PM.
  39. Select any date prior to "01/01/2024".
  40. Validate a "Program" placeholder is not displayed on the calendar since this is prior to the 'Hours Effective Date' for the day program schedule.
  41. Select any date after "01/01/2025".
  42. Validate a "Program" placeholder is not displayed on the calendar since this is after the 'Hours End Date' for the day program schedule.
  43. Select "01/10/2024" as the date.
  44. Validate a "Program" placeholder is not displayed since there is an 'Exception' defined for the date.
  45. Select the current date.
  46. Validate the "Program" placeholder is displayed on the calendar for the day program from 9:00 AM to 12:00 PM.
  47. Click [Dismiss] and [Yes].
  48. Select "Client A" and access the 'Client Program Schedule Exceptions' form.
  49. Select "Add" in the 'Add/Edit/Delete' field.
  50. Select "Program A" in the 'Program' field.
  51. Select "Specific Date" in the 'Exception Type' field.
  52. Enter the current date in the 'Specific Date' field.
  53. Enter the desired value in the 'Reason' field.
  54. Click [Save] and [Submit].
  55. Access the 'Scheduling Calendar' form.
  56. Validate "Client A" is still selected in the 'Recent' list.
  57. Select the current date.
  58. Validate the "Program" placeholder is no longer displayed since a client exception was added for the current date.
  59. Select any other date within the effective day program schedule.
  60. Validate the "Program" placeholder is displayed on the calendar for the day program from 9:00 AM to 12:00 PM.
  61. Click [Dismiss] and [Yes].
Scenario 2: Client Program Schedule Exception - Form Validations
Specific Setup:
  • Please note: this is for Avatar NX only.
  • The 'Day Program Attendance' widget must be added to a view in 'View Definition'.
  • The logged in user must have the 'Day Program Attendance' widget accessible from their myDay view.
  • A program is defined in 'Program Maintenance' with the following (Program A):
  • "Yes" selected in the 'Is This A Day Program?' field.
  • A service code selected in the 'Day Program Missed Visit Service Code' field.
  • A service code selected in the 'Day Program Services' section (Service Code A).
  • A schedule configured for Monday through Friday in the 'Day Program Schedule' section.
  • A client is admitted into "Program A" (Client A).
Steps
  1. Select "Client A" and access the 'Client Program Schedule Exceptions' form.
  2. Select "Add" in the 'Add/Edit/Delete' field.
  3. Select "Program A" in the 'Program' field.
  4. Select "Range" in the 'Exception Type' field.
  5. Validate the 'Day of Week' field becomes enabled and required.
  6. Select "Friday" in the 'Day of Week' field.
  7. Enter the current date in the 'Start Date' field.
  8. Enter the desired value in the 'Reason' field.
  9. Click [Save] and submit the form.
  10. Select "Client A" and access the 'Client Program Schedule Exceptions' form.
  11. Select "Edit" in the 'Add/Edit/Delete' field.
  12. Select the exception added in the previous steps in the 'Select Existing' field.
  13. Validate all previously filed data is displayed.
  14. Select "Specific Date" in the 'Exception Type' field.
  15. Validate the 'Days of Week' field is now disabled
  16. Validate the 'Specific Date' field is now enabled and required.
  17. Enter the desired date in the 'Specific Date' field.
  18. Click [Save] and [Submit].
  19. Select "Client A" and access the 'Client Program Schedule Exceptions' form.
  20. Select "Delete" in the 'Add/Edit/Delete' field.
  21. Select the exception added in the previous steps in the 'Select Existing' field.
  22. Validate all previously filed data is displayed and fields are disabled.
  23. Click [Save] and [Submit].
  24. Select "Client A" and access the 'Client Program Schedule Exceptions' form.
  25. Select "Edit" in the 'Add/Edit/Delete' field.
  26. Validate the 'Select Existing' field no longer contains the deleted exception.
  27. Close the form.
The 'Day Program Attendance' widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • View Definition
  • Day Program Attendance Widget
  • Client Ledger
  • Change MR#
Scenario 1: Day Program Attendance widget - Field Validations
Specific Setup:
  • Please note: this is for Avatar NX only.
  • The 'Day Program Attendance' widget must be added to a view in 'View Definition'.
  • The logged in user must have the 'Day Program Attendance' widget accessible from their myDay view.
  • A program is defined in 'Program Maintenance' with the following (Program A):
  • "Yes" selected in the 'Is This A Day Program?' field.
  • A service code selected in the 'Day Program Missed Visit Service Code' field.
  • A service code selected in the 'Day Program Services' section (Service Code A).
  • A schedule configured for Monday through Friday in the 'Day Program Schedule' section.
  • A client is admitted into "Program A" (Client A).
Steps
  1. Navigate to the 'Day Program Attendance' widget.
  2. Select "Program A" in the 'Program' field.
  3. Select the desired practitioner in the 'Practitioner' field.
  4. Validate the 'Client' search field is displayed.
  5. Validate the 'Episode' field is displayed.
  6. Validate the [Add Client] button is displayed.
  7. Validate the 'Start Time' field is displayed. This should contain the scheduled start time for "Program A" in the "Day Program Schedule" section of 'Program Maintenance'.
  8. Validate the 'Service' field is displayed. This should contain the service(s) for "Program A" in the 'Day Program Services" section of 'Program Maintenance'.
  9. Validate the [Default Start] button is displayed.
  10. Validate the 'Close Time' field is displayed. This should contain the end time for "Program A" in the "Day Program Schedule" section of 'Program Maintenance'.
  11. Validate the [Complete Close] button is displayed.
  12. Validate the following columns are displayed for the client rows within the widget:
  13. 'Name' - Client name will appear for the first row for a client. Subsequent rows will only contain the 'PATID'.
  14. 'PATID' - Patient ID
  15. 'Ep' - Episode Number
  16. 'In' - Check In Time
  17. 'Out' - Check Out Time
  18. 'Service' - The service the client is checking in for
  19. 'Return' - The 'Return' icon will be used to create a subsequent row after a check out is done
  20. 'Length' - Calculated time in minutes between check in and check out. If a check in is filed and no check out has been filed, time will display based on the check in time to current time
  21. 'Total' - Calculated total time for the client including all check ins per selected service
  22. 'Reason' - Icon that will launch a free-text area to enter a reason for check out or late arrival
  23. 'Add Appt' - Icon that will appear on the first main row for a client and will launch the 'Scheduling Calendar - Appointment Details' form to add a new client appointment
  24. 'Remove' - Icon that will first remove 'Out' time (if entered), and then can remove the row entirely
  25. Click [Default Start].
  26. Validate the 'In' and 'Service' fields have defaulted in for all clients who did not have values populated.
  27. Validate the 'Length' and 'Total' fields contain the total time that has passed (in minutes) since the 'In' time, with a * to indicate this is a running count.
  28. Enter the desired time in the 'Out' field.
  29. Validate the 'Length' and 'Total' fields contain the total time that has passed (in minutes) between the 'In' and 'Out' times.
  30. Validate the [Reason] icon is green in color.
  31. Click on the [Reason] icon.
  32. Validate a 'Reason' dialog is displayed.
  33. Enter the desired value in the 'Reason' field, such as the client's reason for check out.
  34. Click [Close].
  35. Validate the [Reason] icon is now black, indicating there is a reason on file.
  36. Validate the [Return] icon is displayed. The 'In', 'Out', and 'Service' fields must be populated in order for this icon to display.
  37. Click on the [Return] icon.
  38. Validate a second row is displayed for "Client A".
  39. Validate the 'In' field contains the current time.
  40. Click on the [Remove] icon.
  41. Validate the second row is no longer displayed for "Client A".
  42. Click on the [Add Appt] icon.
  43. Validate the 'Scheduling Calendar - Appointment Details' form is displayed with the following populated:
  44. Client
  45. Episode Number
  46. Program
  47. Close the form.
  48. Validate the 'Day Program Attendance' widget is displayed.
Scenario 2: Day Program Attendance Widget - Validate 'Add Appt' functionality
Specific Setup:
  • Please note: this is for Avatar NX only.
  • The 'Day Program Attendance' widget must be added to a view in 'View Definition'.
  • The logged in user must have the 'Day Program Attendance' widget accessible from their myDay view.
  • A program is defined in 'Program Maintenance' with the following (Program A):
  • "Yes" selected in the 'Is This A Day Program?' field.
  • A service code selected in the 'Day Program Missed Visit Service Code' field.
  • One or more active service codes selected in the 'Day Program Services' section.
  • A schedule configured for Monday through Friday in the 'Day Program Schedule' section.
  • A client is admitted into "Program A" (Client A).
Steps
  1. Navigate to the 'Day Program Attendance' widget.
  2. Select "Program A" in the 'Program' field.
  3. Select the desired practitioner in the 'Practitioner' field.
  4. Validate "Client A" is displayed in the 'Day Program Attendance' widget.
  5. Click on the [Add Appt] icon.
  6. Validate the 'Scheduling Calendar - Appointment Details' form is displayed.
  7. Select the desired site in the 'Appointment Site' field.
  8. Validate the 'Appointment Date' field contains the current date.
  9. Validate the 'Appointment Start Time' field contains the current time.
  10. Enter the desired value in the 'Duration' field and validate the 'Appointment End Time' field is calculated accordingly.
  11. Select the desired value in the 'Service Code' field.
  12. Validate the 'Client' field contains "Client A".
  13. Validate the 'Episode Number' field contains the episode for "Program A".
  14. Validate the 'Program' field contains "Program A".
  15. Select the desired practitioner in the 'Practitioner' field.
  16. Select the desired value in the 'Location' field.
  17. Click [Submit].
  18. Validate the 'Day Program Attendance' widget is displayed.
  19. Access the 'Scheduling Calendar' form.
  20. Validate the appointment scheduled for "Client A" is displayed for the correct start date/time/practitioner.
  21. Click [Dismiss] and [OK].
Scenario 3: Day Program Attendance Widget - Validate 'Return' functionality
Specific Setup:
  • Please note: this is for Avatar NX only.
  • The 'Day Program Attendance' widget must be added to a view in 'View Definition'.
  • The logged in user must have the 'Day Program Attendance' widget accessible from their myDay view.
  • A program is defined in 'Program Maintenance' with the following (Program A):
  • "Yes" selected in the 'Is This A Day Program?' field.
  • A service code selected in the 'Day Program Missed Visit Service Code' field.
  • One or more active service codes selected in the 'Day Program Services' section (Service Code A).
  • A schedule configured for Monday through Friday in the 'Day Program Schedule' section.
  • A client is admitted into "Program A" (Client A).
Steps
  1. Navigate to the 'Day Program Attendance' widget.
  2. Select "Program A" in the 'Program' field.
  3. Select the desired practitioner in the 'Practitioner' field.
  4. Validate "Client A" is displayed in the 'Day Program Attendance' widget.
  5. Validate the 'Start Time' and 'Close Time' fields contain the times configured in 'Program Maintenance'.
  6. Validate the row for "Client A" does not contain a value in the 'In', 'Out', and 'Service' fields.
  7. Validate the [Return] icon is not displayed.
  8. Enter the desired time in the 'In' field.
  9. Validate the [Return] icon is not displayed.
  10. Validate the 'Length' field contains a running count since the 'In' time.
  11. Enter the desired time in the 'Out' field.
  12. Validate the [Return] icon is not displayed.
  13. Validate the 'Length' field contains the total time between the 'In' and 'Out' times.
  14. Select "Service Code A" in the 'Service' field.
  15. Validate the [Return] icon is now displayed. The 'In', 'Out', and 'Service' fields must be populated in order for this icon to display.
  16. Validate the 'Total' field contains the total time between the 'In' and 'Out' times.
  17. Click on the green [Reason] icon.
  18. Validate a 'Reason' dialog is displayed.
  19. Enter the desired value in the 'Reason' field, such as the client's reason for check out.
  20. Click [Close].
  21. Validate the [Reason] icon is now black, indicating there is a reason on file.
  22. Click on the [Return] icon.
  23. Validate a second row is added for "Client A" with:
  24. 'PATID' containing the PATID for "Client A". Please note: 'Name' field will not be populated for 'Return' rows.
  25. 'In' time with the current time.
  26. 'Length' field will contain * indicating this is a running count until an 'Out' time is calculated.
  27. Validate the [Return] icon is no longer displayed for the first row for "Client A".
  28. Validate the [Return] icon is not displayed for the second row for "Client A" since 'Out' time and 'Service' are not yet populated.
  29. Enter the desired time in the 'Out' field.
  30. Validate the 'Length' field contains the total time between the 'In' and 'Out' times for the second row.
  31. Select "Service Code A" in the 'Service' field.
  32. Validate the 'Total' field contains the sum of the total times from row 1 and row 2.
  33. Validate the [Return] icon is now displayed for the second row.
Scenario 4: Day Program Attendance Widget - Validate 'Complete Close' functionality
Specific Setup:
  • Please note: this is for Avatar NX only.
  • The 'Day Program Attendance' widget must be added to a view in 'View Definition'.
  • The logged in user must have the 'Day Program Attendance' widget accessible from their myDay view.
  • A program is defined in 'Program Maintenance' with the following (Program A):
  • "Yes" selected in the 'Is This A Day Program?' field.
  • A service code selected in the 'Day Program Missed Visit Service Code' field.
  • One or more active service codes selected in the 'Day Program Services' section (Service Code A).
  • A schedule configured for Monday through Friday in the 'Day Program Schedule' section.
  • A client is admitted into "Program A" (Client A).
Steps
  1. Navigate to the 'Day Program Attendance' widget.
  2. Select "Program A" in the 'Program' field.
  3. Select the desired practitioner in the 'Practitioner' field.
  4. Validate "Client A" is displayed in the 'Day Program Attendance' widget.
  5. Validate the 'Start Time' and 'Close Time' fields contain the times configured in 'Program Maintenance'.
  6. Validate the row for "Client A" does not contain a value in the 'In', 'Out', and 'Service' fields.
  7. Click [Complete Close].
  8. Validate a message is displayed stating: All clients must have a time recorded before close can be completed.
  9. Enter the desired time in 'In' field.
  10. Enter the desired time in the 'Out' field.
  11. Validate the 'Length' field contains the total time between the 'In' and 'Out' times.
  12. Select "Service Code A" in the 'Service' field.
  13. Validate the 'Total' field contains the total time between the 'In' and 'Out' times.
  14. Click on the [Return] icon.
  15. Validate a second row is added for "Client A" with:
  16. 'PATID' containing the PATID for "Client A". Please note: 'Name' field will not be populated for 'Return' rows.
  17. 'In' time with the current time.
  18. 'Length' field will contain * indicating this is a running count until an 'Out' time is calculated.
  19. Enter the desired time in the 'Out' field.
  20. Validate the 'Length' field contains the total time between the 'In' and 'Out' times for the second row.
  21. Select "Service Code A" in the 'Service' field.
  22. Validate the 'Total' field contains the sum of the total times from row 1 and row 2.
  23. Click [Complete Close].
  24. Validate a 'Day Program Posting Authentication' dialog is displayed.
  25. Enter the logged in username in the 'User ID' field.
  26. Enter the password for the logged in user in the 'Password' field.
  27. Click [OK].
  28. Validate "Client A" is no longer displayed in the 'Day Program Attendance' widget.
  29. Validate the gray/disabled text field at the top of the widget contains: Close completed for today.
  30. Access the 'Client Ledger' form.
  31. Select "Client A" in the 'Client ID' field.
  32. Select "All Episodes" in the 'Claim/Episode/All Episodes' field.
  33. Select "Simple" in the 'Ledger Type' field.
  34. Select "Yes" in the 'Include Zero Charges' field.
  35. Click [Process].
  36. Validate the 'Client Ledger Report' contains "Service Code A".
  37. Click [Close] and close the form.
  38. Access Crystal Reports or other SQL Reporting Tool.
  39. Create a report using the 'SYSTEM.billing_tx_history' SQL table.
  40. Validate a row is displayed for the posted service for "Client A".
  41. Validate the 'duration' field contains the 'Total' from the second row for "Client A" in the 'Day Program Attendance' widget (the sum of the total times from row 1 and row 2).
  42. Close the report.
Scenario 5: Day Program Attendance Widget - Validate automatic posting process
Specific Setup:
  • Please note: this is for Avatar NX only.
  • The 'Day Program Attendance' widget must be added to a view in 'View Definition'.
  • The logged in user must have the 'Day Program Attendance' widget accessible from their myDay view.
  • A program is defined in 'Program Maintenance' with the following (Program A):
  • "Yes" selected in the 'Is This A Day Program?' field.
  • A service code selected in the 'Day Program Missed Visit Service Code' field.
  • One or more active service codes selected in the 'Day Program Services' section (Service Code A).
  • A schedule configured for Monday through Friday in the 'Day Program Schedule' section.
  • A client is admitted into "Program A" (Client A).
Steps
  1. Navigate to the 'Day Program Attendance' widget.
  2. Select "Program A" in the 'Program' field.
  3. Select the desired practitioner in the 'Practitioner' field.
  4. Validate "Client A" is displayed in the 'Day Program Attendance' widget.
  5. Validate the 'Start Time' and 'Close Time' fields contain the times configured in 'Program Maintenance'.
  6. Enter the desired time in 'In' field.
  7. Enter the desired time in the 'Out' field.
  8. Validate the 'Length' field contains the total time between the 'In' and 'Out' times.
  9. Select "Service Code A" in the 'Service' field.
  10. Validate the 'Total' field contains the total time between the 'In' and 'Out' times.
  11. An automatic posting process for the 'Day Program Attendance' widget will run after midnight and do the following:
  12. Post the services for clients in "Program A".
  13. Please note: If 'In' time is entered but no 'Out' time is entered, the 'Close Time' will act as the 'Out' time.
  14. If a client did not check in for the day, the 'Day Program Missed Visit Service Code' configured for "Program A" will be used.
  15. Wait until the next day.
  16. Access the 'Client Ledger' form.
  17. Select "Client A" in the 'Client ID' field.
  18. Select "All Episodes" in the 'Claim/Episode/All Episodes' field.
  19. Select "Simple" in the 'Ledger Type' field.
  20. Select "Yes" in the 'Include Zero Charges' field.
  21. Click [Process].
  22. Validate the 'Client Ledger Report' contains "Service Code A" for yesterday's date.
  23. Click [Close] and close the form.
  24. Access Crystal Reports or other SQL Reporting Tool.
  25. Create a report using the 'SYSTEM.billing_tx_history' SQL table.
  26. Validate a row is displayed for the posted service for "Client A" for yesterday's date.
  27. Validate the 'duration' field contains the 'Total' for "Client A" in the 'Day Program Attendance' widget.
  28. Close the report.
Scenario 6: Day Program Attendance Widget - Validate 'Change MR#' functionality
Specific Setup:
  • Please note: this is for Avatar NX only.
  • The 'Day Program Attendance' widget must be added to a view in 'View Definition'.
  • The logged in user must have the 'Day Program Attendance' widget accessible from their myDay view.
  • A program is defined in 'Program Maintenance' with the following (Program A):
  • "Yes" selected in the 'Is This A Day Program?' field.
  • A service code selected in the 'Day Program Missed Visit Service Code' field.
  • One or more active service codes selected in the 'Day Program Services' section (Service Code A).
  • A schedule configured for Monday through Friday in the 'Day Program Schedule' section.
  • A client is admitted into "Program A" (Client A).
Steps
  1. Navigate to the 'Day Program Attendance' widget.
  2. Select "Program A" in the 'Program' field.
  3. Select the desired practitioner in the 'Practitioner' field.
  4. Validate "Client A" is displayed in the 'Day Program Attendance' widget. Take note of the PATID for "Client A".
  5. Access the 'Change MR#' form.
  6. Select "Client A" in the 'Client ID' field.
  7. Click [Assign MR#] and [Yes].
  8. Validate the 'New Client ID#' field contains a new value.
  9. Click [Submit].
  10. Navigate to the 'Day Program Attendance' widget.
  11. Select "Program A" in the 'Program' field.
  12. Validate "Client A" is displayed in the 'Day Program Attendance' widget with the new PATID.
Scenario 7: Day Program Attendance Widget - Add/Remove Clients
Specific Setup:
  • Please note: this is for Avatar NX only.
  • The 'Day Program Attendance' widget must be added to a view in 'View Definition'.
  • The logged in user must have the 'Day Program Attendance' widget accessible from their myDay view.
  • A program is defined in 'Program Maintenance' with the following (Program A):
  • "Yes" selected in the 'Is This A Day Program?' field.
  • A service code selected in the 'Day Program Missed Visit Service Code' field.
  • A service code selected in the 'Day Program Services' section (Service Code A).
  • A schedule configured for Monday through Friday in the 'Day Program Schedule' section.
  • A client is admitted into "Program A" (Client A).
Steps
  1. Navigate to the 'Day Program Attendance' widget.
  2. Select "Program A" in the 'Program' field.
  3. Select the desired practitioner in the 'Practitioner' field.
  4. Validate "Client A" is displayed in the widget.
  5. Click [Default Start].
  6. Validate the 'In' and 'Service' fields are now populated for "Client A".
  7. Enter the desired time in the 'Out' field.
  8. Validate the 'Length' and 'Total' fields are calculated accordingly.
  9. Click the [Remove] icon.
  10. Validate the time in the 'Out' field has been removed.
  11. Validate the 'Length' and 'Total' fields are calculated accordingly.
  12. Click the [Remove] icon.
  13. Validate a message is displayed stating: This will remove all rows for this client. Do you want to continue?
  14. Click [Yes].
  15. Validate "Client A" is no longer displayed in the widget.
  16. Search for and select "Client A" in the 'Client' field.
  17. Select the applicable episode in the 'Episode' field.
  18. Click [Add Client].
  19. Validate "Client A" is displayed in the widget.
Topics
• Program Maintenance • File Import • Single Program Maintenance • Scheduling Calendar • Day Program Attendance • Widgets • Client Ledger
2023 Update 156 Summary | Details
CCBHC PPS Compile - Edit PPS Service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Charge Input
  • Client Ledger
  • CCBHC PPS Compile
Scenario 1: CCBHC PPS Compile - Edit PPS1 service.
Specific Setup:
  • Service Codes:
  • Service 1:
  • A PPS enumerated service code. This will be the service used in client charge input, and it will trigger Service 2 during the CCBHC PPS Compile.
  • Service 2:
  • A PPS non-enumerated service code.
  • CCBHC PPS Service definition:
  • PPS-1 definition:
  • The other definition would have an effective date that is the day after the end date in the PPS-2 definition.
  • PPS-1 Service Code is the enumerated service code (Service 1).
  • Review the dates before admitting the client so you know what admission date you want to use.
  • Dictionary Update:
  • For the 'Client' File type -> '(10006) Location' Data element, Pick a dictionary code of a location (Location 1) and set its value as 'Yes' for the Extended Dictionary Data Element-> 'CCBHC Location '
  • Guarantors/Payors:
  • Find an existing or create a Guarantor with the "CCBHC Guarantor" set as "Yes".
  • Client 1 has the following:
  • Is enrolled in a program on or after the CCBHC PPS Service Definition effective date.
  • A financial eligibility record for the CCBHC guarantor.
Steps
  1. Open the 'Client Charge Input' form.
  2. Set the 'Date Of Service' field with a date.
  3. Select Client 1 in the 'Client ID' field.
  4. Select 'Service 1' in the 'Service Code' field.
  5. Select a practitioner from the 'Practitioner' field.
  6. Select 'Location 1' from the 'Location' field.
  7. Select [Submit].
  8. Click [No].
  9. Open 'Close Charges'.
  10. Select 'Close Charges' from 'Liability Update Or Close Charges'.
  11. Select 'T' to set today's date in the 'Thru Date' field.
  12. Select 'Individual' from 'Individual, All, Or Interim Batch Cycle'.
  13. Select 'Client 1' in the 'Client ID' field.
  14. Select the episode from the 'Episode Number' field.
  15. Select [Submit].
  16. Open 'Client Ledger'.
  17. Select 'Client 1' in the 'Client ID' field.
  18. Select 'All Episodes' from 'Claim/Episode/All Episodes'.
  19. Select 'Simple' from 'Ledger Type'.
  20. Set 'From Date' and 'To Date' with the date of 'Service 1' used in Step 2.
  21. Select [Process].
  22. Validate that 'Service 1' is shown in the client's ledger.
  23. Close the report.
  24. Click [No].
  25. Open 'CCBHC PPS Compile'.
  26. Enter the first date of service with the date of 'Service 1' of 'Client 1' in 'Start Date' used in Step 2.
  27. Enter the last date of service with the date of 'Service 1' of 'Client 1' in 'Start Date' used in Step 2.
  28. Enter the 'Client ID' for 'Client 1'.
  29. Click [Compile & Post Services].
  30. Validate that the 'CCBHC Compile Complete' message is received.
  31. Click [OK].
  32. Select [Discard].
  33. Click [Yes].
  34. Open 'Client Ledger'.
  35. Select 'Client 1' in the 'Client ID' field.
  36. Select 'All Episodes' from 'Claim/Episode/All Episodes'.
  37. Select 'Simple' from 'Ledger Type'.
  38. Set 'From Date' and 'To Date' with the date of 'Service 1' used in Step 2.
  39. Select [Process].
  40. Validate that 'Service 2' is created by the 'CCBHC PPS Compile' process and shown in the client's ledger along with 'Service 1'.
  41. Close the report.
  42. Click [No].
  43. Open 'Edit Service Information'.
  44. Select 'Client 1' in the 'Client ID' field.
  45. Validate that the Episode field is populated with the corresponding Episode.
  46. Set the 'Service Start Date' and 'Service End Date' with the date of 'Service 1' used in Step 2.
  47. Click [Select Service(s) To Edit].
  48. Validate that we see both Service 1 and 2 in the 'Select Service(s) To Edit' grid.
  49. Select 'Service 2' from the grid.
  50. Click [OK].
  51. Edit the 'Modifiers text' field and set it to any desired value.
  52. Select [Submit].
  53. Click [No].
  54. Open 'CCBHC PPS Compile'.
  55. Enter the first date of service with the date of Service 1 of 'Client 1' in 'Start Date' used in Step 2.
  56. Enter the last date of service with the date of Service 1 of 'Client 1' in 'Start Date' used in Step 2.
  57. Enter the 'Client ID' for 'Client 1'.
  58. Click [Compile & Post Services].
  59. Validate that the 'CCBHC Compile Complete' message is received.
  60. Click [OK].
  61. Select [Discard].
  62. Click [Yes].
  63. Open 'Client Ledger'.
  64. Select 'Client 1' in the 'Client ID' field.
  65. Select 'All Episodes' from 'Claim/Episode/All Episodes'.
  66. Select 'Simple' from 'Ledger Type'.
  67. Set 'From Date' and 'To Date' with the date of 'Service 1' used in Step 2.
  68. Select [Process].
  69. Validate that there are no new entries added for 'Service 2' by the 'CCBHC PPS Compile' process and make sure that we still have the Services 1 and 2 alone in the client's ledger.
  70. Close the report.
  71. Click [No].
CCBHC PPS Compile
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Charge Input
  • Delete Service
  • Client Ledger
  • Open Closed Charges
  • CCBHC PPS Compile
Scenario 1: CCBHC PPS Compile - posting the CCBHC service.
Specific Setup:
  • Service Codes:
  • Service 1:
  • Is a PPS-enumerated service code. This will be the service used in client charge input, and it will trigger Service 2 during the CCBHC PPS Compile.
  • Service 2:
  • Is a PPS non-enumerated service code.
  • CCBHC PPS Service definition:
  • PPS-1 definition:
  • The other definition would have an effective date that is the day after the end date in the PPS-2 definition.
  • PPS-1 Service Code is the enumerated service code (Service 1).
  • Review the dates before admitting the client so you know what admission date you want to use.
  • PPS-2 definition:
  • Have this definition, with an effective date and end date.
  • Should contain data in the Service Code By Population section for the Population and Service Code at a minimum.
  • Dictionary Update:
  • For the 'Client' File type -> '(10006) Location' Data element, Pick a dictionary code of a location (Location 1) and set its value as 'Yes' for the Extended Dictionary Data Element-> 'CCBHC Location '
  • Guarantors/Payors:
  • Find an existing or create a Guarantor with the "CCBHC Guarantor" set as "Yes".
  • Client 1 has the following:
  • Is enrolled in a program on or after the CCBHC PPS Service Definition effective date.
  • A financial eligibility record for the CCBHC guarantor.
Steps
  1. Open the 'Client Charge Input' form.
  2. Set the 'Date Of Service' field with a date.
  3. Select 'Client 1' in the 'Client ID' field.
  4. Select 'Service 1' in the 'Service Code' field.
  5. Select a practitioner from the 'Practitioner' field.
  6. Select 'Location 1' from the 'Location' field.
  7. Select [Submit].
  8. Click [No].
  9. Open 'Close Charges'.
  10. Select 'Close Charges' from 'Liability Update Or Close Charges'.
  11. Select 'T' to set today's date in the 'Thru Date' field.
  12. Select 'Individual' from 'Individual, All, Or Interim Batch Cycle'.
  13. Select 'Client 1' in the 'Client ID' field.
  14. Select the episode from the 'Episode Number' field.
  15. Select [Submit].
  16. Open 'Client Ledger'.
  17. Select 'Client 1' in the 'Client ID' field.
  18. Select 'All Episodes' from 'Claim/Episode/All Episodes'.
  19. Select 'Simple' from 'Ledger Type'.
  20. Set 'From Date' and 'To Date' with the date of 'Service 1' used in Step 2.
  21. Select [Process].
  22. Validate that 'Service 1' is shown in the client's ledger.
  23. Close the report.
  24. Click [No].
  25. Open 'CCBHC PPS Compile'.
  26. If using a PPS-1 definition, enter the date range of services in the service date fields.
  27. If using a PPS-2 definition, enter the first and last date of the month in the service date fields.
  28. Enter the 'Client ID' for 'Client 1'.
  29. Click [Compile & Post Services].
  30. Validate that the 'CCBHC Compile Complete' message is received.
  31. Click [OK].
  32. Select [Discard].
  33. Click [Yes].
  34. Open 'Client Ledger'.
  35. Select 'Client 1' in the 'Client ID' field.
  36. Select 'All Episodes' from 'Claim/Episode/All Episodes'.
  37. Select 'Simple' from 'Ledger Type'.
  38. Set 'From Date' and 'To Date' with the date of 'Service 1' used in Step 2.
  39. Select [Process].
  40. Validate that 'Service 2' is created by the 'CCBHC PPS Compile' process and shown in the client's ledger along with 'Service 1'.
  41. Close the report.
  42. Click [No].
  43. Open 'Open Closed Charges'.
  44. Select 'Individual Client' from 'Individual Client Or Interim Batch'.
  45. Select 'Client 1' in the 'Client ID' field.
  46. Select the episode from the 'Episode Number' field.
  47. Set 'Start Date' and 'End Date' with the date of 'Service 1' used in Step 2.
  48. Click [Select Charges To Open].
  49. Validate that the 'Open Closed Charges' window contains 'Service 1'.
  50. Select 'Service 1'.
  51. Click [OK].
  52. Select [Submit].
  53. Click [Yes].
  54. Click [No].
  55. Open 'Edit Service Information'.
  56. Select 'Client 1' in the 'Client ID' field.
  57. Validate that the Episode field is populated with the corresponding Episode.
  58. Set the 'Service Start Date' and 'Service End Date' with the date of 'Service 1' used in Step 2.
  59. Click [Select Service(s) To Edit].
  60. Validate that we see both Service 1 and 2 in the 'Select Service(s) To Edit' grid.
  61. Select 'Service 1' from the grid.
  62. Click [OK].
  63. Edit the 'Modifiers text' field and set it to any desired value.
  64. Select [Submit].
  65. Click [No].
  66. Open 'Close Charges'.
  67. Select 'Close Charges' from 'Liability Update Or Close Charges'.
  68. Select 'T' to set today's date in the 'Thru Date' field.
  69. Select 'Individual' from 'Individual, All, Or Interim Batch Cycle'.
  70. Select 'Client 1' in the 'Client ID' field.
  71. Select the episode from the 'Episode Number' field.
  72. Select [Submit].
  73. Open 'Delete Service'.
  74. Select 'Client 1' in the 'Client ID' field.
  75. Set the 'Start Date' and 'End Date' with the date of 'Service 1' used in Step 2.
  76. Click [Display Client].
  77. Validate that we see 'Service 2' in the 'Service Delete' window.
  78. Select 'Service 2' from the grid.
  79. Click [OK].
  80. Click [Delete].
  81. Validate that a 'The following services will be deleted.' window displays with the 'Service 2' we selected in Step 78.
  82. Click [OK].
  83. Click [Yes].
  84. Click [OK].
  85. Select [Discard].
  86. Click [Yes].
  87. Open 'Client Ledger'.
  88. Select 'Client 1' in the 'Client ID' field.
  89. Select 'All Episodes' from 'Claim/Episode/All Episodes'.
  90. Select 'Simple' from 'Ledger Type'.
  91. Set 'From Date' and 'To Date' with the date of 'Service 1' used in Step 2.
  92. Select [Process].
  93. Validate that Services 1 and 2 are shown in the client's ledger, with 'Service 2' marked as 'DELETE' under the 'SERV' column of the report.
  94. Close the report.
  95. Click [No].
  96. Open 'CCBHC PPS Compile'.
  97. If using a PPS-1 definition, enter the date range of services in the service date fields.
  98. If using a PPS-2 definition, enter the first and last date of the month in the service date fields.
  99. Enter the 'Client ID' for 'Client 1'.
  100. Click [Compile & Post Services].
  101. Validate that the 'CCBHC Compile Complete' message is received.
  102. Click [OK].
  103. Select [Discard].
  104. Click [Yes].
  105. Open 'Client Ledger'.
  106. Select 'Client 1' in the 'Client ID' field.
  107. Select 'All Episodes' from 'Claim/Episode/All Episodes'.
  108. Select 'Simple' from 'Ledger Type'.
  109. Set 'From Date' and 'To Date' with the date of 'Service 1' used in Step 2.
  110. Select [Process].
  111. Validate that a new row is created for the 'PPS Service 2' by the 'CCBHC PPS Compile' process and shown in the client's ledger along with 'Service 1'.
  112. Close the report.
  113. Click [No].
Topics
• CCBHC • NX
2023 Update 161 Summary | Details
Purge Billing Files
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Purge Billing Files
  • Quick Billing
Scenario 1: Validate 'Purge Billing Files' when '271 Batch' is selected to purge.
Specific Setup:
  • At least two 'Posted' 271 batch(es) are identified. Note the batch numbers.
Steps
  1. Open 'Purge Billing Files'.
  2. Select '271 Batch' in 'Billing List to Purge'.
  3. Enter a date in 'Date Created Start Date'.
  4. Enter a date in 'Date Created End Date'.
  5. Select 'None' in 'File Selection Default'.
  6. Click [Select File(s) to Purge].
  7. Verify that the file list contains both the 'Posted' batches along with the 'Compiled' batches.
  8. Select the first row, noting the 'Date Created' and 'Batch Name'.
  9. Click [OK].
  10. Click [Submit].
  11. Click [OK].
  12. Repeat steps 1 - 7.
  13. Verify that the batch that was deleted is not present by confirming that the deleted 'Date Created' and 'Batch Name' are not included in the grid.
  14. Run the SQL query and verify that the purged files are only removed from the file lists and not from the system.
Scenario 2: Validate 'Purge Billing Files' when '835 Batch' is selected to purge.
Specific Setup:
  • At least two 835 batch(es) are identified for this test.
  • Note down the batch numbers.
Steps
  1. Open 'Purge Billing Files'.
  2. Select '835 Batch' in 'Billing List to Purge'.
  3. Enter a date in 'Date Created Start Date'.
  4. Enter a date in 'Date Created End Date'.
  5. Select 'None' in 'File Selection Default'.
  6. Click [Select File(s) to Purge].
  7. Verify that the file list contains both the 'Posted' batches along with the 'Compiled' batches.
  8. Select the first row, noting the 'Date Created' and 'Batch Name'.
  9. Click [OK].
  10. Click [Submit].
  11. Click [OK].
  12. Repeat steps 1 - 7.
  13. Verify that the batch that was deleted is not present by confirming that the deleted 'Date Created' and 'Batch Name' are not included in the grid.
  14. Run the SQL query and verify that the purged files are only removed from the file lists and not from the system.
Scenario 3: Validate 'Purge Billing Files' when 'Quick Billing Batch' is selected to purge.
Specific Setup:
  • At least two Quick Billing batches are identified. Note the batch numbers.
Steps
  1. Open 'Purge Billing Files'.
  2. Select 'Quick Billing Batch' in 'Billing List to Purge'.
  3. Enter a date in 'Date Created Start Date'.
  4. Enter a date in 'Date Created End Date'.
  5. Select 'None' in 'File Selection Default'.
  6. Click [Select File(s) to Purge].
  7. Select the first row, noting the 'Date Created' and 'Batch Number'.
  8. Click [OK].
  9. Click [Submit].
  10. Click [OK].
  11. Repeat steps 1 - 7.
  12. Verify that the batch that was deleted is not present by confirming that the deleted 'Date Created' and 'Batch Number' are not included in the list.
  13. If desired, SQL query the 'SYSTEM.billing_quick_batch' table specific to the purged batch, and verify that the associated 837 compiles do not display.
Topics
• Purge Billing Files
2023 Update 162 Summary | Details
Avatar NX - 'All Documents' widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Document Routing Setup (PM)
  • All Documents Widget Definition
  • View Definition
  • CONSOLE WIDGET VIEWER widget
  • Append Progress Notes
Scenario 1: 'All Documents' widget - Validate 'Admission' records
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • The 'All Documents' widget must contain a 'Multi-Form Tab' with the 'Admission', 'Admission (OutPatient)', and 'Pre Admit' forms assigned. This will be referred to as the "Admission" tab.
  • Three clients are enrolled in existing episodes (Client A, Client B, Client C):
  • "Client A" was admitted via the 'Admission' form
  • "Client B" was admitted via the 'Admission (OutPatient)' form
  • "Client C" was admitted via the 'Pre Admit' form.
Steps
  1. Select "Client A" and navigate to the 'All Documents' view.
  2. In the 'All Documents' widget, select the "Admission" tab.
  3. Validate an admission record is displayed from the 'Admission' form.
  4. Click to view the record and validate it displays as expected in the 'Console Widget Viewer'.
  5. Click [Close All].
  6. Select "Client B" and navigate to the 'All Documents' view.
  7. In the 'All Documents' widget, select the "Admission" tab.
  8. Validate an admission record is displayed from the 'Admission (OutPatient)' form.
  9. Click to view the record and validate it displays as expected in the 'Console Widget Viewer'.
  10. Click [Close All].
  11. Select "Client C" and navigate to the 'All Documents' view.
  12. In the 'All Documents' widget, select the "Admission" tab.
  13. Validate an admission record is displayed from the 'Pre Admit' form.
  14. Click to view the record and validate it displays as expected in the 'Console Widget Viewer'.
  15. Click [Close All].
Topics
• Pre Admit • Admission • Admission (Outpatient) • NX
2023 Update 164 Summary | Details
Pre Admit
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Site Specific Section Modeling (PM)
Scenario 1: Pre-Admit Form : Add new fields to the form
Specific Setup:
  • Site Specific Section Modeling: 'Patient 554 (Pre Admit) Site Specific Pre Admission:
  • The site specific section has been modified to include the desired prompt definitions for 'SS Pre Adm Dictionary 15 - 34. Make at least one prompt required,
  • The site specific section has been modified to include the desired prompt definitions for 'SS Pre Adm Multiple Select Dictionary 8 - 27. Make at least one prompt required,
  • Dictionary Update:
  • Client dictionary is used to add values for the prompts selected above - SS Pre Adm Dictionary 15 - 34.
  • Client dictionary is used to add values for the prompts selected above - SS Pre Adm Multiple Select Dictionary 8 - 27.
Steps
  1. Open 'Pre Admit'.
  2. Enter desire data for all sections, including the 'Site Specific Pre Admission'. section. Do not add a value to at least one required field in the 'Site Specific Pre Admission' section.
  3. Click [Submit].
  4. Validate that an error dialog is received regarding the missing required data.
  5. Click [OK].
  6. Add data to the field(s) that are required and are missing data.
  7. Click [Submit].
  8. Open 'Pre Admit' for the same client and select 'Edit'.
  9. Review the submitted data for accuracy.
  10. Change the data is at least one field in the 'Site Specific Pre Admission' section.
  11. Submit the form.
  12. Open 'Pre Admit' for the same client and select 'Edit'.
  13. Review the submitted data to verify that the edited field(s) contain the new data.
  14. Close the form.
  15. If desired, query the 'SYSTEM.site_specific_pre_admission' table to verify the data filed successfully.
Topics
• Pre Admit • Site Specific Section Modeling • NX
2023 Update 166 Summary | Details
File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Sliding Fee Scale
Scenario 1: File Import - Benefit Plans
Specific Setup:
  • Registry Settings: 'Import File Delimiter' is enabled with desired value.
  • File Import:
  • The 'Avatar_PM_File_Import_Record_Layouts' will be included in the update.
  • The 'Benefit Plan' file type is added to the File Import.
  • Create an import "File A" to add a new 'Benefit Plan'.
  • Create an import "File B" to edit above 'Benefit Plan'.
Steps
  1. Open the "File Import" form.
  2. Select the "Benefit Plan" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Select "File A".
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select "File A" in the 'Files(s)' field.
  8. Click [Process Action].
  9. Validate an Information message is displayed stating: Compiled
  10. Click [OK].
  11. Select "Print File" in the 'Action' field.
  12. Select "File A" in the 'Files(s)' field.
  13. Click [Process Action].
  14. Validate the Report Viewer displays the contents of the file.
  15. Click [Close Report].
  16. Select "Post File" in the 'Action' field.
  17. Click [Process Action].
  18. Select "File A".
  19. Validate an Information message is displayed stating: Posted.
  20. Click [OK] and close the form.
  21. Open the "Benefit Plans" form.
  22. Enter the desired plan name.
  23. Verify 'Benefit Plan'.
  24. Verify 'Plan Type'.
  25. Click 'Insurance Plan Level' item.
  26. Verify all the fields are populated as per the import file.
  27. Close the form
  28. Follow steps 1-25, change the import file to "File B" for Edit Benefit Plans File Import.
Scenario 2: File Import: Sliding Fee Scale
Specific Setup:
  • File Import:
  • The 'Avatar_PM_File_Import_Record_Layouts' will be included in the update.
  • The 'Sliding Fee Scale' file type is added to the File Import.
  • Create an import "File A" to add a new 'Sliding Fee Scale'.- "File A".
  • Create an import "File B" to edit above 'Sliding Fee Scale'.-"File B".
  • File Import:
  • The 'Avatar_PM_File_Import_Record_Layouts' will be included in the update.
  • The 'Sliding Fee Scale Calculation Table' is added to the File Import.
  • Create an import "File A" to add a new 'Calculation Table'.-"File C".
  • Create an import "File B" to edit above 'Calculation Table'.-File D".
Steps
  1. Open the "File Import" form.
  2. Select the "Sliding Fee Scale" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Select "File A".
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select "File A" in the 'Files(s)' field.
  8. Click [Process Action].
  9. Validate an Information message is displayed stating: Compiled
  10. Click [OK].
  11. Select "Print File" in the 'Action' field.
  12. Select "File A" in the 'Files(s)' field.
  13. Click [Process Action].
  14. Validate the Report Viewer displays the contents of the file.
  15. Click [Close Report].
  16. Select "Post File" in the 'Action' field.
  17. Click [Process Action].
  18. Select "File A".
  19. Validate an Information message is displayed stating: Posted.
  20. Click [OK] and close the form.
  21. Open the "Sliding Fee Scale" form.
  22. Enter the Sliding Fee Scale.
  23. Validate the fields.
  24. Close the form.
  25. Follow steps 1-25, change the import file to "File B" for 'Edit Sliding Fee Scale' File Import.
  26. Open the "File Import" form.
  27. Select the "Sliding Fee Scale Calculation Table" in the 'File Type' field.
  28. Select "Upload New File" in the 'Action' field.
  29. Click [Process Action].
  30. Select "File C".
  31. Select "Compile/Validate File" in the 'Action' field.
  32. Select "File C" in the 'Files(s)' field.
  33. Click [Process Action].
  34. Validate an Information message is displayed stating: Compiled
  35. Click [OK].
  36. Select "Print File" in the 'Action' field.
  37. Select "File C" in the 'Files(s)' field.
  38. Click [Process Action].
  39. Validate the Report Viewer displays the contents of the file.
  40. Click [Close Report].
  41. Select "Post File" in the 'Action' field.
  42. Click [Process Action].
  43. Select "File C".
  44. Validate an Information message is displayed stating: Posted.
  45. Click [OK] and close the form.
  46. Open the "Sliding Fee Scale" form.
  47. Select the desired Slid Fee Scale.
  48. Select 'Calculation Table' item.
  49. Validate the fields.
  50. Close the form.
  51. Follow steps 1-25, change the import file to "File D" for 'Edit Sliding Fee Scale Calculation Table' File Import.
Topics
• File Import • NX • Sliding Fee Scale
2023 Update 167 Summary | Details
Support for other products and modules
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Site Specific Section Modeling (CWS)
  • CareFabric Monitor
Scenario 1: Progress Notes - Validate the 'EncounterResourceUpdated' SDK event
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The 'Progress Notes (Group and Individual)' form must have a 'SS Note Staff Member' field enabled in 'Site Specific Section Modeling' with "Assign as Primary Care Provider" selected in the 'Product Custom Logic Definition' field. This field will be referred to as the 'Assign as Primary Care Provider' field.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select "Independent Note" in the 'Progress Note For' field.
  5. Select the desired value in the 'Note Type' field.
  6. Enter the desired value in the 'Notes Field'.
  7. Select the desired practitioner in the 'Assign as Primary Care Provider' field.
  8. Select "Final" in the 'Draft/Final' field.
  9. File the note.
  10. Access Crystal Reports or other SQL Reporting tool.
  11. Select the PM namespace.
  12. Create a report using the 'SYSTEM.client_practitioner_assignment' SQL table.
  13. Validate a row is displayed for the note finalized in the previous steps with PCL.
  14. Validate the 'PATID' field contains the client ID for "Client A".
  15. Validate the 'practitioner' field contains the ID for the practitioner selected in the previous steps.
  16. Validate the 'date_of_assignment' and 'time_of_assignment' fields contain the date/time the note was filed.
  17. Close the report.
  18. Access the 'CareFabric Monitor' form.
  19. Enter the current date in the 'From Date' and 'Through Date' fields.
  20. Select "Client A" in the 'Client ID' field.
  21. Click [View Activity Log].
  22. Validate the 'CareFabric Monitor Report' is displayed and contains an "EncounterResourceUpdated" record. Please note: this may be an "EncounterResourceCreated" record if a "Created" message has not yet been triggered for the client. In addition, it may take a few minutes for the event record to display on the report.
  23. Click [Click To View Record].
  24. Validate the last 'individualPractitionerResourceID' - 'id' field contains the ID for the practitioner selected in the previous steps.
  25. Validate the last 'period' - 'fromDate' field contains the date/time the note was filed, which can be found in the 'SYSTEM.client_practitioner_assignment' SQL table.
  26. Validate the last 'typeCodes' - 'codes' - 'code' field contains "PCP".
  27. Validate the last 'typeCodes' - 'codes' - 'displayName' field contains "Primary Care Physician".
  28. Close the report and the form.
Topics
• Progress Notes • CareFabric Monitor
2023 Update 168 Summary | Details
File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
Scenario 1: File import Guarantors/Payors -Authorization Info
Specific Setup:
  • File Import:
  • The 'Guarantors/Payors Authorization Information' type is added to the File Import.
  • Create an import file to add Authorization Information details to a valid Guarantor, "File A".
Steps
  1. Open the "File Import" form.
  2. Select the "Guarantors/Payors Authorization Information" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Select "File A".
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select "File A" in the 'Files(s)' field.
  8. Click [Process Action].
  9. Validate an Information message is displayed stating: Compiled
  10. Click [OK].
  11. Select "Print File" in the 'Action' field.
  12. Select "File A" in the 'Files(s)' field.
  13. Click [Process Action].
  14. Validate the Report Viewer displays the contents of the file.
  15. Click [Close Report].
  16. Select "Post File" in the 'Action' field.
  17. Click [Process Action].
  18. Select "File A".
  19. Validate an Information message is displayed stating: Posted.
  20. Click [OK] and close the form.
  21. Open the "Guarantors/Payors" form.
  22. Click [Edit].
  23. Select the Guarantor in "File A".
  24. Click on Authorization Information Section.
  25. Validate the form is filed with the data based on the uploaded file.
  26. Close the form.
File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
  • Dynamic Form - Document Management Form Re-Mapping - Selection
Scenario 1: File Import: Guarantors Payors - Authorization Info Grid
Specific Setup:
  • File Import:
  • The 'Guarantors/Payors Authorization Information Grid file type is added to the File Import.
  • Create an import "File A" to add a new 'Guarantors/Payors Authorization Information Grid '
  • Create an import "File B" to edit above 'Guarantors/Payors Authorization Information Grid'.
  • Create an import "File C" to delete above added ‘Guarantors/Payors authorization Information Grid'.
Steps
  1. Open the "File Import" form.
  2. Select the "Guarantors/Payors Authorization Information Grid" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Select "File A".
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select "File A" in the 'Files(s)' field.
  8. Click [Process Action].
  9. Validate an Information message is displayed stating: Compiled
  10. Click [OK].
  11. Select "Print File" in the 'Action' field.
  12. Select "File A" in the 'Files(s)' field.
  13. Click [Process Action].
  14. Validate the Report Viewer displays the contents of the file.
  15. Click [Close Report].
  16. Select "Post File" in the 'Action' field.
  17. Click [Process Action].
  18. Select "File A".
  19. Validate an Information message is displayed stating: Posted.
  20. Click [OK].
  21. Close the form.
  22. Open the "Guarantors/Payors" form.
  23. Click [Edit].
  24. Select the appropriate Guarantor
  25. Click on Authorization Information Section.
  26. Validate the fields of the Authorization Information Grid Section.
  27. Close the form.
  28. Follow steps 1-27, using "File B" to edit the Guarantors/Payors Authorization Grid.
  29. Follow steps 1-27, using "File C" to delete the Guarantors/Payors Authorization Information Grid, or a specific row in the grid.
Topics
• File Import • NX
2023 Update 173 Summary | Details
99999 Services Report
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • 99999 Services Report
  • Financial Eligibility
  • Individual Cash Posting (PM)
  • Client Ledger
  • Client Charge Input
Scenario 1: 99999 Services report -When the liability transferred from the Netsmart default guarantor or the agency-defined guarantor to the other guarantor.
Specific Setup:

Guarantors/Payors:

  • Identify an existing guarantor to be used as a default guarantor. Note the guarantor’s id/name.

Registry Setting:

  • The 'Track Services That Failed Liability Distribution' registry setting is set to "Y".
  • Set the 'Agency-Defined Failed Distribution Guarantor' with the desired value.

Admission:

  • An existing client is identified, or a new client is admitted. Note the client id, name, and admission date.
Steps
  1. Open the 'Client Charge Input' form.
  2. Select the date of service, client, service code, and practitioner.
  3. Click [Submit].
  4. Click [No].
  5. Open the 'Close Charges' form.
  6. Set the 'Liability Update Or Close Charges' field to 'Close Charges'.
  7. Set the 'Individual, All, Or Interim Batch Cycle' field to 'Individual'
  8. Set the 'Client ID' field to the ID of the client specified in SETUP'.
  9. Set the 'Episode Number' field to the episode for the services to be closed.
  10. Click [Submit].
  11. Open the 'Financial Eligibility' form.
  12. Select the 'Guarantor Selection' tab.
  13. Click [Add New Item].
  14. Enter any value in the 'Guarantor #' field.
  15. Select any value in the 'Guarantor Plan' field.
  16. Select 'No' in the 'Customize Guarantor Plan' field.
  17. Validate a 'Confirm' message is displayed stating: This Will Delete Any Information Previously Filed In 'Customize Plan'.
  18. Click [OK].
  19. Select 'Yes' in the 'Eligibility Verified' field.
  20. Enter the current date in the 'Coverage Effective Date' field.
  21. Select any value in the 'Client's Relationship To Subscriber' field.
  22. Enter any value in the format of Last Name, First Name in the 'Subscriber's Name' field.
  23. Enter any value in the 'Subscriber Address - Street Line 1' field.
  24. Enter any value in the 'Subscriber's Address - Zip code' field.
  25. Enter any value in the 'Subscriber's Social Security #' field.
  26. Select any value in the 'Subscriber Sex' field.
  27. Select 'Yes' in the 'Coordination of Benefits' field.
  28. Select 'Yes' in the 'Subscriber Assignment of Benefits' field.
  29. Select any value in the 'Subscriber Release Of Info' field.
  30. Select the 'Financial Eligibility' tab.
  31. Select the guarantor selected in the previous steps in the 'Guarantor #1' field.
  32. Click [Submit].
  33. Open 'Individual Cash Posting'.
  34. Enter the 'Client'.
  35. Select desired value in 'Post By'.
  36. Review 'Start Date' and 'Stop Date'. Change the values if desired.
  37. Click [Select Item(s) to Post Against].
  38. Highlight the service from setup.
  39. Click [OK]. Note the 'balance due'.
  40. Click [OK].
  41. Enter the 'Posting Date'.
  42. Enter the 'Date of Receipt'.
  43. Enter the 'Balance Due' in 'Dollar Amount To Be Posted'.
  44. Enter the 'Posting Code'.
  45. Click [Update Temporary File].
  46. Click [OK].
  47. Click [Submit].
  48. Click [Yes].
  49. Click [No].
  50. Open 'Client Ledger'.
  51. Enter the 'Client ID'.
  52. Select 'All Episodes' in 'Claim/Episode/All Episodes'.
  53. Select 'Simple' in 'Ledger Type'.
  54. Set the 'From Date' to the first date of service.
  55. Set the 'To Date' to the last date of service.
  56. Click [Process].
  57. Validate the Report populates with liability transferred to respective Guarantor from NTST Default Guarantor.
  58. Click [Close].
  59. Click [No].
  60. Open the '99999 Services Report' form.
  61. Verify that the ‘Export’ button fields is enabled.
  62. Verify that the following fields are disabled: ‘Service From Date’, ‘Service To Date’, Month/Year of Accounting Period Close'.
  63. Select 'No' in 'Include Closed Services'.
  64. Click [Export].
  65. Validate the message 'No Data to Export' appears.
  66. Click [OK].
  67. Click [Discard].
  68. Click [Yes].
  69. Open the 'Registry Settings' form.
  70. Enable Registry Setting- Agency-Defined Failed Distribution Guarantor.
  71. Submit the Registry Setting.
  72. Close the form.
  73. Repeat the above 1 - 68 steps using Agency Defined Guarantor.
Topics
• Liability Update • NX
2023 Update 176 Summary | Details
835 Healthcare Claim Payment/ Advice - PLB Total
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
  • Client Charge Input (Charge Fee Access)
  • Service Fee/Cross Reference Maintenance
  • Client Ledger
  • Create Interim Billing Batch File
  • Electronic Billing
  • Claim Adjustment Group/Reason Code Definition
  • Guarantors/Payors
Scenario 1: 835 Health Care Claim Payment/Advice - Work Screen Grid
Specific Setup:
  • Claim Adjustment Group/ reason code Definition:
  • A group code is selected for the credit adjustment code and debit adjustment reversal code. Note the adjustment codes and group code setup.
  • Admission:
  • Admit a client into an outpatient episode. Note the Client id/name, Admission date/program.
  • Guarantor/Payors:
  • Three existing commercial guarantors are identified. Note the guarantors codes/names.
  • Financial Eligibility:
  • Three guarantors identified above are assigned to the client. Note the primary, secondary and tertiary guarantor.
  • Client Charge Input:
  • Three services rendered to the client in a same month. Note the service dates.
  • Client Ledger:
  • Make sure the services are distributed to the primary guarantors assigned to the client.
  • Close charges.
  • Electronic Billing:
  • The services are claimed using the 837 Professional bill for the primary guarantor.
  • Create an 835 file based on the claim information found in the 837 professional bill.
Steps
  1. Open the '835 Health Care Claim Payment/Advice' form.
  2. Load and compile the 835 file created that includes the claim for the defined guarantor in the setup.
  3. Verify the 835 file loads/compiles successfully.
  4. Select the 'Work Compile' option.
  5. Select the compiled 835 file.
  6. Click [Launch Work Screen].
  7. Verify the 'PLB Amount' cell includes all the monetary amounts in the PLB to generate a correct total.
  8. Click [Save].
  9. Validate message "Save Successful' is displayed.
  10. Click [Yes] to exit the grid.
  11. Close the form.
Scenario 2: 835 Healthcare Claim Payment/Advise - Validating liability distribution after 'Monthly Maximum Responsibility' distributed
Specific Setup:
  • Claim Adjustment Group/ reason code Definition:
  • The desired group code is selected for the credit adjustment code and credit transfer code. Note the adjustment codes and group code setup.
  • Admission:
  • Admit a client into an outpatient episode. Note the Client id/name, Admission date/program.
  • Guarantor/Payors:
  • Three existing commercial guarantors are identified. Note the guarantors codes/names.
  • Financial Eligibility:
  • Three guarantors identified above are assigned to the client. Note the primary, secondary and tertiary guarantor.
  • The secondary guarantor is customized such that Monthly Maximum Responsibility field has a desired value. This means that once the amount entered in the Monthly Maximum Responsibility is distributed to the secondary guarantor for the month, anything else go to tertiary guarantor.
  • Client Charge Input:
  • Three services rendered to the client in a same month. Note the service dates.
  • Client Ledger:
  • Make sure the services are distributed to the primary guarantors assigned to the client.
  • Close charges.
  • Electronic Billing:
  • The services are claimed using the 837 Professional bill for the primary guarantor.
  • Create an 835 file based on the claim information found in the 837 professional bill.
Steps
  1. Open the '835 Health Care Claim Payment/Advice' form.
  2. Load and compile the 835 file created that includes the claims for the defined guarantor in the setup.
  3. Verify the 835 file loads/compiles successfully.
  4. Select 'Post File' option.
  5. Select the file that is recently compiled successfully.
  6. Populate all the required fields with desired value.
  7. Verify the file posts successfully.
  8. Open the 'Client Ledger' for the client.
  9. Verify the amount entered in the 'Monthly Maximum Responsibility' is distributed to the secondary guarantor for the month and remaining amount distributed to the tertiary guarantor.
835 Healthcare Claim Payment/ Advice - Liability Distribution
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
  • Client Charge Input (Charge Fee Access)
  • Service Fee/Cross Reference Maintenance
  • Client Ledger
  • Create Interim Billing Batch File
  • Electronic Billing
  • Claim Adjustment Group/Reason Code Definition
  • Guarantors/Payors
Scenario 1: 835 Health Care Claim Payment/Advice - Work Screen Grid
Specific Setup:
  • Claim Adjustment Group/ reason code Definition:
  • A group code is selected for the credit adjustment code and debit adjustment reversal code. Note the adjustment codes and group code setup.
  • Admission:
  • Admit a client into an outpatient episode. Note the Client id/name, Admission date/program.
  • Guarantor/Payors:
  • Three existing commercial guarantors are identified. Note the guarantors codes/names.
  • Financial Eligibility:
  • Three guarantors identified above are assigned to the client. Note the primary, secondary and tertiary guarantor.
  • Client Charge Input:
  • Three services rendered to the client in a same month. Note the service dates.
  • Client Ledger:
  • Make sure the services are distributed to the primary guarantors assigned to the client.
  • Close charges.
  • Electronic Billing:
  • The services are claimed using the 837 Professional bill for the primary guarantor.
  • Create an 835 file based on the claim information found in the 837 professional bill.
Steps
  1. Open the '835 Health Care Claim Payment/Advice' form.
  2. Load and compile the 835 file created that includes the claim for the defined guarantor in the setup.
  3. Verify the 835 file loads/compiles successfully.
  4. Select the 'Work Compile' option.
  5. Select the compiled 835 file.
  6. Click [Launch Work Screen].
  7. Verify the 'PLB Amount' cell includes all the monetary amounts in the PLB to generate a correct total.
  8. Click [Save].
  9. Validate message "Save Successful' is displayed.
  10. Click [Yes] to exit the grid.
  11. Close the form.
Scenario 2: 835 Healthcare Claim Payment/Advise - Validating liability distribution after 'Monthly Maximum Responsibility' distributed
Specific Setup:
  • Claim Adjustment Group/ reason code Definition:
  • The desired group code is selected for the credit adjustment code and credit transfer code. Note the adjustment codes and group code setup.
  • Admission:
  • Admit a client into an outpatient episode. Note the Client id/name, Admission date/program.
  • Guarantor/Payors:
  • Three existing commercial guarantors are identified. Note the guarantors codes/names.
  • Financial Eligibility:
  • Three guarantors identified above are assigned to the client. Note the primary, secondary and tertiary guarantor.
  • The secondary guarantor is customized such that Monthly Maximum Responsibility field has a desired value. This means that once the amount entered in the Monthly Maximum Responsibility is distributed to the secondary guarantor for the month, anything else go to tertiary guarantor.
  • Client Charge Input:
  • Three services rendered to the client in a same month. Note the service dates.
  • Client Ledger:
  • Make sure the services are distributed to the primary guarantors assigned to the client.
  • Close charges.
  • Electronic Billing:
  • The services are claimed using the 837 Professional bill for the primary guarantor.
  • Create an 835 file based on the claim information found in the 837 professional bill.
Steps
  1. Open the '835 Health Care Claim Payment/Advice' form.
  2. Load and compile the 835 file created that includes the claims for the defined guarantor in the setup.
  3. Verify the 835 file loads/compiles successfully.
  4. Select 'Post File' option.
  5. Select the file that is recently compiled successfully.
  6. Populate all the required fields with desired value.
  7. Verify the file posts successfully.
  8. Open the 'Client Ledger' for the client.
  9. Verify the amount entered in the 'Monthly Maximum Responsibility' is distributed to the secondary guarantor for the month and remaining amount distributed to the tertiary guarantor.
Topics
• 835 Health Care Claim Payment/Advice • NX
2023 Update 177 Summary | Details
File import: Guarantor/Program Billing Defaults
Scenario 1: File Import: Guarantor/Program Billing Defaults - Assign Template
Specific Setup:
  • File import
  • A file import file of 'GPBD Assign Template' file type is created to assign a template.
Steps
  1. Open the "File Import" form.
  2. Select the 'GPBD Assign Template' File Type.
  3. Click on 'Upload New File' radio button.
  4. Select file for 'GPBD assign template'.
  5. Compile the 'GPBD assign template' file.
  6. Verify that the file compiles successfully.
  7. Post the file.
  8. Verify that the file posts successfully.
  9. Select the 'Print File' option, review the report, and ensure that all data added in the text file is displayed correctly.
  10. Close the report.
  11. Close the form.
  12. Open the 'Guarantor/Program Billing Defaults' form.
  13. Verify all data imported correctly.
Topics
• File Import • Guarantor / Program Billing Defaults • NX
2023 Update 178 Summary | Details
File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
Scenario 1: File Import - Guarantors/Payors - 837 Section
Specific Setup:
  • File Import:
  • The 'Guarantors/Payors 837 Submission file type is added to the File Import.
  • Create an import file to add 837 Submission details to a valid Guarantor.
Steps
  1. Open the "File Import" form.
  2. Select the "Guarantors/Payors 837 Submission" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Select the "File A".
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select the "File A" in the Files(s) field.
  8. Click [Process Action].
  9. Validate an Information message is displayed stating: Compiled
  10. Click [OK].
  11. Select "Print File" in the 'Action' field.
  12. Select the "File A" in the Files(s) field.
  13. Click [Process Action].
  14. Validate the Report Viewer displays the contents of the file.
  15. Click [Close Report].
  16. Select "Post File" in the 'Action' field.
  17. Click [Process Action].
  18. Select the "File A".
  19. Validate an Information message is displayed stating: Posted.
  20. Click [OK] and close the form.
  21. Open the "Guarantors/Payors" form.
  22. Click [Edit].
  23. Select the Valid Guarantor given in File A.
  24. Validate the form is filed with the data based on the uploaded file.
  25. Close the form.
Topics
• File Import
2023 Update 179 Summary | Details
File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
Scenario 1: File import - Guarantors/Payors - Carrier Codes
Specific Setup:
  • File Import:
  • The 'Guarantors/Payors Carrier Codes' file type is added to the File Import.
  • Create an import "File A" to add a new 'Guarantors/Payors Carrier Codes'
  • Create an import "File B" to edit above 'Guarantors/Payors Carrier Codes'.
  • Create an import "File C" to delete above added ‘Guarantors/Payors Carrier Codes'.
Steps
  1. Open the "File Import" form.
  2. Select the "Guarantors/Payors Carrier Codes" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Select "File A".
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select "File A" in the 'Files(s)' field.
  8. Click [Process Action].
  9. Validate an Information message is displayed stating: Compiled
  10. Click [OK].
  11. Select "Print File" in the 'Action' field.
  12. Select "File A" in the 'Files(s)' field.
  13. Click [Process Action].
  14. Validate the Report Viewer displays the contents of the file.
  15. Click [Close Report].
  16. Select "Post File" in the 'Action' field.
  17. Click [Process Action].
  18. Select "File A".
  19. Validate an Information message is displayed stating: Posted.
  20. Click [OK] and close the form.
  21. Open the "Guarantors/Payors" form.
  22. Click [Edit].
  23. Select the appropriate Guarantor
  24. Click on Carrier Code Section.
  25. Validate the fields of the Carrier Code Section.
  26. Close the form
  27. Follow steps 1-25,change the import file to "File B" for Edit Guarantors/Payors Carrier Code File Import.
  28. Follow steps 1-25, change the import file to "File C" for Delete Guarantors/Payors Carrier Code File import.
Topics
• File Import
2023 Update 181 Summary | Details
Client Search
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
Scenario 1: Financial Eligibility - Client Search Change Subscriber Policy#
Specific Setup:
  • Admit a test client.
  • Using the "Financial Eligibility" form:
  • Populate all required fields.
  • Populate "Subscriber Policy#. Note the data.
  • Populate "Subscriber Medicaid#". Note the data.
Steps
  1. Using the "Financial Eligibility" form:
  2. Change the "Subscriber Policy#" and "Subscriber Medicaid# values. Note the values.
  3. File the form.
  4. From the Home View, enter the value that was entered into "Subscriber Policy#" from Step 1.
  5. Validate the correct result returns from the search on that value.
  6. From the Home View, enter the value that was entered into "Subscriber Medicaid#" from Step 1.
  7. Validate the correct result returns from the search on that value.
Topics
• Client Search • NX
2023 Update 184 Summary | Details
837 Electronic Billing - 2300-K3 segment
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Update (PM)
  • Guarantors/Payors
  • Practitioner Numbers By Guarantor And Program
  • Financial Eligibility
  • Service Fee/Cross Reference Maintenance
  • Client Charge Input
  • Create Interim Billing Batch File
  • Electronic Billing
Scenario 1: 837 Institutional - Report Only Guarantor - Validate (2010BA-REF) and (2300-K3) segments
Specific Setup:
  • Registry Settings:
  • Avatar PM->Billing->Electronic Billing->837 Report Only->->Include Subscriber Secondary ID Info (2010BA-REF) has a value of ‘Y’.
  • Dictionary Update:
  • Other Tabled Files:
  • ‘(12125) Specify Information To Include Subscriber Secondary ID Information (2010BA-REF) – Report Only’ has values of ‘Client Social Security Number’ and ‘Client Social Security Number (No Dashes, Only When Subscriber Equals Self)’.
  • Client: Dictionary:
  • ‘(350) State Reporting Ethnic Origin’ has desired values.
  • ‘(8) Ethnic Origin’ has extended dictionary values in ‘(350) State Reporting Ethnic Origin’.
  • ‘(351) State Reporting Client Race’ has desired values.
  • ‘(116) Client Race’ has extended dictionary values in ‘(351) State Reporting Client Race’.
  • ‘(247) Client's Relationship To Subscriber’ has extended dictionary value for the ‘Billing Patient's Relationship To Insured’.
  • Guarantors/Payors 1:
  • Has a value of ‘No’ or a null value in ‘Is This A Report Only Guarantor’, in the ‘837’ section.
  • Note the Financial Class.
  • Guarantors/Payors 2:
  • Has the same Financial Class as Guarantors/Payors 1.
  • Has a value of ‘Yes’ in ‘Is This A Report Only Guarantor’, in the ‘837’ section.
  • Has a value of Guarantors/Payors 1 in 'Only Include Services In The Report Only 837 If Liability For The Service Distributes To The Following Guarantor(s)', in the ‘837’ section.
  • Client 1:
  • Client is the subscriber and has values in ‘Race’, ‘Ethnicity’, and ‘Social Security Number’.
  • Note the client ID, admission date, and program.
  • Client is assigned Guarantors/Payors 1 in Financial Eligibility.
  • Client 2:
  • Client is not the subscriber and has values in ‘Race’, ‘Ethnicity’, and ‘Social Security Number’.
  • Note the client ID, admission date, and program.
  • Client is assigned Guarantors/Payors 1 in Financial Eligibility. The client is not ‘Self’ in ‘Client’s Relationship To Subscriber’. The ‘Subscriber’s Name’ and ‘‘Subscriber’s Social Security #’ contain values.
  • Guarantor/Program Billing Defaults:
  • Select templates for the selected guarantor(s) and the client program(s).
  • 837 Institutional section:
  • Select desired value in ‘Specify Information To Include In Subscriber Secondary ID Information (2010BA-REF) - Report Only’ noting the value.
  • Select desired value in ‘Include Race/Ethnicity/SSN in 2300-K3’, noting the value.
  • Service Codes:
  • Service Code must have a value of ‘Yes’ in ‘Include This Service For Report Only Guarantors’. Note the selected service codes.
  • Services:
  • Create services for the clients, noting the date of service.
  • Close Charges for the clients.
Steps
  1. Open ‘Electronic Billing’.
  2. Create an 837 Institutional for Guarantors/Payors 2.
  3. Review the dump file to validate that the following:
  4. If the billing template selection for ‘Specify Information To Include In Subscriber Secondary ID Information (2010BA-REF) - Report Only’ is 'Client Social Security Number’ the output in the REF segment will contain the following: ‘REF*SY*xxx-xx-xxxx, which represents the SSN with dashes. This segment will exist for Client 1 and Client 2.
  5. If the billing template selection for ‘Specify Information To Include In Subscriber Secondary ID Information (2010BA-REF) - Report Only’ is '‘Client Social Security Number (No Dashes, Only When Subscriber Equals Self)’ the output in the REF for Client 1 will contain the following: ‘REF*SY*xxxxxxxxx, which represents the SSN with no dashes. There will not be a ‘REF*SY* segment for Client 2.
  6. If the billing template selection for ‘Include Race/Ethnicity/SSN in 2300-K3’ is ‘No’, there will be no ‘K3’ segment.
  7. If the billing template selection for ‘Include Race/Ethnicity/SSN in 2300-K3’ is ‘Yes’ the ‘K3’ will include the following, if it exists for the client:
  8. Field 1 = the dictionary codes for ‘Ethnicity’.
  9. Field 2 = the dictionary codes for ‘Race’.
  10. Field 3 = the ‘Social Security Number’ of the client, when the client is not the subscriber. No ‘Social Security Number’ is output when the subscriber is the client.
  11. If the billing template selection for ‘Include Race/Ethnicity/SSN in 2300-K3’ is ‘Yes, but exclude SSN' will include the following, if it exists for the client:
  12. Field 1 = the dictionary codes for ‘Ethnicity’.
  13. Field 2 = the dictionary codes for ‘Race’.
  14. Close the dump file.
  15. Close the form.
Scenario 2: 837 Professional - Report Only Guarantor - Validate (2010BA-REF) and (2300-K3) segments
Specific Setup:
  • Registry Settings:
  • Avatar PM->Billing->Electronic Billing->837 Report Only->->Include Subscriber Secondary ID Info (2010BA-REF) has a value of ‘Y’.
  • Dictionary Update:
  • Other Tabled Files:
  • ‘(12125) Specify Information To Include Subscriber Secondary ID Information (2010BA-REF) – Report Only’ has values of ‘Client Social Security Number’ and ‘Client Social Security Number (No Dashes, Only When Subscriber Equals Self)’.
  • Client: Dictionary:
  • ‘(350) State Reporting Ethnic Origin’ has desired values.
  • ‘(8) Ethnic Origin’ has extended dictionary values in ‘(350) State Reporting Ethnic Origin’.
  • ‘(351) State Reporting Client Race’ has desired values.
  • ‘(116) Client Race’ has extended dictionary values in ‘(351) State Reporting Client Race’.
  • ‘(247) Client's Relationship To Subscriber’ has extended dictionary value for the ‘Billing Patient's Relationship To Insured’.
  • Guarantors/Payors 1:
  • Has a value of ‘No’ or a null value in ‘Is This A Report Only Guarantor’, in the ‘837’ section.
  • Note the Financial Class.
  • Guarantors/Payors 2:
  • Has the same Financial Class as Guarantors/Payors 1.
  • Has a value of ‘Yes’ in ‘Is This A Report Only Guarantor’, in the ‘837’ section.
  • Has a value of Guarantors/Payors 1 in 'Only Include Services In The Report Only 837 If Liability For The Service Distributes To The Following Guarantor(s)', in the ‘837’ section.
  • Client 1:
  • Client is the subscriber and has values in ‘Race’, ‘Ethnicity’, and ‘Social Security Number’.
  • Note the client ID, admission date, and program.
  • Client is assigned Guarantors/Payors 1 in Financial Eligibility.
  • Client 2:
  • Client is not the subscriber and has values in ‘Race’, ‘Ethnicity’, and ‘Social Security Number’.
  • Note the client ID, admission date, and program.
  • Client is assigned Guarantors/Payors 1 in Financial Eligibility. The client is not ‘Self’ in ‘Client’s Relationship To Subscriber’. The ‘Subscriber’s Name’ and ‘‘Subscriber’s Social Security #’ contain values.
  • Guarantor/Program Billing Defaults:
  • Select templates for the selected guarantor(s) and the client program(s).
  • 837 Professional section:
  • Select desired value in ‘Specify Information To Include In Subscriber Secondary ID Information (2010BA-REF) - Report Only’ noting the value.
  • Select desired value in ‘Include Race/Ethnicity/SSN in 2300-K3’, noting the value.
  • Service Codes:
  • Service Code must have a value of ‘Yes’ in ‘Include This Service For Report Only Guarantors’. Note the selected service codes.
  • Services:
  • Create services for the clients, noting the date of service.
  • Close Charges for the clients.
Steps
  1. Open ‘Electronic Billing’.
  2. Create an 837 Professional for Guarantors/Payors 2.
  3. Review the dump file to validate that the following:
  4. If the billing template selection for ‘Specify Information To Include In Subscriber Secondary ID Information (2010BA-REF) - Report Only’ is 'Client Social Security Number’ the output in the REF segment will contain the following: ‘REF*SY*xxx-xx-xxxx, which represents the SSN with dashes. This segment will exist for Client 1 and Client 2.
  5. If the billing template selection for ‘Specify Information To Include In Subscriber Secondary ID Information (2010BA-REF) - Report Only’ is '‘Client Social Security Number (No Dashes, Only When Subscriber Equals Self)’ the output in the REF for Client 1 will contain the following: ‘REF*SY*xxxxxxxxx, which represents the SSN with no dashes. There will not be a ‘REF*SY* segment for Client 2.
  6. If the billing template selection for ‘Include Race/Ethnicity/SSN in 2300-K3’ is ‘No’, there will be no ‘K3’ segment.
  7. If the billing template selection for ‘Include Race/Ethnicity/SSN in 2300-K3’ is ‘Yes’ the ‘K3’ will include the following, if it exists for the client:
  8. Field 1 = the dictionary codes for ‘Ethnicity’.
  9. Field 2 = the dictionary codes for ‘Race’.
  10. Field 3 = the ‘Social Security Number’ of the client, when the client is not the subscriber. No ‘Social Security Number’ is output when the subscriber is the client.
  11. If the billing template selection for ‘Include Race/Ethnicity/SSN in 2300-K3’ is ‘Yes, but exclude SSN' will include the following, if it exists for the client:
  12. Field 1 = the dictionary codes for ‘Ethnicity’.
  13. Field 2 = the dictionary codes for ‘Race’.
  14. Close the dump file.
  15. Close the form.
Topics
• 837 Institutional • NX • 837 Professional
2023 Update 185 Summary | Details
WebService Filing.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Crystal Reports or other SQL Reporting tool (PM Namespace)
  • Site Specific Section Modeling (PM)
Scenario 1: Client Admission via WEBSVC Client Admission
Steps
  1. Using desired web service tool, create a request for 'WEBSVC Client Admission'.
  2. Enter the System Code in 'System Code' Field.
  3. Enter the user name in the 'UserName' field.
  4. Enter the password in the 'Password' field.
  5. Enter any value in 'Last Name'.
  6. Enter any value in 'First Name'.
  7. Enter any value in 'Sex'.
  8. Enter any value in 'Type Of Admission'.
  9. Enter any value in 'Preadmit/Admission Date'.
  10. Enter any value in 'SS Pre Adm Dictionary 15'.
  11. Enter any value in 'SS Pre Adm Multiple Select Dictionary 8'.
  12. Enter any Value in 'SS Pre Adm Multiple Select Dictionary 9'.
  13. Click[Run].
  14. Verify Response.
  15. Open 'Pre -Admit' Form.
  16. Enter Value in 'Last Name'.
  17. Enter Value in 'First Name'.
  18. Enter 'Sex'.
  19. Click[Search].
  20. Select the Client.
  21. Click[Edit].
  22. Validate the fields are populated from WebService.
  23. Click [Submit].
Scenario 2: Pre-Admit Form : Add new fields to the form
Specific Setup:
  • Site Specific Section Modeling: 'Patient 554 (Pre Admit) Site Specific Pre Admission:
  • The site specific section has been modified to include the desired prompt definitions for 'SS Pre Adm Dictionary 15 - 34'. Make at least one prompt required,
  • The site specific section has been modified to include the desired prompt definitions for 'SS Pre Adm Multiple Select Dictionary 8 - 27'. Make at least one prompt required,
  • Dictionary Update:
  • Client dictionary is used to add values for the prompts selected above - 'SS Pre Adm Dictionary 15 - 34'.
  • Client dictionary is used to add values for the prompts selected above - 'SS Pre Adm Multiple Select Dictionary 8 - 27'.
Steps
  1. Open 'Pre Admit'.
  2. Enter desire data for all sections, including the 'Site Specific Pre Admission' section. Do not add a value to at least one required field in the 'Site Specific Pre Admission' section.
  3. Click [Submit].
  4. Validate that an error dialog is received regarding the missing required data.
  5. Click [OK].
  6. Add data to the field(s) that are required and are missing data.
  7. Click [Submit].
  8. Open 'Pre Admit' for the same client and select 'Edit'.
  9. Review the submitted data for accuracy.
  10. Change the data in at least one field in the 'Site Specific Pre Admission' section.
  11. Submit the form.
  12. Open 'Pre Admit' for the same client and select 'Edit'.
  13. Review the submitted data to verify that the edited field(s) contain the new data.
  14. Close the form.
  15. If desired, query the 'SYSTEM.site_specific_pre_admission' table to verify the data filed successfully.
Topics
• Pre Admit • Admission • Web Services • Site Specific Section Modeling • NX
2023 Update 186 Summary | Details
Support Utilities - CCBHC flag
Internal Test Only
Support Utilities - Enable Multiple System Codes
Internal Test Only
Topics
• Support Utilities
 

Avatar_PM_2024_Quarterly_Release_2024.01_Details.csv