Skip to main content

Avatar PM 2023 Monthly Release 2023.03.01 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 82 Summary | Details
Electronic Billing - 837 Professional
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission (Outpatient)
  • Diagnosis
  • Financial Eligibility
  • Client Ledger
  • Client Charge Input
  • Create Interim Billing Batch File
  • Electronic Billing
  • Individual Cash Posting (PM)
  • Dynamic Form - Individual Cash Posting - Information
  • Dynamic Form - Individual Cash Posting - Alert
  • Dynamic Form - Individual Cash Posting - Client
Scenario 1: 837 Professional - 2330A-N3 Other Subscriber Address
Specific Setup:
  • Guarantors/Payors 1: The '837' section has:
  • Any value in 'Claim Filing Indicator Code (2000B/2320-SBR-09)'.
  • 'Yes' in 'Bill As Primary Guarantor (837)'.
  • Will be assigned as 'Guarantor # 1' in 'Financial Eligibility'.
  • Guarantors/Payors 2: The '837' section has:
  • Any value in 'Claim Filing Indicator Code (2000B/2320-SBR-09)'.
  • 'No' in 'Bill As Primary Guarantor (837)'.
  • Will be assigned as 'Guarantor # 2' in 'Financial Eligibility'.
  • Client: identify a client with an unclaimed service where liability was transferred from Guarantors/Payors 1 to Guarantors/Payors 2,
  • Dictionary Update: Other Tabled Files - (13150) Select Segments To Suppress (P):
  • Code '2330A-N3' equals desired values, such as 'Other Sub Address'.
  • Code '2330A-N4' equals desired values, such as 'Other Sub City State'.
  • Guarantor/Program Billing Defaults: '837 Professional':
  • 'Select Segments To Suppress': 'Other Sub Address' & 'Other Sub City State' are selected.
Steps
  1. Open 'Electronic Billing'.
  2. Create an 837 Professional bill for the client and the secondary guarantor.
  3. Review the dump file to verify that the 2430 segment does not include the 'Other Sub Address' and 'Other Sub City State'.
  4. Close the report.
  5. Close the form.
  6. If desired, change the 'Guarantor/Program Billing Defaults' template to not suppress the 'Other Sub Address' and 'Other Sub City State' and submit the form.
  7. Open 'Electronic Billing'.
  8. Create an 837 Professional bill for the client and the secondary guarantor.
  9. Review the dump file to verify that the 2430 segment does include the 'Other Sub Address' and 'Other Sub City State'.
  10. Close the report.
  11. Close the form.
Topics
• 837 Professional • NX
Update 100 Summary | Details
Quick Billing - CCBHC Claim Grouping
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Codes
  • Service Fee/Cross Reference Maintenance
  • Guarantors/Payors
  • Admission
  • Diagnosis
  • Financial Eligibility
  • CCBHC PPS Service Definition
  • Client Charge Input
  • Client Ledger
  • CCBHC PPS Compile
  • Create Interim Billing Batch File
  • Electronic Billing
  • Crystal Report Viewer
  • Quick Billing Rule Definition
  • Quick Billing
  • Program Maintenance
  • Admission (Outpatient)
Scenario 1: CCBHC Enumerated services - Validate 837 Institutional billing for the CCBHC services when CCBHC Claim Grouping = Same
Specific Setup:
  • All CCBHC setup is complete.
  • Service Codes:
  • Service Code 1 has a value of 'Yes' in 'Is this a CCBHC Service' and a value of 'Yes' in 'CCBHC Enumerated Services'. Note the 'Insurance Charge Category'.
  • Service Code 2 has a value of 'Yes' in 'Is this a CCBHC Service' and a value of 'Yes' in 'CCBHC Enumerated Services'. The 'Insurance Charge Category' must be any value other than the value selected for Service Code 1.
  • Guarantor 1 is a CCBHC guarantor. Allow Customization Of Guarantor Plan' has a value of 'Yes'. Note the 'Financial Class'.
  • Admission:
  • A client is enrolled in an outpatient program. Note the program.
  • Client has an active diagnosis record. Note the diagnosis code.
  • The financial eligibility record is:
  • ‘Guarantor # 1’ = Guarantor 1.
  • The 'Customize Guarantor Plan' has a value of 'Yes'. In the 'Customize Plan' section all 'Covered Charge Categories' are selected.
  • Client Charge Input:
  • A service for Service Code 1 and Service Code 2 are rendered to the client on the same date.
  • Use 'Client Ledger' to verify that these services have liability distributed to Guarantor 1. Note the service dates. Note the 'CHG' amount.
  • Use 'Close Charges' to close the charges.
  • Create the 'CCBHC PPS Compile' for the client/the dates of service. Review the report to verify that the client is included with no errors.
  • Use the 'Client Ledger' to verify that the enumerated charge for Service Code 1 was created and liability distributed to Guarantor 1. Note the 'Date'. Note the 'CHG' amount.
  • 'Guarantor/Program Billing Defaults' for the CCBHC guarantor and the program for Client 1:
  • CCBHC Claim Grouping = Same.
  • Maximum Service Information Per Claim Information (Maximum LX Per CLM)’ = blank
  • Close the charges.
Steps
  1. Open 'Electronic Billing'.
  2. Create an '837 Institutional' for the 'CCBHC services, selecting 'Yes' in 'Include CCBHC Services'.
  3. Select 'Dump File' in 'Billing Options'.
  4. Select 'Print' in Print Or Delete Report'.
  5. Select the 'File'.
  6. Click [Process].
  7. Verify the PPS compiled service and enumerated services are included on the same claim.
  8. Close the report.
  9. Close the form.
Scenario 2: Quick Billing - 837 Institutional - CCBHC Claim Grouping - Separate Claim
Specific Setup:
  • All CCBHC setup is complete.
  • Service Codes:
  • Service Code 1 has a value of 'Yes' in 'Is this a CCBHC Service' and a value of 'Yes' in 'CCBHC Enumerated Services'. Note the 'Insurance Charge Category'.
  • Service Code 2 has a value of 'Yes' in 'Is this a CCBHC Service' and a value of 'No' in 'CCBHC Enumerated Services'. The 'Insurance Charge Category' must be any value other than the value selected for Service Code 1.
  • Guarantor 1 is a CCBHC guarantor. Allow Customization Of Guarantor Plan' has a value of 'Yes'. Note the 'Financial Class'.
  • Guarantor 2 is a Non CCBHC guarantor. Allow Customization Of Guarantor Plan' has a value of 'Yes'. Note the 'Financial Class'.
  • Admission:
  • A client is enrolled in an In-patient program. Note the program.
  • The client has an active diagnosis record. Note the diagnosis code.
  • The financial eligibility record is:
  • ‘Guarantor # 1’ = Guarantor 2.
  • ‘Guarantor # 2’ = Guarantor 1.
  • The 'Customize Guarantor Plan' has a value of 'Yes'. In the 'Customize Plan' section all 'Covered Charge Categories' are selected.
  • Client Charge Input:
  • Service for Service Code 1 is rendered to the client.
  • Use 'Client Ledger' to verify that these Enumerated services have liability distributed to Non-CCBHC Guarantor 1. Note the service dates. Note the 'CHG' amount.
  • Use 'Close Charges' to close the charges.
  • Create the 'CCBHC PPS Compile' for the client/the dates of service. Review the report to verify that the client is included with no errors.
  • Use the 'Client Ledger' to verify that the enumerated charge for Service Code 1 was created and liability distributed to CCBHC Guarantor 2. Note the 'Date'. Note the 'CHG' amount.
  • 'Guarantor/Program Billing Defaults' for the CCBHC guarantor and the program for Client 1:
  • CCBHC Claim Grouping = Separate.
  • Maximum Service Information Per Claim Information (Maximum LX Per CLM)’ = blank
  • Close the charges.
Steps
  1. Open 'Electronic Billing'.
  2. Create an '837 Institutional' for the 'CCBHC guarantor, selecting 'Yes' in 'Include CCBHC Services'.
  3. Select 'Sort File' in 'Billing Options'.
  4. Choose the Program/ Dates and all other mandatory fields and select Process.
  5. Observe that we see the error popup says "No Valid info found and there are Errors".
  6. Select 'Run Report' in 'Billing Options'.
  7. Select 'Print' in Print Or Delete Report'.
  8. Select the 'File'.
  9. Click [Print 837 Report].
  10. Verify that the PPS charge is correctly held for billing due to the enumerated service still awaiting remittance from private insurance. The PPS charge is not included in the bill.
  11. Click [X].
  12. Click [X].
Scenario 3: Quick Billing - 837 Professional - CCBHC Claim Grouping - Separate Claim
Specific Setup:
  • All CCBHC setup is complete.
  • Service Codes:
  • Service Code 1 has a value of 'Yes' in 'Is this a CCBHC Service' and a value of 'Yes' in 'CCBHC Enumerated Services'. Note the 'Insurance Charge Category'.
  • Service Code 2 has a value of 'Yes' in 'Is this a CCBHC Service' and a value of 'No' in 'CCBHC Enumerated Services'. The 'Insurance Charge Category' must be any value other than the value selected for Service Code 1.
  • Guarantor 1 is a CCBHC guarantor. Allow Customization Of Guarantor Plan' has a value of 'Yes'. Note the 'Financial Class'.
  • Guarantor 2 is a Non CCBHC guarantor. Allow Customization Of Guarantor Plan' has a value of 'Yes'. Note the 'Financial Class'.
  • Admission:
  • A client is enrolled in an outpatient program. Note the program.
  • The client has an active diagnosis record. Note the diagnosis code.
  • The financial eligibility record is:
  • ‘Guarantor # 1’ = Guarantor 2.
  • ‘Guarantor # 2’ = Guarantor 1.
  • The 'Customize Guarantor Plan' has a value of 'Yes'. In the 'Customize Plan' section all 'Covered Charge Categories' are selected.
  • Client Charge Input:
  • Service for Service Code 1 is rendered to the client.
  • Use 'Client Ledger' to verify that these Enumerated services have liability distributed to Non-CCBHC Guarantor 1. Note the service dates. Note the 'CHG' amount.
  • Use 'Close Charges' to close the charges.
  • Create the 'CCBHC PPS Compile' for the client/the dates of service. Review the report to verify that the client is included with no errors.
  • Use the 'Client Ledger' to verify that the enumerated charge for Service Code 1 was created and liability distributed to CCBHC Guarantor 2. Note the 'Date'. Note the 'CHG' amount.
  • 'Guarantor/Program Billing Defaults' for the CCBHC guarantor and the program for Client 1:
  • CCBHC Claim Grouping = Separate.
  • Maximum Service Information Per Claim Information (Maximum LX Per CLM)’ = blank
  • Close the charges.
Steps
  1. Open 'Electronic Billing'.
  2. Create an '837 Professional' for the 'CCBHC guarantor, selecting 'Yes' in 'Include CCBHC Services'.
  3. Select 'Sort File' in 'Billing Options'.
  4. Choose the Program/ Dates and all other mandatory fields and select Process.
  5. Observe that we see the error popup says "No Valid info found and there are Errors".
  6. Select 'Rub Report' in 'Billing Options'.
  7. Select 'Print' in Print Or Delete Report'.
  8. Select the 'File'.
  9. Click [Print 837 Report]. Verify that the PPS charge is correctly held for billing due to the enumerated service still awaiting remittance from private insurance. The PPS charge is not included in the bill.
  10. Click [X].
  11. Click [X].
Topics
• 837 Institutional • Quick Billing • CCBHC • 837 Professional
Update 103 Summary | Details
Edit Service Information
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Fee/Cross Reference Maintenance
  • Set System Defaults (CWS)
  • Admission (Outpatient)
  • Financial Eligibility
  • Client Charge Input
  • Client Ledger
  • Delete Service
  • Program Maintenance
Scenario 1: Edit Service Information - Changing to a service code not assigned in Program Maintenance
Specific Setup:
  • Program Maintenance:
  • Program 1: ‘Assign Services To Program’ section has a service code assigned. Note the code to use in ‘Client Charge Input’. In additions, note a code that is not assigned.
  • Program 2: ‘Assign Services To Program’ section has does not have the code that will be used in ‘Client Charge Input’ assigned. It does have the above unassigned code assigned.
  • Identify a client in ‘Program 1’.
  • Client Charge Input is used to create a service for the client, using the service code assigned in ‘Program 1’.
Steps
  1. Open ‘Edit Service Information’.
  2. Enter the ‘Client ID’.
  3. Select the ‘Episode Number’ if there is more than one episode.
  4. If desired, enter the ‘Service Start Date’.
  5. If desired, enter the ‘Service End Date’.
  6. If desired, select a value in ‘Service Selection Default’.
  7. Click [Select Service(s) To Edit].
  8. Select the desired service.
  9. Click [OK].
  10. Change the service code to the service code that is not assigned to ‘Program 1’.
  11. Validate that no search results are returned.
  12. Set the service code to the original value.
  13. Change the ‘Program’ to ‘Program 2’.
  14. Validate that an error message is received.
  15. Click [OK].
  16. Delete the service code value.
  17. Change the ‘Program’ to ‘Program 2’.
  18. Change the service code to the code assigned to ‘Program 2’.
  19. Click [Submit].
  20. Click [No].
  21. Click [Submit].
Financial Investigation - Web Services
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SoapUI - AddFinancialInvestigation
  • Financial Investigation
  • Admission (Outpatient)
  • SQL Query/Reporting
Scenario 1: WebSvc.FinancialInvestigationV2 - Validate AddFinancialInvestigation method with "Financial Investigation" form
Specific Setup:
  • An existing client is identified. Note the client's id.
Steps
  1. Access SoapUI for the 'Financial Investigation' - 'AddFinancialInvestigation' web service.
  2. Set the 'FIEffectiveDate' item to desired value, which can include past, current or future dates. Note the value.
  3. Set the 'IHGrossAnnualIncome' item to desired value. Note the value.
  4. Set the 'IRPartyAnnualIncome' item to desired value. Note the value.
  5. Set the 'IncomeValidation' item to desired value. Note the value.
  6. Set the 'NumberOfDependents' item to desired value. Note the value.
  7. Set the 'SlidingFeeScaleDependents' item to desired value. Note the value.
  8. Set the 'SlidingFeeScaleIncome' item to desired value. Note the value.
  9. Set the 'FamilySize' item to desired value. Note the value.
  10. Set the 'SlidingFeeDivideNumFamMembers' to "Y". Note the value.
  11. Set the 'SlidingFeeDivideNumFamMembersNum' to desired value. Note the value.
  12. Set the 'ClientID' to the ClientID identified in the setup section. Note the value.
  13. Set the 'LoginSource' to 'SOAPUI'. Note the value.
  14. Run the request.
  15. Click [Run].
  16. Validate the 'Confirmation' field contains a value such as: "Unique ID: IBE.001".
  17. Validate the 'Message' field contains: "Financial Investigation web service has been filed successfully".
  18. Open the 'Financial Investigation' form for the test client.
  19. Validate that a row has been added to the pre-display.
  20. Select the new row and click [Edit].
  21. Validate the 'Financial Investigation Effective Date' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  22. Validate the 'Income-Responsible Party Annual Income' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  23. Validate the 'Income-Household Gross Annual Income' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  24. Validate the 'Number Of Dependents' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  25. Validate the 'Sliding Fee Scale - Number of Dependents' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  26. Validate the 'Sliding Fee Scale - Income' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  27. Validate the 'Family Size' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  28. Validate the 'Divide Sliding Fee Scale Amount by Number of Family Members Receiving Services' field contains "Yes".
  29. Validate the 'Sliding Fee Scale - Number of Family Members Receiving Services' input box contains the value entered in the 'AddFinancialInvestigation' web service.
  30. Click [Submit].
Disclosure Management - Site Specific Section Modeling
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission
  • Document Routing Setup (PM)
  • Final to Draft Override (PM)
  • Delete Document
  • Site Specific Section Modeling (PM)
  • Disclosure Management Configuration
  • Disclosure Management
Scenario 1: Parent Namespace User Modeled Disclosure Management form with table aliasing
Specific Setup:
  • A user modeled form set up with the primary table being aliased to the Disclosure Management data. Please note: For internal testing purposes the disclosure management SQL table is validated. For your test, you may alias a different form. Note that table and validate it in place of SYSTEM.disclo_mgmt.
  • Admit or select a test client.
Steps
  1. Open the user modeled form from setup.
  2. Fill out all the fields on the form.
  3. Set "Draft/Final" to "Draft".
  4. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was not added to the table because the form was filed in draft mode.
  5. Open the user modeled form from setup.
  6. Fill all the fields on the form.
  7. Set "Draft/Final" to "Final".
  8. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was added to the table because the form was flagged as Final.
  9. Open the "Document Routing Setup" form.
  10. Enable document routing for the user modeled created during setup.
  11. Open the user modeled form from setup.
  12. Fill out all the fields on the form.
  13. Set "Draft/Final" to "Draft".
  14. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was not added to the table because the form was filed in draft mode.
  15. Open the user modeled form from setup.
  16. Fill all the fields on the form.
  17. Set "Draft/Final" to "Final".
  18. Click "Accept" or "Sign" on the "Confirm Document" screen.
  19. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was added to the table because the form was flagged as Final.
  20. Open the "Registry Settings" form.
  21. Enable the registry setting "RADplus->Document Routing->Routing Setup->->->Alias Data File Upon Document Routing Completion".
  22. Open the user modeled form from setup.
  23. Fill out all the fields on the form.
  24. Set "Draft/Final" to "Draft".
  25. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was not added to the table because the form was filed in draft mode.
  26. Open the user modeled form from setup.
  27. Fill all the fields on the form.
  28. Set "Draft/Final" to "Final".
  29. Click "Accept and Route" or "Sign and Route" on "Confirm Document" pop up.
  30. Route to another user.
  31. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was not added to the table because the registry setting mentioned previously is enabled and the document routing is not finalized.
  32. Log in as the user the document was routed to.
  33. Navigate to the "My ToDo" widget.
  34. Approve the document by electronically signing it.
  35. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was added to the table because the registry setting mentioned previously is enabled and the document routing is now finalized for the form.
  36. Open the "Registry Settings" form.
  37. Disable the registry setting "RADplus->Document Routing->Routing Setup->->->Alias Data File Upon Document Routing Completion".
  38. Open the user modeled form from setup.
  39. Fill out all the fields on the form.
  40. Set "Draft/Final" to "Draft".
  41. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was not added to the table because the form was filed in draft mode.
  42. Open the user modeled form from setup.
  43. Fill all the fields on the form.
  44. Set "Draft/Final" to "Final".
  45. Click "Accept and Route" or "Sign and Route" on "Confirm Document" pop up.
  46. Route to another user.
  47. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was added to the table because the registry setting mentioned previously is disabled, the system is not waiting for document routing to be finalized.
  48. Log in as the user the document was routed to.
  49. Navigate to the "My ToDo" widget.
  50. Approve the document by electronic signing it.
  51. By viewing the SQL table from the PM namespace, SYSTEM.disclo_mgmt, validate a row was not added to the table because the registry setting is disabled, and the record was filed when the form was routed.
  52. Open the "Final To Draft Override" form.
  53. Select a finalized document to return to draft status.
  54. A message should pop up noting that "Please note that filed Alias data will not be deleted or altered in any way as a result of filing the override for this row".
  55. Complete process.
  56. Open the "Delete Document" form.
  57. Choose to delete one of the user modeled/aliased documents.
  58. A message should pop up noting that "Please note that filed Alias data will not be deleted or altered in any way as a result of filing the override for this row".
  59. Complete the process.
Scenario 2: Disclosure Management - Validate Site specific fields
Specific Setup:
  • Using the "Disclosure Management Configuration" form, set up the system for Disclosure Management.
  • Using "Site Specific Section Modeling" form, add 3 fields of the type SS Disclosure Management Free Text to the Disclosure Management Disclosure section (PATIENT4000 (Disclosure Management) Disclosure).
  • Note: For NX only, on the Disclosure screen, once the items have been disclosed and viewed, you have to click 'Cancel' to go back to the main form to click "Submit" to finalize the process. This will be addressed in a future NX release to mimic the workflow in myAvatar.
Steps
  1. Open the "Disclosure Management" form.
  2. Fill out the Request, Authorization and Disclosure sections.
  3. In the "Disclosure" section, populate the site specific section modeling fields.
  4. Click "Process" button.
  5. Validate the correct items are included in the disclosure packet.
  6. Click "Disclose" button.
  7. Click the "Printer" icon.
  8. Print the disclosure packet.
  9. Return to the pre-display.
  10. Add another request, authorization, and disclosure.
  11. In the disclosure section, validate the site specific section modeling fields are blank after the last record was filed.
  12. Populate the site specific section modeling fields.
  13. Select "Other" in the "Disclosure Method" field.
  14. Set the "Disclosure Method - Specify Other" to "Mail".
  15. Click the "Process" button.
  16. Click the "Disclose" button.
  17. Return to the pre-display.
  18. Select a row in the pre-display.
  19. Click the "Delete" button.
  20. Validate the disclosure record is removed.
  21. Select one of the previously filed disclosure records that has a date in the "Disclosure Date" column.
  22. Click "Edit".
  23. Validate a message displays indicating the disclosure record was previously finalized because it has a disclosure date and can't be edited. It can only be displayed.
  24. Validate the Request, Authorization and Disclosure data is retrieved as it was entered, including the fields added via "Site Specific Section Modeling".
  25. Remain in the form by returning to the pre-display.
  26. Add another disclosure record.
  27. Fill out the request, authorization, and disclosure sections.
  28. In the disclosure section, Set "Disclosure Method" to "Electronic".
  29. Click the "Submit" button.
  30. Exit the form.
  31. Open the "Disclosure Management" form.
  32. In the disclosure record pre-display, select the disclosure record without a "Disclosure Date" that was just filed.
  33. Click the "Edit" button.
  34. Navigate to the "Disclosure" Section.
  35. Fill in the "Disclosure Date" and "Disclosure Time".
  36. Populate the site specific section modeling fields.
  37. Validate the "Disclosure Method" is set to "Electronic".
  38. Click the "Process" button.
  39. Click the "Disclose" button.
  40. Click the PDF download icon.
  41. Browse to the location on the server where you want to store the file.
  42. Give the file a name with a .pdf extension.
  43. Click the "Save" button.
  44. Validate a message pops up stating that once this Disclosure Management record is filed with a Disclosure Date entered it will no longer be available for edit. This record will only be available to view and print.
  45. Return to the pre-display.
  46. Validate a row was added to the disclosure pre-display.
  47. Exit the form.
Bed Management
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission
  • Bed Management
  • Crystal Report Viewer
  • Bed Management (View Only)
Scenario 1: Bed Management (View Only)
Specific Setup:
  • Client: Is enrolled in an inpatient program and has a value in ‘Social Security Number’, noting the number.
  • Note the 'Preadmit/Admission Date', 'Date of Birth', 'Episode #', 'Program', ‘Unit’, ‘Room’ and ‘Bed’.
  • Use the 'Diagnosis' form to note the diagnosis.
  • User Definition is updated for the signed in tester to select ‘Initial Data Entry’ in ‘Social Security Number Access’.
Steps
  1. Open 'Bed Management (View Only).
  2. Select the 'Unit'.
  3. Select the 'Room'.
  4. Click [Bed Management].
  5. Access the team, room, and bed for the client.
  6. Hover over the client’s name.
  7. Validate that the correct data displays and that the social security number does not display but displays as '***_**_****'.
  8. Close the grid.
  9. Close the form.
Disclosure Management
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Routing Setup (PM)
  • Admission
  • Client
  • Disclosure Management
  • Disclosure Management Configuration
  • Progress Notes (Group and Individual)
  • Treatment Plan
  • Clinical Document Viewer
Scenario 1: Disclosure Management - Date Created vs. Date Signed - Document Routing disabled
Specific Setup:
  • Registry setting "Replace 'Date Created' with 'Date Signed' on Document Routing Images" must be enabled.
  • Using the "Document Routing Setup" form, disable document routing for Progress Notes (Group and Individual), Treatment Plan and a user modeled form.
  • Using "Disclosure Management Configuration", include "Progress Notes (Group and Individual), Treatment Plan and a user modeled form among the forms available to the "Disclosure Management" form.
