Avatar Cal-PM 2022 Quarterly Release 2022.04 Acceptance Tests

Last updated
Save as PDF

Update 6 Summary \| Details Disclosure Management - Site Specific Section Modeling fields Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Site Specific Section Modeling (PM) Disclosure Management Configuration Disclosure Management Scenario 1: Disclosure Management - Validate Site specific fields Specific Setup: Using the "Disclosure Management Configuration" form, set up the system for Disclosure Management. Using "Site Specific Section Modeling" form, add 3 fields of the type SS Disclosure Management Free Text to the Disclosure Management Disclosure section (PATIENT4000 (Disclosure Management) Disclosure). Note: For NX only, on the Disclosure screen, once the items have been disclosed and viewed, you have to click 'Cancel' to go back to the main form to click "Submit" to finalize the process. This will be addressed in a future NX release to mimic the workflow in myAvatar. Steps Open the "Disclosure Management" form. Fill out the Request, Authorization and Disclosure sections. In the "Disclosure" section, populate the site specific section modeling fields. Click "Process" button. Validate the correct items are included in the disclosure packet. Click "Disclose" button. Click the "Printer" icon. Print the disclosure packet. Return to the pre-display. Add another request, authorization, and disclosure. In the disclosure section, validate the site specific section modeling fields are blank after the last record was filed. Populate the site specific section modeling fields. Select "Other" in the "Disclosure Method" field. Set the "Disclosure Method - Specify Other" to "Mail". Click the "Process" button. Click the "Disclose" button. Return to the pre-display. Select a row in the pre-display. Click the "Delete" button. Validate the disclosure record is removed. Select one of the previously filed disclosure records that has a date in the "Disclosure Date" column. Click "Edit". Validate a message displays indicating the disclosure record was previously finalized because it has a disclosure date and can't be edited. It can only be displayed. Validate the Request, Authorization and Disclosure data is retrieved as it was entered, including the fields added via "Site Specific Section Modeling". Remain in the form by returning to the pre-display. Add another disclosure record. Fill out the request, authorization, and disclosure sections. In the disclosure section, Set "Disclosure Method" to "Electronic". Click the "Submit" button. Exit the form. Open the "Disclosure Management" form. In the disclosure record pre-display, select the disclosure record without a "Disclosure Date" that was just filed. Click the "Edit" button. Navigate to the "Disclosure" Section. Fill in the "Disclosure Date" and "Disclosure Time". Populate the site specific section modeling fields. Validate the "Disclosure Method" is set to "Electronic". Click the "Process" button. Click the "Disclose" button. Click the PDF download icon. Browse to the location on the server where you want to store the file. Give the file a name with a .pdf extension. Click the "Save" button. Validate a message pops up stating that once this Disclosure Management record is filed with a Disclosure Date entered it will no longer be available for edit. This record will only be available to view and print. Return to the pre-display. Validate a row was added to the disclosure pre-display. Exit the form. Scenario 2: Disclosure Management - Field Validations Specific Setup: Using the "Disclosure Management Configuration" form, set up the first page image, watermark, and forms to associate to set up Disclosure Management. Steps Open the "Disclosure Management" form. Populate all required and desired fields in the request, authorization, and the disclosure sections. Select "Electronic" in the "Disclosure Method" field. Click the "Process" button. Validate the appropriate items are included in the disclosure packet. Click "Disclose". Click the PDF download icon. Browse to the location to store the file on the server. Provide the file name with a .pdf file extension. Click the "Cancel" button. Click "Submit".	Topics • Site Specific Section Modeling • Disclosure • NX
Update 27 Summary \| Details Outside Provider Cal-OMS Annual Update - Annual Update Date Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Cal-OMS Admission Outside Providers Outside Provider Cal-OMS Admission Outside Provider Cal-OMS Annual Update Dictionary Update Associate User ID With Outside Providers Scenario 1: Outside Provider Cal-OMS Annual Update - Annual update date is more than one year from the admission date - 'Enforce Annual Update Date Rule' registry setting is enabled Specific Setup: Registry Setting: The 'Enable LA County Reporting Requirements' registry setting is set to 'Y'. Dictionary Update: A Cal-OMS Outside Provider must be defined in the Dictionary Update form. This dictionary code has an extended dictionary data element Cal-OMS Type Of Service. Note the dictionary code/values, Extended dictionary codes/values. File – CalOMS File Dictionary – 70701 Outside Provider Dictionary Code - 221001 Dictionary value - desired value Extended Dictionary Data Element - Cal-OMS Type of Service Extended Dictionary Value - desired value Program Maintenance: Create a new Cal-OMS program or identify an existing program to update. The 'Provider ID (CalOMS)' field contains the Dictionary (70701) value defined for the program (221001). The 'Cal-OMS Type of Service' field contains the same value as Dictionary 70701's Extended Dictionary Value for the Outside Provider created. Note the program code/name. Admission: A new client is admitted in the program defined above. Associate User ID With Outside Providers: The user must be granted access to Cal-OMS outside provider. Outside Provider Cal-OMS admission: The 'Outside Provider Cal-OMS admission' is submitted for the client. Please note the admission date is same as the admission date of the client. Steps Open the 'Outside Provider Cal-OMS Annual Update' form. Select desired Cal-OMS outside provider in the 'Provider' field. In the 'Program' field, select the Cal-OMS program. Programs must be associated with the same Cal-OMS Type of Service as the provider (Program Maintenance form, Cal-OMS Type of Service field). In the 'Cal-OMS Type of Service' field, select the Cal-OMS type of service associated with the program. In the Provider's Participant ID field, enter the provider’s participant ID. This number is used to identify the client. In order to access an outside provider Cal-OMS admission, this number must be re-entered exactly. Select 'New' in the 'Submission Type' field. Select the serial number in the 'Select Serial Number' field. Enter the form serial number in the 'Form Serial Number' field. In the Current First Name field, enter the client’s first name if different from the birth name. In the Current Last Name field, enter the client’s last name if different from the birth name. In the Sex field, select the client's sex. In the Social Security Number field, enter the client’s social security number. In the Date Of Birth field, enter the client’s date of birth. In the Admission Date field, enter date of admission. Note the admission date. In the Annual Update Date field, enter the date of the Cal-OMS annual update. Please note the 'Cal-OMS annual update' date is more than one year after admission date. In the Annual Update Number field, enter the annual update number. In the Birth First Name field, enter the client's first name at birth. In the Birth Last Name field, enter the client's last name at birth. In the ZIP Code At Current Residence field, enter the client's ZIP code. In the Place of Birth - County field, select the county from the list. Choose Other if the client was born outside California. In the Place of Birth - State field, select the client's place of birth. In the Driver's License Number field, enter the client’s driver’s license. In the Mother's First Name field, enter the client’s mother’s first name. In the Disability field, select the client disability. In the Consent field, select Yes if the client has given consent to be contacted in the future. Enter/select values for all other fields as desired/as required by form. When finished, click Submit. Verify the form submits successfully. Scenario 2: Outside Provider Cal-OMS Annual Update - Annual update date is more than or equal to 60 days earlier than one year from the admission date Specific Setup: Registry Setting: The 'Enable LA County Reporting Requirements' registry setting is set to 'Y'. Dictionary Update: A Cal-OMS Outside Provider must be defined in the Dictionary Update form. This dictionary code has an extended dictionary data element Cal-OMS Type Of Service. Note the dictionary code/values, Extended dictionary codes/values. File – CalOMS File Dictionary – 70701 Outside Provider Dictionary Code - 221001 Dictionary value - desired value Extended Dictionary Data Element - Cal-OMS Type of Service Extended Dictionary Value - desired value Program Maintenance: Create a new Cal-OMS program or identify an existing program to update. The 'Provider ID (CalOMS)' field contains the Dictionary (70701) value defined for the program (221001). The 'Cal-OMS Type of Service' field contains the same value as Dictionary 70701's Extended Dictionary Value for the Outside Provider created. Note the program code/name. Admission: A new client is admitted in the program defined above. Associate User ID With Outside Providers: The user must be granted access to Cal-OMS outside provider. Outside Provider Cal-OMS admission: The 'Outside Provider Cal-OMS admission' is submitted for the client. Please note the admission date is same as the admission date of the client. Steps Open the 'Outside Provider Cal-OMS Annual Update' form. Select desired Cal-OMS outside provider in the 'Provider' field. In the 'Program' field, select the Cal-OMS program. Programs must be associated with the same Cal-OMS Type of Service as the provider (Program Maintenance form, Cal-OMS Type of Service field). In the 'Cal-OMS Type of Service' field, select the Cal-OMS type of service associated with the program. In the Provider's Participant ID field, enter the provider’s participant ID. This number is used to identify the client. In order to access an outside provider Cal-OMS admission, this number must be re-entered exactly. Select 'New' in the 'Submission Type' field. Select the serial number in the 'Select Serial Number' field. Enter the form serial number in the 'Form Serial Number' field. In the Current First Name field, enter the client’s first name if different from the birth name. In the Current Last Name field, enter the client’s last name if different from the birth name. In the Sex field, select the client's sex. In the Social Security Number field, enter the client’s social security number. In the Date Of Birth field, enter the client’s date of birth. In the Admission Date field, enter date of admission. Note the admission date. In the Annual Update Date field, enter the date of the Cal-OMS annual update. Please note the 'Cal-OMS annual update' date is more than 60 days earlier than one year after admission date. In the Annual Update Number field, enter the annual update number. In the Birth First Name field, enter the client's first name at birth. In the Birth Last Name field, enter the client's last name at birth. In the ZIP Code At Current Residence field, enter the client's ZIP code. In the Place of Birth - County field, select the county from the list. Choose Other if the client was born outside California. In the Place of Birth - State field, select the client's place of birth. In the Driver's License Number field, enter the client’s driver’s license. In the Mother's First Name field, enter the client’s mother’s first name. In the Disability field, select the client disability. In the Consent field, select Yes if the client has given consent to be contacted in the future. Enter/select values for all other fields as desired/as required by form. When finished, click Submit. Verify a 'Annual Update Date: Annual Update Date must be at most 60 days earlier than one year after admission date.' error message. Click [Return to the form]. In the 'Annual Update Date' field, enter the date of the Cal-OMS annual update. Please note the 'Cal-OMS annual update' date is exactly 60 days earlier than one year after admission date. Click [Submit]. Verify the form submits successfully.	Topics • Cal-OMS • NX • Outside Provider Cal-OMS Annual Update
Update 36 Summary \| Details Avatar Cal-PM Cal-OMS Web Services Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Cal-OMS Admission Web Service Cal-OMS Annual Update Web Service Cal-OMS Discharge Web Service Scenario 1: Cal-OMS Admission Web Service - Verification of Web Service Filing Specific Setup: Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' must be enabled (set to 'YC') Avatar Cal-PM Registry Setting 'Enable Non LA County Requirements' must be enabled (set to 'Y') Application utilizing the Avatar Cal-PM 'Cal-OMS Admission' web service (including Netsmart ProviderConnect) One or more client(s) with episodes eligible for 'Cal-OMS Admission' record filing Crystal Reports or other SQL reporting tool Steps Using the 'Cal-OMS Admission' web service (and/or 'Cal-OMS Admission V2' web service), submit request to 'FileCalOMSAdmission' method to create or update Cal-OMS Admission record. Confirm 'Cal-OMS Admission' web service responds with confirmation data/ID on successful filing of 'FileCalOMSAdmission' method. Example:"<Confirmation>ClientID:111\|\|EP:1\|\|UniqueID:OMA.001</Confirmation>" Confirm 'Cal-OMS Admission' web service responds with confirmation message on successful filing of 'FileCalOMSAdmission' method. Example:"<Message>Cal-OMS Admission web service has been filed successfully.</Message>" Confirm 'Cal-OMS Admission' web service responds with successful status value on successful filing of 'FileCalOMSAdmission' method. Example:"<Status>1</Status>" Open Avatar Cal-PM 'Cal-OMS Admission' form and select client/episode/Cal-OMS Admission record filed via web service for view/update. Confirm Cal-OMS Admission record is created/updated in Avatar Cal-PM, with values/data submitted via web service, including the following fields: 'Record To Be Submitted' 'Ethnicity' 'What is your Principal Source of Referral?' 'Primary Drug Route of Administration' 'Secondary Drug Route of Administration' 'Which of the following medication is prescribed as part of treatment?' 'Current Living Arrangements' 'Race 1' 'Race 2' 'Race 3' 'Race 4' 'Race 5' Open Crystal Reports or other SQL reporting tool. In Avatar Cal-PM SQL table 'SYSTEM.cal_oms_admission', ensure data values are filed/present for all fields as filed via web service, including LA-Specific field values noted above. Scenario 2: Cal-OMS Annual Update Web Service - Verification of Web Service Filing Specific Setup: Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' must be enabled (set to 'YC') Avatar Cal-PM Registry Setting 'Enable Non LA County Requirements' must be enabled (set to 'Y') Application utilizing the Avatar Cal-PM 'Cal-OMS Annual Update' web service (including Netsmart ProviderConnect) One or more client(s) with episodes eligible for 'Cal-OMS Annual Update' record filing Crystal Reports or other SQL reporting tool Steps Using the 'Cal-OMS Annual Update' web service (and/or 'Cal-OMS Annual Update V2' web service), submit request to 'FileCalOMSAnnualUpdate' method to create or update Cal-OMS Annual Update record. Confirm 'Cal-OMS Annual Update' web service responds with confirmation data/ID on successful filing of 'FileCalOMSAnnualUpdate' method. Example:"<Confirmation>ClientID:111\|\|EP:1\|\|UniqueID:OMU.001</Confirmation>" Confirm 'Cal-OMS Annual Update' web service responds with confirmation message on successful filing of 'FileCalOMSAnnualUpdate' method. Example:"<Message>Cal-OMS Annual Update web service has been filed successfully.</Message>" Confirm 'Cal-OMS Annual Update' web service responds with successful status value on successful filing of 'FileCalOMSAnnualUpdate' method. Example:"<Status>1</Status>" Open Avatar Cal-PM 'Cal-OMS Annual Update' form and select client/episode/Cal-OMS Annual Update record filed via web service for view/update. Confirm Cal-OMS Annual Update record is created/updated in Avatar Cal-PM, with values/data submitted via web service, including the following fields: 'Primary Drug Route of Administration' 'Secondary Drug Route of Administration' 'Current Living Arrangements' Open Crystal Reports or other SQL reporting tool. In Avatar Cal-PM SQL table 'SYSTEM.cal_oms_annual_update', ensure data values are filed/present for all fields as filed via web service, including LA-Specific field values noted above. Scenario 3: Cal-OMS Discharge Web Service - Verification of Web Service Filing Specific Setup: Avatar Cal-PM Registry Setting 'Enable LA County Reporting Requirements' must be enabled (set to 'YC') Avatar Cal-PM Registry Setting 'Enable Non LA County Requirements' must be enabled (set to 'Y') Application utilizing the Avatar Cal-PM 'Cal-OMS Discharge' web service (including Netsmart ProviderConnect) One or more client(s) with episodes eligible for 'Cal-OMS Discharge' record filing Crystal Reports or other SQL reporting tool Steps Using the 'Cal-OMS Discharge' web service (and/or 'Cal-OMS Discharge V2' web service), submit request to 'FileCalOMSDischarge' (or 'CalOMSAdminDischarge'/'CalOMSYouthDetoxDischarge') method to create or update Cal-OMS Discharge record. Confirm 'Cal-OMS Discharge' web service responds with confirmation data/ID on successful filing of 'FileCalOMSDischarge' (or 'CalOMSAdminDischarge'/'CalOMSYouthDetoxDischarge') method. Example:"<Confirmation>ClientID:111\|\|EP:1\|\|UniqueID:OMD.001</Confirmation>" Confirm 'Cal-OMS Discharge' web service responds with confirmation message on successful filing of 'FileCalOMSDischarge' (or 'CalOMSAdminDischarge'/'CalOMSYouthDetoxDischarge') method. Example:"<Message>Cal-OMS Discharge web service has been filed successfully.</Message>" Confirm 'Cal-OMS Discharge' web service responds with successful status value on successful filing of 'FileCalOMSDischarge' (or 'CalOMSAdminDischarge'/'CalOMSYouthDetoxDischarge') method. Example:"<Status>1</Status>" Open Avatar Cal-PM 'Cal-OMS Discharge' (or 'Cal-OMS Administrative Discharge'/'Cal-OMS Youth/Detox Discharge') form and select client/episode/Cal-OMS Discharge record filed via web service for view/update. Confirm Cal-OMS Discharge record is created/updated in Avatar Cal-PM, with values/data submitted via web service, including the following fields: 'Record To Be Submitted' 'Primary Drug Route of Administration' 'Secondary Drug Route of Administration' 'Current Living Arrangements' 'Discharge Status' Open Crystal Reports or other SQL reporting tool. In Avatar Cal-PM SQL table 'SYSTEM.cal_oms_discharge', ensure data values are filed/present for all fields as filed via web service, including LA-Specific field values noted above.	Topics • Web Services • Cal-OMS
Update 56 Summary \| Details 837 Professional Rendering Provider (2310B/2420A) Information Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: File Import File Import - Compile/Post Report Practitioner Numbers By Guarantor and Program Practitioner Enrollment Electronic Billing Scenario 1: 'File Import' - Verification of 'Guarantor/Program Billing Defaults Template' Import (Avatar Cal-PM) Specific Setup: Avatar Cal-PM 'Guarantor/Program Billing Defaults' Import File containing one or more valid import rows for 837 Professional information Crystal Reports or other SQL reporting tool Steps Open Avatar Cal-PM 'File Import' form. Select File Type 'Guarantor/Program Billing Defaults'. Select 'Upload New File' in 'Action' field and Click 'Process Action' button. Select Avatar Cal-PM 'Guarantor/Program Billing Defaults' import file including value for one or more of the following 837 Professional fields/segments and click 'Open' button: 'Rendering Provider Entity Type Qualifier (2310B/2420A-NM1-02)' field/segment 127 'Rendering Provider Last Or Organization Name (2310B/2420A-NM1-03)' field/segment 128 'Rendering Provider First Name (2310B/2420A-NM1-04)' field/segment 129 'Rendering Provider Middle Name (2310B/2420A-NM1-05)' field/segment 130 'Rendering Provider Name Suffix (2310B/2420A-NM1-07)' field/segment 131 'Rendering Provider Identification Code Qualifier (2310B/2420A-NM1-08)' field/segment 132 'Rendering Provider Identification Code (2310B/2420A-NM1-09)' field/segment 133 'Rendering Provider Taxonomy Code (2310B/2420A-PRV-03)' field/segment 134 'Rendering Provider Reference Identification Qualifier (2310B/2420A-REF-01)' field/segment 135 'Rendering Provider Reference Identification (2310B/2420A-REF-01)' field/segment 136 'Rendering Provider Reference Identification Qualifier-2 (2310B/2420A-REF-01)' field/segment 137 'Rendering Provider Identification Code-2 (2310B/2420A-REF-02)' field/segment 138 'Specify How Rendering Provider Information Should Be Populated' field/segment 139 Select 'Compile/Validate File' in 'Action' field. Select loaded 'Guarantor/Program Billing Defaults' import file and click 'Process Action' button. 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. Click 'OK' button. Select 'Print File' in 'Action' field to view successfully compiled import data; Select compiled import file and click 'Process Action' button. In 'Guarantor/Program Billing Defaults' File Import Report, ensure that all valid import row(s) are included in report with segment/value details. Select 'Post File' in 'Action' field to post successfully compiled import data; Select compiled import file and click 'Process Action' button. 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. Open Avatar Cal-PM 'Guarantor/Program Billing Defaults' form. Select 'Edit Template' in 'Action' field and select imported Guarantor/Program Billing Defaults template for review/edit. Navigate to '837 Professional' section of form. Ensure that imported values for 837 Professional Rendering Provider (2310B/2420A) fields noted above are present for selected template. Open Crystal Reports or other SQL reporting tool. In Avatar Cal-PM SQL table 'SYSTEM.file_import_gpbd_p837', ensure that new row is filed in table for each successfully compiled/posted import row, including values for following fields: 'rendering_entity_code'/'rendering_entity_value' 'rendering_first_name' 'rendering_last_org_name' 'rendering_middle_name' 'rendering_suffix' 'rendering_id_qual_code'/'rendering_id_qual_value' 'rendering_id' 'rendering_taxonomy' 'rendering_ref_qual_code'/'rendering_ref_qual_value' 'rendering_ref_id' 'rendering_ref_qual2_code'/'rendering_ref_qual2_value' 'rendering_ref_id2' 'use_rnd_if_notfound_code'/'use_rnd_if_notfound_value' For Avatar Cal-PM 'Guarantor/Program Billing Defaults - 837 Professional' format/layout, please refer to 'Avatar_Cal-PM_File_Import_Record_Layouts.xls' document included with update. Scenario 2: 'Guarantor/Program Billing Defaults' - Verification of Rendering Provider (2310B/2420A) Fields Specific Setup: Crystal Reports or other SQL reporting tool Steps Open Avatar Cal-PM 'Guarantor/Program Billing Defaults' form. Select 'Add Template' in 'Action field (or 'Edit Template' and select existing Guarantor/Program Billing Defaults template for review/edit). Navigate to '837 Professional' section of form. Ensure the following fields related to 837 Professional Rendering Provider (2310B/2420A) information are present in 'Guarantor/Program Billing Defaults' form: 'Rendering Provider Entity Type Qualifier (2310B/2420A-NM1-02)' 'Rendering Provider Last Or Organization Name (2310B/2420A-NM1-03)' 'Rendering Provider First Name (2310B/2420A-NM1-04)' 'Rendering Provider Middle Name (2310B/2420A-NM1-05)' 'Rendering Provider Name Suffix (2310B/2420A-NM1-07)' 'Rendering Provider Identification Code Qualifier (2310B/2420A-NM1-08)' 'Rendering Provider Identification Code (2310B/2420A-NM1-09)' 'Rendering Provider Taxonomy Code (2310B/2420A-PRV-03)' 'Rendering Provider Reference Identification Qualifier (2310B/2420A-REF-01)' 'Rendering Provider Reference Identification (2310B/2420A-REF-01)' 'Rendering Provider Reference Identification Qualifier-2 (2310B/2420A-REF-01)' 'Rendering Provider Identification Code-2 (2310B/2420A-REF-02)' 'Specify How Rendering Provider Information Should Be Populated' Enter/select values for fields noted above (and any other fields/sections as desired). Click 'Submit' button to file Guarantor/Program Billing Defaults template. Select 'Edit Template' in 'Action field and select previously filed Guarantor/Program Billing Defaults template for review/edit. Navigate to '837 Professional' section of form. Ensure that previously entered/filed values for 837 Professional Rendering Provider (2310B/2420A) fields noted above are present for selected template. Open Crystal Reports or other SQL reporting tool. In Avatar Cal-PM SQL table 'SYSTEM.table_837_p_facility_prov_num', ensure that Guarantor/Program Billing Defaults template entries/records are present, including values for the following fields: 'rendering_entity_code'/'rendering_entity_value' 'rendering_first_name' 'rendering_last_org_name' 'rendering_middle_name' 'rendering_suffix' 'rendering_id_qual_code'/'rendering_id_qual_value' 'rendering_id' 'rendering_taxonomy' 'rendering_ref_qual_code'/'rendering_ref_qual_value' 'rendering_ref_id' 'rendering_ref_qual2_code'/'rendering_ref_qual2_value' 'rendering_ref_id2' 'use_rnd_if_notfound_code'/'use_rnd_if_notfound_value' Scenario 3: 'Electronic Billing' - Verification of Rendering Provider (2310B/2420A) Information Specific Setup: Avatar Cal-PM Registry Setting 'Rendering Provider Name (Loop 2310B)' must be enabled 'Rendering Provider' must be selected in 'Select Type Of Information To Include In Rendering Provider Name (2310B)' field for applicable 'Guarantor/Program Billing Defaults' template One or more service(s) eligible for Avatar Cal-PM 837 Professional file inclusion (via 'Electronic Billing' form) Steps Open Avatar Cal-PM 'Electronic Billing' form. Note - Acceptance testing may also be confirmed via Avatar Cal-PM 'Quick Billing' form/functionality. Select '837 Professional' in the 'Billing Form' field. Select 'Sort File' in the 'Billing Options' field. Enter/select 837 Professional file sorting criteria. Click 'Process' button to sort/generate 837 Professional file. Select 'Dump File' in the 'Billing Options' field (or select 'Create File On Server' to review output file directly). Select 'Print' in the 'Print Or Delete Report' field. Select 837 Professional file sorted which includes services and click 'Process' button to display 837 Professional outbound file data. In Avatar PM 837 Professional format outbound electronic billing file data - ensure that 2310B Rendering Provider Name loop/segment values (and 2420A Rendering Provider Name if included) reflect information from service practitioner or 'Guarantor/Program Billing Defaults' template values according to 'Specify How Rendering Provider Information Should Be Populated' field as follows: If 'Do Not Use Information From The Guarantor/Program Level' is selected (or if no value is selected): 2310B/2420A Rendering Provider Name loop/segments for all claims/services will be populated with information from service practitioner reporting values defined (via Avatar Cal-PM 'Practitioner Numbers By Guarantor and Program' or 'Practitioner Enrollment' forms) If practitioner is not defined for service or if service practitioner reporting values are not defined, 2310B/2420A Rendering Provider Name information will not be included If 'Always Use Information From The Guarantor/Program Level For Both Name And Identification' is selected: 2310B/2420A Rendering Provider Name loop/segments for all claims/services will be populated with information from 'Rendering Provider...' fields in applicable Avatar Cal-PM 'Guarantor/Program Billing Defaults' form/template If 'Rendering Provider...' field values in applicable Avatar Cal-PM 'Guarantor/Program Billing Defaults' form/template are not defined, 2310B/2420A Rendering Provider Name information will not be included If 'Use Information From The Guarantor/Program Level For Both Name And Identification If No Practitioner Found' is selected: 2310B/2420A Rendering Provider Name loop/segments will be populated with information from service practitioner reporting values defined where practitioner is defined for service; 2310B/2420A Rendering Provider Name loop/segments will be populated with information from 'Rendering Provider...' fields in applicable Avatar Cal-PM 'Guarantor/Program Billing Defaults' form/template where practitioner is not defined for service If practitioner is defined for service but service practitioner reporting values are not defined, 2310B/2420A Rendering Provider Name information will not be included If practitioner is not defined for service and 'Rendering Provider...' field values in applicable Avatar Cal-PM 'Guarantor/Program Billing Defaults' form/template are not defined, 2310B/2420A Rendering Provider Name information will not be included If 'Use Information From The Guarantor/Program Level For Identification Only But Just When A Practitioner Is Found Who Lacks Identification Information' is selected: 2310B/2420A Rendering Provider Name loop/segments will be populated with identification information (2310B/2420A NM1-08/09, 2310B/2420A PRV, 2310B/2420A REF) from service practitioner reporting values if defined; 2310B/2420A Rendering Provider Name loop/segments will be populated with identification information (2310B/2420A NM1-08/09, 2310B/2420A PRV, 2310B/2420A REF) from 'Rendering Provider...' fields in applicable Avatar Cal-PM 'Guarantor/Program Billing Defaults' form/template where practitioner is defined for service but service practitioner reporting values are not defined If practitioner is defined for service but service practitioner reporting values are not defined and 'Rendering Provider...' field values in applicable Avatar Cal-PM 'Guarantor/Program Billing Defaults' form/template are not defined, 2310B/2420A Rendering Provider Name information will not be included If practitioner is not defined for service, 2310B/2420A Rendering Provider Name information will not be included In Avatar PM 837 Professional format outbound electronic billing file data - ensure that 2310B Rendering Provider Individual or Organizational Name (NM) values (and 2420A Rendering Provider Name if included) reflect information from service practitioner reporting values defined (via Avatar Cal-PM 'Practitioner Numbers By Guarantor and Program' or 'Practitioner Enrollment' forms) or from the following 'Guarantor/Program Billing Defaults' template fields where applicable: 'Rendering Provider Entity Type Qualifier (2310B/2420A-NM1-02)' 'Rendering Provider Last Or Organization Name (2310B/2420A-NM1-03)' 'Rendering Provider First Name (2310B/2420A-NM1-04)' 'Rendering Provider Middle Name (2310B/2420A-NM1-05)' 'Rendering Provider Name Suffix (2310B/2420A-NM1-07)' 'Rendering Provider Identification Code Qualifier (2310B/2420A-NM1-08)' 'Rendering Provider Identification Code (2310B/2420A-NM1-09)' Examples: NM1821RENDERINGLASTNAMERENDERINGFIRSTNAME***XX1245319599~ NM1821RENDERINGLASTNAMERENDERINGFIRSTNAMERENDERMIDDLESR~ NM1822RENDERINGORGNAME****XX1245319599~ NM1822RENDERINGORGNAME~ In Avatar PM 837 Professional format outbound electronic billing file data - ensure that 2310B Rendering Provider Specialty Information/Taxonomy Code (PRV) value reflects information from service practitioner reporting values defined (via Avatar Cal-PM 'Practitioner Numbers By Guarantor and Program' or 'Practitioner Enrollment' forms)* or from the following 'Guarantor/Program Billing Defaults' template field where applicable: 'Rendering Provider Taxonomy Code (2310B/2420A-PRV-03)' Example: PRVPEPXC1223G0001X~ In Avatar PM 837 Professional format outbound electronic billing file data - ensure that 2310B Rendering Provider Secondary Identification (REF) values reflect information from service practitioner reporting values defined (via Avatar Cal-PM 'Practitioner Numbers By Guarantor and Program' or 'Practitioner Enrollment' forms)* or from the following 'Guarantor/Program Billing Defaults' template fields where applicable: 'Rendering Provider Reference Identification Qualifier (2310B/2420A-REF-01)' 'Rendering Provider Reference Identification (2310B/2420A-REF-01)' 'Rendering Provider Reference Identification Qualifier-2 (2310B/2420A-REF-01)' 'Rendering Provider Identification Code-2 (2310B/2420A-REF-02)' Example: REF1GX99999~ Note - If 'Health Care Financing Administration National Provider Identifier' (NPI) is selected/included in Rendering Provider Identification Code Qualifier/Code (2310 NM1-08/NM1-09), 2310B-REF/2420A-REF loops/segments will not be included in 837 Professional claim In Avatar PM 837 Professional format outbound electronic billing file data - ensure that 2420A Rendering Provider Individual or Organizational Name (NM), 2420A Rendering Provider Specialty Information/Taxonomy Code (PRV) and 2420A Rendering Provider Secondary Identification (REF) loop/segments reflect information from service practitioner or 'Guarantor/Program Billing Defaults' template values as configured/detailed above where 2420A Rendering Provider Name Information is included in 837 Professional claims. Note - 2420A Rendering Provider Name loop/segments may be excluded from 837 Professional claims in case where 'If The Loop/Segment Information At The Service Level Is The Same As The Loop/Segment Information At The Claim Level (e.g. Service Facility Location Loop), Do You Want The Loop/Segment At The Service Level To Be Skipped?' is set to 'Yes' for applicable 'Guarantor/Program Billing Defaults' template Note - If 'Health Care Financing Administration National Provider Identifier' (NPI) is selected/included in Rendering Provider Identification Code Qualifier/Code (2420A NM1-08/NM1-09), 2420A-REF loops/segments will not be included in 837 Professional claim	Topics • Guarantor/Program Billing Defaults • File Import • Electronic Billing • NX
Update 59 Summary \| Details 'Electronic Billing' - 837 Institutional 2300-DTP Statement Dates Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Electronic Billing Scenario 1: 'Electronic Billing' - Verification of 837 Institutional 2300-DTP Claim Statement Date Information Specific Setup: Avatar Cal-PM Registry Setting 'Claim Statement Dates Format (RD8)' may optionally be enabled One or more service(s) eligible for Avatar Cal-PM 837 Institutional file inclusion (via 'Electronic Billing' form) Steps Open Avatar Cal-PM 'Electronic Billing' form. Note - Acceptance testing may also be confirmed via Avatar Cal-PM 'Quick Billing' form/functionality. Select '837 Institutional' in the 'Billing Form' field. Select 'Sort File' in the 'Billing Options' field. Enter/select 837 Institutional file sorting criteria. Click 'Process' button to sort/generate 837 Institutional file. Select 'Dump File' in the 'Billing Options' field (or select 'Create File On Server' to review output file directly). Select 'Print' in the 'Print Or Delete Report' field. Select 837 Institutional file sorted which includes services (for 'Inpatient' or 'Outpatient' Billing Type), and click 'Process' button to display 837 Institutional outbound file data. In Avatar PM 837 Institutional format outbound electronic billing file data, ensure that 2300-DTP-03 Claim Statement Dates loop/segment reflects earliest/latest service date(s) of all service(s) included in claim. Examples: DTP434RD820221001-20221004~ DTP434D820221001~ In Avatar PM 837 Institutional format outbound electronic billing file data - in case where 'Claim Statement Dates Format (RD8)' Registry Setting is enabled and field 'Express Claim Statement Dates In RD8 Format' is set to 'Yes' for applicable 'Guarantor/Program Billing Defaults' template, ensure that 2300-DTP-03 Claim Statement Dates loop/segment reflects earliest/latest service date(s) of all service(s) included in claim (expressed in 'RD8' format even if single date of service). Example: DTP434RD8*20221002-20221002~	Topics • Electronic Billing
Update 62 Summary \| Details File Import - Client Charge Input Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Site Specific Section Modeling (PM) File Import Scenario 1: File Import - Client Charge Input - 'SS Treatment ICD-10 Code' and 'SS Treatment Integer' fields. Specific Setup: Site Specific Section Modeling has been used to add the following fields, at a minimum, to the ‘Client Charge Input’ and ‘Edit Service Information’ forms. Use the ‘Product Custom Logic Definition’ field to assign the values for 'SS Treatment Integer 1’ - 'SS Treatment Integer 9’. 'SS Treatment Integer 1’ - Use As First Field To Calculate Duration. 'SS Treatment Integer 2’ - Use As Second Field To Calculate Duration. 'SS Treatment Integer 3’ - Use As Third Field To Calculate Duration. 'SS Treatment Integer 4’ - Use As First Field To Calculate Co-Practitioner Duration. 'SS Treatment Integer 5’ - Use As Second Field To Calculate Co-Practitioner Duration. 'SS Treatment Integer 6’ - Use As Second Field To Calculate Co-Practitioner Duration. 'SS Treatment Integer 7’ - Use As First Field To Calculate Co-Practitioner 2 Duration. 'SS Treatment Integer 8’ - Use As Second Field To Calculate Co-Practitioner 2 Duration. 'SS Treatment Integer 9’ - Use As Third Field To Calculate Co-Practitioner 2. 'SS Treatment Integer 10’. 'SS Treatment ICD-10 Code 1’. 'SS Treatment ICD-10 Code 2’. 'SS Treatment ICD-10 Code 3’. 'SS Treatment ICD-10 Code 4’. 'SS Treatment ICD-10 Code 5’. File Import – Client Charge Input: A test file has been created which includes the fields above and all required fields. Note the information in the file. The update zip file contains the ‘Avatar_Cal-PM_File_Import_Record_Layouts’ spreadsheet for guidance. Steps Open ‘File Import’. Select ‘Client Charge Input’ in ‘File Type’. Validate that ‘Upload New File’ is selected in ‘Action’. Click [Process Action] and select the file from setup. Click [Open]. Select ‘Compile/Validate File’ in ‘Action’. Select the file from setup. Click [Process Action]. Click [OK] on the compile message. Select ‘Post’ in ‘Action’. Select the file from setup. Click [Process Action]. Click [OK] on the posted message. Close the form. Open ‘Edit Service Information’. Enter the ‘Client ID’ and select the client. Click [Select Service(s) To Edit]. Select the desired service in the ‘Select Services(s) To Edit’ checklist. Click [OK]. Validate that the ‘Duration (Minutes)’, ‘Co-Practitioner Duration (Minutes)’, and ‘Second Co Staff Duration (Minutes)’ fields contain the sum of the three fields for each practitioner’s duration. Also, validate that the other service information matches the information in the imported file. Close the form. If desired, open ‘Client Ledger’. Select the ‘Client ID’ from the import file. Select ‘All Episodes’ in ‘Claim/Episode/All Episodes’. Select the desired ‘From Date’. Select the desired ‘To Date’. Select ‘Simple’ in ‘Ledger Type’. Click [Process]. Validate that the report contains the service information in the import file. Close the report. Close the form.	Topics • Client Charge Input • Site Specific Section Modeling
Update 63 Summary \| Details Reports - 'Bed Availability Report' and 'Official Census Report' Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Bed Availability Report Official Census Report Scenario 1: Bed Availability Report - Validating bed availability after 'Bed Assignment' Specific Setup: Inpatient client assigned to a room and bed (Client A). Steps Select "Client A" and access the 'Bed Assignment' form. Assign a 'Unit', 'Room' and 'Date/Time of Bed Assignment'. Click [Submit]. Access the 'Bed Availability Report' form. Select "Individual" in the 'For Individual Unit Or All' field. Select "Room/Bed" in the 'Sort By Room/Bed Or Alpha' field. Select the unit for "Client A" in the 'For Unit' field. Click [Process]. Validate the 'Bed Availability Report' is displayed as expected. Validate the 'Client Name' field contains "Client A" for the unit/room selected in the previous steps. Click [Dismiss] and close the form. Scenario 2: Validate the 'Official Census Report' Steps Access the 'Official Census Report' form. Enter the desired date in the 'Date' field. Select the desired value in the 'Treatment Setting' field. Click [Process]. Validate the 'Official Census Report' is displayed as expected. Click [Dismiss] and close the form.	Topics • Bed Assignment • Bed Availability Report • Official Census Report
Update 65 Summary \| Details Personal Pronouns may be included on client demographic forms and in client headers. Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Client Lookup/Header Configuration Manager Update Client Data Progress Notes (Group and Individual) Pre Admit Pre Admit Discharge Call Intake Entity Information Display Discharge Admission Web Service Client Search SQL Query/Reporting Scenario 1: Client Lookup/Header Configuration Manager - Client Header Specific Setup: RADplus 2022 Update 109 is required for full functionality. Registry Setting "Avatar PM->Client Information->Client Demographics->->->Client Demographics - Additional Fields" must include a value of '10'. Steps Open 'Client Lookup/Header Configuration Manager'. Click 'Client Header' section. Click [Add New Item]. Select 'Personal Pronouns' from the 'Field to Include in Client Header' drop down list. Select any available location in the 'Field Order'' drop down list. Click [Submit]. Display the client Chart for any client where 'Personal Pronouns' have been entered via an admission form. Verify the 'Personal Pronouns' column displays as defined. Verify the client's preferred pronoun(s) are displayed. Open 'Client Lookup/Header Configuration Manager'. Click 'Client Header Override' section. This will allow setup of the 'Personal Pronouns' to display based on the client's admission program. Click [Add New Item]. Select 'Personal Pronouns' from the 'Field to Include in Client Header' drop down list. Select any program from the 'Program' drop down list. Select any available location in the 'Field Order'' drop down list. Click [Submit]. Open any form such as Progress Notes (Group and Individual) for a client assigned to the selected program and who has 'Personal Pronouns' setup in an admission form. Verify the Client Header displays the 'Personal Pronouns' in the location defined for the program. Close the form. Open the same form for a client who has 'Personal Pronouns' setup in an admission form, but who is not in the selected program. Verify the Client Header displays the 'Personal Pronouns' in the location defined for the 'Client Header' without a program associated. Close the form. Scenario 2: 'Admission' form - Field Validation Specific Setup: RADplus 2022 Update 109 is required for full functionality. Registry Setting "Avatar PM->Client Information->Client Demographics->->->Client Demographics - Additional Fields" must include a value of '2'. Steps Open 'Admission' form for existing client. Ensure that 'Personal Pronouns' field is present in 'Admission' form 'Demographics' section. Enter a value in 'Personal Pronouns' field. Enter/select values for all other required/desired fields in form. Click [Submit]. Re-open Avatar PM 'Admission' form for filed record. In 'Admission' form, ensure that 'Personal Pronouns' field displays 'Personal Pronouns' value from previously filed record. Open Crystal Reports or other SQL reporting tool. In Avatar PM SQL table 'SYSTEM.patient_current_demographics', ensure that 'Personal Pronouns' value filed in 'Admission' form is present in 'personal_pronouns' field. In Avatar PM SQL table 'SYSTEM.patient_demographic_history', ensure that 'Personal Pronouns' value filed in 'Admission' form is present in 'personal_pronouns' field. Scenario 3: 'Update Client Data' form - Verification of 'Client Demographics' form fields Specific Setup: Crystal Reports or other SQL Reporting tool. RADplus 2022 Update 109 is required for full functionality. Steps Open Avatar PM 'Update Client Data' form. Select existing client for update/entry. Ensure that 'Personal Pronouns' field is present in the 'Demographics' section of the 'Update Client Data' form. Enter value in 'Personal Pronouns' field. This is a free text field, allows alphanumeric characters as well as special characters. Maximum length is 40 characters. Enter/select values for all other required/desired fields in form. Click [Submit]. Re-open Avatar PM 'Update Client Data' form for filed record. In 'Update Client Data' form, ensure that 'Personal Pronouns' field displays 'Personal Pronouns' value from previously filed record. Open Crystal Reports or other SQL reporting tool. In Avatar PM SQL table 'SYSTEM.patient_current_demographics', ensure that 'Personal Pronouns' value filed in 'Update Client Data' form is present in 'personal_pronouns' field. In Avatar PM SQL table 'SYSTEM.patient_demographic_history', ensure that 'Personal Pronouns' value filed in 'Update Client Data' form is present in 'personal_pronouns' field. Scenario 4: 'Admission (Outpatient)' - field validation Specific Setup: RADplus 2022 Update 109 is required for full functionality. Registry Setting "Avatar PM->Client Information->Client Demographics->->->Client Demographics - Additional Fields" must include a value of '2'. Steps Open 'Admission (Outpatient)' form for an existing client. Click 'Demographics' section. Ensure that 'Personal Pronouns' field is present in 'Admission (Outpatient)' form. Enter a value in 'Personal Pronouns' field. Enter/select values for all other required/desired fields in form. Click [Submit]. Re-open Avatar PM 'Admission (Outpatient)' form for filed record. Ensure 'Personal Pronouns' field displays ''Personal Pronouns' value from previously filed record. Open Crystal Reports or other SQL reporting tool. In Avatar PM SQL table 'SYSTEM.patient_current_demographics', ensure that 'Personal Pronouns' value filed in 'Admission (Outpatient)' form is present in 'personal_pronoun' field. In Avatar PM SQL table 'SYSTEM.patient_demographic_history', ensure that 'Personal Pronouns' value filed in 'Admission (Outpatient)' form is present in 'personal_pronoun' field. Scenario 5: 'Pre Admit' form - field validation Specific Setup: RADplus 2022 Update 109 is required for full functionality. Steps Open 'Pre Admit' form for an existing Pre Admit client. Click on the 'Demographics' section. Ensure that 'Personal Pronouns' field is present in 'Pre Admit' form. Enter a value in 'Personal Pronouns' field. Enter/select values for all other required/desired fields in form. Click [Submit]. Re-open Avatar PM ''Pre Admit'' form for filed record. Ensure 'Personal Pronouns' field displays 'Personal Pronouns' value from previously filed record. Open Crystal Reports or other SQL reporting tool. In Avatar PM SQL table 'SYSTEM.patient_current_demographics', ensure that 'Personal Pronouns' value filed in ''Pre Admit'' form is present in 'personal_pronouns' field. In Avatar PM SQL table 'SYSTEM.patient_demographic_history', ensure that 'Personal Pronouns' value filed in ''Pre Admit'' form is present in 'personal_pronouns' field. Scenario 6: 'Pre Admit Discharge' - field validation Specific Setup: RADplus 2022 Update 109 is required for full functionality Registry Setting "Avatar PM->Client Information->Client Demographics->->->Client Demographics - Additional Fields" must have value of '2' added in order to display the Personal Pronouns to client demographics forms. Steps Open 'Pre Admit Discharge' form for an existing client. Complete required fields as needed. Ensure that 'Personal Pronouns' field is present in the 'Client Demographics' section. Enter a value in 'Personal Pronouns' field. Enter/select values for all other required/desired fields in form. Click [Submit]. Re-open the 'Pre Admit Discharge' form for the same client. Ensure the 'Personal Pronouns' field is populated with the date entered on discharge. Close the form. Open Crystal Reports or other SQL reporting tool. In Avatar PM SQL table 'SYSTEM.patient_current_demographics', ensure that 'Personal Pronouns' value filed in 'Pre Admit Discharge' form is present in 'personal_pronouns' field. In Avatar PM SQL table 'SYSTEM.patient_demographic_history', ensure that 'Personal Pronouns' value filed in 'Pre Admit Discharge' form is present in ;personal_pronouns; field. Scenario 7: 'Call Intake' - field validation Specific Setup: RADplus 2022 Update 109 is required for full functionality. Registry Setting "Avatar PM->Client Information->Client Demographics->->->Client Demographics - Additional Fields" must include a value of '2'. Steps Open 'Call Intake' form. Set 'Last Name' to any client name. Set 'First Name' to any client name. Set 'Sex' to client gender. Click [Search] Click [New Client]. Enter data in all required fields. Click [Demographics]. Ensure that 'Personal Pronouns' field is present in 'Call Intake' form. Enter a value in 'Personal Pronouns' field. This is a free text alphanumeric field which also allows special characters. Maximum length is 40 characters. Enter/select values for all other required/desired fields in form. Click [Submit]. Re-open 'Call Intake' form for filed record. Ensure 'Personal Pronouns' field displays 'Personal Pronouns' value from previously filed record. Open Crystal Reports or other SQL reporting tool. In Avatar PM SQL table 'SYSTEM.patient_current_demographics', ensure that 'Personal Pronouns' value filed in 'Call Intake' form is present in 'personal_pronouns' field. In Avatar PM SQL table 'SYSTEM.patient_demographic_history', ensure that 'Personal Pronouns' value filed in 'Call Intake' form is present in 'personal_pronouns' field. Scenario 8: 'Entity Information Display' - 'Personal Pronouns'. Specific Setup: RADplus 2022 Update 109 is required for full functionality. Registry Setting "Avatar PM->Client Information->Client Demographics->->->Client Demographics - Additional Fields" is set to include a value of "2" for the Personal Pronouns field to be added to client demographics in various forms. Steps To add the 'Personal Pronouns' to client search windows: Open 'Entity Information Display' form. Select 'Client' from the 'Entity Database' drop down list. Select 'One' in the 'Number of Additional Columns to Display' field. Note that depending on your setup, if there are entries already defined, you may need to select 'Two' or 'Three'. Set the 'Entity name Header Text' to any description. Set the 'Approximate Number of Characters to Display for Entity Name' to any numeric. This will be the number of characters to display in the entity column in the search window. Select 'Personal Pronouns' from the 'Entity Information Display Column 1' drop down list. Set the 'Entity Information Display Column 1 Header Name' to 'Personal Pronouns' or any other description you require. Set the 'Approximate Number of Characters to Display for Entity Lookup Column 1' to any value. Click [Submit]. Open any form where a client search window will pop-up such as 'Update Client Data'. Set the 'Select Client' field to any existing client to search for. When the search selections display, verify the 'Personal Pronouns' column is displayed. This column may be blank at this time. Select any client from the list. In the selected form, 'Update Client Data' was used for this test, navigate to the 'Personal Pronouns' field. This may be at the bottom of the form. Enter any 'Personal Pronouns' as appropriate. This is a free form text field and will accept numbers and letters, as well as special characters. Maximum length is 40. Click [Submit]. Open the same form again. Search for the same client. Verify that the 'Personal Pronouns' column on the search window is now populated with the value entered in the form. Close the form. Scenario 9: Client Discharge web service Specific Setup: SoapUI or other web service tool. Steps Open SoapUI or another web service tool. Consume the WebSvc.ClientDischarge.cls wsdl. Set the 'SystemCode', 'UserName', and 'Password' to correct values. Set 'DateofDischarge' field to the client discharge date. Set 'DischargePractitioner' to the discharging practitioner ID. Set 'DischargeReferral Type' to the Type code for the discharge. Set 'DischargeTime' to the time of the discharge. Set 'PersonalPronouns' to any text value, maximum 40 characters. Set 'ClientID' to the client id to be discharged. Set 'EpisodeNumber' to the client episode to be discharged. Click 'Send' request. Validate the response displays 'Client Discharge web service has been filed successfully'. Open the 'Discharge' form in Avatar PM. Select the client discharged in the web service. Verify the 'Personal Pronouns' display the value entered in the Web Service. Close the form. Scenario 10: Client Admission Web Service - Verification of web service filing Specific Setup: Any Web Service tool such as 'SoapUI'. Steps Using Avatar PM 'Client Admission' web service, submit an 'Admission' record for a client and episode, including the 'Personal Pronouns' field. Ensure that Admission record returns a confirmation message in the web service of successful filing. Open Avatar PM 'Admission' or Avatar PM 'Admission (Outpatient) form. Select client record used in 'Client Admission' web service filing. Ensure that 'Admission' record/episode filed via web service is present with values filed via web service, including the 'Personal Pronouns'. Scenario 11: Call Intake Web Service validation - Intake, Update, Delete records Specific Setup: Any web service tool such as 'SoapUI' Crystal Reports or other SQL tool. Steps Using Avatar PM 'ClientCallIntake' web service, submit an Intake record for a 'Call Intake' client, including the 'Personal Pronouns' field. Ensure that Call Intake record returns 'Client Call Intake web service has been filed successfully' message. Open Avatar PM 'Call Intake' form. Select client the record used in web service filing. Ensure that 'Call Intake' record/episode filed via web service is present with values filed via the web service, including the 'Personal Pronouns'. Using Avatar PM 'UpdateCallIntake' web service, submit an updated record for a 'Call Intake' client, including the 'Personal Pronouns' field. Ensure that the 'Update Call Intake' record returns 'Update Call Intake web service has been filed successfully' message. Open Avatar PM 'Call Intake' form. Select client the record used in web service filing. Ensure that 'Call Intake' record/episode filed via web service is present with values filed via the web service, including the 'Personal Pronouns'. Using Avatar PM 'DeleteCallIntake' web service, submit a delete record for a 'Call Intake' client. Ensure that Call Intake record returns 'Delete Client Call Intake web service has been filed successfully' message. Using Crystal reports, or other SQL reporting tool, create a report against SYSTEM.patient_current_demographics. Include, at a minimum, the following fields: PATID personal_pronouns patient_name Run the report. Verify the above records filed via web services are displayed. Close the report. Scenario 12: Client Demographics Web Service validation Specific Setup: SoapUI or other web service tool. Steps Using SoapUI or any other Web Service tool, consume the WSDL for WEBSVC.ClientDemographics.cls In the Request, set the SystemCode, UserName, and Password to the correct value. Set the 'PersonalPronouns' field to any characters (up to 40 maximum characters). Set the 'Sex' field to the gender for the selected client. Set the 'ClientID' to any client number. Complete other fields as desired. Click the Send button. Validate the Response message displays : 'Client Demographics web service has been filed successfully.' In 'Avatar PM', open the 'Update Client Data' form for the client used in the web service. Navigate to the 'Personal Pronouns' field. Validate that the data displays as entered in the Web Service. Close the form.	Topics • Admission • Update Client Data • Admission (Outpatient) • Pre Admit • Web Services
Update 66 Summary \| Details Claim Support - Create Interim Billing Batch File Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Guarantors/Payors Financial Eligibility Print Bill Re-Print Bill Delete Claim Scenario 1: Re-Print Bill/Delete Claim - Interim Billing Batch File. Specific Setup: Note: Full testing will require waiting until the next day after an additional charge is added during UAT testing steps. Clients: Select or create two clients that are in the same program and are assigned the same guarantor in Financial Eligibility. (Client 1 & Client 2). Client 1: Create one service. Note the date of service. Note the data entry date. Client 2: Create one service using the same date of service. Note the data entry date. ‘Create Interim Billing Batch File’ is used to create a batch for both services. Set the ‘From Date’ and ‘Through Date’ to the date of service. Set the ‘Data Entry From Date’ and the ‘Data Entry Through Date’ to the current date. Note the batch number. ‘Close Charges’ is used to close charges for the interim batch. ‘Print Bill’ is used to create claims for the interim batch. Use a claim date that is a few days after the date of service. Note the date of claim and the claim form. ‘Client Ledger’ is used to verify that the services contain a claim number. Steps Open ‘Re-Print Bill’. Enter the ‘Date Of Claim’ from Setup. Select ‘Interim Batch’ in ‘Reprint Claims By’. Select the interim batch used above in ‘Interim Batch Number’. Select desired value in ‘Unpaid Claims Only’. Select the claim form from Setup in ‘Print On What Form’. Click [Select Claims To Reprint]. Select the claim for both clients. Click [OK]. Click [Process]. Validate that the report contains both client/claims and the information is correct. Close the report. Close the form. Open ‘Delete Claim’. Enter the ‘Date Of Claim’ from Setup. Select ‘Interim Batch’ in ‘Delete Claim By’. Select the interim batch from Setup in ‘Interim Batch Number/837 File’. Select ‘None’ in ‘Default All Or None’. Click [Select Claim To Delete]. Validate that both claims are displayed. Click [Cancel]. Close the form. Open ‘Client Charge Input’. Create a service for Client 1. Note the date of service. Note the data entry date. Close the form. Stop testing and resume the next day. Open ‘Client Charge Input’. Create a service for Client 2, using the same date of service used four steps above. Close the form. Open ‘Create Interim Billing Batch File’ and create a batch for the two services. Set the ‘From Date’ and ‘Through Date’ to the date of service. Set the ‘Data Entry From Date’ and the ‘Data Entry Through Date’ to the current date. Click [Process]. Validate that the report only contains the service for Client 2. Close the report. Close the form. Open ‘‘Print Bill’ and create a claim for the interim batch using the same date of claim from ‘Setup’. Note the claim form. Validate that only Client 2 is contained in the report. Close the report. Close the form. Open ‘Re-Print Bill’. Enter the ‘Date Of Claim’. Select ‘Interim Batch’ in ‘Reprint Claims By’. Select the interim batch created in UAT in ‘Interim Batch Number’. Select desired value in ‘Unpaid Claims Only’. Select the claim form used above in ‘Print On What Form’. Click [Select Claims To Reprint]. Validate that only the claim for Client 2 is included. Select the claim. Click [OK]. Click [Process]. Validate that the report contains Client 2, and the information is correct. Close the report. Close the form. Open ‘Delete Claim’. Enter the ‘Date Of Claim’. Select ‘Interim Batch’ in ‘Delete Claim By’. Select the interim batch used above in ‘Interim Batch Number/837 File’. Select ‘None’ in ‘Default All Or None’. Click [Select Claim To Delete]. Validate that only the claim for Client 2 is displayed. Click [Cancel]. Close the form. Eligibility Inquiry (270) Submission Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: SQL Query/Reporting Guarantors/Payors Eligibility Inquiry (270) Request Eligibility Inquiry (270) Submission Scenario 1: Eligibility Inquiry (270) Submission - compiling 270 request for the client when minimum search options are defined Specific Setup: Registry Settings: The 'Avatar PM->Client Information->Client Demographics->>>Client Demographics - Additional Fields' registry setting doesn't contain a value of '3'. The 'Avatar PM->Billing->Fast Financial Eligibility->->->Additional Fields To Add' registry setting contains all selections. Dictionary Update: File=Client Data Element = Client's Relationship To Subscriber Dictionary Code/Value = desired code/value. Note the dictionary code/value Extended Dictionary Data Element is not set to "Yes" Guarantors/Payors Edit/Add a guarantor that is configured for the 270 eligibility submission. Note the guarantor id and name for further testing. Set the 'Minimum Search Options' field in the '270 / 271 / 834' section to "Last Name", "First Name" and "Date Of Birth". Admission (Outpatient): An outpatient client is admitted. Note the client ID, admission date and admission program. Fast Financial Eligibility: The guarantor configured in 'Guarantors/Payors' form is assigned to the client. Select the dictionary code/value in the 'Client Relationship' field that is configured in the 'Dictionary Update' form. Make sure to populate the Subscriber Name #1, Subscriber's Birth Date # 1 and Subscriber Social Security # 1 fields. Steps Open the 'Eligibility Inquiry (270) Request' form. Add an inquiry for the desired client/guarantor. Note the date range. Close the form. Open the 'Eligibility Inquiry (270) Submission' form. Select 'Compile File' in 'Options'. Select the desired 'Guarantor'. Click 'T' button in 'Through Date'. Click [Process]. Verify that the compile process completed successfully. Review the 'Eligibility Inquiry (270)' report. Click 'Submission Data' link. Verify the report displays client and service included in the eligibility inquiry (270) request/submission correctly. Close the report. Select 'Dump File' in 'Options'. Click the 'T' button in 'File From Date'. Click the 'T' button in 'File Through Date'. Select the desired file in 'Select File' Click [Process]. Verify the report displays client and service included in the eligibility inquiry (270) request/submission correctly. Close the report. Change the 'File From Date' to any valid date Click [Process]. Verify the report displays client and service included in the eligibility inquiry (270) request/submission correctly. Close the report. As desired, repeat steps 14 - 24 for 'Create File On Server For Submission' and 'Run Report' in 'Options'. If desired, select 'Delete File' in 'Options'. Close the form.	Topics • Print Bill • Eligibility Inquiry (270) Submission
Update 68 Summary \| Details CPT Place of Service Override Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: User Definition Financial Eligibility Print Bill Electronic Billing CPT Place Of Service Override Guarantors/Payors File Import Scenario 1: Cal-PM - CPT Place of Service Override - Billing Specific Setup: Registry Settings: Avatar PM->System Maintenance->Service Code Maintenance->->->Allow CPT Place Of Service Override = 'Y'. User Definition is used to give the tester access to the form 'CPT Place Of Service Override' and the tables 'table_cpt_place_override' and 'table_cpt_pos_template_def'. CPT Code Definition: Identify two codes that are associated to two different service codes in ‘Service Fee/Cross Reference Maintenance’. Service Codes: Service Code 1: Is associated to CPT Code 1. Service Code 2: Is associated to CPT Code 2. Client: Select an outpatient client. Note the program. Ensure that the client has an active Diagnosis record. Ensure the client has an active Financial Eligibility record. Note the guarantor. Program Maintenance is used to note the ‘Location’. Client Charge Input: Create a service for each of the service codes. Note the date(s) of service. Client Ledger: Verify that the services distributed to the guarantor noted above. Close Charges is used to close the charges. Create Interim Billing Batch File is used to create a batch specific to the guarantor, program, and client. Print Bill is used to create an unclaimed bill for the interim batch. Print the report for further comparison. The service line will contain the service date, location code, CPT Code, and other details. Electronic Billing is used to create an unclaimed bill for the interim batch. Print the dump file for further comparison. The ‘CLM’ segment will contain the location in field 5 (CLM05). The ‘SV1’ will contain the location in field 5 (SV105). Steps Open ‘CPT Place Of Service Override’. Select ‘Add’ in ‘Action’. Enter desired value in ‘Template Name’. Select the client’s guarantor in ‘Guarantor’. Select the client’s program in ‘Program’. Select ‘Individual’ in ‘All or Individual Service Code’. Enter ‘Service Code 1’ in ‘Select Service’. Validate that the service is saved in ‘Selected Service(s)’. Select ‘Individual’ in ‘All or Individual CPT Code’. Enter ‘CPT Code 1’ in ‘Select CPT’. Validate that the code is saved in ‘Selected CPT(s)’. Select desired value in ‘All or Individual Location’. Enter ‘Modifiers’, if desired. Select a location value that differs from the ‘Print Bill’ location in ‘Place Of Service (HCFA 24-B)’. Select a location value that differs from the ‘Electronic Billing’ location in ‘Place Of Service (837 Professional)’. Click [Submit]. Close the form. Open ‘Print Bill’ and print an unclaimed bill for the interim batch. Validate that the location for Service Code 1 now contains the value selected in ‘Place Of Service (HCFA 24-B)’. Validate that the location for Service Code 2 contains the value that was in bill printed during Setup. Close the report. Close the form. Open ‘Electronic Billing’ and create an unclaimed bill for the interim batch. Validate that the ‘CLM’ LOCATION now contains the value selected in ‘Place Of Service (837 Professional)’. Validate that the ‘SV1’ location for Service Code 1 now contains the value selected in ‘Place Of Service (837 Professional)’. Validate that the ‘SV1’ location for Service Code 2 contains the value that was in the dump file printed during Setup. Close the report. Close the form. Scenario 2: File Import - CPT Place of Service Override Specific Setup: The 'Avatar_Cal-PM_File_Import_Record_Layouts' is included in the update zip file to aid in creating the test files for File Import. Registry Settings: Note the value of the 'Avatar PM->System Maintenance->File Import->->->Import File Delimiter' setting to determine how to build the test files for File Import. Avatar PM->System Maintenance->Service Code Maintenance->->->Allow CPT Place Of Service Override = 'Y'. User Definition is used to give the tester access to the form 'CPT Place Of Service Override' and the tables 'table_cpt_place_override' and 'table_cpt_pos_template_def'. Service Codes: Select one or more for the File Import test files. Guarantors/Payors: Select one or more for the File Import test files. Program Maintenance: Select one or more for the File Import test files. CPT Code Definition: Select one or more for the File Import test files. Dictionary Update: Client: Print dictionary '(578) Place Of Service (HCFA 24-B)' to select a value for the File Import test files. Print dictionary '(579) Place Of Service (837 Professional)' to select a value for the File Import test files. Print dictionary '(10006) Location' to select values for the File Import test files. Other Tabled Files: Print dictionary '(556) Action' to select values for the File Import test files. Create a file import item with an 'Action' of '1' which will 'add' the 'CPT Place Of Service Override Template' when posted. There will be no value in the 'Template ID' field. Copy the 'add' file and edit the 'Action' to be '2' to make it an 'edit' file. Edit at least one thing in the file, such as the 'Modifier' field. After the 'Add' file is posted, the 'Template ID' will need to be added to this file. Copy the 'edit' file and edit the 'Action' to be '3' to make it a 'delete' file. After the 'Add' file is posted, the 'Template ID' will need to be added to this file. Steps Open ‘File Import’. Select ‘CPT Place Of Service Override’ in ‘File Type’. Upload, compile, print, and post the file that will add the template. Close the form. Open ‘CPT Place Of Service Override’. Click [Display CPT Place Of Service Overrides]. Validate that the ‘CPT Place Of Service Override Report’ opens. Validate that the report contains the data that was submitted in the posted file. Close the report. Select ‘Edit’ in ‘Action’. Select the imported template in ‘Select Template’. Validate the template data. Close the form. Open ‘File Import’. Select ‘CPT Place Of Service Override’ in ‘File Type’. Upload, compile, print, and post the file that will edit the template. Close the form. Open ‘CPT Place Of Service Override’. Click [Display CPT Place Of Service Overrides]. Validate that the ‘CPT Place Of Service Override Report’ opens. Validate that the report contains the edited data that was submitted in the posted file. Close the report. Select ‘Edit’ in ‘Action’. Select the imported template in ‘Select Template’. Validate the edited template data. Close the form. Open ‘File Import’. Select ‘CPT Place Of Service Override’ in ‘File Type’. Upload, compile, print, and post the file that will delete the template. Close the form. Open ‘CPT Place Of Service Override’. Click [Display CPT Place Of Service Overrides]. Validate that the ‘CPT Place Of Service Override Report’ opens. Validate that the report does not contain the template. Close the report. Select ‘Edit’ in ‘Action’. Validate that the template is not available in ‘Select Template’. Close the form.	Topics • Print Bill • 837 Professional • Database Management • File Import • NX
Update 70 Summary \| Details UTC enabled - Data Entry Local Time Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Practitioner Enrollment Dynamic Forms CADDS Data Collection Verification Scenario 1: Validating Practitioner Enrollment with UTC Enabled Specific Setup: The system must be configured to use UTC. A practitioner must be enrolled in the system. Steps Open the "Practitioner Enrollment" form. Select the practitioner from setup and update their enrollment. Click "Submit" to file the data. Using the preferred method to validate SQL tables, validate the following columns exist in the SQL table SYSTEM.sfaff_category_history: data_entry_offset (e.g -4), data_entry_time_j (e.g. 12:26:13), data_entry_timezone_info_all (e.g. EDT;Eastern Daylight Time;-0400), data_entry_timezone_short (e.g EDT), data_entry_utc (e.g. 9/21/2022 16:26). Using the preferred method to validate SQL tables, validate the data_entry_time (e.g. 12:26 PM) in the SQL table SYSTEM.sfaff_category_history appropriately reflects the time of data entry. Scenario 2: Validating Practitioner Enrollment with UTC disabled Specific Setup: A practitioner must be enrolled in the system. Steps Open the "Practitioner Enrollment" form. Select the practitioner from setup and update a field in the enrollment. Click "Submit" to file the data. Using the preferred method to validate SQL tables, validate the following columns don't exist in the SQL table SYSTEM.sfaff_category_history: data_entry_offset, data_entry_time_j, data_entry_timezone_info_all, data_entry_timezone_short), data_entry_utc. Using the preferred method to validate SQL tables, validate the data_entry_time (e.g. 12:26 PM) in the SQL table SYSTEM.sfaff_category_history appropriately reflects the time of data entry. Scenario 3: Validating Client Charge Input with UTC enabled Specific Setup: The system must be configured to use UTC. Admit a new client or select an existing client for the test client. Steps Open the "Client Charge Input" form. Enter a service charge for the test client. Using the "Client Ledger" form, validate the service was generated. Using the preferred method to validate SQL tables, validate the following columns in the SYSTEM.billing_tx_history table: data_entry_offset (e.g. -4), data _entry_time_j (e.g. 12:26:13), data_entry_timezone_info_all (e.g. EDT;Eastern Daylight Time;-0400), data_entry_timezone_short (e.g. EDT), data_entry_utc (e.g. 09/20/2022 16:26) Using the preferred method to validate SQL tables, validate the data_entry_time column in the SYSTEM.billing_tx_history table:reflects the time of service entry. Scenario 4: Validating Client Charge Input with UTC disabled Specific Setup: Admit a new client or select an existing client for the test client. Steps Open the "Client Charge Input" form. Enter a service charge for the test client. Using the "Client Ledger" form, validate the service was generated. Using the preferred method to validate SQL tables, validate the following columns don't exist in the SYSTEM.billing_tx_history table: data_entry_offset, data _entry_time_j, data_entry_timezone_info_all, data_entry_timezone_short, data_entry_utc. Using the preferred method to validate SQL tables, validate the data_entry_time column in the SYSTEM.billing_tx_history table:reflects the time of service entry.	Topics • Practitioner • NX • Client Charge Input
Update 73 Summary \| Details Diagnosis - 'Add To Problem List' functionality Scenario 1: Diagnosis - Add new / Add to Problem List Specific Setup: A client must be enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Diagnosis' form. Click [Add] if present. Select any value for the 'Type of Diagnosis' field. Enter the desired values for the 'Date of Diagnosis' and 'Time of Diagnosis' fields. Click [New Row]. Enter any value in the 'Diagnosis Search' field and press the 'Enter' key. Validate "Powered By IMO Terminology" displays under the search results. Select a diagnosis that has an associated SNOMED code. Populate any desired and required fields. Select "Yes" in the 'Add to Problem List' field. Submit the form. Access the 'Problem List' form. Click [Enter Problems]. Validate the new diagnosis is included. Click [View - DSM/IDC Code]. Validate a dialog opens with the DSM/IDC code data for the problem. Close out of the dialog. Click [View - System Notes]. Validate the dialog displays the user information for the problem. Close out of the dialog. Click [Close/Cancel]. Close the form. Scenario 2: Diagnosis / Add to Problem List Specific Setup: A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Diagnosis' form. Add a diagnosis. Select the desired practitioner in the 'Diagnosing Practitioner' field. Do not select a value in the 'Add To Problem List' field. Click [Submit] and close the form. Select "Client A" and access the 'Problem List' form. Click [View/Enter Problems]. Validate the 'Problem List' grid does not contain the problem added via the 'Diagnosis' form. Close the form. Select "Client A" and access the 'Diagnosis' form. Edit the previously filed diagnosis. Select "Yes" in the 'Add To Problem List' field. Click [Submit] and close the form. Select "Client A" and access the 'Problem List' form. Click [View/Enter Problems]. Validate the 'Problem List' grid contains the problem added via the 'Diagnosis' form. Close the form. Scenario 3: Diagnosis - Add new / Add to Problem List Specific Setup: A client must be enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Diagnosis' form. Click [Add] if present. Select any value for the 'Type of Diagnosis' field. Enter the desired values for the 'Date of Diagnosis' and 'Time of Diagnosis' fields. Click [New Row]. Enter any value in the 'Diagnosis Search' field and press the 'Enter' key. Validate "Powered By IMO Terminology" displays under the search results. Select a diagnosis that has an associated SNOMED code. Populate any desired and required fields. Select "Yes" in the 'Add to Problem List' field. Submit the form. Access the 'Problem List' form. Click [Enter Problems]. Validate the new diagnosis is included. Click [View - DSM/IDC Code]. Validate a dialog opens with the DSM/IDC code data for the problem. Close out of the dialog. Click [View - System Notes]. Validate the dialog displays the user information for the problem. Close out of the dialog. Click [Close/Cancel]. Close the form.	Topics • Diagnosis • Problem List
Update 74 Summary \| Details Service Fee/Cross Reference Maintenance Scenario 1: Service Fee/Cross Reference Maintenance - Location Specific Setup: Dictionary Update: Client (10006) Location: Inactivate a location. This code will not be available in the 'Location' field in Service Fee/Cross Reference Maintenance’. Service Code: Identify a service code has a ‘Service Fee/Cross Reference Maintenance’ record. Note the ‘From Date’. Steps Open ‘Service Fee/Cross Reference Maintenance’. Select ‘Edit Existing’ in ‘Enter New Or Edit Existing Fee/Cross Reference’. Enter the service code from setup. Enter the ‘From Date’. Click [Select Fee/Cross Ref To Edit/Default From Existing Row]. Select the desired row. Click [OK]. Select a value in the ‘Location’ field, validating that the inactive dictionary code is not available. Enter a 'Fee'. Enter a 'UB-04 Revenue Code'. Enter a 'CPT-4 / HCPCS Code'. Click [Submit]. Click [Yes]. Select ‘Edit Existing’ in ‘Enter New Or Edit Existing Fee/Cross Reference’. Enter the service code from setup. Enter the ‘From Date’. Click [Select Fee/Cross Ref To Edit/Default From Existing Row]. Select the desired row. Click [OK]. Validate that the selected ‘Location’ exists. Validate that the entered 'Fee' exists. Validate that the entered 'UB-04 Revenue Code' exists. Validate that the entered 'CPT-4 / HCPCS Code' exists. Click [Discard]. Click [Yes].	Topics • Service Fee/Cross Reference Maintenance • NX
Update 75 Summary \| Details "Enable Multiple Add-On Code Per Primary Code " Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Site Specific Section Modeling (CWS) Progress Notes (Group and Individual) Site Specific Section Modeling Import/Export (CWS) Scenario 1: 'Site Specific Section Modeling' - Validate 'Add-On' fields enabled/disabled via the "Enable Multiple Add-On Code Per Primary Code" registry setting Specific Setup: Have a system with a copy of the "Progress Note (Group and Individual)" form, created via the "Create New Progress Note" form. [PNCopy1] Have registry setting 'Enable Multiple Add-On Code Per Primary Code Functionality' set to "N". Steps Open form "Site Specific Section Modeling" Select the "Progress Note (Group and Individual)" form Select the "Prompt Definition" section In the "Prompt Definition" grid, Locate and select the 'Add-On Service' field for edit, Verify the 'Exclude from Data Collection Instrument' field is disabled Locate and select the 'Add-On Duration', field for edit, Verify the 'Exclude from Data Collection Instrument' field is disabled Locate and select the 'Add-On Service Notes', field for edit, Verify the 'Exclude from Data Collection Instrument' field is disabled Locate and select the 'Save Add-On Service Notes' field for edit, Verify the 'Exclude from Data Collection Instrument' field is disabled Locate and select the 'Selected Add-On Services' field for edit, Verify the 'Exclude from Data Collection Instrument' field is disabled Locate and select the ''Select Add-On Service Entry to Edit/Remove' field for edit, Verify the 'Exclude from Data Collection Instrument' field is disabled Locate and select the 'Remove Add-On Service' field for edit, Verify the 'Exclude from Data Collection Instrument' field is disabled Close the form Repeat step 1 for the progress note form copy [PNCopy1] Validate results are as expected Open form "Progress Note (Group and Individual)" Validate fields 'Add-On Service', 'Add-On Duration', 'Add-On Service Notes', Save Add-On Services, 'Selected Add-On Services', 'Select Add-On Service Entry to Edit/Remove' and 'Remove Add-On Service', are not present on the form as expected Repeat step 3 for the progress note form copy [PNCopy1] Validate results are as expected Open form "Registry Settings" Search for registry setting " 'Enable Multiple Add-On Code Per Primary Code Functionality' Click to edit the registry setting and set the "Registry Setting Value" field to "Y" Submit the form Open form "Site Specific Section Modeling" Select the "Progress Note (Group and Individual)" form Select the "Prompt Definition" section In the "Prompt Definition" grid, Locate and select the 'Add-On Service' field for edit, Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No" Locate and select the 'Add-On Duration', field for edit, Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No" Locate and select the 'Add-On Service Notes', field for edit, Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No" Locate and select the 'Save Add-On Service Notes' field for edit, Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No" Locate and select the 'Selected Add-On Services' field for edit, Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No" Locate and select the ''Select Add-On Service Entry to Edit/Remove" field for edit, Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No" Locate and select the 'Remove Add-On Service' field for edit, Verify the 'Exclude from Data Collection Instrument' field is enabled and set the value to "No" Submit the form Return to form "Progress Note (Group and Individual)" Validate fields 'Add-On Service', 'Add-On Duration', 'Add-On Service Notes', Save Add-On Services, 'Selected Add-On Services', 'Select Add-On Service Entry to Edit/Remove' and 'Remove Add-On Service' are now present and enabled on the form, as expected Repeat step 6 and 7 for the progress note form copy [PNCopy1] Validate results are as expected	Topics • Site Specific Section Modeling
Update 76 Summary \| Details The 'CareConnect HIE Configuration' and 'Query For External CCD' forms Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareConnect HIE Configuration Scenario 1: Query for External CCD - Search, Preview, Save CCD's and validate SDK actions are triggered Specific Setup: A client must be enrolled in an existing episode (Client A). Steps Access the 'Query for External CCD' form. Select "Client A" in the 'Client Search' field. Select an organization in the 'Organization Name or Zip' field. Click [Search CCDs]. Select a CCD in the 'Available CCDs' field. Enter the desired provider in the 'Provider Referred To' field. Click [Preview]. Validate the CCD is displayed and close it. Click [Save]. Validate an "Information" message is displayed stating: Saved. Click [OK] and close the form. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Enter "Client A" in the 'Client ID' field. Enter "ExternalDataAckowledgementCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'CareFabric Monitor Report' contains an 'ExternalDataAcknowledgementCreated' record. Click [Click To View Record]. Validate the 'referredToProviderID' - 'id' field contains the provider ID selected in the previous steps. Close the report and the form. Access Crystal Reports or other SQL Reporting Tool. Create a report using the 'SYSTEM.ccd_tempstorage' table. Validate a row is displayed for the CCD saved in the previous steps. Validate the 'PATID' field contains "Client A". Validate the 'provider_referred_to' field contains the provider ID selected in the previous steps. Validate the 'provider_referred_to_name' field contains the provider name selected in the previous steps. Close the report. Scenario 2: CareConnect HIE Configuration - Carequality Configuration - Search Carequality Organizations Steps Access the 'CareConnect HIE Configuration' form. Select the "Carequality Configuration" section. Enter the desired zip code in the 'Organization Name or Zip' field. Validate the 'Within N Miles of Zip' field is displayed. Select the 'Within N Miles of Zip' help message. Validate the following message is displayed: This field can be used to further limit the external provider results when a zip code is entered. Close the help message. Enter the desired value in the 'Within N Miles of Zip' field. Click [Search]. Validate the applicable organizations are displayed in the 'Select Organization(s)' field. Select the desired organization in the 'Select Organization(s)' field. Validate the selected organization is now listed in the 'Organization: Exceptions and Favorites' grid. Select the desired value in the 'Status' field for the new organization. Click [Submit]. Scenario 3: Query For External CCD - Field Validations Specific Setup: A client is enrolled in an existing episode (Client A). Steps Access the 'Query for External CCD' form. Select "Client A" in the 'Client Search' field. Enter the desired zip code in the 'Organization Name or Zip' field. Validate the 'Within N Miles of Zip' field is displayed. Select the 'Within N Miles of Zip' help message. Validate the following message is displayed: This field can be used to further limit the external provider results when a zip code is entered. Close the help message. Enter the desired value in the 'Within N Miles of Zip' field. Click [Search]. Validate the applicable organizations are displayed in the 'Organizations' grid. Click [Clear]. Validate the organizations are no longer displayed in the 'Organizations' grid. Close the form.	Topics • Query for External CCD • CareConnect HIE Configuration
Update 77 Summary \| Details Avatar Cal-PM 'Require Authorizations At Guarantors/Payors Level' Registry Setting Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Guarantors/Payors Managed Care Authorizations Payor Based Authorizations Electronic Billing Electronic Billing - Electronic Billing report Payor Based Authorizations Report Scenario 1: 'Authorization Group Definition' - Form Verification Specific Setup: Avatar Cal-PM Registry Setting 'Require Authorizations at Guarantors/Payors Level' must be enabled Crystal Reports or other SQL reporting tool Steps Open Avatar Cal-PM 'Authorization Group Definition' form (under 'Avatar PM -> System Maintenance -> System Definition' menu). Ensure the following fields/buttons are present in form: 'Add, Edit Or Delete' Radio button selection field 'Authorization Group' Selection field for 'Edit' and/or 'Delete' options 'File Authorization Group' button 'Authorization Group Name' 'Status' Radio button selection field, 'Active'/'Inactive', default value 'Active' 'Authorization Group Information' Multiple row display field for all Authorization Group date/service code rows entered 'Select Row To Edit' Selection field for Authorization Group date/service code rows 'Update' button 'Delete' button 'Effective Date' Effective date for Authorization Group date/service code row; required 'Expiration Date' Expiration date for Authorization Group date/service code row 'Service Code(s)' Multiple selection field for Authorization date/service code row, including 'All Service Codes' selection; required Select 'Add' option, and enter value for 'Authorization Group Name' field. Enter 'Effective Date' and 'Expiration Date' (if desired) for Authorization Group date/service code row entry. Select one or more 'Service Code(s)' value for Authorization Group date/service code row entry (or optionally select 'All Service Codes'). Click 'Update' button to save Authorization Group date/service code row entry. Ensure that Authorization Group date/service code row entry is displayed as entered/updated in the 'Authorization Group Information' display field. Repeat steps 4-6 above for additional Authorization Group date/service code row entries as desired. For Authorization Group date/service code row edit, select desired entry in the 'Select Row To Edit' field; make desired changes and click 'Update' button to save Authorization Group date/service code row update. For Authorization Group date/service code row deletion, select desired entry in the 'Select Row To Edit' field and click 'Delete' button. Click 'File Authorization Group' button to file/save Authorization Group (along with Authorization Group date/service code row entries as defined). Ensure user is presented with confirmation dialog noting 'Filed Successfully'; click 'OK' button to return to form. Select 'Edit' option, and select Authorization Group entered/defined above. Ensure all field values are present in 'Authorization Group Definition' form/record as previously entered/filed, including all Authorization Group date/service code entry row(s). Open Crystal Reports or other SQL reporting tool. In Avatar Cal-PM SQL table 'SYSTEM.table_auth_group', ensure that entered/filed Authorization Groups are present. In Avatar Cal-PM SQL table 'SYSTEM.table_auth_group_svc_cds', ensure that entered/filed Authorization Group date/service code row entries are present. Scenario 2: Avatar Cal-PM Registry Settings - Verification of 'Require Authorizations At Guarantors/Payors Level' Registry Setting Steps Open 'Registry Settings' form. Enter search value 'Require Authorizations At Guarantors/Payors Level' and click 'View Registry Settings' button. Ensure Registry Setting 'Require Authorizations At Guarantors/Payors Level' is returned (under 'Avatar PM -> System Maintenance -> Guarantors/Payors' path). Ensure 'Registry Setting Details' field contains the following explanation text: "Selecting 'Y' allows filing for the 'Authorization Group Definition' form, adds the 'Authorization Group', 'Program', and 'Practitioner Category' fields to the 'Payor Based Authorizations' form, modifies the 'Expiration Date' field in the 'Payor Based Authorizations' form to be not required, modifies the 'Service Code', 'Program', and 'Guarantor' fields in the 'Payor Based Authorizations' form to be multiple select, adds the 'Authorization Group(s)' fields to the 'Guarantors/Payors' (Authorization Information) form, new fields will be added to the 'Guarantors/Payors' (Authorization Information) form which will enable the user to identify if an authorization should be required. In the 'Managed Care Authorizations' (Managed Care Authorization Data) form the 'Authorization Number' field will no longer be required. Selecting 'Y' also modifies the 'Authorization Group' field in the 'Managed Care Authorizations' (Managed Care Authorization Data) form so that if a selection is made in the 'Authorization Group' field the 'Service Code' field will be limited to the Service Codes in the selected Authorization Group. Selecting 'N' disallows filing for the 'Authorization Group Definition' form, removes the 'Authorization Group', 'Program', and 'Practitioner Category' field from the 'Payor Based Authorizations' form, the 'Expiration Date' field in the 'Payor Based Authorizations' form will be required, the 'Service Code', 'Program', and 'Guarantor' field in the 'Payor Based Authorizations' form will be single select, removes the 'Authorization Group(s)' fields from the 'Guarantors/Payors' (Authorization Information) form, new fields in the 'Guarantors/Payors' (Authorization Information) form which will enable the user to identify if an authorization should be required will be removed. In the 'Managed Care Authorizations' (Managed Care Authorization Data) form the 'Authorization Number' field will be required. Selecting 'N' also changes the 'Authorization Group' logic back in the authorization forms." Scenario 3: 'Guarantors/Payors' - Verification of 'Authorization Information' Form Section/Fields Specific Setup: Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' must be enabled Crystal Reports or other SQL reporting tool Steps Open Avatar Cal-PM 'Guarantors/Payors' form. Select Add or Edit action in 'Add New or Edit Existing Guarantor' field. Enter new (or select existing) Guarantor Code. Complete all required/desired fields in main section of 'Guarantors/Payors' form. Navigate to 'Authorization Information' section of 'Guarantors/Payors' form. Ensure the following fields/buttons are present in form: 'Verify Services and Appointments Against Available Authorizations' Selection values for 'Check For Available Dollars', 'Check For Available Units' and/or 'Check For Available Visits' 'Verification Level For Authorizations For Client Charge Input' 'Verification Level For Authorizations For Appointment Scheduling' 'Verification Level For Authorizations For 837 Electronic Billing' 'Preauthorization Notice Upon Assignment' 'Authorization Groups' Ensure that sub-section for input of Authorization Requirements by date/service code is present where Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' is enabled, including the following fields: 'Effective Date' 'Expiration Date' 'Authorization Group' 'Service Code(s)' Multiple selection field for Authorization Requirement date/service code row, including 'All Service Codes' selection; required 'Require Authorization' Yes/No radio button selection field, required Determines whether applicable Authorization (Managed Care Authorization or Payor Based Authorization) is required for selected dates/service code allowance in Client Charge Input, Appointment Scheduling and/or 837 Electronic Billing 'Require Authorization Number' Yes/No radio button selection field, required Determines whether Authorization Number in applicable Managed Care Authorization or Payor Based Authorization is required for selected dates/service code allowance in Client Charge Input, Appointment Scheduling and/or 837 Electronic Billing 'Select Authorization Item' Selection field for Authorization Requirement date/service code rows 'Update' button 'Delete' button Enter 'Effective Date' and 'Expiration Date' (if desired) for Service Authorization Requirement date/service code row entry. Select one or more codes or 'All Service Codes' in 'Service Code(s)' multiple selection field, or select grouping in 'Authorization Group' field and ensure that codes in group are selected in 'Service Codes' field. Select value for 'Require Authorization Number' and 'Select Authorization Item' fields. Click 'Update' button to save Authorization Requirement date/service code row entry. Ensure that Authorization Requirement date/service code row entry is displayed as entered/updated in the 'Authorization Group Information' display field. Repeat steps 8-11 above for additional Authorization Requirement date/service code row entries as desired. For Authorization Requirement date/service code row edit, select desired entry in the 'Select Authorization Item' field; make desired changes and click 'Update' button to save Authorization Requirement date/service code row update. For Authorization Requirement date/service code row deletion, select desired entry in the 'Select Authorization Item' field and click 'Delete' button. Navigate to main/first section of 'Guarantors/Payors' form. Click 'File' button to file Guarantor/Payor information, including Authorization Information/Authorization Requirement entries. Select 'Edit' option, and select Guarantor entered/defined above. Navigate to 'Authorization Information' section of 'Guarantors/Payors' form. Ensure all field values are present in Authorization Information section of 'Guarantors/Payors' form as previously entered/filed, including all Authorization Requirement date/service code entry row(s). Open Crystal Reports or other SQL reporting tool. In Avatar Cal-PM SQL table 'SYSTEM.billing_guar_table', ensure that entered/filed Guarantor information is present. In Avatar Cal-PM SQL table 'SYSTEM.billing_guar_auth_table', ensure that entered/filed Guarantor Authorization Requirement date/service code information is present. Scenario 4: 'Managed Care Authorizations' - Form Verification Specific Setup: Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' may optionally be enabled/disabled Crystal Reports or other SQL reporting tool Steps Open Avatar Cal-PM 'Managed Care Authorizations' form. Select client/episode for Managed Care Authorization entry/update/view. Navigate to 'Managed Care Authorization Data' section of form. Click 'Add New Item' button for Managed Care Authorization entry (or select existing Authorization/row and click 'Edit Selected Item' button). Ensure the following fields are present in the 'Payor Based Authorizations' form: 'Guarantor Number' / 'Guarantor Name' 'Authorization Start Date' 'Authorization End Date' 'Service Code' Multiple selection field (including 'All Service Codes' selection) 'Authorization Group' Available only where Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' is enabled Authorization Number' Not a required field where Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' is enabled 'Maximum Dollar Amount' / 'Maximum Units' / 'Maximum Visits' 'Practitioner Categories Necessary For Coverage' 'Type Of Authorization' 'U/R Staff Person' Select value in 'Guarantor Number' / 'Guarantor Name' field. Enter/select values in 'Authorization Start Date' and 'Authorization End Date' fields. Select one or more codes or 'All Service Codes' in 'Service Code' multiple selection field, or select grouping in 'Authorization Group' field and ensure that codes in group are selected in 'Service Codes' field (and limited to only codes specified for group). Enter value in 'Authorization Number' field if required/desired. Enter/select values for all other Managed Care Authorization fields as required/desired. Repeat steps 4-10 above for additional Managed Care Authorization record/row entries as desired. Click 'Submit' button to file 'Managed Care Authorizations' form/record(s). Re-open Avatar Cal-PM 'Managed Care Authorizations' form for same client/episode where Authorization information filed above. Navigate to 'Managed Care Authorization Data' section of form. Select existing Authorization/row and click 'Edit Selected Item' button Ensure all field values are present in 'Managed Care Authorizations' form/record as previously entered/filed. Open Crystal Reports or other SQL reporting tool. In Avatar Cal-PM SQL table 'SYSTEM.history_managed_care_auths', ensure that data row(s) are added/updated on filing of 'Managed Care Authorizations' form and contain values/information filed via form for all applicable fields (including 'Authorization Group' value where entered). Scenario 5: 'Client Charge Input' - Verification of Guarantor/Payor Level Authorization Requirements Specific Setup: Avatar Cal-PM Registry Setting 'Enable Payor Based Authorizations' must be enabled Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' must be enabled Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' may optionally be enabled/disabled One or more Guarantor(s) where values are selected/defined for 'Verify Services and Appointments Against Available Authorizations' and 'Verification Level For Authorizations For Client Charge Input' fields (via Avatar Cal-PM 'Guarantors/Payors' form, 'Authorization Information' section) Client record eligible for 'Client Charge Input' form service entry where applicable Guarantor(s) is/are assigned via client Financial Eligibility record for service liability distribution Steps Open Avatar Cal-PM 'Client Charge Input' form. Note, acceptance testing may also be confirmed via Avatar Cal-PM 'Client Charge Input (Charge Fee Access)', 'Client Charge Input With Diagnosis Entry', 'Client Charge Input (Charge Fee Access And Diagnosis Entry)', 'Recurring Client Charge Input', 'Recurring Client Charge Input (Charge Fee Access)', 'Recurring Client Charge Input With Diagnosis Entry' and/or 'Recurring Client Charge Input (Charge Fee Access And Diagnosis Entry)' forms Enter value for 'Date of Service'. Enter/select values for 'Client ID', 'Episode Number', 'Program', 'Service Code' and 'Practitioner' fields (and any other fields as desired/required). For service codes/dates of service not included/designated in Authorization requirements for applicable/liable Guarantor (via 'Guarantor/Payors' form, 'Authorization Information' section): In case where no Managed Care Authorization record exists for selected client applicable to service criteria/entry values and no Payor Based Authorization record exists in system applicable to service criteria/entry values - Ensure that user is not presented with Error/Warning message and Service entry is allowed without requirement for coverage by Managed Care Authorization/Payor Based Authorization record(s). For service codes/dates of service designated to require Authorization for applicable/liable Guarantor but where 'Require Authorization' field is set to 'No' (via 'Guarantor/Payors' form, 'Authorization Information' section): In case where no Managed Care Authorization record exists for selected client applicable to service criteria/entry values and no Payor Based Authorization record exists in system applicable to service criteria/entry values - Ensure that user is not presented with Error/Warning message and Service entry is allowed without requirement for coverage by Managed Care Authorization/Payor Based Authorization record(s). For service codes/dates of service designated to require Authorization for applicable/liable Guarantor and where 'Require Authorization' field is set to 'Yes' (via 'Guarantor/Payors' form, 'Authorization Information' section): In case where no Managed Care Authorization record exists for selected client applicable to service criteria/entry values and no Payor Based Authorization record exists in system applicable to service criteria/entry values - Ensure that user is presented with Error/Warning message noting 'No valid authorizations found on file.' In case where Managed Care Authorization record exists for selected client applicable to service criteria/entry values but is exhausted/cannot be used for additional services (due to Available Dollars/Available Units/Available Visits limitations), and no Payor Based Authorization record exists in system applicable to service criteria/entry values - Ensure that user is presented with Error/Warning message noting 'Authorization On File For Guarantor Will Be Exhausted With Requested Services.' In case where Managed Care Authorization record exists for selected client applicable to service criteria/entry values and is not exhausted/can be used for additional services - Ensure that user is not presented with Error/Warning message and Service entry is allowed due to coverage by Managed Care Authorization record(s). In case where no Managed Care Authorization record exists for selected client applicable to service criteria/entry values (or Managed Care Authorization record exists but is exhausted/cannot be used for additional services) but Payor Based Authorization record exists in system applicable to service criteria/entry values - Ensure that user is not presented with Error/Warning message and Service entry is allowed due to coverage by Payor Based Authorization record(s). Notes for service code/date of service Authorization requirements outlined above: If 'Require Authorization Number' field is set to 'Yes' for service code/date Authorization requirement (via 'Guarantor/Payors' form, 'Authorization Information' section), 'Authorization Number' value must also be filed/present for applicable Managed Care Authorization/Payor Based Authorization record for service entry to be allowed without error. For Managed Care Authorizations - Records/Authorizations applicable to 'Date Of Service' entry/value will be those where 'Date of Service' is on or after 'Authorization Start Date' and on or before 'Authorization End Date' (including records where 'Date of Service' is same as 'Authorization End Date'). For Payor Based Authorizations - Records/Authorizations applicable to 'Date Of Service' entry/value will be those where 'Date of Service' is on or after 'Effective Date' and before 'Expiration Date' (not including records where 'Date of Service' is same as 'Expiration Date'). If 'Expiration Date' is not defined, Payor Based Authorization will be considered applicable to all dates of service on/after 'Effective Date'. Service entry via 'Client Charge Input' forms may be disallowed or allowed following error/warning message, dependent on 'Verification Level For Authorizations For Client Charge Input' configuration for applicable Guarantor (via Avatar Cal-PM 'Guarantors/Payors' form, 'Authorization Information' section). Scenario 6: 'Scheduling Calendar' - Verification of Guarantor/Payor Level Authorization Requirements Specific Setup: Avatar Appointment Scheduling must be installed Avatar Cal-PM Registry Setting 'Enable Payor Based Authorizations' must be enabled Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' must be enabled Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' may optionally be enabled/disabled One or more Guarantor(s) where values are selected/defined for 'Verify Services and Appointments Against Available Authorizations' and 'Verification Level For Authorizations For Appointment Scheduling' fields (via Avatar Cal-PM 'Guarantors/Payors' form, 'Authorization Information' section) Client record eligible for Scheduling Calendar/Appointment Scheduling service entry where applicable Guarantor(s) is/are assigned via client Financial Eligibility record Steps Open Avatar Cal-PM 'Scheduling Calendar' form. Select date and Practitioner for Appointment Scheduling entry; right click and select 'Add Appointment' action. Enter/select values for 'Appointment Site', 'Appointment Date', 'Appointment Start Time', 'Duration', 'Appointment End Time', 'Service Code', 'Client' and 'Practitioner' fields. For service codes/dates of service (Appointment date) not included/designated in Authorization requirements for applicable/liable Guarantor (via 'Guarantor/Payors' form, 'Authorization Information' section): In case where no Managed Care Authorization record exists for selected client applicable to Appointment/service criteria values and no Payor Based Authorization record exists in system applicable to Appointment/service criteria - Ensure that user is not presented with Error/Warning message and Appointment/service entry is allowed without requirement for coverage by Managed Care Authorization/Payor Based Authorization record(s). For service codes/dates of service ('Appointment Date') designated to require Authorization for applicable/liable Guarantor but where 'Require Authorization' field is set to 'No' (via 'Guarantor/Payors' form, 'Authorization Information' section): In case where no Managed Care Authorization record exists for selected client applicable to Appointment/service criteria and no Payor Based Authorization record exists in system applicable to Appointment/service criteria- Ensure that user is not presented with Error/Warning message and Appointment/service entry is allowed without requirement for coverage by Managed Care Authorization/Payor Based Authorization record(s). For service codes/dates of service (Appointment Date) designated to require Authorization for applicable/liable Guarantor and where 'Require Authorization' field is set to 'Yes' (via 'Guarantor/Payors' form, 'Authorization Information' section): In case where no Managed Care Authorization record exists for selected client applicable to Appointment/service criteria and no Payor Based Authorization record exists in system applicable to Appointment/service criteria - Ensure that user is presented with Error/Warning message noting 'No valid authorizations found on file.' In case where Managed Care Authorization record exists for selected client applicable to Appointment/service criteria but is exhausted/cannot be used for additional services (due to Available Dollars/Available Units/Available Visits limitations), and no Payor Based Authorization record exists in system applicable to Appointment/service criteria - Ensure that user is presented with Error/Warning message noting 'Authorization On File For Guarantor Will Be Exhausted With Requested Services.' In case where Managed Care Authorization record exists for selected client applicable to Appointment/service criteria and is not exhausted/can be used for additional services - Ensure that user is not presented with Error/Warning message and Service entry is allowed due to coverage by Managed Care Authorization record(s). In case where no Managed Care Authorization record exists for selected client applicable to Appointment/service criteria (or Managed Care Authorization record exists but is exhausted/cannot be used for additional services) but Payor Based Authorization record exists in system applicable to Appointment/service criteria - Ensure that user is not presented with Error/Warning message and Appointment/service entry is allowed due to coverage by Payor Based Authorization record(s). Notes for service code/Appointment Date Authorization requirements outlined above: If 'Require Authorization Number' field is set to 'Yes' for service code/date Authorization requirement (via 'Guarantor/Payors' form, 'Authorization Information' section), 'Authorization Number' value must also be filed/present for applicable Managed Care Authorization/Payor Based Authorization record for Appointment/service entry to be allowed without error. For Managed Care Authorizations - Records/Authorizations applicable to 'Appointment Date' entry/value will be those where 'Appointment Date' is on or after 'Authorization Start Date' and on or before 'Authorization End Date' (including records where 'Appointment Date' is same as 'Authorization End Date'). For Payor Based Authorizations - Records/Authorizations applicable to 'Appointment Date' entry/value will be those where 'Appointment Date' is on or after 'Effective Date' and before 'Expiration Date' (not including records where 'Appointment Date' is same as 'Expiration Date'). If 'Expiration Date' is not defined, Payor Based Authorization will be considered applicable to all dates of service/Appointment dates on/after 'Effective Date'. Appointment/service entry via 'Scheduling Calendar' form may be disallowed or allowed following error/warning message, dependent on 'Verification Level For Authorizations For Appointment Scheduling' configuration for applicable Guarantor (via Avatar Cal-PM 'Guarantors/Payors' form, 'Authorization Information' section). Scenario 7: 'Electronic Billing' - Verification of Guarantor/Payor Level Authorization Requirements Specific Setup: Avatar Cal-PM Registry Setting 'Enable Payor Based Authorizations' must be enabled Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' must be enabled Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' may optionally be enabled/disabled One or more Guarantor(s) where values are selected/defined for 'Verify Services and Appointments Against Available Authorizations' and 'Verification Level For Authorizations For 837 Electronic Billing' fields (via Avatar Cal-PM 'Guarantors/Payors' form, 'Authorization Information' section) 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 Open Avatar Cal-PM 'Electronic Billing' form. Note, acceptance testing may also be confirmed via Avatar Cal-PM 'Quick Billing' form/functionality. Select '837 Professional' or '837 Institutional' in the 'Billing Form' field. Select 'Sort File' in the 'Billing Options' field. Enter/select 837 Professional/837 Institutional file sorting criteria. Click 'Process' button to sort/generate 837 Professional/837 Institutional file. Select 'Run Report' in the 'Billing Options' field. Select 'Print' in the 'Print Or Delete Report' field. Select 837 Professional/837 Institutional file sorted which includes services(s), and click 'Process' button to display 837 Professional/837 Institutional outbound file report. For service codes/dates of service not included/designated in Authorization requirements for selected 837 Guarantor (via 'Guarantor/Payors' form, 'Authorization Information' section): In Avatar Cal-PM 837 Professional/837 Institutional format outbound electronic billing file report - In case where no Managed Care Authorization or Payor Based Authorization record exists for client/service(s) to be included in 837 file, ensure that Authorization-related error is not reported/included for service(s) in 'Required Data Missing: Patient Service Data' (837 Professional) or 'Required Data Missing: Patient Claim Data' (837 Institutional) section of report, and service(s) is/are included in 837 file information without requirement for coverage by Managed Care Authorization/Payor Based Authorization record(s) (subject to all other 837 sorting criteria/requirements). For service codes/dates of service designated to require Authorization for selected 837 Guarantor but where 'Require Authorization' field is set to 'No' (via 'Guarantor/Payors' form, 'Authorization Information' section): In Avatar Cal-PM 837 Professional/837 Institutional format outbound electronic billing file report - In case where no Managed Care Authorization or Payor Based Authorization record exists for client/service(s) to be included in 837 file, ensure that Authorization-related error is not reported/included for service(s) in 'Required Data Missing: Patient Service Data' or 'Required Data Missing: Patient Claim Data' section of report, and service(s) is/are included in 837 file information without requirement for coverage by Managed Care Authorization/Payor Based Authorization record(s) (subject to all other 837 sorting criteria/requirements). For service codes/dates of service designated to require Authorization for selected 837 Guarantor and where 'Require Authorization' field is set to 'Yes' (via 'Guarantor/Payors' form, 'Authorization Information' section): In Avatar Cal-PM 837 Professional/837 Institutional format outbound electronic billing file report - In case where no Managed Care Authorization record exists for client/service(s) to be included in 837 file and no Payor Based Authorization record exists for service(s) to be included in 837 file, ensure that error is reported/included for service(s) in 'Required Data Missing: Patient Service Data' or 'Required Data Missing: Patient Claim Data' section of report. In Avatar Cal-PM 837 Professional/837 Institutional format outbound electronic billing file report - In case where Managed Care Authorization record exists for client/service(s) to be included in 837 file but is exhausted/cannot be used for services (due to Available Dollars/Available Units/Available Visits limitations) and no Payor Based Authorization record exists for service(s) to be included in 837 file, ensure that error is reported/included for service(s) in 'Required Data Missing: Patient Service Data' or 'Required Data Missing: Patient Claim Data' section of report. In Avatar Cal-PM 837 Professional/837 Institutional format outbound electronic billing file report - In case where Managed Care Authorization record exists for client/service(s) to be included in 837 file and is not exhausted/can be used for services, ensure that Authorization-related error is not reported/included for service(s) in 'Required Data Missing: Patient Service Data' or 'Required Data Missing: Patient Claim Data' section of report, and service(s) is/are included in 837 file information due to coverage by Managed Care Authorization record(s) (subject to all other 837 sorting criteria/requirements). In Avatar Cal-PM 837 Professional/837 Institutional format outbound electronic billing file report - In case where no Managed Care Authorization record exists for client/service(s) to be included in 837 file but Payor Based Authorization record exists for service(s) to be included in 837 file, ensure that Authorization-related error is not reported/included for service(s) in 'Required Data Missing: Patient Service Data' or 'Required Data Missing: Patient Claim Data' section of report, and service(s) is/are included in 837 file information due to coverage by Payor Based Authorization record(s) (subject to all other 837 sorting criteria/requirements). Notes for service code/date of service Authorization requirements outlined above: 837 File Report Error Message Examples: 'Authorizations On File For Guarantor Are Exhausted For Service Code: (CODE INFO) On Service Date: (DATE)' 'Service Code (CODE) Is Missing An Authorization Number For Guarantor (GUARANTOR) For Date Of Service (DATE). No More Claims Processing Will Be Done For The Episode' Service(s) may be excluded or included in 837 Professional/837 Institutional file where error is present, dependent on 'Verification Level For Authorizations For 837 Electronic Billing' configuration for applicable Guarantor (via Avatar Cal-PM 'Guarantors/Payors' form, 'Authorization Information' section). Scenario 8: 'Payor Based Authorizations' - Form Verification Specific Setup: Avatar Cal-PM Registry Setting 'Enable Payor Based Authorizations' must be enabled Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' may optionally be enabled/disabled Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' may optionally be enabled/disabled Crystal Reports or other SQL reporting tool Steps Open Avatar Cal-PM 'Payor Based Authorizations' form (under 'Avatar PM / System Maintenance / System Definition' menu). 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). Ensure the following fields are present in the 'Payor Based Authorizations' form: 'Guarantor' 'Program' Available only where Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' is enabled 'Practitioner Category' Available only where Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' is enabled 'Effective Date' 'Expiration Date' Not a required field where Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' is enabled 'Authorization Number' 'Service Code' / 'Service Code(s)' Not available where Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' is enabled 'Service Code' is a single code search/select field where Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' is disabled 'Service Code(s)' is a multiple selection field (including 'All Service Codes' selection) where Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' is enabled 'Authorization Group' Available only where Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' is enabled 'Select CPT ® Codes' button Available only where Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' is enabled 'All CPT Codes' Available only where Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' is enabled 'Display Authorizations' button 'Select Authorizations To Edit/Delete' button Enter/select values in 'Effective Date' and 'Expiration Date' fields. Where Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' is enabled - select one or more values in 'Program' and/or 'Practitioner Category' multiple selection fields if desired. Where Avatar Cal-PM Registry Setting 'Require Authorizations At Guarantors/Payors Level' is enabled - select one or more codes or 'All Service Codes' in 'Service Code(s)' multiple selection field, or select grouping in 'Authorization Group' field and ensure that codes in group are selected in 'Service Codes' field (and limited to only codes specified for group). 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'). Enter 'Authorization Number' field value. Click 'Submit' button to file 'Payor Based Authorizations' form/record. 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. Ensure all field values are present in 'Payor Based Authorizations' form/record as previously entered/filed. Click 'Display Authorizations' button to display the Payor Based Authorizations report/information. 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: 'Guarantor' 'Service Code' or 'CPT Code' Dependent on Avatar Cal-PM Registry Setting 'Enable CPT Based Payor Authorizations' 'Program' 'Practitioner Category' 'Effective Date' Expiration Date' 'Authorization Number' Open Crystal Reports or other SQL reporting tool. 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 (including 'Program' and 'Practitioner Category' values where entered). 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 (including 'Program' and 'Practitioner Category' values where entered).	Topics • Service Authorizations • Registry Settings • NX • Guarantor • Client Charge Input • Scheduling Calendar • Electronic Billing
Update 78 Summary \| Details System Task Scheduler Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Family Registration (CAL) Financial Eligibility System Task Scheduler Scenario 1: System Task Scheduler - Close Charges/Update Liability - Client Ledger Specific Setup: Family Registration: Select an existing registration or create a new registration with at least two clients. Note the client IDs. Validate that all clients have an active Financial Eligibility record. Client Charge Input: Enter a service for each client. System Task Scheduler: Schedule the ‘Close Charges/Update Liability’ for the current date and a few minutes in the future. Note the time the process will begin. Wait for the ‘System Task Scheduler’ task to complete. Steps Open ‘Client Ledger’ for a client in the ‘Family Registration’. Select ‘Simple’ in ‘Ledger Type’. Click [Process]. Validate that the service is closed, and the ‘Claim Number’ columns displays ‘UNBILL’. Close the report. Close the form.	Topics • System Task Scheduler • NX • Client Ledger
Update 81 Summary \| Details 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: Financial Eligibility Guarantors/Payors Managed Care Authorizations Scenario 1: Client Charge Input - Validate error message when authorizations are required Specific Setup: A guarantor is defined that requires authorizations and will disallow service if missing (Guarantor A). A client has "Guarantor A" selected as their guarantor in 'Financial Eligibility' (Client A). "Client A" does not have any valid authorizations on file in 'Managed Care Authorization'. Steps Access the 'Client Charge Input' form. Enter the current date in the 'Date Of Service' field. Select "Client A" in the 'Client ID' field. Select the desired value in the 'Service Code' field. Select the desired practitioner in the 'Practitioner' field. Validate an error message is displayed stating: No valid authorizations found on file. Click [OK] and close the form. Scenario 2: Client Charge Input - Validate warning message when authorizations are required Specific Setup: A guarantor is defined that requires authorizations and will warn if missing (Guarantor A). A client has "Guarantor A" selected as their guarantor in 'Financial Eligibility' (Client A). "Client A" does not have any valid authorizations on file in 'Managed Care Authorization'. Steps Access the 'Client Charge Input' form. Enter the current date in the 'Date Of Service' field. Select "Client A" in the 'Client ID' field. Select the desired value in the 'Service Code' field. Select the desired practitioner in the 'Practitioner' field. Validate a warning message is displayed stating: No valid authorizations found on file. Click [OK] and [Submit]. Please note: since this is just a warning, the user can proceed without authorization, if desired. Access the 'Client Ledger' form. Select "Client A" in the 'Client ID' field. Select "All Episodes" in the 'Claim/Episode/All Episodes' field. Select "Simple" in the 'Ledger Type' field. Select "Yes" in the 'Include Zero Charges' field. Click [Process]. Validate the report contains the service filed in the previous steps. Close the report and the form.	Topics • Client Charge Input • Client Ledger • Managed Care Authorizations
Update 84 Summary \| Details Diagnosis - 'Problem Classification' field Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Dictionary Update (CWS) Scenario 1: Diagnosis - Add new / Add to Problem List Specific Setup: A client must be enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Diagnosis' form. Click [Add] if present. Select any value for the 'Type of Diagnosis' field. Enter the desired values for the 'Date of Diagnosis' and 'Time of Diagnosis' fields. Click [New Row]. Enter any value in the 'Diagnosis Search' field and press the 'Enter' key. Validate "Powered By IMO Terminology" displays under the search results. Select a diagnosis that has an associated SNOMED code. Populate any desired and required fields. Select "Yes" in the 'Add to Problem List' field. Submit the form. Access the 'Problem List' form. Click [Enter Problems]. Validate the new diagnosis is included. Click [View - DSM/IDC Code]. Validate a dialog opens with the DSM/IDC code data for the problem. Close out of the dialog. Click [View - System Notes]. Validate the dialog displays the user information for the problem. Close out of the dialog. Click [Close/Cancel]. Close the form. Scenario 2: Diagnosis - Add new / Add to Problem List Specific Setup: A client must be enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Diagnosis' form. Click [Add] if present. Select any value for the 'Type of Diagnosis' field. Enter the desired values for the 'Date of Diagnosis' and 'Time of Diagnosis' fields. Click [New Row]. Enter any value in the 'Diagnosis Search' field and press the 'Enter' key. Validate "Powered By IMO Terminology" displays under the search results. Select a diagnosis that has an associated SNOMED code. Populate any desired and required fields. Select "Yes" in the 'Add to Problem List' field. Submit the form. Access the 'Problem List' form. Click [Enter Problems]. Validate the new diagnosis is included. Click [View - DSM/IDC Code]. Validate a dialog opens with the DSM/IDC code data for the problem. Close out of the dialog. Click [View - System Notes]. Validate the dialog displays the user information for the problem. Close out of the dialog. Click [Close/Cancel]. Close the form. Scenario 3: 'Diagnosis' form 'Problem Classification' field validation when defaulting diagnosis from a previous episode Specific Setup: The 'Avatar CWS->Problem List->->->->Problem Classification Required' registry setting is set to "Y". A new code has been added to the Avatar CWS 'Dictionary Update' file 'Problem Classification'. This is in field 16250. Steps Access the 'Diagnosis' form for any client. Add a new diagnosis for the client. Note the episode selected as it will be used in later steps. Complete required fields as needed. Select 'Y' in the 'Add to Problem List' field. Do not populate the 'Problem Classification' field at this time. Click [Submit]. Access the 'Diagnosis' form again for the same client. Select 'Add' on the pre-display. Do not select the existing diagnosis. Select the episode used in the above steps in the 'Select Episode To Default Diagnosis Information From' field. Select the diagnosis entered in the above steps in the 'Select Diagnosis To Default Information From' field. Click on the existing diagnosis row to populate the detail fields. Click on the 'Problem Classification' field. Verify that all codes for selection display in the drop down list, including the newly added code (see Setup section). Select a code from the drop down list. Click [Submit] and close the form.	Topics • Diagnosis • Problem List
Update 85 Summary \| Details Avatar Cal-PM is updated to capture additional information Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Practitioner Enrollment Scenario 1: 'Facility Defaults' form - field validations Steps Access the 'Facility Defaults' form. Populate any desired fields. Click [Submit]. Access Crystal Reports or other SQL Reporting tool. Create a report using the 'SYSTEM.table_facility_defaults' SQL table. Validate a row is displayed for the data on file. Validate the following audit fields are displayed and are populated accordingly: data_entry_by data_entry_by_option data_entry_date data_entry_time data_entry_user_id data_entry_user_name option_id option_desc The following audit fields will only be populated in a UTC enabled system: data_entry_utc data_entry_timezone_info_all data_entry_time_j data_entry_offset data_entry_timezone_short Close the report. Scenario 2: 'ClinicianServicesV2' Web Service - Verification Of 'putClinicianCreation' Filing Steps 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 a value for the 'ClinicianOfficeAddressDate' field/segment. Confirm the 'ClinicianServicesV2' web service responds with confirmation data on successful filing of 'putClinicianCreation' method. Example: "<Confirmation>Practitioner ID:000017\|\|\|\|First Name:FIRSTNAME\|\|Last Name:LASTNAME\|\|Registration Date:01/01/2022\|\|NPI:123456789</Confirmation>" Confirm the 'ClinicianServicesV2' web service responds with confirmation message on successful filing of 'putClinicianCreation' method. Example: "<Message>Clinician Services web service has been filed successfully.</Message>" Confirm the 'ClinicianServicesV2' web service responds with successful status value on successful filing of 'putClinicianCreation' method. Example: " <Status>1</Status>" Access the 'Practitioner Enrollment' form and select the 'Practitioner Enrollment' record filed via web service for view/update. Confirm new 'Practitioner Enrollment' record is created with values/data submitted via web service including the 'Office Address - Start Date' field value (as well as values assigned for Avatar MSO 'Performing Provider' and 'Performing Provider Registration' practitioner association/link fields if enabled). Scenario 3: 'ClinicianServicesV2' Web Service - Verification Of 'putClinicianUpdate' Filing Steps 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 a value for the 'ClinicianOfficeAddressDate' field/segment. Confirm the 'ClinicianServicesV2' web service responds with confirmation data on successful filing of 'putClinicianUpdate' method. Example: "<Confirmation>Practitioner ID:000017\|\|\|\|First Name:FIRSTNAME\|\|Last Name:LASTNAME\|\|Registration Date:01/01/2022\|\|NPI:123456789</Confirmation>" Confirm the 'ClinicianServicesV2' web service responds with confirmation message on successful filing of 'putClinicianUpdate' method. Example: "<Message>Clinician Services web service has been filed successfully.</Message>" Confirm the 'ClinicianServicesV2' web service responds with successful status value on successful filing of 'putClinicianUpdate' method. Example: " <Status>1</Status>" Access the 'Practitioner Enrollment' form and select the 'Practitioner Enrollment' record filed via web service for view/update. Confirm the 'Practitioner Enrollment' record is updated with values/data submitted via web service including the 'Office Address - Start Date' field value. Scenario 4: 'Practitioner Enrollment' - Form Verification Specific Setup: Crystal Reports or other SQL Reporting Tool. Steps Access the 'Practitioner Enrollment' form. Select any existing practitioner for view/update. Validate the 'Office Address - Start Date' field is displayed. Enter any value in the 'Office Address - Start Date' field. Populate any other required and desired fields. Click [Submit]. Access the 'Practitioner Enrollment' form. Select the same practitioner from the previous steps. Validate the 'Office Address - Start Date' field contains the value filed in the previous steps. Validate any other previously field data is displayed. Close the form. Access Crystal Reports or other SQL Reporting Tool. Create a report using the 'SYSTEM.staff_enrollment_history' SQL table. Navigate to the row for the practitioner used in the previous steps. Validate the 'office_add_date' field contains the value field in the previous steps. Close the report. Create a report using the 'SYSTEM.staff_current_demographics' SQL table. Navigate to the row for the practitioner used in the previous steps. Validate the 'office_add_date' field contains the value field in the previous steps. Close the report. Scenario 5: Dictionary Update - Validate the 'Treatment Service' dictionary Steps Access the 'Dictionary Update' form. Select "Client" in the 'File' field. Select "(101) Treatment Service" in the 'Data Element' field. Enter an existing code in the 'Dictionary Code' field. Validate the 'Dictionary Value' field populates accordingly. Validate the 'Extended Dictionary Data Element' field contains "(742) Encounter Code (FHIR)". Select "(742) Encounter Code (FHIR)" in the 'Extended Dictionary Data Element' field. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field. Click [Apply Changes]. Validate a message is displayed stating: Filed! Click [OK]. Select the "Print Dictionary" section. Select "Client" in the 'File' field. Select "Individual Data Element" in the 'Individual or All Data Elements' field. Select "(101) Treatment Service" in the 'Data Element' field. Click [Print Dictionary]. Validate the report displays the updated dictionary with the "Encounter Code (FHIR)" extended dictionary value populated. Close the report and the form.	Topics • Facility Defaults • Query/Reporting • Web Services • Practitioner • Dictionary
Update 86 Summary \| Details Dictionary Update - 'Pregnancy Status' dictionary Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: Women's Health History CareFabric Monitor Scenario 1: Women's Health History - Validate the 'PregnancyCreated' and 'PregnancyUpdated' SDK events Specific Setup: The following extended dictionaries must be defined for the "(357) Pregnancy Status" PM dictionary values: (70492) Clinical Status - Pregnancy (FHIR) (70493) Verification Status (FHIR) A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Women's Health History' form. Enter the desired date in the 'Assessment Date' field. Enter the desired date in the 'Pregnancy Start Date' field. Select the desired value in the 'Pregnant Status' field. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "PregnancyCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'clinicalStatusCode' - code' field contains the "Clinical Status - Pregnancy (FHIR)" extended dictionary code defined for the status selected. Validate the 'clinicalStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.164". Validate the 'clinicalStatusCode' - 'codeSystemName' field contains "Condition-Clinical". Validate the 'clinicalStatusCode' - 'displayName' field contains the "Clinical Status - Pregnancy (FHIR)" extended dictionary value defined for the status selected. Validate the 'verificationStatusCode' - code' field contains the "Verification Status (FHIR)" extended dictionary code defined for the status selected. Validate the 'verificationStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.166". Validate the 'verificationStatusCode' - 'codeSystemName' field contains "Condition-Ver-Status". Validate the 'verificationStatusCode' - 'displayName' field contains the "Verification Status (FHIR)" extended dictionary value defined for the status selected. Close the report and the form. Select "Client A" and access the 'Women's Health History' form. Select the record filed in the previous steps and click [Edit]. Enter the desired value in the 'Pregnancy End Date' field. Select any new value in the 'Pregnant Status' field. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "PregnancyUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'clinicalStatusCode' - code' field contains the "Clinical Status - Pregnancy (FHIR)" extended dictionary code defined for the status selected. Validate the 'clinicalStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.164". Validate the 'clinicalStatusCode' - 'codeSystemName' field contains "Condition-Clinical". Validate the 'clinicalStatusCode' - 'displayName' field contains the "Clinical Status - Pregnancy (FHIR)" extended dictionary value defined for the status selected. Validate the 'endDate' field contains the 'Pregnancy End Date'. Validate the 'startDate' field contains the 'Pregnancy Start Date'. Validate the 'verificationStatusCode' - code' field contains the "Verification Status (FHIR)" extended dictionary code defined for the status selected. Validate the 'verificationStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.166". Validate the 'verificationStatusCode' - 'codeSystemName' field contains "Condition-Ver-Status". Validate the 'verificationStatusCode' - 'displayName' field contains the "Verification Status (FHIR)" extended dictionary value defined for the status selected. Close the report and the form. Scenario 2: Dictionary Update - Validate the 'Pregnancy Status' dictionary Steps Access the 'Dictionary Update' form. Select "Client" in the 'File' field. Select "(357) Pregnancy Status" in the 'Data Element' field. Enter an existing code in the 'Dictionary Code' field. Validate the 'Dictionary Value' field populates accordingly. Validate the 'Extended Dictionary Data Element' field contains the following: "(70492) Clinical Status - Pregnancy (FHIR)" "(70493) Verification Status (FHIR)" Select "(70492) Clinical Status - Pregnancy (FHIR)" in the 'Extended Dictionary Data Element' field. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field. Select "(70493) Verification Status (FHIR)" in the 'Extended Dictionary Data Element' field. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field. Click [Apply Changes]. Validate a message is displayed stating: Filed! Click [OK]. Select the "Print Dictionary" section. Select "Client" in the 'File' field. Select "Individual Data Element" in the 'Individual or All Data Elements' field. Select "(357) Pregnancy Status" in the 'Data Element' field. Click [Print Dictionary]. Validate the report displays the updated dictionary with the "(70492) Clinical Status - Pregnancy (FHIR)" and "(70493) Verification Status (FHIR)" extended dictionary values populated. Close the report and the form. Dictionary Update - 'Diagnosis Status' dictionary Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following: CareFabric Monitor Scenario 1: Dictionary Update - Validate the 'Diagnosis Status' dictionary Steps Access the 'Dictionary Update' form. Select "Client" in the 'File' field. Select "(1800) Status" in the 'Data Element' field. Enter an existing code in the 'Dictionary Code' field. Validate the 'Dictionary Value' field populates accordingly. Validate the 'Extended Dictionary Data Element' field contains the following: "(70494) Clinical Status - Diagnosis (FHIR)" "(70493) Verification Status (FHIR)" Select "(70494) Clinical Status - Diagnosis (FHIR)" in the 'Extended Dictionary Data Element' field. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field. Select "(70493) Verification Status (FHIR)" in the 'Extended Dictionary Data Element' field. Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field. Click [Apply Changes]. Validate a message is displayed stating: Filed! Click [OK]. Select the "Print Dictionary" section. Select "Client" in the 'File' field. Select "Individual Data Element" in the 'Individual or All Data Elements' field. Select "(357) Pregnancy Status" in the 'Data Element' field. Click [Print Dictionary]. Validate the report displays the updated dictionary with the "(70494) Clinical Status - Diagnosis (FHIR)" and "(70493) Verification Status (FHIR)" extended dictionary values populated. Close the report and the form. Scenario 2: Diagnosis - Validate the 'DiagnosisCreated' and 'DiagnosisUpdated' SDK events Specific Setup: The following extended dictionaries must be defined for the "(1800) Status" PM dictionary values for 'Diagnosis Status': (70494) Clinical Status - Diagnosis (FHIR) (70493) Verification Status (FHIR) A client is enrolled in an existing episode (Client A). Steps Select "Client A" and access the 'Diagnosis' form. Select the desired value in the 'Type Of Diagnosis' field. Enter the desired date in the 'Date Of Diagnosis' field. Enter the desired time in the 'Time Of Diagnosis' field. Click [New Row]. Select the desired value in the 'Diagnosis Search' field. Select "Active" in the 'Status' field. Select the desired practitioner in the 'Diagnosing Practitioner' field. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "DiagnosisCreated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'clinicalStatusCode' - code' field contains the "Clinical Status - Diagnosis (FHIR)" extended dictionary code defined for the status selected. Validate the 'clinicalStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.164". Validate the 'clinicalStatusCode' - 'codeSystemName' field contains "Condition-Clinical". Validate the 'clinicalStatusCode' - 'displayName' field contains the "Clinical Status - Diagnosis (FHIR)" extended dictionary value defined for the status selected. Validate the 'programAdmissionID' - 'id' field contains the program admission ID for "Client A". Validate the 'programCode' - 'code' field contains the program code "Client A" is enrolled in. Validate the 'programCode' - 'displayName' field contains the program name "Client A" is enrolled in. Validate the 'statusCode' - 'code' field contains "1". Validate the 'statusCode' - 'displayName' field contains "Active". Validate the 'verificationStatusCode' - code' field contains the "Verification Status (FHIR)" extended dictionary code defined for the status selected. Validate the 'verificationStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.166". Validate the 'verificationStatusCode' - 'codeSystemName' field contains "Condition-Ver-Status". Validate the 'verificationStatusCode' - 'displayName' field contains the "Verification Status (FHIR)" extended dictionary value defined for the status selected. Close the report and the form. Select "Client A" and access the 'Diagnosis' form. Select the diagnosis record filed in the previous steps and click [Edit]. Select "Resolved" in the 'Status' field. Enter the desired date in the 'Resolved Date' field. Click [Submit]. Access the 'CareFabric Monitor' form. Enter the current date in the 'From Date' and 'Through Date' fields. Select "Client A" in the 'Client ID' field. Select "DiagnosisUpdated" in the 'Event/Action Search' field. Click [View Activity Log]. Validate the 'clinicalStatusCode' - code' field contains the "Clinical Status - Diagnosis (FHIR)" extended dictionary code defined for the status selected. Validate the 'clinicalStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.164". Validate the 'clinicalStatusCode' - 'codeSystemName' field contains "Condition-Clinical". Validate the 'clinicalStatusCode' - 'displayName' field contains the "Clinical Status - Diagnosis (FHIR)" extended dictionary value defined for the status selected. Validate the 'programAdmissionID' - 'id' field contains the program admission ID for "Client A". Validate the 'programCode' - 'code' field contains the program code "Client A" is enrolled in. Validate the 'programCode' - 'displayName' field contains the program name "Client A" is enrolled in. Validate the 'statusCode' - 'code' field contains "4". Validate the 'statusCode' - 'displayName' field contains "Resolved". Validate the 'verificationStatusCode' - code' field contains the "Verification Status (FHIR)" extended dictionary code defined for the status selected. Validate the 'verificationStatusCode' - 'codeSystem' field contains "2.16.840.1.113883.4.642.3.166". Validate the 'verificationStatusCode' - 'codeSystemName' field contains "Condition-Ver-Status". Validate the 'verificationStatusCode' - 'displayName' field contains the "Verification Status (FHIR)" extended dictionary value defined for the status selected. Close the report and the form.	Topics • CareFabric • Women's Health History • Dictionary • Diagnosis • CareFabric Monitor
Update 89 Summary \| Details Facility Defaults - 'Provider Country' field Scenario 1: Validate the 'GetOrganization' payload Steps Internal testing only. Scenario 2: 'Facility Defaults' form - field validations Steps Access the 'Facility Defaults' form. Populate any desired fields. Validate the 'Provider Country' field is displayed. Select the desired value in the 'Provider Country' field. Note: this field is populated based off the dictionary values under the 'Client' file, '(150) Country Of Origin' data element in 'Dictionary Update'. Click [Submit]. Access Crystal Reports or other SQL Reporting tool. Create a report using the 'SYSTEM.table_facility_defaults' SQL table. Validate a row is displayed for the data on file. Validate the 'provider_country_code' field contains the code associated to the 'Provider Country' selected. Validate the 'provider_country_value' field contains the value associated to the 'Provider Country' selected. Close the report.	Topics • Facility Defaults • Query/Reporting