Skip to main content

Avatar CWS 2024 Monthly Release 2024.01.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 7 Summary | Details
Allergies and Hypersensitivities - No Known Drug Allergy
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • HL7 Connection Monitor
  • Orders This Episode
Scenario 1: 'Known Medication Allergies' and 'Known Food Allergies' in ADT Outbound messages
Specific Setup:
  • An ADT-Outbound connection must be configured for HL7.
  • Three clients must exist that each have an active episode. (Client A) (Client B) (Client C)
  • “Client A”, "Client B", and "Client C" must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
  1. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  2. Click [Update], validate there are no rows in the grid, and click [Close/cancel].
  3. Select "No" in the 'Known Medication Allergies' field.
  4. Select "No" in the 'Known Food Allergies' field.
  5. Click [Submit].
  6. Access the 'HL7 Connection Monitor' form and select the "ADT Outbound" connection.
  7. Validate that the 'Last Message Processed' contains an 'AL1-3.2' segment = "NKDA - NO KNOWN DRUG ALLERGIES".
  8. Create a report using the ‘cw_client_clinical_info’ table and validate that the row for "Client A" has an "N" for the 'known_med_allergies_code', and for the 'known_allergies_code'.
  9. Access the 'Allergies and Hypersensitivities' form and click [Update].
  10. Add a new row for any medicine (for example, Penciclovir) with a "Confirmed" status and click [Save].
  11. Validate 'Known Medication Allergies' field is disabled and has "Yes" selected.
  12. Exit the form without submitting.
  13. Access the 'HL7 Connection Monitor' form, click [Refresh Monitor], and select and select the "ADT Outbound" connection.
  14. Validate that the 'Last Message Processed' contains an 'AL1-3.2' segment = "PENCICLOVIR".
  15. Refresh the report and validate that the row for "Client A" has a "Y" for the 'known_med_allergies_code' and for the 'known_allergies_code'.
  16. Close the 'HL7 Connection Monitor' form and clear "Client A".
  17. Select "Client B" and access the 'Allergies and Hypersensitivities' form.
  18. Click [Update].
  19. Add a new row for any food allergy (for example, SHELLFISH) with a "Confirmed" status and click [Save].
  20. Validate 'Known Food Allergies' is set to "Yes" and is disabled.
  21. Exit the form without submitting.
  22. Access the 'HL7 Connection Monitor' form and select the "ADT Outbound" connection.
  23. Validate that the 'Last Message Processed' contains 2 'AL1' segments.
  24. The 1st 'AL1-3.2' segment = "SHELLFISH".
  25. The 2nd 'AL1-3.2' segment = "NO KNOWN DRUG ALLERGIES - NKDA".
  26. Refresh the report and validate that the row for "Client B" has a "Y" for the 'known_food_allergies_code' and for the 'known_allergies_code'.
  27. Close the 'HL7 Connection Monitor' form and clear "Client B".
  28. Select "Client C" and access the 'Allergies and Hypersensitivities' form.
  29. Click [Update], validate that there is no row in the grid.
  30. Add a new row for any food allergy (for example, SHELLFISH) with a "Confirmed" status.
  31. Add a new row for any medicine allergy (for example, Penciclovir) with "Confirmed" status and click [Save].
  32. Validate the 'Known Medication Allergies' field is disabled and has "Yes" selected.
  33. Validate the 'Known Food Allergies' field is disabled and has "Yes" selected.
  34. Click [Submit].
  35. Click 'myDay'.
  36. Access the 'HL7 Connection Monitor' form and select the "ADT Outbound" connection.
  37. Validate that the 'Last Message Processed' contains 2 'AL1' segments.
  38. The 1st 'AL1-3.2' segment = "SHELLFISH".
  39. The 2nd 'AL1-3.2' segment = "PENCICLOVIR".
  40. Refresh the report and validate that the row for 'Client C' has a "Y" for the 'known_food_allergies_code', 'known_med_allergies_code', and for the 'known_allergies_code'.
  41. Access the 'Allergies and Hypersensitivities' form click [Update].
  42. Edit the row for the medication allergy and set the 'Status to "Invalid" and click [Save].
  43. Select "No" in the 'Known Medication Allergies' field and click [Submit].
  44. Access the 'HL7 Connection Monitor' form.
  45. Click [Refresh Monitor].
  46. Select the "ADT Outbound" connection.
  47. Validate that the 'Last Message Processed' contains 3 'AL1' segments.
  48. The 1st 'AL1-3.2' segment = "SHELLFISH".
  49. The 2nd 'AL1-3.2' segment = "PENCICLOVIR".
  50. The 3rd 'AL1-3.2' segment = "NO KNOWN DRUG ALLERGIES - NKDA".
  51. Refresh the report and validate that the row for "Client C" has a "Y" for the 'known_food_allergies_code' and 'known_allergies_code', and has an "N" for 'known_med_allergies_code'.
  52. Access the 'Allergies and Hypersensitivities' form click [Update].
  53. Edit the row for the food allergy, set the 'Status' to "Invalid", and click [Save].
  54. Select "No" in the 'Known Food Allergies' field and click [Submit].
  55. Access the 'HL7 Connection Monitor' form.
  56. Click [Refresh Monitors].
  57. Select the "ADT Outbound" connection.
  58. Validate that the 'Last Message Processed' contains 3 'AL1' segments.
  59. The 1st 'AL1-3.2' segment = "SHELLFISH".
  60. The 2nd 'AL1-3.2' segment = "PENCICLOVIR".
  61. The 3rd 'AL1-3.2' segment = "NO KNOWN DRUG ALLERGIES - NKDA".
  62. Refresh the report and validate that the row for "Client C" has an "N" for the 'known_food_allergies_code', the 'known_allergies_code', and the 'known_med_allergies_code'.
Topics
• HL7 • Allergies and Hypersensitivities
2023 Update 13 Summary | Details
POC Results Entry - Observation Value Unit
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • POC Results Entry Configuration
Scenario 1: POC Results Entry Configuration form - Observation Value Unit field is not required as vital sign is selected in the 'Observation Definition' tab
Specific Setup:
  • A Prompt Definition (Prompt Definition 1) must be set up via the Avatar CWS 'Site Specific Section Modeling' form for "Vitals Entry - (CWS14000)" such that:
  • 'Site Specific Field' = "SS Vital Signs Integer" or "SS Vital Signs Free Text".
  • 'Exclude from Data Collection Instrument' = "No".
  • 'Initially enabled' = "Yes".
  • The logged in user must have access to the 'POC Results Entry Configuration' form.
Steps
  1. Open the 'POC Results Entry Configuration' form.
  2. Select "Observation Definition" from the 'Section' menu.
  3. Select "Add" from the 'Add/Edit/Delete Observation' field.
  4. Populate the 'Observation ID Code' field.
  5. Select "Prompt Definition 1" from the 'Save as Vital Sign' field.
  6. Validate the 'Observation Value Unit' field contains "Prompt Definition 1 - Units".
  7. Delete the existing value from 'Observation Value Unit' field.
  8. Populate the 'Observation Value Unit' field with any value other than "Prompt Definition 1 - Units" and Press the Tab key.
  9. Validate an "Error Message" is displayed stating "If 'Save as Vital Sign' is defined the Observation Value Unit must either be blank or equal to Value Unit tied to the Vital Sign which is 'SS Vital Signs Free Text 1 - Units'."
  10. Click [OK].
  11. Click [Discard], validate the 'Confirm Close' dialog displays stating "Are you sure you want to Close without saving?" and click [Yes].
Topics
• POC Results Entry • POC Results Entry Configuration form
Update 19 Summary | Details
Medical Note - Limit Note Types By Practitioner Category
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • Dictionary Update (CWS)
Scenario 1: Medical Note - Limit Note Types by Practitioner Category
Specific Setup:
  • A dictionary code must exist for the CWS ‘(10751) Note Type’ dictionary. (Note Type A)
  • The ‘(79) Practitioner Category’ extended attribute must be set to “Medical Doctor” in the CWS ‘(10751) Note Type’ dictionary for "Note Type A".
  • The 'Avatar CWS->Progress Notes->Inpatient (Medical Diagnosis)->->->Limit Note Types By Practitioner Category' registry setting must be set to "Y".
  • The 'Avatar CWS->Progress Notes->Ambulatory (Medical Diagnosis)->->->Limit Note Types By Practitioner Category' registry setting must be set to "Y".
  • Please log out of the application and log back in after completing the above configuration.
  • The logged in user must be associated with a practitioner who has the 'Practitioner Category' field set to "Medical Doctor" in the 'Practitioner Enrollment' form.
  • A client must have an active episode. (Client A)
