Skip to main content

Avatar PM 2024 Update 35

  1. Last updated
  2. Save as PDF

Product Requirements and Recommendations

Avatar PM required
RADplus required

Recommended Update Level

Avatar PM 2024 Monthly Release 2024.01.00
RADplus 2024 Monthly Release 2024.01.00

Product Update Description

Avatar PM is enhanced to support FoRSE.

Required Updates

None

Included Updates

17

Details
NEW4 CHANGED0 FIXED0
New (4)
FoRSE Configuration
These parameters will be used to establish connection with FoRSE API using such parameters as Facility ID, Secret Key and new company registration, registration status, and survey URLs as provided by naatp.
Value Added: FoRSE functionality introduced
Topics
• FoRSE
 
FoRSE Configuration
FoRSE Configuration form is where you define the "Force Facilities Configuration" and also check the status of data sent to ensure the transmission was successful in the "FoRSE Monitor" section.
Value Added: FoRSE functionality introduced
Topics
• FoRSE
 
FoRSE Mapping
FoRSE Mapping provides a method to map Avatar data to the various surveys that the system is set up to provide.
Current surveys are:
BAM
BAM-R
BARC-10
FoRSE Admit Survey
FoRSE Demographic Information Form
FoRSE Discharge Survey
FoRSE Outcomes Survey
FoRSE Progress Monitoring Survey
GAD-7
PHQ-9
Treatment Effectiveness Assessment (TEA)
WHOQOL-BREF
Value Added: FoRSE functionality introduced
Topics
• FoRSE
 
FoRSE Functionality - Communication API
The FoRSE communication post-filing hooks determine what data will be sent.
Value Added: FoRSE functionality introduced
Topics
• FoRSE
 
Acceptance Tests
AV-89865 Summary | Details
FoRSE Configuration
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • FoRSE Configuration
  • User Definition
  • Admission
  • FoRSE Mapping
Scenario 1: FoRSE Configuration
Specific Setup:
  • Using the "User Definition" form, give the user access to the "FoRSE Configuration".
  • Refresh the menus.
Steps
  1. Open the "FoRSE Configuration" form.
  2. Enable "FoRSE" functionality.
  3. Set the "Facility ID" to the value assigned by naatp.
  4. Set the "Secret Key" to the value assigned by naatp.
  5. Set the "Register New Company URL" to the URL provided by naatp.
  6. Set the "Registration Status URL" to the URL provided,
  7. Set the "Surveys URL" to the URL provided.
  8. Go to the "FoRSE Facility Configuration" section.
  9. Enter the information for the EHR Facilities added.
  10. Click "Submit" to file the data.
  11. Open the "FoRSE Configuration" form.
  12. Validate the "Enable" radio button is clicked.
  13. Validate "Facility ID" is set to the value assigned by naatp.
  14. Validate the "Secret Key" is set to the value assigned by naatp.
  15. Validate the "Register New Company URL" is set to the URL provided by naatp.
  16. Validate the "Registration Status URL" is set to the URL provided,
  17. Validate "Surveys URL" is set to the URL provided.
  18. Go to the "FoRSE Facility Configuration" section.
  19. Validate the information for the EHR Facilities is correct.
  20. Click "View" in the "FoRSE Status" column of each row added .
  21. Validate the "FoRSE Status indicates "Success".
  22. Click "Discard" to close the form
Scenario 2: FoRSE Mapping
Specific Setup:
  • FoRSE must be configured and enabled.
Steps
  1. Open the "FoRSE Mapping" form.
  2. Add a new mapping.
  3. Select the desired survey to map to in the "Type of Survey" drop down,
  4. Check the "EHR Facility IDs" to submit for this particular survey.
  5. For each Question in the survey, select an Avatar form and field to map to.
  6. Click "View" under the "Field Translation" column.
  7. Left as is, the system will use the default dictionary values and codes.
  8. If you wish to change the default dictionary values, you can use the "Field Translation".
  9. Click "Submit" to file the form.
  10. Open the "FoRSE Mapping" form.
  11. Edit an existing mapping.
  12. Select an existing mapping in the "Mapping" drop down
  13. Validate mapping is enabled.
  14. Validate the "EHR Facility IDs" are the ones selected previously.
  15. Validate the "Field Mapping" is as what was previously entered.
  16. File the "Admission" form either for a new client or an existing client.
  17. Open the "FoRSE Configuration" form.
  18. Go to the "FoRSE Monitor" section.
  19. Set the start and end dates.
  20. Select the client.
  21. Click "Launch Report".
  22. Click "Click To View Record".
  23. Validate payload indicates success.
Scenario 3: FoRSE Surveys
Specific Setup:
  • Validate FoRSE is configured and enabled.
  • Validate the survey is mapped to an Avatar form.
Steps
  1. Open a form that is mapped to a survey.
  2. File the form.
  3. Open the "FoRSE Configuration" form.
  4. Go to the "FoRSE Monitor" section.
  5. Set the start and end dates.
  6. Select the client.
  7. Click "Launch Report".
  8. Click "Click To View Record".
  9. Validate payload indicates a success.
Topics
• FoRSE
AV-89866 Summary | Details
FoRSE Configuration
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • FoRSE Configuration
  • User Definition
  • Admission
  • FoRSE Mapping
Scenario 1: FoRSE Configuration
Specific Setup:
  • Using the "User Definition" form, give the user access to the "FoRSE Configuration".
  • Refresh the menus.
Steps
  1. Open the "FoRSE Configuration" form.
  2. Enable "FoRSE" functionality.
  3. Set the "Facility ID" to the value assigned by naatp.
  4. Set the "Secret Key" to the value assigned by naatp.
  5. Set the "Register New Company URL" to the URL provided by naatp.
  6. Set the "Registration Status URL" to the URL provided,
  7. Set the "Surveys URL" to the URL provided.
  8. Go to the "FoRSE Facility Configuration" section.
  9. Enter the information for the EHR Facilities added.
  10. Click "Submit" to file the data.
  11. Open the "FoRSE Configuration" form.
  12. Validate the "Enable" radio button is clicked.
  13. Validate "Facility ID" is set to the value assigned by naatp.
  14. Validate the "Secret Key" is set to the value assigned by naatp.
  15. Validate the "Register New Company URL" is set to the URL provided by naatp.
  16. Validate the "Registration Status URL" is set to the URL provided,
  17. Validate "Surveys URL" is set to the URL provided.
  18. Go to the "FoRSE Facility Configuration" section.
  19. Validate the information for the EHR Facilities is correct.
  20. Click "View" in the "FoRSE Status" column of each row added .
  21. Validate the "FoRSE Status indicates "Success".
  22. Click "Discard" to close the form
Scenario 2: FoRSE Mapping
Specific Setup:
  • FoRSE must be configured and enabled.
Steps
  1. Open the "FoRSE Mapping" form.
  2. Add a new mapping.
  3. Select the desired survey to map to in the "Type of Survey" drop down,
  4. Check the "EHR Facility IDs" to submit for this particular survey.
  5. For each Question in the survey, select an Avatar form and field to map to.
  6. Click "View" under the "Field Translation" column.
  7. Left as is, the system will use the default dictionary values and codes.
  8. If you wish to change the default dictionary values, you can use the "Field Translation".
  9. Click "Submit" to file the form.
  10. Open the "FoRSE Mapping" form.
  11. Edit an existing mapping.
  12. Select an existing mapping in the "Mapping" drop down
  13. Validate mapping is enabled.
  14. Validate the "EHR Facility IDs" are the ones selected previously.
  15. Validate the "Field Mapping" is as what was previously entered.
  16. File the "Admission" form either for a new client or an existing client.
  17. Open the "FoRSE Configuration" form.
  18. Go to the "FoRSE Monitor" section.
  19. Set the start and end dates.
  20. Select the client.
  21. Click "Launch Report".
  22. Click "Click To View Record".
  23. Validate payload indicates success.
Scenario 3: FoRSE Surveys
Specific Setup:
  • Validate FoRSE is configured and enabled.
  • Validate the survey is mapped to an Avatar form.
Steps
  1. Open a form that is mapped to a survey.
  2. File the form.
  3. Open the "FoRSE Configuration" form.
  4. Go to the "FoRSE Monitor" section.
  5. Set the start and end dates.
  6. Select the client.
  7. Click "Launch Report".
  8. Click "Click To View Record".
  9. Validate payload indicates a success.
Topics
• FoRSE
AV-89867 Summary | Details
FoRSE Mapping
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • FoRSE Configuration
  • User Definition
  • Admission
  • FoRSE Mapping
Scenario 1: FoRSE Configuration
Specific Setup:
  • Using the "User Definition" form, give the user access to the "FoRSE Configuration".
  • Refresh the menus.
Steps
  1. Open the "FoRSE Configuration" form.
  2. Enable "FoRSE" functionality.
  3. Set the "Facility ID" to the value assigned by naatp.
  4. Set the "Secret Key" to the value assigned by naatp.
  5. Set the "Register New Company URL" to the URL provided by naatp.
  6. Set the "Registration Status URL" to the URL provided,
  7. Set the "Surveys URL" to the URL provided.
  8. Go to the "FoRSE Facility Configuration" section.
  9. Enter the information for the EHR Facilities added.
  10. Click "Submit" to file the data.
  11. Open the "FoRSE Configuration" form.
  12. Validate the "Enable" radio button is clicked.
  13. Validate "Facility ID" is set to the value assigned by naatp.
  14. Validate the "Secret Key" is set to the value assigned by naatp.
  15. Validate the "Register New Company URL" is set to the URL provided by naatp.
  16. Validate the "Registration Status URL" is set to the URL provided,
  17. Validate "Surveys URL" is set to the URL provided.
  18. Go to the "FoRSE Facility Configuration" section.
  19. Validate the information for the EHR Facilities is correct.
  20. Click "View" in the "FoRSE Status" column of each row added .
  21. Validate the "FoRSE Status indicates "Success".
  22. Click "Discard" to close the form
Scenario 2: FoRSE Mapping
Specific Setup:
  • FoRSE must be configured and enabled.
Steps
  1. Open the "FoRSE Mapping" form.
  2. Add a new mapping.
  3. Select the desired survey to map to in the "Type of Survey" drop down,
  4. Check the "EHR Facility IDs" to submit for this particular survey.
  5. For each Question in the survey, select an Avatar form and field to map to.
  6. Click "View" under the "Field Translation" column.
  7. Left as is, the system will use the default dictionary values and codes.
  8. If you wish to change the default dictionary values, you can use the "Field Translation".
  9. Click "Submit" to file the form.
  10. Open the "FoRSE Mapping" form.
  11. Edit an existing mapping.
  12. Select an existing mapping in the "Mapping" drop down
  13. Validate mapping is enabled.
  14. Validate the "EHR Facility IDs" are the ones selected previously.
  15. Validate the "Field Mapping" is as what was previously entered.
  16. File the "Admission" form either for a new client or an existing client.
  17. Open the "FoRSE Configuration" form.
  18. Go to the "FoRSE Monitor" section.
  19. Set the start and end dates.
  20. Select the client.
  21. Click "Launch Report".
  22. Click "Click To View Record".
  23. Validate payload indicates success.
Scenario 3: FoRSE Surveys
Specific Setup:
  • Validate FoRSE is configured and enabled.
  • Validate the survey is mapped to an Avatar form.
Steps
  1. Open a form that is mapped to a survey.
  2. File the form.
  3. Open the "FoRSE Configuration" form.
  4. Go to the "FoRSE Monitor" section.
  5. Set the start and end dates.
  6. Select the client.
  7. Click "Launch Report".
  8. Click "Click To View Record".
  9. Validate payload indicates a success.
Topics
• FoRSE
AV-89868 Summary | Details
FoRSE Functionality - Communication API
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
  • FoRSE Configuration
  • User Definition
  • Admission
  • FoRSE Mapping
Scenario 1: FoRSE Configuration
Specific Setup:
  • Using the "User Definition" form, give the user access to the "FoRSE Configuration".
  • Refresh the menus.
Steps
  1. Open the "FoRSE Configuration" form.
  2. Enable "FoRSE" functionality.
  3. Set the "Facility ID" to the value assigned by naatp.
  4. Set the "Secret Key" to the value assigned by naatp.
  5. Set the "Register New Company URL" to the URL provided by naatp.
  6. Set the "Registration Status URL" to the URL provided,
  7. Set the "Surveys URL" to the URL provided.
  8. Go to the "FoRSE Facility Configuration" section.
  9. Enter the information for the EHR Facilities added.
  10. Click "Submit" to file the data.
  11. Open the "FoRSE Configuration" form.
  12. Validate the "Enable" radio button is clicked.
  13. Validate "Facility ID" is set to the value assigned by naatp.
  14. Validate the "Secret Key" is set to the value assigned by naatp.
  15. Validate the "Register New Company URL" is set to the URL provided by naatp.
  16. Validate the "Registration Status URL" is set to the URL provided,
  17. Validate "Surveys URL" is set to the URL provided.
  18. Go to the "FoRSE Facility Configuration" section.
  19. Validate the information for the EHR Facilities is correct.
  20. Click "View" in the "FoRSE Status" column of each row added .
  21. Validate the "FoRSE Status indicates "Success".
  22. Click "Discard" to close the form
Scenario 2: FoRSE Mapping
Specific Setup:
  • FoRSE must be configured and enabled.
Steps
  1. Open the "FoRSE Mapping" form.
  2. Add a new mapping.
  3. Select the desired survey to map to in the "Type of Survey" drop down,
  4. Check the "EHR Facility IDs" to submit for this particular survey.
  5. For each Question in the survey, select an Avatar form and field to map to.
  6. Click "View" under the "Field Translation" column.
  7. Left as is, the system will use the default dictionary values and codes.
  8. If you wish to change the default dictionary values, you can use the "Field Translation".
  9. Click "Submit" to file the form.
  10. Open the "FoRSE Mapping" form.
  11. Edit an existing mapping.
  12. Select an existing mapping in the "Mapping" drop down
  13. Validate mapping is enabled.
  14. Validate the "EHR Facility IDs" are the ones selected previously.
  15. Validate the "Field Mapping" is as what was previously entered.
  16. File the "Admission" form either for a new client or an existing client.
  17. Open the "FoRSE Configuration" form.
  18. Go to the "FoRSE Monitor" section.
  19. Set the start and end dates.
  20. Select the client.
  21. Click "Launch Report".
  22. Click "Click To View Record".
  23. Validate payload indicates success.
Scenario 3: FoRSE Surveys
Specific Setup:
  • Validate FoRSE is configured and enabled.
  • Validate the survey is mapped to an Avatar form.
Steps
  1. Open a form that is mapped to a survey.
  2. File the form.
  3. Open the "FoRSE Configuration" form.
  4. Go to the "FoRSE Monitor" section.
  5. Set the start and end dates.
  6. Select the client.
  7. Click "Launch Report".
  8. Click "Click To View Record".
  9. Validate payload indicates a success.
Topics
• FoRSE
Table Changes
Table Column Change
SYSTEM.FoRSEConfiguration FACILITY added
SYSTEM.FoRSEConfiguration FacilityID added
SYSTEM.FoRSEConfiguration SecretKey added
SYSTEM.FoRSEConfiguration RegisterNewCompanyURL added
SYSTEM.FoRSEConfiguration RegistrationStatusURL added
SYSTEM.FoRSEConfiguration SurveysURL added
SYSTEM.FoRSEConfiguration enabled_code added
SYSTEM.FoRSEConfiguration enabled_value added
SYSTEM.FoRSEConfiguration Timeout added
SYSTEM.FoRSEConfiguration DaysForLogEntires added
SYSTEM.FoRSEConfiguration LogsLastCheckedDate added
SYSTEM.FoRSEConfiguration data_entry_by added
SYSTEM.FoRSEConfiguration data_entry_by_option added
SYSTEM.FoRSEConfiguration data_entry_date added
SYSTEM.FoRSEConfiguration data_entry_offset added
SYSTEM.FoRSEConfiguration data_entry_source added
SYSTEM.FoRSEConfiguration data_entry_time added
SYSTEM.FoRSEConfiguration data_entry_time_j added
SYSTEM.FoRSEConfiguration data_entry_timezone_info_all added
SYSTEM.FoRSEConfiguration data_entry_timezone_short added
SYSTEM.FoRSEConfiguration data_entry_user_id added
SYSTEM.FoRSEConfiguration data_entry_user_name added
SYSTEM.FoRSEConfiguration data_entry_utc added
SYSTEM.FoRSEConfiguration option_desc added
SYSTEM.FoRSEConfiguration option_id added
SYSTEM.FoRSEFacility FACILITY added
SYSTEM.FoRSEFacility EHRFacilityID added
SYSTEM.FoRSEFacility FacilityAddressCity added
SYSTEM.FoRSEFacility FacilityAddressCountry added
SYSTEM.FoRSEFacility FacilityAddressState added
SYSTEM.FoRSEFacility FacilityAddressStreet added
SYSTEM.FoRSEFacility FacilityAddressZip added
SYSTEM.FoRSEFacility FacilityName added
SYSTEM.FoRSEFacility FoRSEFacilityID added
SYSTEM.FoRSEFacility FoRSELastCheckedDate added
SYSTEM.FoRSEFacility FoRSELastCheckedTime added
SYSTEM.FoRSEFacility FoRSEapisecretkey added
SYSTEM.FoRSEFacility FoRSEisactive added
SYSTEM.FoRSEFacility FoRSEistestfacility added
SYSTEM.FoRSEFacility FoRSEstatus added
SYSTEM.FoRSEFacility FoRSEstatusmsg added
SYSTEM.FoRSEFacility PrimaryContactEmail added
SYSTEM.FoRSEFacility PrimaryContactName added
SYSTEM.FoRSEFacility PrimaryContactPhone added
SYSTEM.FoRSEFacility TestFacility added
SYSTEM.FoRSEFacility data_entry_by added
SYSTEM.FoRSEFacility data_entry_by_option added
SYSTEM.FoRSEFacility data_entry_date added
SYSTEM.FoRSEFacility data_entry_offset added
SYSTEM.FoRSEFacility data_entry_source added
SYSTEM.FoRSEFacility data_entry_time added
SYSTEM.FoRSEFacility data_entry_time_j added
SYSTEM.FoRSEFacility data_entry_timezone_info_all added
SYSTEM.FoRSEFacility data_entry_timezone_short added
SYSTEM.FoRSEFacility data_entry_user_id added
SYSTEM.FoRSEFacility data_entry_user_name added
SYSTEM.FoRSEFacility data_entry_utc added
SYSTEM.FoRSEFacility enabled_code added
SYSTEM.FoRSEFacility enabled_value added
SYSTEM.FoRSEFacility option_desc added
SYSTEM.FoRSEFacility option_id added
SYSTEM.FoRSELog FACILITY added
SYSTEM.FoRSELog ActivityDate added
SYSTEM.FoRSELog ActivityTime added
SYSTEM.FoRSELog ActivityTimeJ added
SYSTEM.FoRSELog ActivityType added
SYSTEM.FoRSELog ActivityURL added
SYSTEM.FoRSELog ActivityStatus added
SYSTEM.FoRSELog RequestStream added
SYSTEM.FoRSELog ResponseStream added
SYSTEM.FoRSELog ActivityMessage added
SYSTEM.FoRSELog RequestStreamRep added
SYSTEM.FoRSELog ResponseStreamRep added
SYSTEM.FoRSELog ENTITYID added
SYSTEM.FoRSELog EPISODE_NUMBER added
SYSTEM.FoRSELog JOIN_TO_UNIQUE_ID added
SYSTEM.FoRSELog FoRSEInstrumentIDs added
SYSTEM.FoRSELog FoRSEInstrumentDesc added
SYSTEM.FoRSELog SessionID added
SYSTEM.FoRSELog data_entry_by added
SYSTEM.FoRSELog data_entry_by_option added
SYSTEM.FoRSELog data_entry_date added
SYSTEM.FoRSELog data_entry_offset added
SYSTEM.FoRSELog data_entry_source added
SYSTEM.FoRSELog data_entry_time added
SYSTEM.FoRSELog data_entry_time_j added
SYSTEM.FoRSELog data_entry_timezone_info_all added
SYSTEM.FoRSELog data_entry_timezone_short added
SYSTEM.FoRSELog data_entry_user_id added
SYSTEM.FoRSELog data_entry_user_name added
SYSTEM.FoRSELog data_entry_utc added
SYSTEM.FoRSELog hasError added
SYSTEM.FoRSELog option_desc added
SYSTEM.FoRSELog option_id added
SYSTEM.FoRSEMapping FACILITY added
SYSTEM.FoRSEMapping FoRSEMappingID added
SYSTEM.FoRSEMapping FoRSEInstrumentID added
SYSTEM.FoRSEMapping FoRSEInstrumentDesc added
SYSTEM.FoRSEMapping enabled_code added
SYSTEM.FoRSEMapping enabled_value added
SYSTEM.FoRSEMapping EHRFacilityIDs added
SYSTEM.FoRSEMapping FoRSEQuestionID added
SYSTEM.FoRSEMapping FoRSEQuestionDesc added
SYSTEM.FoRSEMapping care_record_form_product added
SYSTEM.FoRSEMapping care_record_form_id added
SYSTEM.FoRSEMapping care_record_form_desc added
SYSTEM.FoRSEMapping care_record_field_num added
SYSTEM.FoRSEMapping care_record_field_desc added
SYSTEM.FoRSEMapping data_entry_by added
SYSTEM.FoRSEMapping data_entry_by_option added
SYSTEM.FoRSEMapping data_entry_date added
SYSTEM.FoRSEMapping data_entry_offset added
SYSTEM.FoRSEMapping data_entry_source added
SYSTEM.FoRSEMapping data_entry_time added
SYSTEM.FoRSEMapping data_entry_time_j added
SYSTEM.FoRSEMapping data_entry_timezone_info_all added
SYSTEM.FoRSEMapping data_entry_timezone_short added
SYSTEM.FoRSEMapping data_entry_user_id added
SYSTEM.FoRSEMapping data_entry_user_name added
SYSTEM.FoRSEMapping data_entry_utc added
SYSTEM.FoRSEMapping option_desc added
SYSTEM.FoRSEMapping option_id added
SYSTEM.FoRSEFieldTranslation FACILITY added
SYSTEM.FoRSEFieldTranslation JOIN_TO_FORSEMAPPING added
SYSTEM.FoRSEFieldTranslation carerecord_code added
SYSTEM.FoRSEFieldTranslation carerecord_text added
SYSTEM.FoRSEFieldTranslation forse_code added
SYSTEM.FoRSEFieldTranslation forse_text added

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Page type
    Reference
  2. Tags
    1. Avatar PM 2024 Update 35
    2. content:release
    3. FoRSE
    4. llm-no-index
    5. role:sysadmin