Skip to main content

Avatar Cal-PM 2024 Quarterly Release 2024.01 Acceptance Tests


Update 1 Summary | Details
2024 Update installation
Scenario 1: Validate Upgrading Avatar Cal-PM 2023 to 2024 is successful when 2023.04.00 is loaded
Specific Setup:
  • Latest Monthly Release is installed.
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 Code 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 3 Summary | Details
Cal-OMS Submission - Cal-OMS Annual Update
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Cal-OMS Submission
  • Cal-OMS Annual Update
Scenario 1: Cal-OMS Submission - Annual update.
Specific Setup:
  • Registry Setting:
  • The 'Allow Multiple Cal-OMS Admissions Per Avatar Episode' is set to 'Y'.
  • The 'Enforce Annual Update Date Rule' registry setting is set to 'Y'
  • The 'Enable LA County Reporting Requirements' registry setting is set to 'N'.
  • The 'Enforce Monthly Reporting' registry setting is set to 'N'.
  • Program Maintenance:
  • Create a new Cal-OMS program or identify an existing program for use.
  • The 'Substance Abuse Program (Cal-OMS)' field should be selected as 'Yes (Reportable)'.
  • The 'Provider ID (CalOMS)' field should contain a value. (Not more than 6 digits).
  • Note the program code/name.
  • Admission:
  • A new client is admitted to the program defined above. Note the client's id/name.
  • Client A.
  • Cal-Oms Admission:
  • The 'Cal-OMS Admission' is created with all the required data using the 'Cal-OMS Admission' form for Client A.
Steps
  1. Open the 'Cal-OMS Submission' form.
  2. Set the 'Option' field to 'Compile' and enter the 'Through Date' value which will include Cal-OMS Admission record(s).
  3. Click the 'Submit' button for Cal-OMS Submission file compilation.
  4. Ensure that file compilation is completed successfully.
  5. Set the 'Option' field to 'Print' and select compiled Cal-OMS Submission file.
  6. In Cal-OMS Submission compiled data/records (opened using the 'Print Selected File Error(s)' button), ensure that compiled Cal-OMS admission data for 'Client A' is shown.
  7. Close the report.
  8. Set the 'Option' field to 'Submit (Create File)'.
  9. Select the compiled Cal-OMS Submission file from the 'Select File To Print/Submit' field.
  10. Select 'Review' for the 'Create File' field.
  11. Click the 'Submit' button for Cal-OMS Submission file creation.
  12. Validate that upon the successful submission, the text file(s) with the suffix "R" is generated.
  13. Click [OK].
  14. Click [No].
  15. Ensure that Cal-OMS Submission files are created on the server in the designated output directory.
  16. Validate that the Text Files generated have the suffix "R".
  17. Open the .txt files and validate that the details for Cal-OMS admission show up for 'Client A'.
  18. Open the 'Cal-OMS Submission' form.
  19. Set the 'Option' field to 'Submit (Create File)'.
  20. Select the compiled Cal-OMS Submission file from the 'Select File To Print/Submit' field.
  21. Select 'Final' for the 'Create File' field.
  22. Click the 'Submit' button for Cal-OMS Submission file creation.
  23. Validate that upon the successful submission, the text file(s) with the suffix "F" is generated.
  24. Click [OK].
  25. Click [No].
  26. Ensure that Cal-OMS Submission files are created on the server in the designated output directory.
  27. Validate that the Text Files generated have the suffix "F".
  28. Open the .txt files and validate that the details for Cal-OMS admission show up for 'Client A'.
  29. Open the 'Cal-OMS Annual Update' form.
  30. Select 'Client A' and select the respective Episode and the Cal-OMS Admission records in the pre-display.
  31. Validate that the form opens with the relevant data successfully.
  32. Fill out the form with all the required data.
  33. Click [Submit].
  34. Navigate back to the 'Cal-OMS Annual Update' form.
  35. Validate that all the filed data displays properly.
  36. Click [Discard].
  37. Click [Yes].

Topics
• Cal-Oms Admission • Cal-OMS • NX
Update 5 Summary | Details
Compile/Edit/Post/Unpost Roll-Up Services Worklist
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Compile/Edit/Post/Unpost Roll-Up Services Worklist
Scenario 1: Unpost Roll-Up worklist - Validating the 'Unpost Selected Roll-Up Services' workflow
Specific Setup:
  • Clients are admitted and the diagnosis record(s) are created,
  • Client A
  • Client B
  • Financial Eligibility is added to the clients as below,
  • Client A - Guarantor 1.
  • Client B - Guarantor 2.
  • Rollup services and the respective component services are created using the 'Service Codes' form and set up with the fee using the 'Service Fee/Cross Reference Maintenance' form.
  • Rollup 1
  • Component 1(a)
  • Component 1(b)
  • Component 1(c)
  • Rollup 2
  • Component 2(a)
  • Component 2(b)
  • Component 2(c)
  • Rollup 3
  • Component 3(a)
  • Component 3(b)
  • Component 3(c)
  • Using the 'Client Charge Input' form, enter a few component services on different dates for the client(s).
  • Multiple Roll-Up Services Definitions are created that include the above roll-up/ component services.
  • Rollup Definition 1
  • Rollup Definition 2
  • Rollup Definition 3
  • Using the 'Compile Roll-Up Services Worklist' form compile the roll-up Worklist(s).
  • Post the roll-up compiles and use 'Client Ledger' to spot check the roll-up services have been created and the component services have been adjusted appropriately.
  • User Definition:
  • User Definition gives the tester access to the below database table:
  • "rollup_services_unpost"
Steps
  1. Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
  2. Select 'Unpost Selected Roll-Up Services'.
  3. Validate that the 'Roll-Up Worklists' field is empty.
  4. Click [Select Roll-Ups to Unpost].
  5. Validate the received message says, "Missing required fields.".
  6. Click [OK].
  7. Click [Unpost Roll-Ups].
  8. Validate the received message says, "Please select at least one roll-up service to unpost.".
  9. Click [OK].
  10. Click 'Roll-Up Posting Date' in the 'Select By Posting Date or Date of Service' field.
  11. Enter appropriate 'From' and 'To' date(s), that include the roll-ups.
  12. Click 'All Clients' in the 'All or Individual Client' field.
  13. Validate that the 'Roll-Up Worklists' field shows all the roll-up(s) available to unpost with the selected date range.
  14. Validate that the 'Client' search input field is disabled.
  15. Click 'Individual Client' -in the 'All or Individual Client' field.
  16. Validate that the 'Roll-Up Worklists' field is cleared up and empty.
  17. Validate that the 'Client' search input field is now enabled.
  18. Enter 'Client A' in the 'Client search' field and select from the results.
  19. Validate that the 'Roll-Up Worklists' shows with the data that involves 'Client A'.
  20. Select 'All' in the ''Roll-Up Worklists' field.
  21. Click [Select Roll-Ups to Unpost].
  22. Validate that the 'Select Roll-Up Services To Unpost' window opens up with the below filter options with data to select and the grid that has the service details.
  23. Service Code.
  24. Guarantor.
  25. Location.
  26. Practitioner.
  27. In the 'Select Roll-Up Services To Unpost' form, Validate that the Grid shows data that only involves 'Client A'.
  28. Click [Close/Cancel].
  29. Enter 'Client B' in the 'Client search' field and select from the results.
  30. Validate that the 'Roll-Up Worklists' shows with the data that involves 'Client B'.
  31. Select 'All' in the ''Roll-Up Worklists' field.
  32. Click [Select Roll-Ups to Unpost].
  33. Validate that the 'Select Roll-Up Services To Unpost' window opens up with the below filter options with data to select and the grid that has the service details.
  34. Service Code.
  35. Guarantor.
  36. Location.
  37. Practitioner.
  38. In the 'Select Roll-Up Services To Unpost' form, Validate that the Grid shows data that only involves 'Client B'.
  39. Click [Close/Cancel].
  40. Click 'All Clients' -in the 'All or Individual Client' field.
  41. Validate that the 'Client' search input field is disabled.
  42. Validate that the 'Roll-Up Worklists' field now shows all the roll-up(s) available to unpost with the selected date range.
  43. Select 'All' in the ''Roll-Up Worklists' field.
  44. Click [Select Roll-Ups to Unpost].
  45. Validate that the 'Select Roll-Up Services To Unpost' window opens up with the below filter options with data to select and the grid that has the service details.
  46. Service Code.
  47. Guarantor.
  48. Location.
  49. Practitioner.
  50. In the 'Select Roll-Up Services To Unpost' form, Validate that the Grid shows data that involves both 'Client A' and 'Client B'.
  51. Validate that the grid is sorted by the client's last name.
  52. Select and deselect the data from the four selection fields at the top of the screen.
  53. Verify that when checking/ unchecking any of the values in the above four fields, the grid rows are updated with the appropriate roll-up services that match the selection.
  54. Click [Save].
  55. Click [Yes].
  56. Click [Unpost Roll-Ups].
  57. Validate the received message says, "Roll-up unposting complete."
  58. Click [OK].
  59. Validate that the Report Viewer opens up.
  60. Verify that the report contains all the roll-up data that are successfully unposted.
  61. Close the Report.
  62. Query the below tables and verify that the posted roll-up data is displayed correctly:
  63. "rollup_services_unpost"
  64. Close the SQL Querying window.
Scenario 2: Unpost Roll-Up worklist - 'Unpost Selected Roll-Up Services' Grid/ Additional Error validation.
Specific Setup:
  • Clients are admitted and the diagnosis record(s) are created,
  • Client A
  • Client B
  • Financial Eligibility is added to the clients as below,
  • Client A - Guarantor 1.
  • Client B - Guarantor 2.
  • Rollup services and the respective component services are created using the 'Service Codes' form and set up with the fee using the 'Service Fee/Cross Reference Maintenance' form.
  • Rollup 1
  • Component 1(a)
  • Component 1(b)
  • Component 1(c)
  • Rollup 2
  • Component 2(a)
  • Component 2(b)
  • Component 2(c)
  • Rollup 3
  • Component 3(a)
  • Component 3(b)
  • Component 3(c)
  • Using the 'Client Charge Input' form, enter a few component services on different dates for the client(s).
  • Multiple Roll-Up Services Definitions are created that include the above roll-up/ component services.
  • Rollup Definition 1
  • Rollup Definition 2
  • Rollup Definition 3
  • Using the 'Compile Roll-Up Services Worklist' form compile the roll-up Worklist(s).
  • Post the roll-up compiles and use 'Client Ledger' to spot check the roll-up services have been created and the component services have been adjusted appropriately.
  • Roll-Up already claimed:
  • Using the 'Electronic Billing' form, create claims for some roll-up services that have already been compiled and posted.
  • Roll_Up has a payment, adjustment, or transfer posted:
  • Post a payment, adjustment, or transfer against some existing roll-up services.
  • User Definition:
  • User should be added permissions for the below database table,
  • "rollup_unpost_errors"
Steps
  1. Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
  2. Select 'Unpost Selected Roll-Up Services'.
  3. Click 'Roll-Up Posting Date' in the 'Select By Posting Date or Date of Service' field.
  4. Enter appropriate 'From' and 'To' date(s), that include our roll-ups.
  5. Click 'Individual Client' -in the 'All or Individual Client' field.
  6. Enter 'Client A' in the 'Client search' field and select from the results.
  7. Validate that the 'Roll-Up Worklists' shows with the data that involves 'Client A'.
  8. Select the roll-ups that have Payments/ Adjustments/ Transfers for the services.
  9. Click [Select Roll-Ups to Unpost].
  10. Validate that the 'Select Roll-Up Services To Unpost' window opens up with the below filter options with data to select and the grid that has the service details.
  11. Service Code.
  12. Guarantor.
  13. Location.
  14. Practitioner.
  15. In the 'Select Roll-Up Services To Unpost' form, Validate that the 'Pmt/Adj' column fields show a "Y" for the services that have Payments/ Adjustments/Transfers.
  16. Select the service row for which the 'Pmt/Adj' fields show a "Y".
  17. Click [Save].
  18. Click [Yes].
  19. Click [Unpost Roll-Ups].
  20. Validate that the received message says "Roll-up unposting complete. Errors found."
  21. Click [OK].
  22. Validate that the Report Viewer opens up.
  23. Verify that the report contains 'No Data Found For Report' with the 'Roll-Up Services Unpost Errors' link.
  24. Click the 'Roll-Up Services Unpost Errors' link.
  25. Validate that the 'Roll-Up Services Unpost Errors' have the error detail concerning the payment/ Adjustment/ transfer posted to the roll-up service.
  26. Close the Report.
  27. Repeat steps 3 to 7 for 'Client B'.
  28. Select the roll-ups that have Claims for the services.
  29. Click [Select Roll-Ups to Unpost].
  30. Validate that the 'Select Roll-Up Services To Unpost' window opens up with the below filter options with data to select and the grid that has the service details.
  31. Service Code.
  32. Guarantor.
  33. Location.
  34. Practitioner.
  35. In the 'Select Roll-Up Services To Unpost' form, Validate that the 'Claim #' column fields show the Claim number for the services that are already claimed.
  36. Select the service row for which the 'Claim #' column fields have the Claim number.
  37. Click [Save].
  38. Click [Yes].
  39. Click [Unpost Roll-Ups].
  40. Validate that the received message says "Roll-up unposting complete. Errors found."
  41. Click [OK].
  42. Validate that the Report Viewer opens up.
  43. Verify that the report contains 'No Data Found For Report' with the 'Roll-Up Services Unpost Errors' link.
  44. Click the 'Roll-Up Services Unpost Errors' link.
  45. Validate that the 'Roll-Up Services Unpost Errors' have the error detail concerning the roll-up service that has been claimed along with the claim number(s).
  46. Close the Report.
  47. Query the below tables and verify that the error details are captured and shown correctly,
  48. "rollup_unpost_errors"
  49. Close the SQL Querying window.
Roll-Up Services Definition - Roll-Up Add-On Codes If Present
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Roll-Up Services Definition
  • Compile/Edit/Post/Unpost Roll-Up Services Worklist
Scenario 1: Roll-Up Services Definition - Validating the form with the new field 'Roll-Up Add-On Codes If Present'
Specific Setup:
  • Rollup services and the respective component services are created using the 'Service Codes' form and set up with the fee using the 'Service Fee/Cross Reference Maintenance' form.
  • Rollup 1
  • Component 1(a)
  • Component 1(b)
  • Component 1(c)
Steps
  1. Open ‘Roll-Up Services Definition’.
  2. Validate that the new field 'Roll-Up Add-On Codes If Present' exists with the below options,
  3. Yes.
  4. No.
  5. Validate that by default no options are selected.
  6. Click 'Add' in 'Add/Edit/Delete Roll-Up Service Definition'.
  7. Set any desired value to the 'Roll-Up Description' field.
  8. Rollup Definition 1.
  9. Select 'Rollup 1' from the Roll-Up Service field.
  10. Select the below services in the 'Component Services' field.
  11. Component 1(a).
  12. Component 1(b).
  13. Component 1(c).
  14. Fill in all the required fields.
  15. Select 'Yes' in 'Roll-Up Add-On Codes If Present'.
  16. Click [Submit].
  17. Validate a message is received stating "Roll-Up Services Definition has completed. Do you wish to return to form?".
  18. Click [No].
  19. Open ‘Roll-Up Services Definition’.
  20. Click 'Edit' in 'Add/Edit/Delete Roll-Up Service Definition'.
  21. Select 'Rollup Definition 1' from 'Existing Roll-Up Definition'.
  22. Validate that the field 'Roll-Up Add-On Codes If Present' is retained with the value 'Yes'.
  23. Click [Discard].
  24. Click [Yes].
  25. Query the below table and validate that the columns 'roll_up_add_on_code' and 'roll_up_add_on_value' are shown with the values 'Y' and 'Yes' respectively for 'Rollup Definition 1'.
  26. "rollup_services_def".
  27. Close the SQL query viewer and return to the NX application window.
  28. Open ‘Roll-Up Services Definition’.
  29. Click 'Edit' in 'Add/Edit/Delete Roll-Up Service Definition'.
  30. Select 'Rollup Definition 1' from 'Existing Roll-Up Definition'.
  31. Select 'No' in 'Roll-Up Add-On Codes If Present'.
  32. Click [Submit].
  33. Click [No].
  34. Query the below table and validate that the columns 'roll_up_add_on_code' and 'roll_up_add_on_value' are shown with the values 'N' and 'No' respectively for 'Rollup Definition 1'.
  35. "rollup_services_def".
  36. Close the SQL query viewer and return to the NX application window.
  37. Open ‘Roll-Up Services Definition’.
  38. Click 'Edit' in 'Add/Edit/Delete Roll-Up Service Definition'.
  39. Select 'Rollup Definition 1' from 'Existing Roll-Up Definition'.
  40. Clear the current selection in 'Roll-Up Add-On Codes If Present' by selecting the option and pressing the 'F5' key.
  41. Click [Submit].
  42. Click [No].
  43. Query the below table and validate that the columns 'roll_up_add_on_code' and 'roll_up_add_on_value' are shown with the values '[NULL]' and 'No Entry' respectively for 'Rollup Definition 1'.
  44. "rollup_services_def".
  45. Close the SQL query viewer and return to the NX application window.
Scenario 2: Roll-Up Services Definition - Validating the Roll-Up process with the new field 'Roll-Up Add-On Codes If Present'
Specific Setup:
  • A client got admitted and the diagnosis record(s) were created,
  • Client A
  • Financial Eligibility is added to the clients as below,
  • Client A - Guarantor 1.
  • Rollup service, component service, and add-on services are created using the 'Service Codes' form and set up with the fee using the 'Service Fee/Cross Reference Maintenance' form.
  • Rollup 1 (Roll up code)
  • Component 1 (Component code)
  • AddOn 1 (select 'Add-On Code' for the 'Service Code Category' and Select 'Evaluation Management' for the 'Service Code Type').
  • AddOn 2 (select 'Interactive Complexity' for the 'Service Code Category').
  • Roll-Up Services Definition:
  • Roll-Up Services Definition is created that includes the above roll-up/component services.
  • Rollup Definition 1
  • Do not include the service codes of the add-on services in the list of component services.
  • In the new field- 'Roll-Up Add-On Codes If Present' field, select 'Yes'.
Steps
  1. Open 'Client Charge Input'.
  2. For 'Client A' create charges with the component service(s) of the roll-up as below
  3. Date 1 - Component 1(a)
  4. Select AddOn 1 and AddOn 2 in the 'Additional Information'.
  5. Set any desired value in the 'Psychotherapy Add-On Duration' field, such as 15 or 30 minutes.
  6. Date 2 - Component 1(a), Component 1(b)
  7. Select AddOn 1 and AddOn 2 in the 'Additional Information'.
  8. Set any desired value in the 'Psychotherapy Add-On Duration' field, such as 15 or 30 minutes.
  9. Close the 'Client Charge Input' form.
  10. Open 'Client Ledger'.
  11. Select 'Client A'.
  12. Click 'All Episodes'.
  13. Click 'Simple'.
  14. Click [Process].
  15. Validate that the ledger shows all the component services along with the service add-ons for the respective dates.
  16. Close the report.
  17. Click [No].
  18. Open 'Compile/Edit/Post/Unpost Roll-Up Services Worklist'.
  19. Set the 'From' and 'To' date that covers the services created in Step 2.
  20. Select 'Rollup Definition 1' from 'Roll-Up Definitions'.
  21. Click [Compile Worklist].
  22. Validate a message is received stating "Compile complete.".
  23. Click [OK].
  24. Click [Run Report].
  25. Validate that the primary service('Component 1') and both of its add-on services(AddOn 1 and AddOn 2) are included in the Worklist.
  26. Close the report.
  27. Click 'Post Roll-Up Services Worklist'.
  28. Select the compiled Roll-up Worklist in the 'Through Date' field.
  29. Select any desired posting code from the 'Write Off Posting Code' dropdown.
  30. Click [Post Worklist].
  31. Validate a message is received stating "Post complete.".
  32. Click [OK].
  33. Click [Discard].
  34. Click [Yes].
  35. Open 'Client Ledger'.
  36. Select 'Client A'.
  37. Click 'All Episodes'.
  38. Click 'Simple'.
  39. Click [Process].
  40. Validate that the roll-up service was created and that the primary service and two add-on services are marked as "RollUp" and have been written off.
  41. Close the report.
  42. Click [No].
  43. Open ‘Roll-Up Services Definition’.
  44. Select 'Edit' from the 'Add/Edit/Delete Roll-Up Service Definition' field.
  45. Select 'Rollup Definition 1' from the 'Existing Roll-Up Definition' dropdown list.
  46. Validate that all the fields are populated with the data for the 'Rollup Definition 1'.
  47. Select 'No' for 'Roll-Up Add-On Codes If Present'.
  48. Click [Submit].
  49. Click [No].
  50. Repeat Steps 1 to 18 for some different date(s).
  51. Validate that the add-on services are not included in the Worklist report.
  52. Close the report.
  53. Click 'Post Roll-Up Services Worklist'.
  54. Select the compiled Roll-up Worklist in the 'Through Date' field.
  55. Select any desired posting code from the 'Write Off Posting Code' dropdown.
  56. Click [Post Worklist].
  57. Validate a message is received stating "Post complete.".
  58. Click [OK].
  59. Click [Discard].
  60. Click [Yes].
  61. Open 'Client Ledger'.
  62. Select 'Client A'.
  63. Click 'All Episodes'.
  64. Click 'Simple'.
  65. Click [Process].
  66. Validate that the add-on services are not included during the roll-up and not adjusted off.
  67. Close the report.
  68. Click [No].
  69. Open 'Compile/Edit/Post/Unpost Roll-Up Services Worklist'.
  70. Select 'Unpost Last Roll-Up Services Worklist'.
  71. Select the posted roll-up Worklist from the 'Through Date' dropdown.
  72. Click [Unpost Worklist].
  73. Validate a message is received stating "Unpost complete.".
  74. Click [OK].
  75. Click [Discard].
  76. Click [Yes].
  77. Open 'Client Ledger'.
  78. Select 'Client A'.
  79. Click 'All Episodes'.
  80. Click 'Simple'.
  81. Click [Process].
  82. Validate that the roll-up service is removed and that the adjustments are removed from the component service and the two add-on services.
  83. Close the report.
  84. Click [No].
Roll-Up Services Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Roll-Up Services Definition
  • Compile/Edit/Post/Unpost Roll-Up Services Worklist
Scenario 1: Roll-Up Services Definition - Validating the New Registry Setting 'Prevent Roll-Up From Happening If There Is Only One Component Service'
Specific Setup:
  • Rollup services and the respective component services are created using the 'Service Codes' form and set up with the fee using the 'Service Fee/Cross Reference Maintenance' form.
  • Rollup 1
  • Component 1(a)
  • Component 1(b)
  • Component 1(c)
  • Roll-Up Services Definition is created that includes the above roll-up/component services.
  • Rollup Definition 1
Steps
  1. Open ‘Registry Settings’.
  2. Search for the 'Prevent Roll-Up From Happening If There Is Only One Component Service' setting and select it.
  3. Validate that initially the Registry Setting Value text is defaulted to "N".
  4. Try to enter a value that is more than one character in the 'Registry Setting Value' field and exit the field.
  5. Validate the error message displays saying, "The selected value is not valid in the current system code for the following reason: More than 1 character".
  6. Click [OK].
  7. Try to enter a value that is one character anything other than 'Y' or 'N' in the 'Registry Setting Value' field and exit the field.
  8. Validate the error message displays saying, "The selected value is not valid in the current system code for the following reason: Response must be 'Y' or 'N'".
  9. Click [OK].
  10. Click [Submit].
  11. Click [OK].
  12. Click [No].
  13. Open ‘Roll-Up Services Definition’.
  14. Validate that the new field 'Prevent Roll-Up From Happening If There Is Only One Component Service' does not exist in the form.
  15. Click [Discard].
  16. Open ‘Registry Settings’.
  17. Search for the 'Prevent Roll-Up From Happening If There Is Only One Component Service' setting and select it.
  18. Set the 'Registry Setting Value' field value to "Y".
  19. Click [Submit].
  20. Click [OK].
  21. Click [No].
  22. Open ‘Roll-Up Services Definition’.
  23. Select 'Edit' from the 'Add/Edit/Delete Roll-Up Service Definition' field.
  24. Select 'Rollup Definition 1' from the 'Existing Roll-Up Definition' dropdown list.
  25. Validate that all the fields are populated with the data for the 'Rollup Definition 1'.
  26. Validate that the new field 'Prevent Roll-Up From Happening For A Client If There Is Only One Component Service' exists with the below options:
  27. Yes
  28. No
  29. Validate that no option is selected by default.
  30. Click [Submit].
  31. Click [No].
  32. Query the below table and validate that Columns 'prevent_if_single_code' and 'prevent_if_single_value' have the following values respectively, '[NULL]' and '[NULL]'.
  33. "rollup_services_def"
  34. Close the query window and return to the Avatar NX window.
  35. Open ‘Roll-Up Services Definition’.
  36. Select 'Edit' from the 'Add/Edit/Delete Roll-Up Service Definition' field.
  37. Select 'Rollup Definition 1' from the 'Existing Roll-Up Definition' dropdown list.
  38. Validate that all the fields are populated with the data for the 'Rollup Definition 1'.
  39. Select 'No' for 'Prevent Roll-Up From Happening For A Client If There Is Only One Component Service'.
  40. Click [Submit].
  41. Click [No].
  42. Query the below table and validate that Columns 'prevent_if_single_code' and 'prevent_if_single_value' have the following values respectively, 'N' and 'No'.
  43. "rollup_services_def"
  44. Close the query window and return to the Avatar NX window.
  45. Open ‘Roll-Up Services Definition’.
  46. Select 'Edit' from the 'Add/Edit/Delete Roll-Up Service Definition' field.
  47. Select 'Rollup Definition 1' from the 'Existing Roll-Up Definition' dropdown list.
  48. Validate that all the fields are populated with the data for the 'Rollup Definition 1'.
  49. Validate that the 'Prevent Roll-Up From Happening For A Client If There Is Only One Component Service' field is showing the value filed in Step-36.
  50. Select 'Yes' for 'Prevent Roll-Up From Happening For A Client If There Is Only One Component Service'.
  51. Click [Submit].
  52. Click [No].
  53. Query the below table and validate that Columns 'prevent_if_single_code' and 'prevent_if_single_value' have the following values respectively, 'Y' and 'Yes'.
  54. "rollup_services_def"
  55. Close the SQL Querying window.
Scenario 2: Compile/Post Roll-Up Services Definition - with the New Registry Setting 'Prevent Roll-Up From Happening If There Is Only One Component Service'
Specific Setup:
  • Registry Settings:
  • 'Prevent Roll-Up From Happening For A Client If There Is Only One Component Service' is set to 'Y'.
  • Clients: Client A is admitted and has an active diagnosis and financial eligibility records. The eligibility guarantor is guarantor 1.
  • Rollup services and the respective component services are created using the 'Service Codes' form and set up with the fee using the 'Service Fee/Cross Reference Maintenance' form.
  • Rollup 1
  • Component 1(a)
  • Component 1(b)
  • Roll-Up Services Definition is created that includes the above roll-up/component services.
  • Rollup Definition 1
Steps
  1. Open ‘Roll-Up Services Definition’.
  2. Select 'Edit' from the 'Add/Edit/Delete Roll-Up Service Definition' field.
  3. Select 'Rollup Definition 1' from the 'Existing Roll-Up Definition' dropdown list.
  4. Validate that all the fields are populated with the data for the 'Rollup Definition 1'.
  5. Select desired value in 'Component Service Date Rules'.
  6. Select 'Yes' for 'Prevent Roll-Up From Happening For A Client If There Is Only One Component Service'.
  7. Click [Submit].
  8. Click [No].
  9. Open 'Client Charge Input'.
  10. For 'Client A' create charges with the component service(s) of the roll-up as below
  11. Date 1 - Component 1(a)
  12. Date 2 - Component 1(a), Component 1(b)
  13. Close the 'Client Charge Input' form.
  14. Open 'Client Ledger'.
  15. Select 'Client A'.
  16. Click 'All Episodes'.
  17. Click 'Simple'.
  18. Click [Process].
  19. Validate that the ledger shows the component services for the respective dates.
  20. Close the report.
  21. Click [No].
  22. Open 'Compile/Edit/Post/Unpost Roll-Up Services Worklist'.
  23. Set the 'From' and 'To' dates to cover the services created in Step 10.
  24. Select 'Rollup Definition 1' from 'Roll-Up Definitions'.
  25. Click [Compile Worklist].
  26. Validate that received message says, "Compile complete.".
  27. Click [OK].
  28. Click [Run Report].
  29. Validate that no roll-up was created for the date(s) where there was only one component service entered for 'Client A'.
  30. Validate that a roll-up was created for the date(s) where there are multiple component services.
  31. Close the report.
  32. Click [Discard].
  33. Click [Yes].
  34. Open ‘Roll-Up Services Definition’.
  35. Select 'Edit' from the 'Add/Edit/Delete Roll-Up Service Definition' field.
  36. Select 'Rollup Definition 1' from the 'Existing Roll-Up Definition' dropdown list.
  37. Select 'No' for 'Prevent Roll-Up From Happening For A Client If There Is Only One Component Service'.
  38. Click [Submit].
  39. Click [No].
  40. Open 'Compile/Edit/Post/Unpost Roll-Up Services Worklist'.
  41. Set the 'From' and 'To' dates to cover the services created in Step 10.
  42. Select 'Rollup Definition 1' from 'Roll-Up Definitions'.
  43. Click [Compile Worklist].
  44. Validate that the received message says, "Compile complete.".
  45. Click [OK].
  46. Click [Run Report].
  47. Validate that a roll-up service was created for each component service date, even if there is only one component service on that date for 'Client A'.
  48. Close the report.
  49. Click [Discard].
  50. Click [Yes].
  51. Open ‘Roll-Up Services Definition’.
  52. Select 'Edit' from the 'Add/Edit/Delete Roll-Up Service Definition' field.
  53. Select 'Rollup Definition 1' from the 'Existing Roll-Up Definition' dropdown list.
  54. Validate that all the fields are populated with the data for the 'Rollup Definition 1'.
  55. Select 'Yes' for 'Prevent Roll-Up From Happening For A Client If There Is Only One Component Service'.
  56. Click [Submit].
  57. Click [No].
  58. Open 'Compile/Edit/Post/Unpost Roll-Up Services Worklist'.
  59. Set the 'From' and 'To' dates to cover the services created in Step 10.
  60. Select 'Rollup Definition 1' from 'Roll-Up Definitions'.
  61. Click [Compile Worklist].
  62. Validate that the received message says, "Compile complete.".
  63. Click [OK].
  64. Click [Run Report].
  65. Validate that no roll-up was created for the date(s) where there was only one component service entered for 'Client A'.
  66. Validate that a roll-up was created for the date(s) where there are multiple component services.
  67. Close the report.
  68. Click 'Post Roll-Up Services Worklist'.
  69. Select the compiled Roll-up Worklist in the 'Through Date' field.
  70. Select any desired posting code from the 'Write Off Posting Code' dropdown.
  71. Click [Post Worklist].
  72. Validate the received message says, "Post complete.".
  73. Click [OK].
  74. Click [Discard].
  75. Click [Yes].
  76. Open 'Client Ledger'.
  77. Select 'Client A'.
  78. Click 'All Episodes'.
  79. Click 'Simple'.
  80. Click [Process].
  81. Validate that the ledger shows the component services marked as 'Roll-Up', along with the newly created Roll-Up service as 'Open' only for the dates that have multiple component services.
  82. Validate that the component services are not rolled up and that no Roll-Up service is created for the dates that have only one component service.
  83. Close the report.
  84. Click [No].

Topics
• Compile/Edit/Post/Unpost Roll-up Services Worklist • NX • Roll-Up Service Definition • Registry Settings
Update 6 Summary | Details
Close Charges - Interim Billing Batch
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Open Closed Charges
Scenario 1: Validating 'Close Charges' functionality
Specific Setup:
  • Admit an outpatient client with an active diagnosis and financial eligibility.
  • Render several services to the newly created client.
  • Create an interim billing batch.
Steps
  1. Open the 'Close Charges' form.
  2. Set the "Liability Update Or Close Charges" field to " Close Charges".
  3. Set a date in the "Thru Date" field that includes some, but not all services in the interim batch.
  4. Select "Individual" in the "Individual, All, Or Interim Batch Cycle" field.
  5. Enter a name or ID in the "Client ID" field.
  6. Select an episode in the "Episode Number" field.
  7. Submit the form to close all charges for the client and thru date specified.
  8. Validate the client ledger to ensure the services closed,
  9. Open the 'Close Charges' form.
  10. Set the "Liability Update Or Close Charges" field to " Close Charges".
  11. Set a date in the "Thru Date" field.
  12. Select "Interim Batch Cycle" in the "Individual, All, Or Interim Batch Cycle" field.
  13. Select an Interim Batch Number in the "Interim Batch Number" field.
  14. Submit the form to close all charges for the client and thru date specified.
  15. Validate the client ledger to ensure the services closed.
Scenario 2: Validating 'Close Charges' by 'Interim Batch Cycle' functionality.
Specific Setup:
  • Clients:
  • Client A:
  • Admit an outpatient client with an active diagnosis and financial eligibility.
  • Render four services for four different dates using the Client Charge Input form.
  • Client B:
  • Admit an outpatient client with an active diagnosis and financial eligibility.
  • Render four services for four different dates using the Client Charge Input form.
  • Interim Billing Batch:
  • Batch A:
  • Create an interim billing batch that covers Client A and only covers the first two services.
  • Batch B:
  • Create an interim billing batch that covers Client B and all four services.
  • Registry Setting(s):
  • The "Close Charges By Program And Guarantor Of Batch Only" registry setting should be set to the value 'B'.