Steps
  1. Search for and select "Client A" and navigate to 'Medical Note'.
  2. Click [Add Note] and select "Psychiatry" from the 'Appointment/Note Workflow' field.
  3. Click the 'Note Type' field and validate the dropdown includes "Note Type A".
  4. Populate any remaining required fields, click [Save] and validate the note is created successfully.
Topics
• Medical Note
Update 23 Summary | Details
SQL Table validation - SYSTEM.cwtxProbDefStorage
Scenario 1: SYSTEM.cwtxProbDefStorage - Validating Data Retrieval
Specific Setup:
  • System is configured with 'Avatar Wiley Library 2024' product module.
  • Tester has access to the 'Crystal Report' or any other SQL data viewer for the system.
Steps
  1. Open the 'Crystal Report' or any other SQL data viewer.
  2. Run the SQL query to retrieve data from the 'SYSTEM.cwtxProbDefStorage' table.
  3. Verify that the data successfully retrieved from the table.
  4. Close the report.
Hospitalizations and Surgeries - Data Validation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Hospitalizations and Surgeries
Scenario 1: Hospitalizations and Surgeries - Data validation of the 'Hospital Data' table
Specific Setup:
  • Admission:
  • A new client is admitted, or an existing client is identified. Note the client's id and name of the client.
Steps
  1. Open ‘Hospitalizations and Surgeries’ form for the desired client.
  2. Add more than 10 rows of data with the desired reason code and with the classification of the "Medical", "Substance Abuse" and "Psychiatric" selected in the 'Filter by Classification' field.
  3. Click [Submit].
  4. Reopen the ‘Hospitalizations and Surgeries’ form for the same client.
  5. Verify all rows of data are correctly displayed.
  6. Verify the ‘Filter by Classification’ field is defaulted to ‘All’.
  7. Verify all records display in the grid regardless of assigned ‘Filter by Classification’ field.
  8. Click ‘Medical’ in the ‘Filter by Classification’ field.
  9. Verify only ‘Medical’ records display in the table.
  10. Click ‘Psychiatric’ in the ‘Filter by Classification’ field.
  11. Verify only ‘Psychiatric’ records display in the table.
  12. Click ‘Substance Abuse’ in the ‘Filter by Classification’ field.
  13. Verify only ‘Substance Abuse’ records display in the table.
  14. Click [Discard].
Topics
• Database Management • Hospitalizations and Surgeries
Update 28 Summary | Details
SQL Table validation - SYSTEM.tx_plan_recovery_plan
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
Scenario 1: Verify the Treatment Plan form is checking for required fields when it is submitted
Specific Setup:
  • An application with the new 'Treatment Plan' form must be used.
  • Note: If using the old 'Client Treatment Plan' form disregard this test.
Steps
  1. Open the 'Treatment Plan' form for any client and episode.
  2. Click the [Submit] button.
  3. Verify an error is received warning about missing required fields.
  4. Click the [T] button in the 'Plan Date' field to input today's date.
  5. Enter desired text into the 'Plan Name' field.
  6. Select any value from the 'Plan Type' field.
  7. Select "Draft" from the 'Treatment Plan Status' field.
  8. Add at least 1 row in the 'Problems' grid.
  9. Select "Final" from the ''Treatment Plan Status' field.
  10. Click [Submit].
  11. Verify the form files without errors.
  12. Open the 'Crystal Report' or any other SQL data viewer.
  13. Run the SQL query to retrieve data from the 'SYSTEM.tx_plan' table.
  14. Verify that the data successfully retrieved from the table.
  15. Close the report.
Scenario 2: SYSTEM.tx_plan_recovery_plan - Validating Data Retrieval
Specific Setup:
  • Tester has access to the 'Crystal Report' or any other SQL data viewer for the system.
Steps
  1. Open the 'Crystal Report' or any other SQL data viewer.
  2. Run the SQL query to retrieve data from the 'SYSTEM.tx_plan_recovery_plan' table. Include the 'service_display' field in the query.
  3. Verify that the data was successfully retrieved from the table.
  4. Close the report.
Topics
• Treatment Plan • Database Management
Update 29 Summary | Details
Treatment Plan - Participant Plan and Author Signatures
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
Scenario 1: Client Merge (InPatient and Outpatient)
Specific Setup:
  • At least two clients must be admitted to active episodes. One client is admitted in the inpatient program and the other client is admitted in the outpatient program. (Client A, and Client B).
Steps
  1. Access the 'Client Merge' form.
  2. Set the 'Source Client' field to "Client A"
  3. Select "Episode # 1" from the 'Source Client Episode' field.
  4. Set the 'Target Client' field to "Client B"
  5. Validate the 'Create New Episode On Merge' field is equal to "Yes"
  6. Click [File]
  7. Validate a 'Do you wish to continue with the indicated action?' message is displayed.
  8. Click [Yes].
  9. Validate a message stating 'The following new episode has been created for the target client indicated. Episode 2' is displayed.
  10. Click [OK].
  11. Click [Close Form]
  12. Using SQL, view the SQL tables SYSTEM.cw_tx_pn_sign_data and SYSTEM.cw_tx_pn_sign_data_audit,validate the date_captured and time_captured columns are populated in the row(s) added. Note: This only affects rows created since the update was installed. Previously filed data will have the columns but they won't be populated.
Scenario 2: Progress Notes (Group and Individual) Copy - Validate 'Treatment Plan' Grid and 'Signature' fields
Specific Setup:
  • Set the registry setting "Enable Treatment Plan Grid" to "Yes".
  • A signature field must be added to a copy of the Progress Note (Group and Individual) using "Site Specific Section Modeling".
  • Using "Document Routing Setup", enable document routing for the progress note copy form.
Steps
  1. Open the copy of the "Progress Notes (Group and Individual)" from setup that has a signature field.
  2. Add an independent progress note.
  3. In the Treatment plan Grid, attach a treatment plan problem.
  4. Click [Sign].
  5. Sign the document by using the signature pad.
  6. Set the "Draft/Final" field to "Final".
  7. Click [Submit].
  8. Enter the "Password".
  9. Validate the document image contains the signature.
  10. Using the preferred method to validate SQL data, validate a row was added to the CWSTEMP.cw_tx_pn_sign_data.
  11. Validate the above temporary table contains a column called date_captured and time_captured are correct based on when the document was signed.
  12. Click [Sign] or [Accept].
  13. Using the "Clinical Document Viewer" form, validate the document displays as it was saved with the signature included
  14. Using the preferred method to validate SQL data, validate a row was added to the SYSTEM.cw_tx_pn_sign_data and SYSTEM.cw_tx_pn_sign_data_audit.
  15. Validate the above SQL table contains a column called date_captured and time_captured are correct based on when the document was signed. Note: This only affects rows created since the update was installed. Previously filed data will have the columns but they won't be populated.
Scenario 3: Treatment Plan - Obtain Signature
Specific Setup:
  • The 'Treatment Plan' form must have a signature field.
  • A client must be enrolled in an existing episode (Client A).
  • Must have a Topaz Signature pad for testing.
  • Citrix Users - Citrix Versions (pre - 7.6) - BSB / BBSB pads are supported.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Select the desired value in the 'Plan Type' field.
  4. Select "Draft" in the 'Treatment Plan Status' field.
  5. Click [Launch Plan].
  6. Add the desired treatment plan items.
  7. Click [Return To Plan].
  8. In the "Plan Participants" section of the main page, click [New Row].
  9. Add a row to the Plan Participants table.
  10. Double-click on the "Signature" column of that row.
  11. Double-click [Sign] in the 'Signature' field.
  12. Validate the 'Please Sign Below' dialog is displayed.
  13. Use the mouse to sign in the dialog box.
  14. Validate the dialog contains the signature.
  15. Click [OK].
  16. Validate the 'Please Sign Below' dialog is no longer displayed.
  17. Validate no errors display and the 'Please Sign On Signature Pad' dialog is displayed. Please note: for users using the SigPlusExtLite, the following will display: "Opening signature dialog, please wait..." and an additional dialog will open.
  18. Sign on the signature pad.
  19. Validate the dialog contains the signature.
  20. Click [Cancel].
  21. Disconnect the signature pad.
  22. Double-click [Sign] in the 'Signature' field.
  23. Validate the 'Please Sign Below' dialog is displayed.
  24. Use the mouse to sign in the dialog box.
  25. Validate the dialog contains the signature.
  26. Click [OK].
  27. Validate the 'Please Sign Below' dialog is no longer displayed.
  28. Validate the 'Signature' field contains the signature.
  29. Select "Final" in the 'Treatment Plan Status' field.
  30. Submit the form.
  31. Validate the temporary SQL table CWSTEMP.cw_pn_tx_sign_data has a row added for the 2 treatment Plan grid signatures.
  32. Validate the document image contains all 3 signatures, the 2 from the participant grid and 1 from the form signature.
  33. Click [Sign]
  34. Key in the use's password.
  35. Click [Verify]
  36. Using SQL, view the SQL tables SYSTEM.cw_tx_pn_sign_data and SYSTEM.cw_tx_pn_sign_data_audit, validate the signaturecontent column is populated in the row(s) added. Note: This only affects rows created since the update was installed. Previously filed data will have the columns but they won't be populated.
  37. Using SQL, view the SQL tables SYSTEM.cw_tx_pn_sign_data and SYSTEM.cw_tx_pn_sign_data_audit,validate the date_captured and time_captured columns are populated in the row(s) added. Note: This only affects rows created since the update was installed. Previously filed data will have the columns but they won't be populated.
  38. Open the "Clinical Document Viewer"
  39. Select "Client" from the Select Type: drop down list
  40. Click the Individual radio button
  41. Set the 'Select Client'" to "601"
  42. Click the TAMMY SMITH (000000601) cell
  43. Click [Process]
  44. Click [View] button on row 1
  45. Validate the Signature(s) appear on the finalized form
  46. Click [Print]
  47. Validate the Signature appears on the printed document
  48. Click [Close All Documents]
  49. Click the [Search] tab
  50. Click [Close]
