Skip to main content

Avatar Cal-PM 2022 Quarterly Release 2022.03 Acceptance Tests


Update 4 Summary | Details
Web Services - Clinician Services
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Practitioner Enrollment
  • Dictionary Update (PM)
  • SOAPUI - ClinicianServices
  • SOAPUI - ClinicianServices - putClinicianUpdate
  • SOAPUI - ClinicianServices - putClinicianUpdateResponse
  • SOAPUI - ClinicianServices - putClinicianCreation
  • SOAPUI - ClinicianServices - putClinicianCreationResponse
  • Contracting Provider Registration
  • SOAPUI - ClinicianServices - putClinicianAssociation
  • SOAPUI - ClinicianServices - putClinicianAssociationResponse
  • Performing Provider Association
  • Performing Provider Association - Filing Confirmation
Scenario 1: 'ClinicianServices' web service - Verification of updating/adding taxonomy category for an existing practitioner through 'putClinicianUpdate' method filing
Specific Setup:
  • Registry Setting:
  • The 'Avatar Web Services->Set System Defaults->->->->URL' registry setting is set to 'http://localhost:(port)/csp/(Namespace)'.
  • The 'Avatar PM->Practitioner->->->->Enable Practitioners link to Performing Providers' registry setting is set to 'Y'.
  • The 'Avatar MSO->Provider Management->->->->Overwrite All Contracting Provider Registration Associations on Update link' registry setting is set to 'Y'.
  • Dictionary Update:
  • Dictionary codes/values for the Practitioner Category, Practitioner categories for coverage and Discipline are identified from the:
  • File = Staff File
  • Data Elements= Practitioner Category, Practitioner Categories For Coverage, Discipline
  • Note all the values to be used at the time of creating the web service request.
  • Access to SoapUI for utilizing the Avatar PM 'ClinicianServices' web service.
  • Practitioner Enrollment:
  • A new Practitioner is created with the following required information. Note all the values from the fields.
  • Practitioner Enrollment section:
  • Date Of Birth
  • Registration Date
  • Office Address - Street
  • Office Address - Zip
  • Office Telephone (1)
  • NPI Number
  • Categories/Taxonomy section:
  • A new Category/taxonomy row is created. Make sure that the effective date for this first taxonomy is equal to the registration date provided for the practitioner. The required information entered in the 'Practitioner Category', 'Discipline', and 'Practitioner Categories for Coverage'. Note the values from these fields. Leave the 'End Date' field as blank.
Steps
  1. Open the SoapUI or any other web service tool to run the web service request.
  2. In SoapUI, Create a new web service request for 'putClinicianUpdate' method.
  3. Fill out the ClinicianDetails object field in the request with the specified practitioner's information.
  4. In the ClinicianTaxonomyData field, create two taxonomy objects. The first taxonomy object should have an effective date equal to the effective date of the first taxonomy object/taxonomy row that was created earlier. Fill out an expiration date for this first taxonomy object.
  5. For the second taxonomy object, set the effective date right after the expiration date for the first taxonomy object and leave the expiration date as blank. For both taxonomy objects fill out any taxonomy object information such as: 'ClinicianPractitionerCategory','ClinicianDiscipline', and 'ClinicianPractitionerCategoriesOfCoverage.
  6. Confirm 'ClinicianServices' web service responds with confirmation data on successful filing of 'putClinicianUpdate' method.
  7. Example: " <Confirmation>Practitioner ID:000173||Performing Provider ID:173||First Name:QATESTING||Last Name:JOSH||Registration Date:03/01/2021||NPI:1063581684</Confirmation>".
  8. Confirm 'ClinicianServices' web service responds with confirmation message on successful filing of 'putClinicianUpdate' method.
  9. Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
  10. Confirm 'ClinicianServices' web service responds with successful status value on successful filing of 'putClinicianUpdate' method.
  11. Example: " <Status>1</Status>"
  12. Open Avatar PM 'Practitioner Enrollment' form.
  13. Select Practitioner Enrollment record filed via web service for view/update.
  14. Confirm the Practitioner Enrollment record is updated in Avatar PM, with values/data submitted via web service.
Scenario 2: Cal-PM - 'ClinicianServices' Web Service - Verification Of 'putClinicianAssociation' Filing
Specific Setup:
  • Registry Setting:
  • The 'Avatar Web Services->Set System Defaults->->->->URL' registry setting is set to 'http://localhost:(port)/csp/(Namespace)'.
  • The 'Avatar PM->Practitioner->->->->Enable Practitioners link to Performing Providers' registry setting is set to 'Y'.
  • The 'Avatar MSO->Provider Management->->->->Overwrite All Contracting Provider Registration Associations on Update link' registry setting is set to 'Y'.
  • Dictionary Update:
  • Dictionary codes/values for the Practitioner Category, Practitioner categories for coverage and Discipline are identified from the:
  • File = Staff File
  • Data Elements= Practitioner Category, Practitioner Categories For Coverage, Discipline
  • Note all the values to be used at the time of creating the web service request.
  • Access to SoapUI for utilizing the Avatar PM 'ClinicianServices' web service.
  • Contracting Provider Registration:
  • A new contracting provider is added or an existing contracting provider is identified. Note the contracting provider id, Funding source assigned to the contracting provider and registration date.
Steps
  1. Using Avatar PM 'ClinicianServices' web service, submit request to 'putClinicianCreation' method to create new Avatar PM Practitioner Enrollment (and optionally Avatar MSO Performing Provider Registration record).
  2. Confirm 'ClinicianServices' web service responds with confirmation data on successful filing of 'putClinicianCreation' method.
  3. Example: '<Confirmation>Practitioner ID:000189||Performing Provider ID:189||First Name:CLINICIANASSOCIATION||Last Name:WEBSVC||Registration Date:04/01/2022||NPI:1083157689</Confirmation>'. Note the practitioner id to be used in 'putClinicianAssociation' method.
  4. Confirm 'ClinicianServices' web service responds with confirmation message on successful filing of 'putClinicianCreation' method.
  5. Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
  6. Confirm 'ClinicianServices' web service responds with successful status value on successful filing of 'putClinicianCreation' method.
  7. Example: " <Status>1</Status>"
  8. Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
  9. Confirm new Practitioner Enrollment record is created in Avatar PM, with values/data submitted via web service.
  10. Open the SoapUI or any other web service tool to run the web service request.
  11. In SoapUI, Create a new web service request for 'putClinicianAssociation' method.
  12. Fill out the ClinicianAssociation object field in the request with the specified practitioner's information.
  13. Fill out the ClinicianTaxonomyData field in the request with the specified taxonomy objects.information such as: 'ClinicianPractitionerCategory','ClinicianDiscipline', and 'ClinicianPractitionerCategoriesOfCoverage'.
  14. Confirm 'ClinicianServices' web service responds with confirmation data on successful filing of 'putClinicianAssociation' method.
  15. Example: " <Confirmation>Contacting Provider ID:9||Funding Source ID:A||Contracting Provider Registration Start Date:01/01/2012||Practitioner ID:000189||NPI:1083157689||Clinician Effective Start Date:04/01/2022||Association Effective Start Date:04/01/2022</Confirmation>".
  16. Confirm 'ClinicianServices' web service responds with confirmation message on successful filing of 'putClinicianAssociation' method.
  17. Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
  18. Confirm 'ClinicianServices' web service responds with successful status value on successful filing of 'putClinicianAssociation' method.
  19. Example: " <Status>1</Status>"
  20. Open Avatar PM 'Contracting Provider Registration' form.
  21. Select Practitioner Association record filed via web service for view/update.
  22. Confirm the Contracting Provider record is updated in Avatar PM, with values/data submitted via web service.
Scenario 3: Cal-PM - 'ClinicianServicesV2' Web Service - Verification Of 'putClinicianUpdate' Filing
Specific Setup:
  • Registry Setting:
  • The 'Avatar Web Services->Set System Defaults->->->->URL' registry setting is set to 'http://localhost:(port)/csp/(Namespace)'.
  • The 'Avatar PM->Practitioner->->->->Enable Practitioners link to Performing Providers' registry setting is set to 'Y'.
  • The 'Avatar MSO->Provider Management->->->->Overwrite All Contracting Provider Registration Associations on Update link' registry setting is set to 'Y'.
  • Dictionary Update:
  • Dictionary codes/values for the Practitioner Category, Practitioner categories for coverage and Discipline are identified from the:
  • File = Staff File
  • Data Elements= Practitioner Category, Practitioner Categories For Coverage, Discipline
  • Note all the values to be used at the time of creating the web service request.
  • Access to SoapUI for utilizing the Avatar PM 'ClinicianServices' web service.
  • Practitioner Enrollment:
  • A new Practitioner is created with the following required information. Note the values entered to the following fields.
  • Practitioner Enrollment section:
  • Date Of Birth
  • Registration Date
  • Office Address - Street
  • Office Address - Zip
  • Office Telephone (1)
  • NPI Number
  • Categories/Taxonomy section:
  • A new Category/taxonomy row is created. Make sure that the effective date for this first taxonomy is equal to the registration date provided for the practitioner. The required information entered in the 'Practitioner Category', 'Discipline', and 'Practitioner Categories for Coverage'. Note the values entered to the fields. Leave the 'End Date' field as blank.
Steps
  1. Open the SoapUI or any other web service tool to run the web service request.
  2. In SoapUI, Create a new web service request for 'putClinicianUpdate' method.
  3. Fill out the ClinicianDetails object field in the request with the specified practitioner's information.
  4. In the ClinicianTaxonomyData field, create two taxonomy objects. The first taxonomy object should have an effective date equal to the effective date of the first taxonomy object/taxonomy row that was created earlier. Fill out an expiration date for this first taxonomy object.
  5. For the second taxonomy object, set the effective date right after the expiration date for the first taxonomy object and leave the expiration date as blank. For both taxonomy objects fill out any taxonomy object information such as: 'ClinicianPractitionerCategory','ClinicianDiscipline', and 'ClinicianPractitionerCategoriesOfCoverage.
  6. Confirm 'ClinicianServices' web service responds with confirmation data on successful filing of 'putClinicianUpdate' method.
  7. Example: '<Confirmation>Practitioner ID:000186||Performing Provider ID:186||First Name:CLINICIANSERVICESTWO||Last Name:WEBSVC||Registration Date:03/01/2022||NPI:1013172394</Confirmation>'.
  8. Confirm 'ClinicianServices' web service responds with confirmation message on successful filing of 'putClinicianUpdate' method.
  9. Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
  10. Confirm 'ClinicianServices' web service responds with successful status value on successful filing of 'putClinicianUpdate' method.
  11. Example: '<Status>1</Status>'.
  12. Confirm 'ClinicianServices' web service responds with correct practitioner id on successful filing of 'putClinicianUpdate' method.
  13. Example: 'ClinicianID>000186</ClinicianID>'.
  14. Confirm 'ClinicianServices' web service responds with correct first name of the practitioner on successful filing of 'putClinicianUpdate' method.
  15. Example:<ClinicianFirstName>CLINICIANSERVICESTWO</ClinicianFirstName>.
  16. Confirm 'ClinicianServices' web service responds with correct last name of the practitioner on successful filing of 'putClinicianUpdate' method.
  17. Example: '<ClinicianLastName>WEBSVC</ClinicianLastName>'.
  18. Confirm 'ClinicianServices' web service responds with correct last name of the practitioner on successful filing of 'putClinicianUpdate' method.
  19. Example: '<ClinicianRegistrationDate>2022-03-01</ClinicianRegistrationDate>'.
  20. Confirm 'ClinicianServices' web service responds with correct NPI number of the practitioner on successful filing of 'putClinicianUpdate' method.
  21. Example: '<ClinicianNPI>1013172394</ClinicianNPI>'.
  22. Open Avatar PM 'Practitioner Enrollment' form.
  23. Select Practitioner Enrollment record filed via web service for view/update.
  24. Confirm the Practitioner Enrollment record is updated in Avatar PM, with values/data submitted via web service.
Scenario 4: Cal-PM - 'ClinicianServices' Web Service - Verification Of 'putClinicianCreation' and 'putClinicianUpdate' Filing
Specific Setup:
  • Registry Setting:
  • The 'Avatar Web Services->Set System Defaults->->->->URL' registry setting is set to 'http://localhost:(port)/csp/(Namespace)'.
  • The 'Avatar PM->Practitioner->->->->Enable Practitioners link to Performing Providers' registry setting is set to 'Y'.
  • The 'Avatar MSO->Provider Management->->->->Overwrite All Contracting Provider Registration Associations on Update link' registry setting is set to 'Y'.
  • Dictionary Update:
  • Dictionary codes/values for the Practitioner Category, Practitioner categories for coverage and Discipline are identified from the:
  • File = Staff File
  • Data Elements= Practitioner Category, Practitioner Categories For Coverage, Discipline
  • Note all the values to be used at the time of creating the web service request.
  • Access to SoapUI for utilizing the Avatar Cal-PM 'ClinicianServices' web service.
Steps
  1. Using Avatar PM 'ClinicianServices' web service, submit request to 'putClinicianCreation' method to create new Avatar PM Practitioner Enrollment (and optionally Avatar MSO Performing Provider Registration record).
  2. Confirm 'ClinicianServices' web service responds with confirmation data on successful filing of 'putClinicianCreation' method.
  3. Example: '<Confirmation>Practitioner ID:000175||Performing Provider ID:175||First Name:TESTPRACTITIONERTWO||Last Name:QA||Registration Date:03/01/2021||NPI:1013172394</Confirmation>'. Note the practitioner id to be used in 'putClinicianUpdate' method.
  4. Confirm 'ClinicianServices' web service responds with confirmation message on successful filing of 'putClinicianCreation' method.
  5. Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
  6. Confirm 'ClinicianServices' web service responds with successful status value on successful filing of 'putClinicianCreation' method.
  7. Example: " <Status>1</Status>"
  8. Open Avatar PM 'Practitioner Enrollment' form and select Practitioner Enrollment record filed via web service for view/update.
  9. Confirm new Practitioner Enrollment record is created in Avatar PM, with values/data submitted via web service.
  10. Open the SoapUI or any other web service tool to run the web service request.
  11. In SoapUI, Create a new web service request for 'putClinicianUpdate' method.
  12. Fill out the ClinicianDetails object field in the request with the specified practitioner's information.
  13. In the ClinicianTaxonomyData field, create two taxonomy objects. The first taxonomy object should have an effective date equal to the effective date of the first taxonomy object/taxonomy row that was created earlier. Fill out an expiration date for this first taxonomy object.
  14. For the second taxonomy object, set the effective date right after the expiration date for the first taxonomy object and leave the expiration date as blank. For both taxonomy objects fill out any taxonomy object information such as: 'ClinicianPractitionerCategory','ClinicianDiscipline', and 'ClinicianPractitionerCategoriesOfCoverage.
  15. Confirm 'ClinicianServices' web service responds with confirmation data on successful filing of 'putClinicianUpdate' method.
  16. Example: '<Confirmation>Practitioner ID:000175||Performing Provider ID:175||First Name:TESTPRACTITIONERTWO||Last Name:QA||Registration Date:03/01/2021||NPI:1013172394</Confirmation>'.
  17. Confirm 'ClinicianServices' web service responds with confirmation message on successful filing of 'putClinicianUpdate' method.
  18. Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
  19. Confirm 'ClinicianServices' web service responds with successful status value on successful filing of 'putClinicianUpdate' method.
  20. Example: " <Status>1</Status>"
  21. Open Avatar PM 'Practitioner Enrollment' form.
  22. Select Practitioner Enrollment record filed via web service for view/update.
  23. Confirm the Practitioner Enrollment record is updated in Avatar PM, with values/data submitted via web service.

Topics
• NX • Web Services
Update 18 Summary | Details
Quick Actions - Update Client Data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • View Definition
  • NX View Definition
  • Quick Actions Page
  • Update Client Data
  • Site Specific Section Modeling (PM)
  • Form and Table Documentation (PM)
  • Dictionary Update (PM)
Scenario 1: Quick Action - Update Client Data - 9 digit zip code
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Enter an address with a 9-digit zip code.
  6. Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
  7. Click "Save".
  8. Click "Add" on the "Update Client Data" Quick Action.
  9. Validate the "Zip Code", "City" and "State" fields display appropriately.
  10. Open the "Update Client Data" form.
Scenario 2: Quick Action - Update Client Data - Validate name change
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Change the client's first and last name.
  6. Fill in all other fields.
  7. Click "Save".
  8. Open the "Update Client Data" form.
  9. Validate the first and last name are changed.
  10. Using SQL, validate the name change is reflected in the columns, patient_name, patient_name_first, patient_name_last in SYSTEM.patient_current_demographics SQL.
Scenario 3: Quick Action - Update Client Data - 5 digit zip code
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Admit a test client.
Steps
  1. Select the test client.
  2. Navigate to the "Quick Actions" widget.
  3. Locate the "Update Client Data" Quick Action.
  4. Click "Add" button.
  5. Enter an address with a 5-digit zip code.
  6. Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
  7. Click "Save".
  8. Click "Add" on the "Update Client Data" Quick Action.
  9. Validate the "Zip Code", "City" and "State" fields display appropriately.
  10. Open the "Update Client Data" form.
  11. Validate the same fields all display in uppercase letters.
Scenario 4: Quick Action - Update Client Data - Update Financial Eligibility Data enabled
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Select a client who has existing financial eligibility data.
  • Enable the registry setting "Update Financial Eligibility Data".
Steps
  1. Navigate to the "Quick Action" widget.
  2. Click "Add" on the "Update Client Data" item.
  3. Enter a new name and address for the client with existing financial eligibility data.
  4. Enter the following SQL statement to view the listed fields in SYSTEM.billing_guar_subs_data: SELECT subs_name,subs_name_first,subs_name_last,subs_address_street1,subs_address_street2,subs_address_city,subs_address_state,subs_addess_zip FROM SYSTEM.billing_guar_subs_data to validate that these columns were changed when the Quick Action was filed.
Scenario 5: Quick Action - Update Client Data - Update Financial Eligibility Data disabled
Specific Setup:
  • Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
  • Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
  • Select a client who has existing financial eligibility data.
  • Disable the registry setting "Update Financial Eligibility Data".
