Skip to main content

Avatar Cal-PM 2023 Monthly Release 2023.02.02 Acceptance Tests

  1. Last updated
  2. Save as PDF
Update 7 Summary | Details
Avatar Cal-PM 'Cal-OMS Discharge' and 'Cal-OMS Annual Update' Forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Cal-OMS File Import
  • Cal-OMS Annual Update
  • Cal-OMS Discharge
  • Cal-OMS Discharge Web Service
Scenario 1: 'Cal-OMS File Import' - Verification of Import File Processing
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' must be enabled (set to 'YC' or 'Y')
  • One or more client(s) with episodes eligible for 'Cal-OMS Annual Update'/'Cal-OMS Discharge' record filing via import
  • 'Cal-OMS File Import' file containing one or more valid Cal-OMS Annual Update and/or Cal-OMS Discharge import data rows including information/values for the following fields/segments:
  • 'Has the client been linked to a stable housing during treatment?'
  • 'If no, explain'
  • 'If yes, what is the permanent housing arrangement?'
  • 'Specify Other'
  • 'Zip Code'
Steps
  1. Open Avatar Cal-PM 'Cal-OMS File Import' form.
  2. Select 'Upload New File' action and click 'Process Action' button.
  3. Load import file containing one or more valid Cal-OMS Annual Update and/or Cal-OMS Discharge import data row(s).
  4. Select 'Compile File' action and click 'Process Action' button.
  5. Click 'OK' button in file compilation confirmation dialog.
  6. Select 'Print Compilation Error(s)' action and click 'Process Action' button.
  7. Ensure that valid Cal-OMS Annual Update/Cal-OMS Discharge import data row(s) are successfully compiled.
  8. Click 'OK' button in file compilation confirmation dialog.
  9. Select 'Post File' action and click 'Process Action' button.
  10. Click 'OK' button in file compilation confirmation dialog.
  11. Open 'Cal-OMS Annual Update' or 'Cal-OMS Discharge' form for client with posted import row.
  12. In 'Cal-OMS Annual Update' or 'Cal-OMS Discharge' pre-display, select record posted via 'Cal-OMS File Import'.
  13. Click 'Edit' button.
  14. In 'Cal-OMS Annual Update' or 'Cal-OMS Discharge' form, ensure values are correct/expected value from import file data for the following stable/permanent housing information fields:
  • 'Has the client been linked to a stable housing during treatment?'
  • 'If no, explain'
  • 'If yes, what is the permanent housing arrangement?'
  • 'Specify Other'
  • 'Zip Code'
Scenario 2: 'Cal-OMS Discharge' - Form Verification
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' must be enabled (set to 'YC' or 'Y')
  • One or more client(s) with episodes eligible for 'Cal-OMS Discharge' record filing
  • Crystal Reports or other SQL reporting tool
Steps
  1. Open Avatar Cal-PM 'Cal-OMS Discharge' form.
  2. Select client record/Cal-OMS Admission episode for Cal-OMS Discharge entry/edit.
  3. Click 'Add' button to enter new Cal-OMS Discharge record, or select existing Cal-OMS Discharge record for view/edit in pre-display and click 'Edit' button.
  4. Navigate to the 'Family/Social Data' section of form.
  5. Ensure the following fields are present in form (related to the 'Has the client been linked to a stable housing during treatment?' field/question):
  6. 'If yes, what is the permanent housing arrangement?'
  7. Selections/values available:
  8. 'Rental by client, no ongoing housing subsidy'
  9. 'Rental by client, with ongoing housing subsidy'
  10. 'Staying or living with family, permanent tenure'
  11. 'Staying or living with friends, permanent tenure'
  12. 'Other: specify'
  13. 'Specify Other'
  14. 'Zip Code'
  15. Ensure that if 'No' is selected in the 'Has the client been linked to a stable housing during treatment?' field, stable/permanent housing information fields noted above are disabled (and 'If no, explain' field is enabled for entry).
  16. Ensure that if 'Yes' is selected in the 'Has the client been linked to a stable housing during treatment?' field, stable/permanent housing information fields noted above are enabled for entry.
  17. Ensure that if 'Other: specify' is selected in the 'If yes, what is the permanent housing arrangement?' field, 'Specify Other' field is enabled for entry.
  18. Enter/select values for stable/permanent housing information fields noted above.
  19. Enter/select values for all other 'Cal-OMS Discharge' form fields as required/desired.
  20. Click 'Submit' button to file 'Cal-OMS Discharge' form/record.
  21. Open Crystal Reports or other SQL reporting tool.
  22. In Avatar Cal-PM SQL table 'SYSTEM.cal_oms_discharge', ensure that the following fields are present and reflect data filed via 'Cal-OMS Discharge' form:
  23. 'permanent_housing_code'
  24. 'permanent_housing_value'
  25. 'permanent_housing_zip'
  26. 'permanent_housing_other'
Scenario 3: 'Cal-OMS Annual Update' - Form Verification
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' must be enabled (set to 'YC' or 'Y')
  • One or more client(s) with episodes eligible for 'Cal-OMS Annual Update' record filing
  • Crystal Reports or other SQL reporting tool
Steps
  1. Open Avatar Cal-PM 'Cal-OMS Annual Update' form.
  2. Select client record/Cal-OMS Admission episode for Cal-OMS Annual Update entry/edit.
  3. Click 'Add' button to enter new Cal-OMS Annual Update record, or select existing Cal-OMS Annual Update record for view/edit in pre-display and click 'Edit' button.
  4. Navigate to the 'Family/Social Data' section of form.
  5. Ensure the following fields are present in form (related to the 'Has the client been linked to a stable housing during treatment?' field/question):
  6. 'If yes, what is the permanent housing arrangement?'
  7. Selections/values available:
  8. 'Rental by client, no ongoing housing subsidy'
  9. 'Rental by client, with ongoing housing subsidy'
  10. 'Staying or living with family, permanent tenure'
  11. 'Staying or living with friends, permanent tenure'
  12. 'Other: specify'
  13. 'Specify Other'
  14. 'Zip Code'
  15. Ensure that if 'No' is selected in the 'Has the client been linked to a stable housing during treatment?' field, stable/permanent housing information fields noted above are disabled (and 'If no, explain' field is enabled for entry).
  16. Ensure that if 'Yes' is selected in the 'Has the client been linked to a stable housing during treatment?' field, stable/permanent housing information fields noted above are enabled for entry.
  17. Ensure that if 'Other: specify' is selected in the 'If yes, what is the permanent housing arrangement?' field, 'Specify Other' field is enabled for entry.
  18. Enter/select values for stable/permanent housing information fields noted above.
  19. Enter/select values for all other 'Cal-OMS Annual Update' form fields as required/desired.
  20. Click 'Submit' button to file 'Cal-OMS Annual Update' form/record.
  21. Open Crystal Reports or other SQL reporting tool.
  22. In Avatar Cal-PM SQL table 'SYSTEM.cal_oms_annual_update', ensure that the following fields are present and reflect data filed via 'Cal-OMS Annual Update' form:
  23. 'permanent_housing_code'
  24. 'permanent_housing_value'
  25. 'permanent_housing_zip'
  26. 'permanent_housing_other'