Topics
• Client Merge • Progress Notes • Treatment Plan
Update 33 Summary | Details
Progress Notes - 'Service Duration' field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
  • Ambulatory Progress Notes
  • Clinical
  • Set System Defaults (CWS)
Scenario 1: Progress Notes (Group and Individual) - File an independent note
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • 'Progress Notes (Group and Individual)' must have document routing enabled.
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer' ('All Documents' view).
  • A practitioner must be associated with the logged-in user (Practitioner A).
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select "Independent Note" in the 'Progress Note For' field.
  5. Validate the 'Service Duration' field is disabled.
  6. Select the desired value in the 'Note Type' field.
  7. Enter the desired value in the 'Notes Field'.
  8. Enter any value in the 'Recommended Decision Aids' field.
  9. Validate the 'Service Duration' field is disabled.
  10. Populate any other required or desired fields.
  11. Select "Final" in the 'Draft/Final' field.
  12. Click [Submit Note].
  13. Validate a 'Confirm Document' dialog is displayed.
  14. Click [Accept].
  15. Enter the password associated with the logged-in user and click [Verify].
  16. Validate a 'Progress Notes' dialog stating: "Note Filed. Do you want to return to the Progress Notes form?" and click [No].

2. Select "Client A" and navigate to the 'All Documents' view.

  1. Select 'All Forms'.
  2. Select "Progress Notes (Group and Individual)" from the 'Form Description' field.
  3. Validate that the note from the previous steps is present and select it.
  4. Validate the progress note displays as expected in the 'Console Widget Viewer'.
Progress Notes - 'Service Status' field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Ambulatory Progress Notes
  • Service Codes
  • Registry Settings (CWS)
  • Scheduling Calendar
  • Progress Notes (Group and Individual)
  • Dynamic Form - Individual Progress Notes - Warning
  • Client Ledger
  • Service Fee/Cross Reference Maintenance
  • SoapUI - ProgressNotes.Client.Request
  • SoapUI - ProgressNotes.Client.Request - AddProgressNotes
Scenario 1: Validate the Chart View for Existing Service Progress Notes
Specific Setup:
  • The 'Fields to Include in Client Charge Input' registry setting must have "6" selected for 'Service Status'.
  • Service status(es) must be defined in the 'Service Status Maintenance' form.
  • A client must be enrolled in an existing episode and have an existing service (Client A).
  • The existing service must have 'Service Status' populated.
  • 'Progress Notes (Group and Individual)' must be added to the Chart View.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Enter "Client A" in the 'Select Client' field.
  3. Select the desired value in the 'Select Episode' field.
  4. Select "Existing Service" in the 'Progress Notes For' field.
  5. Select the existing service for "Client A" in the 'Note Addresses Which Existing Service/Appointment' field.
  6. Select any value in the 'Note Type' field.
  7. Enter any value in the 'Notes Field' field.
  8. Validate the 'Service Status' field contains the value filed with the service.
  9. Clear the value in the 'Service Status' field.
  10. Select "Final" in the 'Draft/Final' field.
  11. Click [File Note].
  12. Validate a "Progress Notes" message is displayed stating: Note Filed.
  13. Click [OK] and close the form.
  14. Double click on "Client A" in the 'My Clients' widget.
  15. Validate the 'Chart View' is displayed for "Client A".
  16. Select 'Progress Notes (Group and Individual)' from the left-hand side.
  17. Validate the Existing Service note filed in the previous steps is displayed.
  18. Validate the 'Progress Note For' field contains "Existing Service".
  19. Validate the 'Note Type' field contains the note type selected in the previous steps.
  20. Validate the 'Notes Field' field contains the value entered in the previous steps.
  21. Validate the 'Practitioner' field contains the practitioner associated to the service for Client A.
  22. Validate the 'Date of Service' field contains the date of the service for Client A.
  23. Validate the 'Service Program' field contains the service program selected when creating the service.
  24. Validate the 'Service Charge Code' field contains the service code used when creating the service.
  25. Validate the 'Location' field contains the location of the service.
  26. Validate the 'Service Status' field is not displayed.
  27. Validate the 'Draft/Final' field contains "Final".
  28. Close the chart.
Topics
• Progress Notes • Group Progress Notes • Chart View
Update 34 Summary | Details
Treatment Plan - PCL Date fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Registry Settings (PM)
  • Required User List Management
Scenario 1: Treatment Plan - Validate 'Pending Approval' workflow with PCL date fields
Specific Setup:
  • Please note: this is for Avatar NX only.
  • A client is enrolled in an existing episode (Client A).
  • Document routing must be enabled for the 'Treatment Plan' form.
  • The 'Treatment Plan' form must have the following configured in 'Site Specific Section Modeling':
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan End Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL End Date'.
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan Finalized Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL Finalized Date'.
  • Two users must be defined with associated staff members (User A & User B).
  • "User A" and "User B" must be defined as workflow users in the 'Required User List Management' form for the 'Treatment Plan'.
Steps
  1. Log into Avatar NX as "User A".
  2. Select “Client A” and access the ‘Treatment Plan’ form.
  3. Enter the desired date in the 'Plan Date' field.
  4. Enter any value in the 'Plan Name' field.
  5. Select any value in the ‘Plan Type’ field.
  6. Enter the desired date in the 'Plan End Date' field.
  7. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are displayed and leave them blank.
  8. Select "Draft" in the 'Treatment Plan Status' field.
  9. Click [Launch Plan].
  10. Add a problem, goal, objective, and intervention.
  11. Populate all required and desired fields.
  12. Click [Return to Plan] and [OK].
  13. Select "Pending Approval" in the 'Treatment Plan Status' field.
  14. Click [Submit].
  15. Validate that a "Confirm Document" message is displayed.
  16. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are not displayed.
  17. Click [Accept and Route].
  18. Validate a "Verify Password" message is displayed.
  19. Enter the password associated with the logged-in user in the 'Password' field.
  20. Click [Verify].
  21. Select the practitioner associated to "User A" as an approver and the practitioner associated to "User B" as an approver/supervisor.
  22. Click [Submit].
  23. Log out.
  24. Log into Avatar NX as "User B".
  25. Navigate to the 'My To Do's' widget.
  26. Click [Documents to Sign].
  27. Validate the To Do for "Client A" is displayed.
  28. Click [Review].
  29. Validate the 'Document Preview' contains the treatment plan data, without the 'PCL End Date' and 'PCL Finalized Date' fields.
  30. Click [Accept] and [Sign].
  31. Validate a "Verify Password" message is displayed.
  32. Enter the password associated with the logged-in user in the 'Password' field.
  33. Click [Verify].
  34. Validate the To Do for "Client A" is no longer displayed.
  35. Log out.
  36. Log into Avatar NX as "User A".
  37. Navigate to the 'My To Do's' widget.
  38. Click [Documents to Sign].
  39. Validate the To Do for "Client A" is displayed.
  40. Click [Review].
  41. Validate the 'Document Preview' contains the treatment plan data.
  42. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are appended to the end of the document. If there are multiple approvers, these fields will only become visible when the last approver goes to approve the document.
  43. Click [Accept] and [Sign].
  44. Validate a "Verify Password" message is displayed.
  45. Enter the password associated with the logged-in user in the 'Password' field.
  46. Click [Verify].
  47. Validate the To Do for "Client A" is no longer displayed.