Steps
  1. Using the "Progress Notes (Group and Individual)" form:
  2. Generate a progress note.
  3. Finalize the note.
  4. Using the "Treatment Plan" form:
  5. Generate a new treatment plan.
  6. Finalize the note.
  7. Using a user modeled form:
  8. Generate a new form.
  9. Finalize the form.
  10. Open the "Disclosure Management" form:
  11. Generate a disclosure packet.
  12. On the Request section, select the client, episode and Request Information Start and End Dates that will encompass the forms previously generated for this test.
  13. Click "Apply Filters to Document Images" button.
  14. In the "Requested Chart Items" box, select "Progress Notes (Group and Individual)", Treatment Plan, user modeled forms you want to include in the disclosure packet.
  15. In the "Requested Document Images" box, select the forms for Progress Notes (Group and Individual), Treatment Plan and user modeled form you want to include in the disclosure packet.
  16. Navigate to the "Authorization" section.
  17. Select the same Episode and the Authorization Start and End Dates.
  18. Click "Yes - Default All Chat Items to Yes" radio button.
  19. Click "Update Chart Items Authorized for Disclosure" button.
  20. Click "Save" button.
  21. Click "Refresh Chart Items" button.
  22. Click "Yes - Default All Document Items To Yes" radio button.
  23. Click the "Update Document Images Authorized for Disclosure" button.
  24. Click "Save" button.
  25. Click "Refresh Document Images" button.
  26. Navigate to the "Disclosure" section.
  27. Populate the "Disclosure Date" and "Disclosure Time".
  28. Select all items in the "Chart Disclosure Information" box.
  29. Select all items in the "Disclosure Images" box.
  30. Select "Electronic" in the "Disclosure Method" field.
  31. Click "Process" button.
  32. Select various forms and then press "View".
  33. Validate the forms that were filed after the registry setting for "Replace 'Date Created' With 'Date Signed" on all "Document Routing Images" labels begin with "Date Signed" and the date and time the form was finalized.
  34. Click "Disclose" button.
  35. The final disclosure packet is presented.
  36. Validate the forms that were filed after the registry setting for "Replace 'Date Created' With 'Date Signed" on all "Document Routing Images" labels begin with "Date Signed" and the date and time the form was finalized.
  37. Click "Save" to generate the disclosure packet into a PDF document to be provided for the request, authorization, and disclosure.
  38. Open the "Disclosure Management" form:
  39. Select to edit the disclosure that was just filed.
  40. Validate it displays as it was previously saved.
  41. Open the "Document Routing Setup".
  42. Disable document routing for the progress note form.
  43. Open the "Progress Notes (Group and Individual)" form.
  44. Finalize a note for today's date.
  45. Open the "Disclosure Management" form.
  46. Set the "Request Date" to today's date.
  47. Select the episode the progress note was filed under.
  48. Set the "Information Start Date" to yesterday's date.
  49. Set the "Information End Date" to yesterday's date.
  50. Select the progress that was just filed in the "Requested Chart Items" field.
  51. Fill out the organization information.
  52. Navigate to the "Authorization" section.
  53. Set "Authorization Start Date" to yesterday's date.
  54. Set "Authorization End Date" to yesterday's date.
  55. Select the episode the progress note was filed under.
  56. Select the "Chart Items Authorized for Disclosure".
  57. Navigate to the "Disclosure" section.
  58. Set the "Disclosure Date" and "Disclosure Time".
  59. Click "Process".
  60. Validate the progress note for today isn't included in the disclosure packet because the progress note is outside of the date range for authorization.
Scenario 2: Disclosure Management - Date Created vs. Date Signed - Document Routing Enabled
Specific Setup:
  • Registry setting "Replace 'Date Created' with 'Date Signed' on Document Routing Images" must be enabled.
  • Using the "Document Routing Setup" form, enable document routing for Progress Notes (Group and Individual), Treatment Plan and a user modeled form.
  • Using "Disclosure Management Configuration", include "Progress Notes (Group and Individual), Treatment Plan and a user modeled form among the forms available to the "Disclosure Management" form.
Steps
  1. Using the "Progress Notes (Group and Individual)" form:
  2. Generate a progress note.
  3. Finalize and route the note.
  4. Validate the first line of every page of the document begins with "Date Signed" followed by the date and time the document was finalized.
  5. Using the "Treatment Plan" form:
  6. Generate a new treatment plan.
  7. Finalize and route the note.
  8. Validate the first line of every page of the document begins with "Date Signed" followed by the date and time the document was finalized.
  9. Using a user modeled form:
  10. Generate a new form.
  11. Finalize and route the form.
  12. Validate the first line of every page of the document begins with "Date Signed" followed by the date and time the document was finalized.
  13. Open the "Disclosure Management" form:
  14. Generate a disclosure packet.
  15. On the Request section, select the client, episode and Request Information Start and End Dates that will encompass the forms previously generated for this test.
  16. Click "Apply Filters to Document Images" button.
  17. In the "Requested Chart Items" box, select "Progress Notes (Group and Individual), Treatment Plan, user modeled forms you want to include in the disclosure packet.
  18. In the "Requested Document Images" box, select the forms for Progress Notes (Group and Individual), Treatment Plan and user modeled form you want to include in the disclosure packet.
  19. Navigate to the "Authorization" section.
  20. Select the same Episode and the Authorization Start and End Dates.
  21. Click "Yes - Default All Chat Items to Yes" radio button.
  22. Click "Update Chart Items Authorized for Disclosure" button.
  23. Click "Save" button.
  24. Click "Refresh Chart Items" button.
  25. Click "Yes - Default All Document Items To Yes" radio button.
  26. Click the "Update Document Images Authorized for Disclosure" button.
  27. Click "Save" button.
  28. Click "Refresh Document Images" button.
  29. Navigate to the "Disclosure" section.
  30. Populate the "Disclosure Date" and "Disclosure Time".
  31. Select all items in the "Chart Disclosure Information" box.
  32. Select all items in the "Disclosure Images" box.
  33. Select "Electronic" in the "Disclosure Method" field.
  34. Click "Process" button.
  35. Select various forms and then press "View".
  36. Validate the forms that were filed after the registry setting for "Replace 'Date Created' With 'Date Signed" on all "Document Routing Images" labels begin with "Date Signed" and the date and time the form was finalized.
  37. Click "Disclose" button.
  38. The final disclosure packet is presented.
  39. Validate the forms that were filed after the registry setting for "Replace 'Date Created' With 'Date Signed" on all "Document Routing Images" labels begin with "Date Signed" and the date and time the form was finalized.
  40. Click "Save" to generate the disclosure packet into a PDF document to be provided for the request, authorization, and disclosure.
  41. Open the "Disclosure Management" form:
  42. Select to edit the disclosure that was just filed.
  43. Validate it displays as it was previously saved.
  44. Open the "Document Routing Setup".
  45. Enable document routing for the progress note form.
  46. Open the "Progress Notes (Group and Individual)" form.
  47. Finalize a note for today's date.
  48. Route to another approver.
  49. Log in as the approver.
  50. Navigate to the "ToDo" widget.
  51. Accept and Sign the document.
  52. Open the "Disclosure Management" form.
  53. Set the "Request Date" to today's date.
  54. Select the episode the progress note was filed under.
  55. Set the "Information Start Date" to yesterday's date.
  56. Set the "Information End Date" to yesterday's date.
  57. Select the progress that was just filed in the "Requested Chart Items" field.
  58. Fill out the organization information.
  59. Navigate to the "Authorization" section.
  60. Set "Authorization Start Date" to yesterday's date.
  61. Set "Authorization End Date" to yesterday's date.
  62. Select the episode the progress note was filed under.
  63. Select the "Chart Items Authorized for Disclosure".
  64. Navigate to the "Disclosure" section.
  65. Set the "Disclosure Date" and "Disclosure Time".
  66. Click "Process".
  67. Validate the progress note for today isn't included in the disclosure packet because the progress note is outside of the date range for authorization.
Topics
• Edit Service Information • Financial Investigation • Web Services • Modeling • Disclosure • Site Specific Section Modeling • Maintain Hospital Bed File • Client Management
Update 110 Summary | Details
Guarantors/Payaors form-Claim Order section-Multiple iteration table.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SOAPUI - GuarantorsPayors
  • SOAPUI - UpdateGuarantorsPayors
  • Guarantors/Payors
Scenario 1: Guarantors/Payors - Web Services - Registry Setting 'Specify LX Order On A Claim'
Specific Setup:
  • Registry Setting:
  • 'Specify LX Order On A Claim' is added to the system and defaults to 'N'.
  • Set the registry setting to 'Y' and submit the form.
Steps
  1. Using SOAPUI or some other web service tool, file the AddGuarantorsPayors method of the GuarantorsPayors web service, which includes the Claim Order data.
  2. Open the "Guarantors/Payors" form, in Edit mode search for the Guarantor newly added and validate that the Guarantor is created and the respective details are correct as filed in the web service, including Claim Order data.
  3. Using SOAPUI or some other web service tool, file the UpdateGuarantorsPayors method of the GuarantorsPayors web service, edit at least one item in Claim Order data.
  4. Open the "Guarantors/Payors" form, in Edit mode search for the Guarantor and validate that the Guarantor is updated with the respective details as filed using the web service, including Claim Order data.
Scenario 2: Guarantors/Payors - Registry Setting 'Specify LX Order On A Claim
Specific Setup:
  1. Registry Setting: 'Specify LX Order On A Claim' is added to the system and defaults to 'N'.
Steps
  1. Open 'Guarantors/Payors'.
  2. Validate that there is no 'Claim Order' section exists.
  3. Select the Edit option.
  4. Search and select a Guarantor.
  5. Select '837' section.
  6. Validate that when the Registry setting 'Specify LX Order On A Claim' is set to 'N', the 837 section has the field named Sort Room and Board Codes First (837I/UB04).
  7. Select Discard.
  8. Open 'Registry Settings'.
  9. Search for the Registry setting 'Specify LX Order On A Claim' and set the value as 'Y'
  10. Submit and close the form.
  11. Open 'Guarantors/Payors'.
  12. Validate that the 'Claim Order' section exists.
  13. Select the Edit option.
  14. Search and select a Guarantor.
  15. Select '837' section.
  16. Validate that when the Registry setting 'Specify LX Order On A Claim' is set to 'Y', the 'Sort Room and Board Codes First (837I/UB04)' field is changed to 'Sort Room and Board Codes First (UB04)'.
  17. Select the 'Claim Order' section.
  18. Validate the form elements available.
  19. Add data into the 'Claim Order' section and submit the form.
  20. Go back to the form in 'Edit' mode and validate that the data exists in the 'Claim Order' section.
Electronic Billing - Registry Setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SOAPUI - GuarantorsPayors
  • SOAPUI - UpdateGuarantorsPayors
  • Guarantors/Payors
  • Electronic Billing
Scenario 1: Guarantors/Payors - Web Services - Registry Setting 'Specify LX Order On A Claim'
Specific Setup:
  • Registry Setting:
  • 'Specify LX Order On A Claim' is added to the system and defaults to 'N'.
  • Set the registry setting to 'Y' and submit the form.
Steps
  1. Using SOAPUI or some other web service tool, file the AddGuarantorsPayors method of the GuarantorsPayors web service, which includes the Claim Order data.
  2. Open the "Guarantors/Payors" form, in Edit mode search for the Guarantor newly added and validate that the Guarantor is created and the respective details are correct as filed in the web service, including Claim Order data.
  3. Using SOAPUI or some other web service tool, file the UpdateGuarantorsPayors method of the GuarantorsPayors web service, edit at least one item in Claim Order data.
  4. Open the "Guarantors/Payors" form, in Edit mode search for the Guarantor and validate that the Guarantor is updated with the respective details as filed using the web service, including Claim Order data.
Scenario 2: 837 Institutional - Registry Setting 'Specify LX Order On A Claim'
Specific Setup:
  • Registry Setting:
  • 'Specify LX Order On A Claim' is added to the system and defaults to 'N'.
  • Set the registry setting to 'Y' and submit the form.
  • Client A:
  • Has unclaimed services, for different service codes, that can be billed on the 837 Institutional.
  • Use 'Client Ledger' to note the service codes, dates of service, financial class, and guarantor.
  • Use 'Service Fee/Cross Reference Maintenance' to note the Revenue Code.
  • Create Interim Batch.
  • Close the charges using 'Close Charges'.
  • Guarantors/Payors:
  • Claim Order definition exists by service code or revenue code. Note the order.
Steps
  1. Open the 'Electronic Billing' form.
  2. Select the 'Billing Form' as 837-Institutional.
  3. Select the 'Type Of Bill'.
  4. Select the 'Individual Or All Guarantors'.
  5. Select the 'Guarantor'.
  6. Select the 'Billing Type'.
  7. Select 'Sort File' in the 'Billing Option' field.
  8. Enter any desired value in the 'File Description' field.
  9. Select 'Interim Batch' in the 'All Clients Or Interim Billing Batch' field.
  10. Choose the Interim batch from the 'Interim Batch Number' drop-down field.
  11. Select 'No' for the 'Create Claims' field.
  12. Enter the date value for the 'First Date Of Service To Include' and 'Last Date Of Service To Include' fields (Should cover the services that you want to run the bill for).
  13. Select 'All' for the 'Include Primary and/or Secondary Billing' field.
  14. Select the 'Process' button.
  15. Validate that the confirmation message contains: ‘Compile Complete'.
  16. Select 'OK'.
  17. Select 'Dump File' in the 'Billing Option' field.
  18. Click 'Print' in the 'Print Or Delete Report' field.
  19. Select 'File' from the drop-down.
  20. Click the 'Print 837 Report' button.
  21. Select the 'Process' button.
  22. Verify that the Dump file launched without any error.
  23. Validate that the LX order shown in the file is based on the preferred LX order configured in the Guarantors/Payors- Claim Order section.
Scenario 3: Guarantors/Payors - Registry Setting 'Specify LX Order On A Claim
Specific Setup:
  1. Registry Setting: 'Specify LX Order On A Claim' is added to the system and defaults to 'N'.
Steps
  1. Open 'Guarantors/Payors'.
  2. Validate that there is no 'Claim Order' section exists.
  3. Select the Edit option.
  4. Search and select a Guarantor.
  5. Select '837' section.
  6. Validate that when the Registry setting 'Specify LX Order On A Claim' is set to 'N', the 837 section has the field named Sort Room and Board Codes First (837I/UB04).
  7. Select Discard.
  8. Open 'Registry Settings'.
  9. Search for the Registry setting 'Specify LX Order On A Claim' and set the value as 'Y'
  10. Submit and close the form.
  11. Open 'Guarantors/Payors'.
  12. Validate that the 'Claim Order' section exists.
  13. Select the Edit option.
  14. Search and select a Guarantor.
  15. Select '837' section.
  16. Validate that when the Registry setting 'Specify LX Order On A Claim' is set to 'Y', the 'Sort Room and Board Codes First (837I/UB04)' field is changed to 'Sort Room and Board Codes First (UB04)'.
  17. Select the 'Claim Order' section.
  18. Validate the form elements available.
  19. Add data into the 'Claim Order' section and submit the form.
  20. Go back to the form in 'Edit' mode and validate that the data exists in the 'Claim Order' section.
Scenario 4: 837 Professional - Registry Setting 'Specify LX Order On A Claim'
Specific Setup:
  • Registry Setting:
  • 'Specify LX Order On A Claim' is added to the system and defaults to 'N'.
  • Set the registry setting to 'Y' and submit the form.
  • Client A:
  • Has unclaimed services, for different service codes, that can be billed on the 837 Professional.
  • Use 'Client Ledger' to note the service codes, dates of service, financial class, and guarantor.
  • Use 'Service Fee/Cross Reference Maintenance' to note the Revenue Code.
  • Create Interim Batch.
  • Close the charges using 'Close Charges'.
  • Guarantors/Payors:
  • Claim Order definition exists by service code or revenue code. Note the order.
Steps
  1. Open the 'Electronic Billing' form.
  2. Select the 'Billing Form' as 837-Professional.
  3. Select the 'Type Of Bill'.
  4. Select the 'Individual Or All Guarantors'.
  5. Select the 'Guarantor'.
  6. Select the 'Billing Type'.
  7. Select 'Sort File' in the 'Billing Option' field.
  8. Enter any desired value in the 'File Description' field.
  9. Select 'Interim Batch' in the 'All Clients Or Interim Billing Batch' field.
  10. Choose the Interim batch from the 'Interim Batch Number' drop-down field.
  11. Select 'No' for the 'Create Claims' field.
  12. Enter the date value for the 'First Date Of Service To Include' and 'Last Date Of Service To Include' fields (Should cover the services that you want to run the bill for).
  13. Select 'All' for the 'Include Primary and/or Secondary Billing' field.
  14. Select the 'Process' button.
  15. Will get the dialogue for the confirmation that says 'Compile Complete'.
  16. Select 'OK'.
  17. Select 'Dump File' in the 'Billing Option' field.
  18. Click 'Print' in the 'Print Or Delete Report' field.
  19. Select 'File' from the drop-down.
  20. Click the 'Print 837 Report' button.
  21. Select the 'Process' button.
  22. Verify that the Billing report file launched without any error.
  23. Validate that the LX order shown in the file is based on the preferred LX order configured in the Guarantors/Payors- Claim Order section.
Guarantors/Payors form-Specify LX Order-Electronic Billing 837 Sort
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
  • Electronic Billing
Scenario 1: 837 Institutional - Registry Setting 'Specify LX Order On A Claim'
Specific Setup:
  • Registry Setting:
  • 'Specify LX Order On A Claim' is added to the system and defaults to 'N'.
  • Set the registry setting to 'Y' and submit the form.
  • Client A:
  • Has unclaimed services, for different service codes, that can be billed on the 837 Institutional.
  • Use 'Client Ledger' to note the service codes, dates of service, financial class, and guarantor.
  • Use 'Service Fee/Cross Reference Maintenance' to note the Revenue Code.
  • Create Interim Batch.
  • Close the charges using 'Close Charges'.
  • Guarantors/Payors:
  • Claim Order definition exists by service code or revenue code. Note the order.
Steps
  1. Open the 'Electronic Billing' form.
  2. Select the 'Billing Form' as 837-Institutional.
  3. Select the 'Type Of Bill'.
  4. Select the 'Individual Or All Guarantors'.
  5. Select the 'Guarantor'.
  6. Select the 'Billing Type'.
  7. Select 'Sort File' in the 'Billing Option' field.
  8. Enter any desired value in the 'File Description' field.
  9. Select 'Interim Batch' in the 'All Clients Or Interim Billing Batch' field.
  10. Choose the Interim batch from the 'Interim Batch Number' drop-down field.
  11. Select 'No' for the 'Create Claims' field.
  12. Enter the date value for the 'First Date Of Service To Include' and 'Last Date Of Service To Include' fields (Should cover the services that you want to run the bill for).
  13. Select 'All' for the 'Include Primary and/or Secondary Billing' field.
  14. Select the 'Process' button.
  15. Validate that the confirmation message contains: ‘Compile Complete'.
  16. Select 'OK'.
  17. Select 'Dump File' in the 'Billing Option' field.
  18. Click 'Print' in the 'Print Or Delete Report' field.
  19. Select 'File' from the drop-down.
  20. Click the 'Print 837 Report' button.
  21. Select the 'Process' button.
  22. Verify that the Dump file launched without any error.
  23. Validate that the LX order shown in the file is based on the preferred LX order configured in the Guarantors/Payors- Claim Order section.
Scenario 2: 837 Professional - Registry Setting 'Specify LX Order On A Claim'
Specific Setup:
  • Registry Setting:
  • 'Specify LX Order On A Claim' is added to the system and defaults to 'N'.
  • Set the registry setting to 'Y' and submit the form.
  • Client A:
  • Has unclaimed services, for different service codes, that can be billed on the 837 Professional.
  • Use 'Client Ledger' to note the service codes, dates of service, financial class, and guarantor.
  • Use 'Service Fee/Cross Reference Maintenance' to note the Revenue Code.
  • Create Interim Batch.
  • Close the charges using 'Close Charges'.
  • Guarantors/Payors:
  • Claim Order definition exists by service code or revenue code. Note the order.
Steps
  1. Open the 'Electronic Billing' form.
  2. Select the 'Billing Form' as 837-Professional.
  3. Select the 'Type Of Bill'.
  4. Select the 'Individual Or All Guarantors'.
  5. Select the 'Guarantor'.
  6. Select the 'Billing Type'.
  7. Select 'Sort File' in the 'Billing Option' field.
  8. Enter any desired value in the 'File Description' field.
  9. Select 'Interim Batch' in the 'All Clients Or Interim Billing Batch' field.
  10. Choose the Interim batch from the 'Interim Batch Number' drop-down field.
  11. Select 'No' for the 'Create Claims' field.
  12. Enter the date value for the 'First Date Of Service To Include' and 'Last Date Of Service To Include' fields (Should cover the services that you want to run the bill for).
  13. Select 'All' for the 'Include Primary and/or Secondary Billing' field.
  14. Select the 'Process' button.
  15. Will get the dialogue for the confirmation that says 'Compile Complete'.
  16. Select 'OK'.
  17. Select 'Dump File' in the 'Billing Option' field.
  18. Click 'Print' in the 'Print Or Delete Report' field.
  19. Select 'File' from the drop-down.
  20. Click the 'Print 837 Report' button.
  21. Select the 'Process' button.
  22. Verify that the Billing report file launched without any error.
  23. Validate that the LX order shown in the file is based on the preferred LX order configured in the Guarantors/Payors- Claim Order section.
Topics
• Guarantor/Payors • Web Services • NX • Registry Settings • 837 Institutional • 837 Professional
Update 118 Summary | Details
All Documents Widget - Risk Level Update
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (CWS)
  • Site Specific Section Modeling (PM)
  • Admission (Outpatient)
  • Risk Level Update
  • View Definition
  • NX View Definition
  • All Documents Widget Definition
  • Chart Review
Scenario 1: Risk Level Update - Field Validations
Specific Setup:
  • Enable the registry setting "Enable Risk Level Functionality".
  • Add the risk levels of "Low" and "High" to the dictionary elements numbers 3100, 3101, 3102. Associate the dictionaries through extended dictionary values.
  • Using "Site Specific Section Modeling" add an "SS Admission Dictionary" field to an Admission form. In the "Product Custom Logic" field, select "Use as Risk Level".
Steps
  1. Using the admission form that has the field that was added via the "Site Specific Section Modeling" form
  2. Admit a client
  3. Select "Low" in the site specific modeling field that was added for "Risk Level" value.
  4. Submit the form.
  5. Open the "Risk Level Update" form.
  6. File a form changing the risk level.
  7. Validate the update row is created.
Scenario 2: All Document Widget - Validate Risk Level Update
Specific Setup:
  • Using the "All Documents Widget Definition" form:
  • Add "Risk Level Update" form to a widget.
  • Enable the registry setting "Enable Risk Level Functionality".
  • Give the user access to the "Risk Level Update" form.
  • Set up the Dictionary elements for the "Client" file.
  • Set up codes for different values for instance "High" and "Low" in dictionary 3100, 3101 and 3102.
  • Set up Reasons for Change to risk level in dictionary 3103.
  • Also set up the extended dictionary data elements for each dictionary value.
  • Using "Site Specific Section Modeling":
  • Add a site specific Admission dictionary field for the initial setting of the "Risk Level".
  • This field is being added to the Admission form so initial "Risk Level" value can be established at admission.
  • Designate "Use as Risk Level" in "Product Custom Logic".
  • Admit a test client and populate the field added to the form for the initial "Risk Level" value.
  • Add the "All Documents Widget" to the user's home view.
  • Add the "Risk Level Update" form to the "Chart Review" form.
Steps
  1. Open the "Risk Level Update" form for the test client.
  2. Change the "Risk Level" to a level different from what it is currently.
  3. Navigate to the view set up for the "All Documents Widget".
  4. Select the "Risk Level Update" section of the "All Documents Widget".
  5. Validate the row that was added via the "Risk Level Update" form appears.
  6. Select that row.
  7. Validate it displays in the "Console Widget Viewer".
  8. Click "Open Record" in the "Console Widget Viewer".
  9. Add a new row to the "Risk Level Update" table.
  10. Close out the form.
  11. Return to the "All Documents Widget".
  12. Return to the "Risk Level Update" section.
  13. Click "New Record".
  14. Enter a new "Risk Level Update" row.
  15. Validate the newly added row appears in the "All Documents Widget".
  16. Open the "Chart Review" form.
  17. Select the test client.
  18. Select "Risk Level Update" from the list of documents.
  19. Validate the appropriate number of rows appear under the appropriate episode.
  20. Edit a row of data.
  21. Return to the chart.
  22. Refresh the chart.
  23. Validate the changed data.
  24. Add a row of "Risk Level Update" via the chart.
  25. Return to the chart.
  26. Refresh the chart.
  27. Validate the row of data was added to the chart.
All Documents Widget - Managed Care Authorizations
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Chart Review
  • Risk Level Update
  • Financial Eligibility
  • Managed Care Authorizations
  • Admission
Scenario 1: Chart Review - Risk Level Update
Specific Setup:
  • Tester must add the "Risk Level Update" form to the "Chart Review" form.
  • Registry Setting "Enable Risk Level Functionality" is enabled.
  • Tester must give the Avatar User access to the "Risk Level Update".
Steps
  1. Open "Chart Review" form.
  2. Open the "Risk Level Update" form on the chart.
  3. Click "Add".
  4. Update a client's risk level.
  5. Click "Submit" to file data and return to the chart.
  6. Click "Refresh".
  7. Validate the updated risk level data displays at it was entered.
  8. Click "Edit".
  9. Edit a client's risk level.
  10. Validate the edited risk level data displays as it was entered.
Scenario 2: All Documents Widget - Managed Care Authorizations
Specific Setup:
  • Admit a test client into any episode.
  • Be sure to populate the social security number.
  • Using "Financial Eligibility", assign a guarantor to the test client.
  • Using the "Managed Care Authorizations" form:
  • Enter an authorization for the test client.
  • Using the "All Documents Widget Definition" form:
  • Add "Managed Care Authorizations" to the widget.
  • Add the "All Documents Widget" to the user's home view or an associated view.
