Skip to main content

Avatar CareFabric 2023 Monthly Release 2023.02.00 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 19 Summary | Details
Avatar CareFabric - support for Integrated eSignature functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
  • CareFabric Monitor
  • Ambulatory Progress Notes
  • Clinical Document Viewer
  • Treatment Plan
  • Send Document
Scenario 1: Update Client Data - Validate the 'ClientUpdated' and 'ClientDemographicsCreated' events
Specific Setup:
  • A client must be enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Enter the desired value in the 'Address - Street' field.
  3. Enter the desired value in the 'Apartment or Unit' field.
  4. Enter the desired value in the 'Zip Code' field.
  5. Enter the desired value in the 'City' field.
  6. Select the desired value in the 'State' field.
  7. Enter the desired date in the 'Address Start Date' field.
  8. Select "No" in the 'Consent On File For Use of Integrated eSignature' field.
  9. Populate any other desired fields.
  10. Click [Submit].
  11. Access the 'CareFabric Monitor' form.
  12. Enter the current date in the 'From Date' and 'Through Date' fields.
  13. Enter "Client A" in the 'Client ID' field.
  14. Click [View Activity Log].
  15. Validate the 'CareFabric Monitor Report' contains a "ClientUpdated" record and select it.
  16. Click [Click To View Record].
  17. Validate the 'addresses' - 'city' field contains the value entered in the previous steps.
  18. Validate the 'addresses' - 'fromDate' field contains the 'Address Start Date' entered in the previous steps.
  19. Validate the 'addresses' - 'stateCode' field contains the value entered in the previous steps.
  20. Validate the 'addresses' - 'street1' field contains the value entered in the previous steps.
  21. Validate the 'addresses' - 'street2' field contains the value entered in the previous steps.
  22. Validate the 'addresses' - 'zipCode' field contains the value entered in the previous steps.
  23. Validate the 'addresses' - 'typeCode' - 'code' field contains "H".
  24. Validate the 'addresses' - 'typeCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.67".
  25. Validate the 'addresses' - 'typeCode' - 'codeSystemName' field contains "Address".
  26. Validate the 'addresses' - 'typeCode' - 'displayName' field contains "Home".
  27. Validate the 'isESignatureConsentOnFile' field contains "false".
  28. Validate any other filed data is displayed.
  29. Navigate back to the 'CareFabric Monitor Report' and select the "ClientDemographicsCreated" record.
  30. Click [Click To View Record].
  31. Validate the 'addresses' - 'city' field contains the value entered in the previous steps.
  32. Validate the 'addresses' - 'fromDate' field contains the 'Address Start Date' entered in the previous steps.
  33. Validate the 'addresses' - 'stateCode' field contains the value entered in the previous steps.
  34. Validate the 'addresses' - 'street1' field contains the value entered in the previous steps.
  35. Validate the 'addresses' - 'street2' field contains the value entered in the previous steps.
  36. Validate the 'addresses' - 'zipCode' field contains the value entered in the previous steps.
  37. Validate the 'isESignatureConsentOnFile' field contains "false".
  38. Close the report and the form.
  39. Select "Client A" and access the 'Update Client Data' form.
  40. Enter any new value in the 'Address - Street' field.
  41. Enter any new value in the 'Apartment or Unit' field.
  42. Enter any new value in the 'Zip Code' field.
  43. Enter any new value in the 'City' field.
  44. Select any new value in the 'State' field.
  45. Select "Yes" in the 'Consent On File For Use of Integrated eSignature' field.
  46. Click [Submit].
  47. Access the 'CareFabric Monitor' form.
  48. Enter the current date in the 'From Date' and 'Through Date' fields.
  49. Enter "Client A" in the 'Client ID' field.
  50. Click [View Activity Log].
  51. Validate the 'CareFabric Monitor Report' contains a "ClientUpdated" record and select it.
  52. Click [Click To View Record].
  53. Validate the 'addresses' - 'city' field contains the new value entered in the previous steps.
  54. Validate the 'addresses' - 'stateCode' field contains the new value entered in the previous steps.
  55. Validate the 'addresses' - 'street1' field contains the new value entered in the previous steps.
  56. Validate the 'addresses' - 'street2' field contains the new value entered in the previous steps.
  57. Validate the 'addresses' - 'zipCode' field contains the new value entered in the previous steps.
  58. Validate the second 'addresses' - 'city' field contains the old address value.
  59. Validate the second 'addresses' - 'stateCode' field contains the old address value.
  60. Validate the second 'addresses' - 'street1' field contains the old address value.
  61. Validate the second 'addresses' - 'street2' field contains the old address value.
  62. Validate the second 'addresses' - 'zipCode' field contains the old address value.
  63. Validate the second 'addresses' - 'typeCode' - 'code' field contains "OLD".
  64. Validate the second 'addresses' - 'typeCode' - 'displayName' field contains "Old Address".
  65. Validate the second 'addresses' - 'typeCode' - isActive' field contains "false".
  66. Validate the 'isESignatureConsentOnFile' field contains "true".
  67. Navigate back to the 'CareFabric Monitor Report' page.
  68. Validate the 'CareFabric Monitor Report' contains a "ClientDemographicsCreated" record and select it.
  69. Validate the 'addresses' - 'city' field contains the new value entered in the previous steps.
  70. Validate the 'addresses' - 'stateCode' field contains the new value entered in the previous steps.
  71. Validate the 'addresses' - 'street1' field contains the new value entered in the previous steps.
  72. Validate the 'addresses' - 'street2' field contains the new value entered in the previous steps.
  73. Validate the 'addresses' - 'zipCode' field contains the new value entered in the previous steps.
  74. Validate the 'isESignatureConsentOnFile' field contains "true".
  75. Close the report and the form.