Scenario 4: Cal-OMS Discharge Web Service - Verification of Web Service Filing
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' must be enabled (set to 'YC' or 'Y')
  • Application utilizing the Avatar Cal-PM 'Cal-OMS Discharge' web service
  • One or more client(s) with episodes eligible for 'Cal-OMS Discharge' record filing
Steps
  1. Using the 'Cal-OMS Discharge' web service (and/or 'Cal-OMS Discharge V2' web service), submit request to 'FileCalOMSDischarge' method to create or update Cal-OMS Discharge record.
  2. Confirm 'Cal-OMS Discharge' web service responds with confirmation data/ID on successful filing of 'FileCalOMSDischarge' method.
  3. Example:"<Confirmation>ClientID:111||EP:1||UniqueID:OMD.001</Confirmation>"
  4. Confirm 'Cal-OMS Discharge' web service responds with confirmation message on successful filing of 'FileCalOMSDischarge' method.
  5. Example:"<Message>Cal-OMS Discharge web service has been filed successfully.</Message>"
  6. Confirm 'Cal-OMS Discharge' web service responds with successful status value on successful filing of 'FileCalOMSDischarge' method.
  7. Example:"<Status>1</Status>"
  8. Open Avatar Cal-PM 'Cal-OMS Discharge' form and select client/episode/Cal-OMS Discharge record filed via web service for view/update.
  9. Confirm Cal-OMS Discharge record is created/updated in Avatar Cal-PM, with values/data submitted via web service, including the following fields:
  10. 'Has the client been linked to a stable housing during treatment?' ('LinkedToStableHousing')
  11. 'If yes, what is the permanent housing arrangement?' ('PermanentHousingArrange')
  12. 'Specify Other' ('PermanentHousingOther')
  13. 'Zip Code' ('PermanentHousingArrZip')
Topics
• Cal-OMS • NX • Registry Settings • Web Services
Update 31 Summary | Details
Console Widget Viewer
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Leaves
Scenario 1: 'Console Widget Viewer' - 'Diagnosis' and 'Return From Leaves' forms.
Specific Setup:
  • Tester has access to the 'Console Widget Viewer'.
  • The 'Diagnosis' and 'Return From Leaves' forms have been added to the 'Console Widget Viewer'.
  • Client A: Client has a diagnosis record. The client was placed on ‘Leave’ and has a 'Return From Leaves' record.
Steps
  1. Access the 'Console Widget Viewer' for the client.
  2. Verify that the 'Diagnosis' record displays correctly.
  3. Verify that the 'Return From Leaves' record displays correctly.
  4. Return to homeview.
Topics
• Console Widget • NX
Update 40 Summary | Details
Cal-OMS Discharge
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
  • ClosedEpisodecheck
  • Cal-OMS Discharge
Scenario 1: Cal-OMS Discharge - file a discharge
Specific Setup:
  • The myAvatar Cal-PM system is setup for LASAPCS and enables multiple Cal-OMS admissions.
  • Client A is admitted to a program that supports Cal-OMS.
  • One or more Cal-OMS admissions exist for the client. Note the value of the 'Cal-OMS Type of Service' field.
  • To test that the Cal-OMS Discharge field 'Mental Health Medication In The Last 30 Days' does not allow selection of 'Client unable to answer', please use a value other than "Nonresidential/Outpatient Detoxification" (3), "Residential Detoxification (hospital)" (4), or "Residential Detoxification (non-hospital)" (5), or 'Disability, "Developmentally Disabled".
  • Client B is admitted to a program that supports Cal-OMS.
  • One or more Cal-OMS admissions exist for the client. Note the value of the 'Cal-OMS Type of Service' field.
  • To test that the Cal-OMS Discharge field 'Mental Health Medication In The Last 30 Days' does allow selection of 'Client unable to answer', please use one of the following values: "Nonresidential/Outpatient Detoxification" (3), "Residential Detoxification (hospital)" (4), or "Residential Detoxification (non-hospital)" (5), or 'Disability, "Developmentally Disabled".
Steps
  1. Open ‘Cal-OMS Discharge’ for Client A.
  2. Fill in desired data for the form.
  3. Select ‘'Client unable to answer.' in the ‘Mental Health Medication In The Last 30 Days' field.
  4. Validate that a message is received stating: Cannot select 'Client unable to answer' unless the Cal-OMS Type of Service is 'Nonresidential / Outpatient Detoxification ' (3), 'Residential Detoxification (hospital)' (4), or 'Residential Detoxification (non-hospital)' (5), or 'Disability' on the corresponding Cal-OMS Admission form is 'Developmentally Disabled'.
  5. Click [OK].
  6. Select a different value in the ‘Mental Health Medication In The Last 30 Days' field.
  7. Submit the form.
  8. Open ‘Cal-OMS Discharge’ for Client B.
  9. Fill in desired data for the form.
  10. Select ‘'Client unable to answer.' in the ‘Mental Health Medication In The Last 30 Days' field.
  11. Validate that no message is received.
  12. Submit the form.
Topics
• Cal-OMS
Update 41 Summary | Details
Compile/Edit/Post/Unpost Roll-Up Services Worklist
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Fee/Cross Reference Maintenance
  • Guarantors/Payors
  • Practitioner Numbers By Guarantor and Program
  • Client Ledger
  • Roll-Up Services Definition
  • Compile/Edit/Post/Unpost Roll-Up Services Worklist
  • Financial Eligibility
Scenario 1: Roll-Up Services Definition - Service Codes are User Defined with Durations
Specific Setup:
  • Roll-Up Services Definition:
  • The definition contains services that use a ‘Duration Range’ in the 'Service Fee/Cross Reference Maintenance' definition. Note the service code for the roll-up services, and the codes for the component services.
  • Client A: Has ‘component service codes’ that are within the ‘Duration Range’, and some that are not in the ‘Duration Range’. The services are ready for the ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’ process.
