Skip to main content

Avatar Cal-PM 2024 Monthly Release 2024.02.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 47 Summary | Details
Electronic Billing - Claiming Services.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
  • Client Ledger
  • Create Interim Billing Batch File
  • Electronic Billing
Scenario 1: Progress Notes form - Creating notes for New services with both Primary and Co-Practitioners with add-on service.
Specific Setup:
  • Registry Settings:
  • The 'Enable Co-Practitioner Services From Progress Notes' registry setting is set to 'Y'.
  • The 'Enable Multiple Add-On Code Per Primary Code Functionality' registry setting to 'Y'.
  • Program Maintenance:
  • Identify an existing program to be used for client's admission. Note the program code/value, and associated service programs.
  • The 'Create Co-Practitioner Services From Progress Notes' field is set to 'Yes' for the above program.
  • Site Specific Section modeling:
  • Add-On service, Save Add-On, Add-On Duration, Co-Practitioner, Co-Practitioner Duration fields are added to the Progress Note form if they are not available on the form.
  • Dictionary Update:
  • File= 'Other Tabled File,
  • Data Element - 291 'Service Code Type'
  • Dictionary Code = Desired code
  • Dictionary Value = Desired value
  • Extended Dictionary = 'Allow Multiple Add-On Code Definition'
  • Extended Dictionary Value (Single Dictionary) = Yes
  • Service Codes:
  • A primary service code is created to have desired number of add-on with the following:
  • Service Code Category = Primary Code
  • Service Code Type = desired value
  • Type of Fee = desired value.
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • An add-on service code is created with the following:
  • Service Code Category = Add-On Code
  • Service Code Type = desired value
  • Type of Fee = desired value.
  • Should Add-On Services Generate for Co-Practitioners for this Service Code? = Yes
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Service Fee/Cross Reference Maintenance:
  • A fee definition is created for both the service codes. Note the fee for each service code.
  • Two active practitioners are identified. One will be the primary practitioner, and one will be the co-practitioner. Note the practitioner IDs.
  • Admission:
  • An active client is identified, or a new client is created. Note the client's id, name.
  • Diagnosis:
  • The client has an active diagnosis record. Note the diagnosis codes.
  • Financial Eligibility:
  • The client has an active financial eligibility record. Note the financial class of the guarantor. Note the client ID. Note the episode and program.
  • Guarantor/Program Billing Defaults:
  • The guarantor used in the client's financial eligibility form has an active billing template with the section 837P filled with all the needed values.
Steps
  1. Open the 'Progress Notes (Group and Individual)' form.
  2. Select desired client in 'Select Client'.
  3. Select desired episode in 'Select Episode.
  4. Select ‘New Service’ in 'Progress Notes For'.
  5. Select any value in 'Note Type'.
  6. Enter any value in 'Notes Field'.
  7. Enter desired 'Date Of Service'.
  8. Enter primary service code in 'Service Charge Code'.
  9. Validate that 'Service Program' contains the service program associated to selected episode.
  10. Select desired practitioner in 'Practitioner'.
  11. Enter desired duration in 'Service Duration'.
  12. Select desired co-practitioner in 'Co-Practitioner'.
  13. Enter desired duration in 'Co-Practitioner Duration (Minutes)'.
  14. Click [File Note].
  15. Click [No].
  16. Open the 'Edit Service Information' form.
  17. Select desired client in 'Client ID'.
  18. Select desired episode in 'Episode Number',
  19. Click [Select Service(s) To Edit].
  20. Validate that there are services displayed for both primary and co-practitioner created from progress notes form.
  21. Select and edit both the services to have the 'Add-On Service' added.
  22. Click [Submit].
  23. Click [Yes].
  24. Click [Select Service(s) To Edit].
  25. Validate that there are services displayed for both primary and co-practitioner created from progress notes form.
  26. By selecting each services to edit, verify that the 'Selected Add-On Services' field has the add-on service code added.
  27. Click [Discard].
  28. Click [Yes].
  29. Open the 'Progress Notes (Group and Individual)' form.
  30. Validate the 'Select Client' field contains the client selected.
  31. Select desired episode in 'Select Episode'.
  32. Select ‘New Service’ in 'Progress Notes For'.
  33. Enter any value in 'Notes Field'.
  34. Enter the desired 'Date Of Service' that is different from the previous one.
  35. Enter primary service code in 'Service Charge Code'.
  36. Validate that 'Service Program' contains the service program associated to selected episode.
  37. Select desired practitioner in 'Practitioner'.
  38. Enter desired 'Service Duration'.
  39. Select desired co-practitioner in 'Co-Practitioner'.
  40. Enter desired duration in 'Co-Practitioner Duration (Minutes)'.
  41. Select desired codes in 'Add-On Services'.
  42. Enter desired value in 'Add-On Duration'.
  43. Click [Save Add-On Service].
  44. Verify the add-on service displays in the 'Selected Add-On Services' text area.
  45. Click [File Note].
  46. Validate a message is displays stating: 'Note Filed. Do you want to return to the Progress Notes form?'.
  47. Click [No].
  48. Open the 'Client Ledger' for the client.
  49. Verify the client ledger contains primary and add-on services created for both the practitioner and co-practitioner filed in the progress note.
  50. Close the form.
  51. Use any desired query viewer tool and query the table 'billing_tx_history' for the client.
  52. Validate that there are records displayed for both primary and co-practitioner of the primary and add-on services.
  53. Validate that the column 'JOIN_TO_TX_HISTORY' is displayed with the values for all the rows.
  54. Validate that the column 'join_to_co_staff_tx_history' is not having any values for the primary practitioner row.
  55. Validate that the column 'join_to_co_staff_tx_history' has the 'JOIN_TO_TX_HISTORY' value of respective service's primary practitioner row.
  56. Validate that the column 'join_to_tx_hist_for_addon' has the value only for the add-on services rows of both primary and secondary practitioners.
  57. Open the 'Create Interim Billing Batch File' form.
  58. Create an interim billing batch that covers the client, guarantor and services rendered to the client. Note the batch number.
  59. Close the form.
  60. Open the 'Close Charges' form.
  61. Close all the charges distributed to the guarantor.
  62. Close the form.
  63. Open the 'Client Ledger' for the client.
  64. Verify that primary and add-on services created for both the practitioner and co-practitioner are closed and marked as 'UNBILL'.
  65. Close the form.
  66. Open 'Guarantor/Program Billing Defaults' form.
  67. Select the desired template and edit the '837P' section to have the 'Maximum LX Per CLM' value as "1".
  68. Verify that the field 'Sort "Billing Pay To Provider" Group By Rendering Practitioner' is selected as 'No'.
  69. Click [Submit].
  70. Click [No].
  71. Open the 'Electronic Billing' form.
  72. Compile an 837 bill for the client without claiming the services.
  73. Verify the bill compiles successfully.
  74. Select 'Dump File' option from the billing options.
  75. Select the recently compiled 837 file.
  76. Review the file.
  77. Verify the primary and add-on services are created for both the primary and co-practitioners filed in the progress note.
  78. Validate that only the Primary and Add-On service for the same practitioner are included in a same claim segment.
  79. The Primary and Add-On service for the co-practitioner displayed in a separate claim segment.
  80. Close the report.
  81. Close the form.
  82. Open 'Guarantor/Program Billing Defaults' form.
  83. Select the desired template and edit the '837P' section to have the 'Maximum LX Per CLM' value as "1".
  84. Set the field 'Sort "Billing Pay To Provider" Group By Rendering Practitioner' to have 'Yes' selected.
  85. Click [Submit].
  86. Click [No].
  87. Repeat Step 10.
