Skip to main content

Avatar PM 2022 Monthly Release 2022.01.01 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 10 Summary | Details
View Definition - widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • System Task Scheduler
  • User Definition
  • View Definition
  • Dynamic Form - View Definition - Select Views
  • Task Scheduler Status
Scenario 1: Widget - Task Scheduler Status
Specific Setup:
  • System Task Scheduler:
  • Note the data filed for a minimum of two active tasks and one inactive task.
  • View Definition has been used to add the ‘Task Scheduler Status’ widget to the tester’s homeview.
Steps
  1. Access the ‘Task Scheduler Status’ widget.
  2. Validate that the widget can be undocked, refreshed, and either minimized (Non NX View) or removed (NX View).
  3. Validate that the widget contains the following columns: ‘Application’, ‘Task’. ‘Inactive’, ‘Recur’, ‘Start Date’, ‘End Date’, ‘Last Run Date’, ‘Last Run Time’, and ‘Last Run Status’.
  4. Validate the data in each column for the ‘System Task Scheduler’ data noted in ‘Setup’.
Topics
• Widgets • System Task Scheduler • NX
Update 12 Summary | Details
Quick Billing - 3 Day Billing Rule
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dynamic Form - Plan
  • Guarantors/Payors
  • Service Codes
  • Dynamic Form - Edit Service Fee Definition
  • Admission
  • Client Ledger
  • Discharge
  • Quick Billing
  • Quick Billing Rule Definition
  • Dynamic Form - Pre-Display Confirmation
Scenario 1: 3 Day Billing Rule - Readmission occurs post 3 days from the discharge of first episode - Processing an 837 Institutional with a through date <= 3 days from the discharge date
Specific Setup:
  • Registry Setting:
  • The 'Enable New Quick Billing Format' registry setting is set to 'Y'.
  • Guarantors/Payors:
  • A new guarantor is created, or an existing guarantor is updated. Note the GurantorID and guarantor name.
  • The field 'Does This Guarantor Get Billed Under 3-Day Billing Rule?' is set to "Yes".
  • The field 'Does This Guarantor Get Billed Under PPS Rules?' is set to "Yes".
  • Admission:
  • The client is admitted to an inpatient program or an existing inpatient client is identified. Note the admission date, admission program and client id for further testing.
  • Financial Eligibility:
  • The guarantor identified above is assigned to the client.
  • An existing service code, with a fee definition, is identified to be used for inpatient client.
  • Recurring Client Charge Input:
  • 2-3 Services are rendered to the client in the first episode. Be sure to use service codes that are covered by the benefit plan (insurance charge category).
  • Diagnosis:
  • An admission diagnosis is added for the client.
  • Discharge:
  • The client is discharged after last date of the service. Please note the discharge date.
  • Diagnosis:
  • A Discharge diagnosis is added for the client.
  • Re-Admission - Second episode:
  • A new admission is created for the client after 3 days of when the previous episode was discharged. Please note the date of admission and admission program.
  • Financial Eligibility:
  • The guarantor identified above is assigned to the second episode of the client.
  • Diagnosis:
  • An admission diagnosis is added for the client for the second episode.
  • Recurring Client Charge Input:
  • 2-3 Services are rendered to the client in the first episode. Be sure to use service codes that are covered by the benefit plan (insurance charge category).
  • Discharge:
  • The client is discharged from the second episode on the day after last service in the second episode. Please note the discharge date.
  • Diagnosis:
  • A Discharge diagnosis for the second episode is added for the client.
  • Client Ledger:
  • Verify the charges are correctly distributed to the desired guarantor, and they are in 'Open' status.
  • Quick Billing Rule Definition:
  • A quick Billing Rule definition is created to include service(s), client and guarantor for both the episode.
Steps
  1. Open the ‘Quick Billing’ form.
  2. Set the field ‘Add New Or Edit Existing Quick Billing Batch’ to "Add New".
  3. Set the field ‘First Date Of Service To Include’ to the first date of service.
  4. Set the field ‘Last Date Of Service To Include’ to a date that is within 3 days after last discharge date.
  5. Set the field ‘Billing Rule To Execute’ to rule created in setup section.
  6. Select the 'Create Batch', 'Close Charges', 'Generate Bills', 'Create Claims' options in the ‘Quick Billing Tasks To Execute’ field.
  7. Set the field ‘Date Of Claim’ to desired date.
  8. Submit the form.
  9. Verify the 'Compile Complete' message. The message also displays the quick billing batch number and Interim Billing Batch number.
  10. Click [OK].
  11. Open the 'Client Ledger' form.
  12. Select desired client.
  13. Select "All Episode" from the 'Claim/Episode/All Episode' field.
  14. Select "Simple" from the 'Ledger Type' field.
  15. Select desired date in the 'From Date' and 'To Date' fields to include the service date range for the client.
  16. Click [Process].
  17. Verify the services are claimed and the claim number is generated.
Scenario 2: 3 Day Billing Rule - Readmission occurs within 3 days from the discharge of first episode - Processing an 837 Institutional with a through date <= 3 days from the discharge date
Specific Setup:
  • Registry Setting:
  • The 'Enable New Quick Billing Format' registry setting is set to 'Y'.
  • Guarantors/Payors:
  • A new guarantor is created, or an existing guarantor is updated. Note the GurantorID and guarantor name.
  • The field 'Does This Guarantor Get Billed Under 3-Day Billing Rule?' is set to "Yes".
  • The field 'Does This Guarantor Get Billed Under PPS Rules?' is set to "Yes".
  • Admission:
  • The client is admitted to an inpatient program or an existing inpatient client is identified. Note the admission date, admission program and client id for further testing.
  • Financial Eligibility:
  • The guarantor identified above is assigned to the client.
  • An existing service code, with a fee definition, is identified to be used for inpatient client.
  • Recurring Client Charge Input:
  • 2-3 Services are rendered to the client in the first episode. Be sure to use service codes that are covered by the benefit plan (insurance charge category).
  • Diagnosis:
  • An admission diagnosis is added for the client.
  • Discharge:
  • The client is discharged after last date of the service. Please note the discharge date.
  • Diagnosis:
  • A Discharge diagnosis is added for the client.
  • Re-Admission - Second episode:
  • A new admission is created for the client within 3 days of when the previous episode was discharged. Please note the date of admission and admission program.
  • Financial Eligibility:
  • The guarantor identified above is assigned to the second episode of the client.
  • Diagnosis:
  • An admission diagnosis is added for the client for the second episode.
  • Recurring Client Charge Input:
  • 2-3 Services are rendered to the client in the first episode. Be sure to use service codes that are covered by the benefit plan (insurance charge category).
  • Discharge:
  • The client is discharged from the second episode on the day after last service in the second episode. Please note the discharge date.
  • Diagnosis:
  • A Discharge diagnosis for the second episode is added for the client.
  • Client Ledger:
  • Verify the charges are correctly distributed to the desired guarantor, and they are in 'Open' status.
  • Quick Billing Rule Definition:
  • A quick Billing Rule definition is created to include service(s), client and guarantor for both the episode.