Steps
  1. Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
  2. Enter the desired values to process the compile for the ‘Roll-Up Services Definition’.
  3. Review the report to ensure the data is correct.
  4. Post the Roll-Up Services Worklist’.
  5. Close the form.
  6. Open ‘Client Ledger’ and validate that the roll-up process correctly processed the services and fees.
  7. Close the form.
Topics
• Roll-Up Service Definition • Compile/Edit/Post/Unpost Roll-up Services Worklist • NX
Update 43 Summary | Details
Service Codes - Use Site or Service Based Appointment Color Coding
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Service Code Upload Process
  • Service Code Upload Accepted Codes (2)
  • Service Code Upload Rejected Codes (2)
  • Dictionary Update (PM)
  • Service Codes
Scenario 1: Registry Settings - Use Site or Service Based Appointment Color Coding
Steps
  • Internal testing only
Scenario 2: Cal-PM - Service Code Upload Process - workflow and form validation
Specific Setup:
  • 'Testing File 1'
  • All columns will contain valid values.
  • Note the values for the following columns for verification purposes:
  • Service Code
  • Service Code Definition
  • Should This Visit Be Included On The CCD
  • Save the file locally with a '.txt' extension.
  • 'Testing File 2'
  • All columns will contain valid values, except column 131, ‘Should This Visit Be Included On The CCD?’.
  • In 'Should This Visit Be Included On The CCD?' put "Y" and in 'Is This Service a Visit' put "N" which disables the 'Should This Visit Be Included On The CCD?' field.
  • Save the file locally with a '.txt' extension.
  • 'Testing File 3'
  • The file contains 1 valid row for the Accepted Report and 2 for the Rejected report.
  • Save the file locally with a '.txt' extension.
Steps
  1. Open the 'Service Code Upload Process' form.
  2. Enter the file path for "Testing File 1" in the 'Filename' field.
  3. Select "Compile" in the 'Compile Or Post' field.
  4. Select desired value in the 'Override Existing Service Code' field.
  5. Click [Submit].
  6. Verify that a "Submitting" message is displayed which states: Compile completed. To review results, review accepted report.
  7. Leave the form open.
  8. Access the 'Service Code Upload Accepted Codes' form.
  9. Select "Testing File 1" in the 'Select Desired Service Code Import File Name' field.
  10. Click [Process].
  11. Verify that the 'Service Code Upload Accepted Report' displays.
  12. Verify the data matches the data in "Testing File 1" for: 'Service Code', 'Service Code Definition' and 'Should This Visit Be Included On The CCD'.
  13. Close the report and the form.
  14. Return to the open 'Service Code Upload Process' form.
  15. Select 'Post' in the 'Compile Or Post' field.
  16. Select desired value in the 'Override Existing Service Code' field.
  17. Click [Submit] and close the form.
  18. Access the 'Service Codes' form.
  19. Select "Edit" in the 'Add New or Edit Existing' field.
  20. Enter the service code from "Testing File 1" in the 'Service Code' field.
  21. Verify the data matches the data in "Testing File 1" for: 'Service Code Definition' and 'Should This Visit Be Included On The CCD?'.
  22. Close the form.
  23. Access the 'Service Code Upload Process' form.
  24. Enter the file path for "Testing File 2" in the 'Filename' field.
  25. Select "Compile" in the 'Compile Or Post' field.
  26. Select desired value in the 'Override Existing Service Code' field.
  27. Click [Submit].
  28. Verify that a "Submitting" message is displayed which states: Compile completed. To review results review rejected report.
  29. Leave the form open.
  30. Access the 'Service Code Upload Rejected Codes' form.
  31. Select "Testing File 2" in the 'Select Desired Service Code Import File Name' field.
  32. Click [Process].
  33. Verify that the 'Service Code Upload Rejected Report' displays.
  34. Validate that the 'Should This Visit Be Included On The CCD?' error message states: Due To 'Is This Service A Visit' Invalid Entry: 'Should This Visit Be Included On The CCD?' cannot be set when this field is not set to "Y".
  35. Close the report and the form.
  36. Access the 'Service Codes' form.
  37. Select "Edit" in the 'Add New or Edit Existing' field.
  38. Enter the service code from "Testing File 2" in the 'Service Code' field.
  39. Verify that the service code does not exist.
  40. Close the form.
  41. Access the "Service Code Upload Process" form.
  42. Enter the file path for "Testing File 3" in the 'Filename' field.
  43. Select "Compile" in the "Compile or Post" field.
  44. Click [Submit].
  45. Leave this form open.
  46. Access the "Service Code Upload Accepted Codes" form.
  47. Set the "Select Desired Service Code Import File Name" to Testing File 3.
  48. Click [Process].
  49. Validate "Service Code" from the report matches the first column in Testing File 3.
  50. Validate "Service Code Description" from the report matches the third column in Testing File 3
  51. Validate "Group Code" from the report matches the 11th column in Testing File 3.
  52. Validate "Insurance Charge Category" from the report matches the 12th column in Testing File 3.
  53. Validate "Is This Service A Visit" matches the 16th column in Testing File 3.
  54. Validate "Is this an ODS Group Service" matches the 132nd column of Testing File 3.
  55. Close the report and the form.
  56. Access the "Service Code Upload Rejected Code" form.
  57. Set the "Select Desired Service Code Import File Name" to Testing File 3.
  58. Click [Process].
  59. Validate 2 rows in the same file are listed as rejected.
  60. Close the report.
  61. Return to the open "Service Code Upload Process" form.
  62. Select "Post" in "Compile or Post" field.
  63. Click [Submit].
  64. Access the "Service Codes" form.
  65. Edit the "Service Code" from the "Service Code" from column 1 in Testing File 3.
  66. Validate the "Service Code Definition" matches column 3 in Testing File 3.
  67. Validate the "Group Code" matches column 11 in Testing File 3.
  68. Validate the "Insurance Coverage Category" matches column 12 in Testing File 3.
  69. Validate "Is This Service A Visit" matches column 16 in Testing File 3.
  70. Validate "Is This an ODS Group Service" matches column 132 in Testing File 3.
  71. Close report.
  72. Close all forms.
