Skip to main content

Avatar CareFabric 2023 Monthly Release 2023.00.01 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 2 Summary | Details
Avatar CareFabric - support for ProviderConnect Enterprise
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Authorization Request
  • CareFabric Monitor
  • Service Authorization
Scenario 1: Service Authorization Request - Validate the 'ServiceAuthorizationRequestCreated' and 'ServiceAuthorizationRequestUpdated' events
Specific Setup:
  • A member must be defined in the 'Member Enrollment' form (Client A).
  • CPT Codes and Revenue Codes must be defined in Avatar MSO.
  • Please note: this scenario is for Avatar Cal-PM systems only.
Steps
  1. Select "Client A" and access the 'Service Authorization Request' form.
  2. Select the desired provider in the 'Provider To Be Authorized' field.
  3. Validate the 'Current Authorization Status' field is set to "Pending".
  4. Select the desired value in the 'Current Authorization Status Reason' field.
  5. Enter the desired date in the 'Begin Date Of Authorization' field.
  6. Enter the desired date in the 'End Date Of Authorization' field.
  7. Select "Individual" in the 'Authorization Grouping or Individual Authorizations' field.
  8. Select "CPT Code" in the 'Procedure Code Type (1)' field.
  9. Enter the desired CPT Code in the 'Code Authorized (1)' field.
  10. Enter the desired value in the 'Requested Units (1)' field.
  11. Select "Revenue Code" in the 'Procedure Code Type (1)' field.
  12. Enter the desired Revenue Code in the 'Code Authorized (1)' field.
  13. Enter the desired value in the 'Requested Units (1)' field.
  14. Select the "Care Manager" section.
  15. Enter the desired care manager in the 'Care Manager Assigned' field.
  16. Enter the desired date in the 'Date Care Manager Assigned' field.
  17. Select the "Comments" section.
  18. Enter the desired value in the 'Comments On Authorization' field.
  19. Click [Submit] and [No] to exit the form.
  20. Access the 'CareFabric Monitor' form.
  21. Enter the current date in the 'From Date' and 'Through Date' fields.
  22. Enter "Client A" in the 'Client ID' field.
  23. Enter "ServiceAuthorizationRequestCreated" in the 'Event/Action Search' field.
  24. Click [View Activity Log].
  25. Validate the 'CareFabric Monitor Report' contains the "ServiceAuthorizationRequestCreated" record.
  26. Click [Click to View Record].
  27. Validate the 'assignedCareManagerDate' field contains the date entered in the previous steps.
  28. Validate the 'assignedCareManagerID' - 'id' field contains care manager ID selected in the previous steps.
  29. Validate the 'benefitPlanCode' 'id' field contains the benefit plan ID for the client.
  30. Validate the 'benefitPlanCode' 'displayName' field contains the benefit plan for the client.
  31. Validate the 'clientID' - 'id' field contains the client ID.
  32. Validate the 'comment' field contains the authorization comments entered in the previous steps.
  33. Validate the 'createdDate' field contains the authorization created date.
  34. Validate the 'endDate' field contains the authorization end date entered in the previous steps.
  35. Validate the 'fundingSourceCode' - 'code' field contains the funding source code for the client.
  36. Validate the 'fundingSourceCode' - 'displayName' field contains the funding source for the client.
  37. Validate the 'providerID' - 'id' field contains the provider ID selected.
  38. Validate the 'requestedItems' - 'unit' field contains "CPT".
  39. Validate the 'requestedItems' - 'unitCode' - 'code' field contains the CPT code selected.
  40. Validate the 'requestedItems' - 'unitCode' - 'displayName' field contains the value of the CPT code selected.
  41. Validate the 'requestedItems' - 'value' field contains the amount of requested units.
  42. Validate the second 'requestedUnits' - 'unit' field contains "Revenue".
  43. Validate the second 'requestedUnits' - 'unitCode' - 'code' field contains the revenue code selected.
  44. Validate the second 'requestedUnits' - 'unitCode' - 'displayName' field contains the value of the revenue code selected.
  45. Validate the second 'requestedUnits' - 'value' contains the amount of requested units.
  46. Validate the 'serviceAuthorizationRequestID' - 'id' field contains a unique id for the request (ex. 87||||1).
  47. Validate the 'serviceAuthorizationRequestID' - 'scopeID' field contains the scope being used.
  48. Validate the 'startDate' field contains the authorization start date entered in the previous steps.
  49. Validate the 'statusCode' - 'id' field contains "P".
  50. Validate the 'statusCode' - 'displayName' field contains "Pending".
  51. Close the report and the form.
  52. Select "Client A" and access the 'Service Authorization Request' form.
  53. Select the service authorization request filed in the previous steps and click [Edit].
  54. Enter any new value in the 'Requested Units (1)' field.
  55. Enter any new value in the 'Requested Units (2)' field.
  56. Select the "Comments" section.
  57. Enter any new value in the 'Comments On Authorization' field.
  58. Click [Submit] and [No] to exit the form.
  59. Access the 'CareFabric Monitor' form.
  60. Enter the current date in the 'From Date' and 'Through Date' fields.
  61. Enter "Client A" in the 'Client ID' field.
  62. Enter "ServiceAuthorizationRequestUpdated" in the 'Event/Action Search' field.
  63. Click [View Activity Log].
  64. Validate the 'CareFabric Monitor Report' contains the "ServiceAuthorizationRequestUpdated" record.
  65. Click [Click to View Record].
  66. Validate the 'comments' field contains the new value entered.
  67. Validate the 'requestedItems' - 'value' field contains new requested value.
  68. Validate the second 'requestedItems' - 'value' field contains new requested value.
  69. Validate the 'serviceAuthorizationRequestID' - 'id' field contains a unique id for the request (ex. 87||||1).
  70. Validate the 'serviceAuthorizationRequestID' - 'scopeID' field contains the scope being used.
  71. Close the report and the form.