Steps
  1. Open the ‘Quick Billing’ form.
  2. Set the field ‘Add New Or Edit Existing Quick Billing Batch’ to "Add New".
  3. Set the field ‘First Date Of Service To Include’ to the first date of service.
  4. Set the field ‘Last Date Of Service To Include’ to a date that is within 3 days after last discharge date.
  5. Set the field ‘Billing Rule To Execute’ to rule created in setup section.
  6. Select the 'Create Batch', 'Close Charges', 'Generate Bills', 'Create Claims' options in the ‘Quick Billing Tasks To Execute’ field.
  7. Set the field ‘Date Of Claim’ to desired date.
  8. Submit the form.
  9. Verify the 'Compile Complete' message. The message also displays the quick billing batch number and Interim Billing Batch number.
  10. Click [OK].
  11. Open the 'Client Ledger' form.
  12. Select desired client.
  13. Select "All Episode" from the 'Claim/Episode/All Episode' field.
  14. Select "Simple" from the 'Ledger Type' field.
  15. Select desired date in the 'From Date' and 'To Date' fields to include the service date range for the client.
  16. Click [Process].
  17. Verify the services are not claimed. The first episode receives the three day billing error and does not claim. The second episode receives the missing diagnosis error and will not get picked up in the batch.
Scenario 3: 3 Day Billing Rule - Single client episode - Processing 837 Institutional with a through date greater than 3 days after discharge date
Specific Setup:
  • Guarantors/Payors:
  • A guarantor is created or edited with the field 'Does This Guarantor Get Billed Under 3-Day Billing Rule?' set to "Yes".
  • Admission:
  • The client is admitted to the inpatient program or an existing inpatient client is identified.
  • Diagnosis:
  • An admission diagnosis record is created for the client.
  • Financial Eligibility:
  • The guarantor identified above is assigned to the client.
  • Client Charge Input:
  • 5 Services are rendered to the client in the first episode. Be sure to use service codes that are covered by the benefit plan (insurance charge category).
  • Discharge:
  • The client is discharged after 5 days from the first episode. Please note the discharge date.
  • Client Ledger:
  • Verify the charges are correctly distributed to the desired guarantor, and they are in 'Open' status.
  • Quick Billing Rule Definition:
  • The quick Billing Rules are created to include service(s) distributed to the client.
Steps
  1. Open the ‘Quick Billing’ form.
  2. Set the field ‘Add New Or Edit Existing Quick Billing Batch’ to "Add New".
  3. Set the field ‘First Date Of Service To Include’ to first date of the service.
  4. Set the field ‘Last Date Of Service To Include’ to the date that is greater than 3 days after discharge date.
  5. Set the field ‘Billing Rule To Execute’ to desired rule created in setup section.
  6. Set the field ‘Quick Billing Tasks To Execute’ to "Create Batch, Close Charges, Generate Bills".
  7. Set the field ‘Date Of Claim’ to desired date.
  8. Submit the form.
  9. Verify the 'Compile Complete' message. The message also displays the quick billing batch number and Interim Billing Batch number.
  10. Click [OK].
  11. Open the 'Client Ledger' form.
  12. Select desired client.
  13. Select "All Episode" from the 'Claim/Episode/All Episode' field.
  14. Select "Simple" from the 'Ledger Type' field.
  15. Select desired date in the 'From Date' and 'To Date' fields to include the service date range for the client.
  16. Click [Process].
  17. Verify the services are claimed and the claim number is generated.
Scenario 4: 3 Day Billing Rule - Single client episode - Processing 837 Institutional with a through date within 3 days after discharge date
Specific Setup:
  • Guarantors/Payors:
  • A guarantor is created or edited with the field 'Does This Guarantor Get Billed Under 3-Day Billing Rule?' set to "Yes".
  • Admission:
  • The client is admitted to the inpatient program or an existing inpatient client is identified.
  • Diagnosis:
  • An admission diagnosis record is created for the client.
  • Financial Eligibility:
  • The guarantor identified above is assigned to the client.
  • Client Charge Input:
  • 5 Services are rendered to the client in the first episode. Be sure to use service codes that are covered by the benefit plan (insurance charge category).
  • Discharge:
  • The client is discharged after 5 days from the first episode. Please note the discharge date.
  • Client Ledger:
  • Verify the charges are correctly distributed to the desired guarantor, and they are in 'Open' status.
  • Quick Billing Rule Definition:
  • The quick Billing Rules are created to include service(s) distributed to the client.
Steps
  1. Open the ‘Quick Billing’ form.
  2. Set the field ‘Add New Or Edit Existing Quick Billing Batch’ to "Add New".
  3. Set the field ‘First Date Of Service To Include’ to first date of the service.
  4. Set the ‘Last Date Of Service To Include’ to the date that is less than or equal to 3 days after discharge date.
  5. Set the field ‘Billing Rule To Execute’ to desired rule created in setup section.
  6. Set the field ‘Quick Billing Tasks To Execute’ to "Create Batch, Close Charges, Generate Bills".
  7. Set the field ‘Date Of Claim’ to desired date.
  8. Submit the form.
  9. Verify the 'Compile Complete Errors Found' message. The message also displays the quick billing batch number and Interim Billing Batch number.
  10. Click [OK].
  11. Select 'Edit Existing' in the ‘Add New Or Edit Existing Quick Billing Batch’ field.
  12. Select desired file from the 'File' dropdown list.
  13. Click [Print 837 Report].
  14. Click the 'Required Data Missing: Subscriber and/or Patient Name Data' link.
  15. Verify the 'Episode cannot be billed due to 3 day billing rule' error message is displayed for the desired episode.
  16. Close the report.
  17. Close the form.
Scenario 5: 3 Day Billing Rule - Running an 837 Institutional bill - Readmission occurs within 3 days after discharge - there is at least a 60 day service period between first and last episodes
Specific Setup:
  • Registry Setting:
  • The 'Enable New Quick Billing Format' registry setting is set to 'Y'.
  • Guarantors/Payors:
  • A new guarantor is created or an existing guarantor is updated. Note the GurantorID and guarantor name.
  • Make sure the field 'Does This Guarantor Get Billed Under 3-Day Billing Rule?' is set to "Yes".
  • Make sure the 'Does This Guarantor Get Billed Under PPS Rules?' is set to "Yes".
  • Admission:
  • The client is admitted to the inpatient program or an existing inpatient client is identified. Note the admission date, admission program and client id for further testing.
  • Financial Eligibility:
  • The guarantor identified above is assigned to the client.
  • An existing service code is identified to be used for inpatient client and make sure to have fee definition for the service.
  • Recurring Client Charge Input:
  • 2-3 Services are rendered to the client in the first episode. Be sure to use service codes that are covered by the benefit plan (insurance charge category).
  • Diagnosis:
  • An admission diagnosis is added for the client.
  • Discharge:
  • The client is discharged after last date of the service. Please note the discharge date.
  • Diagnosis:
  • A Discharge diagnosis is added for the client.
  • Re-Admission - Second episode:
  • A new admission is created for the client within 3 days of when the last episode was discharged. Please note the date of admission and admission program.
  • Financial Eligibility:
  • The guarantor identified above is assigned to the second episode of the client.
  • Diagnosis:
  • An admission diagnosis is added for the client for the second episode.
  • Recurring Client Charge Input:
  • Charges are added to the client that exceeds a 60-day period from the first admission date. Be sure to use service codes that are covered by the benefit plan (insurance charge category).
  • Discharge:
  • The client is discharged from the second episode on the next day after last service in the second episode. Please note the discharge date.
  • Diagnosis:
  • A Discharge diagnosis for the second episode is added for the client.
  • Client Ledger:
  • Verify the charges are correctly distributed to the desired guarantor, and they are in 'Open' status.
  • Quick Billing Rule Definition:
  • The quick Billing Rule definition is created to include service(s), client and guarantor for both the episode.