Topics
• Registry Settings • NX • Service Codes
Update 44 Summary | Details
ProviderConnect Enterprise - 'Sexual Orientation' data
Scenario 1: ProviderConnect Enterprise- Validate the 'PutProgramAdmission' action
Specific Setup:
  • The 'Avatar CareFabric->ProviderConnect Enterprise->Contracting Providers->->->Enable External Connections' must be set to "Y".
  • The 'Managing Organization Definition' form must be configured for a valid managing organization.
  • A client must exist in the configured managing organization's system with the following on file: 'Date of Birth', 'Social Security Number', 'Employment Status', 'Sexual Orientation', and 'Education' (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. Access the 'Admission' form.
  2. Verify the 'Select Client' dialog is displayed.
  3. Enter the last name of the client that exists in the managing organization's system in the 'Last Name' field.
  4. Enter the first name of the client that exists in the managing organization's system in the 'First Name' field.
  5. Enter the sex of the client that exists in the managing organization's system in the 'Sex' field.
  6. Click [Search].
  7. Validate a "Search Results" message is displayed stating: No matches found.
  8. Click [OK] and [New Client].
  9. Validate a "Client" message is displayed stating: Auto Assign Next ID Number?
  10. Click [Yes].
  11. Enter the desired date in the 'Preadmit/Admission Date' field.
  12. Enter the desired time in the 'Preadmit/Admission Time' field.
  13. Select any program that is selected in the 'Associated Admission Programs' field in the 'Managing Organization Definition' form in the 'Program' field.
  14. Select the desired value in the 'Type Of Admission' field.
  15. Select desired value in the 'Source Of Admission' field.
  16. Enter "Practitioner A" in the 'Admitting Practitioner' field.
  17. Select the "ProviderConnect Enterprise Identifiers" section.
  18. Click [Add New Item].
  19. Select the defined managing organization in the 'External Organization' field.
  20. Click [Search].
  21. Select the matching client record in the 'Select Matching Client Record' dialog.
  22. Click [OK].
  23. Validate the 'External ID' field contains the client ID for the client in the managing organization's system.
  24. Click [Update Demographics].
  25. Validate an "Information" message is displayed stating: Client Demographics Information Updated.
  26. Click [OK].
  27. Select the "Demographics" section.
  28. Validate demographic fields have been updated to match the managing organizations record.
  29. Validate the 'Education' field contains the value on file in the managing organization's system.
  30. Validate the 'Employment Status' field contains the value on file in the managing organization's system.
  31. Validate the 'Sexual Orientation' field contains the value on file in the managing organization's system.
  32. Select the "Admission" section.
  33. Validate the 'Date of Birth' field contains the value on file in the managing organization's system.
  34. Validate the 'Social Security Number' field contains the value on file in the managing organization's system.
  35. Click [Submit].
  36. Access the 'ProviderConnect Enterprise Action Log'.
  37. Enter the desired date in the 'From Date' and 'Through Date' fields.
  38. Enter the desired time in the 'From Time' and 'Through Time' fields.
  39. Select the desired organization in the 'Managing Organization' field.
  40. Select "PutProgramAdmission" in the 'Action Name' field.
  41. Click [View Action Log].
  42. Verify the 'ProviderConnect Enterprise Action Log' Report is displayed.
  43. Validate the 'ProviderConnect Enterprise Action Log' Report contains a row for the 'PutProgramAdmission' action that was triggered from the 'Admission' form with a result of "Success".
  44. Close the report and the form.
Topics
• Admission
Update 52 Summary | Details
Service Code Upload Process
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Spreadsheet Remittance Posting
  • Service Code Upload Process
  • Service Code Upload Accepted Codes (2)
  • Service Code Upload Rejected Codes (2)
Scenario 1: Validate 'Spreadsheet Remittance Posting' submission.
Specific Setup:
  • The following registry setting has a value of “Y”: Avatar PM->Billing->Client Charge Input->->->Include Start - End Times.
  • In “Client Lookup/Header Configuration Manager” set the “First Alternate Lookup” to “Subscriber Policy #”. This is in the “Alternate Lookup” section of the form.
  • Have a client with services that are rendered and distributed to a primary guarantor (Guarantor A), that need to be transferred to another guarantor, (Guarantor B).
  • Note the following for the eligibility records: “Coverage Effective Dates”, “Coverage Expiration Dates”, “Coverage Description”, “Level Start Date”, “Level End Date” and "Subscriber Policy Number". This information can be displayed in a popup window with hover functionality.
  • Note the service: “Practitioner/Provider name”, “Duration”, "Start Time", “End Time”, and “Service Code Definition”. This information can be displayed in a popup window with hover functionality.
Steps
  1. Open "Spreadsheet Remittance Posting".
  2. Enter the "Subscriber Policy Number" in "Client".
  3. Validate that the correct client is displayed in the results.
  4. Enter the "Client ID" in "Client".
  5. Validate that the correct client is displayed in the results.
  6. Select the client.
  7. Select the "Episode" pertaining to the services.
  8. Select the "Guarantor A" in "Guarantor To Post For".
  9. Click [OK] on the guarantor balance message.
  10. Enter a "Posting Date".
  11. Enter a "Date of Receipt".
  12. Click [Launch Work Screen].
  13. Select a row.
  14. Hover over "Service Date".
  15. Validate that a popup window displays the following: "Provider", "Duration", "Start Time", "End Time" and "Service Code".
  16. Enter desired value in "Payment Amount".
  17. Select desired "Payment Code".
  18. Enter desired value in "Transfer Amount".
  19. Hover over the "Transfer Guar" field.
  20. Validate that a popup window displays the following: "Active Guarantor", "Coverage Effective Date", "Coverage Expiration Date", "Level Start Date", and "Level End Date".
  21. Select "Guarantor B'' in "Transfer Guar".
  22. Validate that the "New Balance" is correct.
  23. Repeat payments and/or transfer for additional rows.
  24. Click [Accept].
  25. Click [Submit].
Scenario 2: Cal-PM - Service Code Upload Process - workflow and form validation
Specific Setup:
  • 'Testing File 1'
  • All columns will contain valid values.
  • Note the values for the following columns for verification purposes:
  • Service Code
  • Service Code Definition
  • Should This Visit Be Included On The CCD
  • Save the file locally with a '.txt' extension.
  • 'Testing File 2'
  • All columns will contain valid values, except column 131, ‘Should This Visit Be Included On The CCD?’.
  • In 'Should This Visit Be Included On The CCD?' put "Y" and in 'Is This Service a Visit' put "N" which disables the 'Should This Visit Be Included On The CCD?' field.
  • Save the file locally with a '.txt' extension.
  • 'Testing File 3'
  • The file contains 1 valid row for the Accepted Report and 2 for the Rejected report.
  • Save the file locally with a '.txt' extension.