Topics
• Service Codes • Edit Service Information • Progress Notes • Client Ledger
Update 55 Summary | Details
Cal-OMS Youth/Detox Discharge
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Cal-OMS Youth/Detox Discharge
Scenario 1: Verify submission of Cal-OMS Youth/Detox Discharge
Specific Setup:
  • Client A:
  • The client is 17 years old or younger and is enrolled in a Cal-OMS program.
  • The client has a 'Cal-OMS Admission' filed.
  • Registry setting:
  • The 'Enable LA County Reporting Requirements' is set to 'N'.
Steps
  1. Open Avatar Cal-PM 'Cal-OMS Youth/Detox Discharge' form.
  2. Select the Cal-OMS episode of 'Client A' from the Pre-Display.
  3. Ensure the 'Discharge Process Date' field does not exist in the form.
  4. Click [Discard].
  5. Click [Yes].
  6. Open 'Registry Settings'.
  7. Search and select the 'Enable LA County Reporting Requirements' and set its value as 'Y'.
  8. Click [Submit].
  9. Click [OK].
  10. Click [No].
  11. Open Avatar Cal-PM 'Cal-OMS Youth/Detox Discharge' form.
  12. Select the Cal-OMS episode of 'Client A' from the Pre-Display.
  13. Ensure the 'Discharge Process Date' field is now present in the form.
  14. Ensure that the 'Discharge Process Date' field is enabled.
  15. Populate all required and desired fields.
  16. Click [Submit].
  17. Query the below Avatar Cal-PM SQL table, and verify that the 'Discharge Process Date' field is present and reflects data filed via the 'Cal-OMS Youth/Detox Discharge' form 'Discharge Process Date' field:
  18. 'cal_oms_discharge'.
Topics
• Cal-OMS
Update 56 Summary | Details
Cal-OMS Discharge - Discharge Status Code
Scenario 1: Cal-OMS Discharge and Administrative Cal-OMS Discharge Web Service - Verification of Web Service Filing with invalid discharge_status_code values
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' set to 'N'.
  • Application utilizing the below Avatar Cal-PM web service:
  • 'Cal-OMS Discharge'.
  • 'Client A' is created/ identified with the episodes eligible for 'Cal-OMS Discharge' record filing.
Steps
  1. Cal-OMS Discharge:
  2. Open the 'Cal-OMS Discharge' web service.
  3. Fill all the required tag values.
  4. Enter any valid value(s) for the 'DischargeStatus' tag.
  5. Submit the request to 'FileCalOMSDischarge' method to create or update Cal-OMS Discharge record.
  6. Confirm 'Cal-OMS Discharge' web service responds with confirmation data/ID on successful filing of 'FileCalOMSDischarge' method.
  7. Example: "<Confirmation>ClientID:305||EP:1||UniqueID:OMD.001</Confirmation>".
  8. Confirm that the 'Cal-OMS Discharge' web service responds with a confirmation message on successful filing of the 'FileCalOMSDischarge' method.
  9. Example: "<Message>Cal-OMS Discharge web service has been filed successfully.</Message>".
  10. Confirm 'Cal-OMS Discharge' web service responds with a successful status value on successful filing of 'FileCalOMSDischarge' method.
  11. Example: "<Status>1</Status>".
  12. Confirm 'Cal-OMS Discharge' web service responds with a successful unique ID value on successful filing of 'FileCalOMSDischarge' method.
  13. Example: "<UniqueID>OMD.001</UniqueID>".
  14. Open Avatar Cal-PM 'Cal-OMS Discharge' form and select client/episode/Cal-OMS Discharge record filed via web service for view/update.
  15. Query the below table and confirm Cal-OMS Discharge record is created/updated in Avatar Cal-PM with values/data submitted via web service.
  16. 'cal_oms_discharge'.
  17. Note the 'GUID' of the discharge record of 'Client A'.
  18. Open the 'Cal-OMS Discharge' web service.
  19. Fill all the required tag values.
  20. Enter any invalid value(s) for the 'DischargeStatus' tag.
  21. Submit the request to 'FileCalOMSDischarge' method to create or update Cal-OMS Discharge record.
  22. Confirm that the 'Cal-OMS Discharge' web service responds with an appropriate error message "You must use the 'Cal-OMS Administrative Discharge' form for this discharge status. : DischargeStatus".
  23. Example: "<Message>You must use the 'Cal-OMS Administrative Discharge' form for this discharge status: DischargeStatus</Message>".
  24. Confirm 'Cal-OMS Discharge' web service responds with an unsuccessful status value.
  25. Example: "<Status>0</Status>".
  26. Open any query viewer tool.
  27. Query the below table and confirm Cal-OMS Discharge record has the values/data submitted via web service.
  28. 'cal_oms_discharge'.
  29. Cal-OMS Admin Discharge:
  30. Open the 'Cal-OMS Admin Discharge' web service.
  31. Fill all the required tag values.
  32. Enter any invalid value(s) for the 'DischargeStatus' tag.
  33. Submit the request to 'FileCalOMSAdminDischarge' method to create or update Cal-OMS Discharge record.
  34. Confirm that the 'Cal-OMS Discharge' web service responds with an appropriate error message "You cannot use the 'Cal-OMS Administrative Discharge' form for this discharge status: DischargeStatus".
  35. Example: "<Message>You cannot use the 'Cal-OMS Administrative Discharge' form for this discharge status. DischargeStatus</Message>".
  36. Confirm 'Cal-OMS Discharge' web service responds with an unsuccessful status value.
  37. Example: "<Status>0</Status>".
  38. Open any query viewer tool.
  39. Query the below table and confirm Cal-OMS Discharge record has the values/data submitted via web service.
  40. 'cal_oms_discharge'.
  41. Open the 'Cal-OMS Admin Discharge' web service.
  42. Fill all the required tag values.
  43. Enter any valid value(s) for the 'DischargeStatus' tag.
  44. Submit the request to 'FileCalOMSAdminDischarge' method to create or update Cal-OMS Discharge record.
  45. Confirm 'Cal-OMS Discharge' web service responds with confirmation data/ID on successful filing of 'FileCalOMSAdminDischarge' method.
  46. Example: "<Confirmation>ClientID:305||EP:1||UniqueID:OMD.001</Confirmation>".
  47. Confirm that the 'Cal-OMS Discharge' web service responds with a confirmation message on successful filing of the 'FileCalOMSAdminDischarge' method.
  48. Example: "<Message>Cal-OMS Discharge web service has been filed successfully.</Message>".
  49. Confirm 'Cal-OMS Discharge' web service responds with a successful status value on successful filing of 'FileCalOMSAdminDischarge' method.
  50. Example: "<Status>1</Status>".
  51. Confirm 'Cal-OMS Discharge' web service responds with a successful unique ID value on successful filing of 'FileCalOMSAdminDischarge' method.
  52. Example: "<UniqueID>OMD.001</UniqueID>".
  53. Open Avatar Cal-PM 'Cal-OMS Discharge' form and select client/episode/Cal-OMS Discharge record filed via web service for view/update.
  54. Query the below table and confirm Cal-OMS Discharge record is created/updated in Avatar Cal-PM with values/data submitted via web service.
  55. 'cal_oms_discharge'.