Steps
  1. Open the ‘Quick Billing’ form.
  2. Set the field ‘Add New Or Edit Existing Quick Billing Batch’ to "Add New".
  3. Set the field ‘First Date Of Service To Include’ to first date of the service.
  4. Set the field ‘Last Date Of Service To Include’ to a date that is greater than 3 days after discharge date.
  5. Set the field ‘Billing Rule To Execute’ to desired rule created in setup section.
  6. Set the field ‘Quick Billing Tasks To Execute’ to "Create Batch, Close Charges, Generate Bills".
  7. Set the field ‘Date Of Claim’ to desired date.
  8. Submit the form.
  9. Verify the 'Compile Complete' message contains error found. The message also displays the quick billing batch number and Interim Billing Batch number.
  10. Click [OK].
  11. Validate the 'Form Return' dialog occurs.
  12. Click [Yes].
  13. Select 'Edit Existing' radio button in the 'Add New Or Edit Existing Quick Billing Batch' field.
  14. Select the file that recently compiled from the 'File' drop down.
  15. Click [Print 837 Report].
  16. Click on the 'Required Data Missing: Subscriber and/or Patient Name Data' link.
  17. Verify the error message for the episode that occurs within 3 days from the discharge of the last episode.
  18. Open the 'Client Ledger' form.
  19. Select desired client.
  20. Select "All Episode" from the 'Claim/Episode/All Episode' field.
  21. Select "Simple" from the 'Ledger Type' field.
  22. Select desired date in the 'From Date' and 'To Date' fields to include the service date range for the client.
  23. Click [Process].
  24. Verify the services are 'Unbilled' in status.
Topics
• Quick Billing • NX
Update 21 Summary | Details
Avatar PM 'Claim Follow-Up' Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • File Import
Scenario 1: 'Claim Follow-Up' - Verification of Submission
Specific Setup:
  • Avatar PM Registry Setting 'Claim Follow-Up' must be enabled
  • Client with claim(s)/service(s) eligible for 'Claim Follow-Up' entry
Steps
  1. Open Avatar PM 'Claim Follow-Up' form; select client record for Claim Follow-Up entry.
  2. Select 'Add' in 'Add, Edit Or Delete Claim Follow-Up' field (or select 'Edit' for review/update of existing entry).
  3. Select value in 'Guarantor' field.
  4. Select value in 'Claim' field.
  5. Select value in 'Denial Type' field.
  6. Select value in 'Service(s)', 'Insurance Based Denial Reason' and '835 Denial Reason' if desired.
  7. Select value in 'Assign Claim For Electronic Re-Billing' field (and 'Claim Submission Reason Code' field if applicable).
  8. In Follow-Up Status/Comments form sub-section, select 'Add' in 'Add, Edit or Delete Row' field (or select 'Edit' for view/update of existing Follow-Up Status/Comments entry).
  9. Select value in 'Follow-Up Status' and 'Followed Up' fields.
  10. Enter/select values in 'Denial CRN#', 'Current CRN#', 'Next Follow-Up Date' and 'Completion Date' fields if desired.
  11. Enter value in 'Comments' field.
  12. Click 'Update Row' button to save Follow-Up Status/Comments entry.
  13. Click 'Submit' button to file 'Claim Follow-Up' form/record.
  14. Ensure filing confirmation dialog noting 'Claim Follow-Up has completed. Do you wish to return to form?' is presented; click 'Yes' button to return to 'Claim Follow-Up' form.
  15. Select 'Edit' in 'Add, Edit Or Delete Claim Follow-Up' field for review of existing entry.
  16. Select existing entry in 'Select Claim Follow-Up To Edit Or Delete' field.
  17. Ensure values for all fields are present in 'Claim Follow-Up' form as previously entered/field for selected entry, including rows/entries in the Follow-Up Status/Comments form sub-section.
Topics
• Claim Follow-up • NX
Update 23 Summary | Details
AR Console User Defaults Setup - Programs
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • AR Console User Defaults Setup
  • HomeView.Accounts Receivable Console
Scenario 1: AR Console User Defaults Setup - field validation
Specific Setup:
  • The following registry setting has a value of Y: Avatar PM->Billing->Accounts Receivable Management->->->Enable Accounts Receivable Management Functionality.
  • User Definition has been used to give the signed in user access to the form: Avatar PM / Billing / AR Management / AR Console User Defaults Setup.
  • View Definition / NX View Definition has been used to place the widget on the tester's home view.
  • Note the ID of two additional users.
Steps
  1. Open ‘AR Console User Defaults Setup’.
  2. Click ‘New Row’ and add a row for the signed in user, or if the signed in user exists in a row select the row.
  3. Click ‘All’ in the following fields: ‘Financial Class(es)’, ‘Guarantor(s)’, ‘Treatment Setting(s)’ ‘Program(s)’ and ‘Client Last Name Initials to be Worked’.
  4. Add desired value to ‘Aged Over # Days’.
  5. Click ‘New Row’ and add a row for the first additional user from ‘Setup’, or if the user exists in a row select the row.
  6. Make any desired changes.
  7. Note the values of each field.
  8. Click ‘New Row’ and add a row for the second additional user from ‘Setup’, or if the user exists in a row select the row.
  9. Make any desired changes.
  10. Note the values of each field.
  11. Click [Submit].
  12. Open ‘AR Console User Defaults Setup’.
  13. Select the row for the signed in user.
  14. Validate that the following fields have every available item in the checklist selected: ‘Financial Class(es)’, ‘Guarantor(s)’, ‘Treatment Setting(s)’ ‘Program(s)’ and ‘Client Last Name Initials to be Worked’.
  15. Select the row for the first additional user.
  16. Validate that the values that were submitted were retained.
  17. Select the row for the second additional user.
  18. Validate that the values that were submitted were retained.
  19. Click [Discard].
Topics
• Accounts Receivable Management • NX
Update 27 Summary | Details
Quick Action - Update Client Data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • View Definition
  • Dynamic Form - View Definition - Select Views
  • NX View Definition
  • Dynamic Form - NX View Definition
  • MPI Search
  • Admission
  • Quick Actions Page
  • Update Client Data
Scenario 1: Quick Action - Update Client Data - 9 digit zip code
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Enter an address with a 9-digit zip code.
  6. Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
  7. Click "Save".
  8. Click "Add" on the "Update Client Data" Quick Action.
  9. Validate the "Zip Code", "City" and "State" fields display appropriately.
  10. Open the "Update Client Data" form.
  11. Validate the same fields all display in uppercase letters.
Scenario 2: Quick Action - Update Client Data - 5 digit zip code
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Enter an address with a 5-digit zip code.
  6. Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
  7. Click "Save".
  8. Click "Add" on the "Update Client Data" Quick Action.
  9. Validate the "Zip Code", "City" and "State" fields display appropriately.
  10. Open the "Update Client Data" form.
  11. Validate the same fields all display in uppercase letters.
Scenario 3: Quick Action - Update Client Data - 9 digit zip code
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Enter an address with a 9-digit zip code.
  6. Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
  7. Click "Save".
  8. Click "Add" on the "Update Client Data" Quick Action.
  9. Validate the "Zip Code", "City" and "State" fields display appropriately.
  10. Open the "Update Client Data" form.
  11. Validate the same fields all display in uppercase letters.
Scenario 4: Quick Action - Update Client Data - 5 digit zip code
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Enter an address with a 5-digit zip code.
  6. Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
  7. Click "Save".
  8. Click "Add" on the "Update Client Data" Quick Action.
  9. Validate the "Zip Code", "City" and "State" fields display appropriately.
  10. Open the "Update Client Data" form.
  11. Validate the same fields all display in uppercase letters.
Quick Action - Update Client Data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • View Definition
  • Dynamic Form - View Definition - Select Views
  • NX View Definition
  • Dynamic Form - NX View Definition
  • MPI Search
  • Admission
  • Quick Actions Page
  • Update Client Data
  • Dynamic Form - Site Specific Section Modeling (CWS)
  • Site Specific Section Modeling (PM)