Scenario 2: Integrated eSignature - Progress Notes - Collect eSignature via Document Routing (No Approvers)
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Ambulatory Progress Notes' form and an approver is not required.
  • The 'Pending eSignatures' widget must be accessible on the HomeView.
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' field.
  5. Select "Final" in the 'Draft/Final' field.
  6. Click [Submit].
  7. Validate a 'Confirm Document' dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user in the 'Password' field and click [Verify].
  10. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  11. Click [Submit].
  12. Navigate to the 'Pending eSignatures' widget.
  13. Validate a row is displayed for the eSignature request sent for "Client A".
  14. Access Crystal Reports or other SQL Reporting tool.
  15. Create a report using the 'DocR.esignature' SQL table.
  16. Validate a row is displayed for the eSignature request sent for "Client A".
  17. Validate the 'eSignature_status' field contains "Pending".
  18. Log in to myHealthPointe for "Client A".
  19. Select the "Documents Awaiting Signature" section.
  20. Validate the document sent for eSignature is displayed.
  21. Click [Sign and Submit].
  22. Enter an eSignature in the 'Enter the Signature' field.
  23. Click [Sign and Submit].
  24. Validate the document is no longer displayed.
  25. Navigate to the 'Pending eSignatures' widget.
  26. Validate the row is no longer displayed for "Client A".
  27. Access Crystal Reports or other SQL Reporting tool.
  28. Refresh the report using the 'DocR.esignature' SQL table.
  29. Validate the 'eSignature_status' field now contains "Approved".
  30. Close the report.
  31. Access the 'Clinical Document Viewer' form.
  32. Select "Client" in the 'Select Client:' field.
  33. Select "Individual" in the 'Select All or Individual Client' field.
  34. Select "Client A" in the 'Select Client' field.
  35. Click [Process].
  36. Validate two document rows are displayed for the client:
  37. One 'Document Description' contains "Integrated eSignature request" - this is what was sent to myHealthPointe for eSignature.
  38. One 'Document Description' contains "Ambulatory Progress Notes" - this is the progress note document finalized via document routing.
  39. Select both documents for viewing and click [View].
  40. Validate the "Integrated eSignature request" displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  41. Validate the "Ambulatory Progress Notes" finalized document displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  42. Click [Close All Documents] and close the form.
Scenario 3: Integrated eSignature - Treatment Plan - Send Document Only via Document Routing
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing outpatient episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • Document Routing is enabled on the 'Treatment Plan' form and an approver is not required.
Steps
  1. Select "Client A" and access the 'Treatment Plan' form.
  2. Enter the desired date in the 'Plan Date' field.
  3. Enter the desired value in the 'Plan Name' field.
  4. Populate all other required and desired fields.
  5. Select "Final" in the 'Treatment Plan Status' field.
  6. Click [Submit].
  7. Validate a 'Confirm Document' dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user in the 'Password' field and click [Verify].
  10. Select "Document Only" in the 'Send to myHealthPointe' field.
  11. Click [Submit].
  12. Access the 'Clinical Document Viewer' form.
  13. Select "Client" in the 'Select Client:' field.
  14. Select "Individual" in the 'Select All or Individual Client' field.
  15. Select "Client A" in the 'Select Client' field.
  16. Click [Process].
  17. Validate two document rows are displayed for the client:
  18. One 'Document Description' contains "Document sent for review" - this is what was sent to myHealthPointe for review.
  19. One 'Document Description' contains "Treatment Plan" - this is the finalized treatment plan form finalized via document routing.
  20. Select both documents for viewing and click [View].
  21. Validate the documents display as expected.
  22. Click [Close All Documents] and close the form.
  23. Log in to myHealthPointe for "Client A".
  24. Select the "Documents" section.
  25. Validate the document sent via document routing is displayed.
  26. Select the document and validate the pdf opens and displays as expected.
  27. Close the document.
Scenario 4: Integrated eSignature - Modeled Form - Collect eSignature via Document Routing (With Approvers)
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • A "Client" entity modeled form must be defined (Form A).
  • Document Routing is enabled on "Form A".
  • The 'Pending eSignatures' widget must be accessible on the HomeView.