Scenario 2: Service Authorization - Validate the 'ServiceAuthorizationResponseCreated' and 'ServiceAuthorizationResponseUpdated' events
Specific Setup:
  • A member must be defined in the 'Member Enrollment' form (Client A).
  • CPT Codes and Revenue Codes must be defined in Avatar MSO.
  • Please note: this scenario is for Avatar Cal-PM systems only.
Steps
  1. Select "Client A" and access the 'Service Authorization' form.
  2. Select the desired provider in the 'Provider To Be Authorized' field.
  3. Select "Approved" in the 'Current Authorization Status' field.
  4. Enter the desired date in the 'Begin Date Of Authorization' field.
  5. Enter the desired date in the 'End Date Of Authorization' field.
  6. Select "Individual" in the 'Authorization Grouping or Individual Authorizations' field.
  7. Select "CPT Code" in the 'Procedure Code Type (1)' field.
  8. Enter the desired CPT Code in the 'Code Authorized (1)' field.
  9. Enter the desired value in the 'Requested Units (1)' field.
  10. Enter the desired value in the 'Units Authorized (1)' field.
  11. Select "Revenue Code" in the 'Procedure Code Type (1)' field.
  12. Enter the desired Revenue Code in the 'Code Authorized (1)' field.
  13. Enter the desired value in the 'Requested Units (1)' field.
  14. Enter the desired value in the 'Units Authorized (1)' field.
  15. Select the "Care Manager" section.
  16. Enter the desired care manager in the 'Care Manager Assigned' field.
  17. Enter the desired date in the 'Date Care Manager Assigned' field.
  18. Select the "Comments" section.
  19. Enter the desired value in the 'Comments On Authorization' field.
  20. Click [Submit] and [No] to exit the form.
  21. Access the 'CareFabric Monitor' form.
  22. Enter the current date in the 'From Date' and 'Through Date' fields.
  23. Enter "Client A" in the 'Client ID' field.
  24. Enter "ServiceAuthorizationResponseCreated" in the 'Event/Action Search' field.
  25. Click [View Activity Log].
  26. Validate the 'CareFabric Monitor Report' contains the "ServiceAuthorizationResponseCreated" record.
  27. Click [Click to View Record].
  28. Validate the 'assignedCareManagerDate' field contains the date entered in the previous steps.
  29. Validate the 'assignedCareManagerID' - 'id' field contains care manager ID selected in the previous steps.
  30. Validate the 'benefitPlanCode' 'id' field contains the benefit plan ID for the client.
  31. Validate the 'benefitPlanCode' 'displayName' field contains the benefit plan for the client.
  32. Validate the 'clientID' - 'id' field contains the client ID.
  33. Validate the 'comment' field contains the authorization comments entered in the previous steps.
  34. Validate the 'createdDate' field contains the authorization created date.
  35. Validate the 'endDate' field contains the authorization end date entered in the previous steps.
  36. Validate the 'fundingSourceCode' - 'code' field contains the funding source code for the client.
  37. Validate the 'fundingSourceCode' - 'displayName' field contains the funding source for the client.
  38. Validate the 'providerID' - 'id' field contains the provider ID selected.
  39. Validate the 'requestedItems' - 'unit' field contains "CPT".
  40. Validate the 'requestedItems' - 'unitCode' - 'code' field contains the CPT code selected.
  41. Validate the 'requestedItems' - 'unitCode' - 'displayName' field contains the value of the CPT code selected.
  42. Validate the 'requestedItems' - 'value' field contains the amount of authorized units.
  43. Validate the second 'requestedUnits' - 'unit' field contains "Revenue".
  44. Validate the second 'requestedUnits' - 'unitCode' - 'code' field contains the revenue code selected.
  45. Validate the second 'requestedUnits' - 'unitCode' - 'displayName' field contains the value of the revenue code selected.
  46. Validate the second 'requestedUnits' - 'value' contains the amount of authorized units.
  47. Validate the 'serviceAuthorizationRequestID' - 'id' field contains a unique id for the request (ex. 87||||1).
  48. Validate the 'serviceAuthorizationRequestID' - 'scopeID' field contains the scope being used.
  49. Validate the 'serviceAuthorizationResponseID' - 'id' field contains a unique id for the response (ex. 87||||1).
  50. Validate the 'serviceAuthorizationResponseID' - 'scopeID' field contains the scope being used.
  51. Validate the 'startDate' field contains the authorization start date entered in the previous steps.
  52. Validate the 'statusCode' - 'id' field contains "A".
  53. Validate the 'statusCode' - 'displayName' field contains "Approved".
  54. Close the report and the form.
  55. Select "Client A" and access the 'Service Authorization Request' form.
  56. Select the service authorization request filed in the previous steps and click [Edit].
  57. Select "Denied" in the 'Current Authorization Status' field.
  58. Enter "0" in the 'Units Authorized (1)' field.
  59. Enter "0" in the 'Units Authorized (2)' field.
  60. Select the "Comments" section.
  61. Enter any new value in the 'Comments On Authorization' field.
  62. Click [Submit] and [No] to exit the form.
  63. Access the 'CareFabric Monitor' form.
  64. Enter the current date in the 'From Date' and 'Through Date' fields.
  65. Enter "Client A" in the 'Client ID' field.
  66. Enter "ServiceAuthorizationResponseUpdated" in the 'Event/Action Search' field.
  67. Click [View Activity Log].
  68. Validate the 'CareFabric Monitor Report' contains the "ServiceAuthorizationResponseUpdated" record.
  69. Click [Click to View Record].
  70. Validate the 'comments' field contains the new value entered.
  71. Validate the 'requestedItems' - 'value' field contains "0".
  72. Validate the second 'requestedItems' - 'value' field contains "0".
  73. Validate the 'serviceAuthorizationRequestID' - 'id' field contains a unique id for the request (ex. 87||||1).
  74. Validate the 'serviceAuthorizationRequestID' - 'scopeID' field contains the scope being used.
  75. Validate the 'serviceAuthorizationResponseID' - 'id' field contains a unique id for the response (ex. 87||||1).
  76. Validate the 'serviceAuthorizationResponseID' - 'scopeID' field contains the scope being used.
  77. Validate the 'statusCode' - 'code' field contains "D".
  78. Validate the 'statusCode' - 'displayName' field contains "Denied".
  79. Close the report and the form.