Scenario 1: Quick Action - Update Client Data - 9 digit zip code
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Enter an address with a 9-digit zip code.
  6. Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
  7. Click "Save".
  8. Click "Add" on the "Update Client Data" Quick Action.
  9. Validate the "Zip Code", "City" and "State" fields display appropriately.
  10. Open the "Update Client Data" form.
  11. Validate the same fields all display in uppercase letters.
Scenario 2: Quick Action - Update Client Data - Convert Client Address to All Uppercase enabled
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
  • Enable registry setting "Convert Client Address To All Uppercase".
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Enter "Address - Street", "Apartment or Unit", and "City" in all lower case letters.
  6. Validate that once you tab out of the field, it's converted to all uppercase letters.
  7. Click "Save".
  8. Click "Add" on the "Update Client Data" Quick Action.
  9. Validate the data that displays in "Address - Street", "Apartment or Unit", and "City" are all uppercase letters.
  10. Open the "Update Client Data" form.
  11. Validate the same fields all display in uppercase letters.
Scenario 3: Quick Action - Update Client Data - Validate name change
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Change the client's first and last name.
  6. Fill in all other fields.
  7. Click "Save".
  8. Open the "Update Client Data" form.
  9. Validate the first and last name are changed.
  10. Using SQL, validate the name change is reflected in the columns, patient_name, patient_name_first, patient_name_last in SYSTEM.patient_current_demographics SQL.
Scenario 4: Quick Action - Update Client Data - 5 digit zip code
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Enter an address with a 5-digit zip code.
  6. Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
  7. Click "Save".
  8. Click "Add" on the "Update Client Data" Quick Action.
  9. Validate the "Zip Code", "City" and "State" fields display appropriately.
  10. Open the "Update Client Data" form.
  11. Validate the same fields all display in uppercase letters.
Scenario 5: Quick Action - Update Client Data - Update Financial Eligibility Data enabled
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Select a client who has existing financial eligibility data.
  • Enable the registry setting "Update Financial Eligibility Data".
Steps
  1. Navigate to the "Quick Action" widget.
  2. Click "Add" on the "Update Client Data" item.
  3. Enter a new name and address for the client with existing financial eligibility data.
  4. Enter the following SQL statement to view the listed fields in SYSTEM.billing_guar_subs_data: SELECT subs_name,subs_name_first,subs_name_last,subs_address_street1,subs_address_street2,subs_address_city,subs_address_state,subs_addess_zip FROM SYSTEM.billing_guar_subs_data to validate that these columns were changed when the Quick Action was filed.
Scenario 6: Quick Action - Update Client Data - Update Financial Eligibility Data disabled
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Select a client who has existing financial eligibility data.
  • Disable the registry setting "Update Financial Eligibility Data".
Steps
  1. Navigate to the "Quick Action" widget.
  2. Click "Add" on the "Update Client Data" item.
  3. Enter a new name and address for the client with existing financial eligibility data.
  4. Enter the following SQL statement to view the listed fields in SYSTEM.billing_guar_subs_data: SELECT subs_name,subs_name_first,subs_name_last,subs_address_street1,subs_address_street2,subs_address_city,subs_address_state,subs_addess_zip FROM SYSTEM.billing_guar_subs_data to validate that these columns were not changed when the Quick Action was filed.
Scenario 7: Quick Action - Update Client Data - 9 digit zip code
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Enter an address with a 9-digit zip code.
  6. Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
  7. Click "Save".
  8. Click "Add" on the "Update Client Data" Quick Action.
  9. Validate the "Zip Code", "City" and "State" fields display appropriately.
  10. Open the "Update Client Data" form.
  11. Validate the same fields all display in uppercase letters.
Scenario 8: Quick Action - Update Client Data - Convert Client Address to All Uppercase enabled
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
  • Enable registry setting "Convert Client Address To All Uppercase".
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Enter "Address - Street", "Apartment or Unit", and "City" in all lower case letters.
  6. Validate that once you tab out of the field, it's converted to all uppercase letters.
  7. Click "Save".
  8. Click "Add" on the "Update Client Data" Quick Action.
  9. Validate the data that displays in "Address - Street", "Apartment or Unit", and "City" are all uppercase letters.
  10. Open the "Update Client Data" form.
  11. Validate the same fields all display in uppercase letters.
Scenario 9: Quick Action - Update Client Data - 5 digit zip code
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Enter an address with a 5-digit zip code.
  6. Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
  7. Click "Save".
  8. Click "Add" on the "Update Client Data" Quick Action.
  9. Validate the "Zip Code", "City" and "State" fields display appropriately.
  10. Open the "Update Client Data" form.
  11. Validate the same fields all display in uppercase letters.
Scenario 10: Quick Action - Update Client Data - Update Financial Eligibility Data enabled
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Select a client who has existing financial eligibility data.
  • Enable the registry setting "Update Financial Eligibility Data".
Steps
  1. Navigate to the "Quick Action" widget.
  2. Click "Add" on the "Update Client Data" item.
  3. Enter a new name and address for the client with existing financial eligibility data.
  4. Enter the following SQL statement to view the listed fields in SYSTEM.billing_guar_subs_data: SELECT subs_name,subs_name_first,subs_name_last,subs_address_street1,subs_address_street2,subs_address_city,subs_address_state,subs_addess_zip FROM SYSTEM.billing_guar_subs_data to validate that these columns were changed when the Quick Action was filed.
Scenario 11: Quick Action - Update Client Data - Update Financial Eligibility Data disabled
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Select a client who has existing financial eligibility data.
  • Disable the registry setting "Update Financial Eligibility Data".
Steps
  1. Navigate to the "Quick Action" widget.
  2. Click "Add" on the "Update Client Data" item.
  3. Enter a new name and address for the client with existing financial eligibility data.
  4. Enter the following SQL statement to view the listed fields in SYSTEM.billing_guar_subs_data: SELECT subs_name,subs_name_first,subs_name_last,subs_address_street1,subs_address_street2,subs_address_city,subs_address_state,subs_addess_zip FROM SYSTEM.billing_guar_subs_data to validate that these columns were not changed when the Quick Action was filed.
Quick Action - Emergency Contact Information
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • View Definition
  • Dynamic Form - View Definition - Select Views
  • NX View Definition
  • Dynamic Form - NX View Definition
  • Quick Actions Page
Scenario 1: Quick Action - Emergency Contact Information - Sort Episodes by Admission Date registry setting enabled
Specific Setup:
  • Registry Setting "Sort Episodes By Admission Date" is enabled.
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the "Emergency Contact Information" form to the available "Quick Actions".
Steps
  1. Select a test client.
  2. Navigate to the "Quick Actions" widget.
  3. Select the "Emergency Contact Information Quick Action".
  4. Fill out the form, noting that the Episodes are sorted in admission date order.
Scenario 2: Quick Action - Emergency Contact Information - Sort Episodes by Admission Date disabled
Specific Setup:
  • Registry Setting "Sort Episodes By Admission Date" is disabled.
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the "Emergency Contact Information" form to the available "Quick Actions".
Steps
  1. Select a test client.
  2. Navigate to the "Quick Actions" widget.
  3. Select the "Emergency Contact Information Quick Action".
  4. Fill out the form, noting that the Episodes aren't sorted in admission date order.
Scenario 3: Quick Action - Emergency Contact Information - Sort Episodes by Admission Date registry setting enabled
Specific Setup:
  • Registry Setting "Sort Episodes By Admission Date" is enabled.
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the "Emergency Contact Information" form to the available "Quick Actions".
Steps
  1. Select a test client.
  2. Navigate to the "Quick Actions" widget.
  3. Select the "Emergency Contact Information Quick Action".
  4. Fill out the form, noting that the Episodes are sorted in admission date order.