Steps
  1. Open the "Managed Care Authorizations" form.
  2. Enter a managed care authorization record for the guarantor assigned to the test client via "Financial Eligibility".
  3. Submit to file data.
  4. Navigate to the view with the "All Documents Widget" where "Managed Care Authorizations" data can be accessed.
  5. Navigate to the "Managed Care Authorizations" sections.
  6. Validate the client's managed care data is present.
  7. Click "Open" to open the document in the "Console Widget Viewer".
  8. Validate the document displays appropriately in the "Console Widget Viewer".
  9. Click "Open Record".
  10. Edit the data in the record.
  11. Close the record.
  12. Click "Refresh" on the "All Documents Widget".
  13. Click "New Record".
  14. Add a new "Managed Care Authorization" row.
  15. Return to the "All Documents Widget".
  16. Click "Refresh" on the "All Documents Widget".
  17. Validate the document displays appropriately in the "Console Widget Viewer".
Topics
• Risk Level Update • NX • Console Widget • Managed Care Authorizations • Widgets
Update 119 Summary | Details
Program maintenance
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • File Import
  • Crystal Report Viewer
  • Program Maintenance
Scenario 1: File Import of Program Maintenance file type - Reject special characters except dashes in new program codes
Specific Setup:
  • Import file for the "Program Maintenance" file type which contains program codes with an apostrophe.
  • Import file for the "Program Maintenance" file type which contains program codes with another special character on the keyboard except the dash.
  • Import file for the "Program Maintenance" file type which contains program codes with a dash.
  • Import file for the "Program Maintenance" file type which contains program codes with no special characters.
Steps
  1. Open the 'File Import' form.
  2. Select "Program Maintenance" in the 'File Type' field.
  3. Upload the import file for the selected "Program Maintenance" file type.
  4. Compile the uploaded file.
  5. Verify the compile was not successful and the generated errors are visible via the error report.
  6. Select "Print Errors" to generate the Program Maintenance File Import Errors report.
  7. Verify the following message was generated "Cannot contain special characters except dashes (-)".
  8. Upload another import file containing a program code with another special character on the keyboard except the dash.
  9. Compile the uploaded file.
  10. Verify the compile was not successful and the generated errors are visible via the error report.
  11. Select "Print Errors" to generate the Program Maintenance File Import Errors report.
  12. Verify the following message was generated "Cannot contain special characters except dashes (-)".
  13. Upload another import file containing a program code with a dash.
  14. Compile the uploaded file.
  15. Verify the compile was successful.
  16. Upload another import file containing a program code with no special characters.
  17. Compile the uploaded file.
  18. Verify the compile was successful.
Scenario 2: File Import - 'Program Maintenance' file - Edit program.
Specific Setup:
  • A 'Program Maintenance' file import file is created that contains the information for the 'Billing Provider NPI' and ‘Type of Bill (First Two Digits)’ fields along with all other required fields.
Steps
  1. Open the "File Import" form.
  2. Select the 'Program Maintenance' File Type.
  3. Compile the program maintenance file import file created in the setup section.
  4. Verify that the file compiles successfully.
  5. Select the 'Print File' option and review the report.
  6. Verify that the ‘Billing Provider NPI’ and ‘Type of Bill (First Two Digits)’ fields are added to the report, and it displays the correct data entered in the file import file.
  7. Post the file which is compiled successfully in step #1c.
  8. Verify that the file posts successfully.
  9. Select the "Print File" option and review the report.
  10. Verify that the ‘Billing Provider NPI’ and ‘Type of Bill (First Two Digits)’ fields are added to the report, and it displays the correct data entered in the file import file.
  11. Open the 'Program Maintenance' form.
  12. Click "Edit" in the 'Add/Edit' field to select the program imported in step #1.
  13. Verify the ‘Billing Provider NPI’ and ‘Type of Bill (First Two Digits)’ fields are added to the program correctly.
Scenario 3: The file import process is updated to support the new field 'Preferred Diagnosis Classification' while importing a program maintenance file to add/edit a program.
Specific Setup:
  • Set the 'Enable Diagnosis Filtering based on Classification' registry setting to "Y".
  • The file import text file 'Testing Preferred Diagnosis 1' is created to add the program (i.e. Testing Diagnosis Classification) with the new field 'Preferred Diagnosis Classification' in that program (i.e. The dictionary codes 5&6 will be added for the Environmental and Medical classification at the 'Preferred Diagnosis Classification' field position in the text file).
Steps
  1. Open the "File Import" form.
  2. Select the 'Program Maintenance' File Type.
  3. Compile the program maintenance file import file created in the setup section.
  4. Verify that the file compiles without any error.
  5. Select the 'Print File' option and review the report.
  6. Verify that the 'Preferred Diagnosis Classification' field is added to the compile report, and it displays the correct classifications entered in the file import file.
  7. Post the file which is compiled successfully in step #1c.
  8. Verify that the file posts without any error.
  9. Select the "Print File" option and review the report.
  10. Verify that the 'Preferred Diagnosis Classification' field is added to the compile report, and it displays the correct classifications entered in the file import file.
  11. Open the 'Program Maintenance' form.
  12. Click "Edit" in the 'Add/Edit' field to edit the program imported in step #1.
  13. Verify the ' 'Preferred Diagnosis Classification'' field is added to the form and populated correctly.
Scenario 4: File Import - 'Program Maintenance' file - Add program.
Specific Setup:
  • A 'Program Maintenance' file import file is created with the required field values.
Steps
  1. Open the "File Import" form.
  2. Select the "Program Maintenance" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Select the "File A".
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select the "File A" in the 'Files(s)' field.
  8. Click [Process Action].
  9. Validate an Information message is displayed stating: Compiled
  10. Click [OK].
  11. Select "Print File" in the 'Action' field.
  12. Select the "File A" in the 'Files(s)' field.
  13. Click [Process Action].
  14. Validate the Report Viewer displays the contents of the file.
  15. Click [Close Report].
  16. Select "Post File" in the 'Action' field.
  17. Click [Process Action].
  18. Select the "File A".
  19. Validate an Information message is displayed stating: Posted.
  20. Click [OK] and close the form.
  21. Open the "Program Maintenance" form.
  22. Click [Edit].
  23. Validate the form is filed with the data based on the uploaded file.
  24. Close the form.
Program maintenance
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • File Import
  • Program Maintenance
  • Crystal Report Viewer
Scenario 1: File Import - 'Program Maintenance' file - Edit program.
Specific Setup:
  • A 'Program Maintenance' file import file is created that contains the information for the 'Billing Provider NPI' and ‘Type of Bill (First Two Digits)’ fields along with all other required fields.
Steps
  1. Open the "File Import" form.
  2. Select the 'Program Maintenance' File Type.
  3. Compile the program maintenance file import file created in the setup section.
  4. Verify that the file compiles successfully.
  5. Select the 'Print File' option and review the report.
  6. Verify that the ‘Billing Provider NPI’ and ‘Type of Bill (First Two Digits)’ fields are added to the report, and it displays the correct data entered in the file import file.
  7. Post the file which is compiled successfully in step #1c.
  8. Verify that the file posts successfully.
  9. Select the "Print File" option and review the report.
  10. Verify that the ‘Billing Provider NPI’ and ‘Type of Bill (First Two Digits)’ fields are added to the report, and it displays the correct data entered in the file import file.
  11. Open the 'Program Maintenance' form.
  12. Click "Edit" in the 'Add/Edit' field to select the program imported in step #1.
  13. Verify the ‘Billing Provider NPI’ and ‘Type of Bill (First Two Digits)’ fields are added to the program correctly.
Scenario 2: File Import - 'Program Maintenance' file - Add program.
Specific Setup:
  • A 'Program Maintenance' file import file is created with the required field values.
Steps
  1. Open the "File Import" form.
  2. Select the "Program Maintenance" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Select the "File A".
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select the "File A" in the 'Files(s)' field.
  8. Click [Process Action].
  9. Validate an Information message is displayed stating: Compiled
  10. Click [OK].
  11. Select "Print File" in the 'Action' field.
  12. Select the "File A" in the 'Files(s)' field.
  13. Click [Process Action].
  14. Validate the Report Viewer displays the contents of the file.
  15. Click [Close Report].
  16. Select "Post File" in the 'Action' field.
  17. Click [Process Action].
  18. Select the "File A".
  19. Validate an Information message is displayed stating: Posted.
  20. Click [OK] and close the form.
  21. Open the "Program Maintenance" form.
  22. Click [Edit].
  23. Validate the form is filed with the data based on the uploaded file.
  24. Close the form.
Topics
• Program Maintenance • File Import • NX
Update 120 Summary | Details
Guarantor Fee Definition: File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
  • Service Codes
  • File Import
  • Service Fee/Cross Reference Maintenance
  • Crystal Report Viewer
  • Service Fee/Cross Reference and Guarantor Definition Export
Scenario 1: File Import - Service Guarantor Definitions
Specific Setup:
  • Note: This functionality is for any service code type, including CCBHC service codes.
  • Please contact your Netsmart representative to enable CCBHC Billing functionality, if desired.
  • CCBHC setup has been completed.
  • The 'Avatar_PM_File_Import_Record_Layouts' spreadsheet is included in the update zip file to assist in creating the 'Service Guarantor Definitions' file to import.
  • Identify an existing service code.
  • Create a 'File Import' for the 'Service Guarantor Definition' file type that contains the service code. Note the value of each field included in the file.
Steps
  1. Open 'File Import'.
  2. Select Service Guarantor Definitions’ in 'File Type'.
  3. Load, compile and post the file.
  4. Open 'Service Fee/Cross Reference Maintenance', 'Guarantor Definitions', and review the imported record in edit mode.
  5. Validate that all values equal the values in the imported file.
  6. Click [Guarantor Definitions Report].
  7. Validate that guarantor information is correct for the service code.
  8. Close the report.
  9. Close the form.
Scenario 2: File Import - Guarantor Definitions
Specific Setup:
  • Set the registry setting "Import Process Type" to "FU&GU".
  • Using the "Service Codes" form, add a new service code for testing purposes.
  • Create a delimited file to be used for the service code guarantor definition file import.
  • Set the registry setting "Import File Delimiter" to the desired value to match the format of the delimited file created in the previous steps.
Steps
  1. Open the "File Import" form.
  2. Import the service fee import file created in setup.
  3. Process a file through file upload, compile and posting processes.
  4. Open the "Service Fee/Cross Reference Maintenance" form.
  5. Navigate to the "Guarantor Definition" section.
  6. Validate the data from the import file is displayed in the form.
Scenario 3: File Import - Service Guarantor Definitions - 'Import Process Type' Registry Setting
Specific Setup:
  • Registry Settings:
  • The 'Avatar PM->System Maintenance->File Import->->->Import Process Type'' has the following values: 'FU&GU'.
  • Service Fee/Cross Reference and Guarantor Definition Export has been used to export the 'Guarantor Definition. Select a service code with a definition to update.
  • File Import:
  • A 'Service Guarantor Definition' file exists to update the guarantor fee for the service code.
Steps
  1. Open 'File Import'.
  2. Select 'Service Guarantor Definitions' in 'File Type'.
  3. Upload/compile/post the 'Service Guarantor Definition' file.
  4. Open 'Service Fee/Cross Reference Maintenance'.
  5. Select the 'Guarantor Definitions' section.
  6. Click [Guarantor Definitions Report].
  7. Validate that the fee for the service code was updated.
  8. Close the report.
  9. Select the 'Restore Definitions' section.
  10. Click [Restore Maximum Liability Assignment Definition That Existed Prior to Last File Import].
  11. Select the 'Guarantor Definitions' section.
  12. Click [Guarantor Definitions Report].
  13. Validate that the fees were restored.
Payment/Adjustment Overpayments: File import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Posting/Adjustment Codes Definition
  • Create Interim Billing Batch File
  • Electronic Billing
  • Client Ledger
  • File Import
  • Crystal Report Viewer
  • Payment Acknowledgement
  • Admission (Outpatient)
  • Diagnosis
  • Financial Eligibility
  • Client Charge Input
Scenario 1: File Import - Validate Payment/Adjustment import files
Specific Setup:
  • Registry Settings:
  • Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement = Y.
  • Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged = 3, at a minimum.
  • Avatar PM->System Maintenance->File Import->->->Import File Delimiter – note the value to be used when creating the file to import.
  • Posting/Adjustment Codes Definition has been used to note a payment code.
  • Client A: Client is identified that has multiple unpaid claims.
  • Note the guarantor, service code, service date, claim number and the line balance.
  • Payment Acknowledgement has been used to create a minimum of one acknowledged payment for the same guarantor as the client’s guarantor. Note the transaction number this is included in the ‘Payment Acknowledgement’ message.
  • Create a file to import to the Payment/Adjustment Posting option and includes the transaction number.
  • The File Import spreadsheet will be included in the zip file.
Steps

1. Open the "File Import" form.

2. Select "File Type" of "Payments/Adjustment Posting".

3. Select "Action" of "Upload New File".

4. Click "Process Action".

5. Select "Action" of "Compile/Validate File".

6. Select the file that was just uploaded in "File(s)".

7. Click "Process Action".

8. Click “OK” on the “Compiled” message.

9. Select "Action" of "Post File".

10. Select the file that was just compiled in "File(s)".

11. Click "Process Action".

12. Click “OK” on the “Posted” message.

13. Close the form.

14. Open the "Client Ledger" form.

15. Process the client ledger.

16. Validate the payment information is reflected in the client's ledger.

17. Close the form.

Scenario 2: File Import - Payment Adjustment - Registry Setting: Post Full Amount When Processing Payment Adjustment Posting File Import File
Specific Setup:
  • The registry setting 'Import File Delimiter' is enabled with desired value.
  • File Import:
  • A file import file of 'Payment Adjustment' file type is created to add a new posting code.
Steps

1. Open the "File Import" form.

2. Select "File Type" of "Payments/Adjustment Posting".

3. Select "Action" of "Upload New File".

4. Click "Process Action".

5. Select "Action" of "Compile/Validate File".

6. Select the file that was just uploaded in "File(s)".

7. Click "Process Action".

8. Click “OK” on the “Compiled” message.

9. Select "Action" of "Post File".

10. Select the file that was just compiled in "File(s)".

11. Click "Process Action".

12. Click “OK” on the “Posted” message.

13. Close the form.

14. Open the "Client Ledger" form.

15. Process the client ledger.

16. Validate the payment information is reflected in the client's ledger.

17. Close the form.

Service Fee/Cross Reference Maintenance: Allows users to edit service fee
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
  • Service Codes
  • Service Fee/Cross Reference Maintenance
  • CPT Code Definition (PM)
Scenario 1: Service Fee/Cross Reference Maintenance - Add/Edit Guarantor Definitions
Specific Setup:
  • Please contact your Netsmart representative to enable CCBHC Billing functionality.
  • CCBHC setup has been completed.
  • An existing 'Service Code' is identified.
  • An existing 'Guarantors'Payors' is identified.
Steps
  1. Open 'Service Fee/Cross Reference Maintenance'.
  2. Set the Section 'Guarantor Definition'.
  3. Select 'Enter New' in 'Enter New Or Edit Existing'.
  4. Enter the 'Service Code'
  5. Enter the 'From Date'.
  6. Select the 'Guarantor'.
  7. Enter data for all desired fields, noting the values.
  8. Click [Submit].
  9. Click [Yes].
  10. Edit the same guarantor and service code combination in 'Guarantor Definition'.
  11. Review the data in each field to validate that it matches the value that was entered.
Scenario 2: Service Fee/Cross Reference Maintenance - Add/Edit Service Fee Definition
Specific Setup:
  • Service Codes:
  • Add a new service code for testing purposes (Service Code A).
  • CPT Code Definition:
  • A CPT Code must be defined (CPT Code A).
Steps
  1. Access the ‘Service Fee/Cross Reference Maintenance’ form.
  2. Select "Enter New" in the ‘Enter New Or Edit Existing Fee/Cross Reference’ field.
  3. Enter "Service Code A" in the 'Service Code' field.
  4. Enter the desired date in the ‘From Date’ field.
  5. Enter the desired value in the 'Fee' field.
  6. Enter "CPT Code A" in the 'CPT-4 / HCPCS Code' field.
  7. Enter desired value with quotation marks into the 'CPT-4 / HCPCS Modifier' field.
  8. Click [Submit].
  9. Click [Yes].
  10. Select "Edit Existing" in the ‘Enter New Or Edit Existing Fee/Cross Reference’ field.
  11. Enter "Service Code A" in the 'Service Code' field.
  12. Enter the same date in the ‘From Date’ field.
  13. Click [Select Fee/Cross Ref To Edit/Default From Existing Row].
  14. Select the desired row that filed in above steps.
  15. Click [OK].
  16. Validate that the entered 'Fee' exists.
  17. Validate that the entered 'CPT-4 / HCPCS Code' exists.
  18. Validate that the selected ‘CPT-4 / HCPCS Modifier’ exists.
  19. Close the form.
  20. Access the ‘Service Fee/Cross Reference Maintenance’ form.
  21. Select "Enter New" in the ‘Enter New Or Edit Existing Fee/Cross Reference’ field.
  22. Enter "Service Code A" in the 'Service Code' field.
  23. Enter the same date entered in the previous steps in the 'From Date' field.
  24. Click [Submit].
  25. Validate a dialog is displayed stating, "Fee Definition already exists, please edit the existing definition".
  26. Click [OK].
  27. Validate the dialog closes.
  28. Validate a 'Filing Error' dialog stating, "Filing aborted" is received.
  29. Click [OK].
  30. Validate the form is still open with the data entered in the previous steps.
  31. Close the form.
Topics
• Service Fee/Cross Reference Maintenance • File Import • Service Fee/Cross Reference and Guarantor Definition Export • NX
Update 122 Summary | Details
File Import - Room Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • File Import
  • Crystal Report Viewer
  • Room Definition
Scenario 1: File Import : Room Definition Add/Edit
Specific Setup:
  • Registry Setting
  • Set the 'Enable Room Scheduling' registry setting to "Y"
  • File import
  • A file import file of 'Room Definition' file type is created to add a new room definition.
  • A file import file of 'Room Definition' file type is created to edit the above room definition.
Steps
  1. Open the "File Import" form.
  2. Select the 'Room Definition' File Type.
  3. Click on 'Upload New File' radio button.
  4. Select file for 'Add' room definition.
  5. Compile the 'Add' room definition file.
  6. Verify that the file compiles without any error.
  7. Post the file.
  8. Verify that the file posts without any error.
  9. Close the report.
  10. Close the form.
  11. Select the 'Print File' option and review the report.
  12. Open the 'Room Definition' form.
  13. Verify all data imported correctly.
  14. Follow step 1-13 for 'Edit' room definition file.
File Import - Resource Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • File Import
  • Resource Definition
  • Crystal Report Viewer
Scenario 1: File Import : Resource Definition Add/Edit
Specific Setup:
  • Dictionary Update
  • Select "Appointment Other Tabled Files" from the File dropdown list.
  • Select "(1505) Resource Type" from the Data Element list box.
  • Add new 'Resource Type' dictionary code.
  • File import
  • A file import file of 'Resource Definition' file type is created to add a new resource definition.
  • A file import file of 'Resource Definition' file type is created to edit the above resource definition.
Steps
  1. Open the "File Import" form.
  2. Select the 'Resource Definition' File Type.
  3. Click on 'Upload New File' radio button.
  4. Select file for 'Add' resource definition.
  5. Compile the 'Add' resource definition file.
  6. Verify that the file compiles without any error.
  7. Post the file.
  8. Verify that the file posts without any error.
  9. Select the 'Print File' option and review the report.
  10. Close the report.
  11. Close the form.
  12. Open the 'Resource Definition' form.
  13. Verify all data imported correctly.
  14. Follow step 1-13 for 'Edit' resource definition file.
Topics
• File Import
Update 130 Summary | Details
SYSTEM.billing_tx_history - SQL table validation after edit service information
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission (Outpatient)
  • Financial Eligibility
  • Client Charge Input
  • Client Ledger
Scenario 1: SYSTEM.billing_tx_charge_totals - Validating table after submission of the 'Edit Service Information' form.
Specific Setup:
  • Registry Settlings:
  • The 'Avatar PM->Billing->->->->Enable California Billing' registry setting is set to 'Y'.
  • Guarantors/Payors:
  • An existing guarantor is identified to be used. Note the guarantor's code/name.
  • Service codes:
  • An existing individual service code is identified to be used. Note the service code/description.
  • Service Fee/ Cross Reference Maintenance:
  • A fee definition is created for the service code identified in the ' Service Codes' form.
  • Admission:
  • An existing client is identified, or a new client is admitted. Note client's 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 individual service code. Note service date, service code.
  • Client Ledger:
  • A service distributed correctly to the assigned guarantor and the status of the service is 'Open'.
Steps
  1. Open option 'Edit Service Information'.
  2. Fill in all required fields using any data.
  3. Click [Select Service(s) To Edit].
  4. Select any service date (if more than one).
  5. Click [OK].
  6. Change the value in 'Duration' (or any field).
  7. Click [Submit].
  8. Verify the form submitted successfully.
  9. Open the 'Crystal report' or any other SQL data viewer.
  10. Query the 'SYSTEM.billing_tx_charge_total' table for the PATID and service from the setup section.
  11. Verify the system retrieves data successfully.
Scenario 2: SYSTEM.billing_tx_history - Validating SQL table after editing the group or individual service codes
Specific Setup:
  • Registry Settlings:
  • The 'Avatar PM->Billing->->->->Enable California Billing' registry setting is set to 'Y'.
  • Guarantors/Payors:
  • An existing guarantor is identified to be used. Note the guarantor's code/name.
  • Service codes:
  • An existing individual and group service codes are identified to be used. Note the service code/description.
  • Service Fee/ Cross Reference Maintenance:
  • A fee definition is created for the service code identified in the ' Service Codes' form.
  • Admission:
  • An existing client is identified, or a new client is admitted. Note client's 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:
  • At least two services are rendered to the client using the group service code and the individual service code. Note service date, service code.
  • Client Ledger:
  • A service distributed correctly to the assigned guarantor and the status of the service is 'Open'.
  • Crystal Report or any other SQL data viewer:
  • Look for the number_of_clients field in the 'SYSTEM.billing_tx_history'. Note the value from the number_of_clients field.
Steps
  1. Open the 'Edit Service Information' form.
  2. Fill in all required fields using any data.
  3. Click [Select Service(s) To Edit].
  4. Select the service date of the group service.
  5. Click [OK].
  6. Edit the group service code to the same group code or the different group service code.
  7. Verify a pop-up: 'Enter The Number Of Clients In The Group'.
  8. Enter any number which is different from the original.
  9. Click [Submit].
  10. Verify the form submitted successfully.
  11. Click [Y] at the 'Return to the Form' pop-up.
  12. Do not close the form. Leave the form open.
  13. Open the 'Crystal report' or any other SQL data viewer.
  14. Query the 'SYSTEM.billing_tx_history' table for the PATID and service from the setup section.
  15. Verify the number_of_clients field in the 'SYSTEM.billing_tx_history' table updated correctly with the number entered at the time of editing the service.
  16. Go back to the 'Edit Service Information' form again.
  17. Fill in all required fields using any data.
  18. Click [Select Service(s) To Edit].
  19. Select the service date for the individual service.
  20. Click [OK].
  21. Edit the duration or anything else for the individual service.
  22. Click [Submit].
  23. Verify the form submitted successfully.
  24. Open the 'Crystal report' or any other SQL data viewer.
  25. Query the 'SYSTEM.billing_tx_history' table for the PATID and service from the setup section.
  26. Verify the number_of_clients field in the 'SYSTEM.billing_tx_history' table does not update for the individual service.
  27. Close the report.
Topics
• Edit Service Information • NX • Database Tables
Update 134 Summary | Details
Registry setting - Enable Program Search
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CPT Code Definition (PM)
  • Service Codes
  • Service Fee/Cross Reference Maintenance
  • Program Maintenance
  • Admission (Outpatient)
  • Admission
  • Electronic Billing
  • Create Interim Billing Batch File
  • Practitioner Numbers By Guarantor And Program
  • Print Bill
  • Re-Print Bill
  • Crystal Self Pay Bill
  • Back Dated Admission/Discharge
  • Spreadsheet Batch Remittance Posting
  • Remittance Post Confirmation
Scenario 1: Service Fee/Cross Reference Maintenance - Add/Edit Service Fee Definition
Specific Setup:
  • Service Codes:
  • A new service code is added. Note the service code and description.
  • CPT Code Definition:
  • A CPT Code definition is defined or an existing CPT Code definition is identified.
Steps
  1. Open the ‘Service Fee/Cross Reference Maintenance’ form.
  2. Select ‘Enter New’ in the ‘Enter New Or Edit Existing Fee/Cross Reference’ field.
  3. Enter desired service code in the 'Service Code' field.
  4. Enter desired date in the ‘From Date’ field.
  5. Enter the desired value in the 'Fee' field.
  6. Enter the desired code in the 'CPT-4 / HCPCS Code' field.
  7. Enter desired value with quotation marks into the 'CPT-4 / HCPCS Modifier' field.
  8. Click [Submit].
  9. Click [Yes].
  10. Select ‘Edit Existing’ in the ‘Enter New Or Edit Existing Fee/Cross Reference’ field.
  11. Enter desired service code in the 'Service Code' field.
  12. Enter desired date in the ‘From Date’ field.
  13. Click [Select Fee/Cross Ref To Edit/Default From Existing Row].
  14. Select the desired row that filed in above steps.
  15. Click [OK].
  16. Validate that the entered 'Fee' exists.
  17. Validate that the entered 'CPT-4 / HCPCS Code' exists.
  18. Validate that the selected ‘CPT-4 / HCPCS Modifier’ exists.
  19. Close the form.
  20. Access the ‘Service Fee/Cross Reference Maintenance’ form.
  21. Select ‘Enter New’ in the ‘Enter New Or Edit Existing Fee/Cross Reference’ field.
  22. Enter desired date in the 'Service Code' field.
  23. Enter the same date in the 'From Date' field.
  24. Click [Submit].
  25. Validate a dialog is displayed stating, ‘Fee Definition already exists, please edit the existing definition’.
  26. Click [OK].
  27. Validate the dialog closes.
  28. Validate a 'Filing Error' dialog stating, ‘Filing aborted’ is received.
  29. Click [OK].
  30. Validate the form is still open with the data as entered.
  31. Close the form.