Steps
  1. Open the 'Service Code Upload Process' form.
  2. Enter the file path for "Testing File 1" in the 'Filename' field.
  3. Select "Compile" in the 'Compile Or Post' field.
  4. Select desired value in the 'Override Existing Service Code' field.
  5. Click [Submit].
  6. Verify that a "Submitting" message is displayed which states: Compile completed. To review results, review accepted report.
  7. Leave the form open.
  8. Access the 'Service Code Upload Accepted Codes' form.
  9. Select "Testing File 1" in the 'Select Desired Service Code Import File Name' field.
  10. Click [Process].
  11. Verify that the 'Service Code Upload Accepted Report' displays.
  12. Verify the data matches the data in "Testing File 1" for: 'Service Code', 'Service Code Definition' and 'Should This Visit Be Included On The CCD'.
  13. Close the report and the form.
  14. Return to the open 'Service Code Upload Process' form.
  15. Select 'Post' in the 'Compile Or Post' field.
  16. Select desired value in the 'Override Existing Service Code' field.
  17. Click [Submit] and close the form.
  18. Access the 'Service Codes' form.
  19. Select "Edit" in the 'Add New or Edit Existing' field.
  20. Enter the service code from "Testing File 1" in the 'Service Code' field.
  21. Verify the data matches the data in "Testing File 1" for: 'Service Code Definition' and 'Should This Visit Be Included On The CCD?'.
  22. Close the form.
  23. Access the 'Service Code Upload Process' form.
  24. Enter the file path for "Testing File 2" in the 'Filename' field.
  25. Select "Compile" in the 'Compile Or Post' field.
  26. Select desired value in the 'Override Existing Service Code' field.
  27. Click [Submit].
  28. Verify that a "Submitting" message is displayed which states: Compile completed. To review results review rejected report.
  29. Leave the form open.
  30. Access the 'Service Code Upload Rejected Codes' form.
  31. Select "Testing File 2" in the 'Select Desired Service Code Import File Name' field.
  32. Click [Process].
  33. Verify that the 'Service Code Upload Rejected Report' displays.
  34. Validate that the 'Should This Visit Be Included On The CCD?' error message states: Due To 'Is This Service A Visit' Invalid Entry: 'Should This Visit Be Included On The CCD?' cannot be set when this field is not set to "Y".
  35. Close the report and the form.
  36. Access the 'Service Codes' form.
  37. Select "Edit" in the 'Add New or Edit Existing' field.
  38. Enter the service code from "Testing File 2" in the 'Service Code' field.
  39. Verify that the service code does not exist.
  40. Close the form.
  41. Access the "Service Code Upload Process" form.
  42. Enter the file path for "Testing File 3" in the 'Filename' field.
  43. Select "Compile" in the "Compile or Post" field.
  44. Click [Submit].
  45. Leave this form open.
  46. Access the "Service Code Upload Accepted Codes" form.
  47. Set the "Select Desired Service Code Import File Name" to Testing File 3.
  48. Click [Process].
  49. Validate "Service Code" from the report matches the first column in Testing File 3.
  50. Validate "Service Code Description" from the report matches the third column in Testing File 3
  51. Validate "Group Code" from the report matches the 11th column in Testing File 3.
  52. Validate "Insurance Charge Category" from the report matches the 12th column in Testing File 3.
  53. Validate "Is This Service A Visit" matches the 16th column in Testing File 3.
  54. Validate "Is this an ODS Group Service" matches the 132nd column of Testing File 3.
  55. Close the report and the form.
  56. Access the "Service Code Upload Rejected Code" form.
  57. Set the "Select Desired Service Code Import File Name" to Testing File 3.
  58. Click [Process].
  59. Validate 2 rows in the same file are listed as rejected.
  60. Close the report.
  61. Return to the open "Service Code Upload Process" form.
  62. Select "Post" in "Compile or Post" field.
  63. Click [Submit].
  64. Access the "Service Codes" form.
  65. Edit the "Service Code" from the "Service Code" from column 1 in Testing File 3.
  66. Validate the "Service Code Definition" matches column 3 in Testing File 3.
  67. Validate the "Group Code" matches column 11 in Testing File 3.
  68. Validate the "Insurance Coverage Category" matches column 12 in Testing File 3.
  69. Validate "Is This Service A Visit" matches column 16 in Testing File 3.
  70. Validate "Is This an ODS Group Service" matches column 132 in Testing File 3.
  71. Close report.
  72. Close all forms.
Topics
• Spreadsheet Remittance Posting • Service Codes
Update 53 Summary | Details
'CareConnect Inbox' - Referrals
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Ambulatory Progress Notes
  • Treatment Plan
  • Patient Health Questionnaire-9
  • CareConnect Inbox
  • Progress Notes (Group and Individual)
  • Care Connect Inbox
  • CareFabric Monitor
Scenario 1: 'CareConnect Inbox' POV - Send a referral with client attachments
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
  • "Client A" has the records on file for the following: 'Ambulatory Progress Notes', 'Progress Notes (Group and Individual)', 'Treatment Plan', and 'Patient Health Questionnaire-9'.
  • Must have access to the 'CareConnect Inbox' widget.
Steps
  1. Access the 'CareConnect Inbox' widget.
  2. Start a new referral.
  3. Select the desired contact in the 'Add Contact' field.
  4. Enter the desired value in the 'Subject' field.
  5. Search for and select the desired provider in the 'Provider Search' field.
  6. Search for and select "Client A" in the 'Client Search' field.
  7. Click [Attach CCD].
  8. Validate the generated CCD is displayed and click [Attach CCD].
  9. Click [Client Attachments].
  10. Select "Client A's" existing episode in the 'Episode' field.
  11. Select "Admission", "Ambulatory Progress Notes", "Progress Notes (Group and Individual)", "Treatment Plan", "Patient Health Questionnaire-9", and "Update Client Data" in the 'Forms to Attach' field.
  12. Click [Generate PDF].
  13. Validate all of the client attachment PDF's are displayed.
  14. Select the 'Admission' PDF.
  15. Validate the admission data is displayed.
  16. Select the 'Ambulatory Progress Notes' PDF.
  17. Validate the progress note data is displayed.
  18. Select the 'Progress Notes (Group and Individual)' PDF.
  19. Validate the progress note data is displayed.
  20. Select the 'Patient Health Questionnaire-9' PDF.
  21. Validate the assessment data is displayed.
  22. Select the 'Treatment Plan' PDF.
  23. Validate the treatment plan data is displayed.
  24. Select the 'Update Client Data' PDF.
  25. Validate the client data is displayed.
  26. Send the referral.
Topics
• CareConnect Inbox
Update 54 Summary | Details
Avatar Cal-PM - support for Integrated eSignature functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Discharge
  • Pre Admit
  • Pre Admit Discharge