Steps
  1. Select "Client A" and access "Form A".
  2. Populate all required and desired fields.
  3. Select "Final" in the 'Treatment Plan Status' field.
  4. Click [Submit].
  5. Validate a 'Confirm Document' dialog is displayed.
  6. Click [Accept and Route].
  7. Enter the password for the logged in user in the 'Password' field and click [Verify].
  8. Add the staff associated to the logged in user as an approver.
  9. Select "Collect eSignature" in the 'Send to myHealthPointe' field.
  10. Click [Submit].
  11. Navigate to the 'Pending eSignatures' widget.
  12. Validate a row is displayed for the eSignature request sent for "Client A".
  13. Access Crystal Reports or other SQL Reporting tool.
  14. Create a report using the 'DocR.esignature' SQL table.
  15. Validate a row is displayed for the eSignature request sent for "Client A".
  16. Validate the 'eSignature_status' field contains "Pending".
  17. Navigate to the 'My To Do's' widget.
  18. Validate a To-Do is not displayed for the document for "Client A" that has a pending eSignature.
  19. The To-Do will only be generated after the document has been signed by the client in myHealthPointe.
  20. Log in to myHealthPointe for "Client A".
  21. Select the "Documents Awaiting Signature" section.
  22. Validate the document sent for eSignature is displayed.
  23. Click [Sign and Submit].
  24. Enter an eSignature in the 'Enter the Signature' field.
  25. Click [Sign and Submit].
  26. Validate the document is no longer displayed.
  27. Navigate to the 'Pending eSignatures' widget.
  28. Validate the row is no longer displayed for "Client A".
  29. Access Crystal Reports or other SQL Reporting tool.
  30. Refresh the report using the 'DocR.esignature' SQL table.
  31. Validate the 'eSignature_status' field now contains "Approved".
  32. Close the report.
  33. Navigate to the 'My To Do's' widget.
  34. Validate a To-Do is displayed for "Client A".
  35. Click [Review] and [Accept].
  36. Validate the 'Document Preview' contains the following electronic signatures appended to the end of the document:
  37. Electronically signed by Author
  38. Electronically signed by "Client A"
  39. Electronically signed by Approver
  40. Click [Sign].
  41. Enter the password for the logged in user in the 'Password' field and click [Verify].
  42. Validate the To-Do is no longer displayed.
  43. Click [Close].
  44. Access the 'Clinical Document Viewer' form.
  45. Select "Client" in the 'Select Client:' field.
  46. Select "Individual" in the 'Select All or Individual Client' field.
  47. Select "Client A" in the 'Select Client' field.
  48. Click [Process].
  49. Validate two document rows are displayed for the client:
  50. One 'Document Description' contains "Integrated eSignature request" - this is what was sent to myHealthPointe for eSignature.
  51. One 'Document Description' contains "Form A" - this is the modeled form finalized via document routing.
  52. Select both documents for viewing and click [View].
  53. Validate the "Integrated eSignature request" displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  54. Validate the "Form A" finalized document displays the document with the author's signature, "Client A" signature, and the approving practitioner signature.
  55. Click [Close All Documents] and close the form.
Scenario 5: Integrated eSignature - 'Send Document' form - Send Document Only
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • User must have access to the 'Send Document' form.
  • Document Routing is enabled on the 'Progress Notes (Group and Individual)' form.
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. Enter the desired value in the 'Notes Field' field.
  6. Select "Final" in the 'Draft/Final' field.
  7. Click [File Note].
  8. Validate a 'Confirm Document' dialog is displayed.
  9. Click [Accept].
  10. Enter the password for the logged in user in the 'Password' field and click [Verify].
  11. Validate a message is displayed stating: Note Filed.
  12. Click [OK] and close the form.
  13. Access the 'Send Document' form.
  14. Select the form type associated to 'Progress Notes (Group and Individual)' in the 'Form Type' field.
  15. Select "Client A" in the 'Entity' field.
  16. Validate 'Episode Number' field contains "All Episodes".
  17. Enter the current date in the 'From Date' and 'To Date' fields.
  18. Select the progress note filed in the previous steps in the 'Select Document' field.
  19. Click [Display Document].
  20. Validate the document displays as filed.
  21. Click [Close All Documents and Exit].
  22. Validate "Send Document Only" is defaulted in the 'Reason for Sending' field.
  23. Once the document has received all approvals, it is considered finalized and may not be sent for eSignature but the document can still be sent for review only.
  24. Click [Send Request].
  25. Validate a message is displayed stating: Request Sent.
  26. Click [OK] and close the form.
  27. Access the 'Clinical Document Viewer' form.
  28. Select "Client" in the 'Select Client:' field.
  29. Select "Individual" in the 'Select All or Individual Client' field.
  30. Select "Client A" in the 'Select Client' field.
  31. Click [Process].
  32. Validate two document rows are displayed for the client:
  33. One 'Document Description' contains "Document sent for review" - this is what was sent to myHealthPointe for review.
  34. One 'Document Description' contains "Progress Notes (Group and Individual)" - this is the finalized progress note form finalized via document routing.
  35. Select both documents for viewing and click [View].
  36. Validate the documents display as expected.
  37. Click [Close All Documents] and close the form.
  38. Log in to myHealthPointe for "Client A".
  39. Select the "Documents" section.
  40. Validate the document sent via the 'Send Document' form is displayed.
  41. Select the document and validate the pdf opens and displays as expected.
  42. Close the document.