Topics
• Service Authorizations • ProviderConnect Enterprise
Update 3 Summary | Details
CarePOV Management - 'Duplicate Name - Header' alert type
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
  • Diagnosis
  • Update Client Data
  • Orders This Episode
  • Pre-Display Confirmation
Scenario 1: CarePOV Management - Client Alerts - 'Duplicate Name - Header' alert type 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 has access to the 'Client Information Header' on the HomeView.
  • Two clients are defined with the same first & last name (Client A & Client B).
  • A third client is defined with a different first & last name (Client C).
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. Validate the 'Base Duplicate Name Alert On' field is now enabled and required.
  6. Select "Full Name (First and Last)" in the 'Base Duplicate Name On' field.
  7. Enter the desired value in the 'Client Alert Description' field.
  8. Select the desired icon in the 'Select Icon' field.
  9. Select "Yes" in the 'Active' field.
  10. Select "Yes" in the 'Include in Client Header' field.
  11. Click [Save].
  12. Validate a message is displayed stating: Saved.
  13. Click [OK] and close the form.
  14. Select "Client A" and navigate to the 'Client Information Header'.
  15. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  16. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  17. Select "Client B" and navigate to the 'Client Information Header'.
  18. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  19. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  20. Select "Client C" and navigate to the 'Client Information Header'.
  21. Validate the duplicate name alert is not displayed.