Scenario 1: 'Admission' form - Field Validation
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Admission' form.
  2. Select an existing episode and click [Edit].
  3. Select the "Demographics" section.
  4. Validate the 'Consent On File For Use of Integrated eSignature' field is present with values of "Yes" and "No".
  5. Select "No" in the 'Consent On File For Use of Integrated eSignature' field.
  6. Click [Submit].
  7. Select "Client A" and access the 'Admission' form.
  8. Select an existing episode and click [Edit].
  9. Select the "Demographics" section.
  10. Validate "No" is selected in the 'Consent On File For Use of Integrated eSignature' field.
  11. Close the form.
  12. Access Crystal Reports or other SQL reporting tool.
  13. Create a report using the 'SYSTEM.patient_current_demographics' SQL table.
  14. Navigate to the row for "Client A".
  15. Validate the 'esig_consent_on_file_code' field is present and contains "N".
  16. Validate the 'esig_consent_on_file_value' field is present and contains "No".
  17. Close the report.
  18. Create a report using the 'SYSTEM.patient_demographic_history' SQL table.
  19. Navigate to the row for "Client A".
  20. Validate the 'esig_consent_on_file_code' field is present and contains "N".
  21. Validate the 'esig_consent_on_file_value' field is present and contains "No".
  22. Close the report.
Scenario 2: 'Update Client Data' form - Verification of 'Client Demographics' form fields
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Update Client Data' form.
  2. Validate the 'Consent On File For Use of Integrated eSignature' field is present with values of "Yes" and "No".
  3. Select "Yes" in the 'Consent On File For Use of Integrated eSignature' field.
  4. Click [Submit].
  5. Select "Client A" and access the 'Update Client Data' form.
  6. Validate "Yes" is selected in the 'Consent On File For Use of Integrated eSignature' field.
  7. Close the form.
  8. Access Crystal Reports or other SQL reporting tool.
  9. Create a report using the 'SYSTEM.patient_current_demographics' SQL table.
  10. Navigate to the row for "Client A".
  11. Validate the 'esig_consent_on_file_code' field is present and contains "Y".
  12. Validate the 'esig_consent_on_file_value' field is present and contains "Yes".
  13. Close the report.
  14. Create a report using the 'SYSTEM.patient_demographic_history' SQL table.
  15. Navigate to the row for "Client A".
  16. Validate the 'esig_consent_on_file_code' field is present and contains "Y".
  17. Validate the 'esig_consent_on_file_value' field is present and contains "Yes".
  18. Close the report.
Scenario 3: 'Admission (Outpatient)' form - Field Validation
Specific Setup:
  • A client is enrolled in an existing outpatient episode (Client A).
Steps
  1. Select "Client A" and access the 'Admission (Outpatient)' form.
  2. Select an existing episode and click [Edit].
  3. Select the "Demographics" section.
  4. Validate the 'Consent On File For Use of Integrated eSignature' field is present with values of "Yes" and "No".
  5. Select "Yes" in the 'Consent On File For Use of Integrated eSignature' field.
  6. Click [Submit].
  7. Select "Client A" and access the 'Admission (Outpatient)' form.
  8. Select an existing episode and click [Edit].
  9. Select the "Demographics" section.
  10. Validate "Yes" is selected in the 'Consent On File For Use of Integrated eSignature' field.
  11. Close the form.
  12. Access Crystal Reports or other SQL reporting tool.
  13. Create a report using the 'SYSTEM.patient_current_demographics' SQL table.
  14. Navigate to the row for "Client A".
  15. Validate the 'esig_consent_on_file_code' field is present and contains "Y".
  16. Validate the 'esig_consent_on_file_value' field is present and contains "Yes".
  17. Close the report.
  18. Create a report using the 'SYSTEM.patient_demographic_history' SQL table.
  19. Navigate to the row for "Client A".
  20. Validate the 'esig_consent_on_file_code' field is present and contains "Y".
  21. Validate the 'esig_consent_on_file_value' field is present and contains "Yes".
  22. Close the report.
Scenario 4: 'Discharge' form - Field Validation
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Select "Client A" and access the 'Discharge' form.
  2. Select an existing episode and click [Edit].
  3. Enter the desired date in the 'Date Of Discharge' field.
  4. Enter the desired time in the 'Discharge Time' field.
  5. Select the desired value in the 'Type Of Discharge' field.
  6. Select the desired practitioner in the 'Discharge Practitioner' field.
  7. Select the "Demographics" section.
  8. Validate the 'Consent On File For Use of Integrated eSignature' field is present with values of "Yes" and "No".
  9. Select "Yes" in the 'Consent On File For Use of Integrated eSignature' field.
  10. Click [Submit].
  11. Select "Client A" and access the 'Discharge' form.
  12. Select the discharged episode and click [Edit].
  13. Select the "Demographics" section.
  14. Validate the 'Consent On File For Use of Integrated eSignature' field contains "Yes".
  15. Close the form.
  16. Access Crystal Reports or other SQL reporting tool.
  17. Create a report using the 'SYSTEM.patient_current_demographics' SQL table.
  18. Navigate to the row for "Client A".
  19. Validate the 'esig_consent_on_file_code' field is present and contains "Y".
  20. Validate the 'esig_consent_on_file_value' field is present and contains "Yes".
  21. Close the report.
  22. Create a report using the 'SYSTEM.patient_demographic_history' SQL table.
  23. Navigate to the row for "Client A".
  24. Validate the 'esig_consent_on_file_code' field is present and contains "Y".
  25. Validate the 'esig_consent_on_file_value' field is present and contains "Yes".
  26. Close the report.
Scenario 5: 'Pre Admit' form - Field Validation
Specific Setup:
  • A client is enrolled in an existing Pre Admit episode (Client A).
Steps
  1. Select "Client A" and access the 'Pre Admit' form.
  2. Select an existing episode and click [Edit].
  3. Select the "Demographics" section.
  4. Validate the 'Consent On File For Use of Integrated eSignature' field is present with values of "Yes" and "No".
  5. Select "Yes" in the 'Consent On File For Use of Integrated eSignature' field.
  6. Click [Submit].
  7. Select "Client A" and access the 'Pre Admit' form.
  8. Select an existing episode and click [Edit].
  9. Select the "Demographics" section.
  10. Validate "Yes" is selected in the 'Consent On File For Use of Integrated eSignature' field.
  11. Close the form.
  12. Access Crystal Reports or other SQL reporting tool.
  13. Create a report using the 'SYSTEM.patient_current_demographics' SQL table.
  14. Navigate to the row for "Client A".
  15. Validate the 'esig_consent_on_file_code' field is present and contains "Y".
  16. Validate the 'esig_consent_on_file_value' field is present and contains "Yes".
  17. Close the report.
  18. Create a report using the 'SYSTEM.patient_demographic_history' SQL table.
  19. Navigate to the row for "Client A".
  20. Validate the 'esig_consent_on_file_code' field is present and contains "Y".
  21. Validate the 'esig_consent_on_file_value' field is present and contains "Yes".
  22. Close the report.