Steps
  1. Open the 'Close Charges' form.
  2. Set the "Liability Update Or Close Charges" field to " Close Charges".
  3. Leave the "Thru Date" field blank.
  4. Select "Interim Batch Cycle" in the "Individual, All, Or Interim Batch Cycle" field.
  5. Select Interim 'Batch A' from the "Interim Batch Number" field.
  6. Submit the form to close all charges with the Interim Batch and "Thru Date" not specified.
  7. Open the 'Client Ledger' form.
  8. Select Client A in the "Client ID" field.
  9. Select "All Episodes" in the "Claim/Episode/All Episodes" field.
  10. Select "Simple" in the "Ledger Type" field.
  11. Select "Process".
  12. Validate that only the services that are covered by Interim 'Batch A' are Closed.
  13. Close the report.
  14. Select "No".
  15. Open the 'Open Closed Charges' form.
  16. Select "Individual" in the "Individual, All, Or Interim Batch Cycle" field.
  17. Select Client A in the "Client ID" field.
  18. Select the Episode from the "Episode" field.
  19. Select the "Select Charges To Open" button.
  20. Select all the services by checking them in the 'Open Closed Charges' window.
  21. Click "OK".
  22. Select "Submit".
  23. Select "Yes".
  24. Select "No".
  25. Open the 'Close Charges' form.
  26. Set the "Liability Update Or Close Charges" field to " Close Charges".
  27. Select "T" in the "Thru Date" field.
  28. Select "Interim Batch Cycle" in the "Individual, All, Or Interim Batch Cycle" field.
  29. Select Interim 'Batch A' from the "Interim Batch Number" field.
  30. Submit the form to close all charges with the Interim Batch and "Thru Date" specified as Today.
  31. Open the 'Client Ledger' form.
  32. Select Client A in the "Client ID" field.
  33. Select "All Episodes" in the "Claim/Episode/All Episodes" field.
  34. Select "Simple" in the "Ledger Type" field.
  35. Select "Process".
  36. Validate that only the services that are covered by Interim 'Batch A' are closed.
  37. Close the report.
  38. Select "No".
  39. Open the 'Close Charges' form.
  40. Set the "Liability Update Or Close Charges" field to " Close Charges".
  41. Leave the "Thru Date" field blank.
  42. Select "Interim Batch Cycle" in the "Individual, All, Or Interim Batch Cycle" field.
  43. Select Interim Batch B from the "Interim Batch Number" field.
  44. Submit the form to close all charges with the Interim Batch and "Thru Date" not specified.
  45. Open the 'Client Ledger' form.
  46. Select Client B in the "Client ID" field.
  47. Select "All Episodes" in the "Claim/Episode/All Episodes" field.
  48. Select "Simple" in the "Ledger Type" field.
  49. Select "Process".
  50. Validate that all the services that are covered by Interim ;Batch B' are Closed.
  51. Close the report.
  52. Select "No".
  53. Open the 'Open Closed Charges' form.
  54. Select "Individual" in the "Individual, All, Or Interim Batch Cycle" field.
  55. Select Client B in the "Client ID" field.
  56. Select the Episode from the "Episode" field.
  57. Select the "Select Charges To Open" button.
  58. Select all the services by checking them in the 'Open Closed Charges' window.
  59. Click "OK".
  60. Select "Submit".
  61. Select "Yes".
  62. Select "No".
  63. Open the 'Close Charges' form.
  64. Set the "Liability Update Or Close Charges" field to " Close Charges".
  65. Set the "Thru Date" field with a date that does not cover a few services from 'Batch B'.
  66. Select "Interim Batch Cycle" in the "Individual, All, Or Interim Batch Cycle" field.
  67. Select Interim Batch B from the "Interim Batch Number" field.
  68. Submit the form to close all charges with the Interim Batch and "Thru Date" not specified.
  69. Open the 'Client Ledger' form.
  70. Select Client B in the "Client ID" field.
  71. Select "All Episodes" in the "Claim/Episode/All Episodes" field.
  72. Select "Simple" in the "Ledger Type" field.
  73. Select "Process".
  74. Validate that only the services of Interim 'Batch B' that are covered under the "Thru Date" specified are closed.
  75. Close the report.
  76. Select "No".

Topics
• Close Charges • Interim Billing Batch
Update 7 Summary | Details
RADPlus - Family Entity Modeling
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Change MR#
  • Family Registration
  • Delete Last Movement
  • Table Definition (PM)
  • High Utilizier
  • Delete Family