Scenario 4: Quick Action - Emergency Contact Information - Sort Episodes by Admission Date disabled
Specific Setup:
  • Registry Setting "Sort Episodes By Admission Date" is disabled.
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the "Emergency Contact Information" form to the available "Quick Actions".
Steps
  1. Select a test client.
  2. Navigate to the "Quick Actions" widget.
  3. Select the "Emergency Contact Information Quick Action".
  4. Fill out the form, noting that the Episodes aren't sorted in admission date order.
Topics
• Update Client Data • NX
Update 33 Summary | Details
Delete Last Movement
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Orders This Episode
  • Delete Last Movement
  • Treatment Plan
  • Admission
  • Patient Account Number Maintenance
  • HL7 Connection Monitor
Scenario 1: Validate 'Delete Last Movement' can be completed when a client has an active order and 'Prevent Delete Admission Movement on Clients with Clinical Data' set to "N".
Specific Setup:
  • The 'Avatar PM->System Maintenance->Client Maintenance->->->Prevent Delete Admission Movement on Clients with Clinical Data' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • A client must have an active inpatient episode. (Client A)
  • “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
  1. Select "Client A" and access the Order Entry Console.
  2. Search for and select "GOOD NEIGHBOR PHARMACY NAPROXEN SODIUM 220 MG CAPSULE, LIQUID FILLED ORAL" in the 'New Order' field.
  3. Set the 'Dose' field to "1".
  4. Select "Tablet" in the 'Dose Unit' field.
  5. Select "As Needed" in the 'Freq' field.
  6. Set the 'Duration' field to "10" and click [Days].
  7. Click [Add to Scratchpad] and [Sign].
  8. Validate the 'Order grid' contains an order for "GOOD NEIGHBOR PHARMACY NAPROXEN SODIUM 220 MG ORAL CAPSULE, LIQUID FILLED 1 Tablet, AS NEEDED".
  9. Access the 'Delete Last Movement' form.
  10. Validate a message is displayed stating "Deletion of any movement will remove the client from any bed they may be in. If a client needs to be in a bed, it needs to be entered via Unit/Room/Bed Assignment." and click [OK].
  11. Select "Episode # 1" in the 'Episode Number' field.
  12. Validate a message is displayed stating "There is data submitted within the associated CWS application for this episode number. Do you want to continue?" and click [OK].
  13. Validate the 'Client Information' field contains all information pertaining to "Client A" and their episode.
  14. Click [Submit].
  15. Validate a message is displayed stating "You are about to delete an Admission movement for episode 1. Do you want to continue?" and click [Yes]
  16. Validate the 'Client Name' Header contains "Client A's First Name Last Name (PATID)".
  17. Validate the 'Header Episode' does not contain a value.
Scenario 2: Validate Delete Last Movement does not undo an Admission when a client has information filed in 'Treatment Plan' and 'Prevent Delete Admission Movement on Clients with Clinical Data'="Y"
Specific Setup:
  • The 'Avatar PM->System Maintenance->Client Maintenance->->->Prevent Delete Admission Movement on Clients with Clinical Data' registry setting to "Y".
  • Please log out of the application and log back in after completing the above configuration.
  • A client must have an active Inpatient episode. (Client A).
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Select the current date in the 'Plan Date' field.
  3. Set the 'Plan Name' field to any value.
  4. Select any value in the 'Plan Type' field.
  5. Select "Final" in the 'Treatment Plan Status' field and click [Submit].
  6. Validate the 'Document Routing' dialog is displayed and click [Accept].
  7. Set the 'Password' field to the password for the user who is logged into the application and click [Verify].
  8. Access the 'Delete Last Movement' form.
  9. Validate a message is displayed "Deletion of any movement will remove the client from any bed they may be in. If a client needs to be in a bed, it needs to be entered via Unit/Room/Bed Assignment." and click [OK].
  10. Select "Episode # 1" in the 'Episode Number' field.
  11. Validate a message is displayed stating "There is data submitted within the associated CWS application for this episode number. Cannot continue." and click [OK].

;

Scenario 3: Validate Delete Last Movement via HL7 Inbound ADT message does not undo an Admission when a client has 'Treatment Plan' info and 'Prevent Delete Admission Movement on Clients with Clinical Data'="Y"
Specific Setup:
  • An Inbound ADT connection must exist.
  • The 'Avatar PM->System Maintenance->Client Maintenance->->->Prevent Delete Admission Movement on Clients with Clinical Data' registry setting must be set to "Y".
  • Please log out of the application and log back in after completing the above configuration.
Steps
  1. Access the 'Admission' form.
  2. Set the 'Last Name' field to any value and press Tab.
  3. Set the 'First Name' field to any value and press Tab.
  4. Select any value in the 'Sex' field.
  5. Set the 'Social Security Number' field to any value and press Tab.
  6. Set the 'Date of Birth' field to any value and press Tab.
  7. Click [Search] and [New Client].
  8. Validate a message is displayed stating "Auto Assign Next ID Number?" and click [Yes].
  9. Validate the 'Client Name' field contains the value entered in the 'Last Name' and 'First Name' fields in the format of Last Name,First Name.
  10. Fill out all required fields, ensuring to select an Inpatient program in the 'Program' field, and that the 'Admitting Practitioner' field contains the staff member associated with the user who is logged into the application.
  11. Select the 'Demographics' section and fill out the 'Address - Street', 'Zipcode', and 'Home Phone' fields.
  12. Select the 'Inpatient/Partial/Day Treatment' section and select a value in the 'Unit', 'Room', 'Bed', and 'Room And Board Billing Code' fields and click [Submit].
  13. Validate that the client created above is selected and access the 'Treatment Plan' form.
  14. Select the current date in the 'Plan Date' field.
  15. Set the 'Plan Name' field to any value.
  16. Select any value in the 'Plan Type' field.
  17. Select "Draft" in the 'Treatment Plan Status' field and click [Submit].
  18. Access the 'Patient Account Number Maintenance' form
  19. Search for and select "Client A" in the 'Client ID' field.
  20. Select "Episode # 1" in the 'Episode' field.
  21. Select "Add" in the 'Action' field.
  22. Set the 'Effective Date' field to the current date.
  23. Validate a message is displayed stating "By default the effective date for the first patient account number filed should not be later than the admission date. This is to ensure that for any services rendered there is an associated patient account number on file." and click [OK].
  24. Set the 'Patient Account Number' field to any unique value. (IA0000022559) and click [Submit].
  25. Validate a message is displayed stating "Patient Account Number Maintenance has completed. Do you wish to return to form?" and click [No].
  26. The 'External Client ID Maintenance' form must contain a unique id for the client created above. This is a Netsmart Staff only form.
  27. An Inbound ADT-11 (Cancel Admission) message comes into the application via Avatar HL7 for the client and episode above.
  28. Access the 'HL7 Connection Monitor' form and select the "ADT-INBOUND" connection.
  29. Click [Show Transaction Log].
  30. Validate there is a message with an 'Event Type' of "A11" for the client created above with a message of "There is data submitted within the associated CWS application for this episode number. Cannot continue."
  31. Close the report and the form.
Scenario 4: Validate Delete Last Movement does not undo an Admission when a client has orders and 'Prevent Delete Admission Movement on Clients with Clinical Data'="Y"
Specific Setup:
  • The 'Avatar PM->System Maintenance->Client Maintenance->->->Prevent Delete Admission Movement on Clients with Clinical Data' registry setting to "Y".
  • Please log out of the application and log back in after completing the above configuration.