Scenario 6: Integrated eSignature - 'Send Document' form - Send for eSignature
Specific Setup:
  • Please note: this is for Avatar NX systems only.
  • Avatar NX must be configured to integrate with myHealthPointe.
  • A client is enrolled in an existing episode with the following (Client A):
  • 'Date of Birth' on file
  • 'Email Address' on file
  • Login credentials for myHealthPointe
  • The 'Enable Send Document to myHealthPointe functionality' registry setting is set to "Y".
  • User must have access to the 'Send Document' form.
  • Document Routing is enabled on the 'Treatment Plan' form.
  • The 'Pending eSignatures' widget must be accessible on the myDay view.
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. Populate all other required and desired fields.
  5. Select "Final" in the 'Treatment Plan Status' field.
  6. Click [Submit].
  7. Validate a 'Confirm Document' dialog is displayed.
  8. Click [Accept and Route].
  9. Enter the password for the logged in user in the 'Password' field and click [Verify].
  10. Add the staff associated to the logged in user as an approver.
  11. Select "None" in the 'Send to myHealthPointe' field.
  12. Click [Submit].
  13. Navigate to the 'My To Do's' widget.
  14. Validate a To-Do is displayed for "Client A" but do not approve it.
  15. Click [Close].
  16. Access the 'Send Document' form.
  17. Select the form type associated to 'Treatment Plan' in the 'Form Type' field.
  18. Select "Client A" in the 'Entity' field.
  19. Validate 'Episode Number' field contains "All Episodes".
  20. Enter the current date in the 'From Date' and 'To Date' fields.
  21. Select the treatment plan filed in the previous steps in the 'Select Document' field.
  22. Click [Display Document].
  23. Validate the document displays as filed.
  24. Click [Close All Documents and Exit].
  25. Validate both "Send Document Only" and "Send for eSignature" are enabled in the 'Reason for Sending' field.
  26. "Re-send for eSignature" is disabled because the document has not been sent for eSignature yet.
  27. Validate "Send for eSignature" is the default value in the 'Reason for Sending' field.
  28. Click [Send Request].
  29. Validate a message is displayed stating: Request Sent.
  30. Click [OK] and close the form.
  31. Navigate to the 'Pending eSignatures' widget.
  32. Validate a row is displayed for the eSignature request sent for "Client A".
  33. Navigate to the 'My To Do's' widget.
  34. Validate the To-Do is no longer displayed for "Client A".
  35. The To-Do will display after the eSignature has been collected.
  36. Click [Close].
  37. Log in to myHealthPointe for "Client A".
  38. Select the "Documents Awaiting Signature" section.
  39. Validate the document sent for eSignature is displayed.
  40. Click [Sign and Submit].
  41. Enter an eSignature in the 'Enter the Signature' field.
  42. Click [Sign and Submit].
  43. Validate the document is no longer displayed.
  44. Navigate to the 'Pending eSignatures' widget.
  45. Validate the row is no longer displayed for "Client A".
  46. Navigate to the 'My To Do's' widget.
  47. Validate a To-Do is displayed for "Client A".
  48. Click [Review] and [Accept].
  49. Validate the 'Document Preview' contains the following electronic signatures appended to the end of the document:
  50. Electronically signed by Author
  51. Electronically signed by "Client A"
  52. Electronically signed by Approver
  53. Click [Sign].
  54. Enter the password for the logged in user in the 'Password' field and click [Verify].
  55. Validate the To-Do is no longer displayed.
  56. Click [Close].
  57. Access the 'Clinical Document Viewer' form.
  58. Select "Client" in the 'Select Client:' field.
  59. Select "Individual" in the 'Select All or Individual Client' field.
  60. Select "Client A" in the 'Select Client' field.
  61. Click [Process].
  62. Validate two document rows are displayed for the client:
  63. One 'Document Description' contains "Integrated eSignature request" - this is what was sent to myHealthPointe for eSignature.
  64. One 'Document Description' contains "Treatment Plan" - this is the finalized treatment plan form finalized via document routing.
  65. Select both documents for viewing and click [View].
  66. Validate the "Integrated eSignature request" displays the document with the author's signature and the signature for "Client A" appended to the bottom right corner.
  67. Validate the "Treatment Plan" finalized document displays the document with the author's signature, "Client A" signature, and the approving practitioner signature.
  68. Click [Close All Documents] and close the form.