Scenario 1: Change MR# - "Family" Entity Data validations
Specific Setup:
  • Have an active test client on the system [ClientA], note their current PATID# [OrigPATID#].
  • In form "Family Registration" have a family created [FamilyA], with [ClientA] added as a family member in "Family Members" section of the form.
  • Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing.
  • A row has been filed in [FormA] for [FamilyA], selecting [ClientA] in the "Family Members" field and the document created during submission has been routed and approved.
  • Have a report [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table.
Steps
  1. Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table.
  2. Validate there is a row displayed for [FamilyA] and [ClientA].
  3. Open "Change MR#" form in Avatar PM.
  4. Select [ClientA] in the "Client ID" field and note their current PATID [OrigPATID#].
  5. Click [Assign MR#].
  6. Note the new PATID# assigned, [NewPATID#].
  7. Click [Submit].
  8. Validate the form files successfully.
  9. At the home view, search for the [OrigPATID#] noted in step 3a.
  10. Validate there are no results.
  11. Now search for the [NewPATID#] noted in step 3b.
  12. Validate the [NewPATID#] is found and the associated client is [ClientA].
  13. Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table.
  14. Validate there is a row displayed for [FamilyA] and with new PATID# [NewPATID#] displayed for [ClientA].
Scenario 2: Client Delete - "Family" Entity Data validations
Specific Setup:
  • Have an active test client on the system [ClientA].
  • In form "Family Registration", have a family created [FamilyA] with [ClientA] added as a family member in "Family Members" section of the form.
  • Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing.
  • A row has been filed in [FormA] for [FamilyA], selecting [ClientA] in the "Family Members" field and the document created during submission has been routed and approved.
  • Have a report [ReportA] created to display data in the "SYSTEM.user_modelled_fam_members" table.
  • User has launched [ReportA] and has logged into the system.
Steps
  1. Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table.
  2. Validate there is a row displayed for [FamilyA] and [ClientA].
  3. Open "Client Delete" form.
  4. Select [ClientA] in the "Client ID" field.
  5. Validate an error message is received "Client Must Be Removed From All Families Before Client Can Be Deleted."
  6. Click [OK].
  7. Close the form.
  8. Open form "Family Registration".
  9. Select [FamilyA].
  10. Click the "Family Members" section.
  11. Select the row for [ClientA].
  12. Click [Delete].
  13. Validate the client is removed as a family member.
  14. Submit the form.
  15. Open form "Delete Last Movement".
  16. Select [ClientA].
  17. Select the admission episode from the "Episode Number" field.
  18. Click [Submit].
  19. Click [Yes] to continue.
  20. Validate the form submits successfully.
  21. Open "Client Delete" form.
  22. Select [ClientA] in the "Client ID" field.
  23. Click [Submit].
  24. Validate the form submits successfully.
  25. At the home view, search for [ClientA].
  26. Validate there are no results.
  27. Run [ReportA] to display data in the "SYSTEM.user_modelled_fam_members" table.
  28. Validate there is no longer a row displayed for [FamilyA] and [ClientA].
Scenario 3: "Family" Entity User Modeled Form - Create a new form
Specific Setup:
  • In form "Family Registration" have a family created [FamilyA] with one or more clients added as family member's in "Family Members" section of the form.
Steps
  1. Open form "Envelope Definition".
  2. Click [New Avatar Envelope].
  3. Set the "Envelope Description" field to the desired name [EnvelopeA], for the envelope.
  4. Select "Family" in the "Entity Database" field.
  5. Click the "Yes - Is Envelope Eligible for Export" field.
  6. Click the "Yes - Always Allow Export" field.
  7. Click [Submit].
  8. Validate the form files successfully.
  9. Open form "Table Definition".
  10. At the "Select Avatar Table" prompt enter the desired table name [TableA].
  11. Click [New Avatar Table].
  12. From the "Envelope" dialog field, select [EnvelopeA].
  13. Populate the "Table Name" field with the desired table name [TableA].
  14. Populate the "Table Description" field with the desired description of the table.
  15. Select the "Column Definition" section.
  16. Click [Add New Item].
  17. Select "Family Member(s)" column from the "Type of Column" field.
  18. Populate the "Column Name" field.
  19. Populate the "Column Description" field.
  20. Populate the "Column Label" field.
  21. Validate the "Column Definition" grid contains a row with values just populated.
  22. Click [Add New Item].
  23. Select "Draft/Final (Document Routing)" column from the "Type of Column" field.
  24. Populate the "Column Name" field.
  25. Populate the "Column Description" field.
  26. Populate the "Column Label" field.
  27. Validate the "Column Definition" grid contains a row with values just populated.
  28. Repeat step 4 for any other desired prompts to be added from the "Type of Column" field.
  29. Validate results are as expected.
  30. Click [Submit].
  31. Validate the form files successfully.
  32. Open form "Form Definition".
  33. At the "Select Avatar Table" prompt enter the desired form name [FormA]
  34. Click [New Avatar Form].
  35. From the "Envelope" dialog, select [EnvelopeA].
  36. Populate the "Table Name" field with the desired table name [TableA].
  37. Populate the "Table Description" field with the desired description of the table.
  38. Select a menu location for the form from the "Menu to Place Form Under" field.
  39. Populate the "Form Name" field [FormA].
  40. In the "Primary Table" field, select [TableA].
  41. Click the "Pre-display" section.
  42. Select one or more pre-display columns from the "Primary Table Pre-display" column prompts.
  43. Click the "Section Definition" section.
  44. Click [Add New Item] and populate the "Section Description" field.
  45. Click the "Object Definition" section.
  46. Click [Add New Item].
  47. From the "Table Column" field, select the "Family Member's" column.
  48. Validate the "Object Definition" grid reflect the column added.
  49. From the "Table Column" field, select the "Draft/Final" column.
  50. Validate the "Object Definition" grid reflect the column added.
  51. Repeat step b adding any other columns desired from the "Table Column" field.
  52. Validate the "Object Definition" grid reflect the columns added.
  53. Click [Submit].
  54. Validate the form files successfully.
  55. Open [FormA].
  56. At the "Select Family" prompt, select [FamilyA].
  57. Validate the form loads successfully.
  58. Verify the "Family Member's" field is present and contains each client added as a family member in the set up, along with a check box next to their name.
  59. Verify the "Draft/Final" field is present on the form.
  60. Verify any other fields added during "Form Definition" are present on the form, as expected.
  61. Select values for any desired fields on the form.
  62. Submit the form.
  63. Validate the form files successfully.
Scenario 4: "Family" Entity User Modeled Form - Form submission and Document Routing Validations
Specific Setup:
  • The "Document Management Defaults" form has "Family - User Defined Family" selected in the field "Select Entity Types Allowed".
  • The "Document Management Definition" form has been submitted with a "Form Name" [FName] associated to the "Family" entity in the "Entity Database" field.
  • In form "Family Registration" have a family created [Family] with family members added in "Family Members" section of the form. For the test [ClientA] and [ClientB].
  • Have a user modeled form [Form] created based on the "Family - User Defined Family" entity database.
  • [Form] contains fields from [Table] that include a "Family Member(s)" column type, a field using a "Draft/Final" column type and any other desired field types.
  • [Form] is enabled for document routing with form name [FName] selected in the "Select Type" field.
  • [User] is a staff member who has access to [Form] and [Table].
  • [User] has the "My To do's" widget on their home view.
  • Have a report [Report], set to display data in the "SYSTEM.user_modelled_fam_members" table.
  • Log in as [User].
Steps
  1. Access [Form].
  2. In the "Select Family" prompt, select [Family].
  3. Validate the "Family Member's" prompt has selections for members [ClientA] and [ClientB].
  4. Click "All", to select all members.
  5. Populate any other desired fields on the form.
  6. Select "Draft" in the 'Draft/Final' field.
  7. Click [Submit].
  8. Validate the form files successfully.
  9. Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table.
  10. Validate there is a row displayed for [Family] and [ClientA].
  11. Validate there is a row displayed for [Family] and [ClientB].
  12. Access [Form].
  13. In the "Select Family" prompt, select [Family].
  14. In the pre-display screen, click [Edit] to select the row filed in step 1.
  15. Validate all fields are populated, as expected.
  16. Close the form.
  17. Access [Form].
  18. In the "Select Family" prompt, select [Family].
  19. In the pre-display screen, select the row filed in step 1.
  20. Click [Delete].
  21. Validate the row is removed from the pre-display.
  22. Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table.
  23. Validate the row field for [Family] and [ClientA], has been deleted.
  24. Validate the row field for [Family] and [ClientB], has been deleted.
  25. Access [Form].
  26. In the "Select Family" prompt, select [Family].
  27. Validate the "Family Member's" prompt has selections for members [ClientA] and [ClientB].
  28. Click "All", to select all members.
  29. Populate any other desired fields on the form.
  30. Select "Final in the 'Draft/Final' field.
  31. Click [Submit] and then [OK].
  32. Validate the "Confirm Document" screen displays all data submitted, including clients [ClientA] and [ClientB] listed in the "Family Member's field.
  33. Click [Accept and Route].
  34. Enter the password for the user in the 'Password' field and click [OK].
  35. At the "Route Document to" dialog, add [User] as an approver.
  36. Click [Submit].
  37. Run [Report] to display data in the "SYSTEM.user_modelled_fam_members" table.
  38. Validate there is a row displayed for [Family] and [ClientA].
  39. Validate there is a row displayed for [Family] and [ClientB].
  40. Navigate to the "My To Do's" widget.
  41. Click the "New" tab.
  42. Validate the To Do for [Form] is present in the list.
  43. Validate the "Client" column indicates [Family].
  44. Click [Approve Document].
  45. Validate the document displays all data submitted, including clients [ClientA] and [ClientB] in the "Family Member's" field.
  46. Click [Accept].
  47. Validate the To Do is removed the widget, as expected.
Scenario 5: Delete Family - Form (Submission and Validations)
Specific Setup:
  • Have an active test client on the system [ClientA].
  • In form "Family Registration" have a family created [FamilyA], with [ClientA] added as a family member in "Family Members" section of the form.
  • Have a user modeled form [FormA] created based on the "Family" entity database that's enabled for document routing.
  • File a row for [FamilyA], selecting [ClientA] selected in the "Family Members" field and routing the document to [UserA] to create To do.
  • [UserA] has the "My To do's" widget on their home view.
  • Have a report [ReportA] created to display data in the "SYSTEM.user_modelled_fam_members" table.
  • [UserA] has launched [ReportA] and has logged into the system.
Steps
  1. Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table.
  2. Verify a data row is displayed for the row filed in the set up for [FamilyA] that includes [ClientA].
  3. On the home view, validate a To do exists in the "My To do's" widget for the row filed in [FormA] in the set up.
  4. Open form "Delete Family".
  5. Select [FamilyA].
  6. Validate an error message is displayed stating "The Family has members on file. You must delete all family members in the Family Registration form prior to deleting the family".
  7. Click [OK].
  8. Open form "Family Registration".
  9. Select [FamilyA].
  10. Click the "Family Members" section.
  11. Select each family member row and click delete to remove the row.
  12. Submit the form.
  13. Open form "Delete Family".
  14. Select [FamilyA].
  15. Click [Submit].
  16. At the "Delete Family" dialog, click [Yes].
  17. Validate the message "Family has been Deleted" displays.
  18. Click [OK].
  19. Open form "Delete Family".
  20. Search for [FamilyA].
  21. Validate [FamilyA] is not found.
  22. Return to the "My To Do's" widget.
  23. Validate a To do is no longer present for [FormA] for [ClientA].
  24. Run [ReportA], to display data in the "SYSTEM.user_modelled_fam_members" table.
  25. Verify there are no rows displayed for [FamilyA].

Topics
• Modeling • Change MR# • Family Registration
Update 8 Summary | Details
Avatar MSO to Parent System Service Filing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Electronic Billing
Scenario 1: 'Close Batch' - Avatar MSO to Cal-PM Parent System Service Filing, Verification of Service Unit Values
Specific Setup:
  • Avatar MSO Registry Setting 'Send Units to Avatar PM' must be enabled
  • 'File Services On Closing Of Batch Or Creation of EOB?' must be set to 'Yes' (via Avatar MSO 'MSO to Parent System Integration Mapping' form 'Service Filing' section)
  • One or more 'Approved' status services originating in Avatar MSO and eligible for filing to parent Avatar Cal-PM system
Steps
  1. Open Avatar MSO 'Close Batch' form.
  2. Select Avatar MSO Claims Processing batch containing one or more 'Approved' status claim/services eligible for filing to parent Avatar Cal-PM system (including Avatar MSO 837 'Replacement' claims/services).
  3. Set 'Close Batch' field to 'Yes' (and click 'OK' button to close warning message dialog).
  4. Click 'Submit' button to close batch/file services to parent Avatar Cal-PM system.
  5. Open 'Client Ledger' form in parent Avatar Cal-PM system.
  6. Select 'Client ID' value for client where services are present in Avatar MSO closed status Claims Processing batch.
  7. Select 'Claim/Episode/All Episodes' value.
  8. Select 'Ledger Type' value.
  9. In Client Ledger data - ensure that 'Approved' status original claim services originating in Avatar MSO are present in Avatar Cal-PM system following 'Close Batch' filing (where services are valid for filing to parent system).
  10. In Client Ledger data - ensure that services originating in Avatar MSO are present in Avatar Cal-PM parent system with correct/original 'Service Units' ('UNT') value filed from Avatar MSO (including Avatar MSO 837 'Replacement' claims/services and case where charges are closed in Avatar Cal-PM automatically on service receipt from Avatar MSO, according to Avatar MSO Registry Setting 'Send Units to Avatar PM' ).

Topics
• Close Charges • Electronic Billing
Update 9 Summary | Details
Eligibility Response (271) - Compile Eligibility Inquiry (270) Request
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Eligibility Response (271)
  • Eligibility Inquiry and Response (270/271) Report
Scenario 1: Eligibility Response (271) - Compile 271 eligibility response file based on 270 request.
Specific Setup:
  • System must be setup to create a 270 request for the client/service.
  • Registry Setting:
  • The 'Avatar PM->Billing->Electronic Submissions->Eligibility Inquiry & Response (270/271)->->Enable 270/271 Transaction Sets' registry setting is set to 'Y'.
  • Guarantors/Payors:
  • An existing guarantor is identified to be used. All the required information for the eligibility inquiry and response are populated correctly on the '270 / 271 / 834' section of the form. Note the guarantor's code/name.
  • Guarantor/Program Billing Defaults:
  • All the fields required to compile 270 request and 271 response data are populated correctly for the template that contains desired program and the guarantor.
  • Service codes:
  • An existing service code is identified to be used. The 'Service Type Code (270)' is set up with the desired value. 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:
  • 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.
  • Client Charge Input:
  • A service is rendered to the client using the service code identified above. Note service date, service code.
  • Client Ledger:
  • A service distributed correctly to the assigned guarantor.
  • Close the charges.
  • Eligibility Inquiry (270) Request:
  • An Eligibility Inquiry (270) request is created for a client.
  • A 271 eligibility response file is created based on the information found on the Eligibility Inquiry (270) Submission. Note the path of the location where the 271 response file is located.
Steps
  1. Open the 'Eligibility Response (271)' form.
  2. Load the 271 eligibility response file created in the setup section.
  3. Verify the file loads successfully.
  4. Compile the loaded 271 eligibility response file.
  5. Verify the file compiles successfully.
  6. Select 'Response Data' option from the report.
  7. Verify the system displays data correctly.
  8. Post the compiled 271 eligibility response file.
  9. Verify the file posts successfully.
  10. Open the 'Crystal report' or any other SQL Data Viewer.
  11. Query the billing_271_sub_elig and billing_271_dep_elig tables.
  12. Verify that the data_entry_utc field is present in the table.
Scenario 2: Eligibility Inquiry and Response (270/271) Report field validation
Steps
  1. Open 'Eligibility Inquiry and Response (270/271) Report'.
  2. Enter the 'Client ID' for the client that will not be rejected.
  3. Verify the AMA Trademark displays 'CPT® Codes' above the 'CPT-4 Code' field.
  4. Verify the AMA Copyright Notice displays on the bottom of the form: 'CPT copyright 2021 American Medical Association. All rights reserved.'.
  5. Close the form.

Topics
• Eligibility Response (271) • NX
Update 10 Summary | Details
Avatar Cal-PM 'Electronic Billing' 837 Professional
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Update (PM)
  • Electronic Billing
Scenario 1: 'Guarantor/Program Billing Defaults' - Verification of 'Service Facility Location 2310D/2420C' Registry Setting
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Service Facility Location 2310D/2420C' must be enabled
Steps
  1. Open Avatar Cal-PM 'Guarantor/Program Billing Defaults' form.
  2. Select 'Add Template' in 'Action field (or 'Edit Template' and select existing Guarantor/Program Billing Defaults template for review/edit).
  3. Navigate to '837 Professional' section of form.
  4. Ensure the 'Select Type Of Information To Include In Service Facility Location (2310D/2420C)' field is present in 'Guarantor/Program Billing Defaults' form '837 Professional' section.
  5. Ensure 'Select Type Of Information To Include In Service Facility Location (2310D/2420C)' field includes the following selections/options:
  6. 'Suppress 2310C/2310D (Only if Facility Type Code is NOT '12 - Home' or '10-Telehealth-Patient in Home')'
  7. 'Suppress 2420C (Only if Place Of Service is NOT '12 - Home' or '10-Telehealth-Patient in Home')'
  8. Select values for 'Select Type Of Information To Include In Service Facility Location (2310D/2420C)' field (and any other fields/sections as desired).
  9. Click 'Submit' button to file Guarantor/Program Billing Defaults template.
  10. Select 'Edit Template' in 'Action field and select previously filed Guarantor/Program Billing Defaults template for review/edit.
  11. Navigate to '837 Professional' section of form.
  12. Ensure that previously selected/filed values for 'Select Type Of Information To Include In Service Facility Location (2310D/2420C)' field are present for selected template.
Scenario 2: 'Electronic Billing' - 837 Professional, Verification of Service Facility Location 2310D/2420C Suppression
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Service Facility Location 2310D/2420C' must be enabled
  • One or more 'Location' Dictionary Codes ('Client' Indirect, Data Element 10006) with Extended Dictionary Data Element '(579) Place Of Service (837 Professional)' value must be defined (via 'Dictionary Update' form)
  • One or more values selected for 'Select Type Of Information To Include In Service Facility Location (2310D/2420C)' field for applicable Guarantor/Program for 837 Professional service billing (via 'Guarantor/Program Billing Defaults' form '837 Professional' section)
Steps
  1. Open Avatar Cal-PM 'Electronic Billing' form.
  2. Note, acceptance testing may also be confirmed via Avatar Cal-PM 'Quick Billing' form/functionality
  3. Select 837 Professional in 'Billing Form' field.
  4. Enter/select 837 file sorting criteria, using values which will include service(s) with 'Location' value defined (for Admission program and/or service).
  5. Click 'Process' button to sort/generate 837 Professional file.
  6. Select 'Dump File' in the 'Billing Options' field (or select 'Create File On Server' to review output file directly).
  7. Select 'Print' in the 'Print Or Delete Report' field.
  8. Select 837 Professional file sorted which includes services with 'Location' value defined, and click 'Process' button to display 837 outbound file data.
  9. In Avatar Cal-PM 837 Professional format outbound electronic billing file data - for claims including service(s) with 'Location' value defined, ensure that the Service Facility Location 2310D/2420C loops/segments are included or not included/suppressed according to selections in 'Select Type Of Information To Include In Service Facility Location (2310D/2420C)' Guarantor/Program Billing Defaults field (based on 'Place Of Service (837 Professional)' Extended Dictionary value for 'Location' code):
  10. Examples:
  11. If 'Suppress 2310C/2310D (Only if Facility Type Code is NOT '12 - Home' or '10-Telehealth-Patient in Home')' and/or 'Suppress 2420C (Only if Place Of Service is NOT '12 - Home' or '10-Telehealth-Patient in Home')' are selected for 'Select Type Of Information To Include In Service Facility Location (2310D/2420C)' field...
  12. Ensure that Service Facility Location 2310D and/or 2420C loops (respectively) are not included in 837 Professional claims where 'Place Of Service (837 Professional)' Extended Dictionary value for 'Location' is any value other than '12 - Home' or '10-Telehealth-Patient in Home'
  13. Ensure that Service Facility Location 2310D and/or 2420C loops (respectively) are included in 837 Professional claims where 'Place Of Service (837 Professional)' Extended Dictionary value for 'Location' is value '12 - Home' or '10-Telehealth-Patient in Home'
  14. If 'Suppress 2310C/2310D (Only if Facility Type Code is '12 - Home')' and/or 'Suppress 2420C (Only if Place Of Service Is '12 - Home')' are selected for 'Select Type Of Information To Include In Service Facility Location (2310D/2420C)' field...
  15. Ensure that Service Facility Location 2310D and/or 2420C loops (respectively) are not included in 837 Professional claims where 'Place Of Service (837 Professional)' Extended Dictionary value for 'Location' is value '12 - Home'
  16. Ensure that Service Facility Location 2310D and/or 2420C loops (respectively) are included in 837 Professional claims where 'Place Of Service (837 Professional)' Extended Dictionary value for 'Location' is any value other than '12 - Home'

Topics
• Registry Settings • Guarantor/Program Billing Defaults • Electronic Billing • 837 Professional
Update 12 Summary | Details
Client Lookup - Sub-System Codes
Scenario 1: Registry Setting - Exclude Non-Episodic Clients From Sub-System Code Client Lookup
Specific Setup:
  • The test system has multiple system codes.
  • Note the 'Root' system code.
  • Note a 'Sub-System' code'.
  • Note a user that can log into both system codes.
  • Tester is logged in to the 'Root' system code.
  • A non-episodic client exists in the 'Root' system code only. Note the client ID. If needed, a non-episodic client can be created in the 'Call Intake' form.
  • Registry Setting: 'Exclude Non-Episodic Clients From Sub-System Code Client Lookup' = 'Y'.
  • Validate that the client ID can be found in 'Client Search'.
  • Validate that the following forms open: 'Pre Admit', 'Admission' and 'Admission (Outpatient)'.
  • On each form, a message displays stating: 'Client has not been assigned a permanent Medical Record number. Clients with temporary numbers cannot be admitted. Would you like to assign a permanent MR# now?' 'Click [No].
  • A new message displays stating: 'Client has not been assigned a permanent Medical Record number. Clients with temporary numbers cannot be admitted. To assign an ID # use the Assign Permanent MR # form. Click [OK].
  • Logout of the 'Root' system code.
  • Sign into the 'Sub-System' code.
Steps
  1. Search for the non-episodic client and verify that no search results are returned.
  2. Log out of the 'Sub-System' code.
  3. Log into the 'Root' system code.
  4. Open 'Registry Settings'.
  5. Change the value of ' 'Exclude Non-Episodic Clients From Sub-System Code Client Lookup' to 'Y'.
  6. Validate that the Client Search returns the non-episodic client.
  7. Log out of the 'Root' system code.
  8. Log into the 'Sub-System' code.
  9. Validate that the Client Search returns the non-episodic client.
  10. Validate that the following forms open: 'Pre Admit', 'Admission' and 'Admission (Outpatient)' and that each form contains the same two messages from 'Setup'.

Topics
• Sub-System Code • NX
Update 15 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)
  • Progress Notes (Group and Individual)
  • 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. In addition, validate the following:
  25. The associated 'period' - 'fromDate' field contains the date/time the note was filed, which can be found in the 'SYSTEM.client_practitioner_assignment' SQL table.
  26. The associated 'typeCodes' - 'codes' - 'code' field contains "PCP".
  27. The associated 'typeCodes' - 'codes' - 'displayName' field contains "Primary Care Physician".
  28. Close the report and the form.

Topics
• Progress Notes
Update 17 Summary | Details
274 Provider Directory Submission
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • 274 - Provider Directory Defaults
  • 274 - Provider Directory Definition
  • 274 - Provider Directory Submission
Scenario 1: 274 - worklflow (274 - Provider Directory Defaults, 274 - Provider Directory Definition, 274 - Provider Directory Submission)
Specific Setup:
  • Tester has been given access to the following forms in 'User Definition' under ‘Avatar PM / System Maintenance / System Definition / Health Care Provider Directory (274)’:
  • 274 - Provider Directory Defaults.
  • 274 - Provider Directory Definition.
  • 274 - Provider Directory Submission.
Steps
  1. Open '274 - Provider Directory Defaults'.
  2. Validate that the 'Plan Type' field is required.
  3. Select desired value in 'Plan Type' and validate that the 'Healthcare Plan Code' field becomes required.
  4. Enter desired data for each field.
  5. Submit the form.
  6. Open '274 - Provider Directory Defaults'.
  7. Validate that the submitted data was retained.
  8. Open ‘274 - Provider Directory Definition’.
  9. Validate that the form opened to the ‘Group Definition’ section.
  10. Validate that the 'Plan Type' field is required.
  11. Select desired value in 'Plan Type' and validate that the 'Add or Edit Group' field is required.
  12. Select 'Add' in 'Add or Edit Group'.
  13. Validate that the 'Active' and 'Provider Group Name (2100CA-NM1-03)' fields are required.
  14. Enter desired data for each field.
  15. Click [File Group Details].
  16. Select 'Edit' in 'Add or Edit Group'.
  17. Select the group added above and validate that the submitted data was retained.
  18. Select the 'Site Definition' section.
  19. Validate that the 'Plan Type' field is required.
  20. Select desired value in 'Plan Type' and validate that the 'Add or Edit Site' field is required.
  21. Select 'Add' in 'Add or Edit Site'.
  22. Validate that 'Site or Location of Service Name (2100DA-NM1-03)', 'Provider Group', and 'Active' fields are required.
  23. Validate that the field label 'Site or Location Address (2100DA-N3-01)' has been replaced with 'Site or Location Address (2110DA-N3-01)'.
  24. Validate that the field label 'Site or Location Address 2 (2100DA-N3-02)' has been replaced with 'Site or Location Address 2 (2110DA-N3-02)'.
  25. Enter desired data for each field, which would include nine digit zip codes with a hyphen.
  26. Click [Site Work Schedule (2100DA-WS)].
  27. Enter desired data.
  28. Click [Save].
  29. Click [Yes].
  30. Click [Foreign Languages Spoken At This Site (2100DA-LUI)].
  31. Enter desired data.
  32. Click [Save].
  33. Click [Yes].
  34. Click [Affiliated Entities (2100DB)].
  35. Enter desired data.
  36. Click [Save].
  37. Click [Yes].
  38. Click [File Site Details].
  39. Click [OK].
  40. Select 'Edit' in 'Add or Edit Site'.
  41. Select the 'Provider Site' that was added above and validate that the submitted data was retained.
  42. Select the 'Provider Definition' section.
  43. Validate that the 'Plan Type' field is required.
  44. Select desired value in 'Plan Type' and validate that the 'Provider' field is required.
  45. Select a 'Provider'.
  46. Validate that 'Associated Site' and 'Active' became required.
  47. Enter desired data for each field. Note:
  48. To meet California regulations, when there is data in these fields, 'Additional Provider Name (2100EA-N2-01)' and 'Provider Doing Business As or Trade Name (2100EA-N2-02)', that data is output in the submission file.
  49. If those fields are left blank, the data from the 'Percentage of FTE Serving Children (2100EA-N2-01)' and 'Percentage of FTE Serving Adults (2100EA-N2-01)' fields will be output in the submission file.
  50. When the 'Plan Type' equals 'Mental Health Plan', the value of the field will contain three characters and be zero filled for values less than three digits. A value of '27' is output as '027'.
  51. When the 'Plan Type' equals 'Drug Medi-Cal Organized Delivery System, can contain three characters and be null filled for values less than three digits. A value of '40' is output as '40'.
  52. Click [File Provider Details].
  53. Click [OK].
  54. Select the same 'Provider'.
  55. Select the 'Associated Site' selected above.
  56. Validate that the submitted data was retained.
  57. Close the form.
  58. Open '274 - Provider Directory Submission'.
  59. Validate that the 'Plan Type' field is required.
  60. Select desired value in 'Plan Type' and validate that the
  61. Select 'Compile File' in 'Options'.
  62. Enter the desired value in 'Reporting Period (MM/YY)'.
  63. Enter desired 'File Description'.
  64. Click [Process File].
  65. Validate that the report display and that the zip code fields do not contain a hyphen.
  66. Validate the report data.
  67. Close the report.
  68. Close the form.

Topics
• NX • 274 - Provider Directory
Update 18 Summary | Details
Registry Settings - Utilize Local Workstation Time Zone
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Current Unit Census
  • Official Census Report
Scenario 1: Utilize Local Workstation Time Zone - Validating timestamp on the 'Current Unit Census' report
Steps
  1. Open the 'Registry Setting' form.
  2. Set the 'Utilize Local Workstation Time Zone' registry setting to 'N'.
  3. Set the 'Time Zone Offset' registry setting to desired positive number.(Please note: The value of the registry setting can be between -12 to +14).
  4. Open the 'Current Unit Census' form.
  5. Select 'Individual' in the 'For Individual Unit Or All' field to generate the report for desired unit in the facility.
  6. Select desired unit.
  7. Click [Process].
  8. Verify the report displays the time stamp based on the time change expected due to the 'Time Zone Offset' registry setting.
  9. Verify the report displays RUN TIME that is current server time + Offset value entered in the registry setting. Please note: The 'RUN DATE' will be updated if the RUN TIME is changed to next or previous date to reflect the time zone offset value.
  10. Close the report.
  11. Close the form.
  12. Open the 'Registry Setting' form.
  13. Set the 'Time Zone Offset' registry setting to 0. (Please note: The value of the registry setting can be between -12 to +14).
  14. Open the 'Current Unit Census' form.
  15. Select 'All' in the 'For Individual Unit Or All' field to generate the report for desired unit in the facility.
  16. Click [Process].
  17. Verify the report displays RUN TIME that is current server time because the offset value entered in the registry setting is 0.
  18. Close the report.
  19. Close the form.
  20. Open the 'Registry Setting' form.
  21. Set the 'Time Zone Offset' registry setting to desired negative value. (Please note: The value of the registry setting can be between -12 to +14).
  22. Open the 'Current Unit Census' form.
  23. Select 'All' in the 'For Individual Unit Or All' field to generate the report for desired unit in the facility.
  24. Click [Process].
  25. Verify the report displays RUN TIME that is current server time + Offset value entered in the registry setting. Please note: RUN DATE will be updated if the RUN TIME changed to next or previous date to reflect the time zone offset value.
  26. Close the report.
  27. Close the form.
  28. Open the 'Registry Setting' form.
  29. Set the 'Utilize Local Workstation Time Zone' registry setting to 'Y'.
  30. Open the 'Current Unit Census' form.
  31. Select desired value in the 'For Individual Unit Or All' field to generate the report for desired unit in the facility.
  32. Select desired unit.
  33. Click [Process].
  34. Verify the report displays current workstation date and time as a RUN DATE and RUN TIME.
  35. Close the report.
  36. Close the form.
Scenario 2: Registry Setting - Time Zone Offset - Validating timestamp on the 'Official Census Report'
Steps
  1. Open the 'Registry Setting' form.
  2. Set the 'Utilize Local Workstation Time Zone' registry setting to 'N'.
  3. Set the 'Time Zone Offset' registry setting to desired positive number.(Please note: The value of the registry setting can be between -12 to +14).
  4. Close the form.
  5. Open the 'Official Census Report' form.
  6. Enter the desired date in the 'Date' field.
  7. Select the desired value in the 'Treatment Setting' field.
  8. Click [Process].
  9. Verify the report displays the time stamp based on the time change expected due to the 'Time Zone Offset' registry setting.
  10. Verify the report displays RUN TIME that is current server time + time zone Offset value entered in the registry setting. Please note: The 'RUN DATE' will be updated if the RUN TIME is changed to next or previous date to reflect the time zone offset value.
  11. Close the form.
  12. Close the form.
  13. Open the 'Registry Setting' form.
  14. Set the 'Time Zone Offset' registry setting to 0. (Please note: The value of the registry setting can be between -12 to +14).
  15. Close the form.
  16. Open the 'Official Census Report' form.
  17. Enter the desired date in the 'Date' field.
  18. Select the desired value in the 'Treatment Setting' field.
  19. Click [Process].
  20. Verify the report displays the time stamp based on the time change expected due to the 'Time Zone Offset' registry setting.
  21. Verify the report displays RUN TIME that is current server time + Offset value entered in the registry setting. Please note: The 'RUN DATE' will be updated if the RUN TIME is changed to next or previous date to reflect the time zone offset value.
  22. Close the form.
  23. Close the form.
  24. Open the 'Registry Setting' form.
  25. Set the 'Time Zone Offset' registry setting to desired negative value. (Please note: The value of the registry setting can be between -12 to +14).
  26. Open the 'Official Census Report' form.
  27. Enter the desired date in the 'Date' field.
  28. Select the desired value in the 'Treatment Setting' field.
  29. Click [Process].
  30. Verify the report displays the time stamp based on the time change expected due to the 'Time Zone Offset' registry setting.
  31. Verify the report displays RUN TIME that is current server time + Offset value entered in the registry setting. Please note: The 'RUN DATE' will be updated if the RUN TIME is changed to next or previous date to reflect the time zone offset value.
  32. Close the form.
  33. Close the form.
  34. Set the 'Utilize Local Workstation Time Zone' registry setting to 'Y'.
  35. Open the 'Current Unit Census' form.
  36. Select desired value in the 'For Individual Unit Or All' field to generate the report for desired unit in the facility.
  37. Select desired unit.
  38. Click [Process].
  39. Verify the report displays current workstation date and time as a RUN DATE and RUN TIME.
  40. Close the report.
  41. Close the form.

Topics
• Verify Unit Census • Official Census Report
Update 20 Summary | Details
Web Service - Cal-OMS Admission
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SOAPUI - CalOMSAdmissionSoap - FileCalOMSAdmission
  • SOAPUI - CalOMSAdmissionSoap - FileCalOMSDischarge
Scenario 1: WEBSVC.CalOMSAdmission - Verification of Web Service Filing - Enable LA County Reporting Requirements=YC
Specific Setup:
  • Registry Setting:
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' must be enabled (set to 'YC').
  • Avatar Cal-PM Registry Setting 'Enable Non LA County Requirements' must be enabled (set to 'Y').
  • Admission:
  • A new client is admitted or an existing client is identified. Note the client id, admission program, admission program code to be used as a location of admission.
  • Crystal Reports or other SQL reporting tool.
Steps
  1. Create a SoapUI project for Avatar Cal-PM 'Cal-OMS Admission' web service.
  2. Populate all the required/desired fields to create a Cal-OMS admission record for the client identified. Note all the data defined while creating web service request.
  3. Using the 'Cal-OMS Admission' web service (and/or 'Cal-OMS Admission V2' web service), submit request to 'FileCalOMSAdmission' method to create or update Cal-OMS Admission record.
  4. Confirm 'Cal-OMS Admission' web service responds with confirmation data/ID on successful filing of 'FileCalOMSAdmission' method. Example:"<Confirmation>ClientID:305||EP:1||UniqueID:OMA.001</Confirmation>"
  5. Confirm 'Cal-OMS Admission' web service responds with confirmation message on successful filing of 'FileCalOMSAdmission' method. Example:"<Message>Cal-OMS Admission web service has been filed successfully.</Message>"
  6. Confirm 'Cal-OMS Admission' web service responds with successful status value on successful filing of 'FileCalOMSAdmission' method. Example:"<Status>1</Status>"
  7. Open Avatar Cal-PM 'Cal-OMS Admission' form and select client/episode/Cal-OMS Admission record filed via web service for view/update.
  8. Confirm Cal-OMS Admission record is created/updated in Avatar Cal-PM, with values/data submitted via web service, including the following fields: 'Record To Be Submitted', 'Ethnicity', 'What is your Principal Source of Referral?', 'Primary Drug Route of Administration', 'Secondary Drug Route of Administration', 'Which of the following medication is prescribed as part of treatment?', 'Current Living Arrangements', 'Race 1', 'Race 2', 'Race 3', 'Race 4', 'Race 5'.
  9. Open Crystal Reports or other SQL reporting tool.
  10. In Avatar Cal-PM SQL table 'SYSTEM.cal_oms_admission', ensure data values are filed/present for all fields as filed via web service, including LA-Specific field values noted above.
Scenario 2: WEBSVC.CalOMSDischarge - Verification of Web Service Filing - Enable LA County Reporting Requirements=YC
Specific Setup:
  • Registry Setting:
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' must be enabled (set to 'YC').
  • Avatar Cal-PM Registry Setting 'Enable Non LA County Requirements' must be enabled (set to 'Y').
  • Admission:
  • A new client is admitted or an existing client is identified. Note the client id, admission program, admission program code to be used as a location of admission.
  • Crystal Reports or other SQL reporting tool.
  • Cal-OMS admission is filed for the client and 'GUID' value received from the SYSTEM.cal_oms_admission table to be used in Associated CalOMS admission. Note the value.
Steps
  1. Using the 'Cal-OMS Discharge' web service (and/or 'Cal-OMS Discharge V2' web service), submit request to 'FileCalOMSDischarge' method to create or update Cal-OMS Discharge record.
  2. Confirm 'Cal-OMS Discharge' web service responds with confirmation data/ID on successful filing of 'FileCalOMSDischarge' method. Example <Confirmation>ClientID:305||EP:1||UniqueID:OMD.001</Confirmation>"
  3. Confirm 'Cal-OMS Discharge' web service responds with confirmation message on successful filing of 'FileCalOMSDischarge' method. Example:"<Message>Cal-OMS Discharge web service has been filed successfully.</Message>".
  4. Confirm 'Cal-OMS Discharge' web service responds with successful status value on successful filing of 'FileCalOMSDischarge' method. Example:"<Status>1</Status>".
  5. Open Avatar Cal-PM 'Cal-OMS Discharge' form and select client/episode/Cal-OMS Discharge record filed via web service for view/update.
  6. Confirm Cal-OMS Discharge record is created/updated in Avatar Cal-PM, with values/data submitted via web service.
Scenario 3: WEBSVC.CalOMSAdmission and WEBSVC.CalOMSDischarge - Enable LA County Reporting Requirements=N
Specific Setup:
  • The registry setting 'Enable LA County Reporting Requirements' is set to 'N'.
  • Admission:
  • A new client is admitted or an existing client is identified. Note the client id, admission program, admission program code to be used as a location of admission.
  • Crystal Reports or other SQL reporting tool.

  • The 'Cal-OMS Admission' is submitted for the client with populating data in each field.
  • The GUID value is selected from the 'SYSTEM'.cal_oms_admission table for the client ID.
Steps
  1. Open the SoapUI or any other web service testing tool.
  2. Create a SoapUI project for Avatar Cal-PM 'Cal-OMS Admission' web service.
  3. Create Cal-OMS Admission web service request for the client identified in the setup section with all the fields EXCEPT for the following tags/fields:
  4. *<MedsAsPartOfTreatment>/'Medication Prescribed As Part Of Treatment' = empty
  5. <PregnantAtAdmission>/'Pregnant At Admission' = empty
  6. SecondaryDrugCode = 0
  7. SecondaryDrugFrequency = empty
  8. SecondaryDrugRoute = file empty
  9. SecondaryDrugAgeFirstUse = empty
  10. Using the 'Cal-OMS Admission' web service (and/or 'Cal-OMS Admission V2' web service), submit request to 'FileCalOMSAdmission' method to create or update Cal-OMS Admission record.
  11. Confirm 'Cal-OMS Admission' web service responds with confirmation data/ID on successful filing of 'FileCalOMSAdmission' method. Example:"<Confirmation>ClientID:305||EP:1||UniqueID:OMA.001</Confirmation>".
  12. Confirm 'Cal-OMS Admission' web service responds with confirmation message on successful filing of 'FileCalOMSAdmission' method. Example:"<Message>Cal-OMS Admission web service has been filed successfully.</Message>"
  13. Confirm 'Cal-OMS Admission' web service responds with successful status value on successful filing of 'FileCalOMSAdmission' method. Example:"<Status>1</Status>".
  14. Open Crystal Reports or other SQL reporting tool
  15. Query 'SELECT GUID.* FROM SYSTEM.cal_oms_admission WHERE PATID= [ClientID].
  16. Verify 'GUID' field populates correctly with the unique value. Note this GUID to be used at the time of editing 'WEBSVC.CalOMSDischarge' web service if needed.
  17. Verify the 'meds_part_treatment_code' field defaults to NULL.
  18. Verify the 'meds_part_treatment_value' field defaults to NULL
  19. Verify the 'pregnant_code' field defaults to 0.
  20. Verify the 'pregnant_value' field defaults to No.
  21. Verify the 'sec_drug_code' field defaults to 0.
  22. Verify the 'sec_drug_value' field defaults to None.
  23. Verify the 'sec_drug_first_use' field defaults to 99902
  24. Verify the 'sec_drug_route_code' field defaults to 99902.
  25. Verify the 'sec_drug_route_value' field defaults to None or Not Applicable.
  26. Verify the 'sec_drug_freq' field defaults to 99902.
  27. Close the SQL data viewer tool.
  28. Go back to SoapUI or any other web service testing tool.
  29. Create Cal-OMS Discharge web service request for the client identified in the setup section with all the fields EXCEPT for the following tags/fields:
  30. PregnantDuringTreatment = empty.
  31. SecondaryDrugCode = 0.
  32. SecondaryDrugFrequency = empty.
  33. SecondaryDrugRoute = file empty.
  34. SecondaryDrugAgeFirstUse = empty.
  35. Enter the client ID used above during Cal-OMS admission, episode number, discharge date and status, GUID value in the property 'AssociatedCalOMSAdmission'.
  36. Submit the web service request.
  37. Confirm 'Cal-OMS Admission' web service responds with confirmation data/ID on successful filing of 'FileCalOMSDischarge' method. Example:"<Confirmation>ClientID:305||EP:1||UniqueID:OMD.001</Confirmation>".
  38. Confirm 'Cal-OMS Admission' web service responds with confirmation message on successful filing of 'FileCalOMSDischarge' method. Example:"<Message>Cal-OMS Discharge web service has been filed successfully.</Message>".
  39. Confirm 'Cal-OMS Admission' web service responds with successful status value on successful filing of 'FileCalOMSDischarge' method. Example:"<Status>1</Status>".
  40. Open Crystal Reports or other SQL reporting tool.
  41. Create a Query against 'SYSTEM.cal_oms_discharge' table.
  42. Run the query for the client used in the above step.
  43. Verify 'GUID' field populate correctly with the unique value.
  44. Verify the 'pregnant_code' field defaults to 0.
  45. Verify the 'pregnant_value' field defaults to No.
  46. Verify the 'sec_drug_code' field defaults to 0.
  47. Verify the 'sec_drug_value' field defaults to None.
  48. Verify the 'sec_drug_route_code' field defaults to 99902.
  49. Verify the 'sec_drug_route_value' field defaults to None or Not Applicable.
  50. Verify the 'sec_drug_freq' field defaults to 99902.
  51. Close the SQL data viewer tool.
Web Service - Cal-OMS Discharge
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SOAPUI - CalOMSAdmissionSoap - FileCalOMSDischarge
  • SOAPUI - CalOMSAdmissionSoap - FileCalOMSAdmission
Scenario 1: WEBSVC.CalOMSDischarge - Verification of Web Service Filing - Enable LA County Reporting Requirements=YC
Specific Setup:
  • Registry Setting:
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' must be enabled (set to 'YC').
  • Avatar Cal-PM Registry Setting 'Enable Non LA County Requirements' must be enabled (set to 'Y').
  • Admission:
  • A new client is admitted or an existing client is identified. Note the client id, admission program, admission program code to be used as a location of admission.
  • Crystal Reports or other SQL reporting tool.
  • Cal-OMS admission is filed for the client and 'GUID' value received from the SYSTEM.cal_oms_admission table to be used in Associated CalOMS admission. Note the value.
Steps
  1. Using the 'Cal-OMS Discharge' web service (and/or 'Cal-OMS Discharge V2' web service), submit request to 'FileCalOMSDischarge' method to create or update Cal-OMS Discharge record.
  2. Confirm 'Cal-OMS Discharge' web service responds with confirmation data/ID on successful filing of 'FileCalOMSDischarge' method. Example <Confirmation>ClientID:305||EP:1||UniqueID:OMD.001</Confirmation>"
  3. Confirm 'Cal-OMS Discharge' web service responds with confirmation message on successful filing of 'FileCalOMSDischarge' method. Example:"<Message>Cal-OMS Discharge web service has been filed successfully.</Message>".
  4. Confirm 'Cal-OMS Discharge' web service responds with successful status value on successful filing of 'FileCalOMSDischarge' method. Example:"<Status>1</Status>".
  5. Open Avatar Cal-PM 'Cal-OMS Discharge' form and select client/episode/Cal-OMS Discharge record filed via web service for view/update.
  6. Confirm Cal-OMS Discharge record is created/updated in Avatar Cal-PM, with values/data submitted via web service.
Scenario 2: WEBSVC.CalOMSAdmission and WEBSVC.CalOMSDischarge - Enable LA County Reporting Requirements=N
Specific Setup:
  • The registry setting 'Enable LA County Reporting Requirements' is set to 'N'.
  • Admission:
  • A new client is admitted or an existing client is identified. Note the client id, admission program, admission program code to be used as a location of admission.
  • Crystal Reports or other SQL reporting tool.

  • The 'Cal-OMS Admission' is submitted for the client with populating data in each field.
  • The GUID value is selected from the 'SYSTEM'.cal_oms_admission table for the client ID.
Steps
  1. Open the SoapUI or any other web service testing tool.
  2. Create a SoapUI project for Avatar Cal-PM 'Cal-OMS Admission' web service.
  3. Create Cal-OMS Admission web service request for the client identified in the setup section with all the fields EXCEPT for the following tags/fields:
  4. *<MedsAsPartOfTreatment>/'Medication Prescribed As Part Of Treatment' = empty
  5. <PregnantAtAdmission>/'Pregnant At Admission' = empty
  6. SecondaryDrugCode = 0
  7. SecondaryDrugFrequency = empty
  8. SecondaryDrugRoute = file empty
  9. SecondaryDrugAgeFirstUse = empty
  10. Using the 'Cal-OMS Admission' web service (and/or 'Cal-OMS Admission V2' web service), submit request to 'FileCalOMSAdmission' method to create or update Cal-OMS Admission record.
  11. Confirm 'Cal-OMS Admission' web service responds with confirmation data/ID on successful filing of 'FileCalOMSAdmission' method. Example:"<Confirmation>ClientID:305||EP:1||UniqueID:OMA.001</Confirmation>".
  12. Confirm 'Cal-OMS Admission' web service responds with confirmation message on successful filing of 'FileCalOMSAdmission' method. Example:"<Message>Cal-OMS Admission web service has been filed successfully.</Message>"
  13. Confirm 'Cal-OMS Admission' web service responds with successful status value on successful filing of 'FileCalOMSAdmission' method. Example:"<Status>1</Status>".
  14. Open Crystal Reports or other SQL reporting tool
  15. Query 'SELECT GUID.* FROM SYSTEM.cal_oms_admission WHERE PATID= [ClientID].
  16. Verify 'GUID' field populates correctly with the unique value. Note this GUID to be used at the time of editing 'WEBSVC.CalOMSDischarge' web service if needed.
  17. Verify the 'meds_part_treatment_code' field defaults to NULL.
  18. Verify the 'meds_part_treatment_value' field defaults to NULL
  19. Verify the 'pregnant_code' field defaults to 0.
  20. Verify the 'pregnant_value' field defaults to No.
  21. Verify the 'sec_drug_code' field defaults to 0.
  22. Verify the 'sec_drug_value' field defaults to None.
  23. Verify the 'sec_drug_first_use' field defaults to 99902
  24. Verify the 'sec_drug_route_code' field defaults to 99902.
  25. Verify the 'sec_drug_route_value' field defaults to None or Not Applicable.
  26. Verify the 'sec_drug_freq' field defaults to 99902.
  27. Close the SQL data viewer tool.
  28. Go back to SoapUI or any other web service testing tool.
  29. Create Cal-OMS Discharge web service request for the client identified in the setup section with all the fields EXCEPT for the following tags/fields:
  30. PregnantDuringTreatment = empty.
  31. SecondaryDrugCode = 0.
  32. SecondaryDrugFrequency = empty.
  33. SecondaryDrugRoute = file empty.
  34. SecondaryDrugAgeFirstUse = empty.
  35. Enter the client ID used above during Cal-OMS admission, episode number, discharge date and status, GUID value in the property 'AssociatedCalOMSAdmission'.
  36. Submit the web service request.
  37. Confirm 'Cal-OMS Admission' web service responds with confirmation data/ID on successful filing of 'FileCalOMSDischarge' method. Example:"<Confirmation>ClientID:305||EP:1||UniqueID:OMD.001</Confirmation>".
  38. Confirm 'Cal-OMS Admission' web service responds with confirmation message on successful filing of 'FileCalOMSDischarge' method. Example:"<Message>Cal-OMS Discharge web service has been filed successfully.</Message>".
  39. Confirm 'Cal-OMS Admission' web service responds with successful status value on successful filing of 'FileCalOMSDischarge' method. Example:"<Status>1</Status>".
  40. Open Crystal Reports or other SQL reporting tool.
  41. Create a Query against 'SYSTEM.cal_oms_discharge' table.
  42. Run the query for the client used in the above step.
  43. Verify 'GUID' field populate correctly with the unique value.
  44. Verify the 'pregnant_code' field defaults to 0.
  45. Verify the 'pregnant_value' field defaults to No.
  46. Verify the 'sec_drug_code' field defaults to 0.
  47. Verify the 'sec_drug_value' field defaults to None.
  48. Verify the 'sec_drug_route_code' field defaults to 99902.
  49. Verify the 'sec_drug_route_value' field defaults to None or Not Applicable.
  50. Verify the 'sec_drug_freq' field defaults to 99902.
  51. Close the SQL data viewer tool.

Topics
• Cal-Oms Admission • Web Services • Cal-OMS
Update 23 Summary | Details
837 Professional bill - Re-Bill Claims - Discharge Date Segment
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
  • Discharge
  • Electronic Billing
  • Electronic Re-Billing Service Assignment
Scenario 1: Validating re-bill claim claimed via 'Electronic Billing' in the 'SYSTEM.billing_rebill_tx_assign' SQL table.
Specific Setup:
  • Registry Setting:
  • The 'Specify Loops/Segments To Suppress/Include' is set 1.
  • Guarantor/Program Billing Defaults:
  • The 'Discharge Date (2300-DTP-096)' is selected in the 'Select Segments To Suppress' field.
  • Guarantors/Payors:
  • An existing guarantor is identified to be used. Note the guarantor's code/name.
  • Service codes:
  • An existing service code is identified to be used where the 'Does This Service Have a professional Component' is set to 'Yes'. 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:
  • An existing inpatient 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.
  • Client Charge Input:
  • A service is rendered to the client on the admission date. Note service date, service code.
  • Client Ledger:
  • A service distributed correctly to the assigned guarantor.
  • Diagnosis:
  • A diagnosis record is created for the client.
  • Close Charges:
  • The charges distributed to the guarantor are closed.
  • Create Interim Billing Batch File:
  • An interim billing batch is created for the client that includes an identified client and services. Note the batch number/name.
  • Discharge:
  • Client is discharged after 30 days from the admission date. Note the discharge date.
  • Electronic Billing:
  • The bill is created, and the services are claimed. Note the claim number.
  • Electronic Re-billing Service Assignment:
  • The claim is flagged for the re-bill.
Steps
  1. Open the 'Electronic Billing' form.
  2. Create an 837-Institutional/professional claim for the services assigned for the re-billing.
  3. Verify the bill compiles successfully.
  4. Close the form.
  5. Open the 'Crystal Reports' or any other SQL reporting tool.
  6. Query the SYSTEM.billing_rebill_tx_assign table.
  7. Verify the SYSTEM.billing_rebill_tx_assign table does not contain the flagged claim.
  8. Close the crystal report.
Scenario 2: Cal-PM - 837 Professional Bill - Validating 2300-DTP segment for the date of discharge - Re-bill services
Specific Setup:
  • Registry Setting:
  • The 'Specify Loops/Segments To Suppress/Include' is set 1.
  • Guarantor/Program Billing Defaults:
  • The 'Discharge Date (2300-DTP-096)' is selected in the 'Select Segments To Suppress' field.
  • Guarantors/Payors:
  • An existing guarantor is identified to be used. Note the guarantor's code/name.
  • Service codes:
  • An existing service code is identified to be used where the 'Does This Service Havs a professional Component' is set to 'Yes'. 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:
  • An existing inpatient 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.
  • Client Charge Input:
  • A service is rendered to the client on the admission date. Note service date, service code.
  • Client Ledger:
  • A service distributed correctly to the assigned guarantor.
  • Diagnosis:
  • A diagnosis record is created for the client.
  • Close Charges:
  • The charges distributed to the guarantor are closed.
  • Create Interim Billing Batch File:
  • An interim billing batch is created for the client that includes an identified client and services. Note the batch number/name.
  • Discharge:
  • Client is discharged after 30 days from the admission date. Note the discharge date.
Steps
  1. Open the 'Electronic Billing' form.
  2. Create an 837-Professional claim for the services.
  3. Verify the bill compiles successfully.
  4. Dump the 837 professional file.
  5. Verify the dump file does not contain DTP*096 segment to the bill to include the date of discharge. Note the claim number.
  6. Close the form.
  7. Open the 'Electronic Re-Billing Service Assignment' form.
  8. Mark the claim from the recent 837 compile to re-bill.
  9. Close the form.
  10. Open the 'Electronic Billing' form.
  11. Compile an 837-Professional bill for the services assigned for the re-billing.
  12. Verify the bill compiles successfully.
  13. Dump the 837 professional file.
  14. Verify the dump file does not contain DTP*096 segment to the bill to include the date of discharge.
  15. Close the form.
  16. Open the 'Guarantor/Program Billing Defaults' form.
  17. The 'Discharge Date (2300-DTP-096)' option is not selected in the 'Select Segments To Suppress' field.
  18. Submit the form.
  19. Open the 'Electronic Billing' form.
  20. Compile an 837-Professional bill for the services assigned for the re-billing.
  21. Verify the bill compiles successfully.
  22. Verify the dump file contains DTP*096 segment to the bill to include the date of discharge.
  23. Close the form.



Topics
• 837 Institutional • Re-Bill • Electronic Re-billing Service Assignment
Update 25 Summary | Details
Enable Co-Practitioner Services From Progress Notes - Edit Service Information
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
  • Delete Service
  • Program Maintenance
  • Site Specific Section Modeling (CWS)
  • Dictionary Update (PM)
  • Admission (Outpatient)
  • Financial Eligibility
  • Electronic Billing
Scenario 1: Enable Co-Practitioner Services From Progress Notes - Delete Service functionality
Specific Setup:
  • Registry Setting:
  • The 'Enable Co-Practitioner Services From Progress Notes' registry setting is set 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.
  • A primary add-on service code is created with the following:
  • Service Code Category = Primary 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? = No
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Another 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.
  • An interactive complexity add-on service code is created with the following:
  • Service Code Category =Interactive Complexity code
  • Service Code Type = desired value
  • Type of Fee = desired value.
  • Should Add-On Services Generate for Co-Practitioners for this Service Code? = NULL
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Service Fee/Cross Reference Maintenance:
  • A fee definition is created for all the service codes. Note the fee for each service code.
  • An active practitioner is identified. Note the practitioner ID.
  • Admission:
  • An active client is identified, or a new client is created. Note the client 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.
Steps
  1. Select desired client from the 'My Clients' widget.
  2. Open the 'Progress Notes (Group and Individual)' form.
  3. Validate the 'Select Client' field contains the client selected from the 'My Clients' widget.’.
  4. Select desired episode from the 'Select Episode' field.
  5. Select ‘New Service’ from the 'Progress Notes For' field.
  6. Select desired value from the 'Note Type' field.
  7. Enter desired value in the 'Notes Field' field.
  8. Enter desired date in the 'Date Of Service' field.
  9. Enter primary service code in the 'Service Charge Code' field.
  10. Validate the 'Service Program' field contains the program associated to the selected episode.
  11. Select desired practitioner from the 'Practitioner' field.
  12. Enter desired duration in the 'Service Duration' field.
  13. Select desired co-practitioner from the 'Co-Practitioner' field.
  14. Enter desired duration in the 'Co-Practitioner Duration (Minutes)'.
  15. Select desired codes from the 'Add-On Services'.
  16. Enter desired value in the 'Add-On Duration'.
  17. Click [Save Add-On Service].
  18. Verify the add-on service displays in the 'Selected Add-On Services' text area.
  19. Repeat steps from 15 through 18 if more than one add-on code needs to be added to the primary code.
  20. Select ‘Final’ from the 'Draft/Final' field.
  21. Click [File Note].
  22. Validate a message is displayed stating: 'Note Filed'.
  23. Click [OK].
  24. Close the form.
  25. Open the 'Client Ledger' for the client.
  26. Verify the client ledger contains primary and add-on services created for all the co-practitioner listed in the progress note if the field 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' is set to 'Yes' or Null for the add-on service code in the 'Service Code' form.
  27. Close the form.
  28. Open the ‘Delete Service’ form.
  29. Select the client in the 'Client Id' field.
  30. Enter 'Start Date' and 'End Date' such that it covers the services rendered to the selected client.
  31. Click [Display Client].
  32. Verify the message box displays only the service of the main practitioner within the date range previously specified.
  33. Select desired service to be deleted.
  34. Click [OK].
  35. Click [Delete].
  36. Verify 'The following services will be deleted' dialog displays the service selected to be deleted.
  37. Click [OK].
  38. Click [Yes].
  39. Verify the 'Information' message contains 'Deleted'.
  40. Close the form.
  41. Open the ‘Client Ledger’ for the client.
  42. Verify the previously selected service and all of its associated co-practitioner services are deleted.
  43. Close the form.
Scenario 2: Enable Co-Practitioner Services From Progress Notes – Edit service Information functionality
Specific Setup:
  • Registry Setting:
  • The 'Enable Co-Practitioner Services From Progress Notes' registry setting is set to 'Y'.
  • Program Maintenance:
  • Identify an existing program to be used for client's admission. Note the program code/value, and the 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.
  • A primary add-on service code is created with the following:
  • Service Code Category = Primary 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? = No
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Another 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.
  • An interactive complexity add-on service code is created with the following:
  • Service Code Category =Interactive Complexity code
  • Service Code Type = desired value
  • Type of Fee = desired value.
  • Should Add-On Services Generate for Co-Practitioners for this Service Code? = NULL
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Service Fee/Cross Reference Maintenance:
  • A fee definition is created for all the service codes. Note the fee for each service code.
  • An active practitioner is identified. Note the practitioner ID.
  • 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.
Steps
  1. Select desired client from the 'My Clients' widget.
  2. Open the 'Progress Notes (Group and Individual)' form.
  3. Validate the 'Select Client' field contains the client selected from the 'My Clients' widget.’.
  4. Select desired episode from the 'Select Episode' field.
  5. Select ‘New Service’ from the 'Progress Notes For' field.
  6. Select desired value from the 'Note Type' field.
  7. Enter desired value in the 'Notes Field' field.
  8. Enter desired date in the 'Date Of Service' field.
  9. Enter primary service code in the 'Service Charge Code' field.
  10. Validate the 'Service Program' field contains the program associated to the selected episode.
  11. Select desired practitioner from the 'Practitioner' field.
  12. Enter desired duration in the 'Service Duration' field.
  13. Select desired co-practitioner from the 'Co-Practitioner' field.
  14. Select desired duration in the 'Co-Practitioner Duration (Minutes)'.
  15. Select ‘Final’ from the 'Draft/Final' field.
  16. Click [File Note].
  17. Validate a message is displayed stating: 'Note Filed'.
  18. Click [OK].
  19. Close the form.
  20. Open the 'Client Ledger' for the client.
  21. Verify the client ledger contains primary and add-on services created for all the co-practitioner listed in the progress note if the field 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' is set to 'Yes' or Null for the add-on service code in the 'Service Code' form.
  22. Close the form.
  23. Open the ‘Edit service Information’ form.
  24. Select the same client from the above step 'Client ID' field.
  25. Click [Select Service(s) to Edit].
  26. Select a service for the practitioner to edit.
  27. Verify the Service Code, Program, Office, all Practitioner fields, and their duration are editable.
  28. Enter a new value in the Duration, Co-Practitioner Duration (Minutes) and Second Co Staff (Minutes).
  29. Click [Submit].
  30. Open the ‘Client Ledger’ form.
  31. Verify the practitioner and co-practitioner services reflect the duration change and new charges are calculated based on the new value specified for the duration.
  32. Close the form.
  33. Open the ‘Edit service Information’ form.
  34. Select the same client from the above step 'Client ID' field.
  35. Click [Select Service(s) to Edit].
  36. Select a service for the practitioner to edit.
  37. Verify the Service Code, Program, Office, all Practitioner fields, and their duration are editable.
  38. Select desired add-on service from the 'Add-On Service' codes to attach to the primary service code.
  39. Click [Submit].
  40. Open the ‘Client Ledger’ form.
  41. Verify that the primary and add-on services are created for the practitioner and co-practitioners.
  42. Close the form.
  43. Open the ‘Edit service Information’ form.
  44. Select the same client from the above step 'Client ID' field.
  45. Click [Select Service(s) to Edit].
  46. Select a service for the practitioner to edit.
  47. Remove one of the add-on service codes added to the primary service code of the practitioner service.
  48. Click [Submit].
  49. Open the ‘Client Ledger’ form.
  50. Verify that the desired add-on service code is deleted for the practitioner and co-practitioners.
  51. Close the form.
Scenario 3: Validating co-practitioner services - 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' = Y, N or Null and 'Create Co-Practitioner Services From Progress Notes' = Y
Specific Setup:
  • Registry Setting:
  • The 'Enable Co-Practitioner Services From Progress Notes' registry setting is set 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.
  • A primary add-on service code is created with the following:
  • Service Code Category = Primary 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? = No
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Another 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.
  • An interactive complexity add-on service code is created with the following:
  • Service Code Category =Interactive Complexity code
  • Service Code Type = desired value
  • Type of Fee = desired value.
  • Should Add-On Services Generate for Co-Practitioners for this Service Code? = NULL
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Service Fee/Cross Reference Maintenance:
  • A fee definition is created for all the service codes. Note the fee for each service code.
  • An active practitioner is identified. Note the practitioner's ID.
  • 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.
Steps
  1. Select desired client from the 'My Clients' widget.
  2. Open the 'Progress Notes (Group and Individual)' form.
  3. Validate the 'Select Client' field contains the client selected from the 'My Clients' widget.’.
  4. Select desired episode from the 'Select Episode' field.
  5. Select ‘New Service’ from the 'Progress Notes For' field.
  6. Select any value from the 'Note Type' field.
  7. Enter any value in the 'Notes Field' field.
  8. Enter the desired date in the 'Date Of Service' field.
  9. Enter primary service code in the 'Service Charge Code' field.
  10. Validate the 'Service Program' field contains the Service Program associated to selected episode.
  11. Select desired practitioner from the 'Practitioner' field.
  12. Enter desired duration in the 'Service Duration' field.
  13. Select desired co-practitioner from the 'Co-Practitioner' field.
  14. Enter desired duration in the 'Co-Practitioner Duration (Minutes)'.
  15. Select desired codes from the 'Add-On Services'.
  16. Select desired value in the 'Add-On Duration'.
  17. Click [Save Add-On Service].
  18. Verify the add-on service displayed in the 'Selected Add-On Services' text area.
  19. Repeat steps from 15 through 18 if more than one add-on code needs to be added to the primary code.
  20. Select ‘Final’ from the 'Draft/Final' field.
  21. Click [File Note].
  22. Validate a message is displayed stating: 'Note Filed'.
  23. Click [OK].
  24. Close the form.
  25. Open the 'Client Ledger' for the client.
  26. Verify the client ledger contains primary and add-on services created for all the co-practitioner listed in the progress note if the field 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' is set to 'Yes' or Null for the add-on service code in the 'Service Code' form.
  27. Close the form.
  28. Open the 'Close Charges' form.
  29. Close all the charges distributed to the guarantor.
  30. Close the form.
  31. Open the 'Create Interim Billing Batch File' form.
  32. Create an interim billing batch that covers the client, guarantor and services rendered to the client. Note the batch number.
  33. Close the form.
  34. Open the 'Electronic Billing' form.
  35. Compile an 837 bill for the client.
  36. Verify the bill compiles successfully.
  37. Select 'Dump File' option from the billing options.
  38. Select the recently compiled 837 file.
  39. Review the file.
  40. Verify the primary and add-on services are created for all the co-practitioner listed in the progress note if the field 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' is set to 'Yes' or Null for the add-on service code in the 'Service Code' form.
  41. Close the report.
  42. Close the form.

Topics
• Progress Notes • Delete Service • Edit Service Information • Service Codes
Update 28 Summary | Details
Client Demographic forms - 'Address Type' field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Discharge
  • Pre Admit
  • Client Alternate Addresses
  • SoapUI - ClientDemographics
  • SoapUI - UpdateAdmission
  • Admission (Outpatient)
  • Pre Admit Discharge
Scenario 1: 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. Select the desired value in the 'Address Type' field. Please note: this will display values defined in the '(10006) Location' dictionary.
  6. Click [Submit].
  7. Access the 'Admission' form for the client admitted in the previous steps.
  8. Click [Edit] for the episode added in the previous steps.
  9. Validate the previously filed data is displayed.
  10. Select the "Demographics" section.
  11. Validate that the 'Address Type' field contains the value selected in the previous steps.
  12. Close the form.
Scenario 2: '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. Select the desired value in the 'Address Type' field. Please note: this will display values defined in the '(10006) Location' dictionary.
  3. Populate any other desired fields.
  4. Click [Submit].
  5. Select "Client A" and access the 'Update Client Data' form.
  6. Validate the previously filed data is displayed.
  7. Validate that the 'Address Type' field contains the value selected in the previous steps.
  8. Close the form.
Scenario 3: '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. Select the desired value in the 'Address Type' field. Please note: this will display values defined in the '(10006) Location' dictionary.
  9. Select the desired value in the 'Do you have family members that are agricultural workers?' field.
  10. Select the desired value in the 'Are you an aged and disabled former migratory agricultural worker?' field.
  11. Click [Submit].
  12. Select "Client A" and access the 'Discharge' form.
  13. Select the discharged episode and click [Edit].
  14. Validate all previously filed data is displayed.
  15. Select the "Demographics" section.
  16. Validate the 'Address Type' field contains the value filed in the previous steps.
  17. Validate the 'Do you have family members that are agricultural workers?' field contains the value filed in the previous steps.
  18. Validate the 'Are you an aged and disabled former migratory agricultural worker?' field contains the value filed in the previous steps.
  19. Close the form.
  20. Access Crystal Reports or other SQL Reporting Tool.
  21. Create a report using the 'SYSTEM.patient_current_demographics' and 'SYSTEM.patient_demographic_history' SQL tables.
  22. Validate a row is displayed for "Client A".
  23. Validate the 'address_type_code' and 'address_type_value' fields contain the code/value filed in the previous steps.
  24. Validate the 'fam_agric_worker_code' and 'fam_agric_worker_value' fields contain the code/value filed in the previous steps.
  25. Validate the 'former_agric_worker_code' and 'former_agric_worker_value' fields contain the code/value filed in the previous steps.
  26. Close the reports.
Scenario 4: '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. Select the desired value in the 'Address Type' field. Please note: this will display values defined in the '(10006) Location' dictionary.
  5. Click [Submit].
  6. Select "Client A" and access the 'Pre Admit' form.
  7. Select an existing episode and click [Edit].
  8. Select the "Demographics" section.
  9. Validate the 'Address Type' field contains the value selected in the previous steps.
  10. Close the form.
Scenario 5: '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. Select the desired value in the 'Address Type' field. Please note: this will display values defined in the '(10006) Location' dictionary.
  5. Click [Submit].
  6. Select "Client A" and access the 'Call Intake' form.
  7. Select the existing call intake record and click [Edit].
  8. Validate the 'Address Type' field contains the value selected in the previous steps.
  9. Close the form.
Scenario 6: Client Alternate Addresses - Form Validations
Specific Setup:
  • The 'Enable Client Alternate Addresses' registry setting must be set to "Y".
  • A client is admitted in an existing episode (Client A).
Steps
  1. Access the 'Client Alternate Addresses' form.
  2. Select "Client A" in the 'Client' field.
  3. Select "Add" in the 'Add/Edit' field.
  4. Enter the desired value in the 'Description' field.
  5. Enter the desired date in the 'Address Start Date' field.
  6. Enter the desired date in the 'Address End Date' field.
  7. Enter the desired value in the 'Address Line 1' field.
  8. Enter the desired value in the 'Address Line 2' field.
  9. Enter the desired value in the 'Zip' field.
  10. Enter the desired value in the 'City' field.
  11. Select the desired value in the 'State' field.
  12. Enter the desired value in the 'Contact Name field.
  13. Enter the desired value in the 'Contact Phone' field.
  14. Enter the desired value in the 'Address Notes' field.
  15. Select the desired value in the 'Address Type' field. Please note: this will display values defined in the '(10006) Location' dictionary.
  16. Select "Yes" in the 'Enabled' field.
  17. Click [File].
  18. Validate a message is displayed stating: Saved.
  19. Click [OK].
  20. Validate the 'Client' field contains "Client A".
  21. Select "Edit" in the 'Add/Edit' field.
  22. Validate the 'Select Existing Address' field contains the alternate address filed in the previous steps with the 'Address Start Date', 'Address End Date', and 'Description'.
  23. Select the address filed in the previous steps in the 'Select Existing Address' field.
  24. Validate all previously filed data is displayed.
  25. Close the form.
  26. Access Crystal Reports or other SQL Reporting Tool.
  27. Select the PM namespace.
  28. Create a report using the 'SYSTEM.client_alternate_address' SQL table.
  29. Validate there is a row for "Client A" will all previously filed data.
  30. Validate the 'addr_type_code' and 'addr_type_value' fields contain the code/value filed in the previous steps.
  31. Close the report.
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. Click [Run].
  13. Validate the 'Message' field contains: Client Discharge web service has been filed successfully.
  14. Select "Client A" and access the 'Discharge' form.
  15. Validate all populated fields are displayed as entered in the web service.
  16. Select the "Demographics" section.
  17. Validate the 'Address Type' field contains the value entered via web service.
  18. 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. Enter the desired value in the 'AddressType' field.
  6. Populate any other desired fields.
  7. Enter "Client A" in the 'ClientID' field.
  8. Click [Run].
  9. Validate the 'Message' field contains: Client Demographics web service has been filed successfully.
  10. Select "Client A" and access the 'Update Client Data' form.
  11. Validate all populated fields are displayed.
  12. Validate the 'Address Type' field contains the value entered via web service.
  13. 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 the desired value in the 'AddressType' field.
  7. Enter "Client A" in the 'ClientID' field.
  8. Enter "Client A's" episode in the 'Episode' field.
  9. Click [Run].
  10. Validate the 'Confirmation' field contains a value such as: "Client Unique ID: # Unique ID: #".
  11. Validate the 'Message' field contains: "Client Admission web service has been filed successfully".
  12. Select "Client A" and access the 'Admission' form.
  13. Select the admission updated in the previous steps and click [Edit].
  14. Validate all populated fields are displayed.
  15. Validate the 'Address Type' field contains the value entered via web service.
  16. Close the form.
Scenario 10: '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. Select the desired value in the 'Address Type' field. Please note: this will display values defined in the '(10006) Location' dictionary.
  6. Click [Submit].
  7. Access the 'Admission (Outpatient)' form for the client admitted in the previous steps.
  8. Click [Edit] for the episode added in the previous steps.
  9. Validate the previously filed data is displayed.
  10. Select the "Demographics" section.
  11. Validate the 'Address Type' field contains the value selected in the previous steps.
  12. Close the form.
Scenario 11: '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. Select the desired value in the 'Address Type' field.
  9. Click [Submit].
  10. Select "Client A" and access the 'Pre Admit Discharge' form.
  11. Select the discharged episode and click [OK].
  12. Validate the previously filed data is displayed.
  13. Select the "Demographics" section.
  14. Validate the 'Address Type' field contains the value selected in the previous steps.
  15. Close the form.

Topics
• Admission • Update Client Data • Discharge • Pre Admit • Call Intake • Web Services • Admission (Outpatient) • Pre Admit Discharge
Update 30 Summary | Details
837 Billing - Primary / Add-On Services
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Update (PM)
  • Admission (Outpatient)
  • Financial Eligibility
  • Electronic Billing
  • Program Maintenance
Scenario 1: Cal-PM -Validating primary and associated add-on services in the same claim
Specific Setup:
  • Registry Setting:
  • Set the 'Include Delay Reason Code' registry setting to 'Y'.
  • Guarantors/Payors:
  • Guarantor 1: Note the ‘Financial Class’. This will be the client’s primary guarantor.
  • Guarantor/Program Billing Defaults:
  • The ‘Maximum Service Information Per Claim Information (Maximum LX Per CLM)’ = 1.
  • Program Maintenance:
  • Identify an existing program to be used for client's admission. Note the program code/value.
  • 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 service codes 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.
  • A primary add-on service code is created with the following:
  • Service Code Category = Primary Add-On Code
  • Service Code Type = desired value
  • Type of Fee = desired value.
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Another 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.
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • An interactive complexity add-on service code is created with the following:
  • Service Code Category =Interactive Complexity code
  • Service Code Type = desired value
  • Type of Fee = desired value.
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Service Fee/Cross Reference Maintenance:
  • A fee definition is created for all the service codes. Note the fee for each service code.
  • An active practitioner is identified. Note the practitioner's ID.
  • 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.
  • Recurring Client Charge Input:
  • Render 9 services to the client that are not add-on services. It could be any service. Once those services are filed, services have been provided for the above ‘Primary Code’ that include add-on codes.
  • Close Charges was used to close the charges.
  • Client Ledger has been used to verify that the liability distributed to the primary guarantor, and note the dates of service for closed, unclaimed services for the above service codes.
  • Create Interim Billing Batch File:
  • An interim billing batch is created to cover the services rendered to the client and distributed to the guarantor. Note the interim billing batch number.
Steps
  1. Open ‘Electronic Billing’.
  2. Select ‘837-Professional’ in ‘Billing Form’.
  3. Select the primary guarantor ‘Financial Class in ‘Type Of Bill’.
  4. Select ‘Individual’ in ‘Individual Or All Guarantors’.
  5. Select the primary guarantor in ‘Guarantor’.
  6. Select ‘Outpatient’ in ‘Billing Type’.
  7. Select ‘Sort File’ in ‘Billing Options’.
  8. Enter the desired value in ‘File Description/Name’.
  9. Select ‘Interim Billing Batch’ in ‘All Clients Or Interim Billing Batch’.
  10. Select desired interim billing batch file from the 'Interim Billing Batch' drop down field.
  11. Select desired value in ‘Program(s)’.
  12. Select ‘No’ in ‘Create Claims’.
  13. Enter the desired value in ‘First Date Of Service To Include’.
  14. Enter the desired value in ‘Last Date Of Service To Include’.
  15. Select ‘All in ‘Include Primary and/or Secondary Billing.
  16. Click [Process].
  17. Validate the ‘Processing Report’ message contains ‘Compile Complete’.
  18. Click [OK].
  19. Select ‘Dump File’ in ‘Billing Options’.
  20. Select ‘Print’ in ‘Print Or Delete Report’.
  21. Select the desired report in ‘File’.
  22. Click [Process].
  23. Validate that there is one ‘CLM’ segment per service for the services which are not primary or add-on services.
  24. Validate that the primary and associated add-on services are included under the same CLM segment.
  25. Close the report.
  26. Select ‘Yes’ in ‘Create Claims’.
  27. Enter desired date in the 'Date Of Claim'.
  28. Click [Process].
  29. Validate the ‘Processing Report’ message contains ‘Compile Complete’.
  30. Click [OK].
  31. Close the form.
  32. Open the 'Client ledger' form.
  33. Select desired client from the 'Client' field.
  34. Enter desired dates in the 'Service Start Date' and 'Service End date' fields.
  35. Select 'Simple' from the 'Ledger Type' field.
  36. Click [Process].
  37. Verify the client ledger contains the primary and associated add-on services on the same claim.
  38. Close the report.
  39. Close the form.
  40. Open the 'Registry Setting' form.
  41. Set the 'Include Delay Reason Code' registry setting to 'N'.
  42. Set the 'Select REF Segments To Include Registry Setting Value' to 2.
  43. Submit the form.
  44. Open the 'Guarantor/Program Billing Defaults'.
  45. Select 'Edit Template' option in the 'Actions' field.
  46. Select desired template from the 'Select Template' drop down list.
  47. Click the '837 Professional' or '837 Institutional' section.
  48. Set the 'Demonstration Project Identifier (2300-REF-02)' field to desired value.
  49. Submit the form.
  50. Repeat the steps from 1 through 39 for different dates of primary/add-on services and verify the primary and add-on are included in the same claim.

Topics
• 837 Professional • NX
Update 31 Summary | Details
Quick Billing - Workscreen
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
  • Practitioner Numbers By Guarantor and Program
  • Quick Billing Rule Definition
  • Admission (Outpatient)
  • Financial Eligibility
  • Quick Billing
Scenario 1: 'Quick Billing' - Verification of workscreen row deletion
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable New Quick Billing Format' must be enabled
  • One or more Quick Billing batch(es) must be present for edit via 'Quick Billing' form workscreen
Steps
  1. Open 'Quick Billing' form.
  2. In the 'Add New Or Edit Existing Quick Billing Batch' field, select 'Edit Existing'.
  3. In the 'File' drop-down selection field, select existing Quick Billing batch for edit.
  4. Click the 'Launch Workscreen' button.
  5. In 'Quick Billing' form work screen, select one or more rows for deletion, and click 'Delete Row' button.
  6. Ensure that 'Confirm Delete' dialog is presented; click 'Yes' button to confirm work screen row deletion.
  7. Repeat row selection and 'Delete Row' action for further rows as desired in the 'Quick Billing' form work screen.
  8. When edits/deletions are complete, click the 'Save' button to save work screen data for selected Quick Billing batch.
  9. Ensure that 'Exit Grid' dialog is presented, noting 'Save Successful'.
  10. In 'Quick Billing' form, select same batch for edit and click 'Launch Work screen' button.
  11. Ensure that the deleted rows from the Quick Billing batch are not present in work screen grid on re-entry of work screen for same batch.
  12. Ensure that the deleted rows from the Quick Billing batch are not re-added to same batch on re-run/submission of 'Quick Billing' form for existing batch.
  13. Ensure that in case where all rows are deleted from Quick Billing batch, the Quick Billing/Interim Billing batch is deleted from system on saving of work screen data/submission of 'Quick Billing' form.
Scenario 2: Quick Billing - Validating work screen and 837 report through 'Edit Existing' quick billing batch
Specific Setup:
  • Registry Setting:
  • The 'Enable New Quick Billing Format' registry setting is enabled.
  • Please note: This is a one-time, system-wide registry setting and the associated functionality cannot be disabled once the registry setting is enabled. Once this setting has been enabled, it will no longer be able to be viewed in the 'Registry Settings' form.
  • Admission:
  • Two outpatient clients are identified. Please note the admission programs of the clients.
  • Guarantors/Payor:
  • An existing guarantor is identified.
  • Financial Eligibility:
  • Guarantor identified above is assigned to the clients.
  • Client Charge Input:
  • 1-2 days of professional charges are rendered to the clients. Please note the service codes used during rendering services.
  • Client Ledger:
  • The charges are distributed to the guarantors assigned to the clients.
  • Quick Billing Rule Definition:
  • A new quick billing rule is created as follows:
  • The admission programs are selected in the 'Program' field.
  • '837 Professional' is selected in the 'Billing Form' field.
  • The guarantor assigned to the clients in their financial eligibility is selected in the 'Guarantors' field.
  • All required fields are populated.
  • The 'Create Interim Billing Batch' field is set to 'Yes'.
Steps
  1. Open the 'Quick Billing' form.
  2. Process a new quick billing batch using the rule created in the setup section.
  3. Use a date range spanning services entered.
  4. Select 'Create Batch', 'Close Charges', and 'Generate Bills' in the 'Quick Billing Tasks To Execute' field.
  5. Submit the form.
  6. Verify that compile completes and the prompt states 'Compile Complete'. A Quick Billing Batch and an Interim Billing Batch will be created.
  7. Select [Yes] and return to the form.
  8. Select the 'Add New' option.
  9. Enter the same parameters used in Steps 2 to 4 again, and click [Submit]
  10. Verify that 'Compile Complete' dialog contains the quick billing batch description followed by 'No Information Found'. A Quick Billing Batch and an Interim Billing Batch will be created, instead of the message "No Information Found" without the Quick Billing Rule description.
  11. Select [Yes] and return to the form.
  12. Select the 'Edit Existing' option.
  13. Select the quick bill that was created in the previous step.
  14. Click [Print 837 Report].
  15. Verify the report launched successfully.
  16. Close the report.
  17. Click [Launch Workscreen].
  18. Verify the work screen contains all the clients included in the batch.
  19. Deselect one client from the 'Client' filter at the top of the work screen.
  20. Verify the grid does not display the services of that client.
  21. Select the same client again from the 'Client' filter at the top of the work screen.
  22. Verify the grid includes the services for that client selected in the 'Client' filter.
  23. Select, Deselect and Re select clients, services codes, and practitioners in the 'Client', 'Service Code' and 'Practitioner' filters.
  24. Verify the grid includes/excludes items from the grid based on the selection made in the filters at the top of the work screen.
  25. Save the grid.
  26. Verify the grid saves successfully.
  27. Close the form.

Topics
• Quick Billing • NX
Update 32 Summary | Details
File Import - Service Guarantor Definitions
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Fee/Cross Reference and Guarantor Definition Export
  • File Import
Scenario 1: File Import: Service Guarantor Definitions - Registry Setting = Disable Full Table Backups Prior To File Import
Specific Setup:
  • Registry Settings: 'Disable Full Table Backups Prior To File Import' contains no value.
  • Click the 'Refresh Forms' icon.
  • Service Fee/Cross Reference Maintenance: The 'Restore Definitions' section contains the 'Restore Definitions That Existed Prior to Last Import' and Restore Maximum Liability Assignment Definitions That Existed Prior to Last Import' buttons.
  • Service Fee/Cross Reference and Guarantor Definition Export:
  • Select 'Guarantor Definition' in 'Record Type(s) to Export'.
  • Select 'Export Guarantor Definition to File and save the file locally.
  • Select 'Export to Crystal Report' and save the report locally.
  • File Import: Copy the exported file and edit it to change at least one 'Service Guarantor Definitions' - 'File A'.
  • Make a copy of 'File A' to edit and use when setting the above registry setting to 'F' - 'File B'.
  • Make a copy of 'File A' to edit and use when setting the above registry setting to 'G' - 'File C'.
  • Make a copy of 'File A' to edit and use when setting the above registry setting to 'null' - 'File D'.
Steps
  1. Open 'Registry Settings'.
  2. Set 'Limit Registry Settings to the Following Search Criteria' to 'Disable Full Table Backups'.
  3. Verify that 'Registry Setting' contains 'Avatar PM->System Maintenance->File Import->Service Fee/Guarantor Definitions->->Disable Full Table Backups Prior To File Import'
  4. Validate that the 'Registry Setting Value' is null.
  5. Close the form.
  6. Open 'Service Fee/Cross Reference Maintenance'.
  7. Click [Restore Definitions].
  8. Validate that the buttons are 'Restore Fee Definitions That Existed Prior To The Last File Import' and 'Restore Maximum Liability Assignment Definitions That Existed Prior To The Last File Import'.
  9. Click [Discard].
  10. Open 'File Import'.
  11. Select 'Service Guarantor Definitions' in 'File Type'.
  12. Upload, compile & post 'File A'
  13. Close the form.
  14. Open 'Service Fee/Cross Reference and Guarantor Definition Export'.
  15. Select 'Guarantor Definition' in 'Record Type(s) to Export'.
  16. Select either option to compare to the 'SETUP' version and validate that the data was changed as edited in the posted file, 'File A': 'Export to Crystal Report' or 'Export Guarantor Definition to File'.
  17. Close the form.
  18. Open 'Registry Settings'.
  19. Set 'Limit Registry Settings to the Following Search Criteria' to 'Disable Full Table Backups'.
  20. Verify that 'Registry Setting' contains 'Avatar PM->System Maintenance->File Import->Service Fee/Guarantor Definitions->->Disable Full Table Backups Prior To File Import'
  21. Set the 'Registry Setting Value' to 'F'.
  22. Click [Submit].
  23. Click [OK].
  24. Click [No].
  25. Click [Refresh Forms] icon.
  26. Open 'Service Fee/Cross Reference Maintenance'.
  27. Click [Restore Definitions].
  28. Validate that the only button is: 'Restore Maximum Liability Assignment Definitions That Existed Prior To The Last File Import'.
  29. Click [Discard].
  30. Open 'File Import'.
  31. Select 'Service Guarantor Definitions' in 'File Type'.
  32. Upload, compile & post 'File B'
  33. Close the form.
  34. Open 'Service Fee/Cross Reference and Guarantor Definition Export'.
  35. Select 'Guarantor Definition' in 'Record Type(s) to Export'.
  36. Select either option to compare the last version and validate that the data was changed as edited in the posted file, 'File B': 'Export to Crystal Report' or 'Export Guarantor Definition to File'.
  37. Close the form.
  38. Open 'Registry Settings'.
  39. Set 'Limit Registry Settings to the Following Search Criteria' to 'Disable Full Table Backups'.
  40. Verify that 'Registry Setting' contains 'Avatar PM->System Maintenance->File Import->Service Fee/Guarantor Definitions->->Disable Full Table Backups Prior To File Import'
  41. Set the 'Registry Setting Value' to 'G'.
  42. Click [Submit].
  43. Click [OK].
  44. Click [No].
  45. Click [Refresh Forms] icon.
  46. Open 'Service Fee/Cross Reference Maintenance'.
  47. Click [Restore Definitions].
  48. Validate that the only button is: 'Restore Fee Definitions That Existed Prior To The Last File Import'.
  49. Click [Discard].
  50. Open 'File Import'.
  51. Select 'Service Guarantor Definitions' in 'File Type'.
  52. Upload, compile & post 'File C'.
  53. Close the form.
  54. Open 'Service Fee/Cross Reference and Guarantor Definition Export'.
  55. Select 'Guarantor Definition' in 'Record Type(s) to Export'.
  56. Select either option to compare the last version and validate that the data was changed as edited in the posted file, 'File C': 'Export to Crystal Report' or 'Export Guarantor Definition to File'.
  57. Close the form.
  58. Open 'Registry Settings'.
  59. Set 'Limit Registry Settings to the Following Search Criteria' to 'Disable Full Table Backups'.
  60. Verify that 'Registry Setting' contains 'Avatar PM->System Maintenance->File Import->Service Fee/Guarantor Definitions->->Disable Full Table Backups Prior To File Import'
  61. Set the 'Registry Setting Value' to be blank.
  62. Click [Submit].
  63. Click [OK].
  64. Click [No].
  65. Click [Refresh Forms] icon.
  66. Open 'Service Fee/Cross Reference Maintenance'.
  67. Click [Restore Definitions].
  68. Validate that the buttons are 'Restore Fee Definitions That Existed Prior To The Last File Import' and 'Restore Maximum Liability Assignment Definitions That Existed Prior To The Last File Import'.
  69. Click [Discard].
  70. Open 'File Import'.
  71. Select 'Service Guarantor Definitions' in 'File Type'.
  72. Upload, compile & post 'File D'.
  73. Close the form.
  74. Open 'Service Fee/Cross Reference and Guarantor Definition Export'.
  75. Select 'Guarantor Definition' in 'Record Type(s) to Export'.
  76. Select either option to compare the last version and validate that the data was changed as edited in the posted file, 'File D': 'Export to Crystal Report' or 'Export Guarantor Definition to File'.
  77. Close the form.
  78. Open 'Service Fee/Cross Reference Maintenance'.
  79. Click [Restore Definitions].
  80. Click [Restore Maximum Liability Assignment Definitions That Existed Prior To The Last File Import].
  81. Click [Yes].
  82. Click [OK].
  83. Click [Restore Fee Definitions That Existed Prior To The Last File Import].
  84. Click [Yes].
  85. Click [OK].
  86. Click [Service Fee/Cross Reference Maintenance].
  87. Click [Guarantor Definitions].
  88. Validate that the report contains the definitions from 'File C'.
  89. Close the report.
  90. Close the form.

Topics
• Service Fee/Cross Reference Maintenance • File Import • NX
Update 33 Summary | Details
Avatar Cal-PM Registry Settings
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • File Import
Scenario 1: Avatar Cal-PM Registry Settings - Verification of 'Enable Override MSO COB Service Charges and Line Adjustments' Registry Setting
Steps
  1. Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' may only be accessed/enabled by Netsmart; please contact Netsmart representative/associate for more information.

"When this registry setting is set to "Y", when a batch is closed in Avatar MSO, each service in the batch that contains Other Healthcare Coverage and is pushed to Avatar Cal-PM will use the parent system service fee table to determine the Fee.


This also gives an end user the ability to override service charge and line adjustments within an 837I and 837P submission for MSO originating services that contain COB. This is accomplished by adding the field 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' to the 'Guarantor/Program Billing Defaults' form.


Entering "N" removes the Avatar MSO logic and the field from the form and disables Enable Override MSO Coordination of Benefits Service Charges and Line Adjustments logic in 837I and 837P submissions.


Upon product installation, the default setting will be "N"."

Scenario 2: File Import - Verification of 'Guarantor/Program Billing Defaults' File Type Import, 'Enable Override MSO COB Service Charges and Line Adjustments' Registry Setting (Avatar Cal-PM)
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' must be enabled
  • Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' may only be accessed/enabled by Netsmart; please contact Netsmart representative/associate for more information
  • Avatar Cal-PM 'Guarantor/Program Billing Defaults Template' File Import file containing one or valid import rows for 837 Professional and/or 837 Institutional Defaults including 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field value ('Y' or 'N' value)
  • Segment 141 for '837 Professional' defaults
  • Segment 131 for '837 Institutional' defaults
  • Updated import file layout document 'Avatar_Cal-PM_File_Import_Record_Layouts.xls' included with update package
  • Crystal Reports or other SQL reporting tool
Steps
  1. Open Avatar Cal-PM 'File Import' form.
  2. Select File Type 'Guarantor/Program Billing Defaults'.
  3. Select 'Upload New File' in 'Action' field and Click 'Process Action' button.
  4. Select Avatar Cal-PM 'Guarantor/Program Billing Defaults' import file including one or more 837 Professional and/or 837 Institutional Defaults import rows and click 'Open' button.
  5. Select 'Compile/Validate File' in 'Action' field.
  6. Select loaded 'Guarantor/Program Billing Defaults' import file and click 'Process Action' button.
  7. Ensure that 'Compile/Validate File' action completes, and message 'Compiled' or '(File Name) contains one or more errors. These errors can be reviewed using 'Print Errors' action' is displayed.
  8. Click 'OK' button.
  9. Select 'Print File' in 'Action' field to view successfully compiled import data; Select compiled import file and click 'Process Action' button.
  10. In 'Guarantor/Program Billing Defaults' File Import Report, ensure that all valid import row(s) are included in report with segment/value details, including 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' fields.
  11. Select 'Post File' in 'Action' field to post successfully compiled import data; Select compiled import file and click 'Process Action' button.
  12. Ensure that 'Compile/Validate File' action completes, and message 'Posted' and/or 'The selected file contains one or more lines with compilation errors. Only those lines without compilation errors will be posted' is displayed.
  13. Open Avatar Cal-PM 'Guarantor/Program Billing Defaults' form.
  14. Select 'Edit Template' in 'Action' field and select imported Guarantor/Program Billing Defaults template for review/edit.
  15. Navigate to '837 Professional' section of form.
  16. Ensure that imported value for 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field is present for selected template.
  17. Navigate to '837 Institutional' section of form.
  18. Ensure that imported value for 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field is present for selected template.
  19. Open Crystal Reports or other SQL reporting tool.
  20. In Avatar Cal-PM SQL table 'SYSTEM.file_import_gpbdt_p837', ensure that value filed via import for 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field is present in 'ovd_mso_cob_chg_adj_code' / 'ovd_mso_cob_chg_adj_value' SQL table fields.
  21. In Avatar Cal-PM SQL table 'SYSTEM.file_import_gpbdt_i837', ensure that value filed via import for 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field is present in 'ovd_mso_cob_chg_adj_code' / 'ovd_mso_cob_chg_adj_value' SQL table fields.
Scenario 3: 'Guarantor/Program Billing Defaults' - Verification of 'Enable Override MSO COB Service Charges and Line Adjustments' Registry Setting (Avatar Cal-PM)
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' must be enabled
  • Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' may only be accessed/enabled by Netsmart; please contact Netsmart representative/associate for more information
  • Crystal Reports or other SQL reporting tool
Steps
  1. Open Avatar Cal-PM 'Guarantor/Program Billing Defaults' form.
  2. Select 'Add Template' in 'Action field (or 'Edit Template' and select existing Guarantor/Program Billing Defaults template for review/edit).
  3. Navigate to '837 Professional' section of form.
  4. Ensure 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field is present in '837 Professional' section of form; ensure User Help information (lightbulb icon) is included for field, containing the following information:
  5. "When "Yes" is selected, the Cal-PM Service Fee associated with the service will post as the Service Line Item Charge Amount. To balance the claim, the system will identify the difference and insert either an OA*23 or OA*94 claim line adjustment segment."
  6. Select value for 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field (and any other fields/sections as desired).
  7. Navigate to '837 Institutional' section of form.
  8. Ensure 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field is present in '837 Institutional' section of form; ensure User Help information (lightbulb icon) is included for field, containing the following information:
  9. "When "Yes" is selected, the Cal-PM Service Fee associated with the service will post as the Service Line Item Charge Amount. To balance the claim, the system will identify the difference and insert either an OA*23 or OA*94 claim line adjustment segment."
  10. Select value for 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field (and any other fields/sections as desired).
  11. Click 'Submit' button to file Guarantor/Program Billing Defaults template.
  12. Select 'Edit Template' in 'Action field and select previously filed Guarantor/Program Billing Defaults template for review/edit.
  13. Navigate to '837 Professional' section of form.
  14. Ensure that previously selected/filed value for 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field is present in '837 Professional' section for selected template.
  15. Navigate to '837 Institutional' section of form.
  16. Ensure that previously selected/filed value for 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field is present in '837 Institutional' section for selected template.
  17. Open Crystal Reports or other SQL reporting tool.
  18. In Avatar Cal-PM SQL table 'SYSTEM.table_837_p_facility_prov_num', ensure that value filed for 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field is present in 'ovd_mso_cob_chg_adj_code' / 'ovd_mso_cob_chg_adj_value' SQL table fields.
  19. In Avatar Cal-PM SQL table 'SYSTEM.table_837_i_facility_prov_num', ensure that value filed for 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field is present in 'ovd_mso_cob_chg_adj_code' / 'ovd_mso_cob_chg_adj_value' SQL table fields.
Scenario 4: 'Close Batch' - Avatar MSO to Cal-PM Parent System Service Filing, Verification of 'Enable Override MSO COB Service Charges and Line Adjustments' Registry Setting
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' must be enabled
  • Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' may only be accessed/enabled by Netsmart; please contact Netsmart representative/associate for more information
  • Avatar Cal-PM Registry Setting 'Support MSO Other Healthcare Coverage' must be enabled
  • Avatar MSO Registry Setting 'Add Support For The Input Of Third Party Payer Amounts' must be enabled
  • Avatar MSO Registry Setting 'Enable Fee Override in PM' must be set to use Parent System Service Fee Table (set to '0' or '4')
  • If Avatar MSO Registry Setting 'Enable Fee Override in PM' is set to '4', 'Fee Override in PM' date/override type entry for service date(s) must be defined to use 'Parent System Service Fee Table' (via Avatar MSO 'MSO to Parent System Integration Mapping' form 'Service Filing' section, 'Enable Fee Override in PM' sub-section)
  • 'File Services On Closing Of Batch Or Creation of EOB?' must be set to 'Yes' (via Avatar MSO 'MSO to Parent System Integration Mapping' form 'Service Filing' section)
  • One or more 'Approved' status Avatar MSO services eligible for filing to parent Avatar Cal-PM system and including Third Party Payment/Adjustment 'Other Healthcare Coverage' information
  • Crystal Reports or other SQL reporting tool
Steps
  1. Open Avatar MSO 'Close Batch' form.
  2. Note - Acceptance Testing may also be confirmed on service filing to parent Avatar Cal-PM system via Avatar MSO 'Create EOB' or 'Other EOB Information' entry/filing where 'Inhibit Service Filing' restrictions are defined via 'MSO to Parent System Integration Mapping' form 'Service Filing' section
  3. Select Avatar MSO Claims Processing batch containing one or more 'Approved' status services eligible for filing to parent Avatar Cal-PM system.
  4. Set 'Close Batch' field to 'Yes' (and click 'OK' button to close warning message dialog).
  5. Click 'Submit' button to close batch/file services to parent Avatar Cal-PM system.
  6. Open 'Client Ledger' form in parent Avatar Cal-PM system.
  7. Select 'Client ID' value for client where services are present in Avatar MSO closed status Claims Processing batch.
  8. Select 'Claim/Episode/All Episodes' value.
  9. Select 'Ledger Type' value.
  10. Click 'Process' button.
  11. In Client Ledger data, ensure that 'Approved' status services originating in Avatar MSO are present in Avatar Cal-PM system following 'Close Batch' filing (where services are valid for filing to parent system).
  12. For services originating via Avatar MSO and filed to Avatar Cal-PM parent system (where Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' is enabled):
  13. Services including Third Party Payment/Adjustment 'Other Healthcare Coverage' information - Ensure that Avatar Cal-PM Client Ledger 'Charge' value for service(s) reflects the applicable Cal-PM Service Fee Table Amount for service(s)
  14. Note - Avatar Cal-PM 'Cost of Service'/'Guarantor Liability' value for service(s) originating in Avatar MSO with Other Healthcare Coverage information will reflect full Cal-PM Service Fee Table Amount, not including 'Other Healthcare Coverage' Third Party Payment amounts for service filed to Avatar Cal-PM
  15. Note - Third Party Payment/Adjustment 'Other Healthcare Coverage' information from Avatar MSO will be stored with Cal-PM parent service to ensure correctly balanced Avatar Cal-PM outbound 837 claim information where Other Healthcare Coverage information is included in original claim/service (via SQL tables noted below)
  16. Services not including Third Party Payment/Adjustment 'Other Healthcare Coverage' information - Ensure that Avatar Cal-PM 'Charge'/'Cost Of Service' (as well as 'Guarantor Liability') value for service(s) in Avatar Cal-PM reflects the applicable Cal-PM Service Fee Table Amount
  17. Open Crystal Reports or other SQL reporting tool.
  18. In Avatar Cal-PM SQL table 'SYSTEM.mso_service_cob', ensure that claim/service Third Party Payer 'Other Healthcare Coverage' filed with service via Avatar MSO is present.
  19. Note - Avatar Cal-PM instance of SQL table 'SYSTEM.mso_service_cob' will on be populated with data where Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' is enabled
  20. In Avatar Cal-PM SQL table 'SYSTEM.mso_claim_adjustments', ensure that claim/service Third Party Adjustment 'Other Healthcare Coverage' filed with service via Avatar MSO is present.
  21. Note - Avatar Cal-PM instance of SQL table 'SYSTEM.mso_claim_adjustments' will on be populated with data where Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' is enabled
Scenario 5: 'Client Ledger' - Verification of 'Enable Override MSO COB Service Charges and Line Adjustments' Registry Setting (Cal-PM)
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' must be enabled
  • Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' may only be accessed/enabled by Netsmart; please contact Netsmart representative/associate for more information
  • Avatar Cal-PM Registry Setting 'Support MSO Other Healthcare Coverage' must be enabled
  • Avatar MSO Registry Setting 'Add Support For The Input Of Third Party Payer Amounts' must be enabled
  • Avatar MSO Registry Setting 'Enable Fee Override in PM' must be set to use Parent System Service Fee Table (set to '0' or '4')
  • If Avatar MSO Registry Setting 'Enable Fee Override in PM' is set to '4', 'Fee Override in PM' date/override type entry for service date(s) must be defined to use 'Parent System Service Fee Table' (via Avatar MSO 'MSO to Parent System Integration Mapping' form 'Service Filing' section, 'Enable Fee Override in PM' sub-section)
  • 'File Services On Closing Of Batch Or Creation of EOB?' must be set to 'Yes' (via Avatar MSO 'MSO to Parent System Integration Mapping' form 'Service Filing' section)
  • One or more services originating in Avatar MSO and including Third Party Payment/Adjustment 'Other Healthcare Coverage' information
Steps
  1. Open Avatar Cal-PM 'Client Ledger' form.
  2. Select 'Client ID' value for client where services originating in Avatar MSO and including Other Healthcare Coverage information exist.
  3. Select 'Claim/Episode/All Episodes' value (and enter/edit 'From Date'/'To Date' values if desired).
  4. Select 'Ledger Type' value.
  5. Click 'Process' button.
  6. Where 'Simple' is selected for 'Ledger Type' - In 'Client Ledger' form display data, ensure that services originating in Avatar MSO and including Other Healthcare Coverage information reflect full Cal-PM Service Fee Table Amount, not including 'Other Healthcare Coverage' Third Party Payment amounts for service filed to Avatar Cal-PM.
  7. Where 'Crystal' is selected for 'Ledger Type' - ensure that new/specific version of Client Ledger report is launched. ('Avatar_Cal_PM_Client_Ledger_Screen_Imbed_OHC_Chg_Adj', used only where Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' is enabled)
  8. In Client Ledger Crystal Report data, ensure that for services originating in Avatar MSO and including Other Healthcare Coverage information, the 'Full Charge' value for service(s) full Cal-PM Service Fee Table Amount, not including 'Other Healthcare Coverage' Third Party Payment amounts for service filed to Avatar Cal-PM.
  9. In Client Ledger Crystal Report data, click on 'Date of Service' to expand service information sub-report.
  10. In Client Ledger Crystal Report data, ensure that for services originating in Avatar MSO and including Other Healthcare Coverage information, including the following fields (information from Avatar Cal-PM SQL tables 'SYSTEM.mso_service_cob' / 'SYSTEM.mso_claim_adjustments'):
  11. 'Third Party Payer Name'
  12. 'Third Party Payer Claim Amount'
  13. 'Third Party Payer Paid Amount'
  14. 'Third Party Payer Adjustment'
  15. 'Third Party Remittance Date'
Avatar Cal-PM 'Electronic Billing' for Avatar MSO Services
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Electronic Billing
Scenario 1: 'Electronic Billing' - 837 Professional, Verification of 'Enable Override MSO COB Service Charges and Line Adjustments' Registry Setting (Cal-PM)
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' must be enabled
  • Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' may only be accessed/enabled by Netsmart; please contact Netsmart representative/associate for more information
  • Avatar Cal-PM Registry Setting 'Support MSO Other Healthcare Coverage' must be enabled
  • Avatar Cal-PM Registry Setting 'Add Support For Client Other Healthcare Coverage' may optionally be enabled (for 837 reporting of manually entered Avatar MSO services with Service-Level Third Party Payment/Adjustment 'Other Healthcare Coverage' information)
  • Avatar MSO Registry Setting 'Add Support For The Input Of Third Party Payer Amounts' must be enabled
  • Avatar MSO Registry Setting 'Enable Fee Override in PM' must be set to use Parent System Service Fee Table (set to '0' or '4')
  • If Avatar MSO Registry Setting 'Enable Fee Override in PM' is set to '4', 'Fee Override in PM' date/override type entry for service date(s) must be defined to use 'Parent System Service Fee Table' (via Avatar MSO 'MSO to Parent System Integration Mapping' form 'Service Filing' section, 'Enable Fee Override in PM' sub-section)
  • 'Include Service Level Adjudication Information (2430)' field must be set to 'Yes' in Avatar Cal-PM 'Guarantor/Program Billing Defaults' form ('837 Professional' section) for applicable Guarantor/Program
  • 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field must be set to 'Yes' in Avatar Cal-PM 'Guarantor/Program Billing Defaults' form ('837 Professional' section) for applicable Guarantor/Program
  • One or more service(s) eligible for Avatar Cal-PM 837 Professional file inclusion (via 'Electronic Billing' form) originating in Avatar MSO and including Third Party Payment/Adjustment 'Other Healthcare Coverage' information
Steps
  1. Open Avatar Cal-PM 'Electronic Billing' form.
  2. Note, acceptance testing may also be confirmed via Avatar Cal-PM 'Quick Billing' form/functionality
  3. Select 837 Professional in 'Billing Form' field.
  4. Enter/select 837 file sorting criteria, using values which will include service(s) originating in Avatar MSO.
  5. Click 'Process' button to sort/generate 837 Professional file.
  6. Select 'Dump File' in the 'Billing Options' field (or select 'Create File On Server' to review output file directly).
  7. Select 'Print' in the 'Print Or Delete Report' field.
  8. Select 837 Professional file sorted which includes services originating in Avatar MSO, and click 'Process' button to display 837 outbound file data.
  9. In Avatar Cal-PM 837 Professional format outbound electronic billing file data - for services originating via Avatar MSO and including Third Party Payment/Adjustment 'Other Healthcare Coverage' information:
  10. Ensure that 2300-CLM Total Claim Charge Amount reflects the sum of Cal-PM Service Fee Table Amounts for all service(s) included in claim
  11. Ensure that the following claim information payer loops reflect Third Party Payor 'Other Healthcare Coverage' information from originating Avatar MSO inbound claim (or Avatar Cal-PM 'Client Other Healthcare Coverage' form information for manually entered Avatar MSO services):
  12. Other Subscriber Information (2320)
  13. Other Insurance Coverage Information (2320)
  14. Other Subscriber Name (2330A)
  15. Other Payer Name (2330B)
  16. Ensure that 2400-SV1 Line Item Charge Amount reflects the Cal-PM Service Fee Table Amount for service(s) included in claim
  17. Ensure that 2430-SVD Line Adjudication Information/Service Line Paid Amount reflects Third Party Payment 'Other Healthcare Coverage' information from originating Avatar MSO inbound claim or manual entry
  18. Ensure that 2430-CAS Line Adjustment entries reflect Third Party Adjustment 'Other Healthcare Coverage' information from originating Avatar MSO inbound claim or manual entry (Claim Adjustment Group Code/Claim Adjustment Reason Code/Adjustment Amount)
  19. In case where there is a difference between 2400-SV1 Line Item Charge Amount for claim and sum of 2430-SVD Paid Amount/2430-CAS Line Adjustment Amounts, ensure that an additional 2430-CAS Line Adjustment entry is inserted by Avatar Cal-PM system to ensure claim total balancing and allow 837 inclusion
  20. In case where this difference is positive, ensure that system-generated 2430-CAS Line Adjustment entry includes Claim Adjustment Group Code 'OA' and Claim Adjustment Reason Code '23' (with claim charge amount difference as Adjustment Amount; Example: 'CAS*OA*23*10~')
  21. In case where this difference is negative, ensure that system-generated 2430-CAS Line Adjustment entry includes Claim Adjustment Group Code 'OA' and Claim Adjustment Reason Code '94' (with claim charge amount difference as Adjustment Amount; Example: 'CAS*OA*94*-10~')
Scenario 2: 'Electronic Billing' - 837 Institutional, Verification of 'Enable Override MSO COB Service Charges and Line Adjustments' Registry Setting (Cal-PM)
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' must be enabled
  • Avatar Cal-PM Registry Setting 'Enable Override MSO COB Service Charges and Line Adjustments' may only be accessed/enabled by Netsmart; please contact Netsmart representative/associate for more information
  • Avatar Cal-PM Registry Setting 'Support MSO Other Healthcare Coverage' must be enabled
  • Avatar Cal-PM Registry Setting 'Add Support For Client Other Healthcare Coverage' may optionally be enabled (for 837 reporting of manually entered Avatar MSO services with Service-Level Third Party Payment/Adjustment 'Other Healthcare Coverage' information)
  • Avatar MSO Registry Setting 'Add Support For The Input Of Third Party Payer Amounts' must be enabled
  • Avatar MSO Registry Setting 'Enable Fee Override in PM' must be set to use Parent System Service Fee Table (set to '0' or '4')
  • If Avatar MSO Registry Setting 'Enable Fee Override in PM' is set to '4', 'Fee Override in PM' date/override type entry for service date(s) must be defined to use 'Parent System Service Fee Table' (via Avatar MSO 'MSO to Parent System Integration Mapping' form 'Service Filing' section, 'Enable Fee Override in PM' sub-section)
  • 'Include Service Level Adjudication Information (2430)' field must be set to 'Yes' in Avatar Cal-PM 'Guarantor/Program Billing Defaults' form ('837 Institutional' section) for applicable Guarantor/Program
  • 'Override MSO Coordination of Benefits Service Charges and Line Adjustments' field must be set to 'Yes' in Avatar Cal-PM 'Guarantor/Program Billing Defaults' form ('837 Institutional' section) for applicable Guarantor/Program
  • One or more service(s) eligible for Avatar Cal-PM 837 Institutional file inclusion (via 'Electronic Billing' form) originating in Avatar MSO and including Third Party Payment/Adjustment 'Other Healthcare Coverage' information
Steps
  1. Open Avatar Cal-PM 'Electronic Billing' form.
  2. Note, acceptance testing may also be confirmed via Avatar Cal-PM 'Quick Billing' form/functionality
  3. Select 837 Institutional in 'Billing Form' field.
  4. Enter/select 837 file sorting criteria, using values which will include service(s) originating in Avatar MSO.
  5. Click 'Process' button to sort/generate 837 Institutional file.
  6. Select 'Dump File' in the 'Billing Options' field (or select 'Create File On Server' to review output file directly).
  7. Select 'Print' in the 'Print Or Delete Report' field.
  8. Select 837 Institutional file sorted which includes services originating in Avatar MSO, and click 'Process' button to display 837 outbound file data.
  9. In Avatar Cal-PM 837 Institutional format outbound electronic billing file data - for services originating via Avatar MSO and including Third Party Payment/Adjustment 'Other Healthcare Coverage' information:
  10. Ensure that 2300-CLM Total Claim Charge Amount reflects the sum of Cal-PM Service Fee Table Amounts for all service(s) included in claim
  11. Ensure that the following claim information payer loops reflect Third Party Payor 'Other Healthcare Coverage' information from originating Avatar MSO inbound claim (or Avatar Cal-PM 'Client Other Healthcare Coverage' form information for manually entered Avatar MSO services):
  12. Other Subscriber Information (2320)
  13. Other Insurance Coverage Information (2320)
  14. Other Subscriber Name (2330A)
  15. Other Payer Name (2330B)
  16. Ensure that 2400-SV2 Line Item Charge Amount reflects the Cal-PM Service Fee Table Amount for service(s) included in claim
  17. Ensure that 2430-SVD Line Adjudication Information/Service Line Paid Amount reflects Third Party Payment 'Other Healthcare Coverage' information from originating Avatar MSO inbound claim or manual entry
  18. Ensure that 2430-CAS Line Adjustment entries reflect Third Party Adjustment 'Other Healthcare Coverage' information from originating Avatar MSO inbound claim or manual entry (Claim Adjustment Group Code/Claim Adjustment Reason Code/Adjustment Amount)
  19. In case where there is a difference between 2400-SV2 Line Item Charge Amount for claim and sum of 2430-SVD Paid Amount/2430-CAS Line Adjustment Amounts, ensure that an additional 2430-CAS Line Adjustment entry is inserted by Avatar Cal-PM system to ensure claim total balancing and allow 837 inclusion
  20. In case where this difference is positive, ensure that system-generated 2430-CAS Line Adjustment entry includes Claim Adjustment Group Code 'OA' and Claim Adjustment Reason Code '23' (with claim charge amount difference as Adjustment Amount; Example: 'CAS*OA*23*10~')
  21. In case where this difference is negative, ensure that system-generated 2430-CAS Line Adjustment entry includes Claim Adjustment Group Code 'OA' and Claim Adjustment Reason Code '94' (with claim charge amount difference as Adjustment Amount; Example: 'CAS*OA*94*-10~')

Topics
• Registry Settings • Guarantor/Program Billing Defaults • File Import • Electronic Billing • Client Ledger • Claims Processing • 837 Professional • 837 Institutional
Update 37 Summary | Details
California Required EDI - CSI
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CSI Submission
Scenario 1: CSI Assessment (Call Intake) - 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.
  • Client: 'Client A' is admitted to a program that contains 'Call-Intake' in 'Program Type' and 'Yes' in 'Mental Health Program (CSI) '.
Steps
  1. Open the 'CSI Assessment (Call Intake)' form for 'Client A'.
  2. Verify that the 'Referral Source' field is required or not required, based on the value in the 'Require Referral Source' registry setting.
  3. Enter data in all required fields and desired optional fields.
  4. Click [Submit].
  5. If desired, change the value of the 'Require Referral Source' registry setting to get a different result.
  6. Open the 'CSI Assessment (Call Intake)' form for 'Client A'.
  7. Verify that the 'Referral Source' field is required or not required, based on the value in the 'Require Referral Source' registry setting.
  8. Close the form.
  9. If desired, submit the data in the 'CSI Submission' form.
  10. Select 'Compile' in 'Options'.
  11. Enter the desired date range.
  12. Click [Submit].
  13. Click [OK].
  14. Select 'Print' in 'Options'.
  15. Select desired file in 'Select File To Print/Submit'.
  16. Click [Print Selected File Information].
  17. Validate the data for 'Client A', including the 'Referral Source'.
  18. If desired, submit the file.
Scenario 2: 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.
  • Client: 'Client A' is admitted to a program that contains 'Admit' in 'Program Type' and 'Yes' in 'Mental Health Program (CSI)'.
Steps
  1. Open the 'CSI Assessment form for 'Client A'.
  2. Verify that the 'Referral Source' field is required or not required, based on the value in the 'Require Referral Source' registry setting.
  3. Enter data in all required fields and desired optional fields.
  4. Click [Submit].
  5. If desired, change the value of the 'Require Referral Source' registry setting to get a different result.
  6. Open the 'CSI Assessment' form for 'Client A'.
  7. Verify that the 'Referral Source' field is required or not required, based on the value in the 'Require Referral Source' registry setting.
  8. Close the form.
  9. If desired, submit the data in the 'CSI Submission' form.
  10. Select 'Compile' in 'Options'.
  11. Enter the desired date range.
  12. Click [Submit].
  13. Click [OK].
  14. Select 'Print' in 'Options'.
  15. Select desired file in 'Select File To Print/Submit'.
  16. Click [Print Selected File Information].
  17. Validate the data for 'Client A', including the 'Referral Source'.
  18. If desired, submit the file.
California Required EDI - CSI
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.
  • Client: 'Client A' is admitted to a program that contains 'Admit' in 'Program Type' and 'Yes' in 'Mental Health Program (CSI)'.
Steps
  1. Open the 'CSI Assessment form for 'Client A'.
  2. Verify that the 'Referral Source' field is required or not required, based on the value in the 'Require Referral Source' registry setting.
  3. Enter data in all required fields and desired optional fields.
  4. Click [Submit].
  5. If desired, change the value of the 'Require Referral Source' registry setting to get a different result.
  6. Open the 'CSI Assessment' form for 'Client A'.
  7. Verify that the 'Referral Source' field is required or not required, based on the value in the 'Require Referral Source' registry setting.
  8. Close the form.
  9. If desired, submit the data in the 'CSI Submission' form.
  10. Select 'Compile' in 'Options'.
  11. Enter the desired date range.
  12. Click [Submit].
  13. Click [OK].
  14. Select 'Print' in 'Options'.
  15. Select desired file in 'Select File To Print/Submit'.
  16. Click [Print Selected File Information].
  17. Validate the data for 'Client A', including the 'Referral Source'.
  18. If desired, submit the file.
California Required EDI -CSI
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.
  • Client: 'Client A' is admitted to a program that contains 'Admit' in 'Program Type' and 'Yes' in 'Mental Health Program (CSI)'.
Steps
  1. Open the 'CSI Assessment form for 'Client A'.
  2. Verify that the 'Referral Source' field is required or not required, based on the value in the 'Require Referral Source' registry setting.
  3. Enter data in all required fields and desired optional fields.
  4. Click [Submit].
  5. If desired, change the value of the 'Require Referral Source' registry setting to get a different result.
  6. Open the 'CSI Assessment' form for 'Client A'.
  7. Verify that the 'Referral Source' field is required or not required, based on the value in the 'Require Referral Source' registry setting.
  8. Close the form.
  9. If desired, submit the data in the 'CSI Submission' form.
  10. Select 'Compile' in 'Options'.
  11. Enter the desired date range.
  12. Click [Submit].
  13. Click [OK].
  14. Select 'Print' in 'Options'.
  15. Select desired file in 'Select File To Print/Submit'.
  16. Click [Print Selected File Information].
  17. Validate the data for 'Client A', including the 'Referral Source'.
  18. If desired, submit the file.
California Required EDI -CSI
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SoapUI - CSIAssessment
Scenario 1: 'CSIAssessment' web service - Add & Update CSI Assessment
Specific Setup:
  • Registry Settings: 'Avatar PM->California Required EDI->CSI->->->Require Referral Source' = desired value. Note the value and expected result.
  • Client: 'Client A' is admitted to a program that contains 'Yes' in 'Mental Health Program (CSI)'.
Steps
  1. Access SoapUI for the 'CSIAssessment' - 'AddCSIAssessment' web service.
  2. Fill out all required and desired fields.
  3. Click [Run].
  4. Validate the 'AddCSIAssessmentResponse' field is populated with data.
  5. Validate the 'Confirmation' field contains a value such as:ClientID:273||EP:1||UniqueID:CSS65274.001.
  6. Validate the 'Message' field contains: CSI Assessment web service has been filed successfully.
  7. Select 'Client A' and access the 'CSI Assessment' form.
  8. Select the desired episode from the Pre-Display and click [OK].
  9. Click [Edit].
  10. Validate the submitted data displays.
  11. Discard the form.
  12. Access SoapUI for the 'CSIAssessment' - 'UpdateCSIAssessment' web service.
  13. Edit at least one field. Note the edits.
  14. Click [Run].
  15. Validate the 'UpdateCSIAssessmentResponse' field is populated with data.
  16. Validate the 'Confirmation' field contains a value such as: ClientID:273||EP:1||UniqueID:CSS65274.001.
  17. Validate the 'Message' field contains: CSI Assessment web service has been filed successfully.
  18. Select 'Client A' and access the 'CSI Assessment' form.
  19. Select the desired episode from the Pre-Display and click [OK].
  20. Click [Edit].
  21. Validate the edited data displays.
  22. Discard the form.

Topics
• NX • CSI Assessment (Call Intake) • CSI Assessment • Web Services
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
  • Pre Admit
  • SoapUI - ClientDemographics
  • SoapUI - UpdateAdmission
  • Admission (Outpatient)
  • 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: '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 11: '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 70 Summary | Details
Family Registration - cache storage table optimization.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Family Registration (CAL)
  • Change MR#
Scenario 1: Family Registration form - field validation - Successful registration.
Specific Setup:

Registry Settings:

  • Set the registry setting 'UMDAP Housing Adjustment Percentage' as any desired percentage value within the range of 1 to 100.

Form designer:

  • Add the hidden elements 'Housing Costs' and 'Housing Adjustment' under the Third Subsection of the UMDAP Information Tab.

Clients:

  • More than one existing client is identified or new ones are created to be used in the family registration process.
  • Client 1
  • Client 2

Family:

  • An existing family with no member(s) and with all the UMDAP data should be identified or created.
  • Family A
Steps
  1. Open the "Family Registration" form.
  2. Enter a desired name for the Family - 'Family B'.
  3. Click [New Family].
  4. Fill in all the needed field values in the "Family Registration" section.
  5. Click on the "Family Members" section.
  6. Select the [Add New Item].
  7. Add 'Client 1' and 'Client 2' as the members.
  8. Fill in all the needed field values in the "Family Members" section.
  9. Verify the "Type of Family Member" column displayed in the "Family Membership Information" grid. Note: as this grid contains many fields, you may need to drag the border between fields to widen the view of this, or any of the other, fields in the grid.
  10. Select the "UMDAP Information" section.
  11. Click [Add New Item].
  12. Validate that the fields "Housing Costs" & "Housing Adjustment" are present in the form.
  13. Fill in all the mandatory field values along with the other desired optional field values.
  14. Click [Submit].
  15. Create an SQL query to the below tables and validate that the above-filed data are saved and shown in the respective cache storage tables,
  16. Validate the Family Demographics information in "SYSTEM.family_current_demographics",
  17. Validate the Member information(s) in "SYSTEM.family_membership_information",
  18. Validate the UMDAP information in "SYSTEM.family_umdap_info".
  19. Close the SQL, return to the NX window, and open the 'Family Registration' form.
  20. Select 'Family A'.
  21. Click on the "Family Members" section.
  22. Verify that no members are existing in the grid.
  23. Select the [Add New Item].
  24. Add 'Client 1' as a member.
  25. Verify that we see an error message stating that there is a Date Range Overlap found with Another Family Assignment for the date range.
  26. Click [OK].
  27. Click [Discard].
  28. Click [Yes].
  29. Open the 'Family Registration' form.
  30. Select 'Family B'.
  31. Click on the "Family Members" section.
  32. Select 'Client 1' from the grid.
  33. Click [Edit Selected Item].
  34. Enter a future date value for the field 'End Date Of Family Membership date'.
  35. Click [Submit].
  36. Create an SQL query to the below table for 'Family B' and validate that 'Client 1' is updated with the 'fam_memb_end_date' value,
  37. "SYSTEM.family_membership_information".
  38. Close the SQL, return to the NX window, and open the 'Family Registration' form.
  39. Select 'Family A'.
  40. Click on the "Family Members" section.
  41. Verify that no members are existing in the grid.
  42. Select the [Add New Item].
  43. Add 'Client 1' as a member.
  44. Enter a date value that falls between the 'Start Date Of Family Membership date' and 'End Date Of Family Membership date' range of 'Client 1' in 'Family B'.
  45. Verify that we see an error message for 'Date Range Overlaps Another Family AssignmentFamily'.
  46. Click [OK].
  47. Enter a date value that is outside the 'Start Date Of Family Membership date' and 'End Date Of Family Membership date' range of 'Client 1' in 'Family B'.
  48. Click [Submit].
  49. Create an SQL query to the below table for Family A and validate that Client 1 is added as a member of the family.
  50. "SYSTEM.family_membership_information".
  51. Create an SQL query to the below table for Family B and validate that Client 1 is also showing with the 'fam_memb_end_date' value.
  52. "SYSTEM.family_membership_information".
  53. Close the SQL.
Scenario 2: Family Registration form - Delete/ Change MR#/ Merge - Clients.
Specific Setup:

Family Registration:

  • A family with more than one member and with all the UMDAP data should be identified or created.
  • Family A:
  • Member 1 (Client 1)
  • Member 2 (Client 2)

Clients:

  • Adding to the above clients, An existing client is identified or a new one is created for the Client Merge process. The client identified/created should have the same information (except for the program) as the member whom we want to merge with.
  • Client 3
Steps
  1. Open the "Family Registration" form.
  2. Enter the Family ID for - 'Family A'.
  3. Select Family A.
  4. Click on the "Family Members" item.
  5. Verify that the members exist and are shown in the grid.
  6. Select 'Member 2' from the grid.
  7. Click [Delete Selected Item].
  8. Click [Yes].
  9. Verify that the member we deleted is removed from the grid, upon successful delete.
  10. Select the "UMDAP Information" item.
  11. Verify that the existing UMDAP record(s) are shown in the grid.
  12. Click [Submit].
  13. Create an SQL query to the below table for Family A and validate that there are no records found for 'Client 2',
  14. "SYSTEM.family_membership_information".
  15. Create an SQL query to the below table for 'Family A' and validate that there are UMDAP data available, which is the same as the data we filed using the 'Family Registration form',
  16. "SYSTEM.family_umdap_info".
  17. Close the querying window and return to the NX window.
  18. Open the "Family Registration" form.
  19. Enter the Family ID for - 'Family A'.
  20. Select 'Family A'.
  21. Click on the "Family Members" item.
  22. Verify that the members exist and are shown in the grid.
  23. Click [Add New Item].
  24. Enter the 'Client ID' field with 'Client 1' and select it.
  25. Verify that we see a popup that says that there is a Date Range Overlap found with the Previous Entry For ClientStart and End Date(s).
  26. Click [OK].
  27. Enter the 'Client ID' field with 'Client 2' and select it.
  28. Fill in all the needed values.
  29. Verify that the new member is now added and shown in the grid.
  30. Select the "UMDAP Information" item.
  31. Select the existing record from the 'UMDAP Information' grid.
  32. Click [Delete Selected Item].
  33. Click [Yes].
  34. Verify that there are no records in the 'UMDAP Information' grid.
  35. Click [Submit].
  36. Create an SQL query to the below table for 'Family A' and validate that there is an existing record found for 'Client 2',
  37. "SYSTEM.family_membership_information".
  38. Create an SQL query to the below table for 'Family A' and validate that there are no UMDAP data available,
  39. "SYSTEM.family_umdap_info".
  40. Close the querying window and return to the NX window.
  41. Open the "Change MR#" form.
  42. Enter the 'Client ID' field with 'Client 2' and select it.
  43. Click [Assign MR#].
  44. Click [Yes].
  45. Validate that the 'New Client ID#' input box contains a new ID - 'New Client 2'.
  46. Click [Submit].
  47. Open the "Family Registration" form.
  48. Enter the Family ID for - 'Family A'.
  49. Select 'Family A'.
  50. Click on the "Family Members" item.
  51. Verify that the members exist and are shown in the grid.
  52. Select 'Member 2' from the grid.
  53. Click [Edit Selected Item].
  54. Validate that the Client ID is replaced with the new MR#. (i.e. 'New Client 2').
  55. Click [Discard].
  56. Click [Yes].
  57. Create an SQL query to the below table for Family A and validate that there are no records found for 'Client 2',
  58. "SYSTEM.family_membership_information".
  59. Verify that we do have a record for 'New Client 2' in the table for 'Family A'.
  60. Close the querying window and return to the NX window.
  61. Open the "Client Merge" form.
  62. Enter the 'Client ID' field with 'New Client 2' and select it.
  63. Select the Episode value from the 'Source Client Episode' dropdown field.
  64. Enter the 'Client ID' field with 'Client 3' and select it.
  65. Click [File].
  66. Click [Yes].
  67. Click [OK].
  68. Click [Discard].
  69. Click [Yes].
  70. Open the "Family Registration" form.
  71. Enter the Family ID for - 'Family A'.
  72. Select 'Family A'.
  73. Click on the "Family Members" item.
  74. Verify that the members exist and are shown in the grid.
  75. Select 'Member 2' from the grid.
  76. Click [Edit Selected Item].
  77. Validate that the Client ID is replaced with 'Client 3'.
  78. Click [Discard].
  79. Click [Yes].
  80. Create an SQL query to the below table for 'Family A' and validate that there are no records found for 'New Client 2',
  81. "SYSTEM.family_membership_information".
  82. Verify that we do have a record for 'Client 3' in the table for 'Family A'.
  83. Close the SQL.

Topics
• Family Registration
2023 Update 75 Summary | Details
Registry Setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
  • Electronic Billing
  • Discharge
  • File Import
Scenario 1: 837I Compile - With '837I-Dates To Populate 2300 DTP' RS 1
Specific Setup:
  • Guarantor:
  • An active guarantor is identified or created - "Guarantor 1".
  • Guarantor/Program Billing Defaults Template:
  • An active 'Guarantor/Program Billing Defaults' template is identified or created that includes "Guarantor 1" - "Template 1".
Steps
  1. Open the 'Registry Settings' form.
  2. Set the 'Limit Registry Settings to the Following Search Criteria' text input box to "837I-Dates To Populate 2300 DTP".
  3. Select 'Yes' in 'Include Hidden Registry Settings'.
  4. Click [View Registry Settings].
  5. Validate that the registry setting exists and show the respective values.
  6. Set the 'Registry Setting Value' field to '1'.
  7. Click [Submit].
  8. Click [OK].
  9. Click [No].
  10. Open the 'Guarantor/Program Billing Defaults' form.
  11. Select 'Edit Template'.
  12. Select "Template 1" from the 'Select Template' dropdown.
  13. Select '837 Institutional'.
  14. Validate that the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' is shown with the following options, (none selected by default):
  15. Yes (Inpatient/Outpatient)
  16. Yes (Outpatient Only)
  17. Yes (Inpatient Only)
  18. No (Inpatient/Outpatient)
  19. Click [Submit].
  20. Click [No].
  21. Open the 'Admission' form.
  22. Admit an Inpatient client - "Client 1".
  23. Using the 'Diagnosis' form, File an active diagnosis record for "Client 1".
  24. File the 'Financial Eligibility' form for "Client 1", with "Guarantor 1".
  25. Specify the 'Coverage Effective Date' and 'Coverage Expiration Date' in the financial eligibility.
  26. Create charges for "Client 1" for more than one date, with the dates between the dates saved in step 21.
  27. Create a new Interim Billing Batch File, "Batch 1", which covers the services created for "Client 1" in step 22.
  28. Close the charges using the Interim Billing Batch File, "Batch 1".
  29. Open 'Client Ledger'.
  30. Select "Client 1" and the respective Episode.
  31. Validate that all the services are closed.
  32. Open 'Electronic Billing'.
  33. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  34. Set 'First Date Of Service To Include' with a date before the 'Coverage Effective Date' filed in step 21.
  35. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  36. Click [Process].
  37. Validate that the compile completes successfully.
  38. Click [OK].
  39. Select 'Dump File' from 'Billing Options'.
  40. Select 'Print' from 'Print Or Delete Report'.
  41. Select the file compiled in step 31.
  42. Click [Process].
  43. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first and last dates of the services being billed.
  44. Close the report.
  45. Click [No].
  46. Open 'Discharge' form.
  47. Set the 'Date Of Discharge' field to a date that is the day after the last day of service.
  48. Fill in all the required fields and select [Submit].
  49. Open 'Electronic Billing'.
  50. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  51. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  52. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  53. Click [Process].
  54. Validate that the compile completes successfully.
  55. Click [OK].
  56. Select 'Dump File' from 'Billing Options'.
  57. Select 'Print' from 'Print Or Delete Report'.
  58. Select the file compiled in step 46.
  59. Click [Process].
  60. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first date of the service being billed and the discharge date file in step 41.
  61. Close the report.
  62. Click [No].
  63. Open the 'Guarantor/Program Billing Defaults' form.
  64. Select 'Edit Template'.
  65. Select "Template 1" from the 'Select Template' dropdown.
  66. Select '837 Institutional'.
  67. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'Yes (Inpatient/Outpatient)'.
  68. Click [Submit].
  69. Click [No].
  70. Open 'Electronic Billing'.
  71. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  72. Set 'First Date Of Service To Include' a date before the 'Coverage Effective Date' filed in step 21.
  73. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  74. Click [Process].
  75. Validate that the compile completes successfully.
  76. Click [OK].
  77. Select 'Dump File' from 'Billing Options'.
  78. Select 'Print' from 'Print Or Delete Report'.
  79. Select the file compiled in step 65.
  80. Click [Process].
  81. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first date of the service being billed and the discharge date file in step 41.
  82. Close the report.
  83. Click [No].
  84. Open the 'Guarantor/Program Billing Defaults' form.
  85. Select 'Edit Template'.
  86. Select "Template 1" from the 'Select Template' dropdown.
  87. Select '837 Institutional'.
  88. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'Yes (Inpatient Only)'.
  89. Click [Submit].
  90. Click [No].
  91. Open 'Electronic Billing'.
  92. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  93. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  94. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  95. Click [Process].
  96. Validate that the compile completes successfully.
  97. Click [OK].
  98. Select 'Dump File' from 'Billing Options'.
  99. Select 'Print' from 'Print Or Delete Report'.
  100. Select the file compiled in step 85.
  101. Click [Process].
  102. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first date of the service being billed and the discharge date file in step 41.
  103. Close the report.
  104. Click [No].
  105. Open the 'Guarantor/Program Billing Defaults' form.
  106. Select 'Edit Template'.
  107. Select "Template 1" from the 'Select Template' dropdown.
  108. Select '837 Institutional'.
  109. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'Yes (Inpatient Only)'.
  110. Click [Submit].
  111. Click [No].
  112. Open 'Electronic Billing'.
  113. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  114. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  115. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  116. Click [Process].
  117. Validate that the compile completes successfully.
  118. Click [OK].
  119. Select 'Dump File' from 'Billing Options'.
  120. Select 'Print' from 'Print Or Delete Report'.
  121. Select the file compiled in step 105.
  122. Click [Process].
  123. Validate that the discharge date is not included instead, the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first and last dates of the services being billed.
  124. Close the report.
  125. Click [No].
  126. Open the 'Guarantor/Program Billing Defaults' form.
  127. Select 'Edit Template'.
  128. Select "Template 1" from the 'Select Template' dropdown.
  129. Select '837 Institutional'.
  130. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'No (Inpatient/Outpatient)'.
  131. Click [Submit].
  132. Click [No].
  133. Open 'Electronic Billing'.
  134. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  135. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  136. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  137. Click [Process].
  138. Validate that the compile completes successfully.
  139. Click [OK].
  140. Select 'Dump File' from 'Billing Options'.
  141. Select 'Print' from 'Print Or Delete Report'.
  142. Select the file compiled in step 105.
  143. Click [Process].
  144. Validate that the discharge date is not included instead, the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first and last dates of the services being billed.
  145. Close the report.
  146. Click [No].
  147. Query the tables below and validate that the new columns 'inc_dis_dt_2300_dtp_code' and 'inc_dis_dt_2300_dtp_value' are shown with the field 'Include Discharge Date In Statement To Date (2300-DTP)' value,
  148. SYSTEM.file_import_gpbdt_i837
  149. SYSTEM.table_837_i_facility_prov_num
  150. Close the SQL query window.
Scenario 2: File Import - Guarantor Program Billing Defaults - New field validations
Specific Setup:
  • At least one 'Guarantor/Program Billing Defaults' template exists, "Template 1", and the 837 Professional and Institutional sections contain data.
  • Files can be saved to the local desktop, "File A", edited, and imported back into Avatar through 'File Import'.
  • Registry setting '837I-Dates To Populate 2300 DTP' value set as '1'.
Steps
  1. Open 'Guarantor/Program Billing Defaults'.
  2. Edit the ‘837 Institutional’ section of "Template 1".
  3. Validate that the new field has no values selected.
  4. Click [Submit].
  5. Export the template in 'Edit' mode, saving it to the desktop with a unique name "File A".
  6. Edit the 'Edit' mode template to have a value defined for piece 130- 'Include Discharge Date In Statement To Date (2300-DTP)' and save it.
  7. Open 'File Import'.
  8. Import/Compile/Post the 'Edit' mode template "File A" in the 'Guarantor/Program Billing Defaults Template' file type.
  9. Select 'Print File'.
  10. Print the file posted in step 8 by selecting it and clicking 'Process Action'.
  11. Validate that the Crystal report is included with the new field 'Include Discharge Date In Statement To Date (2300-DTP)' and it's value we selected in step 6 for file import for 837 Institutional.
  12. Open 'Guarantor/Program Billing Defaults'.
  13. Select 'Edit Template'.
  14. Select the 'Edit mode template', "Template 1".
  15. Select the ‘837 Professional’ section. The field, 'Include Discharge Date In Statement To Date (2300-DTP)' will have the value used in step 6.
  16. Click [Submit].
  17. Click [No].
Scenario 3: 837I Compile - With '837I-Dates To Populate 2300 DTP' RS 2
Specific Setup:
  • Guarantor:
  • An active guarantor is identified or created - "Guarantor 1".
  • Guarantor/Program Billing Defaults Template:
  • An active 'Guarantor/Program Billing Defaults' template is identified or created that includes "Guarantor 1" - "Template 1".
Steps
  1. Open the 'Registry Settings' form.
  2. Set the 'Limit Registry Settings to the Following Search Criteria' text input box to "837I-Dates To Populate 2300 DTP".
  3. Select 'Yes' in 'Include Hidden Registry Settings'.
  4. Click [View Registry Settings].
  5. Validate that the registry setting exists and show the respective values.
  6. Set the 'Registry Setting Value' field to '2'.
  7. Click [Submit].
  8. Click [OK].
  9. Click [No].
  10. Open the 'Guarantor/Program Billing Defaults' form.
  11. Select 'Edit Template'.
  12. Select "Template 1" from the 'Select Template' dropdown.
  13. Select '837 Institutional'.
  14. Validate that the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' is not shown.
  15. Click [Submit].
  16. Click [No].
  17. Open the 'Admission' form.
  18. Admit an Inpatient client - "Client 1".
  19. Using the 'Diagnosis' form, File an active diagnosis record for "Client 1".
  20. File the 'Financial Eligibility' form for "Client 1", with "Guarantor 1".
  21. Specify the 'Coverage Effective Date' and 'Coverage Expiration Date' in the financial eligibility.
  22. Create charges for "Client 1" for more than one date(s), that fall between the dates saved in step 21.
  23. Create a new Interim Billing Batch File "Batch 1" which covers the services created for "Client 1" in step 22.
  24. Close the charges using the Interim Billing Batch File "Batch 1".
  25. Open 'Client Ledger'.
  26. Select "Client 1" and the respective Episode.
  27. Validate that all the services are closed.
  28. Open 'Electronic Billing'.
  29. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  30. Set 'First Date Of Service To Include' with the date earlier than the 'Coverage Effective Date' filed in step 21.
  31. Set 'Last Date Of Service To Include' with a date later than the 'Coverage Expiration Date' filed in step 21.
  32. Click [Process].
  33. Validate that the compile completes successfully.
  34. Click [OK].
  35. Select 'Dump File' from 'Billing Options'.
  36. Select 'Print' from 'Print Or Delete Report'.
  37. Select the file compiled in step 31.
  38. Click [Process].
  39. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the 'Coverage Effective date' filed in step 21 and the 'Last Date Of Service To Include' selected in step 29(b).
  40. Close the report.
  41. Click [No].
  42. Open 'Discharge' form.
  43. Set the 'Date Of Discharge' field to a date that is greater than the 'Coverage Expiration Date' filed in step 21.
  44. Fill in all the required fields and select [Submit].
  45. Open 'Electronic Billing'.
  46. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  47. Set 'First Date Of Service To Include' with the date earlier than the 'Coverage Effective Date' filed in step 21.
  48. Set 'Last Date Of Service To Include' with a date later than the 'Coverage Expiration Date' filed in step 21.
  49. Click [Process].
  50. Validate that the compile completes successfully.
  51. Click [OK].
  52. Select 'Dump File' from 'Billing Options'.
  53. Select 'Print' from 'Print Or Delete Report'.
  54. Select the file compiled in step 46.
  55. Click [Process].
  56. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the 'Coverage Effective Date' and 'Coverage Expiration Date' filed in step 21.
  57. Close the report.
  58. Click [No].
  59. Open 'Electronic Billing'.
  60. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  61. Set 'First Date Of Service To Include' with the date later than the 'Coverage Effective Date' filed in step 21.
  62. Set 'Last Date Of Service To Include' with a date earlier than the 'Coverage Expiration Date' filed in step 21.
  63. Click [Process].
  64. Validate that the compile completes successfully.
  65. Click [OK].
  66. Select 'Dump File' from 'Billing Options'.
  67. Select 'Print' from 'Print Or Delete Report'.
  68. Select the file compiled in step 46.
  69. Click [Process].
  70. Validate that the discharge date is not included instead, the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the First Date Of Service To Include' and 'Last Date Of Service To Include' dates used in the step 57(a, b).
  71. Close the report.
  72. Click [No].
Scenario 4: "Restrict Coverage Effective Date Edits to Prior Dates Only" registry setting functionality
Specific Setup:
  • Client: The client should be admitted and have an active episode - "Client A".
  • Financial Eligibility: "Client A" should have an already existing Financial Eligibility record with both Coverage Effective and Expiration dates.
Steps
  1. Open the 'Registry Settings' form.
  2. Set the 'Limit Registry Settings to the Following Search Criteria' to 'Restrict Coverage Effective Date Edits to Prior Dates Only'.
  3. Click [View Registry Settings].
  4. Validate that the respective registry setting shows up.
  5. Set the 'Avatar PM->Billing->Financial Eligibility->->->Restrict Coverage Effective Date Edits to Prior Dates Only' registry setting to a value other than 'Y' or 'N'.
  6. Verify an error message displays that the valid choices are 'Y or N' only.
  7. Set the 'Avatar PM->Billing->Financial Eligibility->->->Restrict Coverage Effective Date Edits to Prior Dates Only' registry setting to 'Y' and then submit to save.
  8. Open the 'Financial Eligibility' form.
  9. Search and select "Client A".
  10. Select the Episode from the grid.
  11. Select 'Guarantor Selection'.
  12. Check if the 'Coverage Effective Date' field is already showing the date in the file.
  13. Try to enter a date that is after the date that is already in the file and move away from the field.
  14. Validate that an error message appears when updating the 'Coverage Effective Date' field to a date that is later than the previously filed date.
  15. Validate the error text - 'The Coverage Effective Date cannot be updated to be later than the previously filed date.'.
  16. Click [OK].
  17. Validate that the 'Coverage Effective Date' field is restored with the last value saved.
  18. Set 'Coverage Effective Date' with a date that is before the date that is already in the file and move away from the field.
  19. Validate that there are no errors shown.
  20. Click [Submit].
  21. Open the 'Financial Eligibility' form.
  22. Search and select "Client A".
  23. Select the Episode from the grid.
  24. Select 'Guarantor Selection'.
  25. Check if the 'Coverage Effective Date' field is showing with the date we save in step 18.
  26. Click [Discard].
  27. Click [Yes].
  28. Open the 'Registry Settings' form.
  29. Set the 'Limit Registry Settings to the Following Search Criteria' to 'Restrict Coverage Effective Date Edits to Prior Dates Only'.
  30. Click [View Registry Settings].
  31. Set the 'Avatar PM->Billing->Financial Eligibility->->->Restrict Coverage Effective Date Edits to Prior Dates Only' registry setting to 'N' and then submit to save.
  32. Open the 'Financial Eligibility' form.
  33. Search and select "Client A".
  34. Select the Episode from the grid.
  35. Select 'Guarantor Selection'.
  36. Check if the 'Coverage Effective Date' field is showing with the date we save in step 18.
  37. Try to enter a date that is after the date that is already in the file and move away from the field.
  38. Validate that there are no errors shown.
  39. Click [Submit].
  40. Open the 'Financial Eligibility' form.
  41. Search and select "Client A".
  42. Select the Episode from the grid.
  43. Select 'Guarantor Selection'.
  44. Check if the 'Coverage Effective Date' field is showing with the date we save in step 37.
  45. Click [Discard].
  46. Click [Yes].
Scenario 5: Update Financial Eligibility - 'Coverage Effective Date' - Webservice
Specific Setup:
  • Client: The client should be admitted and have an active episode - "Client A"
  • Financial Eligibility: "Client A" should have an already existing Financial Eligibility record with both Coverage Effective and Expiration dates.
  • Registry Setting: Set the 'Restrict Coverage Effective Date Edits to Prior Dates Only' setting value as 'Y'.
Steps
  1. Open SoapUI or any other web service testing tool.
  2. Create a web service request to update the Financial Eligibility information.
  3. Enter the same value in the "SYSTEMCODE" which is used to sign into Avatar.
  4. Enter the same value in the "USERNAME" which is used to sign into Avatar.
  5. Set the value for 'CoverageEffectiveDate' with a date that is after the date already in the file for "Client A".
  6. Enter values for all other required fields.
  7. Submit the request.
  8. Verify that the service failed to post with the error message: "The Coverage Effective Date cannot be updated to be later than the previously filed date."
  9. Set the value for 'CoverageEffectiveDate' with a date that is before the date already in the file for "Client A".
  10. Submit the request.
  11. Verify that the service was posted successfully with the message: "Financial Eligibility web service has been filed successfully."
  12. Open 'Financial Eligibility' for the "Client A".
  13. Select 'Guarantor Selection'.
  14. Validate that the 'Coverage Effective Date' is showing the value that we posted in step 9.
  15. Click [Discard].
  16. Click [Yes].
Registry Setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
  • Electronic Billing
  • Discharge
  • File Import
Scenario 1: 837I Compile - With '837I-Dates To Populate 2300 DTP' RS 1
Specific Setup:
  • Guarantor:
  • An active guarantor is identified or created - "Guarantor 1".
  • Guarantor/Program Billing Defaults Template:
  • An active 'Guarantor/Program Billing Defaults' template is identified or created that includes "Guarantor 1" - "Template 1".
Steps
  1. Open the 'Registry Settings' form.
  2. Set the 'Limit Registry Settings to the Following Search Criteria' text input box to "837I-Dates To Populate 2300 DTP".
  3. Select 'Yes' in 'Include Hidden Registry Settings'.
  4. Click [View Registry Settings].
  5. Validate that the registry setting exists and show the respective values.
  6. Set the 'Registry Setting Value' field to '1'.
  7. Click [Submit].
  8. Click [OK].
  9. Click [No].
  10. Open the 'Guarantor/Program Billing Defaults' form.
  11. Select 'Edit Template'.
  12. Select "Template 1" from the 'Select Template' dropdown.
  13. Select '837 Institutional'.
  14. Validate that the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' is shown with the following options, (none selected by default):
  15. Yes (Inpatient/Outpatient)
  16. Yes (Outpatient Only)
  17. Yes (Inpatient Only)
  18. No (Inpatient/Outpatient)
  19. Click [Submit].
  20. Click [No].
  21. Open the 'Admission' form.
  22. Admit an Inpatient client - "Client 1".
  23. Using the 'Diagnosis' form, File an active diagnosis record for "Client 1".
  24. File the 'Financial Eligibility' form for "Client 1", with "Guarantor 1".
  25. Specify the 'Coverage Effective Date' and 'Coverage Expiration Date' in the financial eligibility.
  26. Create charges for "Client 1" for more than one date, with the dates between the dates saved in step 21.
  27. Create a new Interim Billing Batch File, "Batch 1", which covers the services created for "Client 1" in step 22.
  28. Close the charges using the Interim Billing Batch File, "Batch 1".
  29. Open 'Client Ledger'.
  30. Select "Client 1" and the respective Episode.
  31. Validate that all the services are closed.
  32. Open 'Electronic Billing'.
  33. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  34. Set 'First Date Of Service To Include' with a date before the 'Coverage Effective Date' filed in step 21.
  35. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  36. Click [Process].
  37. Validate that the compile completes successfully.
  38. Click [OK].
  39. Select 'Dump File' from 'Billing Options'.
  40. Select 'Print' from 'Print Or Delete Report'.
  41. Select the file compiled in step 31.
  42. Click [Process].
  43. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first and last dates of the services being billed.
  44. Close the report.
  45. Click [No].
  46. Open 'Discharge' form.
  47. Set the 'Date Of Discharge' field to a date that is the day after the last day of service.
  48. Fill in all the required fields and select [Submit].
  49. Open 'Electronic Billing'.
  50. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  51. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  52. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  53. Click [Process].
  54. Validate that the compile completes successfully.
  55. Click [OK].
  56. Select 'Dump File' from 'Billing Options'.
  57. Select 'Print' from 'Print Or Delete Report'.
  58. Select the file compiled in step 46.
  59. Click [Process].
  60. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first date of the service being billed and the discharge date file in step 41.
  61. Close the report.
  62. Click [No].
  63. Open the 'Guarantor/Program Billing Defaults' form.
  64. Select 'Edit Template'.
  65. Select "Template 1" from the 'Select Template' dropdown.
  66. Select '837 Institutional'.
  67. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'Yes (Inpatient/Outpatient)'.
  68. Click [Submit].
  69. Click [No].
  70. Open 'Electronic Billing'.
  71. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  72. Set 'First Date Of Service To Include' a date before the 'Coverage Effective Date' filed in step 21.
  73. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  74. Click [Process].
  75. Validate that the compile completes successfully.
  76. Click [OK].
  77. Select 'Dump File' from 'Billing Options'.
  78. Select 'Print' from 'Print Or Delete Report'.
  79. Select the file compiled in step 65.
  80. Click [Process].
  81. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first date of the service being billed and the discharge date file in step 41.
  82. Close the report.
  83. Click [No].
  84. Open the 'Guarantor/Program Billing Defaults' form.
  85. Select 'Edit Template'.
  86. Select "Template 1" from the 'Select Template' dropdown.
  87. Select '837 Institutional'.
  88. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'Yes (Inpatient Only)'.
  89. Click [Submit].
  90. Click [No].
  91. Open 'Electronic Billing'.
  92. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  93. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  94. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  95. Click [Process].
  96. Validate that the compile completes successfully.
  97. Click [OK].
  98. Select 'Dump File' from 'Billing Options'.
  99. Select 'Print' from 'Print Or Delete Report'.
  100. Select the file compiled in step 85.
  101. Click [Process].
  102. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first date of the service being billed and the discharge date file in step 41.
  103. Close the report.
  104. Click [No].
  105. Open the 'Guarantor/Program Billing Defaults' form.
  106. Select 'Edit Template'.
  107. Select "Template 1" from the 'Select Template' dropdown.
  108. Select '837 Institutional'.
  109. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'Yes (Inpatient Only)'.
  110. Click [Submit].
  111. Click [No].
  112. Open 'Electronic Billing'.
  113. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  114. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  115. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  116. Click [Process].
  117. Validate that the compile completes successfully.
  118. Click [OK].
  119. Select 'Dump File' from 'Billing Options'.
  120. Select 'Print' from 'Print Or Delete Report'.
  121. Select the file compiled in step 105.
  122. Click [Process].
  123. Validate that the discharge date is not included instead, the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first and last dates of the services being billed.
  124. Close the report.
  125. Click [No].
  126. Open the 'Guarantor/Program Billing Defaults' form.
  127. Select 'Edit Template'.
  128. Select "Template 1" from the 'Select Template' dropdown.
  129. Select '837 Institutional'.
  130. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'No (Inpatient/Outpatient)'.
  131. Click [Submit].
  132. Click [No].
  133. Open 'Electronic Billing'.
  134. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  135. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  136. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  137. Click [Process].
  138. Validate that the compile completes successfully.
  139. Click [OK].
  140. Select 'Dump File' from 'Billing Options'.
  141. Select 'Print' from 'Print Or Delete Report'.
  142. Select the file compiled in step 105.
  143. Click [Process].
  144. Validate that the discharge date is not included instead, the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first and last dates of the services being billed.
  145. Close the report.
  146. Click [No].
  147. Query the tables below and validate that the new columns 'inc_dis_dt_2300_dtp_code' and 'inc_dis_dt_2300_dtp_value' are shown with the field 'Include Discharge Date In Statement To Date (2300-DTP)' value,
  148. SYSTEM.file_import_gpbdt_i837
  149. SYSTEM.table_837_i_facility_prov_num
  150. Close the SQL query window.
Scenario 2: File Import - Guarantor Program Billing Defaults - New field validations
Specific Setup:
  • At least one 'Guarantor/Program Billing Defaults' template exists, "Template 1", and the 837 Professional and Institutional sections contain data.
  • Files can be saved to the local desktop, "File A", edited, and imported back into Avatar through 'File Import'.
  • Registry setting '837I-Dates To Populate 2300 DTP' value set as '1'.
Steps
  1. Open 'Guarantor/Program Billing Defaults'.
  2. Edit the ‘837 Institutional’ section of "Template 1".
  3. Validate that the new field has no values selected.
  4. Click [Submit].
  5. Export the template in 'Edit' mode, saving it to the desktop with a unique name "File A".
  6. Edit the 'Edit' mode template to have a value defined for piece 130- 'Include Discharge Date In Statement To Date (2300-DTP)' and save it.
  7. Open 'File Import'.
  8. Import/Compile/Post the 'Edit' mode template "File A" in the 'Guarantor/Program Billing Defaults Template' file type.
  9. Select 'Print File'.
  10. Print the file posted in step 8 by selecting it and clicking 'Process Action'.
  11. Validate that the Crystal report is included with the new field 'Include Discharge Date In Statement To Date (2300-DTP)' and it's value we selected in step 6 for file import for 837 Institutional.
  12. Open 'Guarantor/Program Billing Defaults'.
  13. Select 'Edit Template'.
  14. Select the 'Edit mode template', "Template 1".
  15. Select the ‘837 Professional’ section. The field, 'Include Discharge Date In Statement To Date (2300-DTP)' will have the value used in step 6.
  16. Click [Submit].
  17. Click [No].
Scenario 3: 837I Compile - With '837I-Dates To Populate 2300 DTP' RS 2
Specific Setup:
  • Guarantor:
  • An active guarantor is identified or created - "Guarantor 1".
  • Guarantor/Program Billing Defaults Template:
  • An active 'Guarantor/Program Billing Defaults' template is identified or created that includes "Guarantor 1" - "Template 1".
Steps
  1. Open the 'Registry Settings' form.
  2. Set the 'Limit Registry Settings to the Following Search Criteria' text input box to "837I-Dates To Populate 2300 DTP".
  3. Select 'Yes' in 'Include Hidden Registry Settings'.
  4. Click [View Registry Settings].
  5. Validate that the registry setting exists and show the respective values.
  6. Set the 'Registry Setting Value' field to '2'.
  7. Click [Submit].
  8. Click [OK].
  9. Click [No].
  10. Open the 'Guarantor/Program Billing Defaults' form.
  11. Select 'Edit Template'.
  12. Select "Template 1" from the 'Select Template' dropdown.
  13. Select '837 Institutional'.
  14. Validate that the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' is not shown.
  15. Click [Submit].
  16. Click [No].
  17. Open the 'Admission' form.
  18. Admit an Inpatient client - "Client 1".
  19. Using the 'Diagnosis' form, File an active diagnosis record for "Client 1".
  20. File the 'Financial Eligibility' form for "Client 1", with "Guarantor 1".
  21. Specify the 'Coverage Effective Date' and 'Coverage Expiration Date' in the financial eligibility.
  22. Create charges for "Client 1" for more than one date(s), that fall between the dates saved in step 21.
  23. Create a new Interim Billing Batch File "Batch 1" which covers the services created for "Client 1" in step 22.
  24. Close the charges using the Interim Billing Batch File "Batch 1".
  25. Open 'Client Ledger'.
  26. Select "Client 1" and the respective Episode.
  27. Validate that all the services are closed.
  28. Open 'Electronic Billing'.
  29. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  30. Set 'First Date Of Service To Include' with the date earlier than the 'Coverage Effective Date' filed in step 21.
  31. Set 'Last Date Of Service To Include' with a date later than the 'Coverage Expiration Date' filed in step 21.
  32. Click [Process].
  33. Validate that the compile completes successfully.
  34. Click [OK].
  35. Select 'Dump File' from 'Billing Options'.
  36. Select 'Print' from 'Print Or Delete Report'.
  37. Select the file compiled in step 31.
  38. Click [Process].
  39. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the 'Coverage Effective date' filed in step 21 and the 'Last Date Of Service To Include' selected in step 29(b).
  40. Close the report.
  41. Click [No].
  42. Open 'Discharge' form.
  43. Set the 'Date Of Discharge' field to a date that is greater than the 'Coverage Expiration Date' filed in step 21.
  44. Fill in all the required fields and select [Submit].
  45. Open 'Electronic Billing'.
  46. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  47. Set 'First Date Of Service To Include' with the date earlier than the 'Coverage Effective Date' filed in step 21.
  48. Set 'Last Date Of Service To Include' with a date later than the 'Coverage Expiration Date' filed in step 21.
  49. Click [Process].
  50. Validate that the compile completes successfully.
  51. Click [OK].
  52. Select 'Dump File' from 'Billing Options'.
  53. Select 'Print' from 'Print Or Delete Report'.
  54. Select the file compiled in step 46.
  55. Click [Process].
  56. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the 'Coverage Effective Date' and 'Coverage Expiration Date' filed in step 21.
  57. Close the report.
  58. Click [No].
  59. Open 'Electronic Billing'.
  60. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  61. Set 'First Date Of Service To Include' with the date later than the 'Coverage Effective Date' filed in step 21.
  62. Set 'Last Date Of Service To Include' with a date earlier than the 'Coverage Expiration Date' filed in step 21.
  63. Click [Process].
  64. Validate that the compile completes successfully.
  65. Click [OK].
  66. Select 'Dump File' from 'Billing Options'.
  67. Select 'Print' from 'Print Or Delete Report'.
  68. Select the file compiled in step 46.
  69. Click [Process].
  70. Validate that the discharge date is not included instead, the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the First Date Of Service To Include' and 'Last Date Of Service To Include' dates used in the step 57(a, b).
  71. Close the report.
  72. Click [No].
Scenario 4: "Restrict Coverage Effective Date Edits to Prior Dates Only" registry setting functionality
Specific Setup:
  • Client: The client should be admitted and have an active episode - "Client A".
  • Financial Eligibility: "Client A" should have an already existing Financial Eligibility record with both Coverage Effective and Expiration dates.
Steps
  1. Open the 'Registry Settings' form.
  2. Set the 'Limit Registry Settings to the Following Search Criteria' to 'Restrict Coverage Effective Date Edits to Prior Dates Only'.
  3. Click [View Registry Settings].
  4. Validate that the respective registry setting shows up.
  5. Set the 'Avatar PM->Billing->Financial Eligibility->->->Restrict Coverage Effective Date Edits to Prior Dates Only' registry setting to a value other than 'Y' or 'N'.
  6. Verify an error message displays that the valid choices are 'Y or N' only.
  7. Set the 'Avatar PM->Billing->Financial Eligibility->->->Restrict Coverage Effective Date Edits to Prior Dates Only' registry setting to 'Y' and then submit to save.
  8. Open the 'Financial Eligibility' form.
  9. Search and select "Client A".
  10. Select the Episode from the grid.
  11. Select 'Guarantor Selection'.
  12. Check if the 'Coverage Effective Date' field is already showing the date in the file.
  13. Try to enter a date that is after the date that is already in the file and move away from the field.
  14. Validate that an error message appears when updating the 'Coverage Effective Date' field to a date that is later than the previously filed date.
  15. Validate the error text - 'The Coverage Effective Date cannot be updated to be later than the previously filed date.'.
  16. Click [OK].
  17. Validate that the 'Coverage Effective Date' field is restored with the last value saved.
  18. Set 'Coverage Effective Date' with a date that is before the date that is already in the file and move away from the field.
  19. Validate that there are no errors shown.
  20. Click [Submit].
  21. Open the 'Financial Eligibility' form.
  22. Search and select "Client A".
  23. Select the Episode from the grid.
  24. Select 'Guarantor Selection'.
  25. Check if the 'Coverage Effective Date' field is showing with the date we save in step 18.
  26. Click [Discard].
  27. Click [Yes].
  28. Open the 'Registry Settings' form.
  29. Set the 'Limit Registry Settings to the Following Search Criteria' to 'Restrict Coverage Effective Date Edits to Prior Dates Only'.
  30. Click [View Registry Settings].
  31. Set the 'Avatar PM->Billing->Financial Eligibility->->->Restrict Coverage Effective Date Edits to Prior Dates Only' registry setting to 'N' and then submit to save.
  32. Open the 'Financial Eligibility' form.
  33. Search and select "Client A".
  34. Select the Episode from the grid.
  35. Select 'Guarantor Selection'.
  36. Check if the 'Coverage Effective Date' field is showing with the date we save in step 18.
  37. Try to enter a date that is after the date that is already in the file and move away from the field.
  38. Validate that there are no errors shown.
  39. Click [Submit].
  40. Open the 'Financial Eligibility' form.
  41. Search and select "Client A".
  42. Select the Episode from the grid.
  43. Select 'Guarantor Selection'.
  44. Check if the 'Coverage Effective Date' field is showing with the date we save in step 37.
  45. Click [Discard].
  46. Click [Yes].
Registry Setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
  • Electronic Billing
  • Discharge
  • File Import
Scenario 1: 837I Compile - With '837I-Dates To Populate 2300 DTP' RS 1
Specific Setup:
  • Guarantor:
  • An active guarantor is identified or created - "Guarantor 1".
  • Guarantor/Program Billing Defaults Template:
  • An active 'Guarantor/Program Billing Defaults' template is identified or created that includes "Guarantor 1" - "Template 1".
Steps
  1. Open the 'Registry Settings' form.
  2. Set the 'Limit Registry Settings to the Following Search Criteria' text input box to "837I-Dates To Populate 2300 DTP".
  3. Select 'Yes' in 'Include Hidden Registry Settings'.
  4. Click [View Registry Settings].
  5. Validate that the registry setting exists and show the respective values.
  6. Set the 'Registry Setting Value' field to '1'.
  7. Click [Submit].
  8. Click [OK].
  9. Click [No].
  10. Open the 'Guarantor/Program Billing Defaults' form.
  11. Select 'Edit Template'.
  12. Select "Template 1" from the 'Select Template' dropdown.
  13. Select '837 Institutional'.
  14. Validate that the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' is shown with the following options, (none selected by default):
  15. Yes (Inpatient/Outpatient)
  16. Yes (Outpatient Only)
  17. Yes (Inpatient Only)
  18. No (Inpatient/Outpatient)
  19. Click [Submit].
  20. Click [No].
  21. Open the 'Admission' form.
  22. Admit an Inpatient client - "Client 1".
  23. Using the 'Diagnosis' form, File an active diagnosis record for "Client 1".
  24. File the 'Financial Eligibility' form for "Client 1", with "Guarantor 1".
  25. Specify the 'Coverage Effective Date' and 'Coverage Expiration Date' in the financial eligibility.
  26. Create charges for "Client 1" for more than one date, with the dates between the dates saved in step 21.
  27. Create a new Interim Billing Batch File, "Batch 1", which covers the services created for "Client 1" in step 22.
  28. Close the charges using the Interim Billing Batch File, "Batch 1".
  29. Open 'Client Ledger'.
  30. Select "Client 1" and the respective Episode.
  31. Validate that all the services are closed.
  32. Open 'Electronic Billing'.
  33. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  34. Set 'First Date Of Service To Include' with a date before the 'Coverage Effective Date' filed in step 21.
  35. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  36. Click [Process].
  37. Validate that the compile completes successfully.
  38. Click [OK].
  39. Select 'Dump File' from 'Billing Options'.
  40. Select 'Print' from 'Print Or Delete Report'.
  41. Select the file compiled in step 31.
  42. Click [Process].
  43. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first and last dates of the services being billed.
  44. Close the report.
  45. Click [No].
  46. Open 'Discharge' form.
  47. Set the 'Date Of Discharge' field to a date that is the day after the last day of service.
  48. Fill in all the required fields and select [Submit].
  49. Open 'Electronic Billing'.
  50. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  51. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  52. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  53. Click [Process].
  54. Validate that the compile completes successfully.
  55. Click [OK].
  56. Select 'Dump File' from 'Billing Options'.
  57. Select 'Print' from 'Print Or Delete Report'.
  58. Select the file compiled in step 46.
  59. Click [Process].
  60. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first date of the service being billed and the discharge date file in step 41.
  61. Close the report.
  62. Click [No].
  63. Open the 'Guarantor/Program Billing Defaults' form.
  64. Select 'Edit Template'.
  65. Select "Template 1" from the 'Select Template' dropdown.
  66. Select '837 Institutional'.
  67. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'Yes (Inpatient/Outpatient)'.
  68. Click [Submit].
  69. Click [No].
  70. Open 'Electronic Billing'.
  71. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  72. Set 'First Date Of Service To Include' a date before the 'Coverage Effective Date' filed in step 21.
  73. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  74. Click [Process].
  75. Validate that the compile completes successfully.
  76. Click [OK].
  77. Select 'Dump File' from 'Billing Options'.
  78. Select 'Print' from 'Print Or Delete Report'.
  79. Select the file compiled in step 65.
  80. Click [Process].
  81. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first date of the service being billed and the discharge date file in step 41.
  82. Close the report.
  83. Click [No].
  84. Open the 'Guarantor/Program Billing Defaults' form.
  85. Select 'Edit Template'.
  86. Select "Template 1" from the 'Select Template' dropdown.
  87. Select '837 Institutional'.
  88. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'Yes (Inpatient Only)'.
  89. Click [Submit].
  90. Click [No].
  91. Open 'Electronic Billing'.
  92. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  93. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  94. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  95. Click [Process].
  96. Validate that the compile completes successfully.
  97. Click [OK].
  98. Select 'Dump File' from 'Billing Options'.
  99. Select 'Print' from 'Print Or Delete Report'.
  100. Select the file compiled in step 85.
  101. Click [Process].
  102. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first date of the service being billed and the discharge date file in step 41.
  103. Close the report.
  104. Click [No].
  105. Open the 'Guarantor/Program Billing Defaults' form.
  106. Select 'Edit Template'.
  107. Select "Template 1" from the 'Select Template' dropdown.
  108. Select '837 Institutional'.
  109. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'Yes (Inpatient Only)'.
  110. Click [Submit].
  111. Click [No].
  112. Open 'Electronic Billing'.
  113. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  114. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  115. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  116. Click [Process].
  117. Validate that the compile completes successfully.
  118. Click [OK].
  119. Select 'Dump File' from 'Billing Options'.
  120. Select 'Print' from 'Print Or Delete Report'.
  121. Select the file compiled in step 105.
  122. Click [Process].
  123. Validate that the discharge date is not included instead, the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first and last dates of the services being billed.
  124. Close the report.
  125. Click [No].
  126. Open the 'Guarantor/Program Billing Defaults' form.
  127. Select 'Edit Template'.
  128. Select "Template 1" from the 'Select Template' dropdown.
  129. Select '837 Institutional'.
  130. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'No (Inpatient/Outpatient)'.
  131. Click [Submit].
  132. Click [No].
  133. Open 'Electronic Billing'.
  134. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  135. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  136. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  137. Click [Process].
  138. Validate that the compile completes successfully.
  139. Click [OK].
  140. Select 'Dump File' from 'Billing Options'.
  141. Select 'Print' from 'Print Or Delete Report'.
  142. Select the file compiled in step 105.
  143. Click [Process].
  144. Validate that the discharge date is not included instead, the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first and last dates of the services being billed.
  145. Close the report.
  146. Click [No].
  147. Query the tables below and validate that the new columns 'inc_dis_dt_2300_dtp_code' and 'inc_dis_dt_2300_dtp_value' are shown with the field 'Include Discharge Date In Statement To Date (2300-DTP)' value,
  148. SYSTEM.file_import_gpbdt_i837
  149. SYSTEM.table_837_i_facility_prov_num
  150. Close the SQL query window.
Scenario 2: File Import - Guarantor Program Billing Defaults - New field validations
Specific Setup:
  • At least one 'Guarantor/Program Billing Defaults' template exists, "Template 1", and the 837 Professional and Institutional sections contain data.
  • Files can be saved to the local desktop, "File A", edited, and imported back into Avatar through 'File Import'.
  • Registry setting '837I-Dates To Populate 2300 DTP' value set as '1'.
Steps
  1. Open 'Guarantor/Program Billing Defaults'.
  2. Edit the ‘837 Institutional’ section of "Template 1".
  3. Validate that the new field has no values selected.
  4. Click [Submit].
  5. Export the template in 'Edit' mode, saving it to the desktop with a unique name "File A".
  6. Edit the 'Edit' mode template to have a value defined for piece 130- 'Include Discharge Date In Statement To Date (2300-DTP)' and save it.
  7. Open 'File Import'.
  8. Import/Compile/Post the 'Edit' mode template "File A" in the 'Guarantor/Program Billing Defaults Template' file type.
  9. Select 'Print File'.
  10. Print the file posted in step 8 by selecting it and clicking 'Process Action'.
  11. Validate that the Crystal report is included with the new field 'Include Discharge Date In Statement To Date (2300-DTP)' and it's value we selected in step 6 for file import for 837 Institutional.
  12. Open 'Guarantor/Program Billing Defaults'.
  13. Select 'Edit Template'.
  14. Select the 'Edit mode template', "Template 1".
  15. Select the ‘837 Professional’ section. The field, 'Include Discharge Date In Statement To Date (2300-DTP)' will have the value used in step 6.
  16. Click [Submit].
  17. Click [No].
Scenario 3: 837I Compile - With '837I-Dates To Populate 2300 DTP' RS 2
Specific Setup:
  • Guarantor:
  • An active guarantor is identified or created - "Guarantor 1".
  • Guarantor/Program Billing Defaults Template:
  • An active 'Guarantor/Program Billing Defaults' template is identified or created that includes "Guarantor 1" - "Template 1".
Steps
  1. Open the 'Registry Settings' form.
  2. Set the 'Limit Registry Settings to the Following Search Criteria' text input box to "837I-Dates To Populate 2300 DTP".
  3. Select 'Yes' in 'Include Hidden Registry Settings'.
  4. Click [View Registry Settings].
  5. Validate that the registry setting exists and show the respective values.
  6. Set the 'Registry Setting Value' field to '2'.
  7. Click [Submit].
  8. Click [OK].
  9. Click [No].
  10. Open the 'Guarantor/Program Billing Defaults' form.
  11. Select 'Edit Template'.
  12. Select "Template 1" from the 'Select Template' dropdown.
  13. Select '837 Institutional'.
  14. Validate that the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' is not shown.
  15. Click [Submit].
  16. Click [No].
  17. Open the 'Admission' form.
  18. Admit an Inpatient client - "Client 1".
  19. Using the 'Diagnosis' form, File an active diagnosis record for "Client 1".
  20. File the 'Financial Eligibility' form for "Client 1", with "Guarantor 1".
  21. Specify the 'Coverage Effective Date' and 'Coverage Expiration Date' in the financial eligibility.
  22. Create charges for "Client 1" for more than one date(s), that fall between the dates saved in step 21.
  23. Create a new Interim Billing Batch File "Batch 1" which covers the services created for "Client 1" in step 22.
  24. Close the charges using the Interim Billing Batch File "Batch 1".
  25. Open 'Client Ledger'.
  26. Select "Client 1" and the respective Episode.
  27. Validate that all the services are closed.
  28. Open 'Electronic Billing'.
  29. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  30. Set 'First Date Of Service To Include' with the date earlier than the 'Coverage Effective Date' filed in step 21.
  31. Set 'Last Date Of Service To Include' with a date later than the 'Coverage Expiration Date' filed in step 21.
  32. Click [Process].
  33. Validate that the compile completes successfully.
  34. Click [OK].
  35. Select 'Dump File' from 'Billing Options'.
  36. Select 'Print' from 'Print Or Delete Report'.
  37. Select the file compiled in step 31.
  38. Click [Process].
  39. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the 'Coverage Effective date' filed in step 21 and the 'Last Date Of Service To Include' selected in step 29(b).
  40. Close the report.
  41. Click [No].
  42. Open 'Discharge' form.
  43. Set the 'Date Of Discharge' field to a date that is greater than the 'Coverage Expiration Date' filed in step 21.
  44. Fill in all the required fields and select [Submit].
  45. Open 'Electronic Billing'.
  46. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  47. Set 'First Date Of Service To Include' with the date earlier than the 'Coverage Effective Date' filed in step 21.
  48. Set 'Last Date Of Service To Include' with a date later than the 'Coverage Expiration Date' filed in step 21.
  49. Click [Process].
  50. Validate that the compile completes successfully.
  51. Click [OK].
  52. Select 'Dump File' from 'Billing Options'.
  53. Select 'Print' from 'Print Or Delete Report'.
  54. Select the file compiled in step 46.
  55. Click [Process].
  56. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the 'Coverage Effective Date' and 'Coverage Expiration Date' filed in step 21.
  57. Close the report.
  58. Click [No].
  59. Open 'Electronic Billing'.
  60. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  61. Set 'First Date Of Service To Include' with the date later than the 'Coverage Effective Date' filed in step 21.
  62. Set 'Last Date Of Service To Include' with a date earlier than the 'Coverage Expiration Date' filed in step 21.
  63. Click [Process].
  64. Validate that the compile completes successfully.
  65. Click [OK].
  66. Select 'Dump File' from 'Billing Options'.
  67. Select 'Print' from 'Print Or Delete Report'.
  68. Select the file compiled in step 46.
  69. Click [Process].
  70. Validate that the discharge date is not included instead, the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the First Date Of Service To Include' and 'Last Date Of Service To Include' dates used in the step 57(a, b).
  71. Close the report.
  72. Click [No].
Scenario 4: "Restrict Coverage Effective Date Edits to Prior Dates Only" registry setting functionality
Specific Setup:
  • Client: The client should be admitted and have an active episode - "Client A".
  • Financial Eligibility: "Client A" should have an already existing Financial Eligibility record with both Coverage Effective and Expiration dates.
Steps
  1. Open the 'Registry Settings' form.
  2. Set the 'Limit Registry Settings to the Following Search Criteria' to 'Restrict Coverage Effective Date Edits to Prior Dates Only'.
  3. Click [View Registry Settings].
  4. Validate that the respective registry setting shows up.
  5. Set the 'Avatar PM->Billing->Financial Eligibility->->->Restrict Coverage Effective Date Edits to Prior Dates Only' registry setting to a value other than 'Y' or 'N'.
  6. Verify an error message displays that the valid choices are 'Y or N' only.
  7. Set the 'Avatar PM->Billing->Financial Eligibility->->->Restrict Coverage Effective Date Edits to Prior Dates Only' registry setting to 'Y' and then submit to save.
  8. Open the 'Financial Eligibility' form.
  9. Search and select "Client A".
  10. Select the Episode from the grid.
  11. Select 'Guarantor Selection'.
  12. Check if the 'Coverage Effective Date' field is already showing the date in the file.
  13. Try to enter a date that is after the date that is already in the file and move away from the field.
  14. Validate that an error message appears when updating the 'Coverage Effective Date' field to a date that is later than the previously filed date.
  15. Validate the error text - 'The Coverage Effective Date cannot be updated to be later than the previously filed date.'.
  16. Click [OK].
  17. Validate that the 'Coverage Effective Date' field is restored with the last value saved.
  18. Set 'Coverage Effective Date' with a date that is before the date that is already in the file and move away from the field.
  19. Validate that there are no errors shown.
  20. Click [Submit].
  21. Open the 'Financial Eligibility' form.
  22. Search and select "Client A".
  23. Select the Episode from the grid.
  24. Select 'Guarantor Selection'.
  25. Check if the 'Coverage Effective Date' field is showing with the date we save in step 18.
  26. Click [Discard].
  27. Click [Yes].
  28. Open the 'Registry Settings' form.
  29. Set the 'Limit Registry Settings to the Following Search Criteria' to 'Restrict Coverage Effective Date Edits to Prior Dates Only'.
  30. Click [View Registry Settings].
  31. Set the 'Avatar PM->Billing->Financial Eligibility->->->Restrict Coverage Effective Date Edits to Prior Dates Only' registry setting to 'N' and then submit to save.
  32. Open the 'Financial Eligibility' form.
  33. Search and select "Client A".
  34. Select the Episode from the grid.
  35. Select 'Guarantor Selection'.
  36. Check if the 'Coverage Effective Date' field is showing with the date we save in step 18.
  37. Try to enter a date that is after the date that is already in the file and move away from the field.
  38. Validate that there are no errors shown.
  39. Click [Submit].
  40. Open the 'Financial Eligibility' form.
  41. Search and select "Client A".
  42. Select the Episode from the grid.
  43. Select 'Guarantor Selection'.
  44. Check if the 'Coverage Effective Date' field is showing with the date we save in step 37.
  45. Click [Discard].
  46. Click [Yes].
Registry Setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Financial Eligibility
  • Electronic Billing
  • Discharge
  • File Import
Scenario 1: 837I Compile - With '837I-Dates To Populate 2300 DTP' RS 1
Specific Setup:
  • Guarantor:
  • An active guarantor is identified or created - "Guarantor 1".
  • Guarantor/Program Billing Defaults Template:
  • An active 'Guarantor/Program Billing Defaults' template is identified or created that includes "Guarantor 1" - "Template 1".
Steps
  1. Open the 'Registry Settings' form.
  2. Set the 'Limit Registry Settings to the Following Search Criteria' text input box to "837I-Dates To Populate 2300 DTP".
  3. Select 'Yes' in 'Include Hidden Registry Settings'.
  4. Click [View Registry Settings].
  5. Validate that the registry setting exists and show the respective values.
  6. Set the 'Registry Setting Value' field to '1'.
  7. Click [Submit].
  8. Click [OK].
  9. Click [No].
  10. Open the 'Guarantor/Program Billing Defaults' form.
  11. Select 'Edit Template'.
  12. Select "Template 1" from the 'Select Template' dropdown.
  13. Select '837 Institutional'.
  14. Validate that the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' is shown with the following options, (none selected by default):
  15. Yes (Inpatient/Outpatient)
  16. Yes (Outpatient Only)
  17. Yes (Inpatient Only)
  18. No (Inpatient/Outpatient)
  19. Click [Submit].
  20. Click [No].
  21. Open the 'Admission' form.
  22. Admit an Inpatient client - "Client 1".
  23. Using the 'Diagnosis' form, File an active diagnosis record for "Client 1".
  24. File the 'Financial Eligibility' form for "Client 1", with "Guarantor 1".
  25. Specify the 'Coverage Effective Date' and 'Coverage Expiration Date' in the financial eligibility.
  26. Create charges for "Client 1" for more than one date, with the dates between the dates saved in step 21.
  27. Create a new Interim Billing Batch File, "Batch 1", which covers the services created for "Client 1" in step 22.
  28. Close the charges using the Interim Billing Batch File, "Batch 1".
  29. Open 'Client Ledger'.
  30. Select "Client 1" and the respective Episode.
  31. Validate that all the services are closed.
  32. Open 'Electronic Billing'.
  33. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  34. Set 'First Date Of Service To Include' with a date before the 'Coverage Effective Date' filed in step 21.
  35. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  36. Click [Process].
  37. Validate that the compile completes successfully.
  38. Click [OK].
  39. Select 'Dump File' from 'Billing Options'.
  40. Select 'Print' from 'Print Or Delete Report'.
  41. Select the file compiled in step 31.
  42. Click [Process].
  43. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first and last dates of the services being billed.
  44. Close the report.
  45. Click [No].
  46. Open 'Discharge' form.
  47. Set the 'Date Of Discharge' field to a date that is the day after the last day of service.
  48. Fill in all the required fields and select [Submit].
  49. Open 'Electronic Billing'.
  50. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  51. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  52. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  53. Click [Process].
  54. Validate that the compile completes successfully.
  55. Click [OK].
  56. Select 'Dump File' from 'Billing Options'.
  57. Select 'Print' from 'Print Or Delete Report'.
  58. Select the file compiled in step 46.
  59. Click [Process].
  60. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first date of the service being billed and the discharge date file in step 41.
  61. Close the report.
  62. Click [No].
  63. Open the 'Guarantor/Program Billing Defaults' form.
  64. Select 'Edit Template'.
  65. Select "Template 1" from the 'Select Template' dropdown.
  66. Select '837 Institutional'.
  67. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'Yes (Inpatient/Outpatient)'.
  68. Click [Submit].
  69. Click [No].
  70. Open 'Electronic Billing'.
  71. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  72. Set 'First Date Of Service To Include' a date before the 'Coverage Effective Date' filed in step 21.
  73. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  74. Click [Process].
  75. Validate that the compile completes successfully.
  76. Click [OK].
  77. Select 'Dump File' from 'Billing Options'.
  78. Select 'Print' from 'Print Or Delete Report'.
  79. Select the file compiled in step 65.
  80. Click [Process].
  81. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first date of the service being billed and the discharge date file in step 41.
  82. Close the report.
  83. Click [No].
  84. Open the 'Guarantor/Program Billing Defaults' form.
  85. Select 'Edit Template'.
  86. Select "Template 1" from the 'Select Template' dropdown.
  87. Select '837 Institutional'.
  88. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'Yes (Inpatient Only)'.
  89. Click [Submit].
  90. Click [No].
  91. Open 'Electronic Billing'.
  92. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  93. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  94. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  95. Click [Process].
  96. Validate that the compile completes successfully.
  97. Click [OK].
  98. Select 'Dump File' from 'Billing Options'.
  99. Select 'Print' from 'Print Or Delete Report'.
  100. Select the file compiled in step 85.
  101. Click [Process].
  102. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first date of the service being billed and the discharge date file in step 41.
  103. Close the report.
  104. Click [No].
  105. Open the 'Guarantor/Program Billing Defaults' form.
  106. Select 'Edit Template'.
  107. Select "Template 1" from the 'Select Template' dropdown.
  108. Select '837 Institutional'.
  109. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'Yes (Inpatient Only)'.
  110. Click [Submit].
  111. Click [No].
  112. Open 'Electronic Billing'.
  113. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  114. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  115. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  116. Click [Process].
  117. Validate that the compile completes successfully.
  118. Click [OK].
  119. Select 'Dump File' from 'Billing Options'.
  120. Select 'Print' from 'Print Or Delete Report'.
  121. Select the file compiled in step 105.
  122. Click [Process].
  123. Validate that the discharge date is not included instead, the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first and last dates of the services being billed.
  124. Close the report.
  125. Click [No].
  126. Open the 'Guarantor/Program Billing Defaults' form.
  127. Select 'Edit Template'.
  128. Select "Template 1" from the 'Select Template' dropdown.
  129. Select '837 Institutional'.
  130. Set the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' to 'No (Inpatient/Outpatient)'.
  131. Click [Submit].
  132. Click [No].
  133. Open 'Electronic Billing'.
  134. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  135. Set 'First Date Of Service To Include' with the date before the 'Coverage Effective Date' filed in step 21.
  136. Set ' Last Date Of Service To Include' with a date after the 'Coverage Expiration Date' filed in step 21.
  137. Click [Process].
  138. Validate that the compile completes successfully.
  139. Click [OK].
  140. Select 'Dump File' from 'Billing Options'.
  141. Select 'Print' from 'Print Or Delete Report'.
  142. Select the file compiled in step 105.
  143. Click [Process].
  144. Validate that the discharge date is not included instead, the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the first and last dates of the services being billed.
  145. Close the report.
  146. Click [No].
  147. Query the tables below and validate that the new columns 'inc_dis_dt_2300_dtp_code' and 'inc_dis_dt_2300_dtp_value' are shown with the field 'Include Discharge Date In Statement To Date (2300-DTP)' value,
  148. SYSTEM.file_import_gpbdt_i837
  149. SYSTEM.table_837_i_facility_prov_num
  150. Close the SQL query window.
Scenario 2: File Import - Guarantor Program Billing Defaults - New field validations
Specific Setup:
  • At least one 'Guarantor/Program Billing Defaults' template exists, "Template 1", and the 837 Professional and Institutional sections contain data.
  • Files can be saved to the local desktop, "File A", edited, and imported back into Avatar through 'File Import'.
  • Registry setting '837I-Dates To Populate 2300 DTP' value set as '1'.
Steps
  1. Open 'Guarantor/Program Billing Defaults'.
  2. Edit the ‘837 Institutional’ section of "Template 1".
  3. Validate that the new field has no values selected.
  4. Click [Submit].
  5. Export the template in 'Edit' mode, saving it to the desktop with a unique name "File A".
  6. Edit the 'Edit' mode template to have a value defined for piece 130- 'Include Discharge Date In Statement To Date (2300-DTP)' and save it.
  7. Open 'File Import'.
  8. Import/Compile/Post the 'Edit' mode template "File A" in the 'Guarantor/Program Billing Defaults Template' file type.
  9. Select 'Print File'.
  10. Print the file posted in step 8 by selecting it and clicking 'Process Action'.
  11. Validate that the Crystal report is included with the new field 'Include Discharge Date In Statement To Date (2300-DTP)' and it's value we selected in step 6 for file import for 837 Institutional.
  12. Open 'Guarantor/Program Billing Defaults'.
  13. Select 'Edit Template'.
  14. Select the 'Edit mode template', "Template 1".
  15. Select the ‘837 Professional’ section. The field, 'Include Discharge Date In Statement To Date (2300-DTP)' will have the value used in step 6.
  16. Click [Submit].
  17. Click [No].
Scenario 3: 837I Compile - With '837I-Dates To Populate 2300 DTP' RS 2
Specific Setup:
  • Guarantor:
  • An active guarantor is identified or created - "Guarantor 1".
  • Guarantor/Program Billing Defaults Template:
  • An active 'Guarantor/Program Billing Defaults' template is identified or created that includes "Guarantor 1" - "Template 1".
Steps
  1. Open the 'Registry Settings' form.
  2. Set the 'Limit Registry Settings to the Following Search Criteria' text input box to "837I-Dates To Populate 2300 DTP".
  3. Select 'Yes' in 'Include Hidden Registry Settings'.
  4. Click [View Registry Settings].
  5. Validate that the registry setting exists and show the respective values.
  6. Set the 'Registry Setting Value' field to '2'.
  7. Click [Submit].
  8. Click [OK].
  9. Click [No].
  10. Open the 'Guarantor/Program Billing Defaults' form.
  11. Select 'Edit Template'.
  12. Select "Template 1" from the 'Select Template' dropdown.
  13. Select '837 Institutional'.
  14. Validate that the new field, 'Include Discharge Date In Statement To Date (2300-DTP)' is not shown.
  15. Click [Submit].
  16. Click [No].
  17. Open the 'Admission' form.
  18. Admit an Inpatient client - "Client 1".
  19. Using the 'Diagnosis' form, File an active diagnosis record for "Client 1".
  20. File the 'Financial Eligibility' form for "Client 1", with "Guarantor 1".
  21. Specify the 'Coverage Effective Date' and 'Coverage Expiration Date' in the financial eligibility.
  22. Create charges for "Client 1" for more than one date(s), that fall between the dates saved in step 21.
  23. Create a new Interim Billing Batch File "Batch 1" which covers the services created for "Client 1" in step 22.
  24. Close the charges using the Interim Billing Batch File "Batch 1".
  25. Open 'Client Ledger'.
  26. Select "Client 1" and the respective Episode.
  27. Validate that all the services are closed.
  28. Open 'Electronic Billing'.
  29. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  30. Set 'First Date Of Service To Include' with the date earlier than the 'Coverage Effective Date' filed in step 21.
  31. Set 'Last Date Of Service To Include' with a date later than the 'Coverage Expiration Date' filed in step 21.
  32. Click [Process].
  33. Validate that the compile completes successfully.
  34. Click [OK].
  35. Select 'Dump File' from 'Billing Options'.
  36. Select 'Print' from 'Print Or Delete Report'.
  37. Select the file compiled in step 31.
  38. Click [Process].
  39. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the 'Coverage Effective date' filed in step 21 and the 'Last Date Of Service To Include' selected in step 29(b).
  40. Close the report.
  41. Click [No].
  42. Open 'Discharge' form.
  43. Set the 'Date Of Discharge' field to a date that is greater than the 'Coverage Expiration Date' filed in step 21.
  44. Fill in all the required fields and select [Submit].
  45. Open 'Electronic Billing'.
  46. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  47. Set 'First Date Of Service To Include' with the date earlier than the 'Coverage Effective Date' filed in step 21.
  48. Set 'Last Date Of Service To Include' with a date later than the 'Coverage Expiration Date' filed in step 21.
  49. Click [Process].
  50. Validate that the compile completes successfully.
  51. Click [OK].
  52. Select 'Dump File' from 'Billing Options'.
  53. Select 'Print' from 'Print Or Delete Report'.
  54. Select the file compiled in step 46.
  55. Click [Process].
  56. Validate that the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the 'Coverage Effective Date' and 'Coverage Expiration Date' filed in step 21.
  57. Close the report.
  58. Click [No].
  59. Open 'Electronic Billing'.
  60. Run the '837-Institutional' bill for the Interim Billing "Batch 1", for "Guarantor 1".
  61. Set 'First Date Of Service To Include' with the date later than the 'Coverage Effective Date' filed in step 21.
  62. Set 'Last Date Of Service To Include' with a date earlier than the 'Coverage Expiration Date' filed in step 21.
  63. Click [Process].
  64. Validate that the compile completes successfully.
  65. Click [OK].
  66. Select 'Dump File' from 'Billing Options'.
  67. Select 'Print' from 'Print Or Delete Report'.
  68. Select the file compiled in step 46.
  69. Click [Process].
  70. Validate that the discharge date is not included instead, the Statement From and To Date in the 2300-DTP-03 segment of the 837 Institutional file is overridden by the First Date Of Service To Include' and 'Last Date Of Service To Include' dates used in the step 57(a, b).
  71. Close the report.
  72. Click [No].
Scenario 4: "Restrict Coverage Effective Date Edits to Prior Dates Only" registry setting functionality
Specific Setup:
  • Client: The client should be admitted and have an active episode - "Client A".
  • Financial Eligibility: "Client A" should have an already existing Financial Eligibility record with both Coverage Effective and Expiration dates.
Steps
  1. Open the 'Registry Settings' form.
  2. Set the 'Limit Registry Settings to the Following Search Criteria' to 'Restrict Coverage Effective Date Edits to Prior Dates Only'.
  3. Click [View Registry Settings].
  4. Validate that the respective registry setting shows up.
  5. Set the 'Avatar PM->Billing->Financial Eligibility->->->Restrict Coverage Effective Date Edits to Prior Dates Only' registry setting to a value other than 'Y' or 'N'.
  6. Verify an error message displays that the valid choices are 'Y or N' only.
  7. Set the 'Avatar PM->Billing->Financial Eligibility->->->Restrict Coverage Effective Date Edits to Prior Dates Only' registry setting to 'Y' and then submit to save.
  8. Open the 'Financial Eligibility' form.
  9. Search and select "Client A".
  10. Select the Episode from the grid.
  11. Select 'Guarantor Selection'.
  12. Check if the 'Coverage Effective Date' field is already showing the date in the file.
  13. Try to enter a date that is after the date that is already in the file and move away from the field.
  14. Validate that an error message appears when updating the 'Coverage Effective Date' field to a date that is later than the previously filed date.
  15. Validate the error text - 'The Coverage Effective Date cannot be updated to be later than the previously filed date.'.
  16. Click [OK].
  17. Validate that the 'Coverage Effective Date' field is restored with the last value saved.
  18. Set 'Coverage Effective Date' with a date that is before the date that is already in the file and move away from the field.
  19. Validate that there are no errors shown.
  20. Click [Submit].
  21. Open the 'Financial Eligibility' form.
  22. Search and select "Client A".
  23. Select the Episode from the grid.
  24. Select 'Guarantor Selection'.
  25. Check if the 'Coverage Effective Date' field is showing with the date we save in step 18.
  26. Click [Discard].
  27. Click [Yes].
  28. Open the 'Registry Settings' form.
  29. Set the 'Limit Registry Settings to the Following Search Criteria' to 'Restrict Coverage Effective Date Edits to Prior Dates Only'.
  30. Click [View Registry Settings].
  31. Set the 'Avatar PM->Billing->Financial Eligibility->->->Restrict Coverage Effective Date Edits to Prior Dates Only' registry setting to 'N' and then submit to save.
  32. Open the 'Financial Eligibility' form.
  33. Search and select "Client A".
  34. Select the Episode from the grid.
  35. Select 'Guarantor Selection'.
  36. Check if the 'Coverage Effective Date' field is showing with the date we save in step 18.
  37. Try to enter a date that is after the date that is already in the file and move away from the field.
  38. Validate that there are no errors shown.
  39. Click [Submit].
  40. Open the 'Financial Eligibility' form.
  41. Search and select "Client A".
  42. Select the Episode from the grid.
  43. Select 'Guarantor Selection'.
  44. Check if the 'Coverage Effective Date' field is showing with the date we save in step 37.
  45. Click [Discard].
  46. Click [Yes].

Topics
• Electronic Billing • Guarantor/Program Billing Defaults • File Import • Registry Settings • Financial Eligibility • Web Services
2023 Update 76 Summary | Details
835 Health Care Claim Payment/Advice
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission (Outpatient)
  • Financial Eligibility
  • Electronic Billing
  • Claim Adjustment Group/Reason Code Definition
  • 835 Health Care Claim Payment/Advice (PM)
Scenario 1: '835 Health Care Claim Payment/Advice' - Files with and without end of segment separator
Specific Setup:
  • 835 Health Care Claim Payment/Advice:
  • An 835 file exists where each segment has its own row, with no end of row separators. Note the client(s) that will have payments/adjustments made and the services the payments will be made to.
  • An 835 file exists where each segment has end of row separators. Note the client(s) that will have payments/adjustments made and the services the payments will be made to.
  • The files have been placed in the appropriate directory for processing as setup in 'Facility Defaults'.
Steps
  1. Open Avatar PM '835 Health Care Claim Payment/Advice' form.
  2. Load, compile and post each file.
  3. Close the form.
  4. Open 'Client Ledger' to validate that the payments/adjustment were posted to the client's ledger appropriately.
  5. Close the form.

Topics
• 835 Health Care Claim Payment/Advice
2023 Update 81 Summary | Details
Avatar Cal-PM 'Cal-OMS...' Forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Cal-OMS Discharge
  • Cal-OMS Youth/Detox Discharge
  • Cal-OMS Administrative Discharge
  • Cal-OMS Annual Update
Scenario 1: Avatar Cal-PM Registry Settings - Verification of 'Do Not Allow User To Continue Filing With Errors' Registry Setting
Steps
  1. Open 'Registry Settings' form.
  2. Enter search value 'Do Not Allow User To Continue Filing' and click 'View Registry Settings' button.
  3. Ensure Registry Setting 'Do Not Allow User To Continue Filing With Errors' is returned (under 'Avatar PM-> California Required EDI -> CAL OMS Reporting' path).
  4. Ensure 'Registry Setting Details' field contains the following explanation text:


Modify the Cal-OMS Admission, Cal-OMS Annual Update, Cal-OMS Discharge, Cal-OMS Youth/Detox Discharge, Cal-OMS Administrative Discharge, Outside Provider Cal-OMS Admission, Outside Provider Cal-OMS Annual Update, Outside Provider Cal-OMS Discharge, Outside Provider Cal-OMS Administrative Discharge forms to return hard error rather than giving the following choices: "Continue Filing" and "Return to Form".

Scenario 2: 'Cal-OMS Admission' - Verification of 'Do Not Allow User To Continue Filing With Errors' Registry Setting
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Do Not Allow User To Continue Filing With Errors' may optionally be enabled/disabled
  • 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 'Cal-OMS Admission' form fields as required/desired (ensuring that at least one field is incomplete/no value entered or selected).
  4. Click 'Submit' button to file 'Cal-OMS Admission' form/record.
  5. Where Registry Setting 'Do Not Allow User To Continue Filing With Errors' is disabled (value 'N', system default) - In case where one or more 'Cal-OMS Admission' fields is incomplete/no value entered or selected, ensure that user is presented with warning dialog noting incomplete fields (or 'There are more than 10 empty fields' message), along with 'Continue Filing' and 'Return to Form' buttons.
  6. Ensure that clicking 'Continue Filing' button files 'Cal-OMS Admission' form/record with incomplete fields
  7. Ensure that clicking 'Return to Form' button cancels filing and returns user to 'Cal-OMS Admission' form/record without filing (for further entry/selection of field values prior to filing)
  8. Where Registry Setting 'Do Not Allow User To Continue Filing With Errors' is enabled (value 'Y') - In case where one or more 'Cal-OMS Admission' fields is incomplete/no value entered or selected, ensure that user is presented with filing error dialog noting incomplete fields (or 'There are more than 10 empty fields' message), with single 'OK' button to close error dialog/return to form.
  9. Ensure that clicking 'OK' button closes error dialog/cancels filing, and user is returned to 'Cal-OMS Admission' form to complete all field entries prior to form/record filing
Scenario 3: 'Cal-OMS Discharge' - Verification of 'Do Not Allow User To Continue Filing With Errors' Registry Setting
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Do Not Allow User To Continue Filing With Errors' may optionally be enabled/disabled
  • Client record eligible for Cal-OMS Discharge record entry/edit
Steps
  1. Open Avatar Cal-PM 'Cal-OMS Discharge', 'Cal-OMS Youth/Detox Discharge' or 'Cal-OMS Administrative Discharge' form.
  2. Select client/episode for Cal-OMS Discharge entry (or select existing Cal-OMS Discharge record for view/edit).
  3. Enter/select values for 'Cal-OMS Discharge' form fields as required/desired (ensuring that at least one field is incomplete/no value entered or selected).
  4. Click 'Submit' button to file 'Cal-OMS Discharge' form/record.
  5. Where Registry Setting 'Do Not Allow User To Continue Filing With Errors' is disabled (value 'N', system default) - In case where one or more 'Cal-OMS Discharge' fields is incomplete/no value entered or selected, ensure that user is presented with warning dialog noting incomplete fields (or 'There are more than 10 empty fields' message), along with 'Continue Filing' and 'Return to Form' buttons.
  6. Ensure that clicking 'Continue Filing' button files 'Cal-OMS Discharge' form/record with incomplete fields
  7. Ensure that clicking 'Return to Form' button cancels filing and returns user to 'Cal-OMS Discharge' form/record without filing (for further entry/selection of field values prior to filing)
  8. Where Registry Setting 'Do Not Allow User To Continue Filing With Errors' is enabled (value 'Y') - In case where one or more 'Cal-OMS Discharge' fields is incomplete/no value entered or selected, ensure that user is presented with filing error dialog noting incomplete fields (or 'There are more than 10 empty fields' message), with single 'OK' button to close error dialog/return to form.
  9. Ensure that clicking 'OK' button closes error dialog/cancels filing, and user is returned to 'Cal-OMS Discharge' form to complete all field entries prior to form/record filing
Scenario 4: 'Cal-OMS Annual Update' - Verification of 'Do Not Allow User To Continue Filing With Errors' Registry Setting
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Do Not Allow User To Continue Filing With Errors' may optionally be enabled/disabled
  • Client record eligible for Cal-OMS Annual Update record entry/edit
Steps
  1. Open Avatar Cal-PM 'Cal-OMS Annual Update' form.
  2. Select client/episode for Cal-OMS Annual Update entry (or select existing Cal-OMS Annual Update record for view/edit).
  3. Enter/select values for 'Cal-OMS Annual Update' form fields as required/desired (ensuring that at least one field is incomplete/no value entered or selected).
  4. Click 'Submit' button to file 'Cal-OMS Annual Update' form/record.
  5. Where Registry Setting 'Do Not Allow User To Continue Filing With Errors' is disabled (value 'N', system default) - In case where one or more 'Cal-OMS Annual Update' fields is incomplete/no value entered or selected, ensure that user is presented with warning dialog noting incomplete fields (or 'There are more than 10 empty fields' message), along with 'Continue Filing' and 'Return to Form' buttons.
  6. Ensure that clicking 'Continue Filing' button files 'Cal-OMS Annual Update' form/record with incomplete fields
  7. Ensure that clicking 'Return to Form' button cancels filing and returns user to 'Cal-OMS Annual Update' form/record without filing (for further entry/selection of field values prior to filing)
  8. Where Registry Setting 'Do Not Allow User To Continue Filing With Errors' is enabled (value 'Y') - In case where one or more 'Cal-OMS Annual Update' fields is incomplete/no value entered or selected, ensure that user is presented with filing error dialog noting incomplete fields (or 'There are more than 10 empty fields' message), with single 'OK' button to close error dialog/return to form.
  9. Ensure that clicking 'OK' button closes error dialog/cancels filing, and user is returned to 'Cal-OMS Annual Update' form to complete all field entries prior to form/record filing

Topics
• Registry Settings • Cal-OMS
2023 Update 83 Summary | Details
Web Service - Add Admission
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. Click [Run].
  20. Validate the 'Confirmation' field contains a value such as: "Client Unique ID: # Unique ID: #".
  21. Validate the 'Message' field contains: "Client Admission web service has been filed successfully".
  22. Select the client filed in the previous steps and access the 'Admission' form.
  23. Select the record filed in the previous steps and click [Edit].
  24. Validate all populated fields are displayed.
  25. Select the "Demographics" section.
  26. Validate the 'Client Last Name' field contains the value filed in the previous steps.
  27. Validate the 'Client First Name' field contains the value filed in the previous steps.
  28. Validate the 'Client Middle Name' field contains the value filed in the previous steps.
  29. Validate the 'Consent On File For Use of Integrated eSignature' field contains the value filed in the previous steps.
  30. Validate 'Time Zone for Appointment Reminders' field contains the value filed in the previous steps.
  31. Validate the 'Preferred Appointment Site' field contains the value filed in the previous steps.
  32. Validate the 'Address Type' field contains the value filed in the previous steps.
  33. Close the form.
File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • File Import
Scenario 1: 'File Import' - Verification of 'Guarantor/Program Billing Defaults Template' Import
Specific Setup:
  • Avatar PM Registry Setting 'Enable Pricing/Re-Pricing Information' must be enabled/set to value '2' or '3'
  • Avatar PM 'Guarantor/Program Billing Defaults Template' import file containing one or more valid '837 Professional' and/or '837 Institutional' import data rows (Updated import file layout document 'Avatar_PM_File_Import_Record_Layouts.xls' included with update package)
  • Crystal Reports or other SQL reporting tool
Steps
  1. Open Avatar PM 'File Import' form.
  2. Select File Type 'Guarantor/Program Billing Defaults Template'.
  3. Select 'Upload New File' in the 'Action' field and Click 'Process Action' button.
  4. Select Avatar PM 'Guarantor/Program Billing Defaults Template' import file and click 'Open' button.
  5. Select 'Compile/Validate File' in 'Action' field.
  6. Select loaded import file and click 'Process Action' button.
  7. Ensure that 'Compile/Validate File' action completes, and message 'Compiled' or '(File Name) contains one or more errors. These errors can be reviewed using 'Print Errors' action' is displayed.
  8. Click 'OK' button.
  9. Select 'Post File' in 'Action' field to post successfully compiled import data; Select compiled import file, but don't post.
  10. Open another "File Import" form.
  11. Select File Type 'Guarantor/Program Billing Defaults Template'.
  12. Select 'Post File'.
  13. Select the same File from Step 9 to Post.
  14. Select 'Process Action'.
  15. Validate import completes without error.
  16. Select 'Discard'.
  17. Open the File Import form which we first kept opened in Step 9.
  18. Ensure that message 'Posted' and/or 'The selected file contains one or more lines with compilation errors. Only those lines without compilation errors will be posted' is displayed.
  19. Open Avatar PM 'Guarantor/Program Billing Defaults' form.
  20. Select 'Edit Template' and select existing Defaults Template added/updated via 'File Import'.
  21. Navigate to '837 Professional' section of form.
  22. Ensure values for the following fields from 837 Professional 'Guarantor/Program Billing Defaults Template' import file data row are present in 837 Professional defaults section of 'Guarantor/Program Billing Defaults' form:
  23. 'Provider Taxonomy Code to Display (2000A-PRV-03)'
  24. 'Billing Provider Tax ID to Display (2010AA-REF-02)'
  25. 'Include Repricer Received Date (2300-DTP)'
  26. 'Default Total Claim Charge Amount (2300-HCP-02)'
  27. 'Default Cost of Service/Units (2400-HCP-02/11/12)'
  28. Navigate to '837 Institutional' section of form.
  29. Ensure values for the following fields from 837 Institutional 'Guarantor/Program Billing Defaults Template' import file data row are present in 837 Institutional defaults section of 'Guarantor/Program Billing Defaults' form:
  30. 'Provider Taxonomy Code to Display (2000A-PRV-03)'
  31. 'Billing Provider Tax ID to Display (2010AA-REF-02)'
  32. 'Include Repricer Received Date (2300-DTP)'
  33. 'Default Total Claim Charge Amount (2300-HCP-02)'
  34. 'Default Cost of Service/Units (2400-HCP-02/11/12)'
  35. Open Crystal Reports or other SQL reporting tool.
  36. In Avatar PM SQL table 'SYSTEM.file_import_gpbdt_p837', ensure that the following fields are present and contain values filed via 837 Professional 'Guarantor/Program Billing Defaults Template' File Import:
  37. prov_taxon_to_disp_code / prov_taxon_to_disp_value
  38. prov_taxid_to_disp_code / prov_taxid_to_disp_value
  39. inc_repric_rec_date_code / inc_repric_rec_date_value
  40. def_tot_clm_chg_amt_code / def_tot_clm_chg_amt_value
  41. def_cost_svc_units_code / def_cost_svc_units_value
  42. In Avatar PM SQL table 'SYSTEM.file_import_gpbdt_i837', ensure that the following fields are present and contain values filed via 837 Institutional 'Guarantor/Program Billing Defaults Template' File Import:
  43. prov_taxon_to_disp_code / prov_taxon_to_disp_value
  44. prov_taxid_to_disp_code / prov_taxid_to_disp_value
  45. inc_repric_rec_date_code / inc_repric_rec_date_value
  46. def_tot_clm_chg_amt_code / def_tot_clm_chg_amt_value
  47. def_cost_svc_units_code / def_cost_svc_units_value
Scenario 2: File Import - Validate Client Charge Input File Import
Specific Setup:
  • A Client Charge Input File Import file must be created to test with. In the file, record units of service (field 11) as 1:00.
Steps
  1. Open the "File Import" form.
  2. Import the file set up in pre-conditions.
  3. The following error message is received. "File XXX.txt contains one or more errors. These errors can be reviewed using the "Print Errors" action.".
  4. Manually modify the sample import file. Change the units of service field (field 11) to "1.00".
  5. Import the file.
  6. Validate import completes without error.
  7. Manually modify the sample import file. Change the units of service field (field 11) to "1".
  8. Compile the file.
  9. Select the File to Post, but don't post.
  10. Open another "File Import" form.
  11. Select the "Client Charge Input" in the File type.
  12. Select "Post File".
  13. Select the same File from Step 9 to Post.
  14. Select "Process Action".
  15. Validate import completes without error.
  16. Select "Discard".
  17. Open the File Import form which we first kept opened in Step 9.
  18. Select "Process Action".
  19. Validate import is not happening with the same file that is already imported.
  20. Validate that we get the error message saying, "File is already posted." with the "OK" button.
  21. Select "OK".
  22. Open "Client Ledger".
  23. Run the report.
  24. Validate that the service(s) were added to the client's ledger and there are no duplicates added for the same date(s).

Topics
• Admission • Web Services • File Import • Guarantor / Program Billing Defaults • Client Charge Input
2023 Update 88 Summary | Details
CSI Submission - Delete Last Movement
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
  • Admission (Outpatient)
  • CSI Submission
  • Delete Last Movement
Scenario 1: CSI Submission - Delete Last Movement - CSI Assessment on client with episode and without episode
Specific Setup:
  • Program Maintenance:
  • Create a new program or identify an existing admit program setup as a ‘Mental Health Program (CSI)’. Note the program code/value.
  • Create a new program or identify an existing call intake program setup as a ‘Mental Health Program (CSI)’. Note the program code/value.
  • Admission:
  • An existing client is identified that have no prior CSI Assessment record on file or the new client is admitted to a CSI program created/identified above. Note the client's id/ name.
  • Call Intake:
  • A client is admitted to a temporary episode in the 'Call Intake' form. Note the client's id/ name.
  • CSI Assessment:
  • The CSI Assessment records are created for the client admitted through admission form and call intake form.
  • The 'Include CSI Submission' field is set to 'Yes'.
  • The location to store CSI submission files is defined in the Facility Defaults form (Output Path On Server For Electronic Billing field).
Steps
  1. Open the 'CSI Submission' form.
  2. Select 'Compile' in the 'Option' field. This file includes all clients who have been admitted in the CSI Admission form.
  3. Verify that the 'From Date' auto populates based on the through date of the last submitted CSI file.
  4. In the 'Through Date' field, enter the last date to include in the compiled file. Note: The through date must be the last date of the month and must be before today's date.
  5. Submit the file.
  6. Verify that the submission completed successfully.
  7. Select 'Submit' option to create the CSI file.
  8. Select the CSI file in the 'Select File to Print/Submit' field.
  9. Select 'Review' in the 'Create File' field.
  10. Select 'Submit' to create the CSI file.
  11. Verify the form submitted successfully and a dialog displays that contains the file name and storage location.
  12. Locate the CSI Submission file and review the contents for desired client/row.
  13. Verify that both the records contain 400 characters.
  14. Open the 'Delete Last Movement' form.
  15. Select desired client admitted through admission form and an existing episode for the client.
  16. Delete the admission movement for the client.
  17. Submit the form.
  18. Open the 'Delete Client' form.
  19. Select desired client admitted through 'Call Intake' form.
  20. Delete the call intake movement for the client.
  21. Submit the form.
  22. Open the 'CSI Submission' form.
  23. Select 'Compile' in the 'Option' field.
  24. Verify that the 'From Date' auto populates.
  25. In the 'Through Date' field, enter the last date to include in the compiled file. Note: The through date must be the last date of the month and must be before today's date.
  26. Submit the file.
  27. Verify that the submission completed successfully.

Topics
• CSI Submission
2023 Update 89 Summary | Details
Service Codes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Code Upload Process
  • Service Code Upload Accepted Codes (2)
  • Service Code Upload Rejected Codes (2)
  • Admission (Outpatient)
  • Dictionary Update (PM)
  • Financial Eligibility
  • Electronic Billing
  • Progress Notes (Group and Individual)
  • Program Maintenance
  • Site Specific Section Modeling (CWS)
Scenario 1: Service code upload process - Validating compile/post file
Specific Setup:
  • The following text files are created to upload the service code in the system with the value of new field 'Should Add-On Services Generate for Co-Practitioners for this Service Code?'. Note the file name and location of the file.
  • The file to upload the add-on code with the value 'Y' for the field. (i.e. Name of the file File1).
  • The file to upload the add-on code with the value 'N' for the field. (i.e. Name of the file File2).
  • The file to upload the add-on code without any value selected for the field. (i.e. Name of the file File3).
  • The file to upload the primary code with the value 'Y' for the field. (i.e. Name of the file File5).
  • The file to upload the primary code with the value 'Y' for the field. (i.e. Name of the file File6).
  • The file to upload the primary code without any value for the field. (i.e. Name of the file File7).
Steps
  1. Open the 'Service Code Upload Process' form.
  2. Click [Select File].
  3. Select File1 created in the setup.
  4. Select 'Compile' in the 'Compile Or Post' field.
  5. Select 'No' in the 'Override Existing Service Codes' field.
  6. Submit the form.
  7. Verify the message: "Compile completed. To View results review accepted reports".
  8. Click [OK].
  9. Open the 'Service Code Upload Accepted Codes' form without exiting out from the 'Service Code Upload Process' form.
  10. Click the drop down for the 'Select Desired service code import file name' field.
  11. Verify the recently compiled file displays in the drop down.
  12. Select the file.
  13. Click [Process].
  14. Verify the report launched successfully and all the data displays correctly as listed in the texted file.
  15. Close the report.
  16. Close the 'Service Code Upload Accepted Codes' form.
  17. Locate to the 'Service Code Upload Process' form
  18. Select 'Post' in the 'Compile Or Post' field.
  19. Verify the file posted successfully.
  20. Open the 'Service Code' form.
  21. Select the recently uploaded service code to edit.
  22. Verify the field 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' is set to desired value defined in the text file.
  23. Close the form.
  24. Repeat steps 1 through 20 for the File1, File2, File3, and File7.
  25. Run the query to retrieve data from the 'SYSTEM.batchload_tx_accepted' sql table.
  26. Verify the 'generate_add_on_services_code' and 'generate_add_on_services_value' are added in the table.
  27. Open the 'Service Code Upload Process' form.
  28. Click [Select File].
  29. Select File5 created in the setup.
  30. Select 'Compile' in the 'Compile Or Post' field.
  31. Select 'No' in the 'Override Existing Service Codes' field.
  32. Submit the form.
  33. Verify that the file should not be compiled successfully.
  34. Verify the message: 'No accepted data compiled. To view results review rejected report'.
  35. Click [OK].
  36. Open the 'Service Code Upload Rejected Codes' form without exiting out from the 'Service Code Upload Process' form.
  37. Click the drop down for the 'Select Desired service code import file name' field.
  38. Verify the recently compiled is available in the drop down.
  39. Select the file.
  40. Click [Process].
  41. Verify the report launched successfully.
  42. Verify the report displays the error message 'The 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' field can only be valued when field 'Service Code Category' is not a primary code'.
  43. Close the report.
  44. Close the 'Service Code Upload Rejected Codes' form.
  45. Exit out of the 'Service Code Upload Rejected Codes' form.
  46. Close the form.
  47. Repeat steps from 22 through 35 for File6.
  48. Open the 'Crystal Report' or SQL data viewer.
  49. Run the query to retrieve data from the 'SYSTEM.billing_tx_master_table' sql table.
  50. Verify the 'generate_add_on_services_code' and 'generate_add_on_services_value' are added in the table.
  51. Verify the 'generate_add_on_services_code' and 'generate_add_on_services_value' contains correct value for the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?' field as set up in the 'Service Code' form.
  52. Run the 'select * from SYSTEM.batchload_tx_accepted' to retrieve data from the 'SYSTEM.batchload_tx_accepted' sql table.
  53. Verify the 'generate_add_on_services_code' and 'generate_add_on_services_value' are added in the table.
  54. Verify the 'generate_add_on_services_code' and 'generate_add_on_services_value' contains correct value for the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?' field as set up in the text file uploaded through the 'Service Code Upload Process' form.
  55. Close the report.
Scenario 2: Validating co-practitioner services - 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' = Y, N or Null and 'Create Co-Practitioner Services From Progress Notes' = Y
Specific Setup:
  • Registry Setting:
  • The 'Enable Co-Practitioner Services From Progress Notes' registry setting is set to 'Y'.
  • Program Maintenance:
  • The 'Create Co-Practitioner Services From Progress Notes' field is set to 'Yes'.
  • 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 = 1
  • Dictionary Value = Evaluation Management
  • 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.
  • A primary add-on service code is created with the following:
  • Service Code Category = Primary 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? = No
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Another 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.
  • An interactive complexity add-on service code is created with the following:
  • Service Code Category =Interactive Complexity code
  • Service Code Type = desired value
  • Type of Fee = desired value.
  • Should Add-On Services Generate for Co-Practitioners for this Service Code? = NULL
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Service Fee/Cross Reference Maintenance:
  • A fee definition is created for all the service codes. Note the fee for each service code.
  • An active practitioner is identified. Note the practitioner ID.
  • Admission:
  • An active client is identified, or a new client is created. Note the client 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.
Steps
  1. Select desired client from the 'My Clients' widget.
  2. Open the 'Progress Notes (Group and Individual)' form.
  3. Validate the 'Select Client' field contains the client selected from the 'My Clients' widget.’.
  4. Select desired episode from the 'Select Episode' field.
  5. Select ‘New Service’ from the 'Progress Notes For' field.
  6. Select any value from the 'Note Type' field.
  7. Enter any value in the 'Notes Field' field.
  8. Enter the desired date in the 'Date Of Service' field.
  9. Enter primary service code in the 'Service Charge Code' field.
  10. Validate the 'Service Program' field contains the Service Program associated to selected episode.
  11. Select desired practitioner.
  12. Enter desired service duration.
  13. Select desired co-practitioner.
  14. Select Co-Practitioner Duration.
  15. Select Add-On codes associated with the primary code and Add-On duration.
  16. Select ‘Final’ from the 'Draft/Final' field.
  17. Click [File Note].
  18. Validate a message is displayed stating: Note Filed.
  19. Click [OK].
  20. Close the form.
  21. Open the 'Client Ledger' for the client.
  22. Verify the client ledger contains primary and add-on services created for all the co-practitioner listed in the progress note if the field 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' is set to 'Yes' or Null for the add-on service code in the 'Service Code' form.
  23. Close the form.
  24. Open the 'Close Charges' form.
  25. Close all the charges distributed to the guarantor.
  26. Close the form.
  27. Open the 'Create Interim Billing Batch File' form.
  28. Create an interim billing batch that covers the client, guarantor and services rendered to the client. Note the batch number.
  29. Close the form.
  30. Open the 'Electronic Billing' form.
  31. Compile an 837 bill for the client.
  32. Verify the bill compiles successfully.
  33. Select 'Dump File' option from the billing options.
  34. Select the recently compiled 837 file.
  35. Review the file.
  36. Verify the primary and add-on services are created for all the co-practitioner listed in the progress note if the field 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' is set to 'Yes' or Null for the add-on service code in the 'Service Code' form.
  37. Close the report.
  38. Close the form.
Scenario 3: Validating co-practitioner services - 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' = Y, N or Null and 'Create Co-Practitioner Services From Progress Notes' = N
Specific Setup:
  • Registry Setting:
  • The 'Enable Co-Practitioner Services From Progress Notes' registry setting is set to 'Y'.
  • Program Maintenance:
  • The 'Create Co-Practitioner Services From Progress Notes' field is set to 'Yes'.
  • 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 = 1
  • Dictionary Value = Evaluation Therapy
  • Extended dictionary 'Allow Multiple Add-On Code' = 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.
  • A primary add-on service code is created with the following:
  • Service Code Category = Primary 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? = No
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Another 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.
  • An interactive complexity add-on service code is created with the following:
  • Service Code Category =Interactive Complexity code
  • Service Code Type = desired value
  • Type of Fee = desired value.
  • Should Add-On Services Generate for Co-Practitioners for this Service Code? = NULL
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • The Add-On service codes created above is selected as an add-on code for the primary service code selected.
  • Service Fee/Cross Reference Maintenance:
  • A fee definition is created for all the service codes. Note the fee for each service code.
  • An active practitioner is identified. Note the practitioner ID.
  • Admission:
  • An active client is identified, or a new client is created. Note the client 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.
Steps
  1. Select desired client from the 'My Clients' widget.
  2. Access the 'Progress Notes (Group and Individual)' form.
  3. Validate the 'Select Client' field contains the client selected from the 'My Clients' widget.’.
  4. Select desired episode from the 'Select Episode' field.
  5. Select ‘New Service’ from the 'Progress Notes For' field.
  6. Select any value from the 'Note Type' field.
  7. Enter any value in the 'Notes Field' field.
  8. Enter the desired date in the 'Date Of Service' field.
  9. Enter primary service code in the 'Service Charge Code' field.
  10. Validate the 'Service Program' field contains the Service Program associated to selected episode.
  11. Select desired practitioner.
  12. Enter desired service duration.
  13. Select desired co-practitioner.
  14. Select Co-Practitioner Duration.
  15. Please note: User can add multiple co-practitioner to the note.
  16. Select Add-On codes associated with the primary code.
  17. Enter Add-On duration for the selected Add-On code.
  18. Click [Save Add-On Service].
  19. Select ‘Final’ from the 'Draft/Final' field.
  20. Click [File Note].
  21. Validate a message is displayed stating: Note Filed.
  22. Click [OK].
  23. Close the form.
  24. Open the 'Client Ledger' for the client.
  25. Verify the client ledger does not contain add-on services created for the co-practitioners added in the progress note. (Please note: The field 'Create Co-Practitioner Services From Progress Notes' in the 'Program Maintenance' form is set to 'No' and it takes precedence over the setting of the 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' field in the 'Service Code' form).
  26. Close the form.
  27. Open the 'Close Charges' form.
  28. Close all the charges distributed to the guarantor.
  29. Close the form.
  30. Open the 'Create Interim Billing Batch File' form.
  31. Create an interim billing batch that covers the client, guarantor and services rendered to the client. Note the batch number.
  32. Close the form.
  33. Open the 'Electronic Billing' form.
  34. Compile an 837 bill for the client.
  35. Verify the bill compiles successfully.
  36. Select 'Dump File' option and select the recently compiled 837 file.
  37. Review the file.
  38. Verify the primary and add-on services are created only for the practitioner. The bill does not display any Add-on services or primary services created for the co-practitioner listed in the progress note. (Please note: The field 'Create Co-Practitioner Services From Progress Notes' in the 'Program Maintenance' form is set to 'No' and it takes precedence over the setting of the 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' field in the 'Service Code' form).
  39. Close the report.
  40. Close the form.
Scenario 4: Cal-PM - Service Codes - Field validation
Specific Setup:
  • Registry Setting:
  • The Avatar PM->System Maintenance->Service Code Maintenance->->->Enable Multiple Add-On Code Per Primary Code Functionality is set to 'Y'.
  • Dictionary Update:
  • File= 'Other Tabled File,
  • Data Element -291, Service Code Type
  • Dictionary Code = 1
  • Dictionary Value = Evaluation Therapy
  • Extended dictionary 'Allow Multiple Add-On Code' = 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.
  • A primary add-on service code is created with the following:
  • Service Code Category = Primary Add-On 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.
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Another add-on service code is created with the following:
  • Service Code Category = Interactive Complexity Code
  • Service Code Type = desired value
  • Type of Fee = desired value.
  • All other fields are populated as required/needed.
  • Note the code and definition.
Steps
  1. Open the 'Service Codes' form.
  2. Verify the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?’ is added to the form.
  3. Verify the field is initially disabled.
  4. Select 'Edit' in the 'Add New Or Edit Existing' field.
  5. Select the primary add-on code created in the setup section.
  6. Verify the field is enabled. (Please note: The field is enabled If the “Service Code Category” field is set to something other than ‘Primary Code‘ i.e. 'Service Code Category' field must equal ‘Add-On Code’, ‘Interactive Complexity’, or ‘Primary Add-On Code’).
  7. Verify the help message text is -If this field is set to 'Yes', when this service is entered as an add-on service in a progress note with co-practitioners, a distinct add-on service for this service code will generate for each co-practitioner listed in the note. If this field is set to 'No', an add-on service will only generate for the Primary Practitioner in the note. The default logic for this field is 'Yes' - unless 'No' is selected, the add-on service will generate for each co-practitioner in the note. Note - services only generate for co-practitioners if the 'Create Co-Practitioner Services from Progress Notes' field in the Program Maintenance form is set to 'Yes.'.
  8. Verify the field is optional and not the required field.
  9. Select 'Yes' in the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?’ field.
  10. Click [File Service Code].
  11. Validate 'Edit' is selected in the 'Add New Or Edit Existing' field.
  12. Select the second add-on code created in the setup section.
  13. Verify the field is enabled. (Please note: The field is enabled If the “Service Code Category” field is set to something other than ‘Primary Code‘ i.e. 'Service Code Category' field must equal ‘Add-On Code’, ‘Interactive Complexity’, or ‘Primary Add-On Code’)
  14. Verify the field is optional and not the required field.
  15. Select 'No' in the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?’ field.
  16. Click [File Service Code].
  17. Validate 'Edit' is selected in the 'Add New Or Edit Existing' field.
  18. Select the interactive complexity code created in the setup section.
  19. Verify the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?' field is enabled. (Please note: The field is enabled If the 'Service Code Category' field is set to something other than ‘Primary Code‘ i.e. 'Service Code Category' field must equal ‘Add-On Code’, ‘Interactive Complexity’, or ‘Primary Add-On Code’)
  20. Verify the field is optional and not the required field.
  21. Do not select any value in the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?’ field.
  22. Click [File Service Code].
  23. Validate 'Edit' is selected in the 'Add New Or Edit Existing' field.
  24. Select the primary code created in the setup section.
  25. Verify the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?' field is not enabled. (Please note: The field is enabled If the 'Service Code Category' field is set to something other than ‘Primary Code‘ i.e. 'Service Code Category' field must equal ‘Add-On Code’, ‘Interactive Complexity’, or ‘Primary Add-On Code’)
  26. Click [File Service Code].
  27. Validate 'Edit' is selected in the 'Add New Or Edit Existing' field.
  28. Select the primary add-on code created in the setup section.
  29. Verify the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?’ field is enabled and set to 'Yes'.
  30. Validate 'Edit' is selected in the 'Add New Or Edit Existing' field.
  31. Select the add-on code created in the setup section.
  32. Verify the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?’ field is enabled and set to 'No'.
  33. Select 'Yes' in the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?’ field.
  34. Select 'Edit' in the 'Add New Or Edit Existing' field.
  35. Select the interactive complexity code created in the setup section.
  36. Verify the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?' field is enabled and nothing is selected in the field.
  37. Select 'Edit' in the 'Add New Or Edit Existing' field.
  38. Select the primary code created in the setup section.
  39. Verify the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?' field is not enabled.
  40. Verify the 'Service Code Report' is updated to include the new field 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' and display its value from the form.
  41. Close the report
  42. Close the form.
  43. Open the 'Crystal Report' or SQL data viewer.
  44. Run the query to retrieve data from the 'SYSTEM.billing_tx_master_table' sql table.
  45. Verify the 'generate_add_on_services_code' and 'generate_add_on_services_value' are added in the table.
  46. Verify the 'generate_add_on_services_code' and 'generate_add_on_services_value' contains correct value for the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?' field as set up in the 'Service Code' form.



Service Codes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Code Upload Process
  • Service Code Upload Accepted Codes (2)
  • Service Code Upload Rejected Codes (2)
  • Admission (Outpatient)
  • Dictionary Update (PM)
  • Financial Eligibility
  • Electronic Billing
  • Progress Notes (Group and Individual)
  • Program Maintenance
  • Site Specific Section Modeling (CWS)
Scenario 1: Service code upload process - Validating compile/post file
Specific Setup:
  • The following text files are created to upload the service code in the system with the value of new field 'Should Add-On Services Generate for Co-Practitioners for this Service Code?'. Note the file name and location of the file.
  • The file to upload the add-on code with the value 'Y' for the field. (i.e. Name of the file File1).
  • The file to upload the add-on code with the value 'N' for the field. (i.e. Name of the file File2).
  • The file to upload the add-on code without any value selected for the field. (i.e. Name of the file File3).
  • The file to upload the primary code with the value 'Y' for the field. (i.e. Name of the file File5).
  • The file to upload the primary code with the value 'Y' for the field. (i.e. Name of the file File6).
  • The file to upload the primary code without any value for the field. (i.e. Name of the file File7).
Steps
  1. Open the 'Service Code Upload Process' form.
  2. Click [Select File].
  3. Select File1 created in the setup.
  4. Select 'Compile' in the 'Compile Or Post' field.
  5. Select 'No' in the 'Override Existing Service Codes' field.
  6. Submit the form.
  7. Verify the message: "Compile completed. To View results review accepted reports".
  8. Click [OK].
  9. Open the 'Service Code Upload Accepted Codes' form without exiting out from the 'Service Code Upload Process' form.
  10. Click the drop down for the 'Select Desired service code import file name' field.
  11. Verify the recently compiled file displays in the drop down.
  12. Select the file.
  13. Click [Process].
  14. Verify the report launched successfully and all the data displays correctly as listed in the texted file.
  15. Close the report.
  16. Close the 'Service Code Upload Accepted Codes' form.
  17. Locate to the 'Service Code Upload Process' form
  18. Select 'Post' in the 'Compile Or Post' field.
  19. Verify the file posted successfully.
  20. Open the 'Service Code' form.
  21. Select the recently uploaded service code to edit.
  22. Verify the field 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' is set to desired value defined in the text file.
  23. Close the form.
  24. Repeat steps 1 through 20 for the File1, File2, File3, and File7.
  25. Run the query to retrieve data from the 'SYSTEM.batchload_tx_accepted' sql table.
  26. Verify the 'generate_add_on_services_code' and 'generate_add_on_services_value' are added in the table.
  27. Open the 'Service Code Upload Process' form.
  28. Click [Select File].
  29. Select File5 created in the setup.
  30. Select 'Compile' in the 'Compile Or Post' field.
  31. Select 'No' in the 'Override Existing Service Codes' field.
  32. Submit the form.
  33. Verify that the file should not be compiled successfully.
  34. Verify the message: 'No accepted data compiled. To view results review rejected report'.
  35. Click [OK].
  36. Open the 'Service Code Upload Rejected Codes' form without exiting out from the 'Service Code Upload Process' form.
  37. Click the drop down for the 'Select Desired service code import file name' field.
  38. Verify the recently compiled is available in the drop down.
  39. Select the file.
  40. Click [Process].
  41. Verify the report launched successfully.
  42. Verify the report displays the error message 'The 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' field can only be valued when field 'Service Code Category' is not a primary code'.
  43. Close the report.
  44. Close the 'Service Code Upload Rejected Codes' form.
  45. Exit out of the 'Service Code Upload Rejected Codes' form.
  46. Close the form.
  47. Repeat steps from 22 through 35 for File6.
  48. Open the 'Crystal Report' or SQL data viewer.
  49. Run the query to retrieve data from the 'SYSTEM.billing_tx_master_table' sql table.
  50. Verify the 'generate_add_on_services_code' and 'generate_add_on_services_value' are added in the table.
  51. Verify the 'generate_add_on_services_code' and 'generate_add_on_services_value' contains correct value for the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?' field as set up in the 'Service Code' form.
  52. Run the 'select * from SYSTEM.batchload_tx_accepted' to retrieve data from the 'SYSTEM.batchload_tx_accepted' sql table.
  53. Verify the 'generate_add_on_services_code' and 'generate_add_on_services_value' are added in the table.
  54. Verify the 'generate_add_on_services_code' and 'generate_add_on_services_value' contains correct value for the ‘Should Add-On Services Generate for Co-Practitioners for this Service Code?' field as set up in the text file uploaded through the 'Service Code Upload Process' form.
  55. Close the report.
Scenario 2: Validating co-practitioner services - 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' = Y, N or Null and 'Create Co-Practitioner Services From Progress Notes' = Y
Specific Setup:
  • Registry Setting:
  • The 'Enable Co-Practitioner Services From Progress Notes' registry setting is set to 'Y'.
  • Program Maintenance:
  • The 'Create Co-Practitioner Services From Progress Notes' field is set to 'Yes'.
  • 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 = 1
  • Dictionary Value = Evaluation Management
  • 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.
  • A primary add-on service code is created with the following:
  • Service Code Category = Primary 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? = No
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Another 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.
  • An interactive complexity add-on service code is created with the following:
  • Service Code Category =Interactive Complexity code
  • Service Code Type = desired value
  • Type of Fee = desired value.
  • Should Add-On Services Generate for Co-Practitioners for this Service Code? = NULL
  • All other fields are populated as required/needed.
  • Note the code and definition.
  • Service Fee/Cross Reference Maintenance:
  • A fee definition is created for all the service codes. Note the fee for each service code.
  • An active practitioner is identified. Note the practitioner ID.
  • Admission:
  • An active client is identified, or a new client is created. Note the client 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.
Steps
  1. Select desired client from the 'My Clients' widget.
  2. Open the 'Progress Notes (Group and Individual)' form.
  3. Validate the 'Select Client' field contains the client selected from the 'My Clients' widget.’.
  4. Select desired episode from the 'Select Episode' field.
  5. Select ‘New Service’ from the 'Progress Notes For' field.
  6. Select any value from the 'Note Type' field.
  7. Enter any value in the 'Notes Field' field.
  8. Enter the desired date in the 'Date Of Service' field.
  9. Enter primary service code in the 'Service Charge Code' field.
  10. Validate the 'Service Program' field contains the Service Program associated to selected episode.
  11. Select desired practitioner.
  12. Enter desired service duration.
  13. Select desired co-practitioner.
  14. Select Co-Practitioner Duration.
  15. Select Add-On codes associated with the primary code and Add-On duration.
  16. Select ‘Final’ from the 'Draft/Final' field.
  17. Click [File Note].
  18. Validate a message is displayed stating: Note Filed.
  19. Click [OK].
  20. Close the form.
  21. Open the 'Client Ledger' for the client.
  22. Verify the client ledger contains primary and add-on services created for all the co-practitioner listed in the progress note if the field 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' is set to 'Yes' or Null for the add-on service code in the 'Service Code' form.
  23. Close the form.
  24. Open the 'Close Charges' form.
  25. Close all the charges distributed to the guarantor.
  26. Close the form.
  27. Open the 'Create Interim Billing Batch File' form.
  28. Create an interim billing batch that covers the client, guarantor and services rendered to the client. Note the batch number.
  29. Close the form.
  30. Open the 'Electronic Billing' form.
  31. Compile an 837 bill for the client.
  32. Verify the bill compiles successfully.
  33. Select 'Dump File' option from the billing options.
  34. Select the recently compiled 837 file.
  35. Review the file.
  36. Verify the primary and add-on services are created for all the co-practitioner listed in the progress note if the field 'Should Add-On Services Generate for Co-Practitioners for this Service Code?' is set to 'Yes' or Null for the add-on service code in the 'Service Code' form.
  37. Close the report.
  38. Close the form.

Topics
• Service Codes • Progress Notes
2023 Update 90 Summary | Details
File Import - Service Fee/Cross Reference
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • File Import
Scenario 1: File Import - Service Fee/Cross Reference - Fee definition with practitioner category, location, practitioner and program
Specific Setup:
  • Registry Setting:
  • Set the registry setting 'Import File Delimiter' to a desired value. Note the value to be used.
  • Service Codes:
  • Add a new service code for testing purposes. Note the service code/name.
  • The following text files are created to import the service codes:
  • File1 -A 'Service Fee/Cross Reference Maintenance' import file is created to define two fee records for the service code. The first record contains practitioner category for the fee definition and the second record does not contain practitioner category. Note the path where the file is located.
  • File2 -A 'Service Fee/Cross Reference Maintenance' import file is created to define two fee records for the service code with the identical values for all values except for the following 4 values: location, practitioner, practitioner category and program. The first record contains location, practitioner category, practitioner, and program for the fee definition and the second record does not contain location. Note the path where the file is located.
  • File3 -A 'Service Fee/Cross Reference Maintenance' import file is created to define three fee records for the service code where first and third record are identical. The first and second record only differ by the 4 values: location, practitioner, practitioner category and program. Note the path where the file is located.
  • File4 -A 'Service Fee/Cross Reference Maintenance' import file is created to define three fee records for the service code where first and third record are not identical. The first and second record only differ by the 4 values: location, practitioner, practitioner category and program. Note the path where the file is located.
Steps
  1. Open the 'File Import' form.
  2. Select the 'Service Fee/Cross Reference Maintenance' from the 'File Type' field.
  3. Upload File 1.
  4. Compile the file.
  5. Verify the file compiles successfully.
  6. Post File 1.
  7. Verify the file posted successfully.
  8. Open the 'Service Fee/Cross Reference Maintenance' form.
  9. Edit the service code mentioned in the file import file.
  10. Enter the 'From Date' same as the date entered in the file import file.
  11. Verify all the fields displays correctly as entered in File 2.
  12. Click [Close Form].
  13. Open the 'File Import' form.
  14. Select the 'Service Fee/Cross Reference Maintenance' from the 'File Type' field.
  15. Upload File 2.
  16. Compile the file.
  17. Verify the information message: 'Compiled'.
  18. Click [OK].
  19. Post File 2.
  20. Verify the file posted successfully.
  21. Open the 'Service Fee/Cross Reference Maintenance' form.
  22. Edit the service code mentioned in the file import file.
  23. Enter the 'From Date' same as the date entered in the file import file.
  24. Verify all the fields displays correctly as entered in File 2.
  25. Click [Close Form].
  26. Open the 'File Import' form.
  27. Select the 'Service Fee/Cross Reference Maintenance' from the 'File Type' field.
  28. Upload File 3.
  29. Compile the file.
  30. Verify the information message: "File [File Name] contains one or more errors. These errors can be reviewed using 'Print Errors' action".
  31. Click [OK] button.
  32. Select the 'Print Errors' option.
  33. Review the error report.
  34. Verify the report displays the error: 'Duplicate Fee Service Code This line is a duplicate of line # 1. This line will be skipped. 1'.
  35. Click [X].
  36. Upload File 4.
  37. Compile the file.
  38. Verify the information message: 'Compiled'.
  39. Click [OK].
  40. Post File 4.
  41. Verify the file posted successfully.
  42. Open the 'Service Fee/Cross Reference Maintenance' form.
  43. Edit the service code mentioned in the file import file.
  44. Enter the 'From Date' same as the date entered in the file import file.
  45. Verify the service fee displays correctly as entered in file.
  46. Click [Close Form].

Topics
• File Import
2023 Update 93 Summary | Details
Cal-OMS Admission
Scenario 1: CalOMSAdmission - Validation
Specific Setup:
  • The registry setting "Enable LA County Reporting Requirements" is set to "Y".
  • A new client (OP) is created or an existing one is identified to perform Cal-OMS admission.
  • 'Client A'.
  • The 'Cal-OMS Admission' is submitted for 'Client A' with populating data in each field.
Steps
  1. Open the 'Cal-OMS Admission' form.
  2. Search for 'Client A' and select from the results.
  3. Select the episode from the grid.
  4. Select the Cal-OMS Admission record from the grid.
  5. Select the 'Admission Data' section.
  6. Validate that the field "What is your Principal Source of Referral?" is populated with the filed value.
  7. Clear the field by clicking the 'x' button on it.
  8. Validate the field is cleared successfully.
  9. Fill out or modify all the needed fields and select [Submit].
  10. Select [Continue Filing].
  11. Open the 'Cal-OMS Admission' form.
  12. Select the episode from the grid.
  13. Select the Cal-OMS Admission record from the grid.
  14. Select the 'Admission Data' section.
  15. Validate that the field "What is your Principal Source of Referral?" is populated with the recently filed value.
  16. Select [Discard].

Topics
• Cal-Oms Admission • NX
2023 Update 94 Summary | Details
Client Demographic forms - 'Time Zone for Appointment Reminders' field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Discharge
  • Pre Admit
  • Pre Admit Discharge
  • SoapUI - ClientDemographics
  • SoapUI - UpdateAdmission
  • Admission (Outpatient)
Scenario 1: 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. Select the desired value in the 'Time Zone For Appointment Reminders' field.
  6. Click [Submit].
  7. Access the 'Admission' form for the client admitted in the previous steps.
  8. Click [Edit] for the episode added in the previous steps.
  9. Validate the previously filed data is displayed.
  10. Select the "Demographics" section.
  11. Validate the 'Time Zone For Appointment Reminders' field contains the value selected in the previous steps.
  12. Close the form.
Scenario 2: '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. Select the desired value in the 'Time Zone For Appointment Reminders' field.
  3. Populate any other desired fields.
  4. Click [Submit].
  5. Select "Client A" and access the 'Update Client Data' form.
  6. Validate the previously filed data is displayed.
  7. Validate the 'Time Zone For Appointment Reminders' field contains the value selected in the previous steps.
  8. Close the form.
Scenario 3: '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. Select the desired value in the 'Time Zone For Appointment Reminders' field.
  9. Click [Submit].
  10. Select "Client A" and access the 'Discharge' form.
  11. Select the discharged episode and click [Edit].
  12. Validate all previously filed data is displayed.
  13. Select the "Demographics" section.
  14. Validate the 'Time Zone For Appointment Reminders' field contains the value filed in the previous steps.
  15. Close the form.
Scenario 4: '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. Select the desired value in the 'Time Zone For Appointment Reminders' field.
  5. Click [Submit].
  6. Select "Client A" and access the 'Pre Admit' form.
  7. Select an existing episode and click [Edit].
  8. Select the "Demographics" section.
  9. Validate the 'Time Zone For Appointment Reminders' field contains the value selected in the previous steps.
  10. Close the form.
Scenario 5: '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. Select the desired value in the 'Time Zone For Appointment Reminders' field.
  5. Click [Submit].
  6. Select "Client A" and access the 'Call Intake' form.
  7. Select the existing call intake record and click [Edit].
  8. Select the "Demographics" section.
  9. Validate the 'Time Zone For Appointment Reminders' field contains the value selected in the previous steps.
  10. Close the form.
Scenario 6: Pre Admit Discharge web service validation
Specific Setup:
  • A client is enrolled in an existing Pre Admit episode (Client A).
Steps
  1. Access SoapUI for the 'ClientPreAdmitDischarge' - 'PreAdmitDischargeClient' 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 'TimeZoneForAppointmentReminders' field.
  10. Enter "Client A" in the 'ClientID' field.
  11. Enter the episode number to be discharged in the 'EpisodeNumber' field.
  12. Click [Run].
  13. Validate the 'Message' field contains: Client Pre-Admit Discharge web service has been filed successfully.
  14. Select "Client A" and access the 'Pre Admit Discharge' form.
  15. Validate all populated fields are displayed as entered in the web service.
  16. Select the "Demographics" section.
  17. Validate the 'Time Zone For Appointment Reminders' field contains the value entered via web service.
  18. 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 'TimeZoneForAppointmentReminders' field.
  10. Enter "Client A" in the 'ClientID' field.
  11. Enter the episode number to be discharged in the 'EpisodeNumber' field.
  12. Click [Run].
  13. Validate the 'Message' field contains: Client Discharge web service has been filed successfully.
  14. Select "Client A" and access the 'Discharge' form.
  15. Validate all populated fields are displayed as entered in the web service.
  16. Select the "Demographics" section.
  17. Validate the 'Time Zone For Appointment Reminders' field contains the value entered via web service.
  18. 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. Enter the desired value in the 'TimeZoneForAppointmentReminders' field.
  6. Populate any other desired fields.
  7. Enter "Client A" in the 'ClientID' field.
  8. Click [Run].
  9. Validate the 'Message' field contains: Client Demographics web service has been filed successfully.
  10. Select "Client A" and access the 'Update Client Data' form.
  11. Validate all populated fields are displayed.
  12. Validate the 'Time Zone For Appointment Reminders' field contains the value entered via web service.
  13. 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 the desired value in the 'TimeZoneForAppointmentReminders' field.
  7. Enter "Client A" in the 'ClientID' field.
  8. Enter "Client A's" episode in the 'Episode' field.
  9. Click [Run].
  10. Validate the 'Confirmation' field contains a value such as: "Client Unique ID: # Unique ID: #".
  11. Validate the 'Message' field contains: "Client Admission web service has been filed successfully".
  12. Select "Client A" and access the 'Admission' form.
  13. Select the admission updated in the previous steps and click [Edit].
  14. Validate all populated fields are displayed.
  15. Validate the 'Time Zone For Appointment Reminders' field contains the value entered via web service.
  16. Close the form.
Scenario 10: '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. Select the desired value in the 'Time Zone For Appointment Reminders' field.
  6. Click [Submit].
  7. Access the 'Admission (Outpatient)' form for the client admitted in the previous steps.
  8. Click [Edit] for the episode added in the previous steps.
  9. Validate the previously filed data is displayed.
  10. Select the "Demographics" section.
  11. Validate the 'Time Zone For Appointment Reminders' field contains the value selected in the previous steps.
  12. Close the form.
Scenario 11: '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. Select the desired value in the 'Time Zone For Appointment Reminders' field.
  9. Click [Submit].
  10. Select "Client A" and access the 'Pre Admit Discharge' form.
  11. Select the discharged episode and click [OK].
  12. Validate the previously filed data is displayed.
  13. Select the "Demographics" section.
  14. Validate the 'Time Zone For Appointment Reminders' field contains the value selected in the previous steps.
  15. Close the form.

Topics
• Admission • Update Client Data • Discharge • Pre Admit • Call Intake • Pre Admit Discharge • Web Services • Admission (Outpatient)
Update 19 Summary | Details
'Electronic Billing' Support for Services Originating in Avatar MSO
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Electronic Billing
Scenario 1: 'Electronic Billing' - Verification of 'Support MSO Other Healthcare Coverage' Registry Setting (Services Originating in Avatar MSO)
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Add Policy Number Override' must be enabled
  • Avatar Cal-PM Registry Setting 'Support MSO Other Healthcare Coverage' must be enabled
  • Avatar Cal-PM Registry Setting 'Include Service Level Adjudication Info' must be enabled (and 'Include Service Level Adjudication Information (2430)' field set to 'Yes' via 'Guarantor/Program Billing Defaults' form '837 Professional' and/or '837 Institutional' section for applicable Guarantor/Program)
  • Avatar MSO Registry Setting 'Add Support For The Input Of Third Party Payer Amounts' must be enabled
  • One or more service(s) eligible for Avatar Cal-PM 837 Professional/837 Institutional file inclusion (via 'Electronic Billing' form) originating in Avatar MSO and including Third Party Payment/Adjustment 'Other Healthcare Coverage' information
Steps
  1. Open Avatar Cal-PM 'Electronic Billing' form.
  2. Note, acceptance testing may also be confirmed via Avatar Cal-PM 'Quick Billing' form/functionality
  3. Select 837 Professional or 837 Institutional in 'Billing Form' field.
  4. Enter/select 837 file sorting criteria, using values which will include service(s) originating in Avatar MSO.
  5. Click 'Process' button to sort/generate 837 Professional or 837 Institutional file.
  6. Select 'Dump File' in the 'Billing Options' field (or select 'Create File On Server' to review output file directly).
  7. Select 'Print' in the 'Print Or Delete Report' field.
  8. Select 837 Professional/837 Institutional file sorted which includes services originating in Avatar MSO, and click 'Process' button to display 837 outbound file data.
  9. In Avatar Cal-PM 837 Professional/837 Institutional format outbound electronic billing file data - for services originating via Avatar MSO inbound 837 file posting and including Service-Level Third Party Payment/Adjustment 'Other Healthcare Coverage' information, ensure that the following 837 Loop/Segments are included with values from original Avatar MSO inbound 837 claim/service Other Healthcare Coverage information:
  10. Other Subscriber Information (2320)
  11. Other Insurance Coverage Information (2320)
  12. Other Subscriber Name (2330A)
  13. Other Payer Name (2330B)
Topics
• Electronic Billing • Claims Processing
 

Avatar_Cal-PM_2024_Quarterly_Release_2024.01_Details.csv