Steps
  1. Navigate to the "Quick Action" widget.
  2. Click "Add" on the "Update Client Data" item.
  3. Enter a new name and address for the client with existing financial eligibility data.
  4. Enter the following SQL statement to view the listed fields in SYSTEM.billing_guar_subs_data: SELECT subs_name,subs_name_first,subs_name_last,subs_address_street1,subs_address_street2,subs_address_city,subs_address_state,subs_addess_zip FROM SYSTEM.billing_guar_subs_data to validate that these columns were not changed when the Quick Action was filed.
Scenario 6: Update Client Data - Site Specific Fields
Specific Setup:
  • Add one of each type of site specific section modeling type field, such as single response dictionary, multi response dictionary, date, time, free text (20), free text (40), scrolling free test and a practitioner lookup to the "Update Client Data" form.
  • Add data dictionaries for the single and multiple response site specific fields.
  • Admit a test client.
  • Add the "Quick Actions" widget to the user's HomeView.
Steps
  1. Open the "Update Client Data" form for the test client.
  2. Populate all fields added to the form via Site Specific Section Modeling in setup.
  3. File the form.
  4. Navigate to the "Quick Actions" widget.
  5. Select the "Update Client Data" quick action.
  6. Save the quick action.
  7. Open the "Update Client Data" form for the test client.
  8. Validate the site specific fields display data as it was originally entered.

Topics
• NX • Quick Actions • Site Specific Section Modeling • Update Client Data
Update 20 Summary | Details
'Add First Ever Diagnosis Check' Registry Setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Table Definition (CWS)
  • Form Definition (CWS)
Scenario 1: 'Diagnosis' Web Service - Verification of 'Diagnosis' Record Filing
Specific Setup:
  • A valid ICD-9 code, ICD-9 description, ICD-10 code, ICD-10 description, SNOMED code, SNOMED description and IMO code are identified for web service request
  • Client/episode eligible for 'Diagnosis' entry in Avatar Cal-PM
  • Application utilizing the Avatar Cal-PM 'Diagnosis' web service
Steps
  1. Using Avatar Cal-PM 'Diagnosis' web service, submit request to 'AddClientDiagnosis' or 'EditClientDiagnosis' method to create or update Avatar PM 'Diagnosis' record, including value for 'FirstEverDx' field/segment (within the 'DiagnosisEntryObject' portion of web service request).
  2. Confirm 'Diagnosis' web service responds with confirmation data/ID on successful filing of 'AddClientDiagnosis'/'EditClientDiagnosis' method.
  3. Example:"<Confirmation>Unique ID: 397</Confirmation>"
  4. Confirm 'Diagnosis' web service responds with confirmation message on successful filing of 'AddClientDiagnosis'/'EditClientDiagnosis' method.
  5. Example:" <Message>Client Diagnosis web service has been filed successfully.</Message>"
  6. Confirm 'Diagnosis' web service responds with successful status value on successful filing of 'AddClientDiagnosis'/'EditClientDiagnosis' method.
  7. Example:" <Status>1</Status>"
  8. Open Avatar Cal-PM 'Diagnosis' form and select client/episode and Diagnosis record filed via web service for view/update.
  9. Confirm 'Diagnosis' record is created/updated in Avatar PM, with values/data submitted via web service including 'Is this the first ever diagnosis?' field value for Diagnosis entry/row.
Scenario 2: 'Diagnosis' - Form Verification
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Add First Ever Diagnosis Check' may be set to '0', '1' or '2'
  • Client/episode eligible for 'Diagnosis' entry in Avatar Cal-PM
Steps
  1. Open Avatar Cal-PM 'Diagnosis' form.
  2. Select client/episode for 'Diagnosis' record entry/edit.
  3. Click 'Add' button in 'Diagnosis' form pre-display to enter new record (or select existing row and click 'Edit' button).
  4. Enter/select values for 'Type Of Diagnosis', 'Date Of Diagnosis' and 'Time Of Diagnosis' fields.
  5. Click 'New Row' to input new Diagnosis entry row (or select existing Diagnosis entry row for view/edit).
  6. In 'Diagnosis Search' field, enter 'B20' (or any search term including 'AIDS'/'HIV' diagnosis text).
  7. Select Diagnosis Code value where 'ICD-10' code value is 'B20'
  8. Ensure that 'Is this the first ever diagnosis?' field is displayed/required according to the following logic where 'B20' ICD-10 Diagnosis Code is selected for Diagnosis entry row:
  9. Where Registry Setting 'Add First Ever Diagnosis Check' is set to '1' (default value), ensure that 'Is this the first ever diagnosis?' field is visible in form and required.
  10. Where Registry Setting 'Add First Ever Diagnosis Check' is set to '2', ensure that 'Is this the first ever diagnosis?' field is visible in form but not required.
  11. Where Registry Setting 'Add First Ever Diagnosis Check' is set to '0', ensure that 'Is this the first ever diagnosis?' field is not displayed/not visible in form (and not required).
  12. If any value other than 'B20' ICD-10 Diagnosis Code is selected for Diagnosis entry row, ensure that 'Is this the first ever diagnosis?' field is not displayed/not visible in form (and not required).
  13. Enter/select values for all other 'Diagnosis' form fields as required/desired.
  14. Click 'Submit' button to file 'Diagnosis' form/record.
Scenario 3: Avatar Modeled Forms - Verification of 'First Ever Diagnosis' Field Requirements
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Add First Ever Diagnosis Check' may be set to '0', '1' or '2'
  • Avatar Cal-PM/MSO/CWS Modeled form including a 'Diagnosis' section and with the following fields added via 'Table Definition'/'Form Definition' options:
  • Diagnosis fields mapped from the product Diagnosis form (with 'Table Alias' entry for 'Diagnosis History (ICD-10)' Alias Table)
  • Up to 5 'Is this the first ever diagnosis?' columns (with columns mapped to 'Is this the first ever diagnosis?' Alias Table Column)
  • Client/episode eligible for Modeled Form record/'Diagnosis' record entry in Avatar Cal-PM
Steps
  1. Open Avatar Cal-PM/MSO/CWS Modeled Form.
  2. Select client/episode for Modeled Form record entry/edit.
  3. In 'Diagnosis Search' field, enter 'B20' (or any search term including 'AIDS'/'HIV' diagnosis text).
  4. Select Diagnosis Code value where 'ICD-10' code value is 'B20'
  5. Ensure that 'Is this the first ever diagnosis?' Alias field is displayed/required according to the following logic where 'B20' ICD-10 Diagnosis Code is selected for Diagnosis Alias field(s):
  6. Where Registry Setting 'Add First Ever Diagnosis Check' is set to '1' (default value), ensure that 'Is this the first ever diagnosis?' Alias field is required to file form (or finalize record).
  7. Where Registry Setting 'Add First Ever Diagnosis Check' is set to '2', ensure that 'Is this the first ever diagnosis?' Alias field is not required to file form (or finalize record).
  8. Where Registry Setting 'Add First Ever Diagnosis Check' is set to '0', ensure that 'Is this the first ever diagnosis?' Alias field is not required to file form (or finalize record).
  9. If any value other than 'B20' ICD-10 Diagnosis Code is selected for Diagnosis Alias field(s), ensure that 'Is this the first ever diagnosis?' Alias field is not required to file form (or finalize record).
  10. Enter/select values for all other Modeled Form fields as required/desired.
  11. Click 'Submit' button to file Modeled Form/record.
Scenario 4: Avatar Cal-PM Registry Settings - Verification of 'Add First Ever Diagnosis Check' Registry Setting
Steps
  1. Open 'Registry Settings' form.
  2. Enter search value 'Add First Ever Diagnosis Check'.
  3. Select 'Yes' for 'Include Hidden Registry Settings' field.
  4. Click 'View Registry Settings' button.
  5. Ensure Registry Setting 'Add First Ever Diagnosis Check' is returned (under 'Avatar PM -> Client Information -> Diagnosis' path).
  6. Ensure Registry Setting 'Add First Ever Diagnosis Check' is set to '1' by default on update installation.
  7. Ensure 'Registry Setting Details' field contains the following explanation text:

"Selecting '1' will make field 'Is this the first ever diagnosis?' visible and required on an add/edit of an HIV related diagnosis in the 'Diagnosis' form.

Selecting '2' will make the field visible but not required on an add/edit.

If valued as '0' then the field will remain hidden.

This field was added to the system to support UDS reporting.


The available choices are as follows:

0 = Hide

1 = Make visible and required

2 = Make visible but not required


The default value is '1' if this setting is left blank"


Topics
• Diagnosis • Modeling • NX • Registry Settings • Web Services
Update 21 Summary | Details
Electronic Billing / Quick Billing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Practitioner Enrollment
  • Practitioner Numbers By Guarantor and Program
  • Guarantors/Payors
  • Program Maintenance
  • Ambulatory Progress Notes
  • Dynamic Form - document routing - sign
  • Electronic Billing
  • Quick Billing Rule Definition
  • Quick Billing
Scenario 1: Cal-PM - 837 Professional - Validate processing when progress note has a practitioner and a co-practitioner
Specific Setup:
  • Registry Setting: ‘Enable Co-Practitioner Services From Progress Notes’ has a value of ‘Y’.
  • Service Code A:
  • Service can be billed on the 837 Professional and has a fee defined in ‘Service Fee/Cross Reference Maintenance. Note the fee.
  • Client A:
  • Note the client’s admission date and program.
  • Financial Eligibility is assigned to a Med-Cal guarantor that allows customization of the plan. The plan is customized to set the ‘Insurance Dollar Limit Per Day’ to the amount of the fee noted above. The client has no other guarantors assigned.
  • A progress note has been created for Client A, Service Code A, has a duration, a practitioner, a co-practitioner, and a co-practitioner duration. Note the date of service.
  • Client Ledger has been used to verify that the practitioner service distributed to the Med-Cal guarantor and that the co- practitioner service distributed to the default guarantor (99999).
  • Close Charges has been used to close the charge.
  • Create Interim Billing Batch File has been used to create a batch for the service. Note the batch number.
Steps
  1. Open ‘Electronic Billing’.
  2. Select ‘837-Professional’ in ‘Billing Form’.
  3. Select ‘Medi-Cal’ in ‘Type Of Bill’.
  4. Select ‘All’ in ‘Individual Or All Guarantors’.
  5. Select ‘Outpatient’ in ‘Billing Type’.
  6. Select ‘Sort File’ in ‘Billing Options’.
  7. Set ‘File Description/Name’ to desired value’.
  8. Select ‘Interim Batch’ in ‘All Clients Or Interim Billing Batch’.
  9. Select the desired ‘Interim Batch Number’.
  10. Select desired value in ‘Create Claims’.
  11. Enter the desired values in required date fields.
  12. Select desired value in ‘Include Primary and/or Secondary Billing’.
  13. Click Process.
  14. Validate that an error message is received stating: ‘No Valid Information Found. Please Check The Error Report’.
  15. Select ‘Run Report’ in ‘Billing Options’.
  16. Select ‘Print’ in ‘Print Or Delete Report’.
  17. Select the ‘File Description/Name’ from above in ‘File’.
  18. Click [Print 837 Report].
  19. Click the ‘Required Data Missing: Patient Service Data’ link.
  20. Validate that the error message states: ‘ A parent service can only be billed if all the co-practitioner services are also on the bill’ and provides the service date and service code.
  21. Close the report.
  22. Close the form.
Scenario 2: Cal-PM - 837 Institutional - Validate processing when progress note has a practitioner and a co-practitioner
Specific Setup:
  • Registry Setting: ‘Enable Co-Practitioner Services From Progress Notes’ has a value of ‘Y’.
  • Service Code A:
  • Service can be billed on the 837 Institutional and has a fee defined in ‘Service Fee/Cross Reference Maintenance. Note the fee.
  • Client A:
  • Note the client’s admission date and program.
  • Financial Eligibility is assigned to a Med-Cal guarantor that allows customization of the plan. The plan is customized to set the ‘Insurance Dollar Limit Per Day’ to the amount of the fee noted above. The client has no other guarantors assigned.,
  • A progress note has been created for Client A, Service Code A, has a duration, a practitioner, a co-practitioner, and a co-practitioner duration. Note the date of service.
  • Client Ledger has been used to verify that the practitioner service distributed to the Med-Cal guarantor and that the co- practitioner service distributed to the default guarantor (99999).
  • Close Charges has been used to close the charge.
  • Create Interim Billing Batch File has been used to create a batch for the service. Note the batch number.
Steps
  1. Open ‘Electronic Billing’.
  2. Select ‘837-Institutional’ in ‘Billing Form’.
  3. Select ‘Medi-Cal’ in ‘Type Of Bill’.
  4. Select ‘All’ in ‘Individual Or All Guarantors’.
  5. Select ‘Outpatient’ in ‘Billing Type’.
  6. Select ‘Sort File’ in ‘Billing Options’.
  7. Set ‘File Description/Name’ to desired value’.
  8. Select ‘Interim Batch’ in ‘All Clients Or Interim Billing Batch’.
  9. Select the desired ‘Interim Batch Number’.
  10. Select desired value in ‘Create Claims’.
  11. Enter the desired values in required date fields.
  12. Select desired value in ‘Include Primary and/or Secondary Billing’.
  13. Click Process.
  14. Validate that an error message is received stating: ‘No Valid Information Found. Please Check The Error Report’.
  15. Select ‘Run Report’ in ‘Billing Options’.
  16. Select ‘Print’ in ‘Print Or Delete Report’.
  17. Select the ‘File Description/Name’ from above in ‘File’.
  18. Click [Print 837 Report].
  19. Click the ‘Required Data Missing: Patient Service Data’ link.
  20. Validate that the error message states: ‘ A parent service can only be billed if all the co-practitioner services are also on the bill’ and provides the service date and service code.
  21. Close the report.
  22. Close the form.
Scenario 3: Cal-PM - Quick Billing - 837 Professional - Validate processing when progress note has a practitioner and a co-practitioner
Specific Setup:
  • Registry Setting: ‘Enable Co-Practitioner Services From Progress Notes’ has a value of ‘Y’.
  • Service Code A:
  • Service can be billed on the 837 Professional and has a fee defined in ‘Service Fee/Cross Reference Maintenance. Note the fee.
  • Client A:
  • Note the client’s admission date and program.
  • Financial Eligibility is assigned to a Med-Cal guarantor that allows customization of the plan. The plan is customized to set the ‘Insurance Dollar Limit Per Day’ to the amount of the fee noted above. The client has no other guarantors assigned.
  • A progress note has been created for Client A, Service Code A, has a duration, a practitioner, a co-practitioner, and a co-practitioner duration. Note the date of service.
  • Client Ledger has been used to verify that the practitioner service distributed to the Med-Cal guarantor and that the co- practitioner service distributed to the default guarantor (99999).
  • Quick Billing Rule Definition’ has been used to create a definition that includes the program and guarantor.
Steps
  1. Open ‘Quick Billing’.
  2. Select ‘Add New’ in ‘Add New or Edit Existing Quick Billing Batch’.
  3. Enter desired value required dates.
  4. Select the desired rule definition in ‘Billing Rule To Execute’.
  5. Select desired values in ‘Quick Billing Tasks to Execute’
  6. Enter desired ‘Date of ‘Claim’.
  7. Click [Submit].
  8. Validate that an error message is received stating ‘No Information Found Errors found’ and contains information specific to the batch.
  9. Click [OK].
  10. Click [Yes].
  11. Select ‘Edit Existing’ in ‘Add New Or Edit Existing Quick Billing Batch’.
  12. Select the desired ‘File’.
  13. Click [Print 837 Report].
  14. Click the ‘Required Data Missing: Patient Service Data’ link.
  15. Validate the error message states: ‘ A parent service can only be billed if all the co-practitioner services are also on the bill’ and provides the service date and service code.
  16. Close the report.
  17. Close the form.
Scenario 4: Cal-PM - Quick Billing - 837 Institutional - Validate processing when progress note has a practitioner and a co-practitioner
Specific Setup:
  • Registry Setting: ‘Enable Co-Practitioner Services From Progress Notes’ has a value of ‘Y’.
  • Service Code A:
  • Service can be billed on the 837 Institutional and has a fee defined in ‘Service Fee/Cross Reference Maintenance. Note the fee.
  • Client A:
  • Note the client’s admission date and program.
  • Financial Eligibility is assigned to a Med-Cal guarantor that allows customization of the plan. The plan is customized to set the ‘Insurance Dollar Limit Per Day’ to the amount of the fee noted above. The client has no other guarantors assigned.
  • A progress note has been created for Client A, Service Code A, has a duration, a practitioner, a co-practitioner, and a co-practitioner duration. Note the date of service.
  • Client Ledger has been used to verify that the practitioner service distributed to the Med-Cal guarantor and that the co- practitioner service distributed to the default guarantor (99999).
  • Quick Billing Rule Definition’ has been used to create a definition that includes the program and guarantor.
Steps
  1. Open ‘Quick Billing’.
  2. Select ‘Add New’ in ‘Add New or Edit Existing Quick Billing Batch’.
  3. Enter desired value required dates.
  4. Select the desired rule definition in ‘Billing Rule To Execute’.
  5. Select desired values in ‘Quick Billing Tasks to Execute’
  6. Enter desired ‘Date of ‘Claim’.
  7. Click [Submit].
  8. Validate that an error message is received stating ‘No Information Found Errors found’ and contains information specific to the batch.
  9. Click [OK].
  10. Click [Yes].
  11. Select ‘Edit Existing’ in ‘Add New Or Edit Existing Quick Billing Batch’.
  12. Select the desired ‘File’.
  13. Click [Print 837 Report].
  14. Click the ‘Required Data Missing: Patient Service Data’ link.
  15. Validate the error message states: ‘ A parent service can only be billed if all the co-practitioner services are also on the bill’ and provides the service date and service code.
  16. Close the report.
  17. Close the form.
Edit Service Information - Inhibited Billing services
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
  • Guarantors/Payors
  • Practitioner Enrollment
  • Practitioner Numbers By Guarantor and Program
  • Inhibit Billing By Reason
  • Dynamic Form - Inhibit Billing By Reason
  • Inhibit Billing By Service
  • Dynamic Form - File Service Inhibit Information
Scenario 1: Cal-PM - 'Inhibit Billing By Reason' - Verification of form filing, single services selection
Specific Setup:
  • Dictionary codes/values must be defined for Avatar Cal-PM 'Billing' file Data Element 'Reason for Inhibit' (20520).
  • Client with 50 or more open service(s) eligible for 'Inhibit Billing By Reason' filing.