Scenario 2: Treatment Plan - Validate 'Final' workflow with PCL Date fields
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • Document routing must be enabled for the 'Treatment Plan' form.
  • The 'Treatment Plan' form must have the following configured in 'Site Specific Section Modeling':
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan End Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL End Date'.
  • 'SS Treatment Plan Client Date' field with "Use as 'Treatment Plan Finalized Date'" selected in the 'Product Custom Logic Definition' field. This field will be referred to as 'PCL Finalized Date'.
  • The logged in user must have an associated practitioner.
Steps
  1. Select “Client A” and access the ‘Treatment Plan’ form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Enter any value in the 'Plan Name' field.
  4. Select any value in the ‘Plan Type’ field.
  5. Enter the desired date in the 'Plan End Date' field.
  6. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are displayed and leave them blank.
  7. Select "Draft" in the 'Treatment Plan Status' field.
  8. Click [Launch Plan].
  9. Add a problem, goal, objective, and intervention.
  10. Populate all required and desired fields.
  11. Click [Return to Plan] and [OK].
  12. Select "Final" in the 'Treatment Plan Status' field.
  13. Click [Submit].
  14. Validate that a "Confirm Document" message is displayed.
  15. Validate the 'PCL End Date' and 'PCL Finalized Date' fields are displayed in the body of the document.
  16. Click [Accept and Route].
  17. Validate a "Verify Password" message is displayed.
  18. Enter the password associated with the logged-in user in the 'Password' field.
  19. Click [Verify].
  20. Select the practitioner associated to the logged in user as an approver.
  21. Click [Submit].
  22. Navigate to the 'My To Do's' widget.
  23. Click [Documents to Sign].
  24. Validate the To Do for "Client A" is displayed.
  25. Click [Review].
  26. Validate the 'Document Preview' contains the treatment plan data, with the 'PCL End Date' and 'PCL Finalized Date' fields in the body of the document.
  27. Click [Accept] and [Sign].
  28. Validate a "Verify Password" message is displayed.
  29. Enter the password associated with the logged-in user in the 'Password' field.
  30. Click [Verify].
  31. Validate the To Do for "Client A" is no longer displayed.
Scenario 3: Treatment Plan - Add a Problem, Goal, Objective, and Intervention with the 'Enable Automatic Backup' registry setting set to "Y"
Specific Setup:
  • The 'Avatar CWS->Treatment Plan->->->->Enable Automatic Backup' registry setting must be set to "Y".
  • A client must be enrolled in an existing 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’ to any value.
  4. Select any value in the ‘Plan Type’ field.
  5. Set the 'Strengths' field to any value.
  6. Set the 'Weaknesses' field to any value.
  7. Set the 'Discharge Planning' field to any value.
  8. Select “Draft” in the ‘Treatment Plan Status’ field and click [Launch Plan].
  9. Click [Add New Problem], [Add New Goal], [Add New Objective] and [Add New Intervention].
  10. Without populating the required fields, click [Return to Plan].
  11. Select "Final" in the 'Treatment Plan Status' field.
  12. Validate a 'Missing Required Fields' dialog is displayed.
  13. Click [OK].
  14. Validate "Draft" remains selected in the 'Treatment Plan Status' field.
  15. Click [Launch Plan].
  16. Select the problem added in the previous steps.
  17. Set the ‘Problem Code’ field to any value.
  18. Select “Active” in the ‘Status (Problem List)’ field.
  19. Set the ‘Problem’ field to any value.
  20. Select any value in the ‘Status’ field.
  21. Select any value in the 'Staff Assigning' field.
  22. Select any value in the 'Staff Responsible' field.
  23. Select the goal added in the previous steps.
  24. Set the ‘Goal’ field to any value.
  25. Select any value in the ‘Status’ field.
  26. Select any value in the 'Staff Assigning' field.
  27. Select any value in the 'Staff Responsible' field.
  28. Select the objective added in the previous steps.
  29. Set the ‘Objective’ field to any value.
  30. Select any value in the ‘Status’ field.
  31. Select any value in the 'Staff Assigning' field.
  32. Select any value in the 'Staff Responsible' field.
  33. Select the intervention added in the previous steps.
  34. Set the ‘Intervention’ field to any value.
  35. Select any value in the ‘Status’ field.
  36. Select any value in the 'Staff Assigning' field.
  37. Select any value in the 'Staff Responsible' field.
  38. Click [Back to Plan Page] and close the form.
  39. Select “Client A” and access the ‘Treatment Plan’ form.
  40. Validate the ‘Load From Backup’ dialog displays with a message stating: "You have an unsubmitted backup of a plan from [the current date] and [the current time]. Would you like to load it instead of creating a new one?" and click [Yes].
  41. Validate the 'Strengths' field contains the value previously filed.
  42. Validate the 'Weaknesses' field contains the value previously filed.
  43. Validate the 'Discharge Planning' field contains the value previously filed.
  44. Click [Launch Plan].
  45. Validate the ‘Tree view’ contains values for the problem, goal, objective, and intervention previously added with all updated data.
  46. Click [Exit to Home View].
Scenario 4: Treatment Plan - File a Treatment Plan with Document Routing
Specific Setup:
  • The client is enrolled in an existing episode (Client A).
  • The 'Treatment Plan' form must have document routing enabled.
  • Must have the 'My To Do's' widget configured on a view.
  • The 'Set Current Status To Active When Plan Is Finalized' registry setting is set to "N" for the 'Treatment Plan' form.
  • The 'Set Current Status To Completed On Plan End Date' registry setting is set to "N" for the 'Treatment Plan' form.
  • The 'Enable Automatic Backup' registry setting is set to "N".
  • Must have a Word document with text containing smart quotes (Text A).
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Click [Add].
  3. Enter the current date displayed in the 'Plan Date' field.
  4. Select the desired date in the 'Plan Date' field.
  5. Select the desired value in the 'Plan Type' field
  6. Select "Draft" in the 'Treatment Plan Status' field.
  7. Enter any value in the 'Strength' field.
  8. Click on the [Text Editor] icon for the 'Strength Field'.
  9. Copy "Text A" from the Word document and paste it into the 'Text Editor'.
  10. Click [Save].
  11. Validate that the 'Strength Field' contains the value from "Text A".
  12. Validate "Draft" is now selected in the 'Current Status' field.
  13. Click [Launch Plan].
  14. Add a problem, goal, objective, and intervention.
  15. Click [Return to Plan] and [OK].
  16. Validate the 'Plan Date' field is disabled.
  17. Select "Final" in the 'Draft/Final' field.
  18. Select "Active" in the 'Current Status' field.
  19. Click [Submit].
  20. Validate a 'Confirm Document' dialog is displayed.
  21. Validate all treatment plan data displays as expected. Please note: the 'Current Status' field will not be included in the document image. This is because the 'Current Status' field can be updated after a 'Treatment Plan' has been finalized.
  22. Click [Accept].
  23. Enter the password and click [Verify].
  24. Select "Client A" and access the 'Treatment Plan' form.
  25. Select the record from the previous steps and click [Edit].
  26. Validate a message is displayed stating: This plan is marked as Final. Only the following field(s) may be updated: 'Current Status'. Do you want to continue?
  27. Click [Yes].
  28. Validate the plan displays as expected and fields are disabled, except for the 'Current Status' field.
  29. Select "Completed" in the 'Current Status' field.
  30. Click [Submit].
  31. Validate a message is displayed stating: The following fields are updated: 'Current Status'.
  32. Click [OK].
  33. Select "Client A" and access the 'Treatment Plan' form.
  34. Select the record from the previous steps and click [Edit].
  35. Validate a message is displayed stating: This plan is marked as Final. Only the following field(s) may be updated: 'Current Status'. Do you want to continue?
  36. Click [Yes].
  37. Validate "Completed" is selected in the 'Current Status' field.
  38. Close the form.
Topics
• Treatment Plan • Document Routing
Update 40 Summary | Details
Allergies and Hypersensitivities - 'History' column
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Change MR#
  • Delete Last Movement
  • Crystal Report Viewer
Scenario 1: Allergies and Hypersensitivities - Validate 'Change MR#' functionality
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  2. Select "No" in the 'Known Medication Allergies' field.
  3. Select "No" in the 'Known Food Allergies' field.
  4. Click [Update].
  5. Validate the 'Allergies and Hypersensitivities' grid is displayed.
  6. Click [New Row].
  7. Validate the current date displays as expected in the 'Date Recorded' field.
  8. Search for and select the desired value in the 'Allergen/Reactant' field.
  9. Enter the desired date in the 'Date Recognized' field.
  10. Select the desired value in the 'Status' field.
  11. Select the desired value in the 'Reactions' field.
  12. Select the desired value in the 'Reaction Severity' field.
  13. Enter the desired value in the 'Onset' field.
  14. Enter the desired value in the 'Treatment' field.
  15. Enter the desired value in the 'Comments' field.
  16. Validate the 'History' column is displayed.
  17. Click [Save].
  18. Validate the 'Allergies and Hypersensitivities' grid is no longer displayed.
  19. Click [Update].
  20. Validate the allergy added in the previous steps is displayed as expected.
  21. Click [View] in the 'History' field.
  22. Validate 'History' dialog displays a row with the following data:
  23. Action - Added
  24. Date
  25. Allergen/Reactant
  26. Status
  27. Reaction Severity
  28. User
  29. Close the dialog.
  30. Select any new value in the 'Status' field.
  31. Click [Save] and [Submit].
  32. Access the 'Change MR#' form.
  33. Select "Client A" in the 'Client ID' field.
  34. Click [Assign MR#] and [Yes].
  35. Validate the 'New Client ID#' field contains a new ID for "Client A".
  36. Submit the form.
  37. Validate the ID# for "Client A" has been updated.
  38. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  39. Click [Update].
  40. Validate the allergy filed in the previous steps is displayed as expected.
  41. Click [View] in the 'History' field.
  42. Validate 'History' dialog displays a row with the following data:
  43. Action - Added
  44. Date
  45. Allergen/Reactant
  46. Status
  47. Reaction Severity
  48. User
  49. Close the form.
Scenario 2: Allergies and Hypersensitivities - Add/Edit Allergies
Specific Setup:
  • A client must have an active episode. (Client A)
Steps
  1. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  2. Select "No" in the 'Known Medication Allergies' field.
  3. Select "No" in the 'Known Food Allergies' field.
  4. Click [Update].
  5. Validate the 'Allergies and Hypersensitivities' grid is displayed.
  6. Click [New Row].
  7. Validate the current date displays as expected in the 'Date Recorded' field.
  8. Search for and select the desired value in the 'Allergen/Reactant' field.
  9. Enter the desired date in the 'Date Recognized' field.
  10. Select the desired value in the 'Status' field.
  11. Select the desired value in the 'Reactions' field.
  12. Select the desired value in the 'Reaction Severity' field.
  13. Enter the desired value in the 'Onset' field.
  14. Enter the desired value in the 'Treatment' field.
  15. Enter the desired value in the 'Comments' field.
  16. Validate the 'History' column is displayed.
  17. Click [Save].
  18. Validate the 'Allergies and Hypersensitivities' grid is no longer displayed.
  19. Click [Update].
  20. Validate the allergy added in the previous steps is displayed as expected.
  21. Click [View] in the 'History' field.
  22. Validate 'History' dialog displays a row with the following data:
  23. Action - Added
  24. Date
  25. Allergen/Reactant
  26. Status
  27. Reaction Severity
  28. User
  29. Close the dialog.
  30. Select any new value in the 'Status' field.
  31. Click [Save] and [Submit].
  32. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  33. Click [Update].
  34. Validate the allergy filed in the previous steps is displayed with the updated 'Status'.
  35. Click [View] in the 'History' field.
  36. Validate the 'History' dialog displays a second row with the following data:
  37. Action - Updated
  38. Date
  39. Allergen/Reactant
  40. Status - Contains the updated 'Status'
  41. Reaction Severity
  42. User
  43. Close the dialog and the form.
Scenario 3: Allergies and Hypersensitivities - Validate 'Client Merge' functionality
Specific Setup:
  • Two clients are enrolled in existing episodes (Client A & Client B).
Steps
  1. Select "Client A" and access the 'Allergies and Hypersensitivities' form.
  2. Select "No" in the 'Known Medication Allergies' field.
  3. Select "No" in the 'Known Food Allergies' field.
  4. Click [Update].
  5. Validate the 'Allergies and Hypersensitivities' grid is displayed.
  6. Click [New Row].
  7. Validate the current date displays as expected in the 'Date Recorded' field.
  8. Search for and select the desired value in the 'Allergen/Reactant' field.
  9. Enter the desired date in the 'Date Recognized' field.
  10. Select the desired value in the 'Status' field.
  11. Select the desired value in the 'Reactions' field.
  12. Select the desired value in the 'Reaction Severity' field.
  13. Enter the desired value in the 'Onset' field.
  14. Enter the desired value in the 'Treatment' field.
  15. Enter the desired value in the 'Comments' field.
  16. Validate the 'History' column is displayed.
  17. Click [Save].
  18. Validate the 'Allergies and Hypersensitivities' grid is no longer displayed.
  19. Click [Update].
  20. Validate the allergy added in the previous steps is displayed as expected.
  21. Click [View] in the 'History' field.
  22. Validate 'History' dialog displays a row with the following data:
  23. Action - Added
  24. Date
  25. Allergen/Reactant
  26. Status
  27. Reaction Severity
  28. User
  29. Close the dialog.
  30. Select any new value in the 'Status' field.
  31. Click [Save] and [Submit].
  32. Access the 'Client Merge' form.
  33. Select "Client A" in the 'Source Client' field.
  34. Select "Yes" in the 'Merge All Client Data Through Single Filing' field.
  35. Select "Client B" in the 'Target Client' field.
  36. Select "Yes" in the 'Create New Episode On Merge' field.
  37. Click [File] and [Yes].
  38. Validate a message is displayed stating: All information has been merged into the target client and the source client has been deleted from the system.
  39. Click [OK] and close the form.
  40. Select "Client B" and access the 'Allergies and Hypersensitivities' form.
  41. Click [Update].
  42. Validate the allergy merged from "Client A" is displayed as expected.
  43. Click [View] in the 'History' field.
  44. Validate 'History' dialog displays a row with the following data:
  45. Action - Added
  46. Date
  47. Allergen/Reactant
  48. Status
  49. Reaction Severity
  50. User
  51. Close the form.
Topics
• Allergies and Hypersensitivities
Update 43 Summary | Details
Table Definition - 'Pathway Name' field aliasing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Pathway Definition
  • Clinical Pathway Enrollment
  • Dictionary Update (CWS)
  • Clinical Pathway Disenrollment
  • Table Definition (CWS)
Scenario 1: Clinical Pathway Enrollment - Table Aliasing
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • One or more pathways defined in the 'Clinical Pathway Definition' form.
  • A user defined modeled form is required that contains the following fields: 'Date of Enrollment', 'Pathway Name', and 'Primary Pathway'. This form will be referred to as "Form A". "Form A" is associated to the table described below.
  • The following must be configured in the 'Table Definition' form- this table will be referred to as "Table A":
  • In the "Column Definition" section:
  • Add a row for 'Pathway Name' with: "Yes" selected in 'Is This Column An Alias To Another Column?', "CWS" selected in 'Alias Type', "(5011) Pathway Name" selected in 'Alias Column'.
  • Add a row for 'Date of Enrollment'.
  • Add a row for 'Primary Pathway'.
  • In the "Table Alias" section, add a row and select "CWS" as the 'Alias Entity Database' and "Clinical Pathway Enrollment" as the 'Alias Table'.
  • In the "Column Mapping" section, add a row and select the column created for "Pathway Name" in the 'Table Column' field and select "Pathway Name" in the 'Alias Table Column' field. Add a second row and select the column created for 'Primary Pathway' in the 'Table Column' field and select "Primary Pathway" in the 'Alias Table Column' field.
Steps
  1. Access the 'Table Definition' form.
  2. Select "Table A" in the 'Select Table' dialog.
  3. Select the "Column Definition" section.
  4. Select the column for "Pathway Name".
  5. Validate the 'Type of Column' is "Dictionary - Single Response".
  6. Close the form.
  7. Select "Client A" and access "Form A".
  8. Validate the 'Pathway Name' field is a single-select dictionary field with all defined pathways.
  9. Select the desired pathway in the 'Pathway Name' field.
  10. Select "Yes" in the 'Primary Pathway' field.
  11. Click [Submit].
  12. Select "Client A" and access the 'Clinical Pathway Enrollment' form.
  13. Validate the enrollment filed in "Form A" is displayed.
  14. Click [Edit].
  15. Validate the previously filed values are displayed as expected.
  16. Close the form.
Clinical Pathway Definition - Edit a pathway
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Pathway Definition
  • Clinical Pathway Enrollment
  • Dictionary Update (CWS)
  • Clinical Pathway Disenrollment
Scenario 1: 'Clinical Pathway Definition' form - Edit a pathway
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
  • The 'Include Client Information header in view' setting is enabled for the user's myDay view.
  • "Clinical Pathway" must be added to the 'Field to Include in Client Header' field in the 'Client Lookup/Header Configuration Manager' form.
Steps
  1. Access the 'Clinical Pathway Definition' form.
  2. Select "New" in the 'Create New or Edit Existing' field.
  3. Enter an alphanumeric value in the 'Pathway ID' field.
  4. Enter "Pathway A" the 'Pathway Name' field.
  5. Select "Yes" in the 'Alert When Client is Accessed?' field. This will cause an alert to display whenever the client is accessed.
  6. Select any value in the 'Appointment Status to Alert' field. This field will trigger an alert when an appointment with this status takes place.
  7. To highlight the pathway using a specific color, enter the color code. Must be in the format of '#FBD9D9'.
  8. Click [Import Icon].
  9. Navigate to the location of the icon and select the icon. When a client is assigned this clinical pathway, the icon will display on the Client Header banner.
  10. Click [Submit].
  11. Select "Client A" and access the 'Clinical Pathway Enrollment' form.
  12. Verify the 'Date of Enrollment' field defaults to the current date.
  13. Select "Pathway A" in the 'Pathway Name' field.
  14. Select "Yes" for 'Primary Pathway'.
  15. Click [Submit] and [No].
  16. Access the 'Clinical Pathway Definition' form.
  17. Select "Edit Existing" in the 'Create New or Edit Existing' field.
  18. Select "Pathway A" in the 'Pathway List' field.
  19. Enter any new value in the 'Pathway Name' field.
  20. Click [Submit] and [No].
  21. Select "Client A" and navigate to the 'Client Information' header.
  22. Navigate to the client alert and validate it displays: Select Client is Enrolled in the following Clinical Pathways: Updated name for "Pathway A".
  23. Access Crystal Reports or other SQL Reporting tool.
  24. Create a report using the 'SYSTEM.Clinical_Pathway_Enrollments' table.
  25. Navigate to the row for "Client A".
  26. Validate the 'pathway_name' field contains the updated name for "Pathway A".
  27. Close the report.
Topics
• Clinical Pathway
Update 45 Summary | Details
Observer NX - future functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Manage Nursing Caseload
  • Nursing Caseload Assignment
  • Manage Observer Caseload
  • Crystal Report Viewer
  • Observer.Observation
Scenario 1: Observer NX - Validate filing an observation for 5 minute interval
Steps

Internal Testing Only.

Scenario 2: Observer NX - Validate transfers in the "Observer.caseload_audit" table
Steps

Internal Testing Only.

Scenario 3: Observer NX - Validate filing an observation for 10 minute interval
Steps

Internal Testing Only.

Scenario 4: Observer NX - Validate filing an observation for 15 minute interval
Steps

Internal Testing Only.

Scenario 5: Observer NX - Validate filing an observation for 30 minute interval
Steps

Internal Testing Only.

Scenario 6: Observer NX - Validate filing an observation for 60 minute interval
Steps

Internal Testing Only.
Topics
• Observer NX • NX Only
Update 47 Summary | Details
'Treatment Plan' - required fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • Treatment Plan
Scenario 1: Treatment Plan - Add a Problem, Goal, Objective, and Intervention with the 'Enable Automatic Backup' registry setting set to "Y"
Specific Setup:
  • The 'Avatar CWS->Treatment Plan->->->->Enable Automatic Backup' registry setting must be set to "Y".
  • A client must be enrolled in an existing 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’ to any value.
  4. Select any value in the ‘Plan Type’ field.
  5. Set the 'Strengths' field to any value.
  6. Set the 'Weaknesses' field to any value.
  7. Set the 'Discharge Planning' field to any value.
  8. Select “Draft” in the ‘Treatment Plan Status’ field and click [Launch Plan].
  9. Click [Add New Problem], [Add New Goal], [Add New Objective] and [Add New Intervention].
  10. Without populating the required fields, click [Return to Plan].
  11. Select "Final" in the 'Treatment Plan Status' field.
  12. Validate a 'Missing Required Fields' dialog is displayed.
  13. Click [OK].
  14. Validate "Draft" remains selected in the 'Treatment Plan Status' field.
  15. Click [Launch Plan].
  16. Select the problem added in the previous steps.
  17. Set the ‘Problem Code’ field to any value.
  18. Select “Active” in the ‘Status (Problem List)’ field.
  19. Set the ‘Problem’ field to any value.
  20. Select any value in the ‘Status’ field.
  21. Select any value in the 'Staff Assigning' field.
  22. Select any value in the 'Staff Responsible' field.
  23. Select the goal added in the previous steps.
  24. Set the ‘Goal’ field to any value.
  25. Select any value in the ‘Status’ field.
  26. Select any value in the 'Staff Assigning' field.
  27. Select any value in the 'Staff Responsible' field.
  28. Select the objective added in the previous steps.
  29. Set the ‘Objective’ field to any value.
  30. Select any value in the ‘Status’ field.
  31. Select any value in the 'Staff Assigning' field.
  32. Select any value in the 'Staff Responsible' field.
  33. Select the intervention added in the previous steps.
  34. Set the ‘Intervention’ field to any value.
  35. Select any value in the ‘Status’ field.
  36. Select any value in the 'Staff Assigning' field.
  37. Select any value in the 'Staff Responsible' field.
  38. Click [Back to Plan Page] and close the form.
  39. Select “Client A” and access the ‘Treatment Plan’ form.
  40. Validate the ‘Load From Backup’ dialog displays with a message stating: "You have an unsubmitted backup of a plan from [the current date] and [the current time]. Would you like to load it instead of creating a new one?" and click [Yes].
  41. Validate the 'Strengths' field contains the value previously filed.
  42. Validate the 'Weaknesses' field contains the value previously filed.
  43. Validate the 'Discharge Planning' field contains the value previously filed.
  44. Click [Launch Plan].
  45. Validate the ‘Tree view’ contains values for the problem, goal, objective, and intervention previously added with all updated data.
  46. Click [Exit to Home View].
Scenario 2: Treatment Plan - Add a Problem, Goal, Objective, and Intervention with the 'Enable Automatic Backup' registry setting set to "Y"
Specific Setup:
  • The 'Avatar CWS->Treatment Plan->->->->Enable Automatic Backup' registry setting must be set to "Y".
  • A client must be enrolled in an existing 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’ to any value.
  4. Select any value in the ‘Plan Type’ field.
  5. Set the 'Strengths' field to any value.
  6. Set the 'Weaknesses' field to any value.
  7. Set the 'Discharge Planning' field to any value.
  8. Select “Draft” in the ‘Treatment Plan Status’ field and click [Launch Plan].
  9. Click [Add New Problem], [Add New Goal], [Add New Objective] and [Add New Intervention].
  10. Without populating the required fields, click [Return to Plan].
  11. Select "Final" in the 'Treatment Plan Status' field.
  12. Validate a 'Missing Required Fields' dialog is displayed.
  13. Click [OK].
  14. Validate "Draft" remains selected in the 'Treatment Plan Status' field.
  15. Click [Launch Plan].
  16. Select the problem added in the previous steps.
  17. Set the ‘Problem Code’ field to any value.
  18. Select “Active” in the ‘Status (Problem List)’ field.
  19. Set the ‘Problem’ field to any value.
  20. Select any value in the ‘Status’ field.
  21. Select any value in the 'Staff Assigning' field.
  22. Select any value in the 'Staff Responsible' field.
  23. Select the goal added in the previous steps.
  24. Set the ‘Goal’ field to any value.
  25. Select any value in the ‘Status’ field.
  26. Select any value in the 'Staff Assigning' field.
  27. Select any value in the 'Staff Responsible' field.
  28. Select the objective added in the previous steps.
  29. Set the ‘Objective’ field to any value.
  30. Select any value in the ‘Status’ field.
  31. Select any value in the 'Staff Assigning' field.
  32. Select any value in the 'Staff Responsible' field.
  33. Select the intervention added in the previous steps.
  34. Set the ‘Intervention’ field to any value.
  35. Select any value in the ‘Status’ field.
  36. Select any value in the 'Staff Assigning' field.
  37. Select any value in the 'Staff Responsible' field.
  38. Click [Back to Plan Page] and close the form.
  39. Select “Client A” and access the ‘Treatment Plan’ form.
  40. Validate the ‘Load From Backup’ dialog displays with a message stating: "You have an unsubmitted backup of a plan from [the current date] and [the current time]. Would you like to load it instead of creating a new one?" and click [Yes].
  41. Validate the 'Strengths' field contains the value previously filed.
  42. Validate the 'Weaknesses' field contains the value previously filed.
  43. Validate the 'Discharge Planning' field contains the value previously filed.
  44. Click [Launch Plan].
  45. Validate the ‘Tree view’ contains values for the problem, goal, objective, and intervention previously added with all updated data.
  46. Click [Exit to Home View].
Topics
• Treatment Plan
Update 50 Summary | Details
Progress Notes - 'Treatment Plan' grid
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • Registry Settings (PM)
  • Progress Notes (Group and Individual)
  • Registry Settings (CWS)
  • Ambulatory Progress Notes
  • Problem List
Scenario 1: Progress Notes (Group and Individual) - Validate the 'Enable Treatment Plan Grid' registry setting
Specific Setup:
  • The 'Enable Treatment Plan Grid' registry setting must be set to "Y" for the 'Progress Notes (Group and Individual)' form.
  • A client must be enrolled in an existing episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated with the following special characters - <, >, ', " added to it (Client A).
  • The 'Progress Notes (Group and Individual)' form must be accessible from the Chart View.
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Enter "Client A" in the 'Select Client' field.
  3. Select the desired episode in the 'Select Episode' field.
  4. Select "Independent Note" in the 'Progress Note For' field.
  5. Select any value in the 'Note Type' field.
  6. Enter the desired value in the 'Notes Field' field.
  7. Populate any other required and desired fields.
  8. Click [New Row] in the 'Treatment Plan' grid.
  9. Select the desired Treatment Plan in the 'Select T.P. Version' field.
  10. Click [View] in the 'Select T.P. Item Note Addresses' field.
  11. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  12. Validate the treatment plan items are displayed with correct characters.
  13. Select the desired treatment plan item in the 'Treatment Plan' window.
  14. Click [Return].
  15. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  16. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  17. Select "Final" in the 'Draft/Final' field.
  18. Submit the note.
  19. Access the 'Chart View' for "Client A".
  20. Select "Progress Notes (Group and Individual)" from the Forms list.
  21. Validate the progress note filed in the previous steps is displayed.
  22. Validate the treatment plan data filed displays as expected with the proper characters.
  23. Close the chart.
  24. Access Crystal Reports or other SQL Reporting tool
  25. Select the CWS namespace.
  26. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  27. Validate a row is displayed for "Client A".
  28. Validate the 'note_add_which_tp_plan_prob' field contains the proper characters for the treatment plan items.
  29. Close the report.
Scenario 2: Ambulatory Progress Notes - Validate the 'Enable Treatment Plan Grid' registry setting
Specific Setup:
  • The 'Enable Treatment Plan Grid' registry setting must be set to "Y" for the 'Ambulatory Progress Notes' form.
  • A client must be enrolled in an outpatient episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated with the following special characters - <, >, ', " added to it (Client A).
  • The 'Ambulatory Progress Notes' form must be accessible from the Chart View.
Steps
  1. Select "Client A" and access the 'Ambulatory Progress Notes' form.
  2. Select the desired episode in the 'Select Episode' field.
  3. Select "Independent Note" in the 'Progress Note For' field.
  4. Select any value in the 'Note Type' field.
  5. Enter the desired value in the 'Notes Field'.
  6. Populate any other required and desired fields.
  7. Click [New Row] in the 'Treatment Plan' grid.
  8. Select the desired Treatment Plan in the 'Select T.P. Version' field.
  9. Click [View] in the 'Select T.P. Item Note Addresses' field.
  10. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  11. Validate the treatment plan items are displayed with correct characters.
  12. Select the desired treatment plan item in the 'Treatment Plan' window.
  13. Click [Return].
  14. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  15. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  16. Select "Final" in the 'Draft/Final' field.
  17. Submit the form.
  18. Access the 'Chart View' for "Client A".
  19. Select "Ambulatory Progress Notes" from the Forms list.
  20. Validate the progress note filed in the previous steps is displayed.
  21. Validate the treatment plan data filed displays as expected with the proper characters.
  22. Close the chart.
  23. Access Crystal Reports or other SQL Reporting tool
  24. Select the CWS namespace.
  25. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  26. Validate a row is displayed for "Client A".
  27. Validate the 'note_add_which_tp_plan_prob' field contains the proper characters for the treatment plan items.
  28. Close the report.
Scenario 3: Inpatient Progress Notes - Validate the 'Enable Treatment Plan Grid' registry setting
Specific Setup:
  • The 'Enable Treatment Plan Grid' registry setting must be set to "Y" for the 'Inpatient Progress Notes' form.
  • A client must be enrolled in an inpatient episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated with the following special characters - <, >, ', " added to it (Client A).
  • The 'Inpatient Progress Notes' form must be accessible from the Chart View.
Steps
  1. Select "Client A" and access the 'Inpatient Progress Notes' form.
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select any value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field'.
  5. Populate any other required and desired fields.
  6. Click [New Row] in the 'Treatment Plan' grid.
  7. Select the desired Treatment Plan in the 'Select T.P. Version' field.
  8. Click [View] in the 'Select T.P. Item Note Addresses' field.
  9. Verify the 'Treatment Plan' window is displayed with "Client A's" treatment plan(s).
  10. Validate the treatment plan items are displayed with correct characters.
  11. Select the desired treatment plan item in the 'Treatment Plan' window.
  12. Click [Return].
  13. Validate the 'Note Addresses Which Treatment Plan Problem' field contains the Treatment Plan item selected in the previous step.
  14. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  15. Select "Final" in the 'Draft/Final' field.
  16. Submit the form.
  17. Access the 'Chart View' for "Client A".
  18. Select "Inpatient Progress Notes" from the Forms list.
  19. Validate the progress note filed in the previous steps is displayed.
  20. Validate the treatment plan data filed displays as expected with the proper characters.
  21. Close the chart.
  22. Access Crystal Reports or other SQL Reporting tool
  23. Select the CWS namespace.
  24. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  25. Validate a row is displayed for "Client A".
  26. Validate the 'note_add_which_tp_plan_prob' field contains the proper characters for the treatment plan items.
  27. Close the report.
Topics
• Treatment Plan • Progress Notes
Update 52 Summary | Details
'Treatment Plan' web service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Treatment Plan
  • SOAPUI - Delete Treatment Plan
  • SoapUI - Get Treatment Plan
Scenario 1: Treatment Plan Web Service - Error validations
Specific Setup:
  • A required 'SS Treatment Plan Client Date' field is added to the 'Objectives' section of the 'Treatment Plan' form via 'Site Specific Section Modeling' (Field A).
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access SoapUI for the 'TreatmentPlan' - 'AddTreatmentPlan' 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 'PlanDate' field.
  6. Enter the desired value in the 'PlanName' field.
  7. Enter the desired value in the 'PlanType' field.
  8. Enter the desired value in the 'TreatmentPlanStatus' field.
  9. Populate all required and desired fields.
  10. Enter all required fields for a problem in the 'TreatmentPlanProblems' section.
  11. Add an associated objective for the problem entered above.
  12. Enter an objective description containing more than 50 characters.
  13. Enter "Field A" in the 'SSDate' - 'FieldNumber' field.
  14. Leave the 'SSDate' - 'FieldValue' field blank.
  15. Repeat steps 1i-1k for 6 more problems/objectives.
  16. Enter "Client A" in the 'ClientID' field.
  17. Enter "1" in the 'EpisodeNumber' field.
  18. Enter "CWS60000" in the 'OptionID' field.
  19. Click [Run].
  20. Validate the 'Message' field contains: Web service request failed with error : Missing Required Fields. Cannot finalize plan until the following required fields are complete.
  21. Enter a valid date in the 'SSDate' - 'FieldValue' fields for all objectives.
  22. Click [Run].
  23. Validate that the 'Confirmation' field contains the unique ID for the treatment plan filed.
  24. Validate the 'Message' field contains: "Treatment Plan web service has been filed successfully".
  25. Select "Client A" and access the 'Treatment Plan' form.
  26. Select the record filed in the previous steps and click [Edit].
  27. Validate all data filed in the previous steps is displayed.
  28. Close the form.
Topics
• Treatment Plan • Web Services
Update 54 Summary | Details
Progress Notes - Signatures and Treatment Plan Grid data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Registry Settings (PM)
  • Progress Notes (Group and Individual)
  • Registry Settings (CWS)
  • Ambulatory Progress Note
  • Treatment Plan
  • SQL
Scenario 1: Progress Notes (Group and Individual) - Validate 'Treatment Plan' Grid and 'Signature' fields
Specific Setup:
  • Signature support must be enabled in the 'System Security Defaults' form.
  • The 'Progress Notes' widget is accessible on the HomeView.
  • The 'Enable Treatment Plan Grid' registry setting is set to "Y" for the 'Progress Notes (Group and Individual)' form.
  • The 'Progress Notes (Group and Individual)' form must have a signature field added via 'Site Specific Section Modeling' (Signature A).
  • A client must have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
  • Must have a crystal report configured for document routing configured for "Signature A" and the 'Treatment Plan' grid for progress notes (Crystal Report A).
  • Crystal Report Document Routing must be configured for the 'Progress Notes (Group and Individual)' form using "Crystal Report A".
Steps
  1. Access the 'Progress Notes (Group and Individual)' form.
  2. Select "Client A" in the 'Select Client' field.
  3. Select "Independent Note" in the 'Progress Note For' field.
  4. Select the desired value in the 'Note Type' field.
  5. Click [New Row] in the 'Treatment Plan Grid'.
  6. Select "Treatment Plan" in the 'Select T.P. Version' field.
  7. Click [View].
  8. Select the desired treatment plan item and click [Return].
  9. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  10. Click [Sign] for "Signature A" and enter the desired signature.
  11. Select "Final" in the 'Draft/Final' field.
  12. Click [File Note].
  13. Validate the 'Confirm Document' dialog is displayed with "Crystal Report A". Validate the signature and treatment plan grid data display as expected.
  14. Leave the form open.
  15. Access Crystal Reports or other SQL Reporting Tool.
  16. Create a report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  17. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  18. Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  19. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  20. Navigate back to the 'Progress Notes (Group and Individual)' form.
  21. Click [Accept].
  22. Enter the password associated to the logged in user.
  23. Close the form.
  24. Access Crystal Reports or other SQL Reporting Tool.
  25. Refresh the report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  26. Validate a row is no longer displayed for the treatment plan data entered for "Client A" in the previous steps.
  27. Refresh the report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  28. Validate a row is no longer displayed for the signature data entered for "Client A" in the previous steps.
  29. Select "Client A" and access the 'Progress Notes' widget.
  30. Validate the progress note filed in the previous steps is displayed with the treatment plan and signature data.
  31. Access Crystal Reports or other SQL Reporting Tool.
  32. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  33. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  34. Close the report.
  35. Create a report using the 'SYSTEM.cw_tx_pn_sign_data' SQL table.
  36. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  37. Close the report.
Scenario 2: Ambulatory Progress Notes - Validate 'Treatment Plan' Grid and Signature fields
Specific Setup:
  • Signature support must be enabled in the 'System Security Defaults' form.
  • The 'Progress Notes' widget is accessible on the HomeView.
  • The 'Enable Treatment Plan Grid' registry setting is set to "Y" for the 'Ambulatory Progress Notes' form.
  • A copy of the 'Ambulatory Progress Notes' form must be defined and have a signature field added via 'Site Specific Section Modeling' (Signature A).
  • A client must be enrolled in an outpatient episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
  • Must have a crystal report configured for document routing configured for "Signature A" and the 'Treatment Plan' grid for 'Ambulatory Progress Notes' (Crystal Report A).
  • Crystal Report Document Routing must be configured for the 'Ambulatory Progress Notes' form using "Crystal Report A".
Steps
  1. Select "Client A" and access the 'Ambulatory Progress Notes' form.
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select the desired value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field'.
  5. Click [New Row] in the 'Treatment Plan Grid'.
  6. Select "Treatment Plan" in the 'Select T.P. Version' field.
  7. Click [View].
  8. Select the desired treatment plan item and click [Return].
  9. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  10. Click [Sign] for "Signature A" and enter the desired signature.
  11. Select "Final" in the 'Draft/Final' field.
  12. Click [Submit].
  13. Validate the 'Confirm Document' dialog is displayed with "Crystal Report A". Validate the signature and treatment plan grid data display as expected.
  14. Leave the form open.
  15. Access Crystal Reports or other SQL Reporting Tool.
  16. Create a report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  17. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  18. Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  19. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  20. Navigate back to the 'Ambulatory Progress Notes' form.
  21. Click [Accept].
  22. Enter the password associated to the logged in user.
  23. Close the form.
  24. Access Crystal Reports or other SQL Reporting Tool.
  25. Refresh the report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  26. Validate a row is no longer displayed for the treatment plan data entered for "Client A" in the previous steps.
  27. Refresh the report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  28. Validate a row is no longer displayed for the signature data entered for "Client A" in the previous steps.
  29. Select "Client A" and access the 'Progress Notes' widget.
  30. Validate the progress note filed in the previous steps is displayed with the treatment plan and signature data.
  31. Access Crystal Reports or other SQL Reporting Tool.
  32. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  33. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  34. Close the report.
  35. Create a report using the 'SYSTEM.cw_tx_pn_sign_data' SQL table.
  36. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  37. Close the report.
Scenario 3: Inpatient Progress Notes - Validate 'Treatment Plan' Grid and 'Signature' fields
Specific Setup:
  • Signature support must be enabled in the 'System Security Defaults' form.
  • The 'Progress Notes' widget is accessible on the HomeView.
  • The 'Enable Treatment Plan Grid' registry setting is set to "Y" for the 'Inpatient Progress Notes' form.
  • A copy of the 'Inpatient Progress Notes' form must be defined and have a signature field added via 'Site Specific Section Modeling' (Signature A).
  • A client must be enrolled in an inpatient episode and have a Treatment Plan filed with a problem, goal, objective, and intervention associated (Client A).
  • Must have a crystal report configured for document routing configured for "Signature A" and the 'Treatment Plan' grid for Inpatient progress notes (Crystal Report A).
  • Crystal Report Document Routing must be configured for the 'Inpatient Progress Notes' form using "Crystal Report A".
Steps
  1. Select "Client A" and access the 'Inpatient Progress Notes' form.
  2. Select "Independent Note" in the 'Progress Note For' field.
  3. Select the desired value in the 'Note Type' field.
  4. Enter the desired value in the 'Notes Field'.
  5. Click [New Row] in the 'Treatment Plan Grid'.
  6. Select "Treatment Plan" in the 'Select T.P. Version' field.
  7. Click [View].
  8. Select the desired treatment plan item and click [Return].
  9. Enter the desired value in the 'T.P. Item Notes/Documentations' field.
  10. Click [Sign] for "Signature A" and enter the desired signature.
  11. Select "Final" in the 'Draft/Final' field.
  12. Click [File Note].
  13. Validate the 'Confirm Document' dialog is displayed with "Crystal Report A". Validate the signature and treatment plan grid data display as expected.
  14. Leave the form open.
  15. Access Crystal Reports or other SQL Reporting Tool.
  16. Create a report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  17. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  18. Create a report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  19. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  20. Navigate back to the 'Inpatient Progress Notes' form.
  21. Click [Accept].
  22. Enter the password associated to the logged in user.
  23. Close the form.
  24. Access Crystal Reports or other SQL Reporting Tool.
  25. Refresh the report using the 'CWSTEMP.cw_patient_notes_tpnotes' SQL table.
  26. Validate a row is no longer displayed for the treatment plan data entered for "Client A" in the previous steps.
  27. Refresh the report using the 'CWSTEMP.cw_tx_pn_sign_data' SQL table.
  28. Validate a row is no longer displayed for the signature data entered for "Client A" in the previous steps.
  29. Select "Client A" and access the 'Progress Notes' widget.
  30. Validate the progress note filed in the previous steps is displayed with the treatment plan and signature data.
  31. Access Crystal Reports or other SQL Reporting Tool.
  32. Create a report using the 'SYSTEM.cw_patient_notes_tpnotes' SQL table.
  33. Validate a row is displayed for the treatment plan data entered for "Client A" in the previous steps.
  34. Close the report.
  35. Create a report using the 'SYSTEM.cw_tx_pn_sign_data' SQL table.
  36. Validate a row is displayed for the signature data entered for "Client A" in the previous steps.
  37. Close the report.
Topics
• Document Routing • Progress Notes • Query/Reporting
2023 Update 98 Summary | Details
OE NX - 'Task Shift' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Task Shift
Scenario 1: OE NX - 'Task Shift' form shift time calculation
Steps
  1. Access the 'Task Shift' form.
  2. Select "Add" in the 'Add/Edit Shift Definition' field.
  3. Set the 'New Shift Code' field to any value.
  4. Set the 'Shift Description' field to any value.
  5. Set the 'Shift 1 Start Time' field to any value where minutes are not equal to 00. (ex. 0730)
  6. Set the 'Shift 2 Start Time' field to any value where minutes are not equal to 00. (ex. 1530)
  7. Set the 'Shift 3 Start Time' field to any value where minutes are not equal to 00. (ex. 2330)
  8. Validate the 'Shift 1 End Time' field contains a time that is one minute prior than the value in the 'Shift 2 Start Time' field.
  9. Validate the 'Shift 2 End Time' field contains a time that is one minute prior than the value in the 'Shift 3 Start Time' field.
  10. Validate the 'Shift 3 End Time' field contains a time that is one minute prior than the value in the 'Shift 1 Start Time' field.
  11. Click [Submit].
  12. Validate a message is displayed stating: "Task Shift has completed. Do you wish to return to form?" and click [No].
Topics
• Task Shift
 

Avatar_CWS_2024_Monthly_Release_2024.01.02_Details.csv