Skip to main content

RADplus 2024 Monthly Release 2024.00.01 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 2 Summary | Details
Client list is not displaying in Vitals iOS application
Scenario 1: Validate 'Vitals' app caseload
Steps
  1. Admit client to inpatient program. Do not add Admitting or Attending Practitioner as yourself.
  2. Navigate to Vitals app and Confirm Client is not on your caseload.
  3. Navigate to 'Attending Practitioner' form and make yourself the attending practitioner.
  4. Confirm the client is displayed in Vitals App.
  5. Using 'Attending Practitioner' Form, remove yourself as attending practitioner.
  6. Confirm patient is not displayed in Vitals app.
  7. Navigate to 'Admission' and edit the admission.
  8. Confirm the attending practitioner is showing the practitioner that you just changed.
  9. You are not able to change the attending but you can change the admitting. Change the admitting practitioner to yourself.
  10. Confirm the patient now displays in the Vitals app.
  11. Go back to 'Admission' and edit the admission.
  12. Change the 'Admitting practitioner' to the other practitioner and submit.
  13. Confirm patient is not displayed in Vitals app.
  14. Log out and log back in and confirm the patient is not displayed in your caseload in Vitals.
  15. Transfer patient from other provider to yourself via 'Transfer practitioner' caseload.
  16. Select 'Attending practitioner' caseload first.
  17. Confirm patient displays in Vitals app.
  18. Transfer patient from yourself to the other provider via 'Transfer practitioner' caseload.
  19. Select 'Attending practitioner' caseload.
  20. Confirm patient is not displayed in Vitals app.
  21. Transfer patient from other provider to yourself via 'Transfer practitioner' caseload.
  22. Select 'Admitting practitioner' caseload.
  23. Confirm patient displays in Vitals app.
  24. Transfer patient from yourself to the other provider via 'Transfer practitioner' caseload.
  25. Select 'Admitting practitioner' caseload.
  26. Confirm patient is not displayed in Vitals app.
  27. Add patient to your caseload via 'Nursing caseload' assignment.
  28. Confirm patient displays in Vitals app.
  29. Deselect patient in 'Nursing caseload' assignment.
  30. Confirm patient is not displayed in Vitals app.
  31. Add patient to caseload using 'Manage nursing' caseload.
  32. Confirm patient displays in Vitals app.
  33. Remove patient from caseload using 'Manage nursing' caseload.
  34. Confirm patient is not displayed in Vitals app.
  35. Add patient to 'Manage observer' caseload.
  36. Confirm patient displays in observer app.
  37. Confirm patient displays in vitals app.
  38. Remove patient in 'Manage observer' caseload.
  39. Confirm patient is not displayed in Observer app.
  40. Confirm patient is not displayed in Vitals app.
Topics
• Medication Vital
Update 5 Summary | Details
Document Management Definition - Perceptive document synchronization
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Management Definition
  • Client Document Capture
  • Clinical Document Viewer
  • Document Capture
Scenario 1: Validate form "Document Management Definition"
Steps
  1. Open "Document Management Definition" form.
  2. Click [Select Form].
  3. Click [Add New].
  4. Populate the "Form Name" field.
  5. Select the desired form type in the "Form Type" field.
  6. Select the desired entity in the "Entity" field.
  7. Populate any other desired fields in the "Form" section.
  8. Click the [Categories] section.
  9. Click [Select Categories].
  10. Select the desired category from the selection list.
  11. Click [OK].
  12. Click the [Display] section.
  13. Select the desired selections form the "Forms to Display" box.
  14. Click the [Reports] section.
  15. Click any to launch any desired report, for example the "Display Form Report".
  16. Validate the "Document Management Form Report" is displayed.
  17. Close the report.
  18. Click back to the [Form] section.
  19. Click [File].
  20. Validate the form files successfully.
  21. Click [Select Form].
  22. Select the form just submitted in step 5.
  23. Validate all fields populated in steps 1 thru 5, are populated as expected.
  24. Click back to the [Form] section.
  25. Click [Delete].
  26. Click [Yes] to accept the deletion.
  27. Click [Select Form].
  28. Validate the form that was deleted in step 7, is no longer present in the list.
  29. Click [Select Form].
  30. Select the form "Inbox Attachments".
  31. Click [Delete]
  32. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed".
  33. Click [OK].
  34. Click [Select Form].
  35. Select the form "Results Document".
  36. Click [Delete].
  37. Validate message "This form is attached to Perceptive functionality text contains "This form is attached to Perceptive functionality that is required by other parts of the system, deleting is not allowed".
  38. Click [OK].
  39. Close the form.
Scenario 2: Client Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • A client must be enrolled in an existing episode (Client A).
  • A document must exist for import.
Steps
  1. Access the 'Client Document Capture' form.
  2. Enter "Client A" in the 'Client ID' field.
  3. Select any episode for the 'Episode Number' field.
  4. Click [Launch POS Capture].
  5. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  6. Click [Import].
  7. Validate the 'Document Capture' opens in a new window.
  8. Select any value in the 'Document Type' field.
  9. Enter any value in the 'Document Description' field.
  10. Click [Capture] and [Browse].
  11. Locate the file to be imported and click [Open] and [Done].
  12. Validate the image displays.
  13. Click [Save].
  14. Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
  15. Close the form.
  16. Access the undocked 'Clinical Document Viewer' form.
  17. Validate the form opens in a new window.
  18. Select "Client" in the 'Select Type' field.
  19. Select "Individual" in the 'Select All or Individual Client' field.
  20. Enter "Client A" in the 'Select Client' field.
  21. Select the episode from the previous steps in the 'Episode' field.
  22. Click [Process].
  23. Locate and select the document that was saved in the previous steps.
  24. Validate the image displays.
  25. Click [Close All Documents], [Search] and [Close].
Topics
• Perceptive
Update 12 Summary | Details
'Clinical Document Viewer' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Clinical Document Viewer
Scenario 1: Clinical Document Viewer - View documents for "All" clients
Specific Setup:
  • The logged in user must be configured as a supervisor to a user with a high volume of client's in their caseload.
  • Must have a high volume of documents on file.
Steps
  1. Access the 'Clinical Document Viewer' form.
  2. Select "All" in the 'Select All or Individual Client' field.
  3. Click [Process].
  4. Validate the documents are displayed in a timely manner.
  5. Scroll to the desired document from the search results table.
  6. Select the desired document in the 'Search Results' field.
  7. Click to view the document.
  8. Validate document data is displayed as expected.
  9. Click [Close All Documents].
  10. Navigate back to the "Search" section.
  11. Click [Close].