Steps
  1. Open the Avatar Cal-PM 'Inhibit Billing By Reason' form (under 'Avatar PM / Billing / Bill Production' menu).
  2. Ensure that the following service criteria selection/entry fields are present in form:
  3. 'Reason For Inhibit' (dropdown selection field)
  4. 'Rendering Practitioner'
  5. 'Client ID' / 'Episode Number'
  6. 'Liable Guarantor'
  7. 'Program Where Service Was Rendered' (dropdown selection field)
  8. 'Search Start Date' (with 'Today' and 'Yesterday' entry buttons)
  9. 'Search End Date' (with 'Today' and 'Yesterday' entry buttons)
  10. 'Services to Display' ('Inhibited' or 'Uninhibited' radio selection buttons)
  11. Ensure that on opening 'Inhibit Billing By Reason' form, only the 'Reason for Inhibit' field is enabled. Selection of value in 'Reason for Inhibit' field is required prior to Inhibit Billing By Reason entry/review/removal in form since a single service may have Inhibit Billing By Reason entries filed under multiple 'Reason for Inhibit' values.
  12. Select value in 'Reason for Inhibit' field to add/remove Inhibit Billing entries under 'Reason For Inhibit' code.
  13. Ensure that all fields in form are enabled following selection of 'Reason for Inhibit' field value.
  14. Enter/select values for service search/selection criteria in 'Rendering Practitioner', 'Client ID', 'Episode Number', 'Liable Guarantor', 'Program Where Service Was Rendered', 'Search Start Date' and/or 'Search End Date' fields. ('Rendering Practitioner' and/or 'Client ID' must be specified for service selection.)
  15. Select 'Uninhibited' in the 'Services to Display' selection field.
  16. Ensure that 'Services' selection field displays all service(s) for selected search/selection criteria which do not currently have an Inhibit Billing By Reason entry for selected 'Reason for Inhibit' value (if more than 50 services meet selected search/selection criteria entered, first 50 services meeting criteria are displayed initially).
  17. Click 'Next 50 Services' button to navigate through displayed services; click 'Prev 50 Services' to navigate backward through same displayed services.
  18. Ensure that if one or more service(s) is selected and 'Inhibit' button (or 'Uninhibit' button) is not used to file selections prior to use of 'Next 50 Services'/'Prev 50 Services' navigation button, user is presented with an error dialog noting 'Selections have been made. Please either click Inhibit or Uninhibit or clear the selections.'
  19. Ensure that if one or more service(s) are not selected and 'Inhibit' button (or 'Uninhibit' button) is clicked, user is presented with an error dialog noting 'No information found to file.'
  20. Select one or more individual service(s) for Inhibit Billing By Reason entry.
  21. Click 'Inhibit' button to file Inhibit Billing By Reason entry under selected Reason for Inhibit for selected service(s).
  22. Ensure user is presented with confirmation dialog noting 'Are you sure you want to inhibit billing for the selected services/reason?', with 'Yes' and 'No' buttons included; click 'Yes' button to continue with Inhibit Billing By Reason filing.
  23. Ensure user is presented with filing confirmation dialog noting 'Inhibit Billing By Reason filed successfully.'
  24. Ensure that service(s) where Inhibit Billing By Reason entry has been filed under selected 'Reason for Inhibit' are not displayed/included in the 'Services' selection field when 'Uninhibited' is selected in the 'Services to Display' field.
  25. Select 'Inhibited' in the 'Services to Display' selection field.
  26. Ensure that 'Services' selection field displays all service(s) for selected search/selection criteria which have an Inhibit Billing By Reason entry for selected 'Reason for Inhibit' value (if more than 50 services with Inhibit Billing By Reason entry meet selected search/selection criteria entered, first 50 services meeting criteria are displayed initially).
  27. Select one or more individual service(s) for Inhibit Billing By Reason 'Uninhibit'/removal action.
  28. Click 'Uninhibit' button to remove Inhibit Billing By Reason entry under selected Reason for Inhibit for selected service(s).
  29. Ensure user is presented with confirmation dialog noting 'Are you sure you want to uninhibit billing for the selected services/reason?', with 'Yes' and 'No' buttons included; click 'Yes' button to continue with removal of Inhibit Billing By Reason entry/'Uninhibit' action.
  30. Ensure user is presented with filing confirmation dialog noting 'Inhibit Billing By Reason filed successfully.'
  31. Ensure that service(s) where Inhibit Billing By Reason entry has been removed/'Uninhibited' under selected 'Reason for Inhibit' are not displayed/included in the 'Services' selection field when 'Inhibited' is selected in the 'Services to Display' field.
  32. Change value/select different value in 'Reason for Inhibit' field.
  33. Ensure that 'Services' selection field (following service search/selection criteria entry) includes only services with/without Inhibit Billing by Reason entries under selected 'Reason for Inhibit' value, and does not include Inhibit Billing by Reason entries for service(s) under any other code/reason (since a single service may have Inhibit Billing By Reason entries filed under multiple 'Reason for Inhibit' values).
  34. Open Crystal Reports or other SQL reporting tool.
  35. In Avatar Cal-PM SQL table 'SYSTEM.inhibit_billing', ensure that one row is included in table for each distinct service with Inhibit Billing By Reason entry; ensure that service row is removed from 'SYSTEM.inhibit_billing' table only if/when all Inhibit Billing By Reason entries for service are Uninhibited.
  36. In Avatar Cal-PM SQL table 'SYSTEM.inhibit_billing_reason', ensure that one row is included in table for each Inhibit Reason per service with Inhibit Billing By Reason entry; ensure that Inhibit Reason/service combination row is removed from 'SYSTEM.inhibit_billing_reason' table when Inhibit Billing By Reason entries for Inhibit Reason/service combination are Uninhibited.
  37. Open ‘Inhibit Billing By Reason' form.
  38. Select desired value in ‘Reason for Inhibit’.
  39. Enter the desired ‘Client ID’.
  40. Select desired ‘Episode Number’.
  41. If desired, enters dates ‘Search Start Date’ and ‘Search End Date’.
  42. Select ‘Uninhibited in ‘Service to Display’.
  43. Select desired service(s) to inhibit.
  44. Click [Inhibit].
  45. Click [Yes].
  46. Click [OK].
  47. Close the form.
  48. Open ‘Edit Service Information’.
  49. Select the inhibited service and change the service code.
  50. Click [Submit].
  51. Click [No].
  52. Open ‘Inhibit Billing By Reason' form.
  53. Select desired value in ‘Reason for Inhibit’.
  54. Enter the desired ‘Client ID’.
  55. Select desired ‘Episode Number’.
  56. Select ‘Inhibited in ‘Service to Display’.
  57. Validate that the previously inhibited service is still inhibited and displays the edited service code.
  58. Close the form.
Scenario 2: Cal-PM- Inhibit Billing By Service - Validating the service that is marked as billing inhibited
Specific Setup:
  • A practitioner must be associated to the user that is logged into the application (Practitioner A).
  • Practitioner A must be associated to services that exist for an existing client.
Steps
  1. Access the 'Inhibit Billing By Service' form.
  2. Enter the practitioner associated to the logged in user in the 'Rendering Practitioner' field.
  3. Select any value from the 'Select Service(s) To Mark Billing-Inhibited' field.
  4. Click [Submit].
  5. Validate a "Please review your selections" dialog is displayed.
  6. Click [OK].
  7. Validate a "File Service Inhibit Information" dialog is displayed stating: Continue Filing?
  8. Click [Yes].
  9. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  10. Click [No].
  11. Open the ‘Edit Service Information’ form.
  12. Edit the service code.
  13. Submit the form.
  14. Open the 'Inhibit Billing By Service' form.
  15. Validate that the service is still inhibited and displays the edited service code.
  16. Open the 'Close Charges' form.
  17. Enter all required information to close the service.
  18. Click [SUBMIT].
  19. Open the 'Client Ledger' form.
  20. Verify the service is in 'Open' status.
  21. Open the 'Crystal report' or any other SQL data viewer.
  22. Query the 'SYSTEM.billing_tx_history' table.
  23. Verify the 'billable_code' field displays 'X'.
  24. Close the report.

Topics
• 837 Institutional • 837 Professional • NX • Progress Notes • Quick Billing • Quick Billing Rule Definition • Inhibit Billing
Update 24 Summary | Details
Spreadsheet Edit Service Information - saving data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Spreadsheet Edit Service Information
Scenario 1: Validate 'Management Portal', 'License Usage' when submitting 'Spreadsheet Edit Service Information' form
Specific Setup:
  • Tester can access the cache Management Portal and has opened 'Usage by Process' in 'License Usage'. This will display the current processes.
  • Registry setting "RADplus->Database Management->Episode Predisplay->Sort Episodes by Admission Date".
  • Services:
  • Create new services or select existing services for distinct clients on the same date where there are 27 or more clients.
Steps
  1. Open the "Spreadsheet Edit Service Information" form.
  2. Select ‘All’ in ‘Individual Or All Programs’.
  3. Select ‘All’ in ‘All - Individual Or All Clients’.
  4. Select ‘No’ in ‘Only Show Services That Require A Diagnosis Or Are Primary Medical Program Services’.
  5. Select desired values in ‘Only Load Services With This Status’.
  6. Enter the service date in ‘Begin Date of Service’ and ‘End Date of Service’.
  7. Click [Edit Service Information].
  8. Edit at least one column for every row in the grid.
  9. Click [Save] and review the 'Usage by Process' in the Management Portal.
  10. Note that the 'Usage by Process' does not create a new process for each row in the spreadsheet.
  11. Click [Save].
  12. Click [Yes].
  13. Click [OK].
  14. Close the form.

Topics
• Edit Service Information
Update 25 Summary | Details
Site Specific Section Modeling - Practitioner Enrollment
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Site Specific Section Modeling (PM)
  • Practitioner Enrollment
Scenario 1: Practitioner Enrollment - Validating required site specific field - Adding a new practitioner
Specific Setup:
  • Site Specific Section Modeling:
  • The Site Specific Enrollment section on the Practitioner Enrollment form is enabled via the 'Site Specific Section Modeling' form.
  • At least one required and one optional field are added on the Site Specific section screen. Note the names of the field.
Steps
  1. Open the 'Practitioner Enrollment' form.
  2. Set the 'Select Staff' field to desired value.
  3. Click [New Staff].
  4. Validate the Staff dialog contains "Auto Assign Next ID Number?".
  5. Click [Yes].
  6. Set the 'Name' field to desired name.
  7. Select desired value in the 'Sex' field.
  8. Set the 'Date Of Birth' field to desired date.
  9. Set the 'Registration Date' field to desired date.
  10. Set the 'Office Address - Street field to desired value.
  11. Set the 'Office Address - Zip Code' field to desired value.
  12. Validate the 'Office Address - City' field auto populated.
  13. Set the 'Office Telephone (1)' field to desired value.
  14. Click the 'Categories/Taxonomy' item.
  15. Select "Create New" from the Category/Taxonomy dropdown list.
  16. Set the Effective Date field to the same date as 'Registration Date'.
  17. Select desired value from the 'Practitioner Category' dropdown list.
  18. Select desired value from the 'Discipline' dropdown list.
  19. Select desired value from the 'Practitioner Category For Coverage' checklist.
  20. Click [Add Practitioner Categories].
  21. Validate the 'Confirm Saved' message contains 'Please note: The changes will take effect when you submit the form.'
  22. Click [OK].
  23. Click the 'Site Specific Enrollment' item.
  24. Leave the required field empty.
  25. Click [Submit].
  26. Validate the missing required field error.
  27. Enter desired value to the required field.
  28. Make sure the optional field is empty.
  29. Click [Submit].
  30. Validate the form files without any error.
Scenario 2: Practitioner Enrollment - Validating required and optional site specific fields - Editing an existing practitioner
Specific Setup:
  • Registry Setting:
  • The 'Avatar PM->Practitioner->->->->Enable Practitioners link to Performing Providers' registry setting is set to "N".
  • Site Specific Section Modeling:
  • The Site Specific Enrollment section on the Practitioner Enrollment form is enabled via the 'Site Specific Section Modeling' form.
  • At least one required and one optional field are added on the Site Specific section screen. Note the names of the field.
  • An existing active practitioner is identified. Note the practitioner id/name.
Steps
  1. Open the 'Practitioner Enrollment' form for the practitioner identified above.
  2. Set the 'Select Staff' field to the practitioner identified above.
  3. Select the practitioner from the results list.
  4. Validate that all the required/ desired fields are populated correctly.
  5. Click the 'Site Specific Enrollment' item.
  6. Leave the required and optional fields empty.
  7. Click [Submit].
  8. Validate the error about missing required fields.
  9. Enter desired value to the required fields.
  10. Leave the optional field is empty.
  11. Click [Submit].
  12. Validate the form files without any error.
837 Institutional - Resolved diagnosis for discharge claims
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
  • Discharge
  • Electronic Billing
Scenario 1: 837 Institutional - Validating diagnosis segment (2300-HI) for the discharge claim - Running through last date of the service / Discharge date
Specific Setup:
  • Admission:
  • A new client is admitted into an inpatient program or an existing inpatient client is identified. Note the Client id/name. Admission date/program.
  • Financial Eligibility:
  • An existing guarantor is assigned to the client. Note the guarantor code/name.
  • Service Codes:
  • A new room and board service code is created or an existing room and board service code is identified. Note the service code.
  • Service Fee/ Cross Reference Maintenance:
  • A fee definition is created for the service code identified.
  • Client Charge Input:
  • The Room & Board services are rendered to the client for 5 days starting from the admission date.
  • Discharge:
  • The client is discharged after last date of the service.
  • Client Ledger:
  • All the charges are distributed to the primary guarantor of the client.
  • Close Charges:
  • The charges are closed.
  • An interim billing batch is created to include client, services and guarantor to the bill.
Steps
  1. Open an 'Electronic Billing' form.
  2. Compile an institutional bill for the primary guarantor using the interim billing batch created in the setup section.
  3. Verify the bill compile successfully.
  4. Run the report.
  5. Verify the report launched successfully.
  6. Review the report.
  7. Verify that the report displays the service rendered to the client.
  8. Launch the Dump file.
  9. Verify the bill contains HI segment of the resolved diagnosis.
Edit Service Information - Validating To-Do's after editing 'Open' service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Edit Service Information -
  • Set System Defaults (CWS)
  • User Definition
  • Delete Service
Scenario 1: Edit Service Information - Editing an open service - the service code is not configured for the work-flow
Specific Setup:
  • Service Codes:
  • A new service code is created or an existing service code is identified. Note the service code.
  • Service Fee/ Cross Reference Maintenance:
  • A fee definition is created for the service code identified in the ' Service Codes' form.
  • Admission:
  • A new client is created or an existing client is identified. Note the Client id/Name, Admission date / program.
  • Client Charge Input:
  • A service rendered to the client using the service code identified above.
  • Client Ledger:
  • The service is in 'Open' status.
Steps
  1. Open the 'Edit Service Information' form.
  2. Select the desired client in the 'Client ID' field.
  3. Select desired episode from the 'Episode Number' field.
  4. Click [Select Service(s) To Edit].
  5. Verify the 'Select Service(s) To Edit' dialog is displayed.
  6. Select desired service from the 'Select Service(s) To Edit' dialog.
  7. Enter a different value in the 'Duration (Minutes)' field.
  8. Select a new service code in the 'Service Code' field.
  9. Click [OK].
  10. Submit the form.
  11. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  12. Click [No].
  13. Query the 'SYSTEM.billing_tx_history' SQL table.
  14. Validate the 'PATID' column is equal to the correct client id identified in the setup.
  15. Validate the 'date_of_service' column is equal to correct date of service rendered to the client.
  16. Validate the 'duration' column is equal to the correct duration added in the 'Edit Service Information' form.
  17. Validate the 'Service Code' column contains correct service code submitted in the 'Edit Service Information' form.
  18. Validate the 'option_desc' column contains 'Edit Service Information'.
  19. Close the crystal report.
Scenario 2: Edit Service Information - Editing/Deleting an open service -the service code is configured for the work-flow
Specific Setup:
  • User Definition:
  • The logged in user (e.g. SYSADM) has a practitioner assigned.
  • Service Codes:
  • A new service code is created or an existing service code is identified. Note the service code.
  • Service Fee/ Cross Reference Maintenance:
  • A fee definition is created for the service code identified in the ' Service Codes' form.
  • Set System Defaults (CWS):
  • The service code identified above is configured for work-flow in the 'Workflow Service Setup' section of the form.
  • The 'Service Provider' is selected in the 'Send To Do Item To Which Staff Member' field.
  • Admission:
  • A new client is created or an existing client is identified. Note the Client id/Name, Admission date / program.
  • Client Charge Input:
  • A service rendered to the client using the service code identified above.
  • Client Ledger:
  • The service is in 'Open' status.
Steps
  1. Open the 'Edit Service Information' form.
  2. Select the desired client in the 'Client ID' field.
  3. Select desired episode from the 'Episode Number' field.
  4. Click [Select Service(s) To Edit].
  5. Verify the 'Select Service(s) To Edit' dialog is displayed.
  6. Select desired service from the 'Select Service(s) To Edit' dialog.
  7. Enter a different value in the 'Duration (Minutes)' field.
  8. Click [OK].
  9. Submit the form.
  10. Validate a "Form Return" message is displayed stating: Submitting has completed. Do you wish to return to form?
  11. Click [No].
  12. Query the 'SYSTEM.RADplus_workflow_to_do' SQL table.
  13. Validate the 'ENTITY_ID' column is equal to the correct client id identified in the setup.
  14. Validate the 'sending_user_desc' column is equal to the correct user associated with the rendering practitioner.
  15. Validate the 'outgoing_comments ' column contains correct comments for the specific service stating that it has been edited.
  16. Open the 'Delete Service' form.
  17. Select desired client from the 'Client ID' field.
  18. Set the Start Date input box to desired date.
  19. Set the End Date input box to desired date.
  20. Click [Display Client].
  21. Select desired service from the 'Service Delete' checklist.
  22. Click [OK].
  23. Click [Delete].
  24. Review the message about the services going to be deleted.
  25. Click [OK].
  26. Validate the WARNING! dialog contains "Continue Filing?"
  27. Click [Yes].
  28. Validate the 'Confirm' dialog contains "Deleted".
  29. Click [OK].
  30. Close the form.
  31. Query the 'SYSTEM.RADplus_workflow_to_do' SQL table.
  32. Validate the row is removed from the table.