Scenario 2: Enable Program Search - Validating field type in the forms when the registry setting is enabled
Steps
  1. Open the 'Registry Setting' form.
  2. Search for the 'Enable Program Search' registry setting.
  3. Set the registry setting value to '7&12'.
  4. Click [Submit].
  5. Verify the form submits successfully.
  6. Open the 'Spreadsheet Batch Remittance Posting' form.
  7. Verify the form opens successfully.
  8. Verify the 'Program' field displays as search field.
  9. Enter desire program code in the 'Program' field.
  10. Verify the system returns matching programs in the field.
  11. Enter desire program name in the 'Program' field.
  12. Verify the system returns matching programs in the field.
  13. Click [Discard].
  14. Open the 'Program Maintenance' form.
  15. Verify the form opens successfully.
  16. Select 'Add' option in the 'Add or Edit Program' field.
  17. Verify the 'Program' field displays as dictionary search field.
  18. Enter desire program code in the 'Program' field.
  19. Verify the system returns matching programs in the field.
  20. Enter desire program name in the 'Program' field.
  21. Verify the system returns matching programs in the field.
  22. Click [Discard].
  23. Open the 'Registry Setting' form.
  24. Search for the 'Enable Program Search' registry setting.
  25. Set the registry setting value to '1&2&3&4&576&7&8&9&10&11&12&13'.
  26. Click [Submit].
  27. Verify the 'Admission' and 'Admission (Outpatient)' forms open successfully.
  28. Verify the 'Program' field displays as search field.
  29. Enter desire program code in the 'Program' field.
  30. Verify the system returns matching programs in the field.
  31. Enter desire program name in the 'Program' field.
  32. Verify the system returns matching programs in the field.
  33. Click [Discard].
  34. Verify the 'Create Interim Billing Batch File' form opens successfully.
  35. Verify the 'Program(s)' field displays as search field.
  36. Enter desire program code in the 'Program' field.
  37. Verify the system returns matching programs in the field.
  38. Enter desire program name in the 'Program' field.
  39. Verify the system returns matching programs in the field.
  40. Click [Discard].
  41. Verify the 'Electronic Billing' form opens successfully.
  42. Verify the 'Print Bill' form opens successfully.
  43. Verify the 'Program(s)' field displays as search field.
  44. Enter desire program code in the 'Program' field.
  45. Verify the system returns matching programs in the field.
  46. Enter desire program name in the 'Program' field.
  47. Verify the system returns matching programs in the field.
  48. Click [Discard].
  49. Verify the 'Re-Print Bill' form opens successfully.
  50. Verify the 'Program(s)' field displays as search field.
  51. Enter desire program code in the 'Program' field.
  52. Verify the system returns matching programs in the field.
  53. Enter desire program name in the 'Program' field.
  54. Verify the system returns matching programs in the field.
  55. Click [Discard].
  56. Verify the 'Crystal Self Pay Bill' form opens successfully.
  57. Verify the 'Program(s)' field displays as search field.
  58. Enter desire program code in the 'Program' field.
  59. Verify the system returns matching programs in the field.
  60. Enter desire program name in the 'Program' field.
  61. Verify the system returns matching programs in the field.
  62. Click [Discard].
  63. Verify the 'Spreadsheet Batch Remittance Posting' form opens successfully.
  64. Verify the 'Program(s)' field displays as search field.
  65. Enter desire program code in the 'Program' field.
  66. Verify the system returns matching programs in the field.
  67. Enter desire program name in the 'Program' field.
  68. Verify the system returns matching programs in the field.
  69. Click [Discard].
  70. Verify the 'Service Fee/Cross Reference Maintenance' form opens successfully.
  71. Verify the 'Program(s)' field displays as search field.
  72. Enter desire program code in the 'Program' field.
  73. Verify the system returns matching programs in the field.
  74. Enter desire program name in the 'Program' field.
  75. Verify the system returns matching programs in the field.
  76. Click [Discard].
  77. Verify the 'Guarantor/Program Billing Defaults' form opens successfully.
  78. Verify the 'Program' field displays as search field.
  79. Enter desire program code in the 'Program' field.
  80. Verify the system returns matching programs in the field.
  81. Enter desire program name in the 'Program' field.
  82. Verify the system returns matching programs in the field.
  83. Click [Discard].
  84. Verify the 'Practitioner Numbers By Guarantor and Program' form opens successfully.
  85. Verify the 'Program(s)' field displays as search field.
  86. Enter desire program code in the 'Program' field.
  87. Verify the system returns matching programs in the field.
  88. Enter desire program name in the 'Program' field.
  89. Verify the system returns matching programs in the field.
  90. Click [Discard].
  91. Verify the 'Call Intake' form opens successfully.
  92. Verify the 'Program' field displays as search field.
  93. Enter desire program code in the 'Program' field.
  94. Verify the system returns matching programs in the field.
  95. Enter desire program name in the 'Program' field.
  96. Verify the system returns matching programs in the field.
  97. Click [Discard].
  98. Verify the 'Program Maintenance' form opens successfully.
  99. Verify the 'Program' field displays as search field.
  100. Enter desire program code in the 'Program' field.
  101. Verify the system returns matching programs in the field.
  102. Enter desire program name in the 'Program' field.
  103. Verify the system returns matching programs in the field.
  104. Click [Discard].
  105. Verify the 'Back Dated Admission/Discharge' form opens successfully.
  106. Verify the 'Program' field displays as search field.
  107. Enter desire program code in the 'Program' field.
  108. Verify the system returns matching programs in the field.
  109. Enter desire program name in the 'Program' field.
  110. Verify the system returns matching programs in the field.
  111. Click [Discard].
Scenario 3: Enable Program Search - Validating field type in the forms when the registry setting is disabled
Steps
  1. Open the 'Registry Setting' form.
  2. Search for the 'Enable Program Search' registry setting.
  3. Set the registry setting value to blank.
  4. Click [Submit].
  5. Verify the 'Admission' and 'Admission (Outpatient)' forms open successfully.
  6. Verify the 'Program' field displays as dropdown field.
  7. Select desire program in the 'Program' field.
  8. Click [Discard].
  9. Verify the 'Create Interim Billing Batch File' form opens successfully.
  10. Verify the 'Program' field displays as a listbox field.
  11. Select desire program in the 'Program' field.
  12. Click [Discard].
  13. Verify the 'Electronic Billing' form opens successfully.
  14. Verify the 'Program' field displays as a listbox field.
  15. Select desire program in the 'Program' field.
  16. Click [Discard].
  17. Open the 'Print Bill' form.
  18. Verify the 'Print Bill' form opens successfully.
  19. Verify the 'Program' field displays as a listbox field.
  20. Select desire program in the 'Program' field.
  21. Click [Discard].
  22. Open the 'Re-Print Bill' form.
  23. Verify the 'Re-Print Bill' form opens successfully.
  24. Verify the 'Program(s)' field displays as search field.
  25. Enter desire program code in the 'Program' field.
  26. Verify the system returns matching programs in the field.
  27. Enter desire program name in the 'Program' field.
  28. Verify the system returns matching programs in the field.
  29. Click [Discard].
  30. Open the 'Crystal Self Pay Bill' form.
  31. Verify the 'Crystal Self Pay Bill' form opens successfully.
  32. Verify the 'Program(s)' field displays as search field.
  33. Enter desire program code in the 'Program' field.
  34. Verify the system returns matching programs in the field.
  35. Enter desire program name in the 'Program' field.
  36. Verify the system returns matching programs in the field.
  37. Click [Discard].
  38. Open the 'Spreadsheet Batch Remittance Posting' form.
  39. Verify the 'Spreadsheet Batch Remittance Posting' form opens successfully.
  40. Verify the 'Program(s)' field displays as search field.
  41. Enter desire program code in the 'Program' field.
  42. Verify the system returns matching programs in the field.
  43. Enter desire program name in the 'Program' field.
  44. Verify the system returns matching programs in the field.
  45. Click [Discard].
  46. Open the 'Service Fee/Cross Reference Maintenance' form.
  47. Verify the 'Service Fee/Cross Reference Maintenance' form opens successfully.
  48. Verify the 'Program(s)' field displays as search field.
  49. Enter desire program code in the 'Program' field.
  50. Verify the system returns matching programs in the field.
  51. Enter desire program name in the 'Program' field.
  52. Verify the system returns matching programs in the field.
  53. Click [Discard].
  54. Open the 'Guarantor/Program Billing Defaults' form.
  55. Verify the 'Guarantor/Program Billing Defaults' form opens successfully.
  56. Verify the 'Program' field displays as search field.
  57. Enter desire program code in the 'Program' field.
  58. Verify the system returns matching programs in the field.
  59. Enter desire program name in the 'Program' field.
  60. Verify the system returns matching programs in the field.
  61. Click [Discard].
  62. Verify the 'Practitioner Numbers By Guarantor and Program' form opens successfully.
  63. Verify the 'Program(s)' field displays as search field.
  64. Enter desire program code in the 'Program' field.
  65. Verify the system returns matching programs in the field.
  66. Enter desire program name in the 'Program' field.
  67. Verify the system returns matching programs in the field.
  68. Click [Discard].
  69. Verify the 'Call Intake' form opens successfully.
  70. Verify the 'Program' field displays as search field.
  71. Enter desire program code in the 'Program' field.
  72. Verify the system returns matching programs in the field.
  73. Enter desire program name in the 'Program' field.
  74. Verify the system returns matching programs in the field.
  75. Click [Discard].
  76. Verify the 'Program Maintenance' form opens successfully.
  77. Verify the 'Program' field displays as search field.
  78. Enter desire program code in the 'Program' field.
  79. Verify the system returns matching programs in the field.
  80. Enter desire program name in the 'Program' field.
  81. Verify the system returns matching programs in the field.
  82. Click [Discard].
  83. Verify the 'Back Dated Admission/Discharge' form opens successfully.
  84. Verify the 'Program' field displays as search field.
  85. Enter desire program code in the 'Program' field.
  86. Verify the system returns matching programs in the field.
  87. Enter desire program name in the 'Program' field.
  88. Verify the system returns matching programs in the field.
  89. Click [Discard].
Registry setting - Enable Program Search
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CPT Code Definition (PM)
  • Service Codes
  • Service Fee/Cross Reference Maintenance
  • Program Maintenance
  • Admission (Outpatient)
  • Admission
  • Electronic Billing
  • Create Interim Billing Batch File
  • Practitioner Numbers By Guarantor And Program
  • Print Bill
  • Re-Print Bill
  • Crystal Self Pay Bill
  • Back Dated Admission/Discharge
  • Spreadsheet Batch Remittance Posting
  • Remittance Post Confirmation
Scenario 1: Service Fee/Cross Reference Maintenance - Add/Edit Service Fee Definition
Specific Setup:
  • Service Codes:
  • A new service code is added. Note the service code and description.
  • CPT Code Definition:
  • A CPT Code definition is defined or an existing CPT Code definition is identified.
Steps
  1. Open the ‘Service Fee/Cross Reference Maintenance’ form.
  2. Select ‘Enter New’ in the ‘Enter New Or Edit Existing Fee/Cross Reference’ field.
  3. Enter desired service code in the 'Service Code' field.
  4. Enter desired date in the ‘From Date’ field.
  5. Enter the desired value in the 'Fee' field.
  6. Enter the desired code in the 'CPT-4 / HCPCS Code' field.
  7. Enter desired value with quotation marks into the 'CPT-4 / HCPCS Modifier' field.
  8. Click [Submit].
  9. Click [Yes].
  10. Select ‘Edit Existing’ in the ‘Enter New Or Edit Existing Fee/Cross Reference’ field.
  11. Enter desired service code in the 'Service Code' field.
  12. Enter desired date in the ‘From Date’ field.
  13. Click [Select Fee/Cross Ref To Edit/Default From Existing Row].
  14. Select the desired row that filed in above steps.
  15. Click [OK].
  16. Validate that the entered 'Fee' exists.
  17. Validate that the entered 'CPT-4 / HCPCS Code' exists.
  18. Validate that the selected ‘CPT-4 / HCPCS Modifier’ exists.
  19. Close the form.
  20. Access the ‘Service Fee/Cross Reference Maintenance’ form.
  21. Select ‘Enter New’ in the ‘Enter New Or Edit Existing Fee/Cross Reference’ field.
  22. Enter desired date in the 'Service Code' field.
  23. Enter the same date in the 'From Date' field.
  24. Click [Submit].
  25. Validate a dialog is displayed stating, ‘Fee Definition already exists, please edit the existing definition’.
  26. Click [OK].
  27. Validate the dialog closes.
  28. Validate a 'Filing Error' dialog stating, ‘Filing aborted’ is received.
  29. Click [OK].
  30. Validate the form is still open with the data as entered.
  31. Close the form.
Scenario 2: Enable Program Search - Validating field type in the forms when the registry setting is enabled
Steps
  1. Open the 'Registry Setting' form.
  2. Search for the 'Enable Program Search' registry setting.
  3. Set the registry setting value to '7&12'.
  4. Click [Submit].
  5. Verify the form submits successfully.
  6. Open the 'Spreadsheet Batch Remittance Posting' form.
  7. Verify the form opens successfully.
  8. Verify the 'Program' field displays as search field.
  9. Enter desire program code in the 'Program' field.
  10. Verify the system returns matching programs in the field.
  11. Enter desire program name in the 'Program' field.
  12. Verify the system returns matching programs in the field.
  13. Click [Discard].
  14. Open the 'Program Maintenance' form.
  15. Verify the form opens successfully.
  16. Select 'Add' option in the 'Add or Edit Program' field.
  17. Verify the 'Program' field displays as dictionary search field.
  18. Enter desire program code in the 'Program' field.
  19. Verify the system returns matching programs in the field.
  20. Enter desire program name in the 'Program' field.
  21. Verify the system returns matching programs in the field.
  22. Click [Discard].
  23. Open the 'Registry Setting' form.
  24. Search for the 'Enable Program Search' registry setting.
  25. Set the registry setting value to '1&2&3&4&576&7&8&9&10&11&12&13'.
  26. Click [Submit].
  27. Verify the 'Admission' and 'Admission (Outpatient)' forms open successfully.
  28. Verify the 'Program' field displays as search field.
  29. Enter desire program code in the 'Program' field.
  30. Verify the system returns matching programs in the field.
  31. Enter desire program name in the 'Program' field.
  32. Verify the system returns matching programs in the field.
  33. Click [Discard].
  34. Verify the 'Create Interim Billing Batch File' form opens successfully.
  35. Verify the 'Program(s)' field displays as search field.
  36. Enter desire program code in the 'Program' field.
  37. Verify the system returns matching programs in the field.
  38. Enter desire program name in the 'Program' field.
  39. Verify the system returns matching programs in the field.
  40. Click [Discard].
  41. Verify the 'Electronic Billing' form opens successfully.
  42. Verify the 'Print Bill' form opens successfully.
  43. Verify the 'Program(s)' field displays as search field.
  44. Enter desire program code in the 'Program' field.
  45. Verify the system returns matching programs in the field.
  46. Enter desire program name in the 'Program' field.
  47. Verify the system returns matching programs in the field.
  48. Click [Discard].
  49. Verify the 'Re-Print Bill' form opens successfully.
  50. Verify the 'Program(s)' field displays as search field.
  51. Enter desire program code in the 'Program' field.
  52. Verify the system returns matching programs in the field.
  53. Enter desire program name in the 'Program' field.
  54. Verify the system returns matching programs in the field.
  55. Click [Discard].
  56. Verify the 'Crystal Self Pay Bill' form opens successfully.
  57. Verify the 'Program(s)' field displays as search field.
  58. Enter desire program code in the 'Program' field.
  59. Verify the system returns matching programs in the field.
  60. Enter desire program name in the 'Program' field.
  61. Verify the system returns matching programs in the field.
  62. Click [Discard].
  63. Verify the 'Spreadsheet Batch Remittance Posting' form opens successfully.
  64. Verify the 'Program(s)' field displays as search field.
  65. Enter desire program code in the 'Program' field.
  66. Verify the system returns matching programs in the field.
  67. Enter desire program name in the 'Program' field.
  68. Verify the system returns matching programs in the field.
  69. Click [Discard].
  70. Verify the 'Service Fee/Cross Reference Maintenance' form opens successfully.
  71. Verify the 'Program(s)' field displays as search field.
  72. Enter desire program code in the 'Program' field.
  73. Verify the system returns matching programs in the field.
  74. Enter desire program name in the 'Program' field.
  75. Verify the system returns matching programs in the field.
  76. Click [Discard].
  77. Verify the 'Guarantor/Program Billing Defaults' form opens successfully.
  78. Verify the 'Program' field displays as search field.
  79. Enter desire program code in the 'Program' field.
  80. Verify the system returns matching programs in the field.
  81. Enter desire program name in the 'Program' field.
  82. Verify the system returns matching programs in the field.
  83. Click [Discard].
  84. Verify the 'Practitioner Numbers By Guarantor and Program' form opens successfully.
  85. Verify the 'Program(s)' field displays as search field.
  86. Enter desire program code in the 'Program' field.
  87. Verify the system returns matching programs in the field.
  88. Enter desire program name in the 'Program' field.
  89. Verify the system returns matching programs in the field.
  90. Click [Discard].
  91. Verify the 'Call Intake' form opens successfully.
  92. Verify the 'Program' field displays as search field.
  93. Enter desire program code in the 'Program' field.
  94. Verify the system returns matching programs in the field.
  95. Enter desire program name in the 'Program' field.
  96. Verify the system returns matching programs in the field.
  97. Click [Discard].
  98. Verify the 'Program Maintenance' form opens successfully.
  99. Verify the 'Program' field displays as search field.
  100. Enter desire program code in the 'Program' field.
  101. Verify the system returns matching programs in the field.
  102. Enter desire program name in the 'Program' field.
  103. Verify the system returns matching programs in the field.
  104. Click [Discard].
  105. Verify the 'Back Dated Admission/Discharge' form opens successfully.
  106. Verify the 'Program' field displays as search field.
  107. Enter desire program code in the 'Program' field.
  108. Verify the system returns matching programs in the field.
  109. Enter desire program name in the 'Program' field.
  110. Verify the system returns matching programs in the field.
  111. Click [Discard].
Scenario 3: Enable Program Search - Validating field type in the forms when the registry setting is disabled
Steps
  1. Open the 'Registry Setting' form.
  2. Search for the 'Enable Program Search' registry setting.
  3. Set the registry setting value to blank.
  4. Click [Submit].
  5. Verify the 'Admission' and 'Admission (Outpatient)' forms open successfully.
  6. Verify the 'Program' field displays as dropdown field.
  7. Select desire program in the 'Program' field.
  8. Click [Discard].
  9. Verify the 'Create Interim Billing Batch File' form opens successfully.
  10. Verify the 'Program' field displays as a listbox field.
  11. Select desire program in the 'Program' field.
  12. Click [Discard].
  13. Verify the 'Electronic Billing' form opens successfully.
  14. Verify the 'Program' field displays as a listbox field.
  15. Select desire program in the 'Program' field.
  16. Click [Discard].
  17. Open the 'Print Bill' form.
  18. Verify the 'Print Bill' form opens successfully.
  19. Verify the 'Program' field displays as a listbox field.
  20. Select desire program in the 'Program' field.
  21. Click [Discard].
  22. Open the 'Re-Print Bill' form.
  23. Verify the 'Re-Print Bill' form opens successfully.
  24. Verify the 'Program(s)' field displays as search field.
  25. Enter desire program code in the 'Program' field.
  26. Verify the system returns matching programs in the field.
  27. Enter desire program name in the 'Program' field.
  28. Verify the system returns matching programs in the field.
  29. Click [Discard].
  30. Open the 'Crystal Self Pay Bill' form.
  31. Verify the 'Crystal Self Pay Bill' form opens successfully.
  32. Verify the 'Program(s)' field displays as search field.
  33. Enter desire program code in the 'Program' field.
  34. Verify the system returns matching programs in the field.
  35. Enter desire program name in the 'Program' field.
  36. Verify the system returns matching programs in the field.
  37. Click [Discard].
  38. Open the 'Spreadsheet Batch Remittance Posting' form.
  39. Verify the 'Spreadsheet Batch Remittance Posting' form opens successfully.
  40. Verify the 'Program(s)' field displays as search field.
  41. Enter desire program code in the 'Program' field.
  42. Verify the system returns matching programs in the field.
  43. Enter desire program name in the 'Program' field.
  44. Verify the system returns matching programs in the field.
  45. Click [Discard].
  46. Open the 'Service Fee/Cross Reference Maintenance' form.
  47. Verify the 'Service Fee/Cross Reference Maintenance' form opens successfully.
  48. Verify the 'Program(s)' field displays as search field.
  49. Enter desire program code in the 'Program' field.
  50. Verify the system returns matching programs in the field.
  51. Enter desire program name in the 'Program' field.
  52. Verify the system returns matching programs in the field.
  53. Click [Discard].
  54. Open the 'Guarantor/Program Billing Defaults' form.
  55. Verify the 'Guarantor/Program Billing Defaults' form opens successfully.
  56. Verify the 'Program' field displays as search field.
  57. Enter desire program code in the 'Program' field.
  58. Verify the system returns matching programs in the field.
  59. Enter desire program name in the 'Program' field.
  60. Verify the system returns matching programs in the field.
  61. Click [Discard].
  62. Verify the 'Practitioner Numbers By Guarantor and Program' form opens successfully.
  63. Verify the 'Program(s)' field displays as search field.
  64. Enter desire program code in the 'Program' field.
  65. Verify the system returns matching programs in the field.
  66. Enter desire program name in the 'Program' field.
  67. Verify the system returns matching programs in the field.
  68. Click [Discard].
  69. Verify the 'Call Intake' form opens successfully.
  70. Verify the 'Program' field displays as search field.
  71. Enter desire program code in the 'Program' field.
  72. Verify the system returns matching programs in the field.
  73. Enter desire program name in the 'Program' field.
  74. Verify the system returns matching programs in the field.
  75. Click [Discard].
  76. Verify the 'Program Maintenance' form opens successfully.
  77. Verify the 'Program' field displays as search field.
  78. Enter desire program code in the 'Program' field.
  79. Verify the system returns matching programs in the field.
  80. Enter desire program name in the 'Program' field.
  81. Verify the system returns matching programs in the field.
  82. Click [Discard].
  83. Verify the 'Back Dated Admission/Discharge' form opens successfully.
  84. Verify the 'Program' field displays as search field.
  85. Enter desire program code in the 'Program' field.
  86. Verify the system returns matching programs in the field.
  87. Enter desire program name in the 'Program' field.
  88. Verify the system returns matching programs in the field.
  89. Click [Discard].
Topics
• Service Fee/Cross Reference Maintenance • NX • Program Maintenance • Admission • Admission (Outpatient) • Print Bill • Practitioner • Re-Print Bill • Guarantor / Program Billing Defaults
Update 136 Summary | Details
File Import - [Support Only] Guarantor Nature
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
  • Financial Eligibility
  • Cross Episode Financial Eligibility
  • File Import
  • Crystal Report Viewer
  • Guarantor Nature File Import
  • Family Financial Eligibility
  • Client Ledger
Scenario 1: File Import - [Support Only] Guarantor Nature - Non contract guarantor to Contract - 'If Customized Retain Customization' = 'N' in the File Import and the 'Customize Guarantor Plan' = 'Y'
Steps

**Internal testing only.

Scenario 2: File Import - [Support Only] Guarantor Nature – Non-contract guarantor to Contract - 'If Customized Retain Customization' = 'Y' in File Import and client has two guarantors
Steps

**Internal testing only
Topics
• Guarantor/Payors • Guarantor • NX • Financial Eligibility • File Import
Update 137 Summary | Details
Task Scheduler Status Widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Product Updates (PM)
Internal Test Only
Topics
• System Task Scheduler • Unbilled Services Report
Update 138 Summary | Details
Claim Follow-Up Productivity Report
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Claim Follow-Up Productivity Report
  • Crystal Report Viewer
  • Client Ledger
  • Financial Eligibility
  • Unbilled Services Report
Scenario 1: 'Claim Follow-Up Productivity' Report
Specific Setup:
  • Claim follow-up notes are created in AR console. Note the follow-up notes created, date when the note created, name of the user in the AR Console.