Steps
  1. Access the 'Admission' form.
  2. Set the 'Last Name' field to any value and press Tab.
  3. Set the 'First Name' field to any value and press Tab.
  4. Select any value in the 'Sex' field.
  5. Set the 'Social Security Number' field to any value and press Tab.
  6. Set the 'Date of Birth' field to any value and press Tab.
  7. Click [Search] and [New Client].
  8. Validate a message is displayed stating "Auto Assign Next ID Number?" and click [Yes].
  9. Validate the 'Client Name' field contains the value entered in the 'Last Name' and 'First Name' fields in the format of Last Name,First Name.
  10. Fill out all required fields, ensuring to select an Inpatient program in the 'Program' field, and that the 'Admitting Practitioner' field contains the staff member associated with the user who is logged into the application.
  11. Select the 'Demographics' section and fill out the 'Address - Street', 'Zipcode', and 'Home Phone' fields.
  12. Select the 'Inpatient/Partial/Day Treatment' section and select a value in the 'Unit', 'Room', 'Bed', and 'Room And Board Billing Code' fields and click [Submit].
  13. Access the Order Entry Console.
  14. Search for and select "ADVIL COLD & SINUS 200 MG-30 MG TABLET ORAL" in the 'New Order' field.
  15. Set the 'Dose' field to "1".
  16. Validate the 'Dose Unit' field contains "Tablet".
  17. Select "As Needed" in the 'Freq' field.
  18. Set the 'Duration' field to "28" and click [Days].
  19. Validate the 'Days Supply' field contains "28".
  20. Validate the 'Dispense Qty' field contains "28"
  21. Select "Tablet" in the 'Dispense Qty Unit' field.
  22. Click [Add to Scratchpad] and [Final Review].
  23. Validate the 'Interactions' dialog is displayed
  24. Override all interactions and click [Save Override and Exit].
  25. Validate the 'Final Review' dialog is displayed.
  26. Select "None" in the 'Output' field and click [Sign].
  27. Validate the 'Order grid' contains an order for "ADVIL COLD & SINUS 200 MG-30 MG ORAL TABLET1 Tablet, AS NEEDED".
  28. Access the 'Delete Last Movement' form.
  29. Validate a message is displayed stating "Deletion of any movement will remove the client from any bed they may be in. If a client needs to be in a bed, it needs to be entered via Unit/Room/Bed Assignment." and click [OK].
  30. Select "Episode 1" in the 'Episode Number' field.
  31. Validate a message is displayed stating "There is data submitted within the associated CWS application for this episode number. Cannot continue." and click [OK].
  32. Close the form.
Scenario 5: Validate Delete Last Movement via an HL7 Inbound ADT message does not undo an Admission when a client has orders and 'Prevent Delete Admission Movement on Clients with Clinical Data'="Y"
Specific Setup:
  • The 'Avatar PM->System Maintenance->Client Maintenance->->->Prevent Delete Admission Movement on Clients with Clinical Data' registry setting to "Y".
  • Please log out of the application and log back in after completing the above configuration.
  • A client must have an active inpatient episode. (Client A)
  • The 'External Client ID Maintenance' form must contain a unique value for "Client A". This is a Netsmart Staff only form.
Steps
  1. Access the 'Patient Account Number Maintenance' form
  2. Search for and select "Client A" in the 'Client ID' field.
  3. Select "Episode # 1" in the 'Episode' field.
  4. Select "Add" in the 'Action' field.
  5. Set the 'Effective Date' field to the current date.
  6. Validate a message is displayed stating "By default the effective date for the first patient account number filed should not be later than the admission date. This is to ensure that for any services rendered there is an associated patient account number on file." and click [OK].
  7. Set the 'Patient Account Number' field to any unique value. (IA0000022559) and click [Submit].
  8. Validate a message is displayed stating "Patient Account Number Maintenance has completed. Do you wish to return to form?" and click [No].
  9. Select "Client A" and access the Order Entry Console.
  10. Search for and select "ADVIL COLD & SINUS 200 MG-30 MG TABLET ORAL" in the 'New Order' field.
  11. Set the 'Dose' field to "1".
  12. Validate the 'Dose Unit' field contains "Tablet".
  13. Select "As Needed" in the 'Freq' field.
  14. Set the 'Duration' field to "28" and click [Days].
  15. Validate the 'Days Supply' field contains "28".
  16. Validate the 'Dispense Qty' field contains "28"
  17. Select "Tablet" in the 'Dispense Qty Unit' field.
  18. Click [Add to Scratchpad] and [Final Review].
  19. Validate the 'Interactions' dialog is displayed
  20. Override all interactions and click [Save Override and Exit].
  21. Validate the 'Final Review' dialog is displayed.
  22. Select "None" in the 'Output' field and click [Sign].
  23. Validate the 'Order grid' contains an order for "ADVIL COLD & SINUS 200 MG-30 MG ORAL TABLET1 Tablet, AS NEEDED".
  24. An Inbound ADT "A11" (Cancel Admission) message comes into the application via Avatar HL7.
  25. Access the 'HL7 Connection Monitor' form.
  26. Select the Inbound ADT connection in the 'Select Row' field.
  27. Set the 'Search Pattern 1" field to "Client A's Last Name".
  28. Click [Show Transaction Log].
  29. Validate the 'HL7 Inbound Transaction Report' is displayed.
  30. Validate there is a row for an 'Event Type' of "A11" with a 'Message Received' of "There is data submitted within the associated CWS application for this episode number. Cannot continue."
  31. Close the report and the form.
Scenario 6: Validate 'Delete Last Movement' can be completed when a client has an active Treatment Plan and 'Prevent Delete Admission Movement on Clients with Clinical Data' set to "N".
Specific Setup:
  • The 'Avatar PM->System Maintenance->Client Maintenance->->->Prevent Delete Admission Movement on Clients with Clinical Data' registry setting must be set to "N".
  • Please log out of the application and log back in after completing the above configuration.
  • A client must have an active inpatient episode. (Client A)
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Set the 'Plan Date' field to the current date.
  3. Set the 'Plan Name' field to any value.
  4. Select any value in the 'Plan Type' field.
  5. Select "Final" in the 'Treatment Plan Status' field and click [Submit].
  6. Validate the 'Document Routing' dialog is displayed and click [Accept].
  7. Set the 'Password' field to the password of the user that is logged into the application and click [Verify].
  8. Validate that "Client A" is selected and access the 'Delete Last Movement' form.
  9. Validate a message is displayed stating "Deletion of any movement will remove the client from any bed they may be in. If a client needs to be in a bed, it needs to be entered via Unit/Room/Bed Assignment." and click [OK].
  10. Select "Episode # 1" in the 'Episode Number' field.
  11. Validate a message is displayed stating "There is data submitted within the associated CWS application for this episode number.Do you want to continue?" and click [OK].
  12. Validate the 'Client Information' field contains information pertaining to "Client A" and "Episode #1".
  13. Click [Submit].
  14. Validate a message is displayed stating "You are about to delete an Admission movement for episode 1. Do you want to continue?" and click [Yes]
  15. Validate the 'Client Name' Header contains "Client A's First Name Last Name (PATID)".
  16. Validate the 'Header Episode' does not contain a value.
Topics
• Delete Last Movement • NX • Treatment Plan • myAvatar/myAvatar NX • HL7 • Admission • Order Entry Console
Update 39 Summary | Details
Avatar NX - 'Emergency Contact' quick action
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Quick Actions Page
  • Update Client Data
Scenario 1: Validate accessing various 'Quick Actions' from the 'Client Dashboard'
Specific Setup:
  • A client must be admitted to an active episode (Client A).
  • "Client A" must not have data saved in the 'Smoking Assessment' quick action.
  • 'Update Client Data', 'Smoking Assessment', 'Problem List', 'Emergency Contact', and 'Alerts' Quick Actions must be assigned to the user in the 'NX View Definition' form.
  • This scenario must be tested in an Avatar NX system.