Topics
• NX • Practitioner • 837 Institutional • Diagnosis • Edit Service Information
Update 26 Summary | Details
Program Maintenance - Cal-OMS Provider No Activity Submission Status
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
Scenario 1: Program Maintenance - Cal-OMS Provider No Activity Submission Status
Specific Setup:
  • Registry Settings:
  • Prior to installing the update, the following registry setting has a value of ‘Y or ‘YC’: 'Avatar PM->California Required EDI->CAL OMS Reporting->->->Enable LA County Reporting Requirements’. Note the value.
  • Program Maintenance is used to validate that the 'Cal-OMS Provider No Activity Submission Status' field is not on the form.
Steps
  1. Open ‘Registry Settings’.
  2. Set ‘Limit Registry Settings to the Following Search Criteria’ to ‘Avatar PM->California Required EDI->CAL OMS Reporting->->->Enable LA County Reporting Requirements’.
  3. Click [View Registry Settings].
  4. Set the ‘Registry Setting Value’ to’ Y’.
  5. Click [Submit].
  6. Close the form.
  7. Open ‘Program Maintenance’ for desired program. Validate that the 'Cal-OMS Provider No Activity Submission Status' field is not on the form.
  8. Close the form.
  9. Open ‘Registry Settings’.
  10. Set ‘Limit Registry Settings to the Following Search Criteria’ to ‘Avatar PM->California Required EDI->CAL OMS Reporting->->->Enable LA County Reporting Requirements’.
  11. Click [View Registry Settings].
  12. Set the ‘Registry Setting Value’ to ‘YC’.
  13. Click [Submit].
  14. Close the form.
  15. Open ‘Program Maintenance’ for desired program. Validate that the 'Cal-OMS Provider No Activity Submission Status' field is on the form. Set the value to the desired value and file the form.
  16. Reenter the same program and validate that the filed value was retained.
  17. Close the form.

Topics
• Cal-OMS • NX
Update 29 Summary | Details
Eligibility Inquiry (270) Submission
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
  • User Definition
  • Practitioner Enrollment
  • Practitioner Numbers By Guarantor and Program
  • Eligibility Inquiry (270) Request
  • Eligibility Inquiry (270) Submission
Scenario 1: Cal-PM - Eligibility Inquiry (270) Submission - validate maximum of 5000 files
Specific Setup:
  • Eligibility Inquiry (270) Submission
  • More than 5000 files exist for selection in the form.
Steps
  1. Open 'Eligibility Inquiry (270) Submission'.
  2. Select 'Run Report' in 'Options'.
  3. Enter a date range that contains more than 5000 files in the 'File From Date' and 'File Through Date' fields.
  4. Validate that an error message displays: More than 5000 entries found. Please refine your search.
  5. Click [OK].
  6. Change the date range to fewer days so that 5000 files or fewer display in 'Select File'.
  7. Validate that the files display in 'Select Files'.
  8. Repeat steps 3 - 7 for the following 'Options': 'Dump File'; 'Create File On Server For Submission'; and 'Delete File'.
  9. Close the form.

Topics
• Eligibility Inquiry (270) Request
Update 30 Summary | Details
274 - Site Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • User Definition
  • 274 - Provider Directory Defaults
  • 274 - Provider Directory Definition
  • 274 - Provider Directory Submission
Scenario 1: 274 - worklflow (274 - Provider Directory Defaults, 274 - Provider Directory Definition, 274 - Provider Directory Submission)
Specific Setup:
  • Tester has been given access to the following forms in 'User Definition' under ‘Avatar PM / System Maintenance / System Definition / Health Care Provider Directory (274)’:
  • 274 - Provider Directory Defaults.
  • 274 - Provider Directory Definition.
  • 274 - Provider Directory Submission.
Steps
  1. Open '274 - Provider Directory Defaults'.
  2. Validate that there are no required fields.
  3. Enter desired data for each field.
  4. Submit the form.
  5. Open '274 - Provider Directory Defaults'.
  6. Validate that the submitted data was retained.
  7. Open ‘274 - Provider Directory Definition’.
  8. Validate that the form opened to the ‘Group Definition’ section.
  9. Validate that 'Add or Edit Group' is the only required field.
  10. Select 'Add' in 'Add or Edit Group'.
  11. Validate that 'Active' and 'Provider Group Name (2100CA-NM1-03)' became required.
  12. Enter desired data for each field.
  13. Click [File Group Details].
  14. Select 'Edit' in 'Add or Edit Group'.
  15. Validate that the submitted data was retained.
  16. Select the 'Site Definition' section.
  17. Validate that 'Add or Edit Site' is the only required field.
  18. Select 'Add' in 'Add or Edit Site'.
  19. Validate that 'Site or Location of Service Name (2100DA-NM1-03)', 'Provider Group', and 'Active' became required.
  20. Validate that the field label 'Site or Location Address (2100DA-N3-01)' has been replaced with 'Site or Location Address (2110DA-N3-01)'.
  21. Validate that the field label 'Site or Location Address 2 (2100DA-N3-02)' has been replaced with 'Site or Location Address 2 (2110DA-N3-02)'.
  22. Enter desired data for each field, which would include nine digit zip codes with a hyphen.
  23. Click [Site Work Schedule (2100DA-WS)].
  24. Enter desired data.
  25. Click [Save].
  26. Click [Yes].
  27. Click [Foreign Languages Spoken At This Site (2100DA-LUI)].
  28. Enter desired data.
  29. Click [Save].
  30. Click [Yes].
  31. Click [Affiliated Entities (2100DB)].
  32. Enter desired data.
  33. Click [Save].
  34. Click [Yes].
  35. Click [File Site Details].
  36. Click [OK].
  37. Select 'Edit' in 'Add or Edit Site'.
  38. Validate that the submitted data was retained.
  39. Select the 'Provider Definition' section.
  40. Validate that 'Provider' is the only required field.
  41. Select a 'Provider'.
  42. Validate that 'Associated Site' and 'Active' became required.
  43. Enter desired data for each field.
  44. Click [File Provider Details].
  45. Click [OK].
  46. Select the same 'Provider'.
  47. Select the 'Associated Site' selected above.
  48. Validate that the submitted data was retained.
  49. Close the form.
  50. Open '274 - Provider Directory Submission'.
  51. Select 'Compile File' in 'Options'.
  52. Enter the desired value in 'Reporting Period (MM/YY)'.
  53. Enter desired 'File Description'.
  54. Click [Process File].
  55. Validate that the report display and that the zip code fields do not contain a hyphen.
  56. Validate the report data.
  57. Close the report.
  58. Close the form.

Topics
• 274 - Provider Directory
Update 32 Summary | Details
'CANS/PSC35 Submission' And 'CANS/PCS File Import' Forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CANS/PSC35 File Import
  • Child and Adolescent Needs and Strengths
  • CANS/PSC35 Submission - CANS Report
  • CANS/PSC35 Submission - CANS/PSC-35 Error Report
  • CANS/PSC35 Submission - PSC-35 Report
Scenario 1: 'CANS/PSC35 File Import' form - Verification of CANS/PSC35 File Import
Specific Setup:
  • 'Subscriber Client Index Number' value not present in 'Financial Eligibility' record for client/episode/guarantor eligible for CANS/PSC35 File Import
  • CANS/PSC35 import file with one or more import rows where physical field 5 ('Client Index Number (CIN)') value is included in import file
  • CANS/PSC35 import file with one or more import rows where physical field 5 ('Client Index Number (CIN)') value is not included in import file
Steps
  1. Open the Avatar Cal-PM 'CANS/PSC35 File Import' form (under 'Avatar PM / System Maintenance / Client Maintenance' menu).
  2. Select CANS or PSC35 Import file for processing in the 'Filename' field.
  3. Click 'Submit' button to process file.
  4. Ensure user is presented with dialog noting 'The file load process has started and may take a while based on the size of the file. Exiting the form at this time will not stop the load process'; click 'OK' button to close dialog/continue.
  5. Ensure user is presented with a confirmation dialog noting 'Submitting has completed. Do you with to return to form?'; click 'Yes' button to return to 'CANS/PSC35 File Import' form.
  6. Following CANS or PSC35 Import file processing, ensure 'Current File Load Status' field displays file processing result information, including 'File Name', 'Total Records Processed' and 'Number of Error(s) Encountered' values for processed import file data.
  7. In CANS/PSC35 Import file processing results - Ensure that where 'Subscriber Client Index Number' value is present in 'Financial Eligibility' record for client/episode/guarantor included in CANS/PSC35 Import file compilation, CANS/PSC35 Import record data/row(s) with or without 'Client Index Number (CIN)' value is/are successfully compiled/posted (with 'Client Index Number (CIN)' value as defined in relevant 'Financial Eligibility' record for client/episode/guarantor).
  8. In CANS/PSC35 Import file processing results - Ensure that where 'Subscriber Client Index Number' value is not present in 'Financial Eligibility' record for client/episode/guarantor included in CANS/PSC35 Import file compilation, CANS/PSC35 Import record data/row(s) without 'Client Index Number (CIN)' value is/are not successfully compiled/posted, and Import Error 'Invalid DATA for : Client Index Number (CIN) on Line ... Please set Client Index Number for associated Client in Financial Eligibility for PATID: ...' is displayed for relevant import file row(s).
Scenario 2: 'CANS/PSC35 Submission' form - Verification of CANS File Sorting with 'Subscriber Client Index Number' Value Not Present in Financial Eligibility Record
Specific Setup:
  • Client with 'Child and Adolescent Needs and Strengths' record eligible for CANS/PSC file inclusion
  • 'Subscriber Client Index Number' value not present in 'Financial Eligibility' record for client/episode/guarantor eligible for 'CANS/PSC35 Submission' reporting
Steps
  1. Open the Avatar Cal-PM 'CANS/PSC35 Submission' form (under 'Avatar PM / System Maintenance / Client Maintenance' menu).
  2. Select value in 'CANS/PSC Selection' field.
  3. Select 'Compile' in 'Option' field, and enter values for 'From Date' and 'Through Date' criteria fields.
  4. Click 'Submit' button to compile CANS (or PSC35) Submission file.
  5. Ensure user is presented with a confirmation dialog noting 'Submitting has completed. Do you with to return to form?'; click 'Yes' button to return to 'CANS/PSC35 Submission' form.
  6. Select 'Print' in 'Option' field, and select compiled file in 'Select File To Print/Submit' field.
  7. Click 'Print Selected File Error(s)' button to display CANS/PSC35 Submission file compilation Error Report data/results.
  8. In CANS/PSC35 Submission file Error Report/data, ensure that where 'Subscriber Client Index Number' value is not present in 'Financial Eligibility' record for client/episode/guarantor included in CANS/PSC35 Submission file compilation, CANS/client record data is not successfully included in submission data and is included in Error Report with Error Message 'Please set Client Index Number for associated Client in Financial Eligibility for PATID ...'
Scenario 3: 'CANS/PSC35 Submission' form - Verification of CANS File Compilation with 'Subscriber Client Index Number' Value Present in Financial Eligibility Record
Specific Setup:
  • Client with 'Child and Adolescent Needs and Strengths' record eligible for CANS/PSC file inclusion
  • 'Subscriber Client Index Number' value present in 'Financial Eligibility' record for client/episode/guarantor eligible for 'CANS/PSC35 Submission' reporting
Steps
  1. Open the Avatar Cal-PM 'CANS/PSC35 Submission' form (under 'Avatar PM / System Maintenance / Client Maintenance' menu).
  2. Select value in 'CANS/PSC Selection' field.
  3. Select 'Compile' in 'Option' field, and enter values for 'From Date' and 'Through Date' criteria fields.
  4. Click 'Submit' button to compile CANS (or PSC35) Submission file.
  5. Ensure user is presented with a confirmation dialog noting 'Submitting has completed. Do you with to return to form?'; click 'Yes' button to return to 'CANS/PSC35 Submission' form.
  6. Select 'Print' in 'Option' field, and select compiled file in 'Select File To Print/Submit' field.
  7. Click 'Print Selected File Information' button to display CANS/PSC35 Submission file compilation data/results.
  8. In CANS/PSC35 Submission file report/data, ensure that where 'Subscriber Client Index Number' value is present in 'Financial Eligibility' record for client/episode/guarantor included in CANS/PSC35 Submission file compilation, CANS/client record data is successfully included in submission data (with 'Client Index Number (CIN)' value as defined in relevant 'Financial Eligibility' record for client/episode/guarantor).
  9. Select 'Submit (Create File)' in 'Option' field, and select compiled file in 'Select File To Print/Submit' field.
  10. Select 'Final' or 'Review' in 'Create File' field.
  11. Click 'Submit' button to create CANS (or PSC35) Submission file on server.
  12. Ensure that CANS (or PSC35) Submission file is created on server (in output path/location defined via 'Facility Defaults' form).

Topics
• CANS/PSC35 File Import • CANS/PSC35 Submission • NX
Update 34 Summary | Details
Task Scheduler Widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • System Task Scheduler
  • Task Scheduler Status
Scenario 1: Task Scheduler Status Widget - validate task executions
Specific Setup:
  • In the 'System Task Scheduler', a minimum of two active tasks and one inactive task should be filed.
  • 'View Definition' form has been used to add the ‘Task Scheduler Status’ widget to HomeView for the logged in user.
Steps
  1. Access the ‘Task Scheduler Status’ widget on the Home View.
  2. Validate that the widget can be undocked, refreshed, and either minimized (Non NX View) or removed (NX View).
  3. Validate that the widget contains the following columns: ‘Application’, ‘Task’. ‘Inactive’, ‘Recur’, ‘Start Date’, ‘End Date’, ‘Last Run Date’, ‘Last Run Time’, and ‘Last Run Status’.
  4. Validate the data in each column is accurate. Note that for any task which has an error, the error will display in the 'Last Run Status' column.

Topics
• NX • System Task Scheduler • Widgets
Update 37 Summary | Details
Financial Eligibility - Subscriber Sex
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dictionary Update (PM)
  • Update Client Data
Scenario 1: Cal-PM - 'Client's Relationship To Subscriber' - Update Client Data 'Sex' field / Financial Eligibility 'Subscriber Sex' field
Specific Setup:
  • Registry Setting: Avatar PM->Client Information->Client Demographics->->->Update Financial Eligibility Data = Y.
  • Dictionary Update:
  • Client Dictionary – (3) Sex – Every value has an extended dictionary value for ‘Gender (837 Professional/Institutional)’. Note the extended dictionary values.
  • Client Dictionary - (837 Professional/Institutional) contains values of Female, Male, and Unknown.
  • Client Dictionary - (247) Client's Relationship To Subscriber:
  • Dictionary Value = Self contains desired extended values. Note the extended dictionary values.
  • Dictionary Value = Any other dictionary value contains desired extended values. Note the extended dictionary values.
  • Client: ‘Sex’ contains either ‘Transgender (F to M)’ or ‘Transgender (M to F)’. Note the value.
  • Update ‘Financial Eligibility to 'Self' in 'Client's Relationship To Subscriber' and desired value in ‘Subscriber Sex’. Note the value.
Steps
  1. Open ‘Update Client Data’.
  2. Validate that ‘Sex’ contains the value noted in setup.
  3. Submit the form.
  4. Open ‘Financial Eligibility’.
  5. Select the ‘Guarantor Selection’ section.
  6. Validate that ‘Subscriber Sex’ contains the dictionary values of ‘Female’, ‘Male’, and ‘Unknown’.
  7. Validate that 'Client's Relationship To Subscriber' contains ‘Self’ and that the ‘Subscriber Sex’ contains the ‘Gender (837 Professional/Institutional)’ extended dictionary value from ‘Client Dictionary – (3) Sex’ for the ‘Sex’ field value in ‘Update Client Data’.
  8. Change the ‘Subscriber Sex’ to a different value.
  9. Submit the form.
  10. Open ‘Update Client Data’.
  11. Validate that ‘Sex’ contains the value noted in setup.
  12. Submit the form.
  13. Open ‘Financial Eligibility’.
  14. Select the ‘Guarantor Selection’ section.
  15. Validate that 'Client's Relationship To Subscriber' contains ‘Self’ and that the ‘Subscriber Sex’ contains the ‘Gender (837 Professional/Institutional)’ extended dictionary value from ‘Client Dictionary – (3) Sex’ for the ‘Sex’ field value in ‘Update Client Data’.
  16. Select the ‘Subscriber Sex’ value that has not been previously selected.
  17. Submit the form.
  18. Open ‘Update Client Data’.
  19. Validate that ‘Sex’ contains the value noted in setup.
  20. Submit the form.
  21. Open ‘Financial Eligibility’.
  22. Select the ‘Guarantor Selection’ section.
  23. Validate that 'Client's Relationship To Subscriber' contains ‘Self’ and that the ‘Subscriber Sex’ contains the ‘Gender (837 Professional/Institutional)’ extended dictionary value from ‘Client Dictionary – (3) Sex’ for the ‘Sex’ field value in ‘Update Client Data’.
  24. Close the form.
  25. Open ‘Update Client Data’.
  26. Change ‘Sex’ to a non-transgender value. Note the value.
  27. Submit the form.
  28. Open ‘Financial Eligibility’.
  29. Select the ‘Guarantor Selection’ section.
  30. Validate that 'Client's Relationship To Subscriber' contains ‘Self’ and that the ‘Subscriber Sex’ contains the ‘Gender (837 Professional/Institutional)’ extended dictionary value from ‘Client Dictionary – (3) Sex’ for the ‘Sex’ field value in ‘Update Client Data’.
  31. Submit the form.
  32. Open ‘Update Client Data’.
  33. Validate that ‘Sex’ contains the changed value.
  34. Submit the form.
  35. Open ‘Financial Eligibility’.
  36. Select the ‘Guarantor Selection’ section.
  37. Validate that 'Client's Relationship To Subscriber' contains ‘Self’ and that the ‘Subscriber Sex’ contains the ‘Gender (837 Professional/Institutional)’ extended dictionary value from ‘Client Dictionary – (3) Sex’ for the ‘Sex’ field value in ‘Update Client Data’.
  38. Change the 'Client's Relationship To Subscriber' to the other dictionary value from setup.
  39. Set ‘Subscriber Sex’ to a value that contradicts the ‘Sex’ field value in ‘Update Client Data’.
  40. Submit the form.
  41. Open ‘Update Client Data’.
  42. Validate that ‘Sex’ contains the changed value.
  43. Submit the form.
  44. Open ‘Financial Eligibility’.
  45. Select the ‘Guarantor Selection’ section.
  46. Validate that 'Client's Relationship To Subscriber' contains the changed value and that the ‘Subscriber Sex’ contains the value that contradicts the ‘Sex’ field value in ‘Update Client Data’.
  47. Select the ‘Subscriber Sex’ value that has not been previously selected.
  48. Submit the form.
  49. Open ‘Update Client Data’.
  50. Validate that ‘Sex’ contains the value noted in setup.
  51. Submit the form.
  52. Open ‘Financial Eligibility’.
  53. Select the ‘Guarantor Selection’ section.
  54. Validate that 'Client's Relationship To Subscriber' contains the changed value and that the ‘Subscriber Sex’ contains the value the changed value.
  55. Close the form.
Registry Setting - Exclude Services If No Treatment Plan
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
  • Guarantors/Payors
  • Electronic Billing
Scenario 1: 837 Professional - 'Exclude Services If No Treatment Plan'
Specific Setup:
  • Registry Setting: ‘Exclude Services If No Treatment Plan’.
  • Note: For our testing purposes, we will start with a value of ‘Y’.
  • 'Y' adds the 'Exclude Service From Bill If No Final Treatment Plan In Effect For Service Date In Question' field to the 'Guarantors/Payors' form. It also adds the fields 'Treatment Plan Required' and 'Number Of Days After Admission That Treatment Plan Is Required' to the 'Program Maintenance' form.
  • 'P' adds or retains the 'Exclude Service From Bill If No Final Treatment Plan In Effect For Service Date In Question' field on the 'Guarantors/Payors' form and adds and a new section, 'Treatment Plan Requirements' to the form.
  • N’ removes all fields/sections from the 'Program Maintenance' and the 'Guarantors/Payors' forms.
  • Program Maintenance: Select a program and add a value of ‘Y’ to 'Treatment Plan Required' and if desired, a value to and 'Number Of Days After Admission That Treatment Plan Is Required'.
  • 'Guarantors/Payors':
  • Select a guarantor and add a value of ‘Yes’ in 'Exclude Service From Bill If No Final Treatment Plan In Effect For Service Date In Question'. Note the ‘Financial Class’.
  • Client A:
  • Is enrolled in the program selected above.
  • Is assigned the above 'Guarantors/Payors' in ‘Financial Eligibility’.
  • Does not have a Treatment Plan.
  • Has unclaimed closed services, noting the service dates and service codes.
  • Create Interim Billing Batch File has been used to create a batch for the guarantor, program, and client.
Steps
  1. Open ‘Electronic Billing’.
  2. Select ‘837-Professional in ‘Billing Form’.
  3. Select desired ‘Financial Class’ in ‘Type of Bill’.
  4. Select ‘Individual in ‘Individual Or All Guarantors’.
  5. Select the desired ‘Guarantor’.
  6. Select ‘Outpatient’ in ‘Billing Type’
  7. Select ‘Sort File’ in ‘Sort File’.
  8. Enter desired ‘File Description/Name’.
  9. Select ‘Interim Batch’ in ‘All Clients Or Interim Billing Batch’.
  10. Select desired value in ’Create Claims’.
  11. Enter ‘Date Of Claim’ if ‘Yes’ selected in ’Create Claims’.
  12. Enter ‘First Date Of Service To Include’ and ‘Last Date Of Service To Include’. Suggest one date for both fields.
  13. Select desired value in ‘Include Primary and/or Secondary Billing’.
  14. Click [Process].
  15. Validate that the ‘No Valid Information Found. Please Check The Error Report’ message displays.
  16. Click [OK].
  17. Select ‘Run Report’ in ‘Sort File’.
  18. Select ‘Print’ in ‘Print Or Delete Report’.
  19. Select the desired ‘File’.
  20. Click [Print 837 Report].
  21. Click the ‘Required Data Missing: Patient Service Data’ link.
  22. Validate the message indicates ‘No Final Treatment Plan In Effect For Service’.
  23. Close the report.
  24. Close the form.
  25. Open 'Guarantors/Payors'.
  26. Edit the guarantor from setup.
  27. Select 'No' in 'Exclude Service From Bill If No Final Treatment Plan In Effect For Service Date In Question'.
  28. Click [File].
  29. Close the form.
  30. Open ‘Program Maintenance’.
  31. Edit the program from setup.
  32. Set 'Treatment Plan Required' to ‘N’.
  33. Click [File].
  34. Close the form.
  35. Open ‘Electronic Billing’.
  36. Repeat ‘Electronic Billing’ steps for one service date.
  37. Validate ‘Compile Complete’ message is received after [Process] is clicked.
  38. If desired, review the dump file.
  39. Close the report.
  40. Close the form.
  41. If desired, continue additional testing with ‘Exclude Services If No Treatment Plan’ registry setting value set to 'Y'.
  42. Open 'Registry Settings'.
  43. Change the value of ‘Exclude Services If No Treatment Plan’ to 'P'.
  44. Submit the form.
  45. Close the form.
  46. Open ‘Program Maintenance’.
  47. Edit the program from setup.
  48. Validate that the 'Treatment Plan Required' and 'Number Of Days After Admission That Treatment Plan Is Required' fields are no longer on the form.
  49. Close the form.
  50. Open 'Guarantors/Payors'.
  51. Edit the guarantor from setup.
  52. Validate that the 'Exclude Service From Bill If No Final Treatment Plan In Effect For Service Date In Question' field retained the previously filed value. Set the value to ‘Yes’.
  53. Validate that the 'Treatment Plan Requirements' section has been added to the form.
  54. Select the section.
  55. Select program from setup in ‘Select Programs’.
  56. Select services codes from setup in ‘Select Services’.
  57. Select ‘No’ in ‘Treatment Plan Required’.
  58. If desired, add values to ‘Remaining Services To Generate To Do’, ‘Default Treatment Plan Coverage (Days)’ and ‘Day/Service Count Rule For Final Treatment Plan’.
  59. Click [Update].
  60. Select the ‘Guarantors/Payors’ section.
  61. Click [File].
  62. Close the form.
  63. Open ‘Electronic Billing’.
  64. Repeat ‘Electronic Billing’ steps for one service date.
  65. Validate ‘Compile Complete’ message is received after [Process] is clicked.
  66. If desired, review the dump file.
  67. Close the report.
  68. Close the form.
  69. Edit the guarantor from setup.
  70. Validate that the 'Exclude Service From Bill If No Final Treatment Plan In Effect For Service Date In Question' field is set to ‘Yes’.
  71. Select the ‘'Treatment Plan Requirements' section’.
  72. Select the previously submitted plan in ‘Select Treatment Plan Requirements’.
  73. Change ‘Treatment Plan Required’ to ‘Yes’.
  74. Click [Update].
  75. Select the ‘Guarantors/Payors’ section.
  76. Click [File].
  77. Close the form.
  78. Open ‘Electronic Billing’.
  79. Repeat ‘Electronic Billing’ steps for one service date.
  80. Click [Process].
  81. Validate that the ‘No Valid Information Found. Please Check The Error Report’ message displays.
  82. Click [OK].
  83. Select ‘Run Report’ in ‘Sort File’.
  84. Select ‘Print’ in ‘Print Or Delete Report’.
  85. Select the desired ‘File’.
  86. Click [Print 837 Report].
  87. Click the ‘Required Data Missing: Patient Service Data’ link.
  88. Validate the message indicates ‘No Final Treatment Plan In Effect For Service’.
  89. Close the report.
  90. Close the form.
  91. If desired, continue additional testing with ‘Exclude Services If No Treatment Plan’ registry setting value set to 'P'.
  92. Open 'Registry Settings'.
  93. Change the value of ‘Exclude Services If No Treatment Plan’ to ‘N’.
  94. Submit the form.
  95. Close the form.
  96. Validate that the 'Exclude Service From Bill If No Final Treatment Plan In Effect For Service Date In Question' field does not exist.
  97. Validate that the 'Treatment Plan Requirements' section does not exist.
  98. Open ‘Electronic Billing’.
  99. Repeat ‘Electronic Billing’ steps for one service date.
  100. Validate ‘Compile Complete’ message is received after [Process] is clicked.
  101. If desired, review the dump file.
  102. Close the report.
  103. Close the form.

Topics
• Financial Eligibility • NX • Update Client Data • Treatment Plan
Update 38 Summary | Details
'File Import' - Program Maintenance
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
Scenario 1: Program Maintenance - Add/Edit program
Steps
  1. Access the 'Program Maintenance' form.
  2. Select "Add" in the 'Add Or Edit Program' field.
  3. Enter the desired value in the 'Program Code' field.
  4. Enter the desired value in the 'Description' field.
  5. Populate all other required and desired fields.
  6. Validate the 'EVV Provider Organization ID' field is displayed.
  7. Enter the desired value in the 'EVV Provider Organization ID' field.
  8. Click [File Program].
  9. Select "Edit" in the 'Add Or Edit Program' field.
  10. Select the program added in the previous steps in the 'Program' field.
  11. Validate all previously filed data is displayed.
  12. Validate the 'EVV Provider Organization ID' field contains the value entered in the previous steps.
  13. Update any desired fields.
  14. Click [File Program] and close the form.
Scenario 2: Cal-PM - File Import - Validate 'Program Maintenance' Import
Specific Setup:
  • Have a valid 'Program Maintenance' import file (File A) created that contains a data row for a program with the following:
  • A value populated in the 'EVV Provider Organization ID' field
  • Value(s) in the 'Associated Service Programs' field
Steps
  1. Access the 'File Import' form.
  2. Select "Program Maintenance" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Navigate to the location of "File A" and click [Open].
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select "File A" in the 'File(s)' field.
  8. Click [Process Action].
  9. Validate a message is displayed stating "Compiled" and click [OK].
  10. Select "Print File" in the 'Action' field.
  11. Select "File A" in the 'File(s)' field.
  12. Click [Process Action].
  13. Validate a report is displayed for the program data in "File A".
  14. Close the report.
  15. Select "Post File" in the 'Action' field.
  16. Select "File A" in the 'File(s)' field.
  17. Click [Process Action].
  18. Validate a message is displayed stating "Posted" and click [OK].
  19. Close the form.
  20. Access the 'Program Maintenance' form.
  21. Select "Edit" in the 'Add Or Edit Program' field.
  22. Select the program imported via 'File Import' in the 'Program' field.
  23. Validate all imported data is populated as expected.
  24. Validate the 'Associated Service Programs' field contains the programs imported in the previous steps.
  25. Validate the 'EVV Provider Organization ID' field contains the value imported in the previous steps.
  26. Close the form.
Program Maintenance - 'EVV Provider Organization ID' field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SoapUI - ProgramMaintenance
  • SoapUI - ProgramMaintenance - AddProgramMaintenance
  • Program Maintenance
Scenario 1: 'WEBSVC.ProgramMaintenance' - add a program
Steps
  1. Access SoapUI for the 'ProgramMaintenance' - 'AddProgramMaintenance' 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 "Y" in the 'Active' field.
  6. Enter the desired value in the 'Description' field.
  7. Enter the desired value in the 'Location' field.
  8. Enter the desired value in the 'Program' field.
  9. Enter the desired value in the 'ProgramCode' field.
  10. Enter the desired value in the 'ProgramType' field.
  11. Enter the desired value in the 'RRG' field.
  12. Enter the desired value in the 'ReqAdmitPract' field.
  13. Enter the desired value in the 'TreatmentService' field.
  14. Enter the desired value in the 'TreatmentSetting' field.
  15. Enter the desired value in the 'UsageType' field.
  16. Enter the desired value in the 'EVVProviderOrgID' field.
  17. Populate any other desired fields.
  18. Click [Run].
  19. Validate the response contains: Program Maintenance web service has been filed successfully.
  20. Access the 'Program Maintenance' form.
  21. Select "Edit" in the 'Add Or Edit Program' field.
  22. Select the program added in the previous steps in the 'Program' field.
  23. Validate all previously filed data is displayed.
  24. Validate the 'EVV Provider Organization ID' field contains the value filed in the previous steps.
  25. Close the form.
Scenario 2: Program Maintenance - Add/Edit program
Steps
  1. Access the 'Program Maintenance' form.
  2. Select "Add" in the 'Add Or Edit Program' field.
  3. Enter the desired value in the 'Program Code' field.
  4. Enter the desired value in the 'Description' field.
  5. Populate all other required and desired fields.
  6. Validate the 'EVV Provider Organization ID' field is displayed.
  7. Enter the desired value in the 'EVV Provider Organization ID' field.
  8. Click [File Program].
  9. Select "Edit" in the 'Add Or Edit Program' field.
  10. Select the program added in the previous steps in the 'Program' field.
  11. Validate all previously filed data is displayed.
  12. Validate the 'EVV Provider Organization ID' field contains the value entered in the previous steps.
  13. Update any desired fields.
  14. Click [File Program] and close the form.
Scenario 3: Cal-PM - File Import - Validate 'Program Maintenance' Import
Specific Setup:
  • Have a valid 'Program Maintenance' import file (File A) created that contains a data row for a program with the following:
  • A value populated in the 'EVV Provider Organization ID' field
  • Value(s) in the 'Associated Service Programs' field
Steps
  1. Access the 'File Import' form.
  2. Select "Program Maintenance" in the 'File Type' field.
  3. Select "Upload New File" in the 'Action' field.
  4. Click [Process Action].
  5. Navigate to the location of "File A" and click [Open].
  6. Select "Compile/Validate File" in the 'Action' field.
  7. Select "File A" in the 'File(s)' field.
  8. Click [Process Action].
  9. Validate a message is displayed stating "Compiled" and click [OK].
  10. Select "Print File" in the 'Action' field.
  11. Select "File A" in the 'File(s)' field.
  12. Click [Process Action].
  13. Validate a report is displayed for the program data in "File A".
  14. Close the report.
  15. Select "Post File" in the 'Action' field.
  16. Select "File A" in the 'File(s)' field.
  17. Click [Process Action].
  18. Validate a message is displayed stating "Posted" and click [OK].
  19. Close the form.
  20. Access the 'Program Maintenance' form.
  21. Select "Edit" in the 'Add Or Edit Program' field.
  22. Select the program imported via 'File Import' in the 'Program' field.
  23. Validate all imported data is populated as expected.
  24. Validate the 'Associated Service Programs' field contains the programs imported in the previous steps.
  25. Validate the 'EVV Provider Organization ID' field contains the value imported in the previous steps.
  26. Close the form.

Topics
• File Import • Program Maintenance • Web Services
Update 40 Summary | Details
A new report: 'CPT License Count Report' is added to Avatar PM.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CPT License Count Report
Scenario 1: CPT License Count Report
Steps
  1. Open the 'CPT License Count Report'.
  2. Set the Start Date input box to any date.
  3. Set the End Date input box to any date.
  4. Click [Process].
  5. Validate the 'Date Range' item contains the Date range as entered on the selection screen.
  6. Validate the '#' column contains a numeric value for each listed line item.
  7. Validate the 'User Name' column contains only active Users.
  8. Validate the 'User ID' column contains only active User IDs.
  9. Validate the 'Provider Name' column contains only active Providers
  10. Validate the 'Provider ID' column contains only active Provider IDs.
  11. Validate the 'Provider Category' column contains the Provider Category associated to the Provider.
  12. Click [Close Report]
  13. Click [Close Form].
Copyright notice is added to forms where CPT content is displayed.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Real Time Inquiry (270 Request)
  • Program Maintenance
  • Confirm Compile Completed
  • Avatar NX Report Viewer
  • Payor Based Authorizations
  • Payor Based Authorizations Report
  • Eligibility Inquiry (270) Request
  • Eligibility Inquiry and Response (270/271) Report
Scenario 1: Process 'Real Time Inquiry (270) Request' with a value of 'Request Inquiry' in 'Eligibility Inquiry (270) Status'.
Specific Setup:
  • Agency uses 'Real Time Inquiry (270) Request' functionality.
  • Avatar PM 2018 Update 187 is installed.
  • At least one 'Guarantors/Payors' has a value of 'Yes' in 'Support 270/271 Transaction Sets'. Note the guarantor.
  • Selecting any client with the above 'Guarantors/Payors', update the 'Financial Eligibility' record to have a value of 'Request Inquiry' in 'Eligibility Inquiry (270) Status'. Note the client and the episode.
  • If the 'Request Type' is 'Specific', a 'Service Code' with a value in 'Service Type Code (270)' must exist.
Steps
  1. Open 'Real Time Inquiry (270) Request'.
  2. Select the client.
  3. Select the episode.
  4. Select the guarantor.
  5. Select any value in 'Request Type'.
  6. Select the 'Service Code' if 'Specific' was selected above.
  7. Verify the AMA trademark 'CPT® Codes' is displayed above the 'CPT-4 Code' field.
  8. Verify the AMA Copyright Notice 'CPT copyright 2021 American Medical Association. All rights reserved.' is displayed at the bottom of the form.
  9. Click [Process Request].
  10. Validate that submission is successful.
  11. If a system error message is received, review the 'Eligibility Inquiry and Response (270/271) Report' to correct client or setup issues.
Scenario 2: 'Program Maintenance' - Field Validation
Steps
  1. Access the 'Program Maintenance' form.
  2. Navigate to the 'Encounter CPT Code' field.
  3. Verify that the AMA CPT Code Trademark 'CPT® Codes' is displayed.
  4. Scroll to the bottom of the form.
  5. Verify that 'CPT copyright 2021 American Medical Association. All rights reserved.' is displayed.
  6. Close the form.
Scenario 3: Modifiers by Practitioner Category - Validation
Steps
  1. Open 'Modifiers by Practitioner Categories' form.
  2. Validate the CPT Code selection box contains 'CPT® Code'.
  3. Validate the AMA copyright notice displays at the bottom of the form: 'CPT copyright 2021 American Medical Association. All rights reserved.'.
  4. Close the form.
Scenario 4: 'Payor Based Authorizations' - Form Verification
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Enable Payor Based Authorizations' must be enabled
  • Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' may optionally be enabled/disabled
  • Crystal Reports or other SQL reporting tool
Steps
  1. Open Avatar Cal-PM 'Payor Based Authorizations' form (under 'Avatar PM / System Maintenance / System Definition' menu).
  2. Select 'Add' action in 'Add/Edit/Delete' field (or select 'Edit' action and click 'Select Authorizations To Edit/Delete' button to view/update existing Payor Based Authorization record/entry).
  3. Ensure the following fields are present in the 'Payor Based Authorizations' form:
  4. 'Guarantor'
  5. 'Service Code' (Not available when Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' is enabled)
  6. 'Effective Date'
  7. 'Expiration Date'
  8. 'Authorization Number'
  9. 'Display Authorizations' Button
  10. 'Select Authorizations To Edit/Delete' Button
  11. 'Select CPT ® Codes' Button (Available only when Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' is enabled)
  12. 'All CPT Codes' (Available only when Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' is enabled)
  13. Validate "CPT copyright 2021 American Medical Association. All rights reserved." Displays at the bottom of the form
  14. Enter/select values for all required/desired fields for Payor Based Authorization record/entry.
  15. Where Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' is enabled - Click 'Select CPT Codes' button and enter one or more code selections in the multi-iteration grid displayed (or set 'All CPT Codes' field to 'Yes').
  16. Click 'Submit' button to file 'Payor Based Authorizations' form/record.
  17. Select 'Edit' action in 'Add/Edit/Delete' field and click 'Select Authorizations To Edit/Delete' button to view/update previously entered Payor Based Authorization record/entry.
  18. Ensure all field values are present in 'Payor Based Authorizations' form/record as previously entered/filed.
  19. Click 'Display Authorizations' button to display the Payor Based Authorizations report/information.
  20. In Payor Based Authorizations report display/results, ensure that all Payor Based Authorization entries/records for selected 'Guarantor' value are displayed, including the following fields:
  21. 'Guarantor'
  22. 'Service Code' or 'CPT Code' (Dependent on Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations')
  23. 'Program' (To be employed by future Avatar Cal-PM update - Will display 'All Programs (NONE)' in report information)
  24. 'Practitioner Category' (To be employed by future Avatar Cal-PM update - Will display 'All Practitioner Categories (NONE)' in report information)
  25. 'Effective Date'
  26. Expiration Date'
  27. 'Authorization Number'
  28. Open Crystal Reports or other SQL reporting tool.
  29. Where Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' is disabled - In Avatar Cal-PM SQL table 'SYSTEM.table_payor_auths', ensure that data row(s) are added/updated on filing of 'Payor Based Authorizations' form and contain values/information filed via form for all applicable fields.
  30. Where Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' is enabled - In Avatar Cal-PM SQL table 'SYSTEM.table_payor_auths_cpt', ensure that data row(s) are added/updated on filing of 'Payor Based Authorizations' form and contain values/information filed via form for all applicable fields.
Scenario 5: Eligibility Inquiry (270) Request field validation
Specific Setup:
  • The following registry setting is enabled: 'Avatar PM->Billing->Electronic Submissions->Eligibility Inquiry & Response (270/271)->->Enable 270/271 Transaction Sets'.
Steps
  1. Open 'Eligibility Inquiry (270) Request'.
  2. Verify the 'CPT-4 Code' field contains the AMA Trademark 'CPT® Codes'.
  3. Verify the AMA copyright notice is displayed at the bottom of the form: 'CPT copyright 2021 American Medical Association. All rights reserved.'
Scenario 6: Eligibility Inquiry and Response (270/271) Report field validation
Steps
  1. Open 'Eligibility Inquiry and Response (270/271) Report'.
  2. Enter the 'Client ID' for the client that is not rejected.
  3. Verify the AMA Trademark displays 'CPT® Codes' above the 'CPT-4 Code' field.
  4. Verify the AMA Copyright Notice displays on the bottom of the form: 'CPT copyright 2021 American Medical Association. All rights reserved.'.
  5. Close the form.
CPT Code copyright notice is added to Avatar forms.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CPT Code Definition (PM)
Scenario 1: Service Fee/Cross Reference Maintenance - field validations
Steps
  1. Access the 'Service Fee/Cross Reference Maintenance' form.
  2. Verify the AMA Trademark displays 'CPT® Codes' above the 'CPT Code' field.
  3. Verify the AMA Copyright Notice displays on the bottom of the form: 'CPT copyright 2021 American Medical Association. All rights reserved.'.
  4. Close the form.
Avatar PM is enhanced with updated CPT codes.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CPT Code Definition (PM)
Scenario 1: CPT Codes: Annual code update
Steps
  1. Open Avatar PM 'CPT Code Definition' form.
  2. Click [Print CPT Codes].
  3. A list of the current CPT Codes will display.
  4. Review the list to assure new codes have been added.
  5. Click [Close].

Topics
• CPT License Count Report • NX • Eligibility Inquiry (270) Request • Eligibility Response (271) • Program Maintenance • Service Authorizations • Service Fee/Cross Reference Maintenance • CPT Codes
Update 42 Summary | Details
Database Management - SQL Query
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • CPT Code Definition (PM)
Scenario 1: Cal-PM: File Import - Service Fee/Cross Reference
Specific Setup:
  • Service Codes: Create two new service codes ( Service Code 1 & Service Code 2).
  • Use Service Fee/Cross Reference Maintenance to add a fee to Service Code 1.
  • Create a 'File Import' file for 'Service Fee/Cross Reference' for Service Code 2. Note the service code, from date, and fee.
  • The 'File Import' spreadsheet will be included in the update zip file.
Steps
  1. Open' File Import'.
  2. Load the file created in setup.
  3. Compile the file.
  4. If necessary correct errors, delete the existing file, load and compile again.
  5. Post the compiled file.
  6. Open 'Service Fee/Cross Reference Maintenance'.
  7. Select 'Edit Existing' in 'Enter New Or Edit Existing Fee/Cross Reference'
  8. Enter 'Service Code 2'.
  9. Enter the 'From Date'.
  10. Click [Select Fee/Cross Ref To Edit/Default From Existing].
  11. Select the desired row in the 'Edit Service Fee Definition' grid,
  12. Click [OK].
  13. Validate the data that was submitted in 'File Import' was saved.
Scenario 2: Cal-PM - SQL Table - SYSTEM.billing_tx_xref_table.
Specific Setup:
  • Prior to the update being installed, use Crystal Reports or other SQL reporting tool to process a query of the SYSTEM.billing_tx_xref_table. Save the results.
Steps
  1. After installation of the update, use Crystal Reports or other SQL reporting tool to process a query of the SYSTEM.billing_tx_xref_table. Save the results.
  2. Compare the results of the two queries to verify that the data is the same.
Cal-OMS Submission
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Dynamic Form - Cal-OMS Annual Update
  • Cal-OMS Annual Update
  • Cal-OMS Submission
Scenario 1: Cal-OMS - Annual Update
Specific Setup:
  • Registry Setting: Note the value of 'Avatar PM->California Required EDI->Cal OMS Reporting->->->Annual Update Number'.
  • A value of 'N' excludes the 'Annual Update Number' field on the 'Cal-OMS Annual Update' form.
  • A value of 'D' includes the 'Annual Update Number' field on the 'Cal-OMS Annual Update' form as a display only field and will contain the previously submitted 'Annual Update Number'
  • A value of 'E' includes the 'Annual Update Number' field on the 'Cal-OMS Annual Update' form as an enabled field. The user can override an existing value, or add a value if blank, if the entry is an integer. If a value is removed and left blank, the standard logic will apply the next time the 'Cal-OMS Annual Update' is processed.
  • Client: Select a client that has a submitted 'Cal-OMS Admission' and is due for the 'Cal-OMS Annual Update'.
Steps
  1. Open 'Cal-OMS Annual Update' for desired client.
  2. Add Data for all required field and desired optional fields. Note the date of entry.
  3. Click [Submit].
  4. Open 'Cal-OMS Submission'.
  5. Select 'Compile' in 'Option'.
  6. Enter a 'Through Date' that includes the date of entry.
  7. Click [Yes].
  8. Select 'Print' in 'Option'.
  9. Select desired file in 'Select File To Print/Submit'.
  10. Click [Print Selected File Annual Update Information].
  11. Validate that the selected client is included in the report.
  12. Close the report.
  13. Close the form.
Cal-OMS Submission - Deletion of submitted Discharge
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Cal-OMS Discharge
  • Cal-OMS Submission
  • Program Maintenance
  • Cal-OMS Admission
  • Dynamic Form - Cal-OMS File Submission
Scenario 1: Cal-OMS Submission - After Deletion of Cal-OMS Discharge
Specific Setup:
  • All Cal-OMS setup is complete.
  • Client 1: Is age 17 or younger and has a Cal-OMS admission in a Detox program. The admission has been submitted as a ‘Final’ submission.
  • Client 2: Is age 18 or older and has a Cal-OMS admission. The admission has been submitted as a ‘Final’ submission.
Steps
  1. Open ‘Cal-OMS Youth/Detox Discharge’ for Client 1. Note the date of discharge.
  2. Complete all the fields on the form, noting that some fields are disabled based on values in other fields.
  3. Submit the form.
  4. Open ‘Cal-OMS Discharge’ for Client 2. Note the date of discharge.
  5. Complete all the fields, in all sections, of the form, noting that some fields are disabled based on values in other fields.
  6. Submit the form.
  7. Open ‘Cal-OMS Submission’.
  8. Select ‘Compile’ in ‘Option’.
  9. Enter a ‘Through Date’ that included the above dates of discharge.
  10. Click [Submit].
  11. Select 'Print' in 'Option'
  12. Select the compiled file in 'Select File To Print/Submit'.
  13. Click [Print Selected File Discharge Information].
  14. Validate that both clients are in the report and contain no errors.
  15. Close the report.
  16. Close the form.
  17. Open ‘Cal-OMS Youth/Detox Discharge’ for Client 1.
  18. Select 'Discharge Delete' in 'Record to be Submitted'.
  19. Click Submit.
  20. Open ‘Cal-OMS Discharge’ for Client 2
  21. Select 'Discharge Delete' in 'Record to be Submitted'.
  22. Click Submit.
  23. Open ‘Cal-OMS Submission’.
  24. Select ‘Compile’ in ‘Option’.
  25. Enter a ‘Through Date’ that included the above dates of discharge.
  26. Click [Submit].
  27. Select 'Print' in 'Option'
  28. Select the compiled file in 'Select File To Print/Submit'.
  29. Click [Print Selected File Discharge Information].
  30. Validate that both clients are in the report and contain no errors.
  31. Close the report.
  32. Close the form.

Topics
• Database Management • Cal-OMS • NX
Update 43 Summary | Details
'Call Intake' is enhanced to add additional fields.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Call Intake
Scenario 1: Validate 'Call Intake' is not permitted for a client active in any program when Registry Setting 'Disallow Call Intakes For Program Types' is set to 'A'.
Specific Setup:
  • Registry Setting 'Disallow Call Intakes For Program Types' is set to 'A'. This setting will not allow any clients with active programs from being added in the 'Call Intake' form.
Steps
  1. Open 'Call Intake' form.
  2. Select a client with any active program.
  3. Verify the following message displays: 'Client is currently active. Only clients discharged from all programs or client in call status without a MR # can be accessed in this function.'
  4. Click [OK].
  5. The form will close.
Scenario 2: Registry Setting "Require Client's Address and Phone Number" is added to the admission form.
Specific Setup:
  • Registry Setting "Require Client's Address and Phone Number" is set to "Y". This setting will make the Client's Address and Phone Number required on the 'Admission', 'Admission (Outpatient)', 'Discharge','Discharge (Outpatient)', 'Pre Admit', 'Pre Admit Discharge', and 'Call-Intake' forms.
Steps
  1. Open the 'Call Intake' form
  2. Add a new client and leave the following fields blank:
  3. Client's Address - Street
  4. Client's Address - City
  5. Client's Address - State
  6. Client's Address - Zip Code
  7. Client's Phone Number - Home
  8. Click [Submit]
  9. Verify a message displays indicating that the above fields are required.
  10. Complete all required fields
  11. Click [Submit].
  12. Open the 'Call Intake' form for the same client.
  13. Verify the client address and phone number fields are populated.
Scenario 3: Registry Setting 'Add Demographics to Call Intake' is added to the 'Call Intake' form.
Specific Setup:
  • Registry Setting 'Add Demographics to Call Intake' is set to 'Y'. This setting will add the 'Demographics' tab and 'Sex', 'Date of Birth', 'Age', and 'Social Security Number' to the Call Intake form.
Steps
  1. Open 'Call Intake'.
  2. Set 'Last Name' to any last name (not an existing client).
  3. Set 'First Name' to any first name.
  4. Select any gender in the 'Sex' drop down list
  5. Click [Search].
  6. Click [New Client].
  7. Click [Call] in the 'Call Or Walk-in' field.
  8. Set the 'Caller Name' to any LastName,FirstName.
  9. Set the 'Call Date' to any date.
  10. Set the 'Call Time' to any time.
  11. Select any value from the 'Program' drop down list.
  12. Select any value from the 'Disposition' drop down list.
  13. Enter any text in the 'Comments for the call intake' text box.
  14. Set the 'Date of Birth' to any date in the past.
  15. Set the 'Social Security Number' to any SSN.
  16. Click the 'Demographics' tab.
  17. Select any value in the 'Prefix' drop down list.
  18. Set the 'Client's Address - Street' to any address.
  19. Set the 'Client's Address - Zipcode' to any zipcode.
  20. Set the 'Client's Home Phone' to any phone number.
  21. Set the 'Client's Work Phone' to any phone number.
  22. Set the 'Client's Cell Phone' to any phone number.
  23. Set the 'Client's Email Address' to any email address.
  24. Select any value in the 'Communication Preference' field.
  25. Select any value in the 'Primary Language' drop down list.
  26. Select any value in the 'Client Race' drop down list.
  27. Select any value in the 'Other Race(s)' list.
  28. Select any value in the 'Ethnic Origin' drop down list.
  29. Select any value from the 'Religion' drop down list.
  30. Set the 'Place of Birth' to any value.
  31. Select any value from the 'Marital Status' drop down list.
  32. Select any value from the 'Education' drop down list.
  33. Select any value from the 'Employment Status' drop down list.
  34. Select any value from the 'Occupation' drop down list.
  35. Select any value from the 'Are you heterosexual, lesbian, gay, bisexual, transgender or do you question your sexual orientation?' field.
  36. Select any value from the 'Smoker' drop down list.
  37. Set the 'Smoking Status Assessment Date' to any date.
  38. Set the 'Client's Mailing Address - Street' to any address.
  39. Set the 'Client's Mailing Address - Street 2' to any address.
  40. Set the 'Client's Mailing Address - Zipcode' to any zipcode.
  41. Set the 'Client's Mailing Address - City' to any City.
  42. Set the 'Client's Mailing Address - State' to any State.
  43. Select any value from the 'Client's Mailing Address - County' field.
  44. Click [Submit].
  45. Open the 'Call Intake' form for the same client.
  46. Verify the Demographic data is retained and correct.
  47. Close the form.
Scenario 4: Registry Setting 'Add SSN to Call Intake' is added to the 'Call Intake' form.
Specific Setup:
  • Registry Setting 'Add SSN to Call Intake' is set to 'Y'. Selecting 'Y' makes 'Social Security Number' field visible in the 'Call Intake' form. Select 'N' to make this field invisible.
Steps
  1. Open 'Call Intake' form.
  2. Select any existing client with a 'Call Intake' record.
  3. Select the client Episode.
  4. Click [Edit].
  5. Navigate to the 'Social Security Number' field at the bottom of the 'Call Intake' form.
  6. Enter the SSN for the client.
  7. Click [Submit].
  8. Open the 'Call Intake' form for the same client.
  9. Verify the SSN is displayed as entered.
  10. Close the form.
Scenario 5: Registry Setting 'Add Mailing Address' includes the 'Call Intake' form.
Specific Setup:
  • Registry Setting 'Add Mailing Address' is set to 'Y'. This setting will add the mailing address to multiple forms: 'Admission', 'Admission(Outpatient)', 'Call Intake, 'Discharge', 'Discharge(Outpatient)', 'Pre-Admit', 'Pre-Admit Discharge', and 'Update Client Data' forms.
Steps
  1. Open 'Call Intake'.
  2. Set 'Last Name' to any last name (not an existing client).
  3. Set 'First Name' to any first name.
  4. Select any gender in the 'Sex' drop down list
  5. Click [Search].
  6. Click [New Client].
  7. Click [Call] in the 'Call Or Walk-in' field.
  8. Set the 'Caller Name' to any LastName,FirstName.
  9. Set the 'Call Date' to any date.
  10. Set the 'Call Time' to any time.
  11. Select any value from the 'Program' drop down list.
  12. Select any value from the 'Disposition' drop down list.
  13. Enter any text in the 'Comments for the call intake' text box.
  14. Set the 'Date of Birth' to any date in the past.
  15. Set the 'Social Security Number' to any SSN.
  16. Click the 'Demographics' tab.
  17. Set the 'Client's Mailing Address - Street' to any address.
  18. Set the 'Client's Mailing Address - Street 2' to any address.
  19. Set the 'Client's Mailing Address - Zipcode' to any zipcode.
  20. Set the 'Client's Mailing Address - City' to any City.
  21. Set the 'Client's Mailing Address - State' to any State.
  22. Select any value from the 'Client's Mailing Address - County' field.
  23. Click [Submit].
  24. Open the 'Call Intake' form for the same client.
  25. Verify the Mailing Address data is retained and correct.
  26. Close the form.
Scenario 6: Validate 'Call Intake' is not permitted for a client active in any Inpatient program when Registry Setting 'Disallow Call Intakes For Program Types' is set to 'I'.
Specific Setup:
  • Client active in any Inpatient program
  • Registry Setting 'Disallow Call Intakes For Program Types' is set to 'I'.
Steps
  1. Open 'Call Intake' form.
  2. Select a client with any active program.
  3. Verify the following message displays: 'Client is currently active. Only clients discharged from all programs or client in call status without a MR # can be accessed in this function.'
  4. Click [OK].
  5. The form will close.
Scenario 7: Validate 'Call Intake' is permitted for a client active in any Outpatient program when Registry Setting 'Disallow Call Intakes For Program Types' is set to 'I'.
Specific Setup:
  • Client active in any Outpatient program
  • Registry Setting 'Disallow Call Intakes For Program Types' is set to 'I'.
Steps
  1. Open 'Call Intake' form for any client with an active Outpatient program episode.
  2. Select any value in the 'Call Or Walk-In' field.
  3. Select any value in the 'Caller Type' drop down list.
  4. Set the 'Call Date' to any date.
  5. Set the 'Call Time' to any time.
  6. Select any value in the 'Disposition' drop down list.
  7. Select any value in the 'Caller Intake/Comments' text box.
  8. Complete any required fields.
  9. Click [Submit].
Scenario 8: Validate 'Call Intake' is always permitted when Registry Setting 'Disallow Call Intakes For Program Types' is set to 'N'.
Specific Setup:
  • Registry Setting 'Disallow Call Intakes For Program Types' is set to 'N'.
Steps
  1. Open 'Call Intake' form for any client with any active program episode.
  2. Select any value in the 'Call Or Walk-In' field.
  3. Select any value in the 'Caller Type' drop down list.
  4. Set the 'Call Date' to any date.
  5. Set the 'Call Time' to any time.
  6. Select any value in the 'Disposition' drop down list.
  7. Select any value in the 'Caller Intake/Comments' text box.
  8. Complete any required fields.
  9. Click [Submit].

Topics
• Call Intake • NX • Registry Settings
Update 45 Summary | Details
'Team Assignment' is enhanced to no longer display inactive teams.
Scenario 1: 'Team Assignment' - validate Inactive and Deleted Teams are not in the 'Admission' form 'Team Assignment' selection drop down field.
Specific Setup:
  • RADplus 2022 Update 58 is required for full functionality.
  • One or more teams are defined in the 'Team Definition' form.
  • Client A is assigned to a team which will be flagged as 'Inactive'.
  • Using 'Team Definition', flag the team Client A is assigned to as 'Inactive'.
  • Client B is assigned to a team which will be deleted.
  • Using 'Team Definition', flag the team Client B assigned to as 'Deleted'
Steps
  1. Create a report against SQL Table 'admission_data_other'.
  2. Include in the report, at a minimum, the following fields:
  3. PATID
  4. team_assignment_value
  5. team_assignment_code
  6. data_entry_date
  7. Run the report. Note the values entered for Client A and Client B. The team_assignment_value and team_assignment_code fields will be blank for both clients.
  8. Open the 'Admission (Outpatient)' form. Note that this functionality is the same in the 'Admission' form as well.
  9. Select Client A.
  10. Verify that there is no selection in the 'Team Assignment' field.
  11. Navigate to the 'Team Assignment' field.
  12. Click on the drop down list.
  13. Verify that no Teams defined as 'Inactive' are displayed for selection.
  14. Select any active Team from the list.
  15. Click [Submit].
  16. Open the 'Admission (Outpatient)' form. Note that this functionality is the same in the 'Admission' form as well.
  17. Select Client B.
  18. Verify that there is no selection in the 'Team Assignment' field. This team has been deleted from the 'Team Definition' form.
  19. Navigate to the 'Team Assignment' field.
  20. Click on the drop down list.
  21. Verify that no Teams which were deleted are included in the drop down list.
  22. Select any active Team from the list.
  23. Click [Submit].
  24. Run the report again.
  25. Verify the team_assignment_value and team_assignment_code fields are populated for both Client A and Client B.

Topics
• Team Assignment • Team Definition
Update 47 Summary | Details
Interim Billing Batch Creation
Scenario 1: 'Create Interim Billing Batch' - Verification of Interim Billing Batch Creation
Specific Setup:
  • One or more service(s) eligible for Interim Billing Batch inclusion
Steps
  1. Open Avatar Cal-PM 'Create Interim Billing Batch' form.
  2. Select 'Create Batch' in 'Create, View Or Delete Batch' field.
  3. Enter/select value for 'Batch Description', 'Through Date', 'Individual Or All Guarantors Or Financial Class' and 'All Or Individual Or Treatment Settings' criteria fields.
  4. Enter/select value for any other fields as required/desired in form.
  5. Click 'Process' button to file 'Create Interim Billing Batch' file form and create Interim Billing Batch for specified criteria.
  6. Ensure that clients/services included in created Interim Billing Batch are displayed following form processing.
  7. Click 'Close' button to close Interim Billing Batch contents display.
Scenario 2: 'Liability Update' - Verification of Form Filing
Specific Setup:
  • One or more client(s)/service(s) eligible for Liability Update
Steps
  1. Open Avatar Cal-PM 'Liability Update' form.
  2. Enter/select value for 'Thru Date' and 'Individual, All, Or Interim Batch Cycle' fields.
  3. Enter/select value for any other fields as required/desired in form.
  4. Click 'Submit' to file 'Liability Update' form and process Liability Update for selected criteria.
  5. Ensure that 'Liability Update' form is closed on filing/completion.

Topics
• Interim Billing Batch • Liability Update • NX
Update 48 Summary | Details
File Import - 'Claim Follow-Up Notes' Support
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • File Import - Compile/Post Report
Scenario 1: 'File Import' - Verification of 'Claim Follow-Up Notes' Import
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Claim Follow-Up' must be enabled
  • Client with claim(s)/services(s) eligible for Claim Follow-Up/Claim Follow-Up Notes entry/import in Avatar Cal-PM
  • Avatar Cal-PM 'Claim Follow-Up Notes' Import File containing one or more valid import rows
  • Crystal Reports or other SQL reporting tool
Steps
  1. Open Avatar Cal-PM 'File Import' form.
  2. Select File Type 'Claim Follow-Up Notes'.
  3. Select 'Upload New File' in 'Action' field and Click 'Process Action' button.
  4. Select Avatar Cal-PM 'Claim Follow-Up Notes' import file and click 'Open' button.
  5. Select 'Compile/Validate File' in 'Action' field.
  6. Select loaded Claim Follow-Up Notes import file and click 'Process Action' button.
  7. Ensure that 'Compile/Validate File' action completes, and message 'Compiled' or '(File Name) contains one or more errors. These errors can be reviewed using 'Print Errors' action' is displayed.
  8. Click 'OK' button.
  9. Select 'Print File' in 'Action' field.
  10. Select compiled Claim Follow-Up Notes import file and click 'Process Action' button to view report.
  11. In File Import 'Claim Follow-Up Import' report, ensure that valid Claim Follow-Up Notes entries are successfully compiled/included in report (including Import File Line Number, 'Client ID', 'Client Name', 'Client Number', Follow-Up Date', etc.)
  12. Select 'Post File' in 'Action' field.
  13. Select compiled Claim Follow-Up Notes import file and click 'Process Action' button.
  14. Ensure that 'Post' action completes, and message 'Posted' and/or 'The selected file contains one or more lines with compilation errors. Only those lines without compilation errors will be posted' is displayed.
  15. Open Avatar Cal-PM 'Claim Follow-Up' form.
  16. Note, Claim Follow-Up Notes information posted via 'File Import' form may also be confirmed via the 'Claim Follow-Up Notes Report' form/report
  17. Select client where Claim Follow-Up/Claim Follow-Up Notes have been filed via 'File Import' form.
  18. Select 'Edit' in 'Add, Edit Or Delete Claim Follow-Up' field.
  19. Select Claim/Claim Follow-Up entry filed via 'File Import' form in 'Select Claim Follow-Up to Edit Or Delete' field.
  20. Ensure that Claim Follow-Up field values ('Insurance Based Denial Reason', etc.) reflect information filed via 'File Import' form.
  21. In Claim Follow-Up Notes section of form, select 'Edit' in 'Add, Edit Or Delete Row' field.
  22. Select Claim Follow-Up Note entry filed via 'File Import' form in 'Select Row to Edit Or Delete' field.
  23. Ensure that Claim Follow-Up Note field values ('Follow-Up Date', 'Completion Date', 'Follow-Up Status', etc.) reflect information filed via 'File Import' form.
  24. Open Crystal Reports or other SQL reporting tool.
  25. In Avatar Cal-PM SQL table 'SYSTEM.file_import_clm_follow_up', ensure that all compiled and/or posted File Import rows are present in SQL data and reflect values imported/compiled/posted via 'File Import' form 'Claim Follow-Up Notes' file type selection.
Scenario 2: 'File Import' - Verification of 'Claim Follow-Up Notes' Import Error Reporting
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Claim Follow-Up' must be enabled
  • Client with claim(s)/services(s) eligible for Claim Follow-Up/Claim Follow-Up Notes entry/import in Avatar Cal-PM
  • Avatar Cal-PM 'Claim Follow-Up Notes' Import File containing one or more invalid import rows
Steps
  1. Open Avatar Cal-PM 'File Import' form.
  2. Select File Type 'Claim Follow-Up Notes'.
  3. Select 'Upload New File' in 'Action' field and Click 'Process Action' button.
  4. Select Avatar Cal-PM 'Claim Follow-Up Notes' import file and click 'Open' button.
  5. Select 'Compile/Validate File' in 'Action' field.
  6. Select loaded Claim Follow-Up Notes import file and click 'Process Action' button.
  7. Ensure that 'Compile/Validate File' action completes, and message '(File Name) contains one or more errors. These errors can be reviewed using 'Print Errors' action' is displayed.
  8. Click 'OK' button.
  9. Select 'Print Errors' in 'Action' field.
  10. Select compiled Claim Follow-Up Notes import file and click 'Process Action' button to view report.
  11. In 'Claim Follow-Up Notes File Import Errors' report, ensure that invalid Claim Follow-Up Notes File Import rows/entries are displayed with error message/detail, including Import File Line Number, Column/Field Name, Import File Data Value and Error Message/Condition information.
  12. Claim Follow-Up Notes File Import error message examples:
  13. 'Missing required field'
  14. 'Invalid Client ID'
  15. 'Invalid Claim Number'
  16. 'Next Follow-Up Date cannot be a past date'
  17. 'Invalid dictionary code'

Topics
• Claim Follow-up • File Import
Update 50 Summary | Details
Program Maintenance - Substance Abuse Program (Cal-OMS)
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Program Maintenance
  • Cal-OMS Admission
  • Cal-OMS Submission
  • Guarantors/Payors
  • Electronic Billing
Scenario 1: Verify submission of Cal-OMS Admission
Specific Setup:

Cal-OMS setup exists.

Program Maintenance:

Program 1: Contains a value of ‘Yes (Reportable)’ in ‘Substance Abuse Program (Cal-OMS)’.

Program 2: : Contains a value of ‘Yes (Not Reportable)’ in ‘Substance Abuse Program (Cal-OMS)’.

Client 1: Is enrolled in Program 1.

Client 2: Is enrolled in Program 2.

Steps
  1. Open 'Cal-OMS Admission for Client 1.
  2. Enter data for all required and desired non-required fields. Note the admission date.
  3. Click [Submit].
  4. Open 'Cal-OMS Admission for Client 2.
  5. Validate the error message contains: Client does not have any Inpatient/Outpatient/Partial(Day) episodes within the current system code'.
  6. Open 'Cal-OMS Submission'.
  7. Select 'Compile' in 'Option'.
  8. Enter a 'Through Date' that includes the admission date for Client 1.
  9. Click [Submit].
  10. Click [Yes].
  11. Select 'Print' in 'Option'.
  12. Selected desired file in 'Select File To Print/Submit'.
  13. Click [Print Selected File Admission Information].
  14. Review the report to verify the data for Client 1.
  15. If desired, submit the file in review or final mode.
  16. Review the data in the submitted file.
  17. Close the form.
Scenario 2: 837 Professional - Cal-OMS Program
Specific Setup:

Cal-OMS setup exists.

Program Maintenance:

Program 1: Contains a value of ‘Yes (Reportable)’ in ‘Substance Abuse Program (Cal-OMS)’.

Program 2: Contains a value of ‘Yes (Not Reportable)’ in ‘Substance Abuse Program (Cal-OMS)’.

Client 1:

Is enrolled in Program 1.

Has financial eligibility and diagnosis records.

Has closed, unclaimed services. Note the date range and the guarantor.

If necessary, review the Guarantors/Payors form to note the 'Financial Class' of the guarantor.

Create Interim Billing Batch File has been used to create a batch specific to Client 1.

Client 2:

Is enrolled in Program 2.

Has financial eligibility and diagnosis records.

Has closed, unclaimed services. Note the date range and the guarantor.

If necessary, review the Guarantors/Payors form to note the 'Financial Class' of the guarantor.

Create Interim Billing Batch File has been used to create a batch specific to Client 2.

Steps
  1. Open ‘Electronic Billing’.
  2. Select ‘837 Professional’ in ‘Billing Form’.
  3. Select the desired ‘HIPAA Transaction Version’.
  4. Select the ‘Financial Class’ in ‘Type Of Bill’. This is for Client 1.
  5. Select ‘Individual’ in ‘Individual Or All Guarantors’.
  6. Select the desired ‘Guarantor’.
  7. Select ‘Outpatient’ in ‘Billing Type’.
  8. Select ‘Sort File’ in ‘ Billing Options’.
  9. Enter desired ‘File Description/Name’.
  10. Select ‘Interim Batch’ in ‘All Clients or Interim Billing Batch’.
  11. Select desired ‘Interim Batch Number’.
  12. Select desired value in ‘Create Claims’. If yes, enter a value on ‘Date of Claim’.
  13. Enter desired value in ‘First Date Of Service To Include’.
  14. Enter desired value in ‘Last Date Of Service To Include’.
  15. Select ‘All’ in ‘Include Primary and/or Secondary Billing’.
  16. Click [Process].
  17. Click [OK].
  18. Select ‘Dump File’ in ‘Billing Options’.
  19. Select ‘Print’ in ’Print Or Delete Report’.
  20. Select the desired ‘File’.
  21. Click [Process].
  22. Validate the date within the file to ensure expected services are output with expected data.
  23. Close the report.
  24. Close the form.

Topics
• 837 Professional • Cal-OMS
Update 51 Summary | Details
Avatar Cal-PM is prepared for future functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Delete Bed Assignment
  • CareFabric Monitor
Scenario 1: Validate 'Bed Assignment' and 'Delete Bed Assignment' on 'CareFabric Monitor' for Cal-PM
Specific Setup:
  • Inpatient client assigned to a room and bed (Client A).
Steps
  1. Open 'Bed Assignment'.
  2. Select 'Client A'.
  3. Assign a different 'Unit', 'Room' and 'Bed' and click [Submit].
  4. Open 'Delete Bed Assignment'.
  5. Select 'Client A' and the corresponding episode.
  6. Select the last 'Bed assignment' from the 'Bed Assignment to Delete' field.
  7. Click [Submit].
  8. Open 'CareFabric Monitor'.
  9. Enter the current date in the 'From Date' field.
  10. Enter the current date in the 'Through Date' field.
  11. Select 'Client A'.
  12. Click [View Activity Log].
  13. Verify the data is correct.
  14. Click [Click to View Record].
  15. Verify the data is correct.

Topics
• Bed Assignment • CareFabric Monitor
Update 58 Summary | Details
'Guarantors/Payors' Form 'Treatment Plan Requirements' Fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Guarantors/Payors
  • File Import - Guarantors/Payors Treatment Plan Requirements
  • File Import - Compile/Post Report
  • Electronic Billing
  • Electronic Billing - Electronic Billing report
  • Treatment Plan
Scenario 1: 'Guarantors/Payors' - Verification of 'Treatment Plan Requirement' Form Section/Fields
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Exclude Services If No Treatment Plan' must be enabled (set to 'P')
  • Crystal Reports or other SQL reporting tool
Steps
  1. Open Avatar Cal-PM 'Guarantors/Payors' form.
  2. Select Add or Edit action in 'Add New or Edit Existing Guarantor' field.
  3. Enter new (or select existing) Guarantor Code.
  4. Complete all required/desired fields in main section of 'Guarantors/Payors' form.
  5. Navigate to 'Treatment Plan Requirements' section of 'Guarantors/Payors' form.
  6. Ensure that the 'Requirement Start Date' and 'Requirement End Date' fields are available in form.
  7. If the date of service falls outside of the Requirement Start/End Date Range it will not be included in the Treatment Plan Requirements definition/check
  8. 'Requirement Start Date' and 'Requirement End Date' fields are not required; if no value entered, the Treatment Plan Requirement definition/check will apply to all dates
  9. If value is entered for either 'Requirement Start Date' or 'Requirement End Date' field, value must be entered for both fields
  10. Enter value for 'Requirement Start Date' and 'Requirement End Date' fields (and any other required/desired fields in 'Treatment Plan Requirements' section of form).
  11. Click 'Update' button to save Treatment Plan Requirement entry; repeat entry for additional Treatment Plan Requirements if desired.
  12. Navigate to main section of 'Guarantors/Payors' form.
  13. Click 'File' button to save/file Guarantor/Payor definition information.
  14. Select 'Edit' action and select previously filed Guarantor Code.
  15. Navigate to 'Treatment Plan Requirements' section of 'Guarantors/Payors' form.
  16. Select previously entered/filed Treatment Plan Requirement in 'Select Treatment Plan Requirements' field.
  17. Ensure that previously entered/filed values for 'Requirement Start Date' and 'Requirement End Date' fields are present in form (as well as values for all other fields in 'Treatment Plan Requirements' section of form).
  18. Open Crystal Reports or other SQL reporting tool.
  19. In Avatar Cal-PM SQL table 'SYSTEM.billing_guar_table_tpreq', ensure that fields 'requirement_start_date' and 'requirement_end_date' are present, and reflect values filed via 'Guarantors/Payors' form for 'Requirement Start Date' and 'Requirement End Date' fields (respectively).
Scenario 2: 'File Import' - Verification of 'Guarantors/Payors - Treatment Plan Requirements' Import
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Exclude Services If No Treatment Plan' must be enabled (set to 'P')
  • Avatar Cal-PM 'Guarantors/Payors - Treatment Plan Requirements' import file containing one or more valid import data rows, including values for 'Requirement Start Date' and 'Requirement End Date' segments/fields
  • Updated import file layout document 'Avatar_Cal-PM_File_Import_Record_Layouts.xls' included with update package
  • Crystal Reports or other SQL reporting tool
Steps
  1. Open Avatar Cal-PM 'File Import' form.
  2. Select File Type 'Guarantors/Payors - Treatment Plan Requirements'.
  3. Select 'Upload New File' in 'Action' field and Click 'Process Action' button.
  4. Select Avatar Cal-PM 'Guarantors/Payors - Treatment Plan Requirements' import file and click 'Open' button.
  5. Select 'Compile/Validate File' in 'Action' field.
  6. Select loaded import file and click 'Process Action' button.
  7. Ensure that 'Compile/Validate File' action completes, and message 'Compiled' or '(File Name) contains one or more errors. These errors can be reviewed using 'Print Errors' action' is displayed.
  8. Click 'OK' button.
  9. Select 'Print Errors' in 'Action' field if errors encountered in compile; Select compiled import file with errors and click 'Process Action' button.
  10. In 'Guarantors/Payors - Treatment Plan Requirements' File Import Error Report, ensure that all invalid/errored import row(s) are included in report with segment/value reference and error message detail.
  11. Examples of 'Guarantors/Payors - Treatment Plan Requirements' File Import errors related to 'Requirement Start Date' and 'Requirement End Date' segments/fields:
  12. 'Invalid date or format'
  13. 'End Date is prior to Start Date'
  14. 'Missing start date'
  15. 'Missing end date'
  16. Select 'Print File' in 'Action' field to view successfully compiled import data; Select compiled import file and click 'Process Action' button.
  17. In 'Guarantors/Payors - Treatment Plan Requirements' File Import Report, ensure that all valid import row(s) are included in report with segment/value details, including 'Requirement Start Date' and 'Requirement End Date' segments/fields.
  18. Select 'Post File' in 'Action' field to post successfully compiled import data; Select compiled import file and click 'Process Action' button.
  19. Ensure that 'Compile/Validate File' action completes, and message 'Posted' and/or 'The selected file contains one or more lines with compilation errors. Only those lines without compilation errors will be posted' is displayed.
  20. Open Avatar Cal-PM 'Guarantors/Payors' form.
  21. Select Edit action in 'Add New or Edit Existing Guarantor' field, and select Guarantor where Treatment Plan Requirement entry was created/updated via File Import filing.
  22. Navigate to 'Treatment Plan Requirements' section of 'Guarantors/Payors' form.
  23. Select Treatment Plan Requirement entry filed via File Import in 'Select Treatment Plan Requirements' field.
  24. Ensure that values for 'Requirement Start Date' and 'Requirement End Date' fields filed via File Import are present in form (as well as values for all other fields in 'Treatment Plan Requirements' section of form according to File Import data).
  25. Open Crystal Reports or other SQL reporting tool.
  26. In Avatar Cal-PM SQL table 'SYSTEM.file_import_guar_tp_req', ensure that fields 'requirement_start_date' and 'requirement_end_date' are present, and reflect values filed via File Import for 'Requirement Start Date' and 'Requirement End Date' fields (respectively).
Scenario 3: 'Electronic Billing' - Verification of 'Treatment Plan Requirement' Restrictions
Specific Setup:
  • Avatar Cal-PM Registry Setting 'Exclude Services If No Treatment Plan' must be enabled (set to 'P')
  • One or more Guarantor(s) where values are selected/defined for 'Requirement Start Date' and 'Requirement End Date' fields (via Avatar Cal-PM 'Guarantors/Payors' form, 'Treatment Plan Requirements' section)
  • Avatar CWS Treatment Plan form (including Draft/Final Status field)
  • One or more service(s) eligible for Avatar Cal-PM 837 Professional or 837 Institutional file inclusion under applicable Guarantor(s) (via 'Electronic Billing' form)
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 the 'Billing Form' field.
  4. Select 'Sort File' in the 'Billing Options' field.
  5. Enter/select 837 Professional/837 Institutional file sorting criteria.
  6. Click 'Process' button to sort/generate 837 Professional/837 Institutional file.
  7. Select 'Run Report' in the 'Billing Options' field.
  8. Select 'Print' in the 'Print Or Delete Report' field.
  9. Select 837 Professional/837 Institutional file sorted which includes services(s), and click 'Process' button to display 837 Professional/837 Institutional outbound file report.
  10. In Avatar Cal-PM 837 Professional/837 Institutional format outbound electronic billing file report:
  11. In case where 'Final' status 'Treatment Plan' record does not exist applicable to client/service(s) to be included in 837 file and no 'Requirement Start Date'/'Requirement End Date' values are defined for applicable Guarantor/Treatment Plan Requirements - Ensure that error is reported/included for service(s) in 'Required Data Missing: Patient Service Data' section of report (and service is not included in 837 file claim/service information).
  12. Error Message Example:
  13. 'No Final Treatment Plan In Effect For Service: [Service Code] - Service Date: [Service Date]'
  14. In case where 'Final' status 'Treatment Plan' record does not exist applicable to client/service(s) to be included in 837 file and service date is within 'Requirement Start Date'/'Requirement End Date' values defined for applicable Guarantor/Treatment Plan Requirements - Ensure that error is reported/included for service(s) in 'Required Data Missing: Patient Service Data' section of report (and service is not included in 837 file claim/service information).
  15. Error Message Example:
  16. 'No Final Treatment Plan In Effect For Service: [Service Code] - Service Date: [Service Date]'
  17. In case where 'Final' status 'Treatment Plan' record does not exist applicable to client/service(s) to be included in 837 file and service date is outside of 'Requirement Start Date'/'Requirement End Date' values defined for applicable Guarantor/Treatment Plan Requirements - Ensure that Treatment Plan-related error is not reported/included for service(s) in 'Required Data Missing: Patient Service Data' section of report and service(s) is/are included in 837 file information as expected (subject to all other 837 sorting criteria/requirements).
  18. In case where 'Final' status 'Treatment Plan' record exists applicable to client/service(s) to be included in 837 file (regardless of 'Requirement Start Date'/'Requirement End Date' values defined for applicable Guarantor/Treatment Plan Requirements) - Ensure that Treatment Plan-related error is not reported/included for service(s) in 'Required Data Missing: Patient Service Data' section of report and service(s) is/are included in 837 file information as expected (subject to all other 837 sorting criteria/requirements).
  19. Select 'Create File On Server' in the 'Billing Options' field.
  20. Select 837 Professional/837 Institutional file sorted which includes services(s), and click 'Process' button to create 837 Professional/837 Institutional outbound file on server.

Topics
• Electronic Billing • File Import • Guarantor • NX • Registry Settings • Treatment Plan
Update 69 Summary | Details
Diagnosis - 'SearchDiagnosisCodes' web service
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • SOAPUI - DiagnosisV2 - SearchDiagnosisCode
Scenario 1: Diagnosis - Validate the 'SearchDiagnosisCode' web service
Steps
  1. Access SoapUI for the 'DiagnosisV2' - 'SearchDiagnosisCodes' 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 diagnosis search term in the 'ClinicalSearchTerm' field.
  6. Click [Run].
  7. Validate the 'SearchDiagnosisCodeResult' field contains all related diagnosis codes.
Support is added for other products and modules
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Delete Last Practitioner Termination Date
  • Practitioner Termination
  • CareFabric Monitor
Scenario 1: Delete Last Practitioner Termination Date - Validate form functionality
Specific Setup:
  • A practitioner has been terminated in the 'Practitioner Termination' form (Practitioner A).
Steps
  1. Access the 'Delete Last Practitioner Termination Date' form for "Practitioner A".
  2. Validate the 'Termination Date' field contains the termination date.
  3. Click [Submit].
  4. Validate a message is displayed stating: Are you sure you want to delete termination date ##/##/#### for practitioner "Practitioner A".
  5. Click [Yes].
  6. Access the 'Practitioner Termination' form for "Practitioner A".
  7. Validate the 'Termination Date' field does not contain a value.
  8. Validate the 'Reason For Termination' field does not contain a value.
  9. Close the form.
Scenario 2: Delete Last Practitioner Termination Date - Validate the 'ProviderUpdated' SDK event
Specific Setup:
  • An active practitioner is defined that has hours for scheduling in the 'Staff Members Hours and Exceptions' form (Practitioner A).
Steps
  1. Access the 'Practitioner Termination' form for "Practitioner A".
  2. Enter the desired date in the 'Termination Date' field.
  3. Populate any other desired fields.
  4. Click [Submit].
  5. Access the 'CareFabric Monitor' form.
  6. Enter the current date in the 'From Date' and 'Through Date' fields.
  7. Search for and select "ProviderUpdated" in the 'Event/Action Search' field.
  8. Click [View Activity Log].
  9. Validate the 'CareFabric Monitor Report' contains a "ProviderUpdated" event triggered from the 'Practitioner Termination' form.
  10. Click [Click To View Record].
  11. Validate the 'isActive' field contains "false".
  12. Close the report and the form.
  13. Access the 'Delete Last Practitioner Termination' form for "Practitioner A".
  14. Validate the 'Termination Date' field contains the termination date.
  15. Click [Submit].
  16. Validate a message is displayed stating: Are you sure you want to delete termination date ##/##/#### for practitioner "Practitioner A".
  17. Click [Yes].
  18. Access the 'CareFabric Monitor' form.
  19. Enter the current date in the 'From Date' and 'Through Date' fields.
  20. Search for and select "ProviderUpdated" in the 'Event/Action Search' field.
  21. Click [View Activity Log].
  22. Validate the 'CareFabric Monitor Report' contains a "ProviderUpdated" event triggered from the 'Delete Last Practitioner Termination' form.
  23. Click [Click To View Record].
  24. Validate the 'isActive' field contains "true".
  25. Close the report and the form.
Scenario 3: Delete Last Practitioner Termination Date - Validate the 'StaffMemberUpdated' SDK event
Specific Setup:
  • An active practitioner is defined in 'Practitioner Enrollment' (Practitioner A).
Steps
  1. Access the 'Practitioner Termination' form for "Practitioner A".
  2. Enter the desired date in the 'Termination Date' field.
  3. Populate any other desired fields.
  4. Click [Submit].
  5. Access the 'CareFabric Monitor' form.
  6. Enter the current date in the 'From Date' and 'Through Date' fields.
  7. Search for and select "StaffMemberUpdated" in the 'Event/Action Search' field.
  8. Click [View Activity Log].
  9. Validate the 'CareFabric Monitor Report' contains a "StaffMemberUpdated" event triggered from the 'Practitioner Termination' form.
  10. Click [Click To View Record].
  11. Validate the 'terminatedDate' field contains the 'Termination Date' filed.
  12. Close the report and the form.
  13. Access the 'Delete Last Practitioner Termination' form for "Practitioner A".
  14. Validate the 'Termination Date' field contains the termination date.
  15. Click [Submit].
  16. Validate a message is displayed stating: Are you sure you want to delete termination date ##/##/#### for practitioner "Practitioner A".
  17. Click [Yes].
  18. Access the 'CareFabric Monitor' form.
  19. Enter the current date in the 'From Date' and 'Through Date' fields.
  20. Search for and select "StaffMemberUpdated" in the 'Event/Action Search' field.
  21. Click [View Activity Log].
  22. Validate the 'CareFabric Monitor Report' contains a "StaffMemberUpdated" event triggered from the 'Delete Last Practitioner Termination' form.
  23. Click [Click To View Record].
  24. Validate the 'terminatedDate' field contains "null".
  25. Close the report and the form.
Scenario 4: Delete Last Practitioner Termination Date - Validate the 'EvvResourceUpdated' SDK event
Specific Setup:
  • Avatar is configured to integrate with Mobile CareGiver+. Please note: This must be done by a Netsmart Representative.
  • One or more program(s) is defined with a value populated in the 'EVV Provider Organization ID' field in the 'Program Maintenance' form.
  • A service code must be defined that has "Yes" selected in the 'Does This Service Require Electronic Visit Verification' field in the 'Service Codes' form and must be assigned to "Program A".
  • An active practitioner is defined in 'Practitioner Enrollment' with the following on file: 'Name', 'Date Of Birth', 'Cellular Telephone', 'Staff EVV ID', 'Email Address', 'Staff EVV Type'.
Steps
  1. Access the 'Practitioner Termination' form for "Practitioner A".
  2. Enter the desired date in the 'Termination Date' field.
  3. Populate any other desired fields.
  4. Click [Submit].
  5. Access the 'CareFabric Monitor' form.
  6. Enter the current date in the 'From Date' and 'Through Date' fields.
  7. Search for and select "EvvResourceUpdated" in the 'Event/Action Search' field.
  8. Click [View Activity Log].
  9. Validate the 'CareFabric Monitor Report' contains a "EvvResourceUpdated" event triggered from the 'Practitioner Termination' form.
  10. Click [Click To View Record].
  11. Validate the 'isActive' field contains "false".
  12. Close the report and the form.
  13. Access the 'Delete Last Practitioner Termination' form for "Practitioner A".
  14. Validate the 'Termination Date' field contains the termination date.
  15. Click [Submit].
  16. Validate a message is displayed stating: Are you sure you want to delete termination date ##/##/#### for practitioner "Practitioner A".
  17. Click [Yes].
  18. Access the 'CareFabric Monitor' form.
  19. Enter the current date in the 'From Date' and 'Through Date' fields.
  20. Search for and select "EvvResourceUpdated" in the 'Event/Action Search' field.
  21. Click [View Activity Log].
  22. Validate the 'CareFabric Monitor Report' contains a "EvvResourceUpdated" event triggered from the 'Delete Last Practitioner Termination' form.
  23. Click [Click To View Record].
  24. Validate the 'isActive' field contains "true".
  25. Close the report and the form.

Topics
• Diagnosis • Web Services • Practitioner
Update 72 Summary | Details
Practitioner Enrollment - The 'Office Location ID, 'Staff EVV ID', 'Staff EVV Type' and 'Email Address' fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • Practitioner Enrollment
Scenario 1: 'ClinicianServicesV2' Web Service - Verification Of 'putClinicianCreation' Filing
Steps
  1. Using the 'ClinicianServicesV2' web service, submit a request using the 'putClinicianCreation' method to create new 'Practitioner Enrollment' record (and optionally Avatar MSO Performing Provider Registration record), including values for the 'StaffEVVID', 'OfficeLocationID', 'EmailAddress' and 'StaffEVVType' fields/segments.
  2. Confirm the 'ClinicianServicesV2' web service responds with confirmation data on successful filing of 'putClinicianCreation' method.
  3. Example: "<Confirmation>Practitioner ID:000017||||First Name:FIRSTNAME||Last Name:LASTNAME||Registration Date:01/01/2022||NPI:123456789</Confirmation>"
  4. Confirm the 'ClinicianServicesV2' web service responds with confirmation message on successful filing of 'putClinicianCreation' method.
  5. Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
  6. Confirm the 'ClinicianServicesV2' web service responds with successful status value on successful filing of 'putClinicianCreation' method.
  7. Example: " <Status>1</Status>"
  8. Access the 'Practitioner Enrollment' form and select the 'Practitioner Enrollment' record filed via web service for view/update.
  9. Confirm new 'Practitioner Enrollment' record is created with values/data submitted via web service including 'Staff EVV ID', 'Office Location ID', 'Email Address' and 'Staff EVV Type' field values (as well as values assigned for Avatar MSO 'Performing Provider' and 'Performing Provider Registration' practitioner association/link fields if enabled).
Scenario 2: 'ClinicianServicesV2' Web Service - Verification Of 'putClinicianUpdate' Filing
Steps
  1. Using the 'ClinicianServicesV2' web service, submit a request using the 'putClinicianUpdate' method to edit/update a 'Practitioner Enrollment' record (and optionally Avatar MSO Performing Provider Registration record if linked), including values for the 'StaffEVVID', 'OfficeLocationID', 'EmailAddress' and 'StaffEVVType' fields/segments.
  2. Confirm the 'ClinicianServicesV2' web service responds with confirmation data on successful filing of 'putClinicianUpdate' method.
  3. Example: "<Confirmation>Practitioner ID:000017||||First Name:FIRSTNAME||Last Name:LASTNAME||Registration Date:01/01/2022||NPI:123456789</Confirmation>"
  4. Confirm the 'ClinicianServicesV2' web service responds with confirmation message on successful filing of 'putClinicianUpdate' method.
  5. Example: "<Message>Clinician Services web service has been filed successfully.</Message>"
  6. Confirm the 'ClinicianServicesV2' web service responds with successful status value on successful filing of 'putClinicianUpdate' method.
  7. Example: " <Status>1</Status>"
  8. Access the 'Practitioner Enrollment' form and select the 'Practitioner Enrollment' record filed via web service for view/update.
  9. Confirm the 'Practitioner Enrollment' record is updated with values/data submitted via web service including 'Staff EVV ID', 'Office Location ID', 'Email Address' and 'Staff EVV Type' field values.
Scenario 3: 'Practitioner Enrollment' - Form Verification
Specific Setup:
  • Crystal Reports or other SQL Reporting Tool.
Steps
  1. Access the 'Practitioner Enrollment' form.
  2. Select any existing practitioner for view/update.
  3. Validate the 'Staff EVV ID', 'Office Location ID', 'Staff EVV Type' and 'Email Address' fields are displayed.
  4. Enter any value in the 'Staff EVV ID' field.
  5. Enter any value in the 'Office Location ID' field.
  6. Enter any value in the 'Staff EVV Type' field.
  7. Enter any value in the 'Email Address' field.
  8. Populate any other required and desired fields.
  9. Click [Submit].
  10. Access the 'Practitioner Enrollment' form.
  11. Select the same practitioner from the previous steps.
  12. Validate the 'Staff EVV ID' field contains the value filed in the previous steps.
  13. Validate the 'Office Location ID' field contains the value filed in the previous steps.
  14. Validate the 'Staff EVV Type' field contains the value filed in the previous steps.
  15. Validate the 'Email Address' field contains the value filed in the previous steps.
  16. Validate any other previously field data is displayed.
  17. Close the form.
  18. Access Crystal Reports or other SQL Reporting Tool.
  19. Create a report using the 'SYSTEM.staff_enrollment_history' SQL table.
  20. Navigate to the row for the practitioner used in the previous steps.
  21. Validate the 'Staff_EVV_ID' field contains the value filed in the previous steps.
  22. Validate the 'Staff_EVV_Type' field contains the value filed in the previous steps.
  23. Validate the 'office_location_ID' field contains the value filed in the previous steps.
  24. Validate the 'email_address' field contains the value filed in the previous steps.
  25. Close the report.
  26. Create a report using the 'SYSTEM.staff_current_demographics' SQL table.
  27. Validate the 'Staff_EVV_ID' field contains the value filed in the previous steps.
  28. Validate the 'Staff_EVV_Type' field contains the value filed in the previous steps.
  29. Validate the 'office_location_ID' field contains the value filed in the previous steps.
  30. Validate the 'email_address' field contains the value filed in the previous steps.
  31. Close the report.
Topics
• Practitioner • Web Services