Steps
  1. Access the 'Claim Follow-Up Productivity Report' form.
  2. Select 'Summary Report' in the 'Summary or Detail Report' field.
  3. Leave the 'User' field blank.
  4. Enter the desired dates in the 'Start Date' and 'End Date' fields.
  5. Process the report.
  6. Validate the 'User' field correctly displays all the user information.
  7. Validate the '# of Claim Follow-Up Notes Entered' field correctly displays the number of notes entered by specific user.
  8. Close the report.
  9. Return to the form.
  10. Select desired user in the 'User' field.
  11. Process the report.
  12. Validate the 'User' field correctly displays the user information of the selected user.
  13. Validate the '# of Claim Follow-Up Notes Entered' field correctly displays the number of notes entered by that user.
  14. Close the report.
  15. Return to the form.
  16. Select 'Detail report' in the 'Summary or Detail Report' field.
  17. Leave the 'User' field blank.
  18. Enter the desired dates in the 'Start Date' and 'End Date' fields.
  19. Process the report.
  20. Validate the report displays correct claim follow-up information for all users.
  21. Verify the 'Client' column contains entire name of the client and it does not overlap to the content of the next column.
  22. Verify the 'Claim#' column contains correct claim number of the client and it does not overlap to the content of the next column.
  23. Verify the 'Guarantor' column contains entire name of the guarantor and it does not overlap to the content of the 'Follow-Up Note Entry Date' column.
  24. Verify the 'Follow-Up Note Entry Date' column contains correct date and it does not overlap to the content of the 'Follow-Up Status' column.
  25. Verify the 'Follow-Up Status' column contains correct status of the note as entered in AR console and it does not overlap to the content of the next column.
  26. Verify the 'Next Follow-Up Date' column contains correct date and it does not overlap to the content of the next column.
  27. Verify the 'Completion Date' column contains correct completion date and it does not overlap to the content of the next column.
  28. Validate the 'Follow-Up Note' field displays text as entered in 'AR Console'.
  29. Close the report.
  30. Return to the form.
  31. Select 'Detail report' in the 'Summary or Detail Report' field.
  32. Select desired user in the 'User' field.
  33. Enter the desired dates in the 'Start Date' and 'End Date' fields.
  34. Process the report.
  35. Validate the report displays correct claim follow-up information only for the selected user.
  36. Verify the 'Client' column contains entire name of the client and it does not overlap to the content of the next column.
  37. Verify the 'Claim#' column contains correct claim number of the client and it does not overlap to the content of the next column.
  38. Verify the 'Guarantor' column contains entire name of the guarantor and it does not overlap to the content of the 'Follow-Up Note Entry Date' column.
  39. Verify the 'Follow-Up Note Entry Date' column contains correct date and it does not overlap to the content of the 'Follow-Up Status' column.
  40. Verify the 'Follow-Up Status' column contains correct status of the note as entered in AR console and it does not overlap to the content of the next column.
  41. Verify the 'Next Follow-Up Date' column contains correct date and it does not overlap to the content of the next column.
  42. Verify the 'Completion Date' column contains correct completion date and it does not overlap to the content of the next column.
  43. Validate the 'Follow-Up Note' field displays text as entered in 'AR Console'.
  44. Close the report.
  45. Close the form.
Scenario 2: 'Client Ledger' report - validate fields have no overlaps
Specific Setup:
  • Client with a Guarantor and Services filed (Client A).
Steps
  1. Open the 'Client Ledger' form.
  2. Select desired client in the 'Client ID' field.
  3. Select ‘All Episodes’ in the 'Claim/Episode/All Episodes' field.
  4. Select ‘Crystal’ in the 'Ledger Type' field.
  5. Click [Process].
  6. Review the 'Client Account Ledger' report.
  7. Verify the 'Service Description' field does not overlap with 'Units' field.
  8. Verify 'Guarantor Name' field does not overlap with 'Guarantor Liability' field.
  9. Validate the 'Line Balance' field does not cut off.
  10. Close the report.
  11. Open the 'Client Ledger' form.
  12. Select desired client in the 'Client ID' field.
  13. Select ‘All Episodes’ in the 'Claim/Episode/All Episodes' field.
  14. Select ‘Simple’ in the 'Ledger Type' field.
  15. Click [Process].
  16. Review the report.
  17. Verify the 'Service Description' field does not overlap with 'Units' field.
  18. Verify 'Guarantor' field does not overlap with 'Guarantor Liability' field.
  19. Validate the 'Line Balance' field is not cut off.
  20. Close the report.
Scenario 3: 'Unbilled Services Report' - validate fields have no overlaps
Steps
  1. Access the 'Unbilled Services Report' form.
  2. Set 'Service Start Date' to any date where services were rendered.
  3. Set 'Service End Date' to any date to include services.
  4. Select ‘All’ in the 'Financial Class(es)' field.
  5. Select ‘All’ in the 'Program(s)' field.
  6. Select ‘All’ in the 'Service Status' field.
  7. Select ‘No’ in the 'Include 0 Liability' field.
  8. Click [Process].
  9. Review the report and note the following:
  10. Verify the value of the 'Guarantor' field does not overlap to the 'FE Expired?' field.
  11. Verify that the Guarantor name wraps, if necessary, to prevent overlapping other fields.
  12. Close the report.
  13. Close the form.
Topics
• Claim Follow-up • NX
Update 139 Summary | Details
Electronic Billing - 837 Dental Bill
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Ledger
  • Electronic Billing
  • Financial Eligibility
  • Admission
  • Diagnosis
  • Client Charge Input
  • Admission (Outpatient)
Scenario 1: 837 Professional Bill - Validating the 'Provider Accept Assignment Code' on the bill – Registry setting 'Use Billing Guarantor to determine Provider Accept Assignment Code (2300-CLM-07)' = Y
Specific Setup:
  • Registry Setting:
  • Set the 'Use Billing Guarantor To Determine Provider Accept Assignment Code (2300-CLM-07)' registry setting to 'Y'.
  • Guarantors/Payors:
  • An existing Medicare guarantor and a non-Medicare guarantor are identified to be used. Note the guarantors code/name.
  • Both the guarantors are configured for 837 professional bills.
  • Service codes:
  • An existing professional service code is identified to be used. Note the service code/description.
  • The 'Does This Code Have A Professional Component' is set to 'Yes'.
  • Service Fee/ Cross Reference Maintenance:
  • A fee definition is created for the service code identified in the ' Service Codes' form.
  • Admission:
  • An existing client is identified with a professional service, or a new client is admitted in to the outpatient program which is selected in the Guarantor/Program Billing Defaults. Note client id, admission program, admission date.
  • Guarantor/Program Billing Defaults:
  • An existing template is identified, and the template is assigned to the guarantors identified above and at least to the admission program of the client. Note the program selection.
  • Financial Eligibility:
  • The guarantors identified in the 'Guarantors/Payors' form are assigned to the client as a primary and secondary guarantor.
  • The 'Subscriber Assignment of Benefits is set to 'Yes' for the primary Medicare guarantor.
  • The 'Subscriber Assignment of Benefits is set to 'No' for the secondary guarantors.
  • Client Charge Input:
  • A professional service is rendered to the client. Note service date, service code.
  • Client Ledger:
  • A service distributed correctly to the primary guarantor.
Steps
  1. Open the 'Electronic Billing' form.
  2. Select the 'All Clients' in the 'Select All Clients Or Interim Batch' field.
  3. Populate all the required fields.
  4. Compile the bill for the primary medicare guarantor.
  5. Verify the bill compiles successfully.
  6. Dump the file.
  7. Review the dump file.
  8. Verify the Provider Accept Assignment Code (2300-CLM-07) will be set to 'A' because the registry setting is set to 'Y' and the 'Subscriber Assignment of Benefits' field for the guarantor being billed is set to 'Yes'.
  9. Close the file.
  10. Close the form.
  11. Open the 'Financial Eligibility' form.
  12. Set the 'Subscriber Assignment of Benefits' to 'No' for the Medicare guarantor.
  13. Set the 'Subscriber Assignment of Benefits' to 'Yes' for the secondary guarantor which is not the billing guarantor.
  14. Submit the form.
  15. Open the 'Electronic Billing' form.
  16. Select the 'All Clients' in the 'Select All Clients Or Interim Batch' field.
  17. Populate all the required fields.
  18. Compile the bill for the primary guarantor.
  19. Verify the bill compiles successfully.
  20. Dump the file.
  21. Review the dump file.
  22. Verify the Provider Accept Assignment Code (2300-CLM-07) will be set to 'C' because the registry setting is set to 'Y' and 'Subscriber Assignment of Benefits' field for the guarantor being billed is set to 'No'.
  23. Close the file.
  24. Close the form.
  25. Open the 'Financial Eligibility' form.
  26. Set the 'Subscriber Assignment of Benefits' to 'Yes' for the Medicare guarantor.
  27. Verify the 'Subscriber Assignment of Benefits' to 'Yes' for the secondary guarantor which is not the billing guarantor.
  28. Submit the form.
  29. Open the 'Electronic Billing' form.
  30. Select the 'All Clients' in the 'Select All Clients Or Interim Batch' field.
  31. Populate all the required fields.
  32. Compile the bill for the primary guarantor.
  33. Verify the bill compiles successfully.
  34. Dump the file.
  35. Review the dump file.
  36. Verify the Provider Accept Assignment Code (2300-CLM-07) will be set to 'A' because the registry setting is set to 'Y' and 'Subscriber Assignment of Benefits' field for the guarantor being billed is set to 'Yes'.
  37. Close the file.
  38. Close the form.
  39. Open the 'Financial Eligibility' form.
  40. Set the 'Subscriber Assignment of Benefits' to 'No' for the Medicare guarantor.
  41. Set the 'Subscriber Assignment of Benefits' to 'No' for the secondary guarantor.
  42. Submit the form.
  43. Open the 'Electronic Billing' form.
  44. Select the 'All Clients' in the 'Select All Clients Or Interim Batch' field.
  45. Populate all the required fields.
  46. Compile the bill for the primary guarantor.
  47. Verify the bill compiles successfully.
  48. Dump the file.
  49. Review the dump file.
  50. Verify the Provider Accept Assignment Code (2300-CLM-07) will be set to 'C' because the registry setting is set to 'Y' and 'Subscriber Assignment of Benefits' field for the guarantor being billed is set to 'No'.
  51. Close the file.
  52. Close the form.
Scenario 2: 837 Institutional Bill - Validating the 'Provider Accept Assignment Code' on the bill – Registry setting 'Use Billing Guarantor to determine Provider Accept Assignment Code (2300-CLM-07)' = Y
Specific Setup:
  • Registry Setting:
  • Set the 'Use Billing Guarantor To Determine Provider Accept Assignment Code (2300-CLM-07)' registry setting to 'Y'.
  • Guarantors/Payors:
  • An existing Medicare guarantor and a non-Medicare guarantor are identified to be used. Note the guarantor's code/name.
  • Both the guarantors are configured for 837 professional bills.
  • Service codes:
  • An existing inpatient service code is identified to be used. Note the service code/description.
  • The 'Does This Code Have A Professional Component' is set to 'Yes'.
  • Service Fee/ Cross Reference Maintenance:
  • A fee definition is created for the service code identified in the ' Service Codes' form.
  • Admission:
  • An existing inpatient client is identified with an inpatient service, or a new client is admitted into the inpatient program. Note client id, admission program, admission date.
  • Guarantor/Program Billing Defaults:
  • An existing template is identified, and the template is assigned to the guarantors identified above and to the admission program of the client. Note the program selection.
  • Financial Eligibility:
  • The Medicare guarantor identified in the 'Guarantors/Payors' form is assigned to the client as a primary and Non Medicare guarantor is assigned to the client as a secondary guarantor.
  • The 'Subscriber Assignment of Benefits is set to 'Yes' for the primary Medicare guarantor.
  • The 'Subscriber Assignment of Benefits is set to 'No' for the secondary guarantors.
  • Client Charge Input:
  • An inpatient service is rendered to the client. Note service date, service code.
  • Client Ledger:
  • A service distributed correctly to the primary guarantor.
Steps
  1. Open the 'Electronic Billing' form.
  2. Select the 'All Clients' in the 'Select All Clients Or Interim Batch' field.
  3. Populate all the required fields.
  4. Compile the bill for the primary Medicare guarantor.
  5. Verify the bill compiles successfully.
  6. Dump the file.
  7. Review the dump file.
  8. Verify the Provider Accept Assignment Code (2300-CLM-07) will be set to 'A' because the registry setting is set to 'Y' and the 'Subscriber Assignment of Benefits' field for the guarantor being billed is set to 'Yes'.
  9. Close the file.
  10. Close the form.
  11. Open the 'Financial Eligibility' form.
  12. Set the 'Subscriber Assignment of Benefits' to 'No' for the Medicare guarantor.
  13. Set the 'Subscriber Assignment of Benefits' to 'Yes' for the secondary guarantor which is not the billing guarantor.
  14. Submit the form.
  15. Open the 'Electronic Billing' form.
  16. Select the 'All Clients' in the 'Select All Clients Or Interim Batch' field.
  17. Populate all the required fields.
  18. Compile the bill for the primary guarantor.
  19. Verify the bill compiles successfully.
  20. Dump the file.
  21. Review the dump file.
  22. Verify the Provider Accept Assignment Code (2300-CLM-07) will be set to 'C' because the registry setting is set to 'Y' and 'Subscriber Assignment of Benefits' field for the guarantor being billed is set to 'No'.
  23. Close the file.
  24. Close the form.
  25. Open the 'Financial Eligibility' form.
  26. Set the 'Subscriber Assignment of Benefits' to 'Yes' for the Medicare guarantor.
  27. Verify the 'Subscriber Assignment of Benefits' to 'Yes' for the secondary guarantor which is not the billing guarantor.
  28. Submit the form.
  29. Open the 'Electronic Billing' form.
  30. Select the 'All Clients' in the 'Select All Clients Or Interim Batch' field.
  31. Populate all the required fields.
  32. Compile the bill for the primary guarantor.
  33. Verify the bill compiles successfully.
  34. Dump the file.
  35. Review the dump file.
  36. Verify the Provider Accept Assignment Code (2300-CLM-07) will be set to 'A' because the registry setting is set to 'Y' and 'Subscriber Assignment of Benefits' field for the guarantor being billed is set to 'Yes'.
  37. Close the file.
  38. Close the form.
  39. Open the 'Financial Eligibility' form.
  40. Set the 'Subscriber Assignment of Benefits' to 'No' for the Medicare guarantor.
  41. Set the 'Subscriber Assignment of Benefits' to 'No' for the secondary guarantor.
  42. Submit the form.
  43. Open the 'Electronic Billing' form.
  44. Select the 'All Clients' in the 'Select All Clients Or Interim Batch' field.
  45. Populate all the required fields.
  46. Compile the bill for the primary guarantor.
  47. Verify the bill compiles successfully.
  48. Dump the file.
  49. Review the dump file.
  50. Verify the Provider Accept Assignment Code (2300-CLM-07) will be set to 'C' because the registry setting is set to 'Y' and 'Subscriber Assignment of Benefits' field for the guarantor being billed is set to 'No'.
  51. Close the file.
  52. Close the form.
Scenario 3: 837 Dental Bill - Validating the 'Provider Accept Assignment Code' on the bill – Registry setting 'Use Billing Guarantor to determine Provider Accept Assignment Code (2300-CLM-07)' = Y
Specific Setup:
  • Registry Setting:
  • Set the 'Use Billing Guarantor To Determine Provider Accept Assignment Code (2300-CLM-07)' registry setting to 'Y'.
  • Guarantors/Payors:
  • Two existing Medicare guarantors are identified to be used. Note the guarantors code/name.
  • Service codes:
  • An existing dental service code is identified to be used. Note the service code/description.
  • The 'Is This A Dental Service' is set to 'Yes'.
  • Service Fee/ Cross Reference Maintenance:
  • A fee definition is created for the service code identified in the ' Service Codes' form.
  • Admission:
  • An existing client is identified, or a new client is admitted. Note client id, admission program, admission date.
  • Financial Eligibility:
  • The guarantors identified in the 'Guarantors/Payors' form are assigned to the client as a primary and secondary guarantor.
  • Set subscriber assignment of benefits to 'No' for the primary guarantor but 'Yes' to the secondary guarantor.
  • Client Charge Input:
  • A dental service is rendered to the client. Note service date, service code.
  • Client Ledger:
  • A service distributed correctly to the primary guarantor.
Steps
  1. Open the 'Electronic Billing' form.
  2. Select the 'All Clients' in the 'Select All Clients Or Interim Batch' field.
  3. Populate all the required fields.
  4. Compile the bill for the primary guarantor.
  5. Verify the bill compiles successfully.
  6. Dump the file.
  7. Review the dump file.
  8. Verify the Provider Accept Assignment Code (2300-CLM-07) will be set to 'C' because the registry setting is set to 'Y' and the 'Subscriber Assignment of Benefits' to 'No'.
  9. Close the file.
  10. Close the form.
  11. Open the 'Financial Eligibility' form.
  12. Set the 'Subscriber Assignment of Benefits' to 'Yes' for the primary guarantor.
  13. Submit the form.
  14. Open the 'Electronic Billing' form.
  15. Select the 'All Clients' in the 'Select All Clients Or Interim Batch' field.
  16. Populate all the required fields.
  17. Compile the bill for the primary guarantor.
  18. Verify the bill compiles successfully.
  19. Dump the file.
  20. Review the dump file.
  21. Verify the Provider Accept Assignment Code (2300-CLM-07) will be set to 'A' because the registry setting is set to 'Y' and 'Subscriber Assignment of Benefits' field for the guarantor being billed is set to 'Yes'.
  22. Close the file.
  23. Close the form.
Topics
• 837 Dental • 837 Institutional • NX
Update 141 Summary | Details
Facility Defaults - CarePathways Configuration
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CarePathways Error
Scenario 1: 'Facility Defaults' form - field validations
Steps
  1. Open the 'Registry Setting' form.
  2. Set the 'Enable CarePathways Benchmarking and Analytics' to 'Y'.
  3. Submit the form.
  4. Open the 'Facility Defaults' form.
  5. Verify the 'CarePathways Configuration' section is available on the form.
  6. Click on the 'CarePathways Configuration' tab.
  7. Verify system navigates user to the 'CarePathways Configuration' section correctly.
  8. Populate required fields as needed.
  9. Click [Submit].
  10. Open the 'Registry Setting' form.
  11. Set the 'Enable CarePathways Benchmarking and Analytics' to 'N'.
  12. Submit the form.
  13. Open the 'Facility Defaults' form.
  14. Verify the 'CarePathways Configuration' section is not available on the form.
  15. Populate any desired fields.
  16. Validate the 'Provider Country' field is displayed.
  17. Select the desired value in the 'Provider Country' field. Note: this field is populated based off the dictionary values under the 'Client' file, '(150) Country Of Origin' data element in 'Dictionary Update'.
  18. Click [Submit].
  19. Access Crystal Reports or other SQL Reporting tool.
  20. Create a report using the 'SYSTEM.table_facility_defaults' SQL table.
  21. Validate a row is displayed for the data on file.
  22. Validate the 'provider_country_code' field contains the code associated to the 'Provider Country' selected.
  23. Validate the 'provider_country_value' field contains the value associated to the 'Provider Country' selected.
  24. Close the report.
  25. Open the 'Registry Setting' form.
  26. Set the 'Enable CarePathways Benchmarking and Analytics' to 'Y'.
  27. Submit the form.
  28. Open the 'Facility Defaults' form.
  29. Verify the 'CarePathways Configuration' section is available on the form.
  30. Click on the 'CarePathways Configuration' tab.
  31. Verify system navigates user to the 'CarePathways Configuration' section correctly.
  32. Populate required fields as needed.
  33. Go back to 'Facility Defaults' section.
  34. Verify the 'Provider Setting Type' field exist.
  35. Select desired value in the field.
  36. Verify the 'Provider Setting Area' field exist.
  37. Select desired value in the field.
  38. Click [Submit].
  39. Open the 'Facility Defaults' form.
  40. Verify the 'CarePathways Configuration' section is available on the form.
  41. Verify the 'Provider Setting Type' field contains the value as entered.
  42. Verify the 'Provider Setting Area' field contains the value as entered.
  43. Click [Discard].
Topics
• Facility Defaults • NX
Update 143 Summary | Details
Payment Acknowledgement - Post Payment Accounting Entry
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Posting/Adjustment Codes Definition
  • Payment Acknowledgement
  • Service Codes
  • Remittance Processing Widget
Scenario 1: Payment Acknowledgement - Post Payment Accounting Entry / Reverse Payment Accounting Entry
Specific Setup:
  • Registry Setting:
  • ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
  • "Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged" has a 'Registry Setting Value that contains '7'
  • Dictionary Update:
  • Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
  • Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
  • Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
  • Posting/Adjustment Codes Definitions: Definitions exist for ‘Payment’.
  • The definitions may have a value in the ‘Payment Acknowledgement Type’ field.
  • All ‘Payment’ definitions will be available in the ‘Payment Acknowledgement’ form.
  • Clients:
  • Identify clients with and without a self-pay balance due. Note the balance due amounts.
  • Note the 'Treatment Setting' of the client's program.
Steps
  1. Open the ‘Payment Acknowledgement’ form.
  2. Verify that ‘Action’ defaults to ‘New’.
  3. Verify that ‘Transaction Number’ is read-only.
  4. Verify that ‘Entered By’ is read-only and defaults to the signed-in user.
  5. Enter the desired value in ‘Batch Number’.
  6. Select the desired ‘Posting Code’. All payment posting codes will be displayed.
  7. Enter the desired value in ‘Check/EFT Number’.
  8. Enter the desired value in ‘Amount’.
  9. Select the desired ‘Guarantor’. If a ‘Self-Pay' guarantor is selected, the ‘Client’ field will be enabled.
  10. Enter the desired value in ‘Name/Source’.
  11. Enter the desired value in ‘Client’, if enabled. The field is only available for ‘Self-Pay' guarantors.
  12. Enter the desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
  13. Enter the desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
  14. Enter the desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
  15. Select the desired ‘Treatment Service’.
  16. Select the desired ‘Category’. Inactive dictionary codes will not display in this field.
  17. Enter the desired value in ‘Bank Ref #’.
  18. Enter the desired value in ‘Comments’.
  19. Click [File].
  20. Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is 6. Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
  21. Click [Yes] to continue to the Post Payment Accounting Entry section or [No] to remain in the ‘Payment Acknowledgement’ section.
  22. If [Yes] was clicked, go to step 30.
  23. If [No] was clicked, select ‘Edit or View’ in ‘Action, which will enable the ‘Payment Acknowledgement Search’ section.
  24. Enter data from the filed ‘Payment Acknowledgement’ into the desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
  25. Click [Search].
  26. Select the desired item in the ‘Payment Acknowledgement’ grid.
  27. Click [OK] to continue or [Cancel] to end the search. Click [OK].
  28. The following ‘Payment Acknowledgement’ displays: Do you need to continue to Post Payment Accounting Entry?
  29. Click [Yes].
  30. Validate that the grid is not enabled.
  31. Click [New Row] in ‘Post Payment Accounting Entry’.
  32. Validate that the grid becomes enabled.
  33. Select the desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
  34. Select the desired ‘Program’. This is from ‘Other Table Files: (5521) Program’, not a program in ‘Program Maintenance’.
  35. Select the desired ‘Account’.
  36. Select the desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
  37. Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgment’.
  38. Select the desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’, or the ‘Deposit Date’.
  39. If desired, enter a ‘Comment’.
  40. Validate that the ‘Posting Summary’ is correct.
  41. If desired, click [New Row] and repeat the steps.
  42. If desired, click [Delete Row]. A ‘Confirm Delete’ message will be displayed. Select the desired value.
  43. Click [File].
  44. The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
  45. Click [Yes].
  46. Click the ‘Reverse’ checkbox in one row of the ‘Post Payment Accounting Entry’.
  47. Enter desired ‘Reversal Reason’.
  48. Click [Reverse].
  49. Validate that a message is received stating: Reversal Posting Date is required.
  50. Enter a ‘Reversal Posting Date’ that is on or after the ‘Posting Date’.
  51. Click [Reverse].
  52. Validate that a new row was added to the ‘Post Payment Accounting Entry’ grid and that it mirrors the row that was selected to reverse, except for ‘Amount’ displays in parentheses, indicating a negative amount. The ‘Comment’ for the new row will contain the ‘Reversal Reason’.
  53. Attempt to reverse the row that was previously reversed. Validate that a message is received that states: Rows selected to reverse that are already reversed: xx – where xx is the row number.
  54. If desired, add a new row to post an additional payment.
  55. Close the form.
Scenario 2: Payment Acknowledgement - Post Payment Accounting Entry - Transaction included a Client
Specific Setup:
  • Registry Setting:
  • ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
  • "Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged" has a 'Registry Setting Value that contains '7'
  • Dictionary Update:
  • Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
  • Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
  • Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
  • Posting/Adjustment Codes Definitions: Definitions exist for ‘Payment’.
  • The definitions may have a value in the ‘Payment Acknowledgement Type’ field.
  • All ‘Payment’ definitions will be available in the ‘Payment Acknowledgement’ form.
  • Clients:
  • Identify one or more clients that a balance due to a self-pay guarantor. Note the balance due amounts.
  • Note the 'Treatment Setting' of the client's program.