Topics
• CareFabric • Update Client Data • CareFabric Monitor • Integrated eSignature • NX
Update 22 Summary | Details
Avatar CareFabric - SDK events
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Care Connect Inbox
  • CareFabric Monitor
  • CareFabric Event Attribute Mapping
Scenario 1: CareConnect Inbox - Admit a new client
Specific Setup:
  • There must be a referral in 'CareConnect Inbox' with a CCD attached ready to be accepted.
Steps
  1. Access the 'CareConnect Inbox' application.
  2. Navigate to the existing referral and select the CCD section.
  3. Click [Manage].
  4. Click [Search] to search for a provider.
  5. Enter the desired provider name in the 'First Name' and 'Last Name' fields.
  6. Click [Search].
  7. Select the desired provider and click [Add Provider].
  8. Click [Admit New Client].
  9. Validate a message is displayed stating: Auto Assign Next ID Number?
  10. Click [Yes].
  11. Validate the 'Admission (Outpatient)' form is now displayed.
  12. Populate all required and desired values.
  13. Click [Submit].
  14. Access the 'CareFabric Monitor' form.
  15. Enter the current date in the 'From Date' and 'Through Date' fields.
  16. Enter "Client A" in the 'Client ID' field.
  17. Enter "IncomingReferralCreated" in the 'Event/Action Search' field.
  18. Click [View Activity Log].
  19. Validate the 'CareFabric Monitor Report' contains an "IncomingReferralCreated" record.
  20. Click [Click To View Record].
  21. Validate the 'clientID' - 'id' field contains the new client ID.
  22. Validate the 'clientName' - 'first' field contains the new client first name.
  23. Validate the 'clientName' - 'last' field contains the new client last name.
  24. Validate the 'incomingReferralID' - 'id' field contains a unique identifier (Ex.1682330382677^^123.456.789.6^ISO)
  25. Close the report and the form.
Scenario 2: Validate the "CareTeam" event type in the 'CareFabric Event Attribute Mapping' form for a user modeled form
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • Must have a user modeled form for testing with the following fields (Form A):
  • Provider ID - Non Scrolling Free Text field
  • Provider Name - Non Scrolling Free Text field
  • Provider Type - Single Response Dictionary field
  • Email Address - Non Scrolling Free Text field
  • "Form A" must be flagged as an assessment in the 'Flag Assessment Forms' form.
Steps
  1. Access the 'CareFabric Event Attribute Mapping' form.
  2. Select "CareTeam" in the 'Associated Event' field.
  3. Click [New Row].
  4. Select "Form A" in the 'Select' field.
  5. Select "Provider ID" in the 'Field' field.
  6. Select "ProviderID" in the 'CareFabric Element' field.
  7. Click [New Row].
  8. Select "Form A" in the 'Select' field.
  9. Select "Provider Name" in the 'Field' field.
  10. Select "ProviderName" in the 'CareFabric Element' field.
  11. Click [New Row].
  12. Select "Form A" in the 'Select' field.
  13. Select "Provider Type" in the 'Field' field.
  14. Select "TypeofProvider" in the 'CareFabric Element' field.
  15. Enter the desired value in the 'Non-standard Code System Code' field.
  16. Click [New Row].
  17. Select "Form A" in the 'Select' field.
  18. Select "EmailAddress" in the 'Field' field.
  19. Select "DirectMailAddress" in the 'CareFabric Element' field.
  20. Click [Submit].
  21. Select "Client A" and access "Form A".
  22. Enter the desired value in the 'Provider ID' field.
  23. Enter the desired value in the 'Provider Name' field.
  24. Select the desired value in the 'Provider Type' field.
  25. Enter the desired value in the 'Email Address' field.
  26. Click [Submit].
  27. Access the 'CareFabric Monitor' form.
  28. Enter the current date in the 'From Date' and 'Through Date' fields.
  29. Enter "Client A" in the 'Client ID' field.
  30. Enter "ProgramAdmissionUpdated" in the 'Event/Action Search' field.
  31. Click [View Activity Log].
  32. Validate the 'CareFabric Monitor Report' contains an "ProgramAdmissionUpdated" record.
  33. Click [Click To View Record].
  34. Validate the 'careTeam' - 'emailAccounts' - 'address' field contains the 'Email Address' entered in the previous steps.
  35. Validate the 'careTeam' - 'name' - 'first' field contains the 'Provider Name' entered in the previous steps.
  36. Validate the 'careTeam' - 'name' - 'last' field contains the 'Provider Name' entered in the previous steps.
  37. Validate the careTeam' - 'providerID' - 'id' field contains the 'Provider ID' entered in the previous steps.
  38. Validate the careTeam- 'roleCode' - 'displayName' field contains the 'Provider Type' entered in the previous steps.
  39. Close the report and the form.