Scenario 2: CarePOV Management - Client Alerts - 'Duplicate Name - Header' alert type 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 has access to the 'Client Information Header' on the HomeView.
  • Two clients are defined with the same first name & last initial (Client A & Client B).
  • A third client is defined with a different first name & last initial (Client C).
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. Validate the 'Base Duplicate Name Alert On' field is now enabled and required.
  6. Select "First Name, Last Initial" in the 'Base Duplicate Name On' field.
  7. Enter the desired value in the 'Client Alert Description' field.
  8. Select the desired icon in the 'Select Icon' field.
  9. Select "Yes" in the 'Active' field.
  10. Select "Yes" in the 'Include in Client Header' field.
  11. Click [Save].
  12. Validate a message is displayed stating: Saved.
  13. Click [OK] and close the form.
  14. Select "Client A" and navigate to the 'Client Information Header'.
  15. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  16. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  17. Select "Client B" and navigate to the 'Client Information Header'.
  18. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  19. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  20. Select "Client C" and navigate to the 'Client Information Header'.
  21. Validate the duplicate name alert is not displayed.
Scenario 3: CarePOV Management - Client Alerts - 'Duplicate Name - Header' alert type 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 has access to the 'Client Information Header' on the HomeView.
  • Two clients are defined with the same last name & first initial (Client A & Client B).
  • A third client is defined with a different last name & first initial (Client C).
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. Validate the 'Base Duplicate Name Alert On' field is now enabled and required.
  6. Select "Last Name, First Initial" in the 'Base Duplicate Name On' field.
  7. Enter the desired value in the 'Client Alert Description' field.
  8. Select the desired icon in the 'Select Icon' field.
  9. Select "Yes" in the 'Active' field.
  10. Select "Yes" in the 'Include in Client Header' field.
  11. Click [Save].
  12. Validate a message is displayed stating: Saved.
  13. Click [OK] and close the form.
  14. Select "Client A" and navigate to the 'Client Information Header'.
  15. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  16. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  17. Select "Client B" and navigate to the 'Client Information Header'.
  18. Validate the icon associated to the duplicate name alert added in the previous steps is displayed.
  19. Hover over the icon and validate the 'Client Alert Description' added in the previous steps is displayed.
  20. Select "Client C" and navigate to the 'Client Information Header'.
  21. Validate the duplicate name alert is not displayed.
Scenario 4: CarePOV Management - Client Alerts - Field Validations
Steps
  1. Access the 'CarePOV Management' form.
  2. Select the "Client Alerts" section.
  3. Click "Add" in the 'Add or Edit Alert' field.
  4. Validate "Duplicate Name - Header" is displayed in the 'Alert Type' field.
  5. Validate the previous "Duplicate Name" alert has been renamed as "Duplicate Name - BedBoard" in the 'Alert Type' field.
  6. Validate the 'Base Duplicate Name Alert On' field is displayed and initially disabled. This field will become enabled/required when the "Duplicate Name - Header" alert type is selected.
  7. Validate the 'Base Duplicate Name Alert On' field contains the following values: "First Name, Last Initial", "Full Name (First and Last)", and "Last Name, First Initial".
  8. Select "Duplicate Name - Header" in the 'Alert Type' field.
  9. Validate the 'Base Duplicate Name Alert On' field is now enabled and required.
  10. Select the desired value in the 'Base Duplicate Name Alert On' field.
  11. Enter the desired value in the 'Client Alert Description' field.
  12. Select the desired icon in the 'Select Icon' field.
  13. Select "Yes" in the 'Active' field.
  14. Select "Yes" in the 'Include in Client Header' field.
  15. Click [Save].
  16. Validate a message is displayed stating: Saved.
  17. Click [OK].
  18. Select "Edit" in the 'Add or Edit Alert' field.
  19. Select the alert added in the previous steps in the 'Client Alert' field.
  20. Validate all previously filed data is displayed.
  21. Close the form.