Steps
  1. Open ‘Payment Acknowledgement’ form.
  2. Verify that ‘Action’ defaults to ‘New’.
  3. Verify that ‘Transaction Number’ is read only.
  4. Verify that ‘Entered By’ is read only and defaults to the signed in user.
  5. Enter desired value in ‘Batch Number’.
  6. Select desired ‘Posting Code’. All payment posting codes will display.
  7. Enter desired value in ‘Check/EFT Number’.
  8. Enter desired value in ‘Amount’.
  9. Select desired ‘Guarantor’. If a ‘Self-Pay' guarantor is selected, the ‘Client’ field will be enabled.
  10. Enter desired value in ‘Name/Source’.
  11. Enter desired value in ‘Client’, if enabled. The field is only available for ‘Self-Pay' guarantors.
  12. Enter desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
  13. Enter desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
  14. Enter desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
  15. Select desired ‘Treatment Service’.
  16. Select desired ‘Category’. Inactive dictionary codes will not display in this filed.
  17. Enter desired value in ‘Bank Ref #’.
  18. Enter desired value in ‘Comments’.
  19. Click [File].
  20. Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is 6. Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
  21. Click [Yes] to continue to Post Payment Accounting Entry section or [No] to remain in the ‘Payment Acknowledgement’ section.
  22. Select [Yes] was clicked, go to step 30.
  23. Validate that the grid is not enabled.
  24. Click [New Row] in ‘Post Payment Accounting Entry’.
  25. Validate that the grid becomes enabled.
  26. Select desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
  27. Select desired ‘Program’. This is from ‘Other Table Files: (5521) Program’, not a program in ‘Program Maintenance’.
  28. Select desired ‘Account’.
  29. Select desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
  30. Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgement’.
  31. Select desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’ or the ‘Deposit Date’.
  32. If desired, enter a ‘Comment’.
  33. Validate that the ‘Posting Summary’ is correct.
  34. If desired, click [New Row] and repeat the steps.
  35. If desired, click [Delete Row]. A ‘Confirm Delete’ message will be displayed. Select desired value.
  36. Click [File].
  37. The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
  38. Click [No].
  39. Close the form.
Future Functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Crystal Reports or other SQL Reporting tool (PM Namespace)
  • Client Ledger
  • Financial Eligibility
  • Remittance Processing Widget
Internal Test Only
Payment Acknowledgement -
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Posting/Adjustment Codes Definition
  • Payment Acknowledgement
  • Service Codes
Scenario 1: Payment Acknowledgement - Post Payment Accounting Entry / Reverse Payment Accounting Entry
Specific Setup:
  • Registry Setting:
  • ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
  • "Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged" has a 'Registry Setting Value that contains '7'
  • Dictionary Update:
  • Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
  • Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
  • Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
  • Posting/Adjustment Codes Definitions: Definitions exist for ‘Payment’.
  • The definitions may have a value in the ‘Payment Acknowledgement Type’ field.
  • All ‘Payment’ definitions will be available in the ‘Payment Acknowledgement’ form.
  • Clients:
  • Identify clients with and without a self-pay balance due. Note the balance due amounts.
  • Note the 'Treatment Setting' of the client's program.
Steps
  1. Open the ‘Payment Acknowledgement’ form.
  2. Verify that ‘Action’ defaults to ‘New’.
  3. Verify that ‘Transaction Number’ is read-only.
  4. Verify that ‘Entered By’ is read-only and defaults to the signed-in user.
  5. Enter the desired value in ‘Batch Number’.
  6. Select the desired ‘Posting Code’. All payment posting codes will be displayed.
  7. Enter the desired value in ‘Check/EFT Number’.
  8. Enter the desired value in ‘Amount’.
  9. Select the desired ‘Guarantor’. If a ‘Self-Pay' guarantor is selected, the ‘Client’ field will be enabled.
  10. Enter the desired value in ‘Name/Source’.
  11. Enter the desired value in ‘Client’, if enabled. The field is only available for ‘Self-Pay' guarantors.
  12. Enter the desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
  13. Enter the desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
  14. Enter the desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
  15. Select the desired ‘Treatment Service’.
  16. Select the desired ‘Category’. Inactive dictionary codes will not display in this field.
  17. Enter the desired value in ‘Bank Ref #’.
  18. Enter the desired value in ‘Comments’.
  19. Click [File].
  20. Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is 6. Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
  21. Click [Yes] to continue to the Post Payment Accounting Entry section or [No] to remain in the ‘Payment Acknowledgement’ section.
  22. If [Yes] was clicked, go to step 30.
  23. If [No] was clicked, select ‘Edit or View’ in ‘Action, which will enable the ‘Payment Acknowledgement Search’ section.
  24. Enter data from the filed ‘Payment Acknowledgement’ into the desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
  25. Click [Search].
  26. Select the desired item in the ‘Payment Acknowledgement’ grid.
  27. Click [OK] to continue or [Cancel] to end the search. Click [OK].
  28. The following ‘Payment Acknowledgement’ displays: Do you need to continue to Post Payment Accounting Entry?
  29. Click [Yes].
  30. Validate that the grid is not enabled.
  31. Click [New Row] in ‘Post Payment Accounting Entry’.
  32. Validate that the grid becomes enabled.
  33. Select the desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
  34. Select the desired ‘Program’. This is from ‘Other Table Files: (5521) Program’, not a program in ‘Program Maintenance’.
  35. Select the desired ‘Account’.
  36. Select the desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
  37. Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgment’.
  38. Select the desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’, or the ‘Deposit Date’.
  39. If desired, enter a ‘Comment’.
  40. Validate that the ‘Posting Summary’ is correct.
  41. If desired, click [New Row] and repeat the steps.
  42. If desired, click [Delete Row]. A ‘Confirm Delete’ message will be displayed. Select the desired value.
  43. Click [File].
  44. The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
  45. Click [Yes].
  46. Click the ‘Reverse’ checkbox in one row of the ‘Post Payment Accounting Entry’.
  47. Enter desired ‘Reversal Reason’.
  48. Click [Reverse].
  49. Validate that a message is received stating: Reversal Posting Date is required.
  50. Enter a ‘Reversal Posting Date’ that is on or after the ‘Posting Date’.
  51. Click [Reverse].
  52. Validate that a new row was added to the ‘Post Payment Accounting Entry’ grid and that it mirrors the row that was selected to reverse, except for ‘Amount’ displays in parentheses, indicating a negative amount. The ‘Comment’ for the new row will contain the ‘Reversal Reason’.
  53. Attempt to reverse the row that was previously reversed. Validate that a message is received that states: Rows selected to reverse that are already reversed: xx – where xx is the row number.
  54. If desired, add a new row to post an additional payment.
  55. Close the form.
Scenario 2: Payment Acknowledgement_Restricting Negative value the Amount fields
Specific Setup:
  • Registry Setting:
  • ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
  • "Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged" has a 'Registry Setting Value that contains '7'
  • Dictionary Update:
  • Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
  • Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
  • Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
  • Posting/Adjustment Codes Definitions: Definitions exist for ‘Payment’.
  • The definitions may have a value in the ‘Payment Acknowledgement Type’ field.
  • All ‘Payment’ definitions will be available in the ‘Payment Acknowledgement’ form.
  • Clients:
  • Identify clients with and without a self-pay balance. Note the balance due amounts.
  • Note the 'Treatment Setting' of the client's program.
Steps
  1. Open the ‘Payment Acknowledgement’ form.
  2. Verify that ‘Action’ defaults to ‘New’.
  3. Verify that ‘Transaction Number’ is read-only.
  4. Verify that ‘Entered By’ is read-only and defaults to the signed-in user.
  5. Enter the desired value in ‘Batch Number’.
  6. Select the REVERSAL type of ‘Posting Code’. All payment posting codes will be displayed.
  7. Enter the desired value in ‘Check/EFT Number’.
  8. Try Entering a negative value for the 'Amount' field.
  9. Validate that the user is not allowed to enter a negative value and see the appropriate error popup message.
  10. Enter the desired value in ‘Amount’.
  11. Select the desired ‘Guarantor’. If a ‘Self-Pay' guarantor is selected, the ‘Client’ field will be enabled.
  12. Enter the desired value in ‘Name/Source’.
  13. Enter the desired value in ‘Client’, if enabled. The field is only available for ‘Self-Pay' guarantors.
  14. Enter the desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
  15. Enter the desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
  16. Enter the desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
  17. Select the desired ‘Treatment Service’.
  18. Select the desired ‘Category’. Inactive dictionary codes will not display in this filed.
  19. Enter the desired value in ‘Bank Ref #’.
  20. Enter the desired value in ‘Comments’.
  21. Click [File].
  22. Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is 6. Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
  23. Click [Yes] to continue to the Post Payment Accounting Entry section or [No] to remain in the ‘Payment Acknowledgement’ section.
  24. Select [No].
  25. Verify that the user remains on the form with all the filed data cleared out.
  26. Select ‘Action’ as ‘Edit or View’.
  27. Validate that the 'Payment Acknowledgement Search' section is enabled.
  28. Enter data from the filed ‘Payment Acknowledgement’ into the desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
  29. Click [Search].
  30. Verify the 'Payment Acknowledgement' Grid shows up for user selection.
  31. Validate that the amount column is showing the value as negative even though the user entered it as a positive value. (Here the system decides this based on the Posting Code type.)
  32. Select the desired row and select 'OK'.
  33. Validate that all the appropriate entries filed for that Transaction are being loaded into the form.
  34. Validate that the grid under 'Post Payment Accounting Entry' is not enabled.
  35. Click [New Row] in ‘Post Payment Accounting Entry’.
  36. Validate that the grid becomes enabled.
  37. Select the desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
  38. Select the desired ‘Program’. This is from ‘Other Table Files: (5521) Program’, not a program in ‘Program Maintenance’.
  39. Select the desired ‘Account’.
  40. Try Entering a negative value for the 'Amount' field.
  41. Validate that the user is not allowed to enter a negative value and see the appropriate error popup message.
  42. Select the desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
  43. Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgment’.
  44. Select the desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’, or the ‘Deposit Date’.
  45. If desired, enter a ‘Comment’.
  46. Validate that the ‘Posting Summary’ is correct. (Even though the entered/shown amount is a positive value, based on the Posting code type the amount value should be shown as a negative one in the 'Posting Summary')
  47. If desired, click [New Row] and repeat the steps.
  48. If desired, click [Delete Row]. A ‘Confirm Delete’ message will be displayed. Select the desired value.
  49. Click [File].
  50. The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
  51. Click [No].
  52. Close the form.
Payment Acknowledgement - Post Payment Accounting Entry
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Posting/Adjustment Codes Definition
  • Payment Acknowledgement
  • Service Codes
Scenario 1: Payment Acknowledgement - Post Payment Accounting Entry / Reverse Payment Accounting Entry
Specific Setup:
  • Registry Setting:
  • ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
  • "Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged" has a 'Registry Setting Value that contains '7'
  • Dictionary Update:
  • Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
  • Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
  • Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
  • Posting/Adjustment Codes Definitions: Definitions exist for ‘Payment’.
  • The definitions may have a value in the ‘Payment Acknowledgement Type’ field.
  • All ‘Payment’ definitions will be available in the ‘Payment Acknowledgement’ form.
  • Clients:
  • Identify clients with and without a self-pay balance due. Note the balance due amounts.
  • Note the 'Treatment Setting' of the client's program.
Steps
  1. Open the ‘Payment Acknowledgement’ form.
  2. Verify that ‘Action’ defaults to ‘New’.
  3. Verify that ‘Transaction Number’ is read-only.
  4. Verify that ‘Entered By’ is read-only and defaults to the signed-in user.
  5. Enter the desired value in ‘Batch Number’.
  6. Select the desired ‘Posting Code’. All payment posting codes will be displayed.
  7. Enter the desired value in ‘Check/EFT Number’.
  8. Enter the desired value in ‘Amount’.
  9. Select the desired ‘Guarantor’. If a ‘Self-Pay' guarantor is selected, the ‘Client’ field will be enabled.
  10. Enter the desired value in ‘Name/Source’.
  11. Enter the desired value in ‘Client’, if enabled. The field is only available for ‘Self-Pay' guarantors.
  12. Enter the desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
  13. Enter the desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
  14. Enter the desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
  15. Select the desired ‘Treatment Service’.
  16. Select the desired ‘Category’. Inactive dictionary codes will not display in this field.
  17. Enter the desired value in ‘Bank Ref #’.
  18. Enter the desired value in ‘Comments’.
  19. Click [File].
  20. Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is 6. Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
  21. Click [Yes] to continue to the Post Payment Accounting Entry section or [No] to remain in the ‘Payment Acknowledgement’ section.
  22. If [Yes] was clicked, go to step 30.
  23. If [No] was clicked, select ‘Edit or View’ in ‘Action, which will enable the ‘Payment Acknowledgement Search’ section.
  24. Enter data from the filed ‘Payment Acknowledgement’ into the desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
  25. Click [Search].
  26. Select the desired item in the ‘Payment Acknowledgement’ grid.
  27. Click [OK] to continue or [Cancel] to end the search. Click [OK].
  28. The following ‘Payment Acknowledgement’ displays: Do you need to continue to Post Payment Accounting Entry?
  29. Click [Yes].
  30. Validate that the grid is not enabled.
  31. Click [New Row] in ‘Post Payment Accounting Entry’.
  32. Validate that the grid becomes enabled.
  33. Select the desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
  34. Select the desired ‘Program’. This is from ‘Other Table Files: (5521) Program’, not a program in ‘Program Maintenance’.
  35. Select the desired ‘Account’.
  36. Select the desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
  37. Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgment’.
  38. Select the desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’, or the ‘Deposit Date’.
  39. If desired, enter a ‘Comment’.
  40. Validate that the ‘Posting Summary’ is correct.
  41. If desired, click [New Row] and repeat the steps.
  42. If desired, click [Delete Row]. A ‘Confirm Delete’ message will be displayed. Select the desired value.
  43. Click [File].
  44. The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
  45. Click [Yes].
  46. Click the ‘Reverse’ checkbox in one row of the ‘Post Payment Accounting Entry’.
  47. Enter desired ‘Reversal Reason’.
  48. Click [Reverse].
  49. Validate that a message is received stating: Reversal Posting Date is required.
  50. Enter a ‘Reversal Posting Date’ that is on or after the ‘Posting Date’.
  51. Click [Reverse].
  52. Validate that a new row was added to the ‘Post Payment Accounting Entry’ grid and that it mirrors the row that was selected to reverse, except for ‘Amount’ displays in parentheses, indicating a negative amount. The ‘Comment’ for the new row will contain the ‘Reversal Reason’.
  53. Attempt to reverse the row that was previously reversed. Validate that a message is received that states: Rows selected to reverse that are already reversed: xx – where xx is the row number.
  54. If desired, add a new row to post an additional payment.
  55. Close the form.
Scenario 2: Payment Acknowledgement - Adding and Editing rows.
Specific Setup:
  • Registry Setting:
  • ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
  • "Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged" has a 'Registry Setting Value that contains '7' at a minimum.
  • Dictionary Update:
  • Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
  • Other Table Files: (5522) Account - contains dictionary codes, dictionary values, and extended dictionary values.
  • Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
  • Posting/Adjustment Codes Definitions: Definitions exist for ‘Payment’.
  • The definitions may have a value in the ‘Payment Acknowledgement Type’ field.
  • All ‘Payment’ definitions will be available in the ‘Payment Acknowledgement’ form.
  • Clients:
  • Identify clients with and without a self-pay balance due. Note the balance due amounts.
  • Note the 'Treatment Setting' of the client's program.
Steps
  1. Open the ‘Payment Acknowledgement’ form.
  2. Verify that ‘Action’ defaults to ‘New’.
  3. Verify that ‘Transaction Number’ is read-only.
  4. Verify that ‘Entered By’ is read-only and defaults to the signed-in user.
  5. Enter the desired value in ‘Batch Number’.
  6. Select the desired ‘Posting Code’. All payment posting codes will be displayed.
  7. Enter the desired value in ‘Check/EFT Number’.
  8. Enter the desired value in ‘Amount’.
  9. Select the desired ‘Guarantor’. If a ‘Self-Pay' guarantor is selected, the ‘Client’ field will be enabled.
  10. Enter the desired value in ‘Name/Source’.
  11. Enter the desired value in ‘Client’, if enabled. The field is only available for ‘Self-Pay' guarantors.
  12. Enter the desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
  13. Enter the desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
  14. Enter the desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
  15. Select the desired ‘Treatment Service’.
  16. Select the desired ‘Category’. Inactive dictionary codes will not display in this field.
  17. Enter the desired value in ‘Bank Ref #’.
  18. Enter the desired value in ‘Comments’.
  19. Click [File].
  20. Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is xx. Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
  21. Click [Yes] to continue to the Post Payment Accounting Entry section or [No] to remain in the ‘Payment Acknowledgement’ section.
  22. If [Yes] was clicked, go to step 30.
  23. If [No] was clicked, select ‘Edit or View’ in ‘Action, which will enable the ‘Payment Acknowledgement Search’ section.
  24. Enter data from the filed ‘Payment Acknowledgement’ into the desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
  25. Click [Search].
  26. Select the desired item in the ‘Payment Acknowledgement’ grid.
  27. Click [OK] to continue or [Cancel] to end the search. Click [OK].
  28. The following ‘Payment Acknowledgement’ displays: Do you need to continue to Post Payment Accounting Entry?
  29. Click [Yes].
  30. Validate that the grid is not enabled.
  31. Click [New Row] in ‘Post Payment Accounting Entry’.
  32. Validate that the grid becomes enabled.
  33. Select the desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
  34. Select the desired ‘Program’. This is from ‘Other Table Files: (5521) Program’, not a program in ‘Program Maintenance’.
  35. Select the desired ‘Account’.
  36. Select the desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
  37. Validate that the ‘Posting Code' defaulted from the ‘Payment Acknowledgment’.
  38. Select the desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’, or the ‘Deposit Date’.
  39. If desired, enter a ‘Comment’.
  40. Validate that the ‘Posting Summary’ is correct.
  41. Click [New Row] and repeat the steps.
  42. Click [New Row] multiple times, which will create multiple empty rows on the grid.
  43. Click [Delete Row]. A ‘Confirm Delete’ message will be displayed. Select the desired value. (Perform this for all the empty rows created)
  44. Select a row with values and edit one or more values.
  45. Validate the edits are being applied only to the selected row.
  46. Select a different row with values in it.
  47. Validate that when a row is selected that the values display correctly in the respective fields.
  48. Click [File].
  49. The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
  50. Click [No].
  51. Verify that the user remains on the form with all the filed data cleared out.
  52. Select ‘Action’ as ‘Edit or View’.
  53. Validate that the 'Payment Acknowledgement Search' section is getting enabled.
  54. Enter data from the filed ‘Payment Acknowledgement’ into the desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
  55. Click [Search].
  56. Verify the 'Payment Acknowledgement' Grid shows up for user selection.
  57. Select the desired row and click 'OK'.
  58. Validate that all the appropriate entries filed for that Transaction are being loaded into the form.
  59. Select the rows with values in them.
  60. Validate that when a row is selected that the values are showing correctly in the respective fields.
  61. Click the ‘Reverse’ checkbox in one row of the ‘Post Payment Accounting Entry’.
  62. Enter desired ‘Reversal Reason’.
  63. Click [Reverse].
  64. Validate that a message is received stating: Reversal Posting Date is required.
  65. Enter a ‘Reversal Posting Date’ that is on or after the ‘Posting Date’.
  66. Click [Reverse].
  67. Validate that a new row was added to the ‘Post Payment Accounting Entry’ grid and that it mirrors the row that was selected to reverse, except for ‘Amount’ displays in parentheses, indicating a negative amount. The ‘Comment’ for the new row will contain the ‘Reversal Reason’.
  68. Attempt to reverse the row that was previously reversed. Validate that a message is received that states: Rows selected to reverse that are already reversed: xx – where xx is the row number.
  69. If desired, add a new row to post an additional payment.
  70. Close the form.
Payment Acknowledgement - Post Front Office and myHP Payments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Deposit Entry
  • Payment Acknowledgement
Scenario 1: Payment Acknowledgement - Post Front Office Payments - Deposit Entry / Scheduling Calendar Check In
Specific Setup:
  • Registry Setting:
  • The 'Enable Payment Acknowledgement' registry setting is enabled.
  • The 'Prevent Posting Payments Unless Payment has been Acknowledged' registry setting includes value '1'.
  • Client A has a payment collected in Scheduling Calendar Check In. Note the payment date. Note the receipt number in the generated receipt. There is no data in 'Name on Card'.
  • Client B has a payment collected in 'Deposit Entry’. Add a value to 'Name on Card'. Note the payment date. Note the receipt number in the generated receipt.
Steps
  1. Open the ‘Payment Acknowledgment’ form.
  2. Select the ‘Post Front Office and myHP Payments’ section.
  3. Enter the desired ‘Payment Collection Date’.
  4. If desired, select a ‘Treatment Service’.
  5. Select the desired ‘Type’.
  6. Click [Review].
  7. Validate that the grid contains a row for each client and the correct data for the appropriate columns.
  8. Add data to 'Name on Card' for Client A.
  9. Click the checkbox for both rows.
  10. Click [Save].
  11. Click [Yes].
  12. Enter desired ‘Batch Number’.
  13. Enter desired ‘Deposit Date’.
  14. Select desired ‘Category’.
  15. Enter desired ‘Bank Ref #’.
  16. If desired, enter ‘Comments’.
  17. Click [Post].
  18. Validate that a ‘Conform’ message is received stating ‘Filed successfully’.
  19. Click [OK].
  20. Click [Discard].
  21. Click [Yes] on the ‘Confirm Close’ message.
Payment Acknowledgement - Comments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Posting/Adjustment Codes Definition
  • Payment Acknowledgement
  • Service Codes
Scenario 1: Payment Acknowledgement - Editing Comments
Specific Setup:
  • Registry Setting:
  • ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
  • "Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged" has a 'Registry Setting Value that contains '7'
  • Dictionary Update:
  • Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
  • Other Table Files: (5522) Account - contains dictionary codes, dictionary values, and extended dictionary values.
  • Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
  • Posting/Adjustment Codes Definitions: Definitions exist for ‘Payment’.
  • The definitions may have a value in the ‘Payment Acknowledgement Type’ field.
  • All ‘Payment’ definitions will be available in the ‘Payment Acknowledgement’ form.
  • Clients:
  • Identify clients with and without a self pat balance. Note the balance due amounts.
  • Note the 'Treatment Setting' of the client's program.