Cal-OMS Discharge - All Docs/Chart View
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Cal-OMS Youth/Detox Discharge
Scenario 1: Cal-Oms Discharge - Accessing the form through 'All Doc' Widget and using 'Console Widget Viewer'.
Specific Setup:
  • Registry Settings:
  • The 'Allow Multiple Cal-OMS Admissions Per Avatar Episode' registry setting is set to 'Y'.
  • Program Maintenance:
  • Create a new Cal-OMS program or identify an existing program to update.
  • Note the program code/name.
  • Admission:
  • Client A.
  • A new client is admitted to the program defined above. Note the client ID/ name, Admission Date.
  • Cal-OMS Admission:
  • File the Cal-Oms admission for 'Client A'.
  • Cal-OMS Discharge:
  • File the Cal-Oms discharge for 'Client A'.
  • Configure All Documents Widget:
  • Using the 'All Documents Widget Definition' form the 'AllDocsWidget' is configured to display the Cal-OMS forms.
  • Using the 'View Definition' form, add the "All Docs Widget" just created to the user's home view.
  • Using the 'View Definition' form, add the "Console Widget Viewer".
Steps
  1. Search and select 'Client A' using 'What can I help you find?' in the Home view and have it highlighted in the 'Recent Clients'.
  2. Verify that the 'All Docs Widget' populates with the Cal-OMS info of 'Client A'.
  3. Select the Cal-OMS discharge record for 'Client A' in the 'All Docs Widget'.
  4. Click [Open].
  5. Verify that the appropriate Cal-OMS discharge form opens with the discharge data filed for 'Client A'.
  6. Make any desired updates and click [Submit].
  7. Open any query viewer.
  8. Query the SQL table below for 'Client A':
  9. cal_oms_discharge
  10. Verify that there is a record displayed for the Cal-oms discharge.
  11. Verify that the record displays the correct data for 'Client A'.
  12. Verify that the updated values display correctly in the respective column(s).
  13. Close the query window and return to NX.
  14. Select the Cal-OMS discharge record for 'Client A' in the 'All Docs Widget'.
  15. Verify that the 'Console Widget Viewer' populates with the Cal-Oms info of 'Client A'.
  16. Click [Open Record].
  17. Verify that the appropriate Cal-OMS discharge form opens with the discharge data filed for 'Client A'.
  18. Make any desired updates and click [Submit].
  19. Open any query viewer.
  20. Query the SQL table below for 'Client A':
  21. cal_oms_discharge
  22. Verify that there is a record displayed for the Cal-oms discharge.
  23. Verify that the record displays the correct data for 'Client A'.
  24. Verify that the updated values display correctly in the respective column(s).
  25. Close the query window.
Cal-OMS Admission - Other Funding Programs
Scenario 1: Cal-OMS Admission - Form submission with the required fields
Specific Setup:
  • Registry Settings:
  • The 'Enable LA County Reporting Requirements' registry setting is set to 'Y'.
  • Program Maintenance:
  • Create a new Cal-OMS program or identify an existing program to update.
  • Note the program code/name.
  • Admission:
  • Client A.
  • A new client is admitted to the program defined above. Note the client ID/ name, Admission Date.
  • Client is less than 17 years of age.
  • Client B.
  • A new client is admitted to the program defined above. Note the client ID/ name, Admission Date.
  • Client is greater than 18 years of age.
Steps
  1. Open 'Cal-OMS Admission' form.
  2. Select 'Client A' from the "Select Client" dialog window.
  3. Select the episode from the "Episode" selection dialog window. Note: the episode selection will display only when the client has more than one active episode.
  4. Select 'Admission Data'.
  5. Select/deselect 'General Relief' in the 'Other Funding Programs' field, and tab out.
  6. Verify that the 'General Relief Case Number' field is enabled/disabled when the 'General Relief' option is selected/deselected:
  7. The field is enabled and required when the 'General Relief' is selected.
  8. The field is disabled when the 'General Relief' is deselected.
  9. Select/ deselect 'Juvenile In Custody Probation Camp' in the 'Other Funding Programs' field, and tab out.
  10. Verify that the 'Please select camp' field is enabled/ disabled when the 'Juvenile In Custody Probation Camp' option is selected/ deselected:
  11. The field is enabled and required when the 'General Relief' is selected.
  12. The field is disabled when the 'General Relief' is deselected.
  13. Select 'General Relief' and enter any desired value in the 'General Relief Case Number' field.
  14. Complete all the required fields.
  15. Click [Submit].
  16. Verify the system displays the missing fields' error.
  17. Click [Continue Filing].
  18. Verify the system navigates the user to the home view.
  19. Open any query viewer.
  20. Query the SQL table below for 'Client A':
  21. cal_oms_admission
  22. Verify that there is a record created for the Cal-oms admission.
  23. Verify that the column 'gen_relief_case_num' has the value field in step 1(h).
  24. Close the query window and return to NX.
  25. Open "Cal-OMS Admission" form.
  26. Select 'Client B' from the "Select Client" dialog window.
  27. Select the episode from the "Episode" selection dialog window. Note: the episode selection will display only when the client has more than one active episode.
  28. Select 'Admission Data'.
  29. Select/deselect 'General Relief' in the 'Other Funding Programs' field, and tab out.
  30. Verify that the 'General Relief Case Number' field is enabled/disabled when the 'General Relief' option is selected/deselected:
  31. The field is enabled and required when the 'General Relief' is selected.
  32. The field is disabled when the 'General Relief' is deselected.
  33. Select/ deselect 'Juvenile In Custody Probation Camp' in the 'Other Funding Programs' field, and tab out.
  34. Verify that the 'Please select camp' field is enabled/ disabled when the 'Juvenile In Custody Probation Camp' option is selected/ deselected:
  35. The field is enabled and required when the 'General Relief' is selected.
  36. The field is disabled when the 'General Relief' is deselected.
  37. Select 'General Relief' and enter any desired value in the 'General Relief Case Number' field.
  38. Complete all the required fields.
  39. Click [Submit].
  40. Verify the system displays the missing fields' error.
  41. Click [Continue Filing].
  42. Verify the system navigates the user to the home view.
  43. Open any query viewer.
  44. Query the SQL table below for 'Client B':
  45. cal_oms_admission
  46. Verify that there is a record created for the Cal-oms admission.
  47. Verify that the column 'gen_relief_case_num' has the value field in step 3(h).
  48. Close the query window.
Topics
• Cal-OMS • Console Widget • Cal-Oms Admission
Update 59 Summary | Details
Guardiant - metric processing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guardiant
Scenario 1: Guardiant Metric Processing/Data - Validations (Avatar Cal-PM)
Specific Setup:
  • Have a system configured for "Guardiant" reporting
  • Logged in user has access to the "Guardiant" form in Avatar and the "Guardiant" application
Steps
  1. Open form "Guardiant"
  2. Click [Test Daily Collection]
  3. Validate message "Test Succeeded" is displayed
  4. Click [Yes] to the warning message
  5. Validate message "Test Succeeded" is displayed
  6. Click [Test Metrics Collection]
  7. Validate message "Test Succeeded" is displayed
  8. Click [Yes] to the warning message
  9. Validate message "Test Succeeded" is displayed
  10. Log into "Guardiant"
  11. At the "Client Search", select the desired client account number
  12. In the right-hand corner, click the menu icon
  13. Select "Grafana"
  14. Click "Dashboards"
  15. Select "DSC2 Metrics Summary" dashboard
  16. From the "Metrics" field drop down list, select "Cal OMS And CSI Admissions"
  17. Hover over the current date and a previous date on the graph
  18. Validate the values displayed, are as expected
  19. From the "Metrics" field drop down, select "Cal OMS Discharges by Program"
  20. Hover over the current date and a previous date on the graph
  21. Validate the values displayed, are as expected