Topics
• Client Alerts • CarePOV Management
Update 4 Summary | Details
Avatar CareFabric - 'GetOrganization' SDK action
Scenario 1: Validate the 'GetOrganization' payload
Steps

Internal testing only.
Topics
• CareFabric
Update 7 Summary | Details
Flowsheet - Administered Medications
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Flowsheet
Scenario 1: Flowsheet - Validate display of medications in the 'Graph' section
Specific Setup:
  • A client is enrolled in an existing episode (Client A) with the following:
  • Active medications that have been administered via Avatar eMAR with different administration dosage amounts.
Steps
  1. Navigate to the 'Flowsheet' application.
  2. Select "Client A" and navigate to the "Graph" section.
  3. Select the "Meds" sub-section.
  4. Validate the list of active medications for "Client A" are displayed.
  5. Select an administered medication.
  6. Validate the graph displays the appropriate data including:
  7. Recorded administration date/time
  8. Dosage
  9. Units
  10. Validate the graph points are displayed as expected.
Topics
• Active Medications
2022 Update 90 Summary | Details
ProviderConnect Enterprise - 'Diagnosis' data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Diagnosis
  • Women's Health History
Scenario 1: ProviderConnect Enterprise - Validate the 'PutDiagnosis' and 'PutDiagnosisEntry' actions
Specific Setup:
  • The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
  • The 'Managing Organization Definition' form must be defined for a valid managing organization.
  • A client must be enrolled in an existing episode and be mapped to the defined managing organization in the 'ProviderConnect Enterprise Identifiers' section of the 'Admission' form (Client A).
  • A practitioner must have a NPI that is mapped to a matching practitioner in the managing organization's system (Practitioner A).
Steps
  1. Select "Client A" and access the 'Diagnosis' form.
  2. Select the episode mapped to the managing organization from the Pre-Display.
  3. Click [OK].
  4. Select the desired value in the 'Type Of Diagnosis' field.
  5. Enter the desired date in the 'Date Of Diagnosis' field.
  6. Enter the desired time in the 'Time Of Diagnosis' field.
  7. Click [New Row].
  8. Enter the desired value in the 'Diagnosis Search' field.
  9. Validate the 'Ranking' field contains "Primary".
  10. Enter "Practitioner A" in the 'Diagnosing Practitioner' field.
  11. Select the "Additional Diagnosis Information" section.
  12. Select the desired value in the 'Trauma (CSI)' field.
  13. Select the desired value(s) in the 'General Medical Condition Summary Code (CSI)' field.
  14. Select "Yes" in the 'Substance Abuse / Dependence (CSI)' field.
  15. Select the desired value in the 'Substance Abuse / Dependence Diagnosis (CSI)' field.
  16. Click [Submit].
  17. Validate a "Pre-Display Confirmation" message is displayed stating: Do you want to return to Pre-Display?
  18. Click [No].
  19. Access the 'ProviderConnect Enterprise Action Log'.
  20. Enter the desired dates in the 'From Date' and 'Through Date' fields.
  21. Enter the desired times in the 'From Time' and 'Through Time' fields.
  22. Select the desired organization in the 'Managing Organization' field.
  23. Select "PutDiagnosis" in the 'Action Name' field.
  24. Click [View Action Log].
  25. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  26. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutDiagnosis' action that was triggered from the 'Diagnosis' form with a "Success" result.
  27. Close the report.
  28. Select "PutDiagnosisEntry" in the 'Action Name' field.
  29. Click [View Action Log].
  30. Validate the 'ProviderConnect Enterprise Action Log' Report is displayed.
  31. Validate the 'ProviderConnect Enterprise Action Log' Report contains the 'PutDiagnosisEnry' action that was triggered from the 'Diagnosis' form with a "Success" result.
  32. Close the report and the form.
Topics
• Diagnosis • ProviderConnect Enterprise