Topics
• Admission • CareConnect Inbox • CareFabric Event Attribute Mapping
Update 24 Summary | Details
CarePOV Management - 'Duplicate Name - Header' Client Alert
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Client Lookup/Header Configuration Manager
  • CarePOV Management
  • Pre Admit
  • Discharge
Scenario 1: Validate the 'Trigger 'Duplicate Name-Header' Alert on matching client in Pre Admit Episode' registry setting when the client alert is configured based on 'Full Name (First and Last)'
Specific Setup:
  • "Bed Board Alerts" should be configured in the 'Client Header' section of the 'Client Lookup/Header Configuration Manager' form.
  • The user must have access to the 'Client Information Header' on the HomeView.
  • Two clients are defined with the same first & last name (Client A & Client B).
  • "Client A" must be admitted into an admission program.
  • "Client B" must be admitted into a pre-admit program.
Steps
  1. Access the 'CarePOV Management' form.
  2. Select the "Client Alerts" section.
  3. Click "Add" in the 'Add or Edit Alert' field.
  4. Select "Duplicate Name - Header" in the 'Alert Type' field.
  5. Select "Full Name (First and Last)" in the 'Base Duplicate Name On' field.
  6. Enter the desired value in the 'Client Alert Description' field.
  7. Select the desired icon in the 'Select Icon' field.
  8. Select "Yes" in the 'Active' field.
  9. Select "Yes" in the 'Include in Client Header' field.
  10. Click [Save].
  11. Validate a message is displayed stating: Saved.
  12. Click [OK] and close the form.
  13. Access the 'Registry Settings' form.
  14. Enter "Trigger 'Duplicate Name-Header' Alert on matching client in Pre-Admit Episode" in the 'Limit Registry Settings to the Following Search Criteria' field.
  15. Click [View Registry Settings].
  16. Validate the 'Registry Setting' field contains: "Trigger 'Duplicate Name-Header' Alert on matching client in Pre-Admit Episode".
  17. Validate the 'Registry Setting Value' field contains "Y". This is the default value.
  18. Validate the 'Registry Setting Detail' field contains: If setting is set to 'Y' and 'Duplicate Name - Header' alerts are configured in the 'CarePOV Management' form, then a header alert will be triggered if a matching client is found in an active Pre-Admit program. If setting is set to 'N' and 'Duplicate Name - Header' alerts are configured in the 'CarePOV Management' form, then header alerts will not trigger if only an active Pre-Admit program exists.
  19. Click [Submit] and close the form.
  20. Select "Client A" and navigate to the 'Client Information Header'.
  21. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  22. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  23. Select "Client B" and navigate to the 'Client Information Header'.
  24. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  25. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  26. Access the 'Registry Settings' form.
  27. Enter "Trigger 'Duplicate Name-Header' Alert on matching client in Pre-Admit Episode" in the 'Limit Registry Settings to the Following Search Criteria' field.
  28. Click [View Registry Settings].
  29. Validate the 'Registry Setting' field contains: "Trigger 'Duplicate Name-Header' Alert on matching client in Pre-Admit Episode".
  30. Enter "N" in the 'Registry Setting Value' field.
  31. Click [Submit] and close the form.
  32. Select "Client A" and navigate to the 'Client Information Header'.
  33. Validate the duplicate name alert is no longer displayed since the matching client is admitted in a pre-admit program.
  34. Select "Client B" and navigate to the 'Client Information Header'.
  35. Validate the duplicate name alert is still displayed since the matching client is admitted in a regular admission program.
  36. Select "Client A" and access the 'Discharge' form.
  37. Enter the desired date in the 'Date Of Discharge' field.
  38. Enter the desired time in the 'Discharge Time' field.
  39. Select the desired value in the 'Type Of Discharge' field.
  40. Select the desired value in the 'Discharge Practitioner' field.
  41. Submit the form.
  42. Select "Client B" and navigate to the 'Client Information Header'.
  43. Validate the duplicate name alert is no longer displayed since the matching client has been discharged and is no longer active.
Scenario 2: Validate the 'Trigger 'Duplicate Name-Header' Alert on matching client in Pre Admit Episode' registry setting when the client alert is configured based on 'First Name & Last Initial'
Specific Setup:
  • "Bed Board Alerts" should be configured in the 'Client Header' section of the 'Client Lookup/Header Configuration Manager' form.
  • The user must have access to the 'Client Information Header' on the HomeView.
  • Two clients are defined with the same first name & last initial (Client A & Client B).
  • "Client A" must be admitted into an admission program.
  • "Client B" must be admitted into a pre-admit program.
