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
• Disclosure
• NX
• Site Specific Section Modeling
|
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
• Cal-OMS
• Web Services
|
'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
- Registry Settings (PM)
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:
- DTP*434*RD8*20221001-20221004~
- DTP*434*D8*20221001~
- 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:
- DTP*434*RD8*20221002-20221002~
|
Topics
• Electronic Billing
|
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)
- Admission (Outpatient)
- 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
• Admission (Outpatient)
• Pre Admit
• Update Client Data
• Web Services
|
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:
- Program Maintenance
- Guarantors/Payors
- Admission (Outpatient)
- 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:
- Registry Settings (PM)
- Dictionary Update (PM)
- Admission (Outpatient)
- 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
|
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
• CareConnect HIE Configuration
• Query for External CCD
|
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
- Authorization Warning
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
|
| |