Scenario 6: 'Pre Admit Discharge' form - Field Validation
Specific Setup:
  • A client is enrolled in an existing Pre Admit episode (Client A).
Steps
  1. Select "Client A" and access the 'Pre Admit Discharge' form.
  2. Select an existing episode and click [Edit].
  3. Enter the desired date in the 'Date Of Discharge' field.
  4. Enter the desired time in the 'Discharge Time' field.
  5. Select the desired value in the 'Type Of Discharge' field.
  6. Select the desired practitioner in the 'Discharge Practitioner' field.
  7. Populate any other desired fields.
  8. Select the "Demographics" section.
  9. Validate the 'Consent On File For Use of Integrated eSignature' field is present with values of "Yes" and "No".
  10. Select "No" in the 'Consent On File For Use of Integrated eSignature' field.
  11. Click [Submit].
  12. Select "Client A" and access the 'Pre Admit Discharge' form.
  13. Select the previously discharged Pre Admit episode and click [Edit].
  14. Select the "Demographics" section.
  15. Validate "No" is selected in the 'Consent On File For Use of Integrated eSignature' field.
  16. Close the form.
  17. Access Crystal Reports or other SQL reporting tool.
  18. Create a report using the 'SYSTEM.patient_current_demographics' SQL table.
  19. Navigate to the row for "Client A".
  20. Validate the 'esig_consent_on_file_code' field is present and contains "N".
  21. Validate the 'esig_consent_on_file_value' field is present and contains "No".
  22. Close the report.
  23. Create a report using the 'SYSTEM.patient_demographic_history' SQL table.
  24. Navigate to the row for "Client A".
  25. Validate the 'esig_consent_on_file_code' field is present and contains "N".
  26. Validate the 'esig_consent_on_file_value' field is present and contains "No".
  27. Close the report.
Scenario 7: 'Call Intake' form - Field Validation
Specific Setup:
  • A client is enrolled in an existing Call Intake program (Client A).
Steps
  1. Select "Client A" and access the 'Call Intake' form.
  2. Select the existing call intake record and click [Edit].
  3. Select the "Demographics" section.
  4. Validate the 'Consent On File For Use of Integrated eSignature' field is present with values of "Yes" and "No".
  5. Select "No" in the 'Consent On File For Use of Integrated eSignature' field.
  6. Click [Submit].
  7. Select "Client A" and access the 'Call Intake' form.
  8. Select the existing call intake record and click [Edit].
  9. Select the "Demographics" section.
  10. Validate "No" is selected in the 'Consent On File For Use of Integrated eSignature' field.
  11. Close the form.
  12. Access Crystal Reports or other SQL reporting tool.
  13. Create a report using the 'SYSTEM.patient_current_demographics' SQL table.
  14. Navigate to the row for "Client A".
  15. Validate the 'esig_consent_on_file_code' field is present and contains "N".
  16. Validate the 'esig_consent_on_file_value' field is present and contains "No".
  17. Close the report.
  18. Create a report using the 'SYSTEM.patient_demographic_history' SQL table.
  19. Navigate to the row for "Client A".
  20. Validate the 'esig_consent_on_file_code' field is present and contains "N".
  21. Validate the 'esig_consent_on_file_value' field is present and contains "No".
  22. Close the report.
Scenario 8: The 'ClientAdmission' - 'AddAdmission' web service: Admission of a new client
Steps
  1. Access SoapUI for the 'ClientAdmission' - 'AddAdmission' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter the desired date in the 'AdmissionDate' field.
  6. Enter the desired time in the 'AdmissionTime' field.
  7. Enter the desired practitioner in the 'AdmittingPractitioner' field.
  8. Enter the desired value in the 'ClientFirstName' field.
  9. Enter the desired value in the 'ClientLastName' field.
  10. Enter the desired value in the 'ClientMiddleName' field.
  11. Enter the corresponding name in the 'ClientName' field.
  12. Enter the desired value in the 'ESignatureConsentOnFile' field. Note: "Y" and "N" are accepted values.
  13. Enter the desired value in the 'Program' field.
  14. Enter the desired value in the 'Sex' field.
  15. Populate any other required and desired fields.
  16. Click [Run].
  17. Validate the 'Confirmation' field contains a value such as: "Client Unique ID: # Unique ID: #".
  18. Validate the 'Message' field contains: "Client Admission web service has been filed successfully".
  19. Select the client filed in the previous steps and access the 'Admission' form.
  20. Select the record filed in the previous steps and click [Edit].
  21. Validate all populated fields are displayed.
  22. Select the "Demographics" section.
  23. Validate the 'Client Last Name' field contains the value filed in the previous steps.
  24. Validate the 'Client First Name' field contains the value filed in the previous steps.
  25. Validate the 'Client Middle Name' field contains the value filed in the previous steps.
  26. Validate the 'Consent On File For Use of Integrated eSignature' field contains the value filed in the previous steps.
  27. Close the form.
Scenario 9: Validate the 'ClientDemographics' - 'UpdateClientDemographics' web service
Specific Setup:
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access SoapUI for the 'ClientDemographics' - 'UpdateClientDemographics' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter the desired value in the 'ESignatureConsentOnFile' field. Note: "Y" and "N" are accepted values.
  6. Populate any other desired fields.
  7. Enter "Client A" in the 'ClientID' field.
  8. Click [Run].
  9. Validate the 'Message' field contains: Client Demographics web service has been filed successfully.
  10. Select "Client A" and access the 'Update Client Data' form.
  11. Validate the 'Consent On File For Use of Integrated eSignature' field contains the value filed in the previous steps.
  12. Validate all populated fields are displayed.
  13. Close the form.
'Outbound Referral History' form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Outbound Referral History
Scenario 1: Outbound Referral History - Form Validations
Specific Setup:
  • Must be configured for CareConnect.
  • A client is enrolled in an existing episode (Client A).