Steps
  1. Select "Client A" and launch the 'Client Dashboard'.
  2. Validate there is no grey box behind the client's name.
  3. Navigate to the 'Quick Actions' widget.
  4. Click [Update Client Data - Add].
  5. Click outside of the 'Update Client Data' dialog.
  6. Validate the dialog is fixed and centered in the screen.
  7. Enter "LASTNAME, FIRSTNAME" in the 'Name' field and press the "Tab" key.
  8. Validate the space is automatically removed after the comma.
  9. Click the 'State' field and validate the states are listed alphabetically.
  10. Populate the required and desired fields.
  11. Click [Save].
  12. Click [Emergency Contact - Add].
  13. Click outside of the 'Emergency Contact' dialog.
  14. Validate the dialog is fixed and centered in the screen.
  15. Enter "LASTNAME, FIRSTNAME" in the 'Emergency Contact Name' field and press the "Tab" key.
  16. Validate the space is automatically removed after the comma.
  17. Fill out any required any desired fields.
  18. Click [Save].
  19. Click [Smoking Assessment - Add].
  20. Click outside of the 'Smoking Assessment' dialog.
  21. Validate the dialog is fixed and centered in the screen.
  22. Populate the required fields.
  23. Click [Save].
  24. Click [Problems List - Add].
  25. Click outside of the 'Problems List' dialog.
  26. Validate the dialog is fixed and centered in the screen.
  27. Click [Cancel].
  28. Click [Alerts - Add].
  29. Select "Warning (Custom)" in the 'Type of Alert' field.
  30. Select "All Episodes" in the 'Episode(s)' field.
  31. Enter any value with a special character in the 'Custom Message' field.
  32. Validate an error message and click [OK].
  33. Enter any value in the 'Custom Message' field.
  34. Select "No" in the 'Disabled' field.
  35. Select "Active for Date Range" in the 'Active or Active for Date Range' field.
  36. Validate the 'Start Date' and 'End Date' field populate with the current date.
  37. Click [End Date Y].
  38. Validate an 'Error' dialog stating: "Please choose an end date on or after the start date." and click [OK].
  39. Validate the 'End Date' field contains the current date.
  40. Enter any future value in the 'End Date' field.
  41. Select any form in the 'Applicable Forms' field (Form A).
  42. Validate the 'Applicable Forms' are listed alphabetically.
  43. Click [Save].
  44. Close the 'Client Dashboard'.
  45. Access 'Form A'.
  46. Validate the 'Client Alert' message is displayed and contains the message entered in the previous steps.
  47. Click [OK].
  48. Close the form.
Avatar NX - 'Alerts' quick action
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Alerts (PM)
  • Quick Actions Page
  • Update Client Data
Scenario 1: 'Alert Types' - validate data populates in 'Client Alerts' and the 'Alerts' quick action
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • The 'Alerts' quick action must be set up on a user's view.
  • User must select a form to access (Form A).
Steps
  1. Access the 'Alert Types' form.
  2. Enter any value in the 'Alert Type ID' field.
  3. Enter any value in the 'Description' field.
  4. Enter any value in the 'Message' field.
  5. Select "Error" in the 'Type of Alert' field.
  6. Select "Active for Date Range" in the 'Active or Active for Date Range' field.
  7. Select "No" in the 'Community Alert' field.
  8. Select "Form A" in the 'Applicable Forms' field.
  9. Click [Submit].
  10. Access the 'Client Alerts' form.
  11. Select "Client A".
  12. Select the value entered in the previous steps in the 'Type of Alert' field.
  13. Validate the form populates.
  14. Validate the 'Start Date' and 'End Date' fields contain the current date.
  15. Click [End Date Y].
  16. Validate the 'Error' dialog stating: "Please choose an end date on or after the start date."
  17. Click [OK].
  18. Validate the 'End Date' field contains the current date.
  19. Click [Discard] and [Yes].
  20. Select "Client A" and navigate to the 'Alerts' quick action.
  21. Click [Add].
  22. Select the value entered in the previous steps in the 'Type of Alert' field.
  23. Validate the form populates.
  24. Select "All Episodes" in the 'Episode(s)' field.
  25. Validate the 'Start Date' and 'End Date' fields contain the current date.
  26. Click [Save] and [Close].
  27. Access "Form A".
  28. Validate the 'Client Alert' dialog containing the message entered in the previous steps.
  29. Click [OK]
  30. Validate the 'Error' dialog stating: "Canceled!"
  31. Click [OK]
  32. Validate the form closes and the user is returned to the myDay view.
Scenario 2: Validate accessing various 'Quick Actions' from the 'Client Dashboard'
Specific Setup:
  • A client must be admitted to an active episode (Client A).
  • "Client A" must not have data saved in the 'Smoking Assessment' quick action.
  • 'Update Client Data', 'Smoking Assessment', 'Problem List', 'Emergency Contact', and 'Alerts' Quick Actions must be assigned to the user in the 'NX View Definition' form.
  • This scenario must be tested in an Avatar NX system.
Steps
  1. Select "Client A" and launch the 'Client Dashboard'.
  2. Validate there is no grey box behind the client's name.
  3. Navigate to the 'Quick Actions' widget.
  4. Click [Update Client Data - Add].
  5. Click outside of the 'Update Client Data' dialog.
  6. Validate the dialog is fixed and centered in the screen.
  7. Enter "LASTNAME, FIRSTNAME" in the 'Name' field and press the "Tab" key.
  8. Validate the space is automatically removed after the comma.
  9. Click the 'State' field and validate the states are listed alphabetically.
  10. Populate the required and desired fields.
  11. Click [Save].
  12. Click [Emergency Contact - Add].
  13. Click outside of the 'Emergency Contact' dialog.
  14. Validate the dialog is fixed and centered in the screen.
  15. Enter "LASTNAME, FIRSTNAME" in the 'Emergency Contact Name' field and press the "Tab" key.
  16. Validate the space is automatically removed after the comma.
  17. Fill out any required any desired fields.
  18. Click [Save].
  19. Click [Smoking Assessment - Add].
  20. Click outside of the 'Smoking Assessment' dialog.
  21. Validate the dialog is fixed and centered in the screen.
  22. Populate the required fields.
  23. Click [Save].
  24. Click [Problems List - Add].
  25. Click outside of the 'Problems List' dialog.
  26. Validate the dialog is fixed and centered in the screen.
  27. Click [Cancel].
  28. Click [Alerts - Add].
  29. Select "Warning (Custom)" in the 'Type of Alert' field.
  30. Select "All Episodes" in the 'Episode(s)' field.
  31. Enter any value with a special character in the 'Custom Message' field.
  32. Validate an error message and click [OK].
  33. Enter any value in the 'Custom Message' field.
  34. Select "No" in the 'Disabled' field.
  35. Select "Active for Date Range" in the 'Active or Active for Date Range' field.
  36. Validate the 'Start Date' and 'End Date' field populate with the current date.
  37. Click [End Date Y].
  38. Validate an 'Error' dialog stating: "Please choose an end date on or after the start date." and click [OK].
  39. Validate the 'End Date' field contains the current date.
  40. Enter any future value in the 'End Date' field.
  41. Select any form in the 'Applicable Forms' field (Form A).
  42. Validate the 'Applicable Forms' are listed alphabetically.
  43. Click [Save].
  44. Close the 'Client Dashboard'.
  45. Access 'Form A'.
  46. Validate the 'Client Alert' message is displayed and contains the message entered in the previous steps.
  47. Click [OK].
  48. Close the form.