Topics
• Discharge • Cal-Oms Admission • CFMS
Update 61 Summary | Details
Monthly 835 Denial Trends Report - Data validation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Monthly 835 Denial Trends Report
Scenario 1: 'Monthly 835 Denial Trends Report' - One Guarantor - multiple claims/clients - same service date
Specific Setup:
  • Guarantors/Payors:
  • An existing guarantor is identified to be used. Note the guarantor's code/name.
  • Guarantor/Program Billing Defaults:
  • The 'Maximum Service Information Per Claim Information (Maximum LX Per CLM)' field does not contain any value.
  • Service codes:
  • An existing service code is identified to be used. Note the service code/description.
  • Service Fee/ Cross Reference Maintenance:
  • A fee definition is created for the service code identified in the ' Service Codes' form.
  • Admission:
  • 5-6 existing clients are identified, or new clients are admitted. Note client ids, admission program, admission date.
  • Financial Eligibility:
  • A guarantor identified in the 'Guarantors/Payors' form is assigned to all the clients as a primary guarantor.
  • Recurring Client Charge Input:
  • 2-3 services are rendered to all the client on the same dates. (i.e. Select a month and the same days of that month to create services for all the clients, using the same service codes and same dates of service for each client.). Note service dates.
  • Client Ledger:
  • All the services are distributed to the assigned guarantor.
  • Claim Adjustment Group/Reason Code Definitions:
  • 2-3 group/reason codes are created/identified. Note the definitions.
  • Close Charges:
  • All the services distributed to the identified guarantor are closed.
  • Create Interim Billing Batch:
  • An interim billing batch is created to include all the services rendered to all the clients. Note the batch number.
  • Electronic Billing:
  • Claims are created for all the clients and services. Note the claim numbers.
  • An 835 Healthcare Claim Payment/Advice file is created to deny at least two of the services for each of your test clients. Note the file name/path.
  • The Claim Adjustment Group/Reason Code Definitions used for the denials are the same for every client in the 835.
  • 835 Healthcare Claim Payment/Advice:
  • Load/compile/post the 835 Healthcare Claim Payment/Advice file. Note the posting date.
Steps
  1. Open 'Monthly 835 Denial Trends Report'.
  2. Set 'By Financial Class or Guarantor(s)' to 'Guarantor(s)'.
  3. Enter the claims 'Start Date'.
  4. Enter the claims 'End Date'.
  5. Click [Process].
  6. Review the report, 'MONTHLY 835 DENIAL TRENDS BY GUARANTOR REPORT'.
  7. The 'CLAIM DATE' displays the dates entered in 'Start Date' and 'End Date'.
  8. The 'GUARANTOR' column displays the guarantor’s name.
  9. The 'DENIALS' column displays the denial 'Reason Codes' defined in 'Claim Adjustment Group/Reason Code Definition'.
  10. The distinctive months will display a count by reason code.
  11. Validate that the 'Total Denials For Month' values are correct.
  12. Close the report.
  13. Set 'By Financial Class or Guarantor(s)' to 'Financial Class'.
  14. Enter the claims 'Start Date'.
  15. Enter the claims 'End Date'.
  16. Click [Process].
  17. Review the report, 'MONTHLY 835 DENIAL TRENDS BY FINANCIAL CLASS REPORT'.
  18. The 'FINANCIAL CLASS' displays the financial class.
  19. The 'DENIALS' column displays the denial 'Reason Codes' defined in 'Claim Adjustment Group/Reason Code Definition'.
  20. The distinctive months will display a count by reason code.
  21. Validate that the 'Total Denials For Month' values are correct.
  22. Close the report.
  23. Close the form.
Topics
• 835 Health Care Claim Payment/Advice • 837 Professional
Update 67 Summary | Details
Delete Service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Charge Input
  • Client Ledger
  • Delete Service
Scenario 1: Delete Service - Delete Primary and Add on Services
Specific Setup:
  • Registry Setting:
  • 'Enable Multiple Add-On Code Per Primary Code Functionality' = Y.
  • Admission:
  • An existing client is identified, or a new client is admitted. Note client id, admission program, admission date.
  • Financial Eligibility:
  • A guarantor identified in the 'Guarantors/Payors' form is assigned to the client as a primary guarantor.
  • Service Codes:
  • Service Code 1 is created with a 'Service Code Category of 'Add-On Code' and a 'Service Code Type’ of any desired value. Note the code and definition.
  • Service Code 2 is created with a 'Service Code Category of 'Primary Code' and a 'Service Code Type’ of any desired value. Note the code and definition.
  • After Service Code 2 is submitted, it must be edited and Service Codes 1 must be selected in 'Select Multiple Add-On Codes'.
  • Client Charge Input:
  • A service rendered to a client with an add-on service.
  • Client Ledger:
  • Make sure both services are on the ledger.
Steps
  1. Open "Client Charge Input" form.
  2. Enter any date in 'Date of Service'.
  3. Enter 'Client ID'.
  4. Select appropriate 'Episode' in 'Episode Number'.
  5. Enter 'Service Code 2' in 'Service Code'.
  6. Enter appropriate 'Practitioner' in 'Practitioner'.
  7. Enter any value in 'Duration (Minutes)'.
  8. Select 'Service Code 1 in 'Add-On Service'.
  9. Enter any value in 'Add-On Duration'.
  10. Click [Save Add-On Service].
  11. Click [Submit].
  12. Validate Form Return Dialog.
  13. Click [No].
  14. Open "Client Ledger" form.
  15. Enter 'Client ID'.
  16. Click [All Episodes] in 'Claim/Episode/All Episodes'.
  17. Click [Simple] in 'Ledger Type'.
  18. Click [Yes] in 'Include Zero Charges'.
  19. Click [Process].
  20. Validate both primary and add on service display in the ledger.
  21. Click [X].
  22. Validate Form Return.
  23. Click [No].
  24. Open "Delete Service" form.
  25. Enter 'Client ID'.
  26. Enter any value in 'Start Date'.
  27. Enter any value in 'End Date'.
  28. Click [Display Client].
  29. Select primary and add on services to be deleted.
  30. Click [OK].
  31. Validate the message displays 'Continue filing?'
  32. Click [Yes].
  33. Validate the message: 'Deleted'.
  34. Click [OK].
  35. Click [Discard].
  36. Validate Form Close Dialog.
  37. Click [Yes].
  38. Repeat steps 14-23, to validate that both primary and add on service deleted no longer exists in the report.
Topics
• Delete Service
Update 74 Summary | Details
CSI Assessment and CSI Assessment Call Intake forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CSI Admission
  • CSI Assessment
  • CSI Assessment (Call Intake)
Scenario 1: CSI Assessment - Registry Setting: Require Referral Source
Specific Setup:
  • Registry Settings: 'Avatar PM->California Required EDI->CSI->->->Require Referral Source' = desired value. Note the value and expected result.
  • For this test we are using 'Y&YC'. 'Y' is for the 'CSI Assessment' form. 'YC is for the 'CSI Assessment Call Intake' form.
  • Program Maintenance:
  • 'Program 1' contains 'Admit' in 'Program Type' and 'Yes' in 'Mental Health Program (CSI)'.
  • 'Program 2' contains 'Call Intake' in 'Program Type',
  • 'Program 3' contains 'Call Intake' in 'Program Type' and 'Yes' in 'Mental Health Program (CSI)'. The 'CSI Assessment Call Intake' record will be created in the steps.
  • Clients:
  • 'Client A' is admitted to 'Program 1'. The 'CSI Assessment' record will be created in the steps.
  • 'Client B' is admitted to 'Program 2'. The 'CSI Assessment Call Intake' record will be created in the steps.