Steps
  1. Access the 'CarePOV Management' form.
  2. Select the "Client Alerts" section.
  3. Click "Add" in the 'Add or Edit Alert' field.
  4. Select "Duplicate Name - Header" in the 'Alert Type' field.
  5. Select "First Name, Last Initial" in the 'Base Duplicate Name On' field.
  6. Enter the desired value in the 'Client Alert Description' field.
  7. Select the desired icon in the 'Select Icon' field.
  8. Select "Yes" in the 'Active' field.
  9. Select "Yes" in the 'Include in Client Header' field.
  10. Click [Save].
  11. Validate a message is displayed stating: Saved.
  12. Click [OK] and close the form.
  13. Access the 'Registry Settings' form.
  14. Enter "Trigger 'Duplicate Name-Header' Alert on matching client in Pre-Admit Episode" in the 'Limit Registry Settings to the Following Search Criteria' field.
  15. Click [View Registry Settings].
  16. Validate the 'Registry Setting' field contains: "Trigger 'Duplicate Name-Header' Alert on matching client in Pre-Admit Episode".
  17. Validate the 'Registry Setting Value' field contains "Y". This is the default value.
  18. Validate the 'Registry Setting Detail' field contains: If setting is set to 'Y' and 'Duplicate Name - Header' alerts are configured in the 'CarePOV Management' form, then a header alert will be triggered if a matching client is found in an active Pre-Admit program. If setting is set to 'N' and 'Duplicate Name - Header' alerts are configured in the 'CarePOV Management' form, then header alerts will not trigger if only an active Pre-Admit program exists.
  19. Click [Submit] and close the form.
  20. Select "Client A" and navigate to the 'Client Information Header'.
  21. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  22. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  23. Select "Client B" and navigate to the 'Client Information Header'.
  24. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  25. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  26. Access the 'Registry Settings' form.
  27. Enter "Trigger 'Duplicate Name-Header' Alert on matching client in Pre-Admit Episode" in the 'Limit Registry Settings to the Following Search Criteria' field.
  28. Click [View Registry Settings].
  29. Validate the 'Registry Setting' field contains: "Trigger 'Duplicate Name-Header' Alert on matching client in Pre-Admit Episode".
  30. Enter "N" in the 'Registry Setting Value' field.
  31. Click [Submit] and close the form.
  32. Select "Client A" and navigate to the 'Client Information Header'.
  33. Validate the duplicate name alert is no longer displayed since the matching client is admitted in a pre-admit program.
  34. Select "Client B" and navigate to the 'Client Information Header'.
  35. Validate the duplicate name alert is still displayed since the matching client is admitted in a regular admission program.
  36. Select "Client A" and access the 'Discharge' form.
  37. Enter the desired date in the 'Date Of Discharge' field.
  38. Enter the desired time in the 'Discharge Time' field.
  39. Select the desired value in the 'Type Of Discharge' field.
  40. Select the desired value in the 'Discharge Practitioner' field.
  41. Submit the form.
  42. Select "Client B" and navigate to the 'Client Information Header'.
  43. Validate the duplicate name alert is no longer displayed since the matching client has been discharged and is no longer active.
Scenario 3: Validate the 'Trigger 'Duplicate Name-Header' Alert on matching client in Pre Admit Episode' registry setting when the client alert is configured based on 'Last Name & First Initial'
Specific Setup:
  • "Bed Board Alerts" should be configured in the 'Client Header' section of the 'Client Lookup/Header Configuration Manager' form.
  • The user must have access to the 'Client Information Header' on the HomeView.
  • Two clients are defined with the same last name & first initial (Client A & Client B).
  • "Client A" must be admitted into an admission program.
  • "Client B" must be admitted into a pre-admit program.