Topics
• Emergency Contact Information • NX • Quick Actions • Client Alerts
Update 51 Summary | Details
Registry Setting - Disable Demographics Section On Discharge Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Discharge
Scenario 1: Registry Setting - Disable Demographics Section On Discharge Form
Steps
  1. Access the 'Registry Settings' form.
  2. Set the 'Limit Registry Settings to the Following Search Criteria' field to "disable demographics" and click [View Registry Settings].
  3. Validate the 'Registry Setting' field is equal to "Avatar PM->Client Information->Client Demographics->->->Disable Demographics Section On Discharge Form".
  4. Validate the 'Registry Setting Value' field is equal to "N" and close the form.
  5. Select any client and access the 'Discharge' form.
  6. Select the 'Demographics' section.
  7. Validate fields in the 'Demographics' section are not disabled and close the form.
  8. Access the 'Registry Settings' form.
  9. Set the 'Limit Registry Settings to the Following Search Criteria' field to "disable demographics" and click [View Registry Settings].
  10. Validate the 'Registry Setting' field is equal to "Avatar PM->Client Information->Client Demographics->->->Disable Demographics Section On Discharge Form".
  11. Set the 'Registry Setting Value' field to "Y" and click [Submit].
  12. Log out of the application and log back in.
  13. Select any client and access the 'Discharge' form.
  14. Select the 'Demographics' section.
  15. Validate all fields are disabled.
Topics
• Registry Settings • NX
Update 54 Summary | Details
Print Bill - UB-04
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Print Bill
  • Client Ledger
Scenario 1: Print Bill - Form = UB-04
Specific Setup:
  • Client:
  • Client is enrolled in an inpatient program, has an active diagnosis record and a financial eligibility record. Note the guarantor.
  • Client has unclaimed, closed services with the fee distributed to the guarantor. Note the episode and dates of service.
Steps
  1. Open ‘Print Bill’.
  2. Enter desired date in ‘Print Charge Thru’.
  3. Select desired value in ‘Create Claims’. If yes is selected, enter a value in ‘Date of Claim’ and verify that the claim number exists in the ‘Client Ledger’ beginning in step # 15.
  4. Select ‘UB-04’ in ‘Print For What Form’.
  5. Select ‘No’ in ‘Print For Interim Batch’.
  6. Select desired value in ‘Guarantor’.
  7. Select ‘Individual’ in ‘Print For An Individual or All Clients’.
  8. Enter the desired ‘Client ID’.
  9. Select desired value in ‘Print All Episodes’. If ‘No’ is selected, select the ‘Episode Number’.
  10. Select desired value in ‘Print Summary By Revenue Code’ If ‘Yes’ is selected, select desired value in ‘Summary By Revenue Code or Revenue Code And Charge’.
  11. Click [Process].
  12. Review the report for accuracy.
  13. Close the report.
  14. Close the form.
  15. Open ’Client Ledger’ for the client.
  16. Select ‘All Episodes’ in ‘Claim/Episode/All Episodes’/
  17. Select ‘Simple’ in ‘Ledger Type’.
  18. Enter desired values in ‘From Date’ and ‘To Date’.
  19. Click [Process].
  20. Review the report to validate that the services contain a value in ‘CLAIM NUMBER.
  21. Close the report.
  22. Close the form.
Topics
• Print Bill • NX
2021 Update 132 Summary | Details
Quick Billing Rule Definition - new fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Definition
  • Guarantors/Payors
  • Client Charge Input
  • Practitioner Enrollment
  • Practitioner Numbers By Guarantor And Program
  • Quick Billing Rule Definition
  • Quick Billing
  • Program Maintenance
  • Client Ledger
Scenario 1: Qucik Billing Rule Definition - 'Include "errors.txt" File' and 'File Location' for "errors.txt".
Specific Setup:
  • Client:
  • Select a client that has missing data that will prevent it from being billed. This example will use a missing ‘Policy Number’ in Financial Eligibility’. Note the guarantor.
  • Create services for the client and validate that the fee distributed to the above guarantor. Note the service code, program, and dates of service.
  • Quick Billing Rue Definition:
  • A quick billing rule definition is defined that will include the guarantor, service code, and program.
  • ‘Send Generated Bill To' = File.
  • Note the ‘File Location’ value.
  • ‘Include “errors.txt” File’ = ‘No’.
Steps
  1. Open ‘Quick Billing’.
  2. Select ‘Add’ in ‘Add New Or Edit Existing Quick Billing Batch’.
  3. Enter desired ‘First Date Of Service To Include’.
  4. Enter desired ‘Last Date Of Service To Include’.
  5. Select desired ‘Billing Rule To Execute’.
  6. Select ‘Create Batch’, ‘Close Charges ’, and ‘Generate Bills’ in ‘Quick Billing Tasks to Execute’.
  7. Enter desired ‘Date Of Claim‘.
  8. Validate that the ‘Compile Complete’ message indicates that errors were found.
  9. Close the form.
  10. Go to the ‘File Location’ and verify that no error file was created.
  11. Open ‘Quick Billing Rule Definition’ and edit the rule from ‘Setup’.
  12. Change the ‘Include “errors.txt” File’ to ‘Yes’.
  13. Submit the form.
  14. Open ‘Quick Billing’.
  15. Select ‘Add’ in ‘Add New Or Edit Existing Quick Billing Batch’.
  16. Enter desired ‘First Date Of Service To Include’.
  17. Enter desired ‘Last Date Of Service To Include’.
  18. Select desired ‘Billing Rule To Execute’.
  19. Select ‘Create Batch’, ‘Close Charges’, and ‘Generate Bills’ in ‘Quick Billing Tasks to Execute’.
  20. Enter desired ‘Date Of Claim‘.
  21. Validate that the ‘Compile Complete’ message indicates that errors were found.
  22. Close the form.
  23. Go to the ‘File Location’ and verify that the error file was created.
  24. Open ‘Quick Billing Rule Definition’ and edit the rule from ‘Setup.
  25. Change the ‘Include “errors.txt” File’ to ‘In Separate Location’.
  26. Enter a value in ‘File Location for "errors.txt" File’ that differs from the ‘File Location’ value’.
  27. Submit the form.
  28. Open ‘Quick Billing’.
  29. Select ‘Add’ in ‘Add New Or Edit Existing Quick Billing Batch’.
  30. Enter desired ‘First Date Of Service To Include’.
  31. Enter desired ‘Last Date Of Service To Include’.
  32. Select desired ‘Billing Rule To Execute’.
  33. Select ‘Create Batch’, ‘Close Charges’, and ‘Generate Bills’ in ‘Quick Billing Tasks to Execute’.
  34. Enter desired ‘Date Of Claim‘.
  35. Validate that the ‘Compile Complete’ message indicates that errors were found.
  36. Close the form.
  37. Go to the ‘File Location for "errors.txt" File’ and verify that the error file was created.
  38. Fix the client data, in this example the missing ‘Policy Number’ in Financial Eligibility’.
  39. Open ‘Quick Billing’.
  40. Select ‘Add’ in ‘Add New Or Edit Existing Quick Billing Batch’.
  41. Enter desired ‘First Date Of Service To Include’.
  42. Enter desired ‘Last Date Of Service To Include’.
  43. Select desired ‘Billing Rule To Execute’.
  44. Select ‘Create Batch’, ‘Close Charges’, ‘Generate Bills’, and 'Create Claims' in ‘Quick Billing Tasks to Execute’.
  45. Enter desired ‘Date Of Claim‘.
  46. Validate that the ‘Compile Complete’ message indicates that no errors were found.
  47. Go to the ‘File Location’ and verify that the billing file was created.
  48. Open 'Client Ledger' for the client and validate that the claim number displays.
Topics
• Quick Billing • NX