Steps
  1. Open the 'CSI Assessment' form for 'Client A'.
  2. Verify that the 'Referral Source' field is required.
  3. Enter data in all required fields and desired optional fields.
  4. Click [Submit].
  5. If desired, reopen the 'CSI Assessment' form for 'Client A' and validate the submitted data.
  6. Open the 'CSI Assessment Call Intake' for 'Client B'.
  7. Verify that the 'Referral Source' field is required.
  8. Enter data in all required fields and desired optional fields.
  9. Click [Submit].
  10. If desired, reopen the ''CSI Assessment Call Intake' for 'Client B' and validate the submitted data.
  11. If desired, change the value of the 'Require Referral Source' registry setting to get a different result.
  12. Open the 'CSI Assessment' form for 'Client A'.
  13. Verify that the 'Referral Source' field is required or not required, based on the new value in the 'Require Referral Source' registry setting.
  14. Close the form.
  15. 'CSI Assessment Call Intake' for 'Client B'.
  16. Verify that the 'Referral Source' field is required or not required, based on the new value in the 'Require Referral Source' registry setting.
  17. Close the form.
Topics
• CSI Assessment • CSI Assessment (Call Intake)
Update 77 Summary | Details
Future Functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Remittance Processing Widget
Scenario 1: Remittance Processing Widget- Collapse Rows By Default
Steps

Internal testing only.
Topics
• Widgets • Remittance Processing
Update 79 Summary | Details
Avatar Cal-PM - Smart Search functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
Scenario 1: Validate the 'Enable Smart Search Functionality' registry setting
Specific Setup:
  • The 'Enable Smart Search Functionality' registry setting is set to "Y".
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Enter the desired value in the 'Preferred Name' field.
  3. Enter the desired value in the 'Client's Home Phone' field.
  4. Enter the desired value in the 'Client's Cell Phone' field.
  5. Click [Submit].
  6. Navigate to the 'Search Clients' field in the 'My Clients' widget.
  7. Enter the 'Preferred Name' for "Client A".
  8. Validate the 'Results' contains "Client A" as expected.
  9. Enter the 'Home Phone' for "Client A".
  10. Validate the 'Results' contains "Client A" as expected.
  11. Enter the 'Cell Phone' for "Client A".
  12. Validate the 'Results' contains "Client A" as expected.
  13. Access the 'Progress Notes (Group and Individual)' form.
  14. In the 'Select Client' field, enter the 'Preferred Name' for "Client A".
  15. Validate the 'Results' contains "Client A" as expected.
  16. In the 'Select Client' field, enter the 'Home Phone' for "Client A".
  17. Validate the 'Results' contains "Client A" as expected.
  18. In the 'Select Client' field, enter the 'Cell Phone' for "Client A".
  19. Validate the 'Results' contains "Client A" as expected.
  20. Close the form.
  21. Access the 'Update Client Data' form.
  22. Validate a 'Select Client' dialog is displayed.
  23. In the 'Select Client' field, enter the 'Preferred Name' for "Client A".
  24. Validate the 'Results' contains "Client A" as expected.
  25. In the 'Select Client' field, enter the 'Home Phone' for "Client A".
  26. Validate the 'Results' contains "Client A" as expected.
  27. In the 'Select Client' field, enter the 'Cell Phone' for "Client A".
  28. Validate the 'Results' contains "Client A" as expected.
  29. Click [Cancel].
Topics
• Registry Settings • Client Search
Update 82 Summary | Details
Dynamic fields/forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Crystal Report Viewer
Scenario 1: Service Fee/Cross Reference Maintenance - Multiple Definitions on Same Date - Dynamic Messaging
Steps

Internal testing only
Topics
• Disclosure
Update 83 Summary | Details
Client Ledger CR
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Ledger CR
Scenario 1: Client Ledger CR - report validation.
Specific Setup:
  • 'Staff A':
  • Has access to the 'Client Ledger CR' form (Avatar PM -> Billing -> Billing Reports -> Client Ledger CR).
  • 'Staff B':
  • Does not have access to the form, 'Client Ledger CR' (Avatar PM -> Billing -> Billing Reports -> Client Ledger CR).
  • Service Codes:
  • An active service code is identified or created that has all the needed details.
  • Has active fee definition.
  • 'Client A':
  • A new client is created or an existing one is identified and admitted to any Inpatient/ Outpatient program.
  • Has active diagnosis.
  • Has active financial eligibility records.
  • Guarantors filed in client's financial eligibility form has all the details filled.
  • Has services charged.
  • Has a payment and an adjustment posted and claimed.
Steps
  1. Log into the system as 'Staff B'.
  2. Try to search and access the 'Client Ledger CR' form.
  3. Verify that the form is not accessible for 'Staff B'.
  4. Log out and log back in to the system as 'Staff A'.
  5. Try to search and access the 'Client Ledger CR' form.
  6. Verify that the form is accessible for 'Staff A'.
  7. Open 'Client Ledger CR'.
  8. Select 'Client A'.
  9. Verify that the following fields are displayed in the form:
  10. Select Patient:
  11. Is required and enabled.
  12. Populated with the selected client - 'Client A'.
  13. Select Episode Number:
  14. Is required and enabled.
  15. Initially blank.
  16. Has all the linked episodes of 'Client A'.
  17. Include Service Starting:
  18. Is required and enabled.
  19. Initially blank.
  20. Accepts future date values.
  21. Include Services Through:
  22. Is required and enabled.
  23. Initially blank.
  24. Accepts future date values.
  25. Remove the value from 'Select Patient'.
  26. Leave all the required fields empty and click [Process].
  27. Verify an error message displays for the missing mandatory fields.
  28. Click [OK].
  29. Select 'Client A' in the 'Select Patient' field.
  30. Select a desired episode.
  31. Enter any desired date value in 'Include Service Starting', that is a future date and does not include the services of 'Client A'.
  32. Verify the warning message, "Future date entered." is displayed.
  33. Click [Cancel].
  34. Verify that the filed 'Include Service Starting' is cleared/ reverted to it's last valid value entered if any.
  35. Repeat steps 3 (i - j).
  36. Click [OK].
  37. Verify that the field 'Include Service Starting' has the entered date value.
  38. Enter any desired date value in 'Include Services Through', that is before the date entered in 'Include Service Starting'.
  39. Verify the error message, "Should be after 'Include Service Starting' date" is displayed.
  40. Click [OK].
  41. Verify that the filed 'Include Services Through' is cleared/ reverted to it's last valid value entered if any.
  42. Enter any desired date value in 'Include Services Through', that is a future date and after the date entered in 'Include Service Starting'.
  43. Verify the warning message, "Future date entered." is displayed.
  44. Click [Cancel].
  45. Verify that the filed 'Include Services Through' is cleared/ reverted to it's last valid value entered if any.
  46. Repeat steps 3 (t - u).
  47. Click [OK].
  48. Verify that the field 'Include Services Through' has the entered date value.
  49. Click [Process].
  50. Verify that the report generated has no data for the selected client and the episode.
  51. Close the report.
  52. Click [Yes].
  53. Enter any desired date values in 'Include Service Starting' and 'Include Services Through', that includes the 'Client A' services.
  54. Click [Process].
  55. Verify that the report contains 'Client A' service data within the entered date range.
  56. Verify that the report's header has the below:
  57. RUNDATE.
  58. Page numbers.
  59. Provider name, address, and City.
  60. Report name.
  61. Client Name.
  62. Client ID.
  63. Selected Episode.
  64. Diagnosis History - Link.
  65. Graph of Charges & Payments By Month - Link.
  66. Verify that the appropriate service details are displayed in a table.
  67. Click the Client Name link in the report header.
  68. Validate that a new tab with title 'Client_demographics' is opened with the 'Client Demographic Data' of 'Client A'.
  69. Close the 'Client_demographics' report tab.
  70. Click the 'Diagnosis History' link in the report header.
  71. Validate that a new tab with title 'DIAGNOSIS_HISTORY' is opened.
  72. Close the 'DIAGNOSIS_HISTORY' report tab.
  73. Click the 'Graph of Charges & Payments By Month' link from the report header.
  74. Validate that a new report tab titled as 'Graph of charges_Payments' displayed with the Summary of 'Charges and Payments By Month' for 'Client A' with the graph representation.
  75. Close the tab, 'Graph of charges_Payments'.
  76. Click any value under the 'Date of Service' column of the report table.
  77. Validate that a new tab titled as 'Service Detail Data' is displayed with the 'Detail Service Information' of the selected service.
  78. Close the report tab, 'Service Detail Data'.
  79. Click any value under the 'Service Description' column of the report table.
  80. Validate that a new report tab titled as 'service_code_information', is displayed with the 'Service Code Definition' details of the selected service.
  81. Close the 'service_code_information' report tab.
  82. Click any available value under the column, 'Guarantor Name' of the report table.
  83. Validate that a new report tab titled as 'Guarantor detail' is displayed with 'Guarantor Data' and 'Subscriber Data' of the selected row.
  84. Close the report tab, 'Guarantor detail'.
  85. Click any value under the column, 'Guarantor Payments'.
  86. Validate that a new report tab titled as 'payment_detail', is displayed with the payment details of the selected guarantor payment value.
  87. Close the report tab, 'payment_detail'.
  88. Click any value under the column, 'Claim Number'.
  89. Validate that a new report tab titled as 'CLAIM DATA', displayed with the 'Claim Detail' of the clam number selected.
  90. Close the report tab, 'CLAIM DATA'.
  91. Click [Close Report].
  92. Click [No].