Scenario 2: Clinical Document Viewer - View documents for an individual client
Specific Setup:
  • The logged in user must be configured as a supervisor for a user with a high volume of client's in their caseload.
  • A client must have a high volume of documents on file (Client A).
Steps
  1. Access the 'Clinical Document Viewer' form.
  2. Select "Individual" in the 'Select All or Individual Client' field.
  3. Select "Client A" in the 'Select Client' field.
  4. Select "All" in the 'Episode' field.
  5. Click [Process].
  6. Validate the documents are displayed in a timely manner.
  7. Select the desired document in the 'Search Results' field.
  8. Click to view the document.
  9. Validate document data is displayed.
  10. Click [Close All Documents].
  11. Navigate back to the "Search" section.
  12. Click [Close].
Topics
• Clinical Document Viewer
Update 17 Summary | Details
Support for Waiting Room functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Diagnosis
  • Spreadsheet Edit Service Information
  • Appointment Management
  • Client Ledger
  • Walk-in Clinic Registration/Waiting Room
  • Walk-in Clinic/Waiting Room
  • Financial Eligibility
Scenario 1: Waiting Room - Place Client in Context
Specific Setup:
  • Please note: this is for Avatar NX systems only. Avatar Appointment Scheduling 2023 Update 34, RADplus 2024 Update 17 and Avatar NX Release 2024.01.00 are required for full functionality.
  • The 'Enable Clinic Scheduling' registry setting must be set to "Y".
  • The 'Walk-in Clinic Registration/Waiting Room' widget must be accessible on the user's myDay view.
  • A site is defined with time slots for clinic hours in 'Site Registration' (Site A), (Time Slot A).
  • Two clients are enrolled in existing episodes (Client A & Client B).
Steps
  1. Navigate to the 'Walk-in Clinic Registration/Waiting Room' widget.
  2. Select "Site A" in the 'Waiting Room/Site' field.
  3. Select "Client A" in the 'Add Client' field.
  4. Validate the 'Select Episode' and 'Service Program' populate with the existing episode information.
  5. Populate any other desired fields.
  6. Click [Add To Waitlist].
  7. Validate a message is displayed stating: Saved.
  8. Click [OK].
  9. Validate "Client A" is displayed in the Waiting Room.
  10. Click on the name for "Client A".
  11. Validate "Client A" is now in context and selected in the 'My Clients' list.
  12. Access the 'Update Client Data' form.
  13. Validate the form is displayed for "Client A".
  14. Close the form and clear the client.
  15. Select "Client B" in the 'Add Client' field.
  16. Validate the 'Select Episode' and 'Service Program' populate with the existing episode information.
  17. Populate any other desired fields.
  18. Click [Add To Waitlist].
  19. Validate a message is displayed stating: Saved.
  20. Click [OK].
  21. Validate "Client B" is now displayed in the Waiting Room.
  22. Navigate to the Staff View 'Walk-in Clinic/Waiting Room' widget.
  23. Validate "Client A" and "Client B" are displayed.
  24. Click on the name for "Client B".
  25. Validate "Client B" is now in context and selected in the 'My Clients' list.
  26. Access the 'Update Client Data' form.
  27. Validate the form is displayed for "Client B".
  28. Close the form and clear the client.
Scenario 2: Waiting Room - Validate Client Information Flyover
Specific Setup:
  • Please note: this is for Avatar NX systems only. Avatar Appointment Scheduling 2023 Update 34, RADplus 2024 Update 17, Avatar NX Release 2024.01.00, and Avatar NX Release 2024.02.00 are required for full functionality.
  • The 'Enable Clinic Scheduling' registry setting must be set to "Y".
  • The 'Walk-in Clinic Registration/Waiting Room' widget must be accessible on the user's myDay view.
  • A site is defined with time slots for clinic hours in 'Site Registration' (Site A), (Time Slot A).
  • A client is enrolled in an existing episode and has the following on file (Client A):
  • Date Of Birth
  • Primary Diagnosis
  • Primary Guarantor
Steps
  1. Navigate to the 'Walk-in Clinic Registration/Waiting Room' widget.
  2. Select "Site A" in the 'Waiting Room Site' field.
  3. Select the desired value in the 'Time Slot' field.
  4. Select "Client A" in the 'Add Client' field.
  5. Validate the 'Select Episode' and 'Service Program' populate with the existing episode information.
  6. Click [Add to Waitlist] and [OK].
  7. Validate the client is added to the Waitlist.
  8. Hover over "Client A".
  9. Validate a client information flyover is displayed with the following:
  10. Name
  11. Date Of Birth
  12. Age
  13. Primary Diagnosis
  14. Primary Guarantor
  15. Click on "Client A".
  16. Validate the client information flyover is now locked into place.
  17. Click [X] to close the flyover.
  18. Select "Add to Calendar" in the 'Action' field for "Client A".
  19. Click [Yes].
  20. Validate the 'Scheduling Calendar - Appointment Details' form is displayed.
  21. Populate all required and desired fields for the appointment.
  22. Click [Submit].
  23. Validate the 'Walk-in Clinic Registration/Waiting Room' widget is displayed.
  24. Hover over "Client A".
  25. Validate a client information flyover is displayed with the following:
  26. Name
  27. Date Of Birth
  28. Age
  29. Primary Diagnosis
  30. Primary Guarantor
  31. Appointment Details
  32. Click on "Client A".
  33. Validate the client information flyover is now locked into place.
  34. Click [X] to close the flyover.
  35. Navigate to the Staff 'Walk-in Clinic/Waiting Room' widget.
  36. Validate "Client A" is displayed in the Waitlist.
  37. Hover over "Client A".
  38. Validate a client information flyover is displayed with the following:
  39. Name
  40. Date Of Birth
  41. Age
  42. Primary Diagnosis
  43. Primary Guarantor
  44. Appointment Details
  45. Click on "Client A".
  46. Validate the client information flyover is now locked into place.
  47. Click [X] to close the flyover.
Topics
• NX • Waiting Room
Update 19 Summary | Details
Delete Document - 'Display Document' button
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Delete Document
  • Clinical Document Viewer
  • Document Routing Setup (PM)
  • Site Specific Section Modeling (CWS)
  • Append Progress Notes
  • TO DO'S
  • DOCUMENTS TO REVIEW