Steps
  1. Open the ‘Payment Acknowledgement’ form.
  2. Verify that ‘Action’ defaults to ‘New’.
  3. Verify that ‘Transaction Number’ is read-only.
  4. Verify that ‘Entered By’ is read-only and defaults to the signed-in user.
  5. Enter the desired value in ‘Batch Number’.
  6. Select the desired ‘Posting Code’. All payment posting codes will be displayed.
  7. Enter the desired value in ‘Check/EFT Number’.
  8. Enter the desired value in ‘Amount’.
  9. Select the desired ‘Guarantor’. If a ‘Self-Pay' guarantor is selected, the ‘Client’ field will be enabled.
  10. Enter the desired value in ‘Name/Source’.
  11. Enter the desired value in ‘Client’, if enabled. The field is only available for ‘Self-Pay' guarantors.
  12. Enter the desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
  13. Enter the desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
  14. Enter the desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
  15. Select the desired ‘Treatment Service’.
  16. Select the desired ‘Category’. Inactive dictionary codes will not display in this field.
  17. Enter the desired value in ‘Bank Ref #’.
  18. Enter the desired value in ‘Comments’.
  19. Click [File].
  20. Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is 6. Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
  21. Click [Yes] to continue to the Post Payment Accounting Entry section or [No] to remain in the ‘Payment Acknowledgement’ section.
  22. If [Yes] was clicked, go to step 36.
  23. If [No] was clicked, select ‘Edit or View’ in ‘Action, which will enable the ‘Payment Acknowledgement Search’ section.
  24. Enter data from the filed ‘Payment Acknowledgement’ into the desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
  25. Click [Search].
  26. Select the desired item in the ‘Payment Acknowledgement’ grid.
  27. Click [OK] to continue or [Cancel] to end the search. Click [OK].
  28. The following ‘Payment Acknowledgement’ displays: Do you need to continue to Post Payment Accounting Entry?
  29. Click [Yes].
  30. Validate that the 'Comments' field under the first section is enabled.
  31. Validate that the correct value is being populated for the 'Comments' box.
  32. Update the value in the 'Comments' box.
  33. Click [File].
  34. Click [Yes] to continue to the Post Payment Accounting Entry section or [No] to remain in the ‘Payment Acknowledgement’ section.
  35. Select [Yes]
  36. Validate that the grid is not enabled.
  37. Click [New Row] in ‘Post Payment Accounting Entry’.
  38. Validate that the grid becomes enabled.
  39. Select the desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
  40. Select the desired ‘Program’. This is from ‘Other Table Files: (5521) Program’, not a program in ‘Program Maintenance’.
  41. Select the desired ‘Account’.
  42. Select the desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
  43. Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgment’.
  44. Select the desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’, or the ‘Deposit Date’.
  45. Enter a ‘Comment’.
  46. Validate that the ‘Posting Summary’ is correct.
  47. Click [New Row] in ‘Post Payment Accounting Entry’.
  48. Validate that the grid becomes enabled.
  49. Select the desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
  50. Select the desired ‘Program’. This is from ‘Other Table Files: (5521) Program’, not a program in ‘Program Maintenance’.
  51. Select the desired ‘Account’.
  52. Try Entering a negative value for the 'Amount' field.
  53. Validate that the user is not allowed to enter a negative value and see the appropriate error popup message.
  54. Select the desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
  55. Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgment’.
  56. Select the desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’, or the ‘Deposit Date’.
  57. If desired, enter a ‘Comment’.
  58. Validate that the ‘Posting Summary’ is correct. (Even though the entered/shown amount is a positive value, based on the Posting code type the amount value should be shown as a negative one in the 'Posting Summary')
  59. If desired, click [New Row] and repeat the steps.
  60. If desired, click [Delete Row]. A ‘Confirm Delete’ message will be displayed. Select the desired value.
  61. Click [File].
  62. The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
  63. Click [No].
  64. Select ‘Edit or View’ in ‘Action, which will enable the ‘Payment Acknowledgement Search’ section.
  65. Enter data from the filed ‘Payment Acknowledgement’ into the desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
  66. Click [Search].
  67. Select the desired item in the ‘Payment Acknowledgement’ grid.
  68. Click [OK] to continue or [Cancel] to end the search. Click [OK].
  69. Validate that the 'Comments' field under the first section is enabled.
  70. Validate that the correct value is being populated for the 'Comments' box.
  71. Delete the values in the 'Comments' box and make it empty.
  72. Click [File].
  73. Click [Yes] to continue to the Post Payment Accounting Entry section or [No] to remain in the ‘Payment Acknowledgement’ section.
  74. Select [No]
  75. Select ‘Edit or View’ in ‘Action, which will enable the ‘Payment Acknowledgement Search’ section.
  76. Enter data from the filed ‘Payment Acknowledgement’ into the desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
  77. Click [Search].
  78. Select the desired item in the ‘Payment Acknowledgement’ grid.
  79. Click [OK] to continue or [Cancel] to end the search. Click [OK].
  80. The following ‘Payment Acknowledgement’ displays: Do you need to continue to Post Payment Accounting Entry?
  81. Click [Yes].
  82. Validate that the 'Comments' field under the first section is enabled.
  83. Validate that the correct value is being populated for the 'Comments' box.
  84. Close the form.
  85. Select the PM namespace.
  86. Identify desired database and SQL table - SYSTEM.billing_pay_adj_history
  87. Query 'select * from SYSTEM.billing_pay_adj_historySELECT * FROM "SYSTEM".pay_ack_post_pay_acc_ent' for the desired transaction_number.
  88. Validate that all the instances filed for the Post Payment Accounting Entry are shown in the table.
  89. Validate that the ID cell contains the correct information.
  90. Validate that the account_value cell is equal to the PATID set up in the setup section.
  91. Validate that the comments column contains the correct respective value.
  92. Validate that the data_entry_by column contains the correct respective value.
  93. Validate that the data_entry_date column contains the correct respective value.
  94. Validate that the data_entry_time column contains the correct respective value.
  95. Validate that the data_entry_user_id column contains the correct respective value.
  96. Validate that the data_entry_user_name column contains the correct respective value.
  97. Validate that the option_desc column contains the correct respective value.
  98. Validate the option_id column equal to 'RemittanceProcWidget'.
  99. Validate that the payment_amount column contains the correct respective value.
  100. Validate that the payment_type_code column is equal to 'PAYMENT'.
  101. Validate that the payment_type_value column contains the correct respective value.
  102. Validate that the posting_date column contains the correct respective value.
  103. Validate that the program_code column contains the correct respective value.
  104. Validate that the program_value column contains the correct respective value.
  105. Validate that the transaction_number column contains the correct respective value.
  106. Close the SQL data viewer.
Scenario 2: Payment Acknowledgement - Post Payment Accounting Entry / Reverse Payment Accounting Entry
Specific Setup:
  • Registry Setting:
  • ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
  • "Avatar PM->Billing->Remittance Processing->->->Prevent Posting Payments Unless Payment has been Acknowledged" has a 'Registry Setting Value that contains '7'
  • Dictionary Update:
  • Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
  • Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
  • Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
  • Posting/Adjustment Codes Definitions: Definitions exist for ‘Payment’.
  • The definitions may have a value in the ‘Payment Acknowledgement Type’ field.
  • All ‘Payment’ definitions will be available in the ‘Payment Acknowledgement’ form.
  • Clients:
  • Identify clients with and without a self-pay balance due. Note the balance due amounts.
  • Note the 'Treatment Setting' of the client's program.
Steps
  1. Open the ‘Payment Acknowledgement’ form.
  2. Verify that ‘Action’ defaults to ‘New’.
  3. Verify that ‘Transaction Number’ is read-only.
  4. Verify that ‘Entered By’ is read-only and defaults to the signed-in user.
  5. Enter the desired value in ‘Batch Number’.
  6. Select the desired ‘Posting Code’. All payment posting codes will be displayed.
  7. Enter the desired value in ‘Check/EFT Number’.
  8. Enter the desired value in ‘Amount’.
  9. Select the desired ‘Guarantor’. If a ‘Self-Pay' guarantor is selected, the ‘Client’ field will be enabled.
  10. Enter the desired value in ‘Name/Source’.
  11. Enter the desired value in ‘Client’, if enabled. The field is only available for ‘Self-Pay' guarantors.
  12. Enter the desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
  13. Enter the desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
  14. Enter the desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
  15. Select the desired ‘Treatment Service’.
  16. Select the desired ‘Category’. Inactive dictionary codes will not display in this field.
  17. Enter the desired value in ‘Bank Ref #’.
  18. Enter the desired value in ‘Comments’.
  19. Click [File].
  20. Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is 6. Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
  21. Click [Yes] to continue to the Post Payment Accounting Entry section or [No] to remain in the ‘Payment Acknowledgement’ section.
  22. If [Yes] was clicked, go to step 30.
  23. If [No] was clicked, select ‘Edit or View’ in ‘Action, which will enable the ‘Payment Acknowledgement Search’ section.
  24. Enter data from the filed ‘Payment Acknowledgement’ into the desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
  25. Click [Search].
  26. Select the desired item in the ‘Payment Acknowledgement’ grid.
  27. Click [OK] to continue or [Cancel] to end the search. Click [OK].
  28. The following ‘Payment Acknowledgement’ displays: Do you need to continue to Post Payment Accounting Entry?
  29. Click [Yes].
  30. Validate that the grid is not enabled.
  31. Click [New Row] in ‘Post Payment Accounting Entry’.
  32. Validate that the grid becomes enabled.
  33. Select the desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
  34. Select the desired ‘Program’. This is from ‘Other Table Files: (5521) Program’, not a program in ‘Program Maintenance’.
  35. Select the desired ‘Account’.
  36. Select the desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
  37. Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgment’.
  38. Select the desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’, or the ‘Deposit Date’.
  39. If desired, enter a ‘Comment’.
  40. Validate that the ‘Posting Summary’ is correct.
  41. If desired, click [New Row] and repeat the steps.
  42. If desired, click [Delete Row]. A ‘Confirm Delete’ message will be displayed. Select the desired value.
  43. Click [File].
  44. The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
  45. Click [Yes].
  46. Click the ‘Reverse’ checkbox in one row of the ‘Post Payment Accounting Entry’.
  47. Enter desired ‘Reversal Reason’.
  48. Click [Reverse].
  49. Validate that a message is received stating: Reversal Posting Date is required.
  50. Enter a ‘Reversal Posting Date’ that is on or after the ‘Posting Date’.
  51. Click [Reverse].
  52. Validate that a new row was added to the ‘Post Payment Accounting Entry’ grid and that it mirrors the row that was selected to reverse, except for ‘Amount’ displays in parentheses, indicating a negative amount. The ‘Comment’ for the new row will contain the ‘Reversal Reason’.
  53. Attempt to reverse the row that was previously reversed. Validate that a message is received that states: Rows selected to reverse that are already reversed: xx – where xx is the row number.
  54. If desired, add a new row to post an additional payment.
  55. Close the form.
835 Health Care Claim Payment/Advice
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Claim Adjustment Group/Reason Code Definition
  • Crystal Report Viewer
  • Guarantors/Payors
  • Default Guarantor Assignment
  • Posting/Adjustment Codes Definition
  • Admission (Outpatient)
  • Financial Eligibility
  • Diagnosis
  • 835 Health Care Claim Payment/Advice (PM)
  • Client Ledger
  • Create Interim Billing Batch File
  • Electronic Billing
  • Payment Acknowledgement
  • Client Charge Input
  • Dynamic Form - Form and Table Documentation / File Export - File Name
Scenario 1: 835 Health Care Claim Payment/Advice - Three checks per file - Posting Acknowledged, Unacknowledged and Zero dollar payments
Specific Setup:
  • Registry Setting:
  • The 'Enable Payment Acknowledgement' registry setting is enabled.
  • The 'Prevent Posting Payments Unless Payment has been Acknowledged' registry setting includes value '1'.
  • The 'Check Number' registry setting is set to '1'.
  • The 'Posting Date for Automated 835s' registry setting is set to '1'.
  • Claim Adjustment Group/ reason code Definition:
  • A group code is selected for the credit adjustment code and debit adjustment reversal code. Note the adjustment codes and group code setup.
  • Admission:
  • Admit a client into an outpatient episode. Note the Client id/name, Admission date/program.
  • Guarantor/Payors:
  • Two existing guarantors are identified who have a Financial Class that has the Extended Data Element for (1500) System Financial Class set to Self Pay.
  • Financial Eligibility:
  • The desired guarantors identified above are assigned to the client. Note the primary and secondary guarantor.
  • Client Charge Input:
  • A service is rendered to the client.
  • Client Ledger:
  • Make sure the service is distributed to one of the guarantors assigned to the client.
  • Close charges.
  • Electronic Billing:
  • Claim the service using the 837 Professional bill for the guarantor.
  • Create an 835 file based on the claim information found in the 837 professional bill.
Steps
  1. Open the '835 Health Care Claim Payment/Advice' form.
  2. Load and compile the 835 file created that includes the claim for the defined guarantor in the setup.
  3. Verify the 835 file loads/compiles successfully.
  4. Select 'Post File' option.
  5. Select the compiled file.
  6. Populate all the required fields with desired value.
  7. Verify the Check/EFT# is populated correctly with the status of acknowledged or unacknowledged in the 'Check/EFT#' checkbox.
  8. Check the Check/EFT# that is unacknowledged.
  9. Click [Process File].
  10. Verify the message: 'Selecting Unacknowledged Check/EFT numbers is not permitted.'
  11. Click [OK].
  12. Close the form.
  13. Open the ‘Payment Acknowledgment’ form.
  14. Enter desired value in ‘Batch Number’.
  15. Select desired ‘Posting Code’.
  16. Enter desired value in ‘Check/EFT Number’ from the TRN*02 segment of the 835 file created in the setup.
  17. Enter desired value in ‘Amount’ that matches the amount entered in the CLP*04 segment of the 835 file.
  18. Select desired ‘Guarantor’ set up in the setup section. Note: If a ‘Self-Pay guarantor is selected, the ‘Client’ field will be enabled.
  19. Enter desired value in ‘Name/Source’.
  20. Enter desired value in ‘Client’, if enabled.
  21. Enter desired value in ‘Check/EFT Date’ that matches the date entered in the BPR*16 segment of the 835 file.
  22. Enter desired value in ‘Receipt Date’.
  23. Enter desired value in ‘Deposit Date’.
  24. Select desired ‘Treatment Service’.
  25. Select desired ‘Category’.
  26. Enter desired value in ‘Bank Ref #’.
  27. Enter desired value in ‘Comments’.
  28. Click [File].
  29. Verify that the ‘Payment Acknowledgment’ message is received and states the following: Filed successfully. The Transaction Number is [number] Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
  30. Click [No].
  31. Close the form.
  32. Open the '835 Health Care Claim Payment/Advice' form.
  33. Select 'Post File' option.
  34. Select the compiled file.
  35. Populate all the required fields with desired value.
  36. Verify the Check/EFT# is populated correctly with the status of acknowledged or unacknowledged in the 'Check/EFT#' checkbox.
  37. Check the Check/EFT# that acknowledged in above steps.
  38. Click [Process File].
  39. Verify the file posts successfully.
  40. Open the 'Client Ledger' for the client.
  41. Verify the payments are posted correctly on the ledger.
  42. Open the 'Crystal Report' or any other SQL Data viewer.
  43. Create a query to retrieve data from the SYSTEM.billing_pay_adj_history table.
  44. Validate the check number field contains check number from the TRN-02 segment of the 835 file.
  45. Validate the 'pay_acknowledge_trans_num' column contains the transaction number from the 'Payment Acknowledgement' form for the Check/EFT.
Scenario 2: 835 Healthcare Claim Payment/Advice - One check per file - Posting acknowledged payments and adjustments
Specific Setup:
  • Registry Setting:
  • The 'Enable Payment Acknowledgement' registry setting is enabled.
  • The 'Prevent Posting Payments Unless Payment has been Acknowledged' registry setting includes value '1'.
  • The 'Check Number' registry setting is set to '1'.
  • The 'Posting Date for Automated 835s' registry setting is set to '1'.
  • Claim Adjustment Group/ reason code Definition:
  • A group code is selected for the credit adjustment code and debit adjustment reversal code. Note the adjustment codes and group code setup.
  • Admission:
  • Admit a client into an outpatient episode. Note the Client id/name, Admission date/program.
  • Guarantor/Payors:
  • Two existing guarantors are identified who have a Financial Class that has the Extended Data Element for (1500) System Financial Class set to Self Pay.
  • Financial Eligibility:
  • The desired guarantors identified above are assigned to the client. Note the primary and secondary guarantor.
  • Client Charge Input:
  • A service is rendered to the client.
  • Client Ledger:
  • Make sure the service is distributed to one of the guarantors assigned to the client.
  • Close charges.
  • Electronic Billing:
  • Claim the service using the 837 Professional bill for the guarantor.
  • Create an 835 file based on the claim information found in the 837 professional bill.
Steps
  1. Open the '835 Health Care Claim Payment/Advice' form.
  2. Load and compile the 835 file created that includes the claim for the defined guarantor in the setup.
  3. Verify the 835 file loads/compiles successfully.
  4. Select 'Post File' option.
  5. Select the file that is recently compiled successfully.
  6. Populate all the required fields with desired value.
  7. Verify the Check/EFT# is populated correctly with the status of acknowledged or unacknowledged in the 'Check/EFT#' checkbox.
  8. Check the Check/EFT# that is unacknowledged.
  9. Click [Process File].
  10. Verify the message: 'Selecting Unacknowledged Check/EFT numbers is not permitted.'
  11. Click [OK].
  12. Close the form.
  13. Open the ‘Payment Acknowledgment’ form.
  14. Enter desired value in ‘Batch Number’.
  15. Select desired ‘Posting Code’.
  16. Enter desired value in ‘Check/EFT Number’ from the TRN*02 segment of the 835 file created in the setup.
  17. Enter desired value in ‘Amount’ that matches the amount entered in the CLP*04 segment of the 835 file.
  18. Select desired ‘Guarantor’ set up in the setup section. Note: If a ‘Self-Pay guarantor is selected, the ‘Client’ field will be enabled.
  19. Enter desired value in ‘Name/Source’.
  20. Enter desired value in ‘Client’, if enabled.
  21. Enter desired value in ‘Check/EFT Date’ that matches the date entered in the BPR*16 segment of the 835 file.
  22. Enter desired value in ‘Receipt Date’.
  23. Enter desired value in ‘Deposit Date’.
  24. Select desired ‘Treatment Service’.
  25. Select desired ‘Category’.
  26. Enter desired value in ‘Bank Ref #’.
  27. Enter desired value in ‘Comments’.
  28. Click [File].
  29. Verify that the ‘Payment Acknowledgment’ message is received and states the following: Filed successfully. The Transaction Number is [number] Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing. Note the transaction number.
  30. Click [No].
  31. Close the form.
  32. Open the '835 Health Care Claim Payment/Advice' form.
  33. Select 'Post File' option.
  34. Select the file that is recently compiled successfully.
  35. Populate all the required fields with desired value.
  36. Verify the Check/EFT# is populated correctly with the status of acknowledged or unacknowledged in the 'Check/EFT#' checkbox.
  37. Check the Check/EFT# that acknowledged in above steps.
  38. Click [Process File].
  39. Verify the file posts successfully.
  40. Open the 'Client Ledger' for the client.
  41. Verify the payments are posted correctly on the ledger.
  42. Open the 'Crystal Report' or any other SQL Data viewer.
  43. Create a query to retrieve data from the SYSTEM.billing_pay_adj_history table.
  44. Validate the check number field contains check number from the TRN-02 segment of the 835 file.
  45. Validate the date of payment column contains the posting date from the '835 Health Care Claim Payment/Advice' form.
  46. Validate the 'pay_acknowledge_trans_num' column contains the transaction number from the 'Payment Acknowledgement' form for the Check/EFT.
Topics
• NX • Payment Acknowledgement • 835 Health Care Claim Payment/Advice
Update 146 Summary | Details
Client Name - 'Client Prefix' and 'Client Suffix' fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission
  • Update Client Data
Scenario 1: Update Client Data - 'Client Demographics - Additional Fields' registry setting includes "Detailed Client Name"
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • The 'Client Demographics - Additional Fields' registry setting includes "Detailed Client Name".
Steps
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Enter the desired value in the 'Client Last Name' field.
  3. Enter the desired value in the 'Client First Name' field.
  4. Enter the desired value in the 'Client Middle Name' field.
  5. Select the desired value in the 'Client Prefix' field.
  6. Select the desired value in the 'Client Suffix' field.
  7. Click [Submit].
  8. Validate the 'My Clients' list displays "Client A" with the 'Client Prefix' and 'Client Suffix'.
  9. Validate the 'Recent Clients' list displays "Client A" with the 'Client Prefix' and 'Client Suffix'. Please note: this is not yet supported in Avatar NX.
  10. Select "Client A" and access the 'Update Client Data' form.
  11. Validate the 'Client Header' displays "Client A" with the 'Client Prefix' and 'Client Suffix'. Please note: this is not yet supported in the 'Condensed Client Header' in Avatar NX.
  12. Validate the 'Client Last Name' field contains the value filed in the previous steps.
  13. Validate the 'Client First Name' field contains the value filed in the previous steps.
  14. Validate the 'Client Middle Name' field contains the value filed in the previous steps.
  15. Validate the 'Client Prefix' field contains the value filed in the previous steps.
  16. Validate the 'Client Suffix' field contains the value filed in the previous steps.
  17. Close the form.
  18. Access Crystal Reports or other SQL Reporting Tool.
  19. Create a report using the 'patient_current_demographics' SQL table.
  20. Validate a row is displayed for "Client A".
  21. Validate the 'patient_name_last' field contains the value filed in the previous steps.
  22. Validate the 'patient_name_first' field contains the value filed in the previous steps.
  23. Validate the 'patient_name_middle' field contains the value filed in the previous steps.
  24. Validate the 'patient_name_prefix_value' field contains the value filed in the previous steps.
  25. Validate the 'patient_name_suffix_value' field contains the value filed in the previous steps.
  26. Close the report.
Topics
• Registry Settings • Update Client Data
Update 148 Summary | Details
Registry Setting - Define Alternate Values for 837P-2300-NTE-02 (HCFA-1500 Form Locator 19)'.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Practitioner Numbers By Guarantor And Program
  • Admission
  • Financial Eligibility
  • Diagnosis
  • Client Charge Input
  • Create Interim Billing Batch File
  • Electronic Billing
  • Print Bill
Scenario 1: Registry Setting - Define Alternate Values for 837P-2300-NTE-02 (HCFA-1500 Form Locator 19) = Y
Specific Setup:
  • Registry Setting:
  • Avatar PM->System Maintenance->System Definition->Practitioner Numbers->->Enable New Practitioner Numbers By Guarantor and Program Form = ‘Y’.
  • Avatar PM->System Maintenance->System Definition->Practitioner Numbers->->Specify Additional Fields To Show = ‘2’, at a minimum.
  • Avatar PM->Billing->Electronic Billing->837 Professional->->Define Alternate Values for 837P-2300-NTE-02 (HCFA-1500 Form Locator 19) = ‘Y’.
  • Client A: Identify an active client that can be billed using 837 Professional or HCFA-1500 billing.
  • Note the client’s program.
  • Validate that there is an active Diagnosis record.
  • Validate that there is an active Financial Eligibility record, noting the guarantor(s). Note the Financial Class(es).
  • Guarantor/Program Billing Defaults:
  • Paper CMS 1500 section: Enter any value in ‘Form Locator 19 text’. Note the value.
  • 837 Professional section:
  • Select desired value in ‘Claim Note Reference Code (837P-2300-NTE-01)’.
  • Enter desired value on ‘Claim Note Text (837P-2300-NTE-02)’.
  • Select 'Participating Provider Information for AHCCCS Billing' in 'Claim Note Text (837P-2300-NTE-02) Alternate Value'.
  • Set ‘Maximum Service Information Per Claim Information (Maximum LX Per CLM)’ to ‘1’.
  • Practitioner Enrollment: Identify a minimum of two practitioners that will be used for billing services.
  • Practitioner Numbers By Guarantor and Program:
  • For one of the practitioners selected above, select the clients’ program and guarantors, and edit the existing record to add a unique value to the 'HCFA-1500 Form Locator 19' field and the ‘Claim Note Text (837P-2300-NTE-02)’ field.
  • For the other practitioner, add '9999999999' to the 'HCFA-1500 Form Locator 19' field and the ‘Claim Note Text (837P-2300-NTE-02)’ field.
  • Client Charge Input: Create a charge for the client and one of the practitioners. Note the date.
  • Create Interim Billing Batch File is used to create a batch for the service.
  • Close Charges is used to close the charges.
  • Client Charge Input: Create a charge for the other practitioner. Note the date.
  • Create Interim Billing Batch File is used to create a batch for the service.
  • Close Charges is used to close the charges.
Steps
  1. Open ‘Print Bill’.
  2. Enter the last date of service in ‘Print Charges Thru’.
  3. Select ‘No’ in ‘Create Claims Y/N’.
  4. Select ‘HCFA-1500-NPI Version (Sort By Practitioner) in ‘Print On What Form’.
  5. Select ‘Yes’ in ‘Print For Interim Batch’.
  6. Select the ‘Interim Batch Number’ for the practitioner that has '9999999999' to the 'HCFA-1500 Form Locator 19' field.
  7. Click [Process].
  8. Validate that ‘Form Locator 19’ field contains '9999999999' in the 'HCFA-1500 Form Locator 19' field.
  9. Close the report.
  10. Close the form.
  11. Repeat steps 1 - 8 for the other interim batch.
  12. Validate that ‘Form Locator 19’ field contains 'XX' before the unique value to the 'HCFA-1500 Form Locator 19' field
  13. Close the report.
  14. Close the form.
  15. Open ‘Electronic Billing’.
  16. Select ‘837-Professional’ in ‘Billing Form’.
  17. Select the desired ‘Financial Class’ in ‘Type Of Bill’.
  18. Select ‘Individual’ in ‘Individual Or All Guarantors’.
  19. Select the desired ‘Guarantor’.
  20. Select desired value in ‘Billing Type’.
  21. Select ‘Sort File’ in ‘Billing Options’.
  22. Enter desired ‘File Description’.
  23. Select ‘Interim Batch’ in ‘All Clients Or Interim Billing Batch’.
  24. Select the ‘Interim Billing Batch Number’ for the practitioner that has '9999999999' in the ‘Claim Note Text (837P-2300-NTE-02)’ field.
  25. Select ‘No’ in ‘Create Claims’.
  26. Enter the ‘First Date Of Service To Include’.
  27. Enter the ‘Last Date Of Service To Include’.
  28. Select ‘All’ in ‘Include Primary and/or Secondary Billing’.
  29. Click [Process].
  30. Click [OK] on ‘Compile Complete’ message.
  31. Select ‘Dump File’ in ‘Billing Options’.
  32. Select ‘Print’ in ‘Select ‘Dump File’ in ‘Billing Options’.
  33. Select the ‘File’, which contains the ‘File Description’ added above.
  34. Click [Process].
  35. Validate that the NTE segment contains '9999999999' before the practitioner name.
  36. Close the report.
  37. Repeat steps 16-34 for the other interim batch.
  38. Validate that the NTE segment contains 'XX' before the unique value and the practitioner name.
  39. Close the report.
  40. Close the form.