Topics
• Client Ledger
Update 85 Summary | Details
Self Pay Payment Redistribution
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Codes
  • Posting/Adjustment Codes Definition
  • Dictionary Update (PM)
  • Financial Eligibility
  • Client Charge Input
  • Deposit Entry
  • Client Ledger
  • Self Pay Payment Redistribution
Scenario 1: Cal-PM Self Pay Payment Redistribution
Specific Setup:
  • Service Codes:
  • Identify an existing 'prepayment' service code or create a new service code.
  • Posting/Adjustment Codes Definition:
  • An existing payment posting code (credit) is identified. Select 'Yes' for the 'Include in Self Pay Redistribution Payment Process' field.
  • An existing payment reversal posting code (debit) is identified and is the reversal for the above code. Select 'Yes' for the 'Include in Self Pay Redistribution Payment Process' field.
  • Registry Settings:
  • 'Pre Payment Service Code' = the above 'Service Code'.
  • 'Self Pay Payment Redistribution Posting Code' = the above credit 'Posting/Adjustment Code'.
  • 'Include Guarantors with Self Pay System Financial Class' = N.
  • Dictionary Update: Identify an existing, or create a new financial class with the following:
  • File - Payor
  • Data Element - (1000) Financial Class
  • Dictionary Code - The dictionary code for the financial class of the guarantor identified above to be used as secondary guarantor.
  • Extended Dictionary Data Element - (1500) System Financial Class
  • Extended Dictionary Value - Self Pay.
  • Guarantors/Payors:
  • Identify a guarantor with the standard 'Self Pay' financial class.
  • Identify or create a new guarantor with the new financial class added through dictionary update.
  • Identify a primary guarantor.
  • Admission:
  • Two new clients are admitted, or existing clients are identified. Note the client id, admission date and admission program.
  • Financial Eligibility:
  • Client 1:
  • Assigned a primary guarantor where the benefit plan includes a co-pay amount.
  • Assigned self-pay guarantor defined above with the standard 'Self Pay' financial class, as the secondary guarantor.
  • Client 2:
  • Assigned a primary third party guarantor where the benefit plan includes a co-pay amount.
  • Assigned the guarantor defined above with the new self pay financial class added through dictionary update. This is the secondary guarantor.
  • Client Charge Input:
  • Services are rendered to the clients. Note the service date and service code.
  • Client Ledger is used to review the report data for each client, and to note the self pay balance due for each client.
  • Deposit Entry:
  • Client 1: Create a payment for the standard self-pay guarantor. Note the date and amount.
  • Client 2: Create a payment for the new self pay financial class. Note the date and amount.
  • Self Pay Payment Redistribution
  • Run the process by 'Individual' for 'Client 1'.
  • Run the process by 'Individual' for 'Client 2'.
  • Client Ledger
  • Client 1: Process the report and validate that the payment made through 'Deposit Entry' was applied to the co-pay portion of the services distributed to the self-pay guarantor.
  • Client 2: Process the report and validate that the payment made through 'Deposit Entry' was not applied to the co-pay portion of the services distributed to the self-pay guarantor.
Steps
  1. Open the “Registry Settings” form.
  2. Set the 'Limit Registry Settings' to 'Self Pay Payment Redistribution'.
  3. Click [Yes] in 'Include Hidden Registry Settings'.
  4. Click [View Registry Settings].
  5. Select 'Include Guarantors with Self Pay System Financial Class Registry Setting Value: N' item.
  6. Validate the message displays: 'When set to 'Y', the 'Self Pay Payment Redistribution' process will consider guarantors that have a Financial Class value where the System Financial Class is set to Self Pay. When 'N' is selected, only text contains 'When set to 'Y', the 'Self Pay Payment Redistribution' process will consider guarantors that have a Financial Class value where the System Financial Class is set to Self Pay. When 'N' is selected, only guarantors with a base Financial Class of Self Pay will be considered during the 'Self Pay Payment Redistribution' process. This is the default behavior of the system'.
  7. Click [OK].
  8. Set the 'Registry Setting Value' to 'Y'.
  9. Click [Submit].
  10. Click [OK].
  11. Click [No].
  12. Open the “Self Pay Payment Redistribution” form.
  13. Click [Individual] in 'All Or Individual Client'.
  14. Enter 'Client 2' in 'Client ID'.
  15. Click [Run Self Pay Payment Redistribution].
  16. Validates the message displays: 'The process is complete for Client 2'.
  17. Click [OK].
  18. Click [Discard].
  19. Click [Yes].
  20. Open the "Client Ledger" form.
  21. Enter 'Client 2' in 'Client ID'.
  22. Click [All Episodes] in 'Claim/Episode/All Episodes'.
  23. Click [Simple] in 'Ledger Type'.
  24. Click [Process].
  25. Validate that the payment made through 'Deposit Entry' was applied to the co-pay portion of the services distributed to the self-pay guarantor.
  26. Click [X].
  27. Click [No].
Topics
• Self Pay Payment Redistribution
Update 86 Summary | Details
Client Demographics - Personal pronouns
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Update Client Data
  • Discharge
  • Pre Admit