Scenario 1: Validate the functionality of the form "Delete Document"
Specific Setup:
  • Have a client with any type document created for any episode. For example a "Document Routing" document.
Steps
  1. Open form "Delete Document":
  2. Select "Client" in the "Entity Type" field.
  3. Select "Individual" in the "Include" field.
  4. In the "Entity" field, select the client that has the document.
  5. Select the episode in the "Episode" field.
  6. Click [Form Search].
  7. Select the form name in the "Select a Form" screen.
  8. Click [OK].
  9. Click the "Select Form" drop down list.
  10. Select the row pertaining to the clients document.
  11. Click [Delete].
  12. Click [Yes], confirming the deletion.
  13. Open form "Clinical Document Viewer":
  14. Select "Individual" from the "Select All or Individual Client" field,
  15. In the "Select Client" field, select a client that had the document,
  16. Select the episode in the "Episode" field,
  17. Click [Process],
  18. Validate the row with the document that was deleted, is not present.
  19. Open the form originally used to create the deleted document:
  20. Select the row originally used to submit the document,
  21. Validate the row has been reverted to "Draft" status.
Scenario 2: Delete Document - Validate form functionality
Specific Setup:
  • Have a client with any type document created for any episode. For example a "Document Routing" document (Client A).
Steps
  1. Access the 'Delete Document' form.
  2. Select "Client" in the 'Entity Type' field.
  3. Select "Individual" in the 'Include' field.
  4. Select "Client A" in the 'Entity' field.
  5. Select the episode in the "Episode" field.
  6. Click [Form Search].
  7. Select the form name in the "Select a Form" screen.
  8. Click [OK].
  9. Select the desired form in the 'Select Form' field.
  10. Validate the 'Display Document' button is displayed.
  11. Click [Display Document].
  12. Validate the document displays as expected.
  13. Click [Close All Documents and Exit].
  14. Click [Delete].
  15. Click [Yes], confirming the deletion.
  16. Access the 'Clinical Document Viewer' form.
  17. Select "Individual" in the 'Select All or Individual Client' field,
  18. Select "Client A" in the 'Select Client' field.
  19. Select the episode in the 'Episode' field.
  20. Click [Process].
  21. Validate the deleted document is not present.
  22. Close the form.
Scenario 3: Delete Document - User with access to confidential notes
Specific Setup:
  • The 'RADplus->System Security->User Definition->->->Enable View Confidential Notes' registry setting is set to "Y".
  • The following must be configured for the 'Progress Notes (Group and Individual)' form:
  • In 'Site Specific Section Modeling' - A single select dictionary with "Confidential Notes Logic" selected in the 'Product Custom Logic Definition' field. This field will be named 'Is this a confidential note?'.
  • Yes/No dictionary values should also be configured for this field which can be done in 'Dictionary Update'.
  • Document routing is enabled in 'Document Routing Setup'.
  • The logged in user has access to confidential notes in 'User Definition' (User A).
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the Progress Notes (Groups and Individual)' 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' field.
  5. Select "Yes" in the 'Is this a confidential note?' field.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [Submit].
  8. Validate a 'Confirm Document' dialog is displayed.
  9. Click [Accept].
  10. Enter the password associated to the logged in user and click [Verify].
  11. Access 'Delete Document' form.
  12. Select "Client" in the 'Entity Type' field.
  13. Select "Individual" in the 'Include' field.
  14. Select "Client A" in the 'Entity Search' field.
  15. Select the desired episode in the 'Episode' field.
  16. Click [Form Search].
  17. Select the corresponding form type and click [OK].
  18. Select the record filed in the previous steps in the 'Select Form' field.
  19. Click [Display Document].
  20. Validate the document details are displayed. User can select/view the document since they have access to confidential notes.
  21. Click [Close All Documents] and [Delete].
  22. Validate a message is displayed stating: Are you sure you want to delete this document?
  23. Click [Yes].
  24. Select "Client" in the 'Entity Type' field.
  25. Select "Individual" in the 'Include' field.
  26. Select "Client A" in the 'Entity Search' field.
  27. Select the desired episode in the 'Episode' field.
  28. Click [Form Search].
  29. Select the corresponding form type and click [OK].
  30. Validate the deleted record is no longer displayed.
  31. Close the form.
Scenario 4: Delete Document - User without access to confidential notes
Specific Setup:
  • The 'RADplus->System Security->User Definition->->->Enable View Confidential Notes' registry setting is set to "Y".
  • The following must be configured for the 'Progress Notes (Group and Individual)' form:
  • In 'Site Specific Section Modeling' - A single select dictionary with "Confidential Notes Logic" selected in the 'Product Custom Logic Definition' field. This field will be named 'Is this a confidential note?'.
  • Yes/No dictionary values should also be configured for this field which can be done in 'Dictionary Update'.
  • Document routing is enabled in 'Document Routing Setup'.
  • The logged in user has access to confidential notes in 'User Definition' (User A).
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the Progress Notes (Groups and Individual)' 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' field.
  5. Select "Yes" in the 'Is this a confidential note?' field.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [Submit].
  8. Validate a 'Confirm Document' dialog is displayed.
  9. Click [Accept].
  10. Enter the password associated to the logged in user and click [Verify].
  11. Access the 'User Definition' form.
  12. Select "User A" in the 'Select User' field.
  13. Select the "Forms and Tables" section.
  14. Select "No" in the 'Allow User to View Confidential Notes' field.
  15. Submit the form.
  16. Access 'Delete Document' form.
  17. Select "Client" in the 'Entity Type' field.
  18. Select "Individual" in the 'Include' field.
  19. Select "Client A" in the 'Entity Search' field.
  20. Select the desired episode in the 'Episode' field.
  21. Click [Form Search].
  22. Select the corresponding form type and click [OK].
  23. Validate the document is not displayed since the user does not have access to confidential notes.
  24. Close the form.
Topics
• Documentation • Clinical Document Viewer • Delete Document
Update 20 Summary | Details
'Change User Role ID' Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Change User Role ID
  • User Role Definition
  • Dynamic Form - User Role Definition - Select User Role
Scenario 1: Change User Role ID
Specific Setup:
  • A user role is defined in 'User Role Definition' (User Role A).
  • This user role must be associated to a template in the 'Product Scrolling Free Text Templates' form.
Steps
  1. Access the 'Change User Role ID' form.
  2. Select "ROLETEST" in the 'User Role' field.
  3. Validate the 'Current User Role ID' field contains "ROLETEST".
  4. Enter "ROLETEST1" in the 'New User Role ID' field.
  5. Click [Submit].
  6. Validate a message is displayed stating "Change User Role ID has completed. Do you wish to return to form?"
  7. Click [No].
  8. Access the 'Change User Role ID' form.
  9. Select "ROLETEST1" in the 'User Role' field.
  10. Validate the 'Current User Role ID' field contains "ROLETEST1".
  11. Enter "roletest1" in the 'New User Role ID' field.
  12. Click [Submit].
  13. Validate a message is displayed stating "Change User Role ID has completed. Do you wish to return to form?"
  14. Click [No].
  15. Access the 'Change User Role ID' form.
  16. Select "roletest1" in the 'User Role' field.
  17. Validate the 'Current User Role ID' field contains "roletest1".
  18. Close the form.
Topics
• Change User Role Id • User Role Definition
Update 26 Summary | Details
Client Lookup/Header Configuration Manager - Client Header
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Lookup/Header Configuration Manager
Scenario 1: 'Client Lookup/Header Configuration Manager' - Validate Header Information
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • "Client A" has emergency contact information on file.
  • The 'Client Information' widget must be accessible on the HomeView.
Steps
  1. Access the 'Client Lookup/Header Configuration Manager' form.
  2. Select the "Client Header" section.
  3. Click [Add New Item].
  4. Select "Clinical Pathway" in the 'Field to Include in Client Header' field.
  5. Select "Column 2, Position 4" in the 'Field Order' field.
  6. Click [Add New Item].
  7. Select "Emergency Contact Name" in the 'Field to Include in Client Header' field.
  8. Select "Column 3, Position 4" in the 'Field Order' field.
  9. Click [Add New Item].
  10. Select "Emergency Contact Phone" in the 'Field to Include in Client Header' field.
  11. Select "Column 3, Position 5" in the 'Field Order' field.
  12. Click [Submit].
  13. Select "Client A" and navigate to the 'Client Information' header.
  14. Validate the 'Client Information' header is displayed with any applicable details for "Client A".
  15. Validate the 'Emergency Contact' and 'Phone' fields are displayed in the third column, positions 4 and 5, as expected.
  16. Validate all other fields are displayed in their configured column/positions.
Client Header - Problems
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • System Code Definition
  • Dictionary Update (CWS)
Scenario 1: Problem List - validate Problem Classification sub-system code restrictions
Specific Setup:
  • A client is admitted into two episodes (Client A):
  • Episode 1 = Program A
  • Episode 2 = Program B
  • Two sub-system codes are defined in the 'System Code Definition' form:
  • "System Code A" has "Program A" selected in 'Associated Programs'.
  • "System Code B" has "Program B" selected in 'Associated Programs'.
  • Two problem classifications are defined for the '(16250) Problem Classification' CWS dictionary:
  • "Classification A" has both the root system code being used & "System Code A" selected in the 'Restricted Sub-system Codes' extended dictionary.
  • "Classification B" has both the root system code being used & "System Code B" selected in the 'Restricted Sub-system Codes' extended dictionary.
  • The 'Client Information' widget is accessible on the HomeView.
Steps
  1. Select "Client A" and access the 'Problem List' form.
  2. Click [View/Enter Problems].
  3. Validate the 'Problem List' grid is displayed.
  4. Click [New Row].
  5. Add a new problem. This will be referred to as "Problem A".
  6. Select "Classification A" in the 'Problem Classification' field.
  7. Select "Primary" in the 'Type' field.
  8. Select "Active" in the 'Status' field.
  9. Click [New Row].
  10. Add a new problem. This will be referred to as "Problem B".
  11. Select "Classification B" in the 'Problem Classification' field.
  12. Select "Primary" in the 'Type' field.
  13. Select "Active" in the 'Status' field.
  14. Click [Save], [Yes] and [Submit].
  15. Log out.
  16. Login using "System Code A".
  17. Select "Client A" and access the 'Problem List' form.
  18. Click [View/Enter Problems].
  19. Validate only "Problem A" is displayed.
  20. Click [Close/Cancel] and close the form.
  21. Select "Client A" and navigate to the 'Client Information' widget.
  22. Validate "Problem A" is displayed in the 'Problem' section.
  23. Log out.
  24. Login using "System Code B".
  25. Select "Client A" and access the 'Problem List' form.
  26. Click [View/Enter Problems].
  27. Validate only "Problem B" is displayed.
  28. Click [Close/Cancel] and close the form.
  29. Select "Client A" and navigate to the 'Client Information' widget.
  30. Validate "Problem B" is displayed in the 'Problem' section.
Topics
• Client Header • Sub-System Code • Problem List
2023 Update 105 Summary | Details
Program/User Defined – Program Maintenance Entities
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Delete Document
  • Clinical Document Viewer
  • Entity-Based Document Capture
  • Table Definition (PM)
  • Document Routing Setup (PM)
  • Document Management Definition
  • Program User Defined Program Maintenance
  • Document Capture
Scenario 1: Validate the functionality of the form "Delete Document"
Specific Setup:
  • Have a client with any type document created for any episode. For example a "Document Routing" document.
Steps
  1. Open form "Delete Document":
  2. Select "Client" in the "Entity Type" field.
  3. Select "Individual" in the "Include" field.
  4. In the "Entity" field, select the client that has the document.
  5. Select the episode in the "Episode" field.
  6. Click [Form Search].
  7. Select the form name in the "Select a Form" screen.
  8. Click [OK].
  9. Click the "Select Form" drop down list.
  10. Select the row pertaining to the clients document.
  11. Click [Delete].
  12. Click [Yes], confirming the deletion.
  13. Open form "Clinical Document Viewer":
  14. Select "Individual" from the "Select All or Individual Client" field,
  15. In the "Select Client" field, select a client that had the document,
  16. Select the episode in the "Episode" field,
  17. Click [Process],
  18. Validate the row with the document that was deleted, is not present.
  19. Open the form originally used to create the deleted document:
  20. Select the row originally used to submit the document,
  21. Validate the row has been reverted to "Draft" status.
Scenario 2: Entity-Based Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • In the "Document Management Defaults" form, select "Program" in the "Select Entity Types to Allow" field.
  • Select a performing provider and a program for the tests.
Steps
  1. Access the 'Entity-Based Document Capture' form.
  2. Select "Performing Provider" in the 'Entity Type' field.
  3. Enter the desired performing provider in the 'Entity' field in the format of "LAST,FIRST".
  4. Validate the 'Results' field displays the performing provider and select it.
  5. Click [Launch POS Capture].
  6. Import in a document saved as a file on the server.
  7. Validate the document renders on screen.
  8. Select the desired value in the 'Document Type' field.
  9. Enter the desired value in the 'Document Description' field.
  10. Click [Save].
  11. Validate that messages display indicating the document was successfully saved.
  12. Close the form.
  13. Access the 'Clinical Document Viewer' form.
  14. Select "Performing Provider" in the 'Entity' field.
  15. Select "Individual" in the 'Select All or Individual Performing Provider' field.
  16. Select the performing provider from the previous steps in the 'Select Performing Provider' field.
  17. Click [Process].
  18. Validate a row was added for the document that was just saved.
  19. View the document to validate it displays as it was captured.
  20. Close the form.
  21. Access the 'Entity-Based Document Capture' form.
  22. Select "Program" in the 'Entity Type' field.
  23. Enter the desired program in the 'Entity' field.
  24. Validate the 'Results' field displays the program and select it.
  25. Click [Launch POS Capture].
  26. Import in a document saved as a file on the server.
  27. Validate the document renders on screen.
  28. Select the desired value in the 'Document Type' field.
  29. Enter the desired value in the 'Document Description' field.
  30. Click [Save].
  31. Validate that messages display indicating the document was successfully saved.
  32. Close the form.
  33. Access the 'Clinical Document Viewer' form.
  34. Select "Program" in the 'Entity' field.
  35. Select "Individual" in the 'Select All or Individual Performing Program' field.
  36. Select the program from the previous steps.
  37. Click [Process].
  38. Validate a row was added for the document that was just saved.
  39. View the document to validate it displays as it was captured.
  40. Close the form.
Scenario 3: Program User Defined Program Maintenance entity - Create Modeled Form
Specific Setup:
  • Create a user modeled form for the "Program User Defined Program Maintenance" entity.
  • Using "Envelope Definition", create a new envelope for the user modeled form.
  • Using "Table Definition", create a table that also includes a "Draft/Final (Document Routing)" field.
  • Using "Form Definition", define the user modeled form.
  • Refresh menus.
  • Using "Document Routing Setup", enable document routing for the user modeled form.
  • Using "Document Management Definition", create a new form for the "Program User Defined Program Maintenance".
Steps
  1. Open the user modeled form created for this test.
  2. Populate the form and mark the "Draft/Final" as "Draft".
  3. Route the document to an approver.
  4. Log in as the approver.
  5. Navigate to the "ToDo" widget.
  6. Approve the document.
  7. Open "Clinical Document Viewer".
  8. Locate the document that was just finalized.
  9. View the document and validate it displays as it was stored.
  10. Print the document and validate it prints as it displays.
Scenario 4: Program Entity - Validation
Specific Setup:
  • Using the "Document Management Defaults" form, select "Program" in the "Select Entity Types Allowed" field.
  • Using the "Document Management Definition" form, add a new form for the "Program" entity.
Steps
  1. Open the "Entity-Based Document Capture" form.
  2. Scan a document and set the "Document Type" to "Program".
  3. Save the document.
  4. Import a document and set the "Document Type" to "Program".
  5. Open the "Clinical Document Viewer" form.
  6. Set "Select Type" to "Program".
  7. Elect "All" or "Individual" programs.
  8. Locate the documents that were just scanned/imported.
  9. Validate the document displays.
  10. Validate the document prints.
Scenario 5: Program User Defined Program Maintenance Entity - Validation
Specific Setup:
  • Using "Document Management Defaults", define "Program - User Defined Program Maintenance" and "Program" entity types.
  • Using "Document Management Definition", define forms for the "Program" entity and "Program User Defined Program Maintenance" entities.
  • Create a user modeled form for the "Program User Defined Program Maintenance" entity.
  • Using "Envelope Definition", create a new envelope for the user modeled form.
  • Using "Table Definition", create a table that also includes a "Draft/Final (Document Routing)" field.
  • Using "Form Definition", define the user modeled form.
  • Refresh menus.
  • Using "Document Routing Setup", enable document routing for the user modeled form.
Steps
  1. Open the user modeled form created for this test.
  2. Populate the form and mark the "Draft/Final" as "Draft".
  3. Route the document to an approver.
  4. Log in as the approver.
  5. Navigate to the "ToDo" widget.
  6. Approve the document.
  7. Open "Clinical Document Viewer".
  8. Locate the document that was just finalized.
  9. View the document and validate it displays as it was stored.
  10. Print the document and validate it prints as it displays.
Scenario 6: Clinical Document Viewer - "Void & Copy" documents
Specific Setup:
  • Perceptive is enabled.
  • In "User Definition", validate user has permissions to void documents.
  • The entity being tested must have imported or scanned documents on file.
Steps
  1. Access the 'Clinical Document Viewer' form.
  2. Select the desired entity in the "Entity Type field".
  3. Select "Individual" in the 'Select All or Individual' entity field.
  4. Select the desired entity (Client ID, Staff ID, Family ID, etc).
  5. Click [Process].
  6. Select a document and view it.
  7. Click [Void] and then [Void & Copy].
  8. Validate 'Form Type' & 'Change Description' displays as expected for the selected document.
  9. Select a target entity to copy the document to.
  10. If the entity is a client, select the desired episode in the 'Select Episode' field.
  11. Click [Void].
  12. Validate the document list now has a Status of "Void" for the original document.
  13. Select the "Search" section.
  14. Select the target entity.
  15. Click [Process].
  16. Validate the copied document is now in the document list for this entity.
  17. View the copied document and validate it displays as expected.
  18. Click [Void] and then [Void & Copy].
  19. Validate 'Form Type' & 'Change Description' displays as expected for the selected document.
  20. Click [Cancel Void].
  21. Click [Close All Documents].
  22. Select the "Search" section.
  23. Click [Close].
Scenario 7: Clinical Document Viewer - "Void" documents
Specific Setup:
  • Perceptive is enabled.
  • User has permissions to void documents.
  • A client must have non-routed documents on file in the 'Clinical Document Viewer' (Client A).
  • A Documentation View must be set up on a user's view containing the 'All Documents' widget and the 'Console Widget Viewer'.
Steps
  1. Access the 'Clinical Document Viewer' form.
  2. Select "Individual" in the 'Select All or Individual Client' field.
  3. Select "Client A" in the 'Select Client' field.
  4. Click [Process].
  5. Select any non-routed document and view it.
  6. Click [Void] and [Void] again.
  7. Select the desired value in the 'Void Reason' field.
  8. Enter the desired value in the 'Void Comments' field.
  9. Click [Void] and [Close All Documents].
  10. Select the "Search" section.
  11. Click [Close].
  12. Select "Client A" and navigate to the 'All Documents' view.
  13. Validate the documents is present in the 'All Documents' widget with a 'Document Status' of "Void".
  14. Select the document.
  15. Validate the document displays with "Voided" in the 'Console Widget Viewer'.
Perceptive - Document Viewing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Capture
  • Client Document Capture
  • Clinical Document Viewer
Scenario 1: Validate Document Capture - Import Episodic
Specific Setup:
  • Perceptive must be installed and enabled.
Steps
  1. Select a client from "myClients" or from the Client search.
  2. Open the client's dashboard.
  3. Using "Document Capture", scan or import in a document.
  4. Select the desired episode to assign the document to.
  5. Validate the correct Episode displays in the "Document Properties" pane.
  6. Capture and save the document.
  7. View the document using "Clinical Document Viewer" or the Chart to ensure it has the correct episode designation and that it displays.
Scenario 2: Client Chart - Document Capture - Import Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Import a document and select an episode.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was imported.
  11. Print the document and validate it prints as it was imported.
  12. Close the forms.
Scenario 3: Client Document Capture - Validation
Specific Setup:
  • Perceptive storage method must be utilized.
  • A client must be enrolled in an existing episode (Client A).
  • A document must exist for import.
Steps
  1. Access the 'Client Document Capture' form.
  2. Enter "Client A" in the 'Client ID' field.
  3. Select any episode for the 'Episode Number' field.
  4. Click [Launch POS Capture].
  5. Validate a 'Capture Mode' dialog stating: "How would you like to capture documents?"
  6. Click [Import].
  7. Validate the 'Document Capture' opens in a new window.
  8. Select any value in the 'Document Type' field.
  9. Enter any value in the 'Document Description' field.
  10. Click [Capture] and [Browse].
  11. Locate the file to be imported and click [Open] and [Done].
  12. Validate the image displays.
  13. Click [Save].
  14. Validate a message stating: "Save Was Successful." and "Document Added to Avatar!"
  15. Close the form.
  16. Access the undocked 'Clinical Document Viewer' form.
  17. Validate the form opens in a new window.
  18. Select "Client" in the 'Select Type' field.
  19. Select "Individual" in the 'Select All or Individual Client' field.
  20. Enter "Client A" in the 'Select Client' field.
  21. Select the episode from the previous steps in the 'Episode' field.
  22. Click [Process].
  23. Locate and select the document that was saved in the previous steps.
  24. Validate the image displays.
  25. Click [Close All Documents], [Search] and [Close].
Scenario 4: Chart Review - Document Capture - Scan Non-episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Scan a document and identify it was non-episodic.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was scanned.
  11. Print the document and validate it prints as it was scanned.
  12. Close the forms.
Scenario 5: Chart Review - Document Capture - Scan Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Scan a document and identify an episode.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was scanned.
  11. Print the document and validate it prints as it was scanned.
  12. Close the forms.
Scenario 6: Client Document Capture - Scan Episodic
Specific Setup:
  • Perceptive must be configured and enabled.
Steps
  1. Open the "Chart Review" form.
  2. Select the desired client.
  3. Navigate to the "Chart".
  4. Click "Document Capture".
  5. Scan a document and identify an episode.
  6. Note the document type.
  7. Save the document.
  8. Click the document type the document was just saved under.
  9. Locate the document that was just saved.
  10. Validate the document displays as it was scanned.
  11. Print the document and validate it prints as it was scanned.
  12. Close the forms.
Document Routing - Saving documents
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Document Routing Setup (PM)
  • Results Importing
  • View Results
Scenario 1: Progress Notes (Group and Individual) - Document Routing with Crystal Report Template
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • Document routing must be enabled for the 'Progress Notes (Group and Individual)' form with the following:
  • "Yes" selected in the 'Use Crystal Report Template' field.
  • A crystal report template selected in the 'Crystal Report' field.
  • User must have the 'My To Do's' widget and 'All Documents' widget accessible on their home view.
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 "New Service" in the 'Progress Note For' field.
  5. Populate all other required and desired fields.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [Submit Note].
  8. Validate the "Confirm Document" dialog is displayed with the crystal report template.
  9. Click [Sign and Route].
  10. Select the practitioner associated to the logged in user in the 'Supervisor' field.
  11. Click [Submit].
  12. Enter the password associated to the logged in user and click [Verify].
  13. Validate a message is displayed stating: Note Filed.
  14. Click [OK] and close the form.
  15. Navigate to the 'My To Do's' widget.
  16. Click [Documents To Sign].
  17. Validate a To-Do is displayed for the progress note filed in the previous steps.
  18. Click [Review].
  19. Validate the 'Document Preview' displays the crystal report template.
  20. Click [Accept] and [Sign].
  21. Enter the password associated to the logged in user and click [Verify].
  22. Validate the To-Do is no longer displayed.
  23. Click [Close].
  24. Select "Client A" and navigate to the 'All Documents'' widget.
  25. Click [Refresh].
  26. Validate the progress note is displayed and select it.
  27. Validate the 'Console Widget Viewer' displays the crystal report template.
  28. Click [Close All].
Scenario 2: Import Lab Result
Specific Setup:
  • A Results file for importing must be obtained/created for use in testing.
  • This results file should have a facility that matches the facility in the MSH segment.
  • This results file should have a client ID in the PID segment that matches up to a client in the system the test is to be performed in.
  • This results file should be in a .txt format.
  • Place this file on the cache server and note the path name where it's stored.
Steps
  1. Using the "Results Importing" form
  2. Import the file designated in setup by setting "File Path For Import" to the file path name.
  3. Open the "View Results" form.
  4. Validate you can view the result that was just imported.
Topics
• Documentation • Perceptive • Document Capture • Document Routing • Program • Clinical Document Viewer • NX • Results
2023 Update 109 Summary | Details
Entity Information Display - 'Approximate Number of Characters to Display' fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Entity Information Display
Scenario 1: Entity Information Display
Specific Setup:
  • The user must have access to the 'Entity Information Display' form.
Steps
  1. Access the 'Entity Information Display' form.
  2. Select "Client" from the 'Entity Database' field.
  3. Select "Three" from the 'Number of Additional Columns to Display' field.
  4. Enter the desired value in the 'Entity Name Header Text' field.
  5. Validate the 'Approximate Number of Characters to Display for Entity Name' field does not accept more than two digits.
  6. Enter the desired value in the 'Approximate Number of Characters to Display for Entity Name' field.
  7. Select the desired value form the 'Entity Information Display Column 1' field.
  8. Validate the 'Entity Information Display Column 1 Header Name' field populates and displays as expected.
  9. Validate the 'Approximate Number of Characters to Display for Entity Lookup Column 1' field does not accept more than two digits.
  10. Enter the desired value in the 'Approximate Number of Characters to Display for Entity Lookup Column 1' field.
  11. Select the desired value from the 'Entity Information Display Column 2' field.
  12. Validate the 'Entity Information Display Column 2 Header Name' field populates and displays as expected.
  13. Validate the 'Approximate Number of Characters to Display for Entity Lookup Column 2' field does not accept more than two digits.
  14. Enter the desired value in the 'Approximate Number of Characters to Display for Entity Lookup Column 2' field.
  15. Select the desired value from the 'Entity Information Display Column 3' field.
  16. Validate the 'Entity Information Display Column 3 Header Name' field populates and displays as expected.
  17. Validate the 'Approximate Number of Characters to Display for Entity Lookup Column 3' field does not accept more than two digits.
  18. Enter the desired value in the 'Approximate Number of Characters to Display for Entity Lookup Column 3' field.
  19. Click [Submit].
Topics
• Entity Information Display • NX
2023 Update 118 Summary | Details
'Change User ID' form
Scenario 1: "Change User ID" - Validate reverting a UserID to its previous Value
Specific Setup:
  • [ChangedUserB] is a user whose UserID had been changed from [ChangedUserA], via the "Change User ID" form
  • Have a form, for example, a user based product or modeled form [TestForm] that enabled for document routing. For this test product, form "Ambulatory Progress Notes" is used
  • [ChangedUserB] has been routed a "To Do" document for client [TestClient] via form [TestForm] and has approved it, to create the document [TestDoc]
  • [ChangedUserB] has been routed another "To Do" document that is still in their "To Do" list
  • Have a report or query to display data in the "SYSTEM.Doc_documents" table and include the "data_entry_user_id" field [ReportA]
  • Have a report or query to display data in the table used in [TestForm] and include the "data_entry_user_id" field. For this test, the "SYSTEM.cw_patient_notes" table is used [ReportB]
  • A test [TestUser] and [ChangedUserB] have access to forms "Change UserID", "User Definition"
  • Log in as [TestUser]
Steps
  1. Open form "Change UserID"
  2. Select [ChangedUserB] in the "User" field
  3. Validate the "Old User ID" field is populated with [ChangedUserB]
  4. Click the "Previous" radio button in the "New or Previous ID" field
  5. Validate the "Select Previous ID" field is enabled
  6. Click the drop down list
  7. Select the users original ID [ChangedUserA] from the list
  8. Submit the form
  9. Validate the form submits successfully
  10. Open form "User Definition"
  11. In the "Select User" field, search for [ChangedUserB]
  12. Validate a message is displayed "User ID [ChangedUserB] is disabled. Only User Description can be updated"
  13. Click [OK]
  14. Validate the "Deactivate User" field is selected and disabled
  15. In the "Select User" field, search for [ChangedUserA]
  16. Validate the "Deactivate User" field is 'not' selected and the field is enabled
  17. Close the form
  18. Log out as [TestUser]
  19. At the Login screen
  20. Log in as [ChangedUserB]
  21. Validate login is unsuccessful
  22. At the Login screen
  23. Log in as [ChangedUserA] using the password that was assigned to [ChangedUserB]
  24. Validate login is successful
  25. At the Home View, navigate to the "My To Do's" list
  26. Validate the "To Do" for the document routed for [TestForm] is present in their "To Do" list, as expected
  27. Generate the report to display data in the "SYSTEM.Doc_documents" table
  28. Locate the row containing [TestDoc] for [TestClient] submitted in the setup
  29. Validate the "data_entry_user_id" field now indicates [ChangedUserA], as expected
  30. Validate other data fields are populated as expected
  31. Generate the report to display data tabled associated with [TestForm]
  32. Locate the row containing submitted for [TestClient] in the setup
  33. Validate the "data_entry_user_id" field now indicates [ChangedUserA], as expected
  34. Validate other data fields are populated as expected
  35. Open form "User Definition"
  36. In the "Select User" field, search for [ChangedUserA]
  37. Change the password to a new password
  38. Submit the form
  39. Log out as [ChangedUserA]
  40. Log in as [TestUser]
  41. Open form "Change UserID"
  42. Select [ChangedUserA] in the "User" field
  43. Validate the "Old User ID" field is populated with [ChangedUserA]
  44. Click the "Previous" radio button in the "New or Previous ID" field
  45. Validate the "Select Previous ID" field is enabled
  46. Click the drop down list
  47. Select the users original ID [ChangedUserB] from the list
  48. Submit the form
  49. Validate the form submits successfully
  50. Open form "User Definition"
  51. In the "Select User" field, search for [ChangedUserA]
  52. Validate a message is displayed "User ID [ChangedUserA] is disabled. Only User Description can be updated"
  53. Click [OK]
  54. Validate the "Deactivate User" field is selected and disabled
  55. In the "Select User" field, search for [ChangedUserB]
  56. Validate the "Deactivate User" field is 'not' selected and the field is enabled
  57. Close the form
  58. Log out as [TestUser]
  59. At the login screen
  60. Log in as [ChangedUserA]
  61. Validate login is unsuccessful
  62. At the login screen
  63. Log in as [ChangedUserB] using the new password assigned [ChangedUserA] in step 8
  64. Validate login is successful
  65. Generate the report to display data in the "SYSTEM.Doc_documents" table
  66. Locate the row containing [TestDoc] for [TestClient] submitted in the setup
  67. Validate the data_entry_user_id" field now indicates [ChangedUserB], as expected
  68. Validate other data fields are populated as expected
  69. Generate the report to display data tabled associated with [TestForm]
  70. Locate the row containing submitted for [TestClient] in the setup
  71. Validate the "data_entry_user_id" field now indicates [ChangedUserB], as expected
  72. Validate other data fields are populated as expected
User Merge File Import
Scenario 1: User Merge File Import' form (Multiple Users) - create new user
Specific Setup:
  • Have four users for testing
  • [TestUser1], [TestUser2], [TestUser3], [TestUser4],
  • Have a "User Import File" file created [TestImport]
  • Have the import file set up to merge the following users to new user:
  • [TestUser1] and [TestUser2] to a new user [Merged1]
  • [TestUser3] and [TestUser4] to a new user [Merged2]
  • Note: (For file format and requirements for a "User Merge" file, see Wiki page: https://wikihelp.ntst.com/EHR/myAvat...ge_File_Import")
  • Have a report or query to display data in the "SYSTEM.RadPlusUserLink" table
Steps
  1. Open form "User File Import"
  2. Click [Select User Import File]
  3. Navigate to the location of the [TestImport] file
  4. Select the file and click [OK]
  5. In the "User Merge File Scan Results" field, validate there are no messages blocking the import
  6. Click [Process User Merge File]
  7. Validate the merge is successful. [Please Note: by default, the new merged user's temporary password will be their user name after the merge is processed]
  8. Log in as [TestUser1]
  9. Validate login is not successful, as expected
  10. Log in as [TestUser2]
  11. Validate login is not successful, as expected
  12. Using their user name as their temporary password, log in as [Merged1]
  13. Validate the user is prompted to change their password
  14. Enter a new password
  15. Validate login is successful
  16. Repeat step 2 and 3 using [TestUser2] and [TestUser3]
  17. Validate the results are same, as expected
  18. Using their user name as their temporary password, log in as [Merged2]
  19. Validate the user is prompted to change their password
  20. Enter a new password
  21. Validate login is successful
  22. Run the report or query to display data in the "SYSTEM.RadPlusUserLink" table
  23. Locate the row for [Merged1]
  24. Validate the value in the "disable_value" field indicate "No" and note the value in their 'system_link_id" field
  25. Locate the row for [Merged2]
  26. Validate the value in the "disable_value" field indicate "No"
  27. Validate the value in their 'system_link_id" is unique, a different value than what was noted for [Merged1] in step 6a
Topics
• Change User ID • User Merge
2023 Update 136 Summary | Details
Clinical Document Viewer - Service Date
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Envelope Import (CWS)
  • Document Routing Setup (PM)
  • Modeled Form With Service Documentation
  • Clinical Document Viewer
  • Envelope Definition (CWS)
  • Table Definition (CWS)
  • Form Definition (CWS)
  • Modeled Form with Service Documentation Sorted by Order Entry
  • Client
Scenario 1: Clinical Document Viewer - Viewing user modeled form with service documentation sorted by date
Specific Setup:
  • Create or import a user modeled form with service documentation that must be ordered by date of service.
  • Give the user access to the modeled form using the "User Definition" form.
  • Click "Refresh Forms".
  • Using "Document Routing Setup":
  • Enable document routing for the user modeled form.
Steps
  1. Open the "Scheduling Calendar" form.
  2. Create an appointment.
  3. Open the modeled form from setup that was enabled for document routing.
  4. Create and finalize the note.
  5. Open the "Clinical Document Viewer
  6. Locate the row that contains the form that was finalized.
  7. Validate the "Service Date" columns is populated with the service date on the form.
Scenario 2: Clinical Document Viewer - Viewing user modeled form with service documentation sorted by entry order
Specific Setup:
  • Create or import a user modeled form with service documentation and must be ordered order of entry.
  • Give the user access to the modeled form using the "User Definition" form.
  • Click "Refresh Forms".
  • Using "Document Routing Setup":
  • Enable document routing for the user modeled form.
Steps
  1. Open the "Scheduling Calendar" form.
  2. Create an appointment.
  3. Open the modeled form from setup that was enabled for document routing.
  4. Create and finalize the note.
  5. Open the "Clinical Document Viewer
  6. Locate the row that contains the form that was finalized.
  7. Validate the "Service Date" columns is populated with the entry date of the form
Topics
• Modeling • Service Documentation • Clinical Document Viewer
2023 Update 144 Summary | Details
Client Lookup
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Import Client Picture (PM)
Scenario 1: Validate the 'Display Name as Last,First' registry setting
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access the 'Registry Settings' form.
  2. Enter "Display Name As Last, First" in the 'Limit Registry Settings to the Following Search Criteria' field.
  3. Click [View Registry Settings].
  4. Validate the 'Registry Setting' field contains "RADplus->Database Management->Client Lookup->->->Display Name As Last, First"
  5. Validate the 'Registry Setting Details' field contains "Selecting 'Y' will display client name as Last Name, First Name when using the Select Client search from the Home Page. Selecting 'N' will display client name as First Name Last Name".
  6. Enter "Y" in the 'Registry Setting Value' field.
  7. Click [Submit] and close the form.
  8. In the 'Client Search', search for "Client A" using a partial last name.
  9. Validate the 'Results' contain "Client A" in the format of "LAST,FIRST (ID#)" without extra commas.
  10. Access the 'Import Client Picture' form.
  11. Search for "Client A" in the 'Client' field using a partial last name.
  12. Validate "Client A" is displayed in the format of "LAST,FIRST (ID#)" without extra commas.
  13. Close the form.
  14. Access the 'Registry Settings' form.
  15. Enter "Display Name As Last, First" in the 'Limit Registry Settings to the Following Search Criteria' field.
  16. Click [View Registry Settings].
  17. Validate the 'Registry Setting' field contains "RADplus->Database Management->Client Lookup->->->Display Name As Last, First"
  18. Validate the 'Registry Setting Details' field contains "Selecting 'Y' will display client name as Last Name, First Name when using the Select Client search from the Home Page. Selecting 'N' will display client name as First Name Last Name".
  19. Enter "N" in the 'Registry Setting Value' field.
  20. Click [Submit] and close the form.
  21. In the 'Client Search', search for "Client A" using a partial last name.
  22. Validate the 'Results' contain "Client A" in the format of "FIRST LAST (ID#)".
  23. Access the 'Import Client Picture' form.
  24. Search for "Client A" in the 'Client' field using a partial last name.
  25. Validate "Client A" is displayed in the format of "FIRST LAST (ID#)"
  26. Close the form.
Topics
• Registry Settings • Client Search
2023 Update 145 Summary | Details
Netsmart - Support Utilities
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Support Utility
Internal Test Only
Topics
• RADplus Utilities
 

RADplus_2024_Monthly_Release_2024.00.01_Details.csv