Steps
  1. Access the 'Outbound Referral History' form.
  2. Select "Client A" in the 'Client Search' field.
  3. Click [New Row] in the 'Referrals' grid.
  4. Enter the desired value in the 'Receiving Organization' field.
  5. Select the desired provider in the 'Receiving Provider' field.
  6. Select the desired provider in the 'Referring Provider' field.
  7. Enter the desired value in the 'Reason For Referral' field.
  8. Enter the desired value in the 'Notes Field' field.
  9. Select the desired value in the 'Status' field.
  10. Click [Submit].
  11. Access the 'Outbound Referral History' form.
  12. Select "Client A" in the 'Client Search' field.
  13. Validate the 'Referrals' grid contains the record filed in the previous steps.
  14. Close the form.
Topics
• Admission • Update Client Data • Admission (Outpatient) • Discharge • Pre Admit • Pre Admit Discharge • Call Intake • Web Services • Outbound Referral History
Update 61 Summary | Details
Avatar Cal-PM Sub-System Code Program Restrictions
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • System Code Definition
Scenario 1: 'Admission' - Verification of Form Pre-Display Program Restrictions for Sub-System Code
Specific Setup:
  • One or more sub-system codes must be enabled/defined in Avatar Cal-PM, with no 'Associated Programs' assigned (via 'System Code Definition' form)
  • One or more client record(s) with Admission/Episode record(s) existing in system
Steps
  1. Login to Avatar Cal-PM sub-system code with no Associated Program(s) defined/associated.
  2. Open 'Admission' form, selecting client where one or more Admission/Episode record(s) exist in system.
  3. Note - Acceptance testing may also be confirmed via Avatar Cal-PM 'Admission (Outpatient)' and/or 'Pre Admit' forms
  4. In 'Admission' form pre-display - ensure that pre-display includes no Admission/Episode records for client where no Associated Program(s) are defined/associated to current sub-system code (as only Admission/Episode records under Programs applicable to/allowed for current sub-system code are available, as defined in 'System Code Definition' form 'Associated Programs' field).
  5. Click 'Cancel' button to close 'Admission' form/pre-display.
  6. Login to Avatar Cal-PM sub-system code with one or more Associated Program(s) defined/associated.
  7. Open 'Admission' form, selecting client where one or more Admission/Episode record(s) exist in system.
  8. In 'Admission' form pre-display - ensure that pre-display includes only Admission/Episode records under Programs applicable to/allowed for current sub-system code (as defined in 'System Code Definition' form 'Associated Programs' field).
  9. Select existing record for view/update and click 'Edit' button to open Admission form/record (or click 'Add' or 'Cancel' buttons to add Admission record or close form/pre-display, respectively).
Topics
• Admission • Sub-System Code • NX
Update 62 Summary | Details
The 'ClientPreAdmitDischarge' web service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Discharge
  • Pre Admit Discharge
Scenario 1: Discharge a client via the 'ClientPreAdmitDischarge' web service
Specific Setup:
  • A client is enrolled in an existing Pre Admit episode (Client A).
  • Must have access to SoapUI or other web service tool.
Steps
  1. Access SoapUI for the 'ClientPreAdmitDischarge' - 'PreAdmitDischargeClient' web service.
  2. Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
  3. Enter the user name that will be used to log into Avatar in the 'UserName' field.
  4. Enter the password that will be used to log into Avatar in the 'Password' field.
  5. Enter the desired date in the 'DateOfDischarge' field.
  6. Enter the desired practitioner in the 'DischargePractitioner' field.
  7. Enter the desired time in the 'DischargeTime' field.
  8. Enter the desired value in the 'TypeOfDischarge' field.
  9. Enter "Client A" in the 'ClientID' field.
  10. Enter the Pre Admit episode number to be discharged in the 'EpisodeNumber' field.
  11. Click [Run].
  12. Validate the 'Message' field contains: Client Discharge web service has been filed successfully.
  13. Select "Client A" and access the 'Pre Admit Discharge' form.
  14. Validate all populated fields are displayed as entered in the web service.
  15. Close the form.
Topics
• Pre Admit Discharge • Web Services • Discharge
Update 64 Summary | Details
'Electronic Billing' Support for Services Originating in Avatar MSO
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Electronic Billing
  • Service Fee/Cross Reference Maintenance
Scenario 1: 'Electronic Billing' - Verification of 'Support MSO Other Healthcare Coverage' Registry Setting (Services Originating in Avatar MSO)
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Support MSO Other Healthcare Coverage' must be enabled
  • Avatar Cal-PM Registry Setting 'Include Service Level Adjudication Info' must be enabled (and 'Include Service Level Adjudication Information (2430)' field set to 'Yes' via 'Guarantor/Program Billing Defaults' form '837 Professional' and/or '837 Institutional' section for applicable Guarantor/Program)
  • Avatar MSO Registry Setting 'Add Support For The Input Of Third Party Payer Amounts' must be enabled
  • One or more service(s) eligible for Avatar Cal-PM 837 Professional/837 Institutional file inclusion (via 'Electronic Billing' form) originating in Avatar MSO and including Third Party Payment/Adjustment 'Other Healthcare Coverage' information
Steps
  1. Open Avatar Cal-PM 'Electronic Billing' form.
  2. Note, acceptance testing may also be confirmed via Avatar Cal-PM 'Quick Billing' form/functionality
  3. Select 837 Professional or 837 Institutional in 'Billing Form' field.
  4. Enter/select 837 file sorting criteria, using values which will include service(s) originating in Avatar MSO.
  5. Click 'Process' button to sort/generate 837 Professional or 837 Institutional file.
  6. Select 'Dump File' in the 'Billing Options' field (or select 'Create File On Server' to review output file directly).
  7. Select 'Print' in the 'Print Or Delete Report' field.
  8. Select 837 Professional/837 Institutional file sorted which includes services originating in Avatar MSO, and click 'Process' button to display 837 outbound file data.
  9. In Avatar Cal-PM 837 Professional/837 Institutional format outbound electronic billing file data - for services originating via Avatar MSO and including Service-Level Third Party Payment/Adjustment 'Other Healthcare Coverage' information, ensure that 2430-SVD-03 Service Line Adjudication Product/Service ID in Avatar Cal-PM 837 file contains 2430-SVD-03 Service Code value from original Avatar MSO inbound claim/service Other Healthcare Coverage information with any modifiers if/where present.
  10. Examples:
  11. SVD*87755XX*7.5*HC:90806**11~
  12. SVD*87755XX*7.5*HC:90806:HA**11~
  13. SVD*87755XX*7.5*HC:90806:HA:HE**11~
  14. SVD*87755XX*7.5*HC:90806:HA:HE:HF**11~
  15. SVD*87755XX*7.5*HC:90806:HA:HE:HF:ZZ**11~
Topics
• Electronic Billing • Claims Processing • NX
 

Avatar_Cal-PM_2023_Monthly_Release_2023.02.02_Details.csv