Scenario 1: 'Admission' form - Field Validation
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The registry setting "Client Demographics - Additional Fields to Include" must include "10" at a minimum.
Steps
  1. Select "Client A" and access the 'Admission' form.
  2. Select an existing episode and click [Edit].
  3. Select the "Demographics" section.
  4. Validate the 'Consent On File For Use of Integrated eSignature' field is present with values of "Yes" and "No".
  5. Select "No" in the 'Consent On File For Use of Integrated eSignature' field.
  6. Select "Something else, please specify" in 'Select Personal Pronouns'.
  7. The "Personal Pronouns" text field become enabled.
  8. Enter text into the "Personal Pronouns" field.
  9. Click [Submit].
  10. Select "Client A" and access the 'Admission' form.
  11. Select an existing episode and click [Edit].
  12. Select the "Demographics" section.
  13. Validate "No" is selected in the 'Consent On File For Use of Integrated eSignature' field.
  14. Validate "Personal Pronouns" reflects the value entered or chosen.
  15. Close the form.
  16. Access Crystal Reports or other SQL reporting tool.
  17. Create a report using the 'SYSTEM.patient_current_demographics' SQL table.
  18. Navigate to the row for "Client A".
  19. Validate the 'esig_consent_on_file_code' field is present and contains "N".
  20. Validate the 'esig_consent_on_file_value' field is present and contains "No".
  21. Close the report.
  22. Create a report using the 'SYSTEM.patient_demographic_history' SQL table.
  23. Navigate to the row for "Client A".
  24. Validate the 'esig_consent_on_file_code' field is present and contains "N".
  25. Validate the 'esig_consent_on_file_value' field is present and contains "No".
  26. Close the report.
Scenario 2: 'Update Client Data' form - Verification of 'Client Demographics' form fields
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The 'Client Demographics - Additional Fields' registry setting must include "10" at a minimum.
Steps
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Validate the 'Other Race(s)' field is present on the form.
  3. Select any two desired values from the 'Other Race(s)' field.
  4. Click the "Clear All" link.
  5. Validate the previously selected values no longer display as selected in the 'Other Race(s)' field.
  6. Select "Something else, please specify" in 'Select Personal Pronouns'.
  7. The "Personal Pronouns" text field become enabled.
  8. Enter text into the "Personal Pronouns" field.
  9. Click [Submit].
  10. Select "Client A" and access the 'Update Client Data' form.
  11. Validate the 'Other Race(s)' field displays as expected.
  12. Validate "Personal Pronouns" reflects the value entered or chosen.
  13. Close the form.
  14. Access Crystal Reports or other SQL reporting tool.
  15. Create a report using the 'SYSTEM.patient_current_demographics' SQL table.
  16. Navigate to the row for "Client A".
  17. Validate the 'other_race_value_long' field is present and displays blank.
  18. Validate the 'other_race_value_short' field is present and displays blank.
  19. Close the report.
  20. Create a report using the 'SYSTEM.patient_demographic_history' SQL table.
  21. Navigate to the row for "Client A".
  22. Validate the 'other_race_value_long' field is present and displays blank.
  23. Validate the 'other_race_value_short' field is present and displays blank.
  24. Close the report.
Scenario 3: 'Discharge' form - Field Validation
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The registry setting "Client Demographics - Additional Fields to Include" must include "10" at a minimum.
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. Select "Something else, please specify" in 'Select Personal Pronouns'.
  20. The "Personal Pronouns" text field become enabled.
  21. Enter text into the "Personal Pronouns" field.
  22. Click [Submit].
  23. Select "Client A" and access the 'Discharge' form.
  24. Select the discharged episode and click [Edit].
  25. Validate all previously filed data is displayed.
  26. Select the "Demographics" section.
  27. Validate the 'Client's Email Address' field contains "test@gmail.com".
  28. Validate "Personal Pronouns" reflects the value entered or chosen.
  29. Close the form.
Scenario 4: 'Pre Admit' form - Field Validation
Specific Setup:
  • A client is enrolled in an existing Pre Admit episode (Client A).
  • The registry setting "Client Demographics - Additional Fields to Include" must include "10" at a minimum.
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. Select "Something else, please specify" in 'Select Personal Pronouns'.
  16. The "Personal Pronouns" text field become enabled.
  17. Enter text into the "Personal Pronouns" field.
  18. Click [Submit].
  19. Select "Client A" and access the 'Pre Admit' form.
  20. Select an existing episode and click [Edit].
  21. Select the "Demographics" section.
  22. Validate the 'Client's Email Address' field contains "test@gmail.com".
  23. Validate "Personal Pronouns" reflects the value entered or chosen.
  24. Close the form.
Topics
• Admission • Update Client Data • Discharge • Pre Admit
Update 88 Summary | Details
'Client Merge' process
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CareFabric Monitor
  • Crystal Report Viewer
Scenario 1: Client Merge - Validate the 'Allow Merging Into Existing Episode' registry setting
Specific Setup:
  • Two clients are admitted into existing episodes in the same outpatient programs (Client A, Client B).
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Allow Merging Into Existing Episode" 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->System Maintenance->Client Merge->->->Allow Merging Into Existing Episode.
  5. Enter "Y" in the 'Registry Setting Value' field.
  6. Submit the form.
  7. Access the 'Client Merge' form.
  8. Select "Client A" in the 'Source Client' field.
  9. Select "Episode # 1" from the 'Source Client Episode' field.
  10. Select "Client B" in the 'Target Client' field.
  11. Validate the 'Create New Episode on Merge' field is displayed.
  12. Select "No" in the 'Create New Episode On Merge' field.
  13. Click [File].
  14. Validate a 'Do you wish to continue with the indicated action?' message is displayed.
  15. Click [Yes].
  16. Validate a message stating 'The following episode has been updated for the target client indicated to include data from the source. Episode 1.
  17. Click [OK] and close the form.
  18. Access Crystal Reports or other SQL Reporting Tool.
  19. Create a report using the 'SYSTEM.client_merge_log' SQL table.
  20. Validate the merged client data is displayed as expected.
  21. Close the report.
Scenario 2: Client Merge - Validate the 'Allow Merging Of All Client Data Through Single Filing' registry setting
Specific Setup:
  • Three clients are admitted into existing episodes in different outpatient programs (Client A, Client B, Client C).
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Allow Merging Of All Client Data" 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->System Maintenance->Client Merge->->->Allow Merging Of All Client Data Through Single Filing.
  5. Enter "Y" in the 'Registry Setting Value' field.
  6. Submit the form.
  7. Access the 'Client Merge' form.
  8. Select "Client A" in the 'Source Client' field.
  9. Validate the 'Merge All Client Data Through Single Filing' field is displayed.
  10. Select "Yes" in the 'Merge All Client Data Through Single Filing' field.
  11. Select "Client B" in the 'Target Client' field.
  12. Click [File].
  13. Validate a "Client Merge" message is displayed stating: Do you wish to continue with the indicated action.
  14. Click [Yes].
  15. Validate a "Client Merge" message is displayed stating: All information has been merged into the target client and the source client has been deleted from the system.
  16. Click [OK].
  17. Close the form.
  18. Access Crystal Reports or other SQL Reporting Tool.
  19. Create a report using the 'SYSTEM.client_merge_log' SQL table.
  20. Validate the merged client data is displayed as expected.
  21. Close the report.
Topics
• Registry Settings • Admission (Outpatient) • Client Merge • Query/Reporting • Admission
Update 89 Summary | Details
Delete Bed Assignment
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Discharge
  • Delete Bed Assignment
Scenario 1: Delete Bed Assignment - Discharged Patient
Specific Setup:
  • Admission:
  • An existing inpatient client is identified, or a new client is admitted and assigned room and bed is noted.
Steps
  1. Open "Bed Assignment" form.
  2. Enter the 'Client ID'.
  3. Validate the 'Date Of Bed Assignment' populates value assigned during client admission.
  4. Validate the 'Room' populates value assigned during client admission.
  5. Validate the 'Bed' populates value assigned during client admission.
  6. Select desired bed from 'Bed'.
  7. Validate the 'Room And Board Billing Code' populates value assigned during client admission.
  8. Click [Submit].
  9. Open "Discharge" form.
  10. Enter the 'Client ID'.
  11. Select any date in 'Date of Discharge'.
  12. Enter any time in 'Discharge Time'.
  13. Select any reason from 'Type of Discharge'.
  14. Enter the desired 'Discharge Practitioner'.
  15. Click [Submit].
  16. Open "Delete Bed Assignment" form.
  17. Enter the 'Client ID'.
  18. Validate the dialog: 'No caseload access' set any desired reason.
  19. Click [OK].
  20. Select desired 'Episode #' from 'Episode'.
  21. Select desired bed assignment to delete in 'Bed Assignment To Delete'.
  22. Click [Submit].
  23. Validate dialog message: 'Deleted'.
  24. Click [OK]
  25. Click [No].
Scenario 2: Delete Bed Assignment - Active Patient
Specific Setup:
  • Admission:
  • An existing inpatient client is identified, or a new client is admitted and assigned room and bed is noted.
Steps
  1. Open "Bed Assignment" form.
  2. Enter the 'Client ID'.
  3. Validate the 'Date Of Bed Assignment' populates value assigned during client admission.
  4. Validate the 'Room' populates value assigned during client admission.
  5. Validate the 'Bed' populates value assigned during client admission.
  6. Select desired bed from 'Bed'.
  7. Validate the 'Room And Board Billing Code' populates value assigned during client admission.
  8. Click [Submit].
  9. Open "Delete Bed Assignment" form.
  10. Enter the 'Client ID'.
  11. Validate the dialog: 'No caseload access' set any desired reason.
  12. Click [OK].
  13. Select desired 'Episode #' from 'Episode'.
  14. Select desired bed assignment to delete in 'Bed Assignment To Delete'.
  15. Click [Submit].
  16. Validate dialog message: 'Deleted'.
  17. Click [OK]
  18. Click [No].
Topics
• Bed Assignment
Update 92 Summary | Details
Real Time Inquiry (270) Request
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
  • Real Time Inquiry (270) Request
Scenario 1: Cal PM - Real Time Inquiry (270) Request
Specific Setup:
  • Avatar Cal-PM Registry Setting: Enable 270/271 Transaction Sets = Y.
  • Client record eligible for real-time 270 Eligibility Request submission entry in Avatar Cal-PM/Netsmart
Steps
  1. Open "Real Time Inquiry (270) Request".
  2. Verify that the field '271 Eligibility Benefit Response Data' exists on the form.
  3. Enter/select desired 'Client ID'.
  4. Select desired 'Episode Number'.
  5. Select desired 'Guarantor'.
  6. Select desired 'Request Type'.
  7. As desired, enter/select data for other fields.
  8. Click [Process Request].
  9. Click [OK] on the process message.
  10. Verify that the response data displays in the '271 Eligibility Benefit Response Data' field.
  11. Close the form.
Topics
• Real Time Inquiry (270) Request
Update 95 Summary | Details
Registry Settings - Enable LA County Reporting Requirements
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Cal-OMS Discharge
  • Discharge (Outpatient)
Scenario 1: 'Cal-OMS Discharge' - Registry Setting - 'Enable LA County Reporting Requirements'
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' = desired value. Note the value
  • Avatar Cal-PM Registry Setting 'Enable Form Serial Number in Cal-OMS Admission' may optionally be enabled/disabled
  • Avatar Cal-PM Registry Setting 'Allow Edit of Form Serial Number in Cal-OMS Admission' may optionally be enabled/disabled
  • One or more client(s) with episodes eligible for 'Cal-OMS Discharge' record filing
  • Crystal Reports or other SQL reporting tool
Steps
  1. Open Avatar Cal-PM 'Cal-OMS Discharge' form.
  2. Select client record/Cal-OMS Admission episode for Cal-OMS Discharge entry/edit.
  3. Click 'Add' button to enter new Cal-OMS Discharge record or select existing Cal-OMS Discharge record for view/edit in pre-display and click 'Edit' button.
  4. Enter/select value for 'Discharge Date'.
  5. Ensure 'Form Serial Number' is present in form; ensure 'Form Serial Number' field is disabled/read-only.
  6. Ensure 'Form Serial Number' field contains/displays Form Serial Number value from associated Cal-OMS Admission record/selected 'Associated Level of Care' record (where Registry Setting 'Enable Form Serial Number in Cal-OMS Admission' is enabled; otherwise, field will remain blank/contain no value).
  7. Navigate to 'Medical/Physical Health Data' section of form.
  8. Select value for 'Which of the following medications did you take as part of treatment?' field (if enabled/present).
  9. In case where 'Methadone' is selected for 'Which of the following medications did you take as part of treatment?' field, ensure the following validation is present:
  10. Where Registry Setting 'Enable LA County Reporting Requirements' is disabled with value 'N' - ensure that the ''Which of the following medications did you take as part of treatment?' field is not on the form.
  11. Where Registry Setting 'Enable LA County Reporting Requirements' is enabled with value 'Y' - ensure that the field is included and the following message displays: You can only select Methadone if the 'Level of Care Admitted' is Opioid Treatment Program.
  12. Where Registry Setting 'Enable LA County Reporting Requirements' is enabled with value 'YC' - ensure that the field is on the form and no message is received.
  13. Enter/select values for all other 'Cal-OMS Discharge' form fields as required/desired.
  14. Click 'Submit' button to file 'Cal-OMS Discharge' form/record.
  15. Open Crystal Reports or other SQL reporting tool.
  16. In Avatar Cal-PM SQL table 'SYSTEM.cal_oms_discharge', ensure that 'form_serial_number' field is present and reflects data filed via 'Cal-OMS Discharge' form 'Form Serial Number' field.
  17. In case where Form Serial Number value for associated Cal-OMS Admission record is edited/updated (where Registry Setting 'Allow Edit of Form Serial Number in Cal-OMS Admission' is enabled) - ensure that 'Form Serial Number' value for any associated Cal-OMS Discharge record is updated to same value (may be confirmed via 'Cal-OMS Discharge' form and/or SQL table 'SYSTEM.cal_oms_discharge').
Scenario 2: 'Cal-OMS Admission' - Registry Setting - 'Enable LA County Reporting Requirements'
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' = 'YC'.
  • Client record eligible for Cal-OMS Admission record entry/edit.
Steps
  1. Open Avatar Cal-PM 'Cal-OMS Admission' form.
  2. Select client/episode for Cal-OMS Admission entry (or select existing Cal-OMS Admission record for view/edit).
  3. Enter/select values for required form fields in first/main section of form.
  4. Navigate to 'Medical/Physical Health Data' section of form.
  5. Select value for 'Which of the following medication is prescribed as part of treatment?' field (or 'Medication is prescribed as part of treatment' field).
  6. In case where 'Methadone' is selected for 'Which of the following medication is prescribed as part of treatment?' field, ensure the following validation is present:
  7. Where Registry Setting 'Enable LA County Reporting Requirements' is disabled with value 'N' - ensure that user is presented with error dialog noting 'You can only select Methadone if the 'Level of Care Admitted' is Opioid Treatment Program' and 'Methadone' value/selection is allowed
  8. Where Registry Setting 'Enable LA County Reporting Requirements' is enabled with value 'Y' - ensure that user is presented with error dialog noting 'You can only select Methadone if the 'Level of Care Admitted' is Opioid Treatment Program' and 'Methadone' value/selection is allowed
  9. Where Registry Setting 'Enable LA County Reporting Requirements' is enabled with value 'YC' - ensure that if 'Level of Care Admitted' for selected episode/location of admission is not 'Opioid Treatment Program' user is not presented with error dialog noting 'You can only select Methadone if the 'Level of Care Admitted' is Opioid Treatment Program' and 'Methadone' value/selection is not allowed
Topics
• Registry Settings • Cal-OMS
 

Avatar_Cal-PM_2024_Monthly_Release_2024.02.00_Details.csv