Scenario 2: Registry Setting - Define Alternate Values for 837P-2300-NTE-02 (HCFA-1500 Form Locator 19) = N
Specific Setup:
  • Registry Setting:
  • Avatar PM->System Maintenance->System Definition->Practitioner Numbers->->Enable New Practitioner Numbers By Guarantor and Program Form = ‘Y’.
  • Avatar PM->System Maintenance->System Definition->Practitioner Numbers->->Specify Additional Fields To Show = ‘2’, at a minimum.
  • Avatar PM->Billing->Electronic Billing->837 Professional->->Define Alternate Values for 837P-2300-NTE-02 (HCFA-1500 Form Locator 19) = ‘N’.
  • Client A: Identify an active client that can be billed using 837 Professional or HCFA-1500 billing.
  • Note the client’s program.
  • Validate that there is an active Diagnosis record.
  • Validate that there is an active Financial Eligibility record, noting the guarantor(s). Note the Financial Class(es).
  • Guarantor/Program Billing Defaults:
  • Paper CMS 1500 section: Enter any value in ‘Form Locator 19 text’. Note the value.
  • 837 Professional section: Select desired value in ‘Claim Note Reference Code (837P-2300-NTE-01)’. Enter desired value on ‘Claim Note Text (837P-2300-NTE-02)’. Set ‘Maximum Service Information Per Claim Information (Maximum LX Per CLM)’ to ‘1’.
  • Practitioner Enrollment: Identify a minimum of two practitioners that will be used for billing services.
  • Practitioner Numbers By Guarantor and Program:
  • For the practitioners selected above, select the clients’ program and guarantors, and edit the existing record to add unique values to the 'HCFA-1500 Form Locator 19' field and the ‘Claim Note Text (837P-2300-NTE-02)’ field.
  • Client Charge Input: Create a charge for the client and one of the practitioners. Note the date.
  • Create Interim Billing Batch File is used to create a batch for the service.
  • Close Charges is used to close the charges.
  • Client Charge Input: Create a charge for the other practitioner. Note the date.
  • Create Interim Billing Batch File is used to create a batch for the service.
  • Close Charges is used to close the charges.
Steps
  1. Open ‘Print Bill’.
  2. Enter the last date of service in ‘Print Charges Thru’.
  3. Select ‘No’ in ‘Create Claims Y/N’.
  4. Select ‘HCFA-1500-NPI Version (Sort By Practitioner) in ‘Print On What Form’.
  5. Select ‘Yes’ in ‘Print For Interim Batch’.
  6. Select desired ‘Interim Batch Number’.
  7. Click [Process].
  8. Validate that ‘Form Locator 19’ field contains the value added to ‘Practitioner Numbers By Guarantor and Program’ during setup for the service practitioner.
  9. Close the report.
  10. Close the form.
  11. Repeat steps 1-9 for the other interim batch.
  12. Open ‘Electronic Billing’.
  13. Select ‘837-Professional’ in ‘Billing Form’.
  14. Select the desired ‘Financial Class’ in ‘Type Of Bill’.
  15. Select ‘Individual’ in ‘Individual Or All Guarantors’.
  16. Select the desired ‘Guarantor’.
  17. Select desired value in ‘Billing Type’.
  18. Select ‘Sort File’ in ‘Billing Options’.
  19. Enter desired ‘File Description’.
  20. Select ‘Interim Batch’ in ‘All Clients Or Interim Billing Batch’.
  21. Select ‘desired ‘Interim Billing Batch Number’.
  22. Select ‘No’ in ‘Create Claims’.
  23. Enter the ‘First Date Of Service To Include’.
  24. Enter the ‘Last Date Of Service To Include’.
  25. Select ‘All’ in ‘Include Primary and/or Secondary Billing’.
  26. Click [Process].
  27. Click [OK] on ‘Compile Complete’ message.
  28. Select ‘Dump File’ in ‘Billing Options’.
  29. Select ‘Print’ in ‘Select ‘Dump File’ in ‘Billing Options’.
  30. Select the ‘File’, which contains the ‘File Description’ added above.
  31. Click [Process].
  32. Validate that the NTE segment contains the values added to ‘Claim Note Reference Code (837P-2300-NTE-01)’ in ‘Practitioner Numbers By Guarantor and Program’.
  33. Close the report.
  34. Repeat steps 12- 33 for the other interim batch.
Topics
• Print Bill • 837 Professional • NX
Update 149 Summary | Details
File Import - Posting/Adjustment Code Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • File Import
  • Crystal Report Viewer
  • Posting/Adjustment Codes Definition
Scenario 1: File Import: Posting/Adjustment Codes Definition
Specific Setup:
  • The registry setting 'Import File Delimiter' is enabled with desired value.
  • File Import:
  • A file import file of 'Posting/Adjustment Codes Definition' file type is created to add a new posting code.
  • A file import file of 'Posting/Adjustment Codes Definition' file type is created to edit the above posting code.
Steps
  1. Open the 'File Import' form.
  2. Select the 'Posting/Adjustment Codes Definition' from the 'File Type' field.
  3. Upload the 'add' file created in the setup section.
  4. Compile the file.
  5. Verify the information message : 'Compiled'.
  6. Click [OK].
  7. Post the file.
  8. Verify the file posted successfully.
  9. Close the form.
  10. Open the 'Posting/Adjustment Codes Definition' form.
  11. Validate the Code contains the imported data.
  12. Close the form.
  13. Open the 'File Import' form.
  14. Select the 'Posting/Adjustment Codes Definition' from the 'File Type' field.
  15. Upload the 'edit' file created in the setup section.
  16. Compile the file.
  17. Verify the information message : 'Compiled'.
  18. Click [OK].
  19. Post the file.
  20. Verify the file posted successfully.
  21. Close the form.
  22. Open the 'Posting/Adjustment Codes Definition' form.
  23. Validate the Code contains the edited imported data.
  24. Close the form.
Topics
• File Import • Posting/Adjustment Codes Definition • NX
Update 150 Summary | Details
Quick billing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Quick Billing
  • Guarantors/Payors
  • Admission (Outpatient)
  • Financial Eligibility
  • Diagnosis
  • Client Ledger
  • Quick Billing Rule Definition
  • Crystal Report Viewer
Scenario 1: 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 program 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.
  • An '837 Professional' is selected in the 'Billing Form' field.
  • The guarantors assigned to the clients in their financial eligibility are 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. Run 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 completes and the prompt states 'Compile Complete'. 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. Submit the form again.
  15. Click [OK].
  16. Select the 'Edit Existing' option.
  17. Select the quick bill that was created in the previous step.
  18. Click [Print 837 Report].
  19. Verify the report launched successfully.
  20. Close the report.
  21. Click [Launch Workscreen].
  22. Verify the work screen contains all the clients included in the batch.
  23. Deselect one client from the 'Client' filter at the top of the work screen.
  24. Verify the grid does not display the services of that client.
  25. Select the same client again from the 'Client' filter at the top of the work screen.
  26. Verify the grid displays the services of that client.
  27. Save the grid.
  28. Verify the grid saves successfully.
  29. Close the form.
Topics
• Quick Billing
Update 154 Summary | Details
Demographic forms - Time Zone for Appointment Reminders
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Admission
  • Update Client Data
  • Pre Admit
  • Pre Admit Discharge
  • Assign MR#
  • Discharge Web Service
  • Discharge
  • SoapUI - ClientDemographics
  • SoapUI - UpdateAdmission
  • SOAPUI - ClientCallIntake - UpdateCallIntake
  • SQL Query/Reporting
  • Admission (Outpatient)
  • Leaves
Scenario 1: Validate the 'Admission' form for a new client
Specific Setup:
  • Using the "Site Registration" form:
  • Create additional sites.
  • Using the "Site Hours of Operation" button to enter in operating days/hours for the sites.
  • Using the "User Definition" form:
  • In the "Appointment Scheduling" section, give the user access to the new sites added.
  • Using the "Staff Members Hours and Exceptions" form:
  • Enter hours for the staff member.
Steps
  1. Open the "Admission" form.
  2. Enter a new client into any episode.
  3. Populate the "Preferred Appointment Site" field.
  4. Populate the "Time Zone for Appointment Reminders" field.
  5. Submit to file the form.
  6. Open the "Admission" form.
  7. Edit the admission episode that was just entered.
  8. Validate the data re displays at it was originally entered.
Scenario 2: 'Update Client Data' - Verification of form filing
Specific Setup:
  • If custom Form Designer changes are present in 'Update Client Data' form, please use 'Form Designer' to revert to 'Netsmart Produced Changes'.
  • A client is enrolled in an existing episode (Client A).
  • The 'Enable Address Validation' registry setting must be enabled.
  • Using the "Site Registration" form:
  • Create additional sites.
  • Using the "Site Hours of Operation" button to enter in operating days/hours for the sites.
  • Using the "User Definition" form:
  • In the "Appointment Scheduling" section, give the user access to the new sites added.
  • Using the "Staff Members Hours and Exceptions" form:
  • Enter hours for the staff member.
Steps
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Enter an invalid address in the 'Client's Address - Street' field and press the 'Tab' key.
  3. Validate an 'Address Validation' dialog stating: "The address was invalid for the following reason: Address Not Found. Discard changes?"
  4. Click [No].
  5. Enter an invalid address in the 'Client's Address - Street' field and press the 'Tab' key.
  6. Validate an 'Address Validation' dialog stating: "The address was invalid for the following reason: Address Not Found. Discard changes?"
  7. Click [Yes].
  8. Validate a dialog stating: "Cancelled." and click [OK].
  9. Validate the 'Client's Address - Street' field is cleared.
  10. Enter a valid address and populate any desired fields.
  11. Enter a 'Place of Birth' value that contains 40 characters.
  12. Select a preferred site in the "Preferred Site" field.
  13. Select a time zone in the "Time Zone for Appointment Reminders".
  14. Click [Submit].
  15. Re-enter the form for the client and validate that the data submitted successfully.
Scenario 3: '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. Validate the 'Consent On File For Use of Integrated eSignature' field is present with values of "Yes" and "No".
  5. Select "Yes" in the 'Consent On File For Use of Integrated eSignature' field.
  6. Select the desired value in the "Time Zone for Appointment Reminders".
  7. Click [Submit].
  8. Select "Client A" and access the 'Pre Admit' form.
  9. Select an existing episode and click [Edit].
  10. Select the "Demographics" section.
  11. Validate "Yes" is selected in the 'Consent On File For Use of Integrated eSignature' field.
  12. Validate the desired time zone displays as selected in the "Time Zone for Appointment Reminders" field.
  13. Close the form.
  14. Access Crystal Reports or other SQL reporting tool.
  15. Create a report using the 'SYSTEM.patient_current_demographics' SQL table.
  16. Navigate to the row for "Client A".
  17. Validate the 'esig_consent_on_file_code' field is present and contains "Y".
  18. Validate the 'esig_consent_on_file_value' field is present and contains "Yes".
  19. Close the report.
  20. Create a report using the 'SYSTEM.patient_demographic_history' SQL table.
  21. Navigate to the row for "Client A".
  22. Validate the 'esig_consent_on_file_code' field is present and contains "Y".
  23. Validate the 'esig_consent_on_file_value' field is present and contains "Yes".
  24. Close the report.
Scenario 4: 'Call Intake' form - Field Validation
Specific Setup:
  • 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. Validate the 'Consent On File For Use of Integrated eSignature' field is present with values of "Yes" and "No".
  5. Select "No" in the 'Consent On File For Use of Integrated eSignature' field.
  6. Select "America/Shiprock" in the "Time Zone for Appointment Reminders".
  7. Click [Submit].
  8. Select "Client A" and access the 'Call Intake' form.
  9. Select the existing call intake record and click [Edit].
  10. Select the "Demographics" section.
  11. Validate "No" is selected in the 'Consent On File For Use of Integrated eSignature' field.
  12. Validate "Time Zone for Appointment Reminders" is equal to "America/Shiprock".
  13. Close the form.
  14. Access Crystal Reports or other SQL reporting tool.
  15. Create a report using the 'SYSTEM.patient_current_demographics' SQL table.
  16. Navigate to the row for "Client A".
  17. Validate the 'esig_consent_on_file_code' field is present and contains "N".
  18. Validate the 'esig_consent_on_file_value' field is present and contains "No".
  19. Close the report.
  20. Create a report using the 'SYSTEM.patient_demographic_history' SQL table.
  21. Navigate to the row for "Client A".
  22. Validate the 'esig_consent_on_file_code' field is present and contains "N".
  23. Validate the 'esig_consent_on_file_value' field is present and contains "No".
  24. Close the report.
Scenario 5: Pre Admit Discharge web service validation
Specific Setup:
  • Existing 'Pre Admit' client whose full name is longer than 40 characters.
  • Registry Setting 'Avatar PM->Client Information->Client Demographics->->->Allow Spaces in Client Name' is set to 'Y' to allow spaces. Note: Once enabled, the user will only be able to edit an existing client 'Client Name' field within 'Update Client Data' form.
  • Registry Setting 'Client Demographics - Additional Fields' must be set to include '3: 'Detailed Client Name' to enable this functionality. This setting will add the 'Detail Client Name' fields to the 'Demographics' section of Admission forms.
  • Access to, and understanding of, SoapUI or other Web Service tools.
Steps
  1. Using 'SoapUI' or another web service tool, consume the WSDL for the 'Pre Admit Discharge' form.
  2. Set the 'SystemCode' code to the agency system code for testing.
  3. Set the 'UserName' to the logged in user name.
  4. Set the 'Password' to the logged in user password.
  5. Set the 'DateOfDischarge' to the discharge date.
  6. Set the 'DischargeTime' to the time of discharge.
  7. Set the 'Discharge Practitioner' to a practitioner code (not the practitioner’s name).
  8. Set the 'Client ID' to the ID for the client to be discharged.
  9. Set the 'EpisodeNumber' to the client episode to be discharged.
  10. Set the "PreferredAppointmentSite" to the desired site.
  11. Set the "TimeZoneForAppointmentReminders" to any valid value.
  12. Click [Send].
  13. Review the response and verify the response message displays: <Message>Client Pre-Admit Discharge web service has been filed successfully.</Message>
  14. Open 'Pre Admit Discharge' in Avatar.
  15. Select the client discharged in the Web Service.
  16. Verify the 'Date of Discharge' is set to the date entered in the Web Service.
  17. Verify the 'Time of Discharge' is set to the time entered in the Web Service.
  18. Verify the 'Discharge Practitioner' is set to the practitioner entered in the Web Service.
  19. Verify the "Preferred Appointment Site" is set to the desired site.
  20. Verify the "TimeZoneForAppointmentReminders" is set to the desired value.
  21. Click [Close Form].
Scenario 6: The 'ClientAdmission' - 'AddAdmission' web service: Admission of a new client
Steps
  1. Access SoapUI 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. Populate any other required and desired fields.
  17. Click [Run].
  18. Validate the 'Confirmation' field contains a value such as: "Client Unique ID: # Unique ID: #".
  19. Validate the 'Message' field contains: "Client Admission web service has been filed successfully".
  20. Select the client filed in the previous steps and access the 'Admission' form.
  21. Select the record filed in the previous steps and click [Edit].
  22. Validate all populated fields are displayed.
  23. Select the "Demographics" section.
  24. Validate the 'Client Last Name' field contains the value filed in the previous steps.
  25. Validate the 'Client First Name' field contains the value filed in the previous steps.
  26. Validate the 'Client Middle Name' field contains the value filed in the previous steps.
  27. Validate the 'Consent On File For Use of Integrated eSignature' field contains the value filed in the previous steps.
  28. Validate "Time Zone for Appointment Reminders" field displays as it was recorded.
  29. Close the form.
Scenario 7: Client Discharge Web Service - Verification of web service filing
Specific Setup:
  • Application utilizing the 'Client Discharge' web service (including Netsmart ProviderConnect).
  • Client record with one or more episodes eligible for 'Discharge' record entry.
Steps
  1. Using 'Client Discharge' web service submit 'Discharge' record for valid client and episode.
  2. Set "PreferredAppointmentSite" to the desired value.
  3. Set "TimeZoneForAppointmentReminders" to any valid value.
  4. Ensure that Discharge records filed successfully return confirmation message via web service. (Example: <Confirmation>New discharge filed.</Confirmation> <Message>Client Discharge web service has been filed successfully</Message>)
  5. Open Avatar 'Discharge' form.
  6. Select client record/episode used in 'Client Discharge' web service filing.
  7. Ensure that 'Discharge' record filed via web service is present in Avatar Cal-PM with values filed via web service.
  8. Validate the "Preferred Appointment Site" displays the value that was previously filed with the web service filing.
  9. Validate the "Time Zone For Appointment Reminders" displays the value that was previously filed with the web service filing.
Scenario 8: Client Demographic Web Service validation
Steps
  1. Using soapUI or some other web service tool, file the ClientDemographics web service.
  2. Set up a request to update the client demographic data.
  3. Include the field "PreferredAppointmentSite".
  4. Include the field "TimeZoneForAppointmentReminders".
  5. Submit to file the request.
  6. Open the "Update Client Data" form.
  7. Validate the data that was just filed through the web service is now displayed on the form, including the "Preferred Appointment Site", and the "Time Zone For Appointment Reminders".
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).
  • Include the "Detailed Client Name" functionality for Client Demographics - Additional Fields in the registry setting.
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 'ClientDeclinedToProvideInfo' field.
  7. Enter the desired value in the 'MothersMaidenName' field.
  8. Enter the desired value in the 'NameQualifier' field.
  9. Enter the desired value in the 'OtherLanguages' field.
  10. Enter the desired value in the 'ProtectionIndicator' field.
  11. Enter the desired value in the 'ProtectionIndicatorDate' field.
  12. Enter "Client A" in the 'ClientID' field.
  13. Enter "Client A's" episode in the 'Episode' field.
  14. Enter the desired value in the "PreferredAppointmentSite" field.
  15. Enter the desired value in the "TimeZoneForAppointmentReminders" field.
  16. Click [Run].
  17. Validate the 'Confirmation' field contains a value such as: "Client Unique ID: # Unique ID: #".
  18. Validate the 'Message' field contains: "Client Admission web service has been filed successfully".
  19. Select the client filed in the previous steps and access the 'Admission' form.
  20. Select the admission updated in the previous steps and click [Edit].
  21. Validate all populated fields are displayed.
  22. Validate the 'Client Declined To Provide Information On The Following' field contains the value entered in the previous steps.
  23. Validate the 'Mother's Maiden Name' field contains the value entered in the previous steps.
  24. Validate the 'Protection Indicator' field contains the value entered in the previous steps.
  25. Validate the 'Protection Indicator Effective Date' field contains the value entered in the previous steps.
  26. Validate the 'Name Qualifier' field contains the value entered in the previous steps.
  27. Validate the 'Other Language(s)' field contains the value entered in the previous steps.
  28. Validate the "Preferred Appointment Site" field contains the value entered in the previous steps.
  29. Validate the "Time Zone For Appointment Reminders" field contains the value entered in the previous steps.
  30. Close the form.
Scenario 10: 'ClientCallIntake' Web Service - Verification of 'UpdateCallIntake' Filing
Specific Setup:
  • One or more 'Call Intake' programs must be defined (via Avatar PM 'Program Maintenance' form).
  • Avatar PM Registry Setting 'Auto Assign Next ID' may be enabled or disabled.
  • Existing Avatar PM client/Call Intake record for edit via web service.
  • Application utilizing the Avatar PM 'ClientCallIntake' web service.
Steps
  1. Using Avatar PM 'ClientCallIntake' web service, submit request to 'UpdateCallIntake' method to edit existing Avatar PM Call Intake record, including value for 'SlidingFeeDivideNumFamMembers' ('Divide Sliding Fee Scale Amount by Number of Family Members Receiving Services') and 'SlidingFeeDivideNumFamMembersNum' ('Sliding Fee Scale - Number of Family Members Receiving Services'), PreferredAppointmenSite and "TimeZoneForAppointmentReminders" fields/segments,
  2. Confirm 'ClientCallIntake' web service responds with confirmation data/Client Unique ID on successful filing of 'UpdateCallIntake' method.
  3. Example:"<Confirmation>Client Unique ID : P26 Unique ID: CAL66110.001</Confirmation>"
  4. Confirm 'ClientCallIntake' web service responds with confirmation message on successful filing of 'UpdateCallIntake' method.
  5. Example:"<Message>Client Call Intake web service has been filed successfully.</Message>"
  6. Confirm 'ClientCallIntake' web service responds with successful status value on successful filing of 'UpdateCallIntake' method.
  7. Example:"<Status>1</Status>"
  8. Open Avatar PM 'Call Intake' form and select client/Call Intake record updated via web service for view/update.
  9. Confirm Call Intake record is updated in Avatar PM with values/data submitted via web service including 'Divide Sliding Fee Scale Amount by Number of Family Members Receiving Services' and 'Sliding Fee Scale - Number of Family Members Receiving Services', 'Preferred Appointment Site" and "Time Zone For Appointment Reminders" field values.
Scenario 11: Call Intake Web Service validation - ClientCallIntake
Specific Setup:
  • Any web service tool such as 'SoapUI'
  • Crystal Reports or other SQL tool.
Steps
  1. Using Avatar PM 'ClientCallIntake' web service, submit an Intake record for a 'Call Intake' client:
  2. Include the 'Personal Pronouns' field.
  3. Include the 'Preferred Appointment Site' field.
  4. Include the "Time Zone for Appointment Reminders" field.
  5. Ensure that Call Intake record returns 'Client Call Intake web service has been filed successfully' message.
  6. Ensure that 'Call Intake' record/episode filed via web service is present with values filed via the web service, including the 'Personal Pronouns', the 'Preferred Appointment Site" and the "Time Zone For Appointment Reminders".
Scenario 12: 'Admission (Outpatient)' - Verification of form filing
Specific Setup:
  • If custom Form Designer changes are present in 'Admission (Outpatient)' form, please use 'Form Designer' to revert to 'Netsmart Produced Changes'.
  • Using the "Site Registration" form:
  • Create additional sites.
  • Using the "Site Hours of Operation" button to enter in operating days/hours for the sites.
  • Using the "User Definition" form:
  • In the "Appointment Scheduling" section, give the user access to the new sites added.
  • Using the "Staff Members Hours and Exceptions" form:
  • Enter hours for the staff member.
Steps
  1. Open Avatar PM 'Admission (Outpatient)' form.
  2. In 'Select Client' dialog, enter values for search criteria and click 'Search' button.
  3. Select existing client record to enter Admission record or click 'New Client' button to create new client record via Admission record entry.
  4. In 'Admission (Outpatient)' form, enter/select values for 'Preadmit/Admission Date', 'Preadmit/Admission Time', 'Program', 'Type of Admission', 'Admitting Practitioner' and any other required/desired fields.
  5. Navigate to 'Demographics' section of form.
  6. In 'Admission (Outpatient)' form 'Demographics' section, ensure that 'Client's Middle Initial' field is relabeled as 'Client Middle Name', and is updated to allow values/entries up to 50 characters in length.
  7. Verify that 'Communication Preference' contains the following: Email, Regular Mail, Home Phone, Text, Work Phone, Cell Phone, Do Not Contact, and Consumer Portal.
  8. Select any value in 'Communication Preference'.
  9. Select any value in "Preferred Site".
  10. Select any value in "Time Zone for Appointment Reminders".
  11. Click 'Submit' button to file new Admission/episode for existing client/new client creation.
  12. In 'My Clients' Widget (or via 'Admission (Outpatient)'/'Update Client Data' forms), ensure that 'Client Middle Name', 'Communication Preference' and 'Preferred Site' values entered in 'Admission (Outpatient)' form is present.
Scenario 13: 'Pre Admit Discharge' - Verification of form filing
Specific Setup:
  • If custom Form Designer changes are present in 'Pre Admit Discharge' form, 'Client's Middle Initial'/'Client Middle Name' field label change may not be visible on update installation; in this case, any future reverting of form to 'Netsmart Produced Changes' copy (via 'Form Designer') would include this field label change.
  • Client record with existing Pre Admit Discharge record or eligible for new Pre Admit Discharge record entry, where Client Demographic information includes 'Client Middle Name' value (formerly 'Client's Middle Initial').
  • Using the "Site Registration" form:
  • Create additional sites.
  • Using the "Site Hours of Operation" button to enter in operating days/hours for the sites.
  • Using the "User Definition" form:
  • In the "Appointment Scheduling" section, give the user access to the new sites added.
  • Using the "Staff Members Hours and Exceptions" form:
  • Enter hours for the staff member.
Steps
  1. Open Avatar PM 'Pre Admit Discharge' form.
  2. In 'Select Client' dialog, enter values for search criteria and click 'Search' button.
  3. Select existing client episode and click 'OK' button to enter new Pre Admit Discharge record or view/edit existing Pre Admit Discharge record.
  4. In 'Pre Admit Discharge' form, enter/select values for 'Date of Discharge', 'Discharge Time', 'Type of Discharge', 'Discharge Practitioner' and any other required/desired fields.
  5. Navigate to 'Demographics' section of form.
  6. In 'Pre Admit Discharge' form 'Demographics' section, ensure that 'Client's Middle Initial' field is relabeled as 'Client Middle Name', and is updated to display values/entries up to 50 characters in length (from current Client Demographic information).
  7. Select a site in the "Preferred Appointment Site" field.
  8. Select the desired time zone in the "Time Zone for Appointment Reminders".
  9. Click 'Submit' button to file Pre Admit Discharge record.
  10. Open the "Pre Admit Discharge" form.
  11. Bring up the same record and validate all fields display as they were data entered.
Scenario 14: 'Discharge' - Required/Full field validations
Specific Setup:
  • Client must be admitted to an active episode (Client A).
  • Using the "Site Registration" form:
  • Create additional sites.
  • Using the "Site Hours of Operation" button to enter in operating days/hours for the sites.
  • Using the "User Definition" form:
  • In the "Appointment Scheduling" section, give the user access to the new sites added.
  • Using the "Staff Members Hours and Exceptions" form:
  • Enter hours for the staff member.
Steps
  1. Open the "Discharge" form.
  2. Select a client to be discharged.
  3. Complete all required fields.
  4. Click [Submit]
Topics
• Discharge
 

Avatar_PM_2023_Monthly_Release_2023.03.01_Details.csv