Steps
  1. Access the 'CarePOV Management' form.
  2. Select the "Client Alerts" section.
  3. Click "Add" in the 'Add or Edit Alert' field.
  4. Select "Duplicate Name - Header" in the 'Alert Type' field.
  5. Select "Last Name, First Initial" in the 'Base Duplicate Name On' field.
  6. Enter the desired value in the 'Client Alert Description' field.
  7. Select the desired icon in the 'Select Icon' field.
  8. Select "Yes" in the 'Active' field.
  9. Select "Yes" in the 'Include in Client Header' field.
  10. Click [Save].
  11. Validate a message is displayed stating: Saved.
  12. Click [OK] and close the form.
  13. Access the 'Registry Settings' form.
  14. Enter "Trigger 'Duplicate Name-Header' Alert on matching client in Pre-Admit Episode" in the 'Limit Registry Settings to the Following Search Criteria' field.
  15. Click [View Registry Settings].
  16. Validate the 'Registry Setting' field contains: "Trigger 'Duplicate Name-Header' Alert on matching client in Pre-Admit Episode".
  17. Validate the 'Registry Setting Value' field contains "Y". This is the default value.
  18. Validate the 'Registry Setting Detail' field contains: If setting is set to 'Y' and 'Duplicate Name - Header' alerts are configured in the 'CarePOV Management' form, then a header alert will be triggered if a matching client is found in an active Pre-Admit program. If setting is set to 'N' and 'Duplicate Name - Header' alerts are configured in the 'CarePOV Management' form, then header alerts will not trigger if only an active Pre-Admit program exists.
  19. Click [Submit] and close the form.
  20. Select "Client A" and navigate to the 'Client Information Header'.
  21. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  22. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  23. Select "Client B" and navigate to the 'Client Information Header'.
  24. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  25. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  26. Access the 'Registry Settings' form.
  27. Enter "Trigger 'Duplicate Name-Header' Alert on matching client in Pre-Admit Episode" in the 'Limit Registry Settings to the Following Search Criteria' field.
  28. Click [View Registry Settings].
  29. Validate the 'Registry Setting' field contains: "Trigger 'Duplicate Name-Header' Alert on matching client in Pre-Admit Episode".
  30. Enter "N" in the 'Registry Setting Value' field.
  31. Click [Submit] and close the form.
  32. Select "Client A" and navigate to the 'Client Information Header'.
  33. Validate the duplicate name alert is no longer displayed since the matching client is admitted in a pre-admit program.
  34. Select "Client B" and navigate to the 'Client Information Header'.
  35. Validate the duplicate name alert is still displayed since the matching client is admitted in a regular admission program.
  36. Select "Client A" and access the 'Discharge' form.
  37. Enter the desired date in the 'Date Of Discharge' field.
  38. Enter the desired time in the 'Discharge Time' field.
  39. Select the desired value in the 'Type Of Discharge' field.
  40. Select the desired value in the 'Discharge Practitioner' field.
  41. Submit the form.
  42. Select "Client B" and navigate to the 'Client Information Header'.
  43. Validate the duplicate name alert is no longer displayed since the matching client has been discharged and is no longer active.
Topics
• Client Alerts • CarePOV Management • Client Header
Update 28 Summary | Details
Avatar CareFabric - Bells Notes Integration
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Progress Notes (Group and Individual)
  • Client Ledger
Scenario 1: Bells Notes Integration - Validate the duplicate service check is skipped
Specific Setup:
  • myAvatar must be configured to integrate with Bells Notes. Please note: this must be done by a Netsmart Associate.
  • The 'Progress Notes (Group and Individual)' form is configured and selected in the "Bells Notes" section of the 'CarePOV Management' form. Please note: this must be done by a Netsmart Associate.
  • The 'Allow Skipping Duplicate Service Check' registry setting must be set to "N".
  • The 'Progress Notes (Group and Individual)' form does not have document routing enabled.
  • The 'Progress Notes (Group and Individual)' form must have the 'Service Start Time' and 'Service End Time' fields added via 'Site Specific Section Modeling.
  • A user is defined with the following (User A):
  • Access to Bells Notes
  • Associated practitioner
  • 'Progress Notes' widget accessible on the HomeView
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Log into Bells Notes with existing login credentials for "User A".
  2. Search for "Client A".
  3. Click [Start Note] and verify the existence of the 'Session Information' window.
  4. Select the desired service code in the 'Service Code' field.
  5. Fill out all other required fields and select the desired note type.
  6. Verify the existence of "Client A" in the client header when note is started.
  7. Enter "9:00 AM" in the 'Start' field.
  8. Enter "9:30 AM" in the 'End' field.
  9. Fill out all required fields.
  10. Click [Sign Note].
  11. Validate the Sign Note' dialog is displayed.
  12. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  13. Validate a message is displayed stating: Note Signed Successfully.'
  14. Select "Client A" and access the 'Progress Notes' widget.
  15. Validate the note filed in the previous steps is displayed with all expected data.
  16. Log into Bells Notes with existing login credentials for "User A".
  17. Search for "Client A".
  18. Click [Start Note] and verify the existence of the 'Session Information' window.
  19. Select the service code selected in the previous steps in the 'Service Code' field.
  20. Fill out all other required fields and select the desired note type.
  21. Verify the existence of "Client A" in the client header when note is started.
  22. Enter "9:00 AM" in the 'Start' field.
  23. Enter "9:30 AM" in the 'End' field. Note: we are using the same start/end times to create a duplicate service.
  24. Fill out all required fields.
  25. Click [Sign Note].
  26. Validate the Sign Note' dialog is displayed.
  27. Enter the pin for "User A" in the 'Pin' field and click [Sign].
  28. Validate a message is displayed stating: Note Signed Successfully.'
  29. Select "Client A" and access the 'Progress Notes' widget.
  30. Validate the duplicate service note filed in the previous steps is displayed with all expected data.
  31. Access the 'Client Ledger' form.
  32. Select "Client A" in the 'Client ID' field.
  33. Select "All Episodes" in the 'Claim/Episode/All Episodes' field.
  34. Select "Yes" in the 'Include Zero Charges' field.
  35. Click [Process].
  36. Validate the client ledger contains the duplicate services for the client.
  37. Close the form.
Topics
• Progress Notes • CareFabric
 

Avatar_CareFabric_2023_Monthly_Release_2023.02.00_Details.csv