Avatar PM 'Benefit Enrollment and Maintenance (834)'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Benefit Enrollment and Maintenance (834)
- Benefit Enrollment and Maintenance (834) Compile/Post Report
Scenario 1: 'Benefit Enrollment and Maintenance (834)' - Verification of Effective Date/Expiration Date Information
Specific Setup:
- Avatar PM Registry Setting 'Enable 834 Transaction Set' must be enabled
- 'Default Benefit Effective Date (2300-DTP-03)' and/or 'Default Expiration Date (2300-DTP-03)' values may optionally be defined (via Avatar PM 'Guarantors/Payors' form '270 / 271 / 834' section)
- 834 Benefit Enrollment Maintenance eligibility file for loading/compilation/posting in Avatar PM system, including one or more valid health coverage details
- Crystal Reports or other SQL reporting tool
Steps
- Open Avatar PM 'Benefit Enrollment and Maintenance (834)' form.
- Select 'Load File' in 'Options' field, and enter 'File Path/Name' value for 834 file to be loaded - selecting inbound 834 file including one or valid more health coverage details.
- Select 'Compile File' in 'Options' field, and select loaded 834 file for compilation.
- Click 'Process File' button to compile inbound 834 file data.
- Select 'Run Report' in 'Options' field, and select compiled 834 file for report.
- Click 'Process File' button to open 834 inbound compile report.
- In 834 inbound compile report - ensure that in case where 2300-DTP Effective Date is included without 2300-DTP Expiration Date in health coverage detail and previously posted 834 coverage information for same Unique ID/Policy Number and Coverage Expiration Date exist in Avatar PM (existing information in SQL table 'SYSTEM.eligibility_dependent_cov'), inbound 834 health care coverage entry is successfully compiled.
- Note - 'Coverage Expiration Date' values may also be determined by Avatar PM Guarantor/Payor in cases where not directly present in 834 file health coverage information (via 'Default Expiration Date (2300-DTP-03)' field in Avatar PM 'Guarantors/Payors' form, '270 / 271 / 834' section); In case where 'Default Expiration Date (2300-DTP-03)' is defined and 2300-DTP Expiration Date is not included in 834 file health coverage information, ensure that inbound 834 health care coverage entry is successfully compiled with default 'Coverage Expiration Date' value.
- In 834 inbound compile report - ensure that in case where 2300-DTP Expiration Date is included without 2300-DTP Effective Date in health coverage detail and previously posted 834 coverage information for same Unique ID/Policy Number and Coverage Expiration Date exist in Avatar PM (existing information in SQL table 'SYSTEM.eligibility_dependent_cov'), inbound 834 health care coverage entry is successfully compiled.
- Note - 'Coverage Effective Date' values may also be determined by Avatar PM Guarantor/Payor in cases where not directly present in 834 file health coverage information (via 'Default Benefit Effective Date (2300-DTP-03)' field in Avatar PM 'Guarantors/Payors' form, '270 / 271 / 834' section); In case where 'Default Benefit Effective Date (2300-DTP-03)' is defined and 2300-DTP Effective Date is not included in 834 file health coverage information, ensure that inbound 834 health care coverage entry is successfully compiled with default 'Coverage Effective Date' value.
- In 834 inbound compile report - ensure that in case where 2300-DTP Effective Date and 2300-DTP Expiration Date are included for same Unique ID/Policy Number under separate/different 2000 loop sets, inbound 834 health care coverage entry is successfully compiled (using 2300-DTP Effective Date and 2300-DTP Expiration Date values from file where present).
- Select 'Post File' in 'Options' field, and select compiled 834 file for posting.
- Click 'Process File' button to post inbound 834 file data.
- Open Crystal Reports or other SQL reporting tool.
- In Avatar PM SQL table 'SYSTEM.eligibility_dependent_cov', ensure that 'eligibility_eff_date' and 'eligibility_exp_date' values from 834 file health coverage information (or defaulted by Avatar PM system per Guarantor configurations) are present for eligibility data row(s) created via 834 inbound file posting; For client/834 coverage information where previous coverage information existed in SQL table 'SYSTEM.eligibility_dependent_cov' prior to latest 834 file posting, ensure that 'eligibility_eff_date' and 'eligibility_exp_date' values are updated according to new/latest 834 file health coverage information where applicable.
|
Topics
• Benefit Enrollment and Maintenance (834)
|
Diagnosis - Chart View
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Practitioner Enrollment
- Progress Notes (Group and Individual)
- Ambulatory Progress Notes
Scenario 1: Diagnosis - Validate display of Practitioner Credentials in the Chart View
Specific Setup:
- A client is enrolled in an existing episode (Client A).
- A practitioner is defined in 'Practitioner Enrollment' with the following (Practitioner A):
- 'Category/Taxonomy' Row 1:
- 'Effective Date' of "01/01/2022".
- 'End Date' of "10/01/2023".
- Practitioner Credential of "Administrator".
- 'Category/Taxonomy' Row 2:
- 'Effective Date' of "10/02/2023"
- No 'End Date' on file.
- Practitioner Credential of "Medical Doctor".
- The 'Diagnosis' form must be accessible from the Chart View.
Steps
- Select "Client A" and access the 'Diagnosis' form.
- Select "Update" in the 'Type Of Diagnosis' field.
- Enter "05/01/2023" in the 'Date Of Diagnosis' field.
- Enter the desired value in the 'Time Of Diagnosis Field'.
- Click [New Row].
- Search for and select the desired value in the 'Diagnosis Search' field.
- Select "Active" in the 'Status' field.
- Select "Practitioner A" in the 'Diagnosing Practitioner' field.
- Populate all other required and desired fields.
- Submit the form.
- Double-click on "Client A" to access the Chart View.
- Select the 'Diagnosis' form from the left-hand side.
- Select the episode used in the previous steps.
- Validate that the previously diagnosis is displayed.
- Validate "Practitioner A" is displayed with the proper practitioner credentials based on the diagnosis date, which is "Administrator".
- Close the chart.
- Select "Client A" and access the 'Diagnosis' form.
- Click [Add].
- Select "Update" in the 'Type Of Diagnosis' field.
- Enter "11/01/2023" in the 'Date Of Diagnosis' field.
- Enter the desired value in the 'Time Of Diagnosis Field'.
- Click [New Row].
- Search for and select the desired value in the 'Diagnosis Search' field.
- Select "Active" in the 'Status' field.
- Select "Practitioner A" in the 'Diagnosing Practitioner' field.
- Populate all other required and desired fields.
- Submit the form.
- Double-click on "Client A" to access the Chart View.
- Select the 'Diagnosis' form from the left-hand side.
- Select the episode used in the previous steps.
- Validate that the previously filed diagnosis is displayed.
- Validate "Practitioner A" is displayed with the proper practitioner credentials based on the diagnosis date, which is "Medical Doctor".
- Close the chart.
|
Topics
• Diagnosis
• Chart View
|
SQL Validation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Advanced Billing Rule Definition
- Client Charge Input
- Advanced Billing Failed Compliance Report
Scenario 1: Advanced Billing Rule - Advanced Billing Failed Compliance Report-Validate SYSTEM.billing_tx_filing_compliance
Specific Setup:
- An Advanced Billing Rule Definition exists for service code 1.
- Note the conditions that will allow the service code 1 to fail compliance.
- Note the 'Reason For Failed Compliance'.
- Create a service for a client that will cause service code 1 to fail compliance. Note the service date.
Steps
- Open 'Advance Billing Failed Compliance Report'.
- Enter the 'Client'.
- Enter the service date in 'Service From Date' and Service Through Date'.
- Click [Launch Failed Compliance Report].
- Validate the 'Client'.
- Validate the 'Service Code'.
- Validate the 'Rule Description'.
- Validate the 'Reason for Failed Compliance'.
- Close the report.
- Close the form.
- Use Crystal Reports or other SQL reporting tool to create a query of the 'SYSTEM.billing_tx_filing_compliance' table.
- Validate the query results match with details filled in 'Advance Billing Failed Compliance Report' form.
- Close the query results.
|
Topics
• Advanced Billing Rule Definition
|
AR Console Export
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- System Task Scheduler
- AR Console export Form
Scenario 1: AR Console Export
Specific Setup:
- Note the tester's 'User Definition'.
- Registry Settings:
- Set the 'Avatar PM->Billing->Accounts Receivable Management->->->Enable Accounts Receivable Management Functionality' registry setting to "Yes".
- Accounts Receivable functionality has been defined.
- Guarantors/Payors:
- An existing guarantor is identified to be used. Note the guarantor code/name.
- Service codes:
- An existing service code is identified to be used. Note the service code/description.
- Service Fee/ Cross Reference Maintenance:
- A fee definition is created for the service code identified in the ' Service Codes' form.
- Admission:
- An existing client is identified or a new client is admitted. Note client id, admission program, admission date.
- Financial Eligibility:
- A guarantor identified in the 'Guarantors/Payors' form is assigned to the client as a primary guarantor.
- Recurring Client Charge Input:
- 3-5 services are rendered to the client. Note service date, service code.
- Close charges.
- Charges created are closed.
- Client Ledger:
- The service distributed correctly to the assigned guarantor.
- Electronic Billing:
- All the services are claimed. Note the claim numbers.
- Use ‘AR Console User Defaults’ to give the tester access to the following:
- First initial of the client's last name.
- Admission program
- Guarantor the claim liability distributed to.
- Use ‘System Task Scheduler’ to process the ‘Auto AR Batch’ after the claims were created.
- AR Console:
- A claim follow up note is created for the first service of the client. Note the information of the claim follow-up note.
Steps
- Open ''Claim Follow-up'' form.
- Enter the client identified in setup in 'Select Client' input box.
- Click [Add] in 'Add, Edit Or Delete Claim' Follow-Up.
- Select the Guarantor defined in the setup from 'Guarantor' dropdown list.
- Select the desired claim in 'Claim' dropdown list.
- Validate that services display in 'Service(s)' text area.
- Click [Add] in 'Add, Edit Or Delete Row'.
- Enter any value in 'Follow-Up Date '.
- Click [No] in 'Followed Up'.
- Enter any value in 'Comments'.
- Repeat steps 7-11.
- Click [Update Row].
- Validate the values of 'Follow-Up Date / Status / Followed Up / Next Follow-Up Date / Completion Date / (Denial CRN# / Current CRN#)'.
- Click [Submit].
- Click [No].
- Open "AR Console Export" form.
- Click [Selected Values] in 'AR Console Data to Export'.
- Select desired value in 'Financial Class Selection'.
- Select desired guarantor in 'Guarantors'.
- Select desired programs in 'Programs'.
- Click 'Export To CSV'.
- Click [Discard].
- Click [Yes].
- Verify excel file is downloaded.
- Validate that the correct data displays in one row.
|
Topics
• Accounts Receivable Management
• NX
|
|
Topics
• Service Codes
• File Import
• Client Charge Input
• Edit Service Information
|
Search Results - Diagnosis Filtering
Scenario 1: Diagnosis - Editing a diagnosis
Specific Setup:
- Admission:
- An existing client is identified or a new client is admitted. Note the client id/Name.
- Diagnosis:
- A client must have a diagnosis entered.
Steps
- Open the 'Diagnosis' form.
- Search for desired client in the 'Select Client' field.
- Validate results display.
- Select desired client from the results.
- Validate a Pre-Display is displayed showing existing diagnoses for the client.
- Select an existing diagnosis record.
- Click [Edit].
- Enter an invalid time in the 'Time of Diagnosis' field.
- Validate an Error message stating: "Invalid time format. HH:MM AM, HH:MM PM or HHMM military time (Midnight is 0000 hours.)"
- Validate the 'Time of Diagnosis' field defaults to the time that was saved prior.
- Change the 'Time of Diagnosis' field to the current time.
- Enter a different practitioner in the 'Diagnosing Practitioner' field.
- Select "Void" in the 'Status' field.
- Validate the voided diagnosis is crossed off.
- Navigate to the myDay view.
- Navigate back to the open 'Diagnosis' form.
- Validate the voided diagnosis is crossed off.
- Validate the 'Diagnosing Practitioner' contains the value entered in the previous steps.
- Click [Submit].
- Validate a Pre-Display Confirmation dialog is displayed stating: Do you want to return to Pre-Display?
- Click [Yes].
- Select desired diagnosis record.
- Click [Edit].
- Select "No" in the 'Show Active Only' field.
- Validate the voided diagnosis displays and is crossed off.
- Close the form.
- Open the "Registry Settings" form.
- Search for the registry setting "Default Limit Results by ICD Category".
- Set the value to any valid value. You can combine values by inserting an '&' such as "F&Z", which will return results whose ICD10 value begins with the letters "F" and "Z".
- Click [Submit] to file the form.
- Open the "Diagnosis" form.
- Edit a previously added row of the "Diagnosis" table.
- Search for any a number or letter and only the values with an ICD10 code that begins with the value specified in the registry setting will show up in the search results.
Scenario 2: Diagnosis - Diagnosis Entry
Specific Setup:
- A client must be enrolled in an active episode (Client A).
Steps
- Select "Client A" and access the 'Diagnosis' form.
- Click [Add].
- Select "Admission" in the 'Type of Diagnosis' field.
- Press the 'Tab' key on the 'Type of Diagnosis' field.
- Validate the focus shifts to the 'Date of Diagnosis' field and the admission date is displayed as expected.
- Press the 'Tab' key on the 'Date of Diagnosis' field.
- Validate the focus shifts to the 'Time of Diagnosis' field.
- Enter any value in the 'Time of Diagnosis' field.
- Click [New Row].
- Search for and select the desired value in the 'Diagnosis Search' field.
- Verify the 'Add To Problem List' field is defaulted to 'Yes'.
- Populate all required and desired fields.
- Click [Submit] and [No].
- Select "Client A" and access the ‘Diagnosis’ form.
- Select the previously created diagnosis row to edit.
- Click [Edit].
- Click [New Row].
- Search for and select the desired value in the 'Diagnosis Search' field.
- Validate that the 'Diagnosis Search' returns the expected diagnoses.
- Populate all required and desired fields.
- Click [Submit] and [No].
- Select "Client A" and access the 'Diagnosis' form.
- Select the diagnosis row edited in the previous steps.
- Click [Edit].
- Validate that the newly added diagnosis row is displayed.
- Close the form.
- Open the "Registry Settings" form.
- Search for the registry setting "Default Limit Results by ICD Category".
- Set the value to any valid value. You can combine values by inserting an '&' such as "F&Z", which will return results whose ICD10 value begins with the letters "F" and "Z".
- Click [Submit] to file the form.
- Select 'Client A' and open the "Diagnosis" form.
- Edit a previously added row of the "Diagnosis" table.
- Search for any number or letter and only the values with an ICD10 code that begins with the value specified in the registry setting will show up in the search results.
Scenario 3: Registry Setting - Default Limit Results by ICD Category"
Specific Setup:
- Note: When setting up the new Registry Setting, 'Default Limit Results by ICD Category', also check the following registry setting: 'Avatar PM->Client Information->Diagnosis->->->Remove References to ICD-9/DSM-IV Codesets'. If it's set to '2' do the following:
- Open the "Client Charge Input With Diagnosis Entry" form.
- Attempt to do a search on Diagnosis.
- Validate the search results are limited to the ICD codes that begin with the letters from the registry setting value.
- If 'No Records Found' is in the search results, then update 'Remove References to ICD-9/DSM-IV Codesets' as follows:
- Change the value from 2 to 0 and submit the change.
- Change the value from 0 back to 2 and submit the change.
- Repeat steps the above steps to verify that the results are displayed as expected.
Steps
- Open the "Registry Settings" form.
- Search for the registry setting "Default Limit Results by ICD Category".
- Note: This registry setting is only available in NX.
- Note the registry setting is defaulted to blank. This will generate all results.
- Open any of the following forms that include a diagnosis search such as "Client Chart Input with Diagnosis", "Diagnosis", "Edit Service Information", "Service Panel Chart Input", "Set Associated Codes", Ambulatory or Inpatient Progress Notes with Diagnosis, etc.
- Attempt to do a search on Diagnosis.
- Validate the search result returns all values and does not filter any results.
- Open the "Registry Settings" form.
- Search for the registry setting "Default Limit Results by ICD Category".
- Set the registry setting to a valid value other than blank.
- Open any of the forms mentioned in step 2.
- Attempt to do a search on Diagnosis.
- Validate the search results are limited to the ICD codes that begin with the letters from the registry setting value.
|
Topics
• Diagnosis
|
FoRSE Configuration
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- User Definition
- FoRSE Configuration
- FoRSE Mapping
Scenario 1: FoRSE Configuration
Specific Setup:
- Using the "User Definition" form, give the user access to the "FoRSE Configuration".
- Refresh the menus.
Steps
- Open the "FoRSE Configuration" form.
- Enable "FoRSE" functionality.
- Set the "Facility ID" to the value assigned by naatp.
- Set the "Secret Key" to the value assigned by naatp.
- Set the "Register New Company URL" to the URL provided by naatp.
- Set the "Registration Status URL" to the URL provided,
- Set the "Surveys URL" to the URL provided.
- Go to the "FoRSE Facility Configuration" section.
- Enter the information for the EHR Facilities added.
- Click "Submit" to file the data.
- Open the "FoRSE Configuration" form.
- Validate the "Enable" radio button is clicked.
- Validate "Facility ID" is set to the value assigned by naatp.
- Validate the "Secret Key" is set to the value assigned by naatp.
- Validate the "Register New Company URL" is set to the URL provided by naatp.
- Validate the "Registration Status URL" is set to the URL provided,
- Validate "Surveys URL" is set to the URL provided.
- Go to the "FoRSE Facility Configuration" section.
- Validate the information for the EHR Facilities is correct.
- Click "View" in the "FoRSE Status" column of each row added .
- Validate the "FoRSE Status indicates "Success".
- Click "Discard" to close the form
Scenario 2: FoRSE Mapping
Specific Setup:
- FoRSE must be configured and enabled.
Steps
- Open the "FoRSE Mapping" form.
- Add a new mapping.
- Select the desired survey to map to in the "Type of Survey" drop down,
- Check the "EHR Facility IDs" to submit for this particular survey.
- For each Question in the survey, select an Avatar form and field to map to.
- Click "View" under the "Field Translation" column.
- Left as is, the system will use the default dictionary values and codes.
- If you wish to change the default dictionary values, you can use the "Field Translation".
- Click "Submit" to file the form.
- Open the "FoRSE Mapping" form.
- Edit an existing mapping.
- Select an existing mapping in the "Mapping" drop down
- Validate mapping is enabled.
- Validate the "EHR Facility IDs" are the ones selected previously.
- Validate the "Field Mapping" is as what was previously entered.
- File the "Admission" form either for a new client or an existing client.
- Open the "FoRSE Configuration" form.
- Go to the "FoRSE Monitor" section.
- Set the start and end dates.
- Select the client.
- Click "Launch Report".
- Click "Click To View Record".
- Validate payload indicates success.
Scenario 3: FoRSE Surveys
Specific Setup:
- Validate FoRSE is configured and enabled.
- Validate the survey is mapped to an Avatar form.
Steps
- Open a form that is mapped to a survey.
- File the form.
- Open the "FoRSE Configuration" form.
- Go to the "FoRSE Monitor" section.
- Set the start and end dates.
- Select the client.
- Click "Launch Report".
- Click "Click To View Record".
- Validate payload indicates a success.
FoRSE Configuration
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- User Definition
- FoRSE Configuration
- FoRSE Mapping
Scenario 1: FoRSE Configuration
Specific Setup:
- Using the "User Definition" form, give the user access to the "FoRSE Configuration".
- Refresh the menus.
Steps
- Open the "FoRSE Configuration" form.
- Enable "FoRSE" functionality.
- Set the "Facility ID" to the value assigned by naatp.
- Set the "Secret Key" to the value assigned by naatp.
- Set the "Register New Company URL" to the URL provided by naatp.
- Set the "Registration Status URL" to the URL provided,
- Set the "Surveys URL" to the URL provided.
- Go to the "FoRSE Facility Configuration" section.
- Enter the information for the EHR Facilities added.
- Click "Submit" to file the data.
- Open the "FoRSE Configuration" form.
- Validate the "Enable" radio button is clicked.
- Validate "Facility ID" is set to the value assigned by naatp.
- Validate the "Secret Key" is set to the value assigned by naatp.
- Validate the "Register New Company URL" is set to the URL provided by naatp.
- Validate the "Registration Status URL" is set to the URL provided,
- Validate "Surveys URL" is set to the URL provided.
- Go to the "FoRSE Facility Configuration" section.
- Validate the information for the EHR Facilities is correct.
- Click "View" in the "FoRSE Status" column of each row added .
- Validate the "FoRSE Status indicates "Success".
- Click "Discard" to close the form
Scenario 2: FoRSE Mapping
Specific Setup:
- FoRSE must be configured and enabled.
Steps
- Open the "FoRSE Mapping" form.
- Add a new mapping.
- Select the desired survey to map to in the "Type of Survey" drop down,
- Check the "EHR Facility IDs" to submit for this particular survey.
- For each Question in the survey, select an Avatar form and field to map to.
- Click "View" under the "Field Translation" column.
- Left as is, the system will use the default dictionary values and codes.
- If you wish to change the default dictionary values, you can use the "Field Translation".
- Click "Submit" to file the form.
- Open the "FoRSE Mapping" form.
- Edit an existing mapping.
- Select an existing mapping in the "Mapping" drop down
- Validate mapping is enabled.
- Validate the "EHR Facility IDs" are the ones selected previously.
- Validate the "Field Mapping" is as what was previously entered.
- File the "Admission" form either for a new client or an existing client.
- Open the "FoRSE Configuration" form.
- Go to the "FoRSE Monitor" section.
- Set the start and end dates.
- Select the client.
- Click "Launch Report".
- Click "Click To View Record".
- Validate payload indicates success.
Scenario 3: FoRSE Surveys
Specific Setup:
- Validate FoRSE is configured and enabled.
- Validate the survey is mapped to an Avatar form.
Steps
- Open a form that is mapped to a survey.
- File the form.
- Open the "FoRSE Configuration" form.
- Go to the "FoRSE Monitor" section.
- Set the start and end dates.
- Select the client.
- Click "Launch Report".
- Click "Click To View Record".
- Validate payload indicates a success.
FoRSE Mapping
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- User Definition
- FoRSE Configuration
- FoRSE Mapping
Scenario 1: FoRSE Configuration
Specific Setup:
- Using the "User Definition" form, give the user access to the "FoRSE Configuration".
- Refresh the menus.
Steps
- Open the "FoRSE Configuration" form.
- Enable "FoRSE" functionality.
- Set the "Facility ID" to the value assigned by naatp.
- Set the "Secret Key" to the value assigned by naatp.
- Set the "Register New Company URL" to the URL provided by naatp.
- Set the "Registration Status URL" to the URL provided,
- Set the "Surveys URL" to the URL provided.
- Go to the "FoRSE Facility Configuration" section.
- Enter the information for the EHR Facilities added.
- Click "Submit" to file the data.
- Open the "FoRSE Configuration" form.
- Validate the "Enable" radio button is clicked.
- Validate "Facility ID" is set to the value assigned by naatp.
- Validate the "Secret Key" is set to the value assigned by naatp.
- Validate the "Register New Company URL" is set to the URL provided by naatp.
- Validate the "Registration Status URL" is set to the URL provided,
- Validate "Surveys URL" is set to the URL provided.
- Go to the "FoRSE Facility Configuration" section.
- Validate the information for the EHR Facilities is correct.
- Click "View" in the "FoRSE Status" column of each row added .
- Validate the "FoRSE Status indicates "Success".
- Click "Discard" to close the form
Scenario 2: FoRSE Mapping
Specific Setup:
- FoRSE must be configured and enabled.
Steps
- Open the "FoRSE Mapping" form.
- Add a new mapping.
- Select the desired survey to map to in the "Type of Survey" drop down,
- Check the "EHR Facility IDs" to submit for this particular survey.
- For each Question in the survey, select an Avatar form and field to map to.
- Click "View" under the "Field Translation" column.
- Left as is, the system will use the default dictionary values and codes.
- If you wish to change the default dictionary values, you can use the "Field Translation".
- Click "Submit" to file the form.
- Open the "FoRSE Mapping" form.
- Edit an existing mapping.
- Select an existing mapping in the "Mapping" drop down
- Validate mapping is enabled.
- Validate the "EHR Facility IDs" are the ones selected previously.
- Validate the "Field Mapping" is as what was previously entered.
- File the "Admission" form either for a new client or an existing client.
- Open the "FoRSE Configuration" form.
- Go to the "FoRSE Monitor" section.
- Set the start and end dates.
- Select the client.
- Click "Launch Report".
- Click "Click To View Record".
- Validate payload indicates success.
Scenario 3: FoRSE Surveys
Specific Setup:
- Validate FoRSE is configured and enabled.
- Validate the survey is mapped to an Avatar form.
Steps
- Open a form that is mapped to a survey.
- File the form.
- Open the "FoRSE Configuration" form.
- Go to the "FoRSE Monitor" section.
- Set the start and end dates.
- Select the client.
- Click "Launch Report".
- Click "Click To View Record".
- Validate payload indicates a success.
FoRSE Functionality - Communication API
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- User Definition
- FoRSE Configuration
- FoRSE Mapping
Scenario 1: FoRSE Configuration
Specific Setup:
- Using the "User Definition" form, give the user access to the "FoRSE Configuration".
- Refresh the menus.
Steps
- Open the "FoRSE Configuration" form.
- Enable "FoRSE" functionality.
- Set the "Facility ID" to the value assigned by naatp.
- Set the "Secret Key" to the value assigned by naatp.
- Set the "Register New Company URL" to the URL provided by naatp.
- Set the "Registration Status URL" to the URL provided,
- Set the "Surveys URL" to the URL provided.
- Go to the "FoRSE Facility Configuration" section.
- Enter the information for the EHR Facilities added.
- Click "Submit" to file the data.
- Open the "FoRSE Configuration" form.
- Validate the "Enable" radio button is clicked.
- Validate "Facility ID" is set to the value assigned by naatp.
- Validate the "Secret Key" is set to the value assigned by naatp.
- Validate the "Register New Company URL" is set to the URL provided by naatp.
- Validate the "Registration Status URL" is set to the URL provided,
- Validate "Surveys URL" is set to the URL provided.
- Go to the "FoRSE Facility Configuration" section.
- Validate the information for the EHR Facilities is correct.
- Click "View" in the "FoRSE Status" column of each row added .
- Validate the "FoRSE Status indicates "Success".
- Click "Discard" to close the form
Scenario 2: FoRSE Mapping
Specific Setup:
- FoRSE must be configured and enabled.
Steps
- Open the "FoRSE Mapping" form.
- Add a new mapping.
- Select the desired survey to map to in the "Type of Survey" drop down,
- Check the "EHR Facility IDs" to submit for this particular survey.
- For each Question in the survey, select an Avatar form and field to map to.
- Click "View" under the "Field Translation" column.
- Left as is, the system will use the default dictionary values and codes.
- If you wish to change the default dictionary values, you can use the "Field Translation".
- Click "Submit" to file the form.
- Open the "FoRSE Mapping" form.
- Edit an existing mapping.
- Select an existing mapping in the "Mapping" drop down
- Validate mapping is enabled.
- Validate the "EHR Facility IDs" are the ones selected previously.
- Validate the "Field Mapping" is as what was previously entered.
- File the "Admission" form either for a new client or an existing client.
- Open the "FoRSE Configuration" form.
- Go to the "FoRSE Monitor" section.
- Set the start and end dates.
- Select the client.
- Click "Launch Report".
- Click "Click To View Record".
- Validate payload indicates success.
Scenario 3: FoRSE Surveys
Specific Setup:
- Validate FoRSE is configured and enabled.
- Validate the survey is mapped to an Avatar form.
Steps
- Open a form that is mapped to a survey.
- File the form.
- Open the "FoRSE Configuration" form.
- Go to the "FoRSE Monitor" section.
- Set the start and end dates.
- Select the client.
- Click "Launch Report".
- Click "Click To View Record".
- Validate payload indicates a success.
|
Topics
• FoRSE
|
Registry Settings - Validate Program For Staff Guarantor Coverage
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Practitioner Enrollment
- Client Charge Input
- Create Interim Billing Batch File
- Electronic Billing
- Crystal Reports or other SQL Reporting tool (PM Namespace)
- SOAPUI - WEBSVC.PractitionerRegister
- SOAPUI - AddPractitionerGuarantorCoverage
- SOAPUI - DeletePractitionerGuarantorCoverage
Scenario 1: Registry Setting - Validate Program For Staff Guarantor Coverage
Steps
- Open the ‘Registry Settings’ form.
- Set the ‘Limit Registry Setting to the Following Search Criteria’ field to the ‘Validate Program For’.
- Click [View Registry Settings].
- Validate the ‘Registry Setting’ field equal to ‘Avatar PM->Practitioner->Enrollment->->->Validate Program For Staff Guarantor Coverage’.
- Validate the ‘Registry Setting Details’ field contains ‘[FACILITY SPECIFIC] Enter 'Y' to add the 'Program' field to 'Practitioner Enrollment' (Guarantor Coverage). This will allow the service to be validated against the selected Programs when checking the Practitioner's Guarantor Coverage in the bills. Enter 'N' to remove the 'Program' field and the associated logic.’.
- Validate the ‘Registry Setting Value’ field defaults to ‘N’.
- Close the form.
- Open the ‘Practitioner Enrollment’ form.
- Select desired practitioner from the ‘Select Staff’ field.
- Select the ‘Guarantor Coverage’ section.
- Validate the ‘Guarantor Coverage’ section does not contain ‘Program’ field.
- Close the form.
- Open the ‘Registry Settings’ form.
- Set the ‘Limit Registry Setting to the Following Search Criteria’ field to the ‘Validate Program For’.
- Click [View Registry Settings].
- Validate the ‘Registry Setting’ field equals to ‘Avatar PM->Practitioner->Enrollment->->->Validate Program For Staff Guarantor Coverage’.
- Set the ‘Registry Setting Value’ field to ‘Y’.
- Click [Submit].
- Click [OK].
- Click [No].
- Open the ‘Practitioner Enrollment’ form.
- Select desired practitioner from the ‘Select Staff’ field.
- Select the ‘Guarantor Coverage’ section.
- Validate the ‘Guarantor Coverage’ section contains ‘Program’ field.
- Validate the ‘Program’ value displays in scrolling text box.
- Close the form.
- Open the ‘Registry Settings’ form.
- Set the ‘Limit Registry Setting to the Following Search Criteria’ field to the ‘Validate Program For’.
- Click [View Registry Settings].
- Validate the ‘Registry Setting’ field equals to ‘Avatar PM->Practitioner->Enrollment->->->Validate Program For Staff Guarantor Coverage’.
- Click [View Registry Settings].
- Set the ‘Registry Setting Value’ field to ‘1’.
- Validate the error dialog contains ‘The selected value is not valid in the current system code for the following reason: Invalid Response - Example:'Y' or 'N'’.
- Click [Enter].
- Click [OK].
- Set the ‘Registry Setting Value’ field to ‘m’.
- Validate the error dialog contains ‘The selected value is not valid in the current system code for the following reason: Invalid Response - Example:'Y' or 'N'’.
- Click [Enter].
- Click [OK].
- Set the ‘Registry Setting Value’ field to ‘YES’
- Validate the error dialog contains ‘The selected value is not valid in the current system code for the following reason: More than 1 characters.
- Click [OK].
- Set the ‘Registry Setting Value’ field to ‘’.
- Click [Submit].
- Validate the ‘Filing Error’ dialog box contains: ‘The following fields are missing: Registry Setting Value’.
- Click [OK].
- Set the ‘Registry Setting Value’ field to ‘Y’.
- Click [Submit].
- Click [OK].
- Click [No].
- Open the ‘Practitioner Enrollment’ form.
- Select the ‘Guarantor Coverage’ section.
- Select desired practitioner from the ‘Select Staff’ field.
- Select ‘Create New’ from the ‘Guarantor Coverage Entry’ field.
- Select desired guarantor from the Guarantor field.
- Select desired program(s) form the ‘Program’ field.
- Set the ‘Effective Date’ field to desired date.
- Set the ‘Lapse Date’ field to desired date.
- Click [File Mapping].
- Validate the ‘Filed!’ dialog box contains: ‘Saved. Please note: The changes will take effect when you submit the form.’
- Click [OK].
- Click [Submit].
- Open the ‘Practitioner Enrollment’ form.
- Select the same practitioner as above from the ‘Select Staff’ field.
- Select the ‘Guarantor Coverage’ section.
- Validate the ‘Guarantor Coverage’ text area contains ‘Guarantor’, ‘Program’, ‘Effective Date’ and ‘Lapse Date’ as defined in above steps.
- Click [Submit].
Scenario 2: 837 Professional bill - Validating 'Validate Program For Staff Guarantor Coverage' registry setting
Specific Setup:
- Registry Setting:
- The 'Validate Program For Staff Guarantor Coverage' registry setting is set to 'Y'.
- Guarantors/Payors:
- An existing guarantor is identified to be used and all the options are checked in the 'Inhibit Billing if Practitioner is not Covered by this Guarantor' field. Note the guarantor's code/name.
- Service codes:
- An existing service code is identified to be used. Note the service code/description.
- Service Fee/ Cross Reference Maintenance:
- A fee definition is created for the service code identified in the 'Service Codes' form.
- Practitioner Enrollment:
- An existing practitioner is identified, or a new practitioner is created. The guarantor coverage record for the staff is created that includes guarantor identified in the 'Guarantors/Payors' and desired program(s). Note the guarantor and program.
- Admission:
- An existing client is identified, or a new client is admitted in a program which is defined in the guarantor coverage for the practitioner in the 'Practitioner Enrollment' form. Note client id, admission program, admission date.
- Financial Eligibility:
- A guarantor identified in the 'Guarantors/Payors' form is assigned to the client as a primary guarantor.
- Client Charge Input:
- A service is rendered to the client. Note service date, service code.
- Client Ledger:
- A service distributed correctly to the assigned guarantor.
- Close Charges:
- The service(s) rendered to the client is closed.
- Create Interim Billing Batch:
- An interim billing batch is created that includes desired client, service and the guarantor. Note the batch number.
Steps
- Open the 'Electronic Billing' form.
- Compile an unclaimed 837 Professional bill for the client.
- Verify the bill compiles successfully.
- Select 'Run Report' in 'Billing Options' field.
- Select 'Print' in 'Print Or Delete Report' field.
- Select the 'File' field.
- Click [Print 837 Report].
- Validate that the report launches successfully and contains correct client, service, and guarantor.
- Close the report.
- Close the form.
- Open the 'Crystal Report' or any other SQL data viewer.
- Locate to the PM namespace.
- Query the 'Select * from SYSTEM.staff_guarantor_coverage'.
- Verify the 'ID' column displays unique id for the guarantor coverage entry created in the 'Practitioner Enrollment' form.
- Verify the 'STAFFID' column displays the correct practitioner id which is set up in the setup section.
- Verify the 'guarantor_id' column displays correct guarantor id for the guarantor assigned to the client in the 'Financial Eligibility' form.
- Verify the 'program_code' column displays correct program(s) code set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'program_shval' column displays correct program(s) description set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'program_value' column displays correct program(s) description set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'effective_date' column displays the correct date set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'lapse_date' column displays the correct date set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Close the 'Crystal Report' or SQL data viewer.
- Open the 'Practitioner Enrollment' form for the practitioner identified in the setup section.
- Select the 'Guarantor Coverage' section.
- Select an existing guarantor coverage entry from the 'Guarantor Coverage Entry' field.
- Verify the admission program is selected in the 'Program' field.
- Click [Delete Mapping].
- Click [Yes].
- [OK].
- Verify the guarantor coverage record removed from the 'Guarantor Coverage' text area.
- Select 'Create New' from the 'Guarantor Coverage Entry' field.
- Select the guarantor which is assigned to the client as a primary guarantor.
- Select the program different from the admission program of the client in the 'Program' field.
- Enter desired date in the 'Effective Date' and 'Lapse Date' fields.
- Click [File Mapping].
- Click [Submit].
- Verify the user navigates to the home page.
- Open 'Electronic Billing' form.
- Compile an unclaimed bill for the client.
- Validate that a message is received stating: No Valid Information Found. Please Check The Error Report.
- Click [OK].
- Select 'Run Report' in 'Billing Options'.
- Select 'Print' in 'Print Or Delete Report'.
- Select the 'File'.
- Click [Print 837 Report].
- Validate that the report launches and contains a link to 'Required Data Missing: Patient Claim Data'.
- Click the 'Required Data Missing: Patient Service Data' link.
- Verify that the error is - 'No Guarantor Coverage in Effect for Rendering Practitioner'.
- Close the report.
- Close the form.
- Open the 'Crystal Report' or any other SQL data viewer.
- Locate to the PM namespace.
- Query the 'Select * from SYSTEM.staff_guarantor_coverage'.
- Verify the 'ID' column displays unique id for the guarantor coverage entry created in the 'Practitioner Enrollment' form.
- Verify the 'STAFFID' column displays the correct practitioner id which is set up in the setup section.
- Verify the 'guarantor_id' column displays correct guarantor id for the guarantor set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'program_code' column displays correct program(s) code for the program set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'program_shval' column displays correct program(s) description for the program set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'program_value' column displays correct program(s) description for the program set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'effective_date' column displays the correct date set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'lapse_date' column displays the correct date set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Close the 'Crystal Report' or SQL data viewer.
- Open the 'Registry Settings' form.
- Set the 'Validate Program For Staff Guarantor Coverage' registry setting to 'N'.
- Click [Submit].
- Open the 'Practitioner Enrollment' form for the practitioner identified in the setup section.
- Select the 'Guarantor Coverage' section.
- Verify the guarantor coverage record exist in the 'Guarantor Coverage' text area.
- Close the form.
- Verify the user navigates to the home page.
- Open the 'Electronic Billing' form.
- Compile an unclaimed 837 Professional bill for the client.
- Verify the bill compiles successfully.
- Select 'Run Report' in 'Billing Options' field.
- Select 'Print' in 'Print Or Delete Report' field.
- Select the 'File' field.
- Click [Print 837 Report].
- Validate that the report launches successfully and contains correct client, service, and guarantor.
- Close the report.
- Close the form.
- Verify the user navigates to the home page.
Scenario 3: 837 Institutional bill - Validating 'Validate Program For Staff Guarantor Coverage' registry setting
Specific Setup:
- Registry Setting:
- The 'Validate Program For Staff Guarantor Coverage' registry setting is set to 'Y'.
- Guarantors/Payors:
- An existing guarantor is identified to be used and all the options are checked in the 'Inhibit Billing if Practitioner is not Covered by this Guarantor' field. Note the guarantor'scode/name.
- Service codes:
- An existing service code is identified to be used. Note the service code/description.
- Service Fee/ Cross Reference Maintenance:
- A fee definition is created for the service code identified in the 'Service Codes' form.
- Practitioner Enrollment:
- An existing practitioner is identified, or a new practitioner is created. The guarantor coverage record for the staff is created that includes guarantor identified in the 'Guarantors/Payors' and desired program(s). Note the guarantor and program.
- Admission:
- An existing client is identified, or a new client is admitted in a program which is defined in the guarantor coverage for the practitioner in the 'Practitioner Enrollment' form. Note client id, admission program, admission date.
- Financial Eligibility:
- A guarantor identified in the 'Guarantors/Payors' form is assigned to the client as a primary guarantor.
- Client Charge Input:
- A service is rendered to the client. Note service date, service code.
- Client Ledger:
- A service distributed correctly to the assigned guarantor.
- Close Charges:
- The service(s) rendered to the client is closed.
- Create Interim Billing Batch:
- An interim billing batch is created that includes desired client, service and the guarantor. Note the batch number.
Steps
- Open the 'Electronic Billing' form.
- Compile an unclaimed 837 Institutional bill for the client.
- Verify the bill compiles successfully.
- Select 'Run Report' in 'Billing Options' field.
- Select 'Print' in 'Print Or Delete Report' field.
- Select the 'File' field.
- Click [Print 837 Report].
- Validate that the report launches successfully and contains correct client, service, and guarantor.
- Close the report.
- Close the form.
- Open the 'Crystal Report' or any other SQL data viewer.
- Locate to the PM namespace.
- Query the 'Select * from SYSTEM.staff_guarantor_coverage'.
- Verify the 'ID' column displays unique id for the guarantor coverage entry created in the 'Practitioner Enrollment' form.
- Verify the 'STAFFID' column displays the correct practitioner id which is set up in the setup section.
- Verify the 'guarantor_id' column displays correct guarantor id for the guarantor assigned to the client in the 'Financial Eligibility' form.
- Verify the 'program_code' column displays correct program(s) code set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'program_shval' column displays correct program(s) description set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'program_value' column displays correct program(s) description set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'effective_date' column displays the correct date set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'lapse_date' column displays the correct date set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Close the 'Crystal Report' or SQL data viewer.
- Open the 'Practitioner Enrollment' form for the practitioner identified in the setup section.
- Select the 'Guarantor Coverage' section.
- Select an existing guarantor coverage entry from the 'Guarantor Coverage Entry' field.
- Verify the admission program is selected in the 'Program' field.
- Click [Delete Mapping].
- Click [Yes].
- [OK].
- Verify the guarantor coverage record for the admission program of the client is removed from the 'Guarantor Coverage' text area.
- Click [Submit].
- Open the 'Crystal Report' or any other SQL data viewer.
- Locate to the PM namespace.
- Query the 'Select * from SYSTEM.staff_guarantor_coverage'.
- Verify the guarantor coverage created for the client's admission program is deleted from the SQL table.
- Close the 'Crystal Report' or SQL data viewer.
- Verify the user navigates to the home page.
- Open 'Electronic Billing' form.
- Compile an unclaimed bill for the client.
- Validate that a message is received stating: No Valid Information Found. Please Check The Error Report.
- Click [OK].
- Select 'Run Report' in 'Billing Options'.
- Select 'Print' in 'Print Or Delete Report'.
- Select the 'File'.
- Click [Print 837 Report].
- Validate that the report launches and contains a link to 'Required Data Missing: Patient Claim Data'.
- Click the 'Required Data Missing: Patient Service Data' link.
- Verify that the error is - 'No Guarantor Coverage in Effect for Rendering Practitioner'.
- Close the report.
- Close the form.
- Open the 'Registry Settings' form.
- Set the 'Validate Program For Staff Guarantor Coverage' registry setting to 'N'.
- Click [Submit].
- Click [OK].
- Click [No] on the [Form Return] dialog.
- Verify the user navigates to the home page.
- Open the 'Electronic Billing' form.
- Compile an unclaimed 837 Institutional bill for the client.
- Verify the bill compiles successfully.
- Select 'Run Report' in 'Billing Options' field.
- Select 'Print' in 'Print Or Delete Report' field.
- Select the 'File' field.
- Click [Print 837 Report].
- Validate that the report launches successfully and contains correct client, service, and guarantor.
- Close the report.
- Close the form.
- Verify the user navigates to the home page.
Scenario 4: WEBSVC.PractitionerRegister - AddPractitionerGuarantorCoverage / DeletePractitionerGuarantorCoverage - Registry setting 'Validate Program For Staff Guarantor Coverage'
Specific Setup:
- Registry Setting:
- The 'Validate Program For Staff Guarantor Coverage' registry setting is set to 'Y'.
- Guarantors/Payors:
- An existing guarantor is identified to be used and all the options are checked in the 'Inhibit Billing if Practitioner is not Covered by this Guarantor' field. Note the guarantor's code/name.
- Practitioner:
- An existing practitioner is identified, or a new practitioner is created. Note the practitioner id.
- Admission:
- An existing client is identified, or a new client is admitted in a desired program. Note the client id, admission program, admission date.
- Financial Eligibility:
- The guarantor identified in the 'Guarantors/Payors' form is assigned to the client as a primary guarantor.
Steps
- Access SOAPUI or any other web service tool.
- File the 'AddPractitionerGuarantorCoverage' method of the WEBSVC.PractitionerRegister web service for the desired guarantor and practitioner by entering desired value to the 'Guarantor', 'EffectiveDate', 'LapseDate','Program', and 'PractitionerID' fields. Note all the values.
- Verify the web service files successfully.
- Open the 'Crystal Report' or any other SQL data viewer.
- Locate to the PM namespace.
- Query the 'Select * from SYSTEM.staff_guarantor_coverage'.
- Verify the 'ID' column displays unique id for the guarantor coverage entry created in the 'Practitioner Enrollment' form. Note this 'ID' number for later use.
- Verify the 'STAFFID' column displays the correct practitioner id which is set up in the setup section.
- Verify the 'guarantor_id' column displays correct guarantor id for the guarantor assigned to the client in the 'Financial Eligibility' form.
- Verify the 'program_code' column displays correct program(s) code set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'program_shval' column displays correct program(s) description set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'program_value' column displays correct program(s) description set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'effective_date' column displays the correct date set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Verify the 'lapse_date' column displays the correct date set up in the guarantor coverage entry for the practitioner in the 'Practitioner Enrollment' form.
- Close the 'Crystal Report' or SQL data viewer.
- Login to myAvatar.
- Open the 'Practitioner Enrollment' form for the practitioner identified in the setup section.
- Select the 'Guarantor Coverage' section.
- Verify the guarantor coverage entry created through the 'AddPractitionerGuarantorCoverage' is available in the 'Guarantor Coverage Entry' text area.
- Close the form.
- Open the 'Client Charge Input' form.
- Render a service to the client identified in the setup section. Note the service date, service code.
- Open the 'Client Ledger' form.
- Verify the service distributed correctly to the assigned guarantor.
- Open the 'Close Charges' form.
- Close the service rendered to the client.
- Open the 'Create Interim Billing Batch' form.
- Create an interim billing batch that includes desired client, service, and the guarantor. Note the batch number.
- Close the form.
- Open the 'Electronic Billing' form.
- Compile an unclaimed 837 Professional bill for the client.
- Verify the bill compiles successfully.
- Select 'Run Report' in 'Billing Options' field.
- Select 'Print' in 'Print Or Delete Report' field.
- Select the 'File' field.
- Click [Print 837 Report].
- Validate that the report launches successfully and contains correct client, service, and guarantor.
- Close the report.
- Close the form.
- Access SOAPUI or any other web service tool.
- Locate to the 'DeletePractitionerGuarantorCoverage' method of the WEBSVC.PractitionerRegister web service.
- Enter the practitioner id in the 'PractitionerID' field which is used in the 'AddPractitionerGuarantorCoverage' method.
- Enter the value noted above from the 'ID' field of the SYSTEM.staff_guarantor_coverage SQL table in the 'PractitionerGuarantorCoverageID' field.
- Submit the request.
- Verify the web service files successfully.
- Open the 'Crystal Report' or any other SQL data viewer.
- Locate to the PM namespace.
- Query the 'Select * from SYSTEM.staff_guarantor_coverage'.
- Verify the row with the ID used in the 'DeletePractitionerGuarantorCoverage' is deleted.
- Close the report.
- Open 'Electronic Billing' form.
- Compile an unclaimed bill for the client.
- Validate that a message is received stating: No Valid Information Found. Please Check The Error Report.
- Click [OK].
- Select 'Run Report' in 'Billing Options'.
- Select 'Print' in 'Print Or Delete Report'.
- Select the 'File'.
- Click [Print 837 Report].
- Validate that the report launches and contains a link to 'Required Data Missing: Patient Claim Data'.
- Click the 'Required Data Missing: Patient Service Data' link.
- Verify that the error is - 'No Guarantor Coverage in Effect for Rendering Practitioner'.
- Close the report.
- Close the form.
- Open the 'Registry Settings' form.
- Set the 'Validate Program For Staff Guarantor Coverage' registry setting to 'N'.
- Click [Submit].
- Click [OK].
- Click [No] on the [Form Return] dialog.
- Verify the user navigates to the home page.
- Open the 'Electronic Billing' form.
- Compile an unclaimed 837 Professional bill for the client.
- Verify the bill compiles successfully.
- Select 'Run Report' in 'Billing Options' field.
- Select 'Print' in 'Print Or Delete Report' field.
- Select the 'File' field.
- Click [Print 837 Report].
- Validate that the report launches successfully and contains correct client, service, and guarantor.
- Close the report.
- Close the form.
- Verify the user navigates to the home page.
|
Topics
• Registry Settings
• Practitioner
• 837 Professional
• 837 Institutional
• Web Services
|
Future Functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Remittance Processing Widget
Scenario 1: Remittance Processing Widget- Collapse Rows By Default
|
Topics
• Remittance Processing
• NX
|
Remittance Processing - Future Functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Charge Input
- Remittance Processing Widget
- Delete Service (Open Service Only)
- Delete Last Movement
- Change MR#
Internal Test Only
|
Topics
n/a
|
Payment Acknowledgement - Scheduling Calendar - Check In
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Payment Acknowledgement
- Posting/Adjustment Codes Definition
- File Import
Scenario 1: Payment Acknowledgement - Posting Front desk payments - With new registry settings on for client with Guarantor - financial class=6 (self pay)
Specific Setup:
- Registry Settings:
- Set 'Enable Payment Acknowledgement' to "Y".
- Select "4" in 'Prevent Posting Payments Unless Payment has been Acknowledged'.
- Select "1" in 'Add Previous Balance To Expected Self Pay Amount'.
- Select "Y" in ' 'Include Guarantors with Self Pay System Financial Class'.
- Guarantors/Payors:
- Guarantor 1:
- An existing guarantor with a financial class of 'Self Pay' is identified to be assigned to the client. Note the guarantor code/value.
- Program Maintenance:
- Identify an existing program code/value to be used for the client's admission.
- Identify the location of the program to be used for the Client's admission.
- Admission:
- Client A:
- An inpatient or outpatient client is created using the program identified above or an existing client is identified. Note the client ID/name, and admission date/program.
- Financial Eligibility: "Guarantor 1" is assigned to the client.
- Service code:
- Service code 1:
- An existing service code to be used with inpatient/ outpatient programs is identified. Note the service code for further validation.
- Posting/Adjustment Code Definition:
- Posting code 1:
- An existing payment, adjustment, or transfer code is identified to be used. Note the code and type of the code.
- Recurring Client Charge Input:
- "Client A" is charged with "Service code 1" on different dates (more than one date that creates a self pay balance).
Steps
Scenario 2: File Import - Deposit Entry' - Posting a file for the active client/episode
Specific Setup:
- Registry Settings:
- Set 'Enable Payment Acknowledgement' to "Y".
- Select "5" in 'Prevent Posting Payments Unless Payment has been Acknowledged'.
- Guarantors/Payor:
- Guarantor 1:
- An existing guarantor is identified to be assigned to the client. Note the guarantor code/value.
- Program Maintenance:
- Identify an existing program code/value to be used for the client's admission.
- Identify the location of the program to be used for the Client's admission.
- Admission:
- Client A:
- An inpatient or outpatient client is created using the program identified above or an existing client is identified. Note the client ID/name, and admission date/program.
- Financial Eligibility: The existing guarantor is assigned to the client.
- Service code:
- Service code 1:
- An existing service code to be used with inpatient/ outpatient programs is identified. Note the service code for further validation.
- Posting/Adjustment Code Definition:
- Posting code 1:
- An existing payment, adjustment, or transfer code is identified to be used. Note the code and type of the code.
- File Import:
- File A:
- An import file is created to process the deposit entry. Ensure that the file contains all required fields and desired optional fields. Note the file name/location of the file.
Steps
- Open 'Recurring Client Charge Input'.
- Create more than one service on different dates for "Client A".
- Open 'Client Ledger'.
- Verify that "Client A" is filed with the services.
- Close the report.
- Click [No].
- Open the 'File Import' form.
- Select the 'Deposit Entry' from the File Type field.
- Select 'Upload New File'.
- Click [Process Action].
- Select the deposit entry file Import file ("File A") created in the setup section.
- Compile the file by selecting the 'Compile/Validate File' option and selecting the uploaded file ("File A").
- Click [Process Action].
- Verify the file compiles successfully.
- Click [OK].
- Select the 'Post File' option.
- Post the compiled file by selecting it.
- Click [Process Action].
- Verify the file posted successfully.
- Click [OK].
- Verify that the crystal report is generated with the posted data.
- Click [Close Report].
- Click [Discard].
- Click [Yes].
- Query the below table for "Client A" and verify that the payment posted is shown in a new row.
- "unacknowledged_payments"
- Close the SQL query window.
- Open 'Payment Acknowledgement'.
- Select 'Post Front Office and myHP Payments'.
- Select the date for which the deposit entry was posted.
- Select the value 'Both' from the 'Type' field.
- Click [Review].
- Verify that the 'PAYMENT ACKNOWLEDGEMENT' window is opened with a grid showing with the payment to acknowledge data.
- Verify that the data posted in the deposit entry is shown as expected.
- Select the payment row.
- Click [Save].
- Click [Yes].
- Enter any desired valid value for the below fields in the Payment Acknowledgement form,
- Batch Number
- Deposit Date
- Category
- Bank Ref #
- Click [Post].
- Verify the popup message says, "Filed successfully.".
- Click [OK].
- Click [Discard].
- Click [Yes].
- Open 'Client Ledger'.
- Verify that "Client A" is shown with the acknowledged payment.
- Close the report.
- Click [No].
- Query the below table for "Client A" and verify that the row(s) are removed upon the successful Payment Acknowledgement.
- "unacknowledged_payments"
- Query the below table for "Client A" and verify that there is a new row added for the Acknowledged deposit entry.
- "billing_pay_adj_history"
- Verify that the below column values are shown:
- payment_amount
- payment_type_code
- payment_type_value
- service_code
- v_program_of_service_code
- v_program_of_service_value
- GUARANTOR_ID
- service_code
- option_desc
- Close the SQL query window.
Scenario 3: Payment Acknowledgement - Posting Front desk payments - With new registry settings on for client with Guarantor - system financial class=6 (self pay)
Specific Setup:
- Registry Settings:
- Set 'Enable Payment Acknowledgement' to "Y".
- Select "4" in 'Prevent Posting Payments Unless Payment has been Acknowledged'.
- Select "1" in 'Add Previous Balance To Expected Self Pay Amount'.
- Select "Y" in ' 'Include Guarantors with Self Pay System Financial Class'.
- Guarantors/Payors:
- Guarantor 1:
- An existing guarantor with a financial class other than 'Self Pay' is identified to be assigned to the client. Note the guarantor code/value.
- Dictionary Update:
- The identified guarantor's financial class's dictionary code for the data element 'Financial Class' should have the value of "Self Pay" for its extended dictionary Value 'System Financial Class'.
- Program Maintenance:
- Identify an existing program code/value to be used for the client's admission.
- Identify the location of the program to be used for the Client's admission.
- Admission:
- Client A:
- An inpatient or outpatient client is created using the program identified above or an existing client is identified. Note the client ID/name, and admission date/program.
- Financial Eligibility: "Guarantor 1" is assigned to the client.
- Service code:
- Service code 1:
- An existing service code to be used with inpatient/ outpatient programs is identified. Note the service code for further validation.
- Posting/Adjustment Code Definition:
- Posting code 1:
- An existing payment, adjustment, or transfer code is identified to be used. Note the code and type of the code.
- Recurring Client Charge Input:
- "Client A" is charged with "Service code 1" on different dates (more than one date that crates the client to have self pay balance).
Steps
|
Topics
• Scheduling Calendar
• Check-In
• NX
• Deposit Entry
• File Import
• Payment Acknowledgement
• Front Desk
|
Cross Episode Financial Eligibility - Policy number
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Default Guarantor Assignment
- Cross Episode Financial Eligibility
Scenario 1: Cross Episode Financial Eligibility - Policy Number Verification
Specific Setup:
- Registry Settings:
- Set the 'Avatar PM->Client Information->Client Demographics->->->Additional Fields Registry Setting Value' to the value that covers the value to add 'Additional Policy Numbers'.
- Set the 'Avatar PM->Billing->Financial Eligibility->->->Enable Default Guarantor Assignment' to 'Y'.
- Default Guarantor Assignment:
- A guarantor is defined to default in 'Cross Episode Financial Eligibility' upon the filing of admission. Note the guarantor code/name.
- Admission (Outpatient):
- A new client is admitted. The guarantor defined above and the policy number of the guarantor are added in the 'Demographics' section. Note the client id, value of the 'Guarantor 1' field and the value added in the 'Policy Number 1' field.
Steps
- Open the 'Cross Episode Financial Eligibility' form.
- Validate the 'Guarantor #1' field populated correctly with the guarantor added in the 'Demographics' section of the admission form of the client.
- Navigate to the 'Guarantor Selection' section.
- Validate the 'Subscriber Policy #' is populated correctly with the policy number of the guarantor added in the 'Demographics' section of the admission form of the client.
- Click [Submit].
- Open the 'Default Guarantor Assignment' form.
- Select desired guarantor in the 'Select Guarantor to Default' field.
- Select the 'Filing of Admission' option in the 'Default the Guarantor(s) During' field.
- Select the 'Financial Eligibility' in the 'Add the Guarantor(s) to Which Form' field.
- Click [Submit].
- Open the 'Admission' or Admission(Outpatient)' form.
- Admit a new client.
- Navigate to the 'Demographics' section.
- Add the guarantor used in the 'Default Guarantor Assignment' form and add a policy number.
- Click [Submit].
- Open the 'Financial Eligibility' form.
- Validate the 'Guarantor #1' field populated correctly with the guarantor added in the 'Demographics' section of the admission form of the client.
- Navigate to the 'Guarantor Selection' section.
- Validate the 'Subscriber Policy #' is populated correctly with the policy number of the guarantor added in the 'Demographics' section of the admission form of the client.
- Click [Submit].
NCPDP Response screen - Spelling error
Scenario 1: RXConnect - PM - NCPDP responses to RxConnect - Validating spelling error
SYSTEM.billing_guar_table - field validation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Form and Table Documentation (PM)
Scenario 1: SYSTEM.billing_guar_table' - field validations
Specific Setup:
- Guarantors/Payors:
- An existing non contract guarantor is identified that has data on file for the following field. Note the guarantor code/name and value from the field.
- Guarantors/Payors section:
- 837 Section:
- Value to Display in 2330B NM1-09/2430 SVD-01
- Review the help message associated with this field.
- Guarantor/Program Bulling Defaults:
- 837 Professional section:
- Payer Identification # (2010BB/2330B-NM1-09)
- 837 Institutional section:
- Payer Identification Number
Steps
- Open the 'Crystal Report' or any other data viewer.
- Query the 'SYSTEM.billing_guar_table' for the guarantors identified in the setup section.
- Verify the 'value_to_display_in_2330B_code' and 'value_to_display_in_2330B_value' fields are added to the 'SYSTEM.billing_guar_table.
- Verify that the 'value_to_display_in_2330B_code' and 'value_to_display_in_2330B_value' displays data correctly based on the data set up in the 'Value to Display in 2330B NM1-09/2430 SVD-01' field of the 'Guarantors/Payors' form and the 'Payer Identification # (2010BB/2330B-NM1-09)' field set up in the 'Guarantor/Program Billing Defaults' form.
- Close the report.
|
Topics
• Cross Episode Financial Eligibility
• Dictionary
• Guarantor/Payors
• Database Tables
|
|
Topics
• Program Maintenance
• Single Program Maintenance
• File Import
|
Various SQL views changed to SQL tables
Scenario 1: Validating SYSTEM.billing_837_d_report switched from a SQL view to an SQL table
Specific Setup:
- An 837 Dental report file has been created by the "Electronic Billing" process for 837 Dental files.
Steps
- Using the preferred method of viewing SQL tables, validate SYSTEM.billing_837_d_report is no longer an SQL view, and is now a table.
Scenario 2: Validating SYSTEM.billing_837_i_report switched from a SQL view to an SQL table
Specific Setup:
- An 837 Institutional report file has been created by the "Electronic Billing" process for 837 Institutional files.
Steps
- Using the preferred method of viewing SQL tables, validate SYSTEM.billing_837_i_report is no longer an SQL view, and is now a table.
Scenario 3: Validating SYSTEM.billing_837_p_report switched from a SQL view to an SQL table
Specific Setup:
- An 837 Professional report file has been created by the "Electronic Billing" process for 837 Professional files.
Steps
- Using the preferred method of viewing SQL tables, validate SYSTEM.billing_837_p_report is no longer an SQL view, and is now a table.
|
Topics
• 837 Dental
• 837 Institutional
• 837 Professional
|
Edit Service Information
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Charge Input
- Edit Service Information (Charge Fee Access)
Scenario 1: Edit Service Information – Change the Service Code.
Specific Setup:
- Registry Settings:
- Set 'Enable California Billing' Registry Setting Value to 'Y'.
- Set 'End Date California Billing' Registry Setting Value to a future date, allowing ample time for testing.
- Client
- An existing client or newly admitted client is used, where Client ID is noted.
Steps
- Open "Client Charge Input" form.
- Enter any value in 'Date of Service'.
- Enter the 'Client ID' created in the setup.
- Select desired value in 'Episode Number'.
- Enter group service code in 'Service Code'.
- Validate the message 'Enter The Number Of Clients In The Group' is received.
- Click [Cancel].
- Validate the message 'You Must Enter The Number Of Clients In The Group For Group Services' is received.
- Click[OK].
- Enter any code other than group code in 'Service Code'.
- Click [Submit].
- Click [No].
- Open "Client Ledger" form.
- Enter the 'Client ID' created in the setup.
- Click [All Episodes] in 'Claim/Episode/All Episodes'.
- Click [Simple] in 'Ledger Type'.
- Click[Process].
- Validate the services are filled with correct service code entered in previous steps in the report.
- Click [X].
- Close the form.
- Open the "Edit Service Information" form.
- Enter the Client ID created in the setup.
- Click [Select Service(s) To Edit].
- Select any service from the grid.
- Click [OK].
- Repeat Steps 5-21.
- Open "Edit Service Information (Charge Fee Access)" form.
- Repeat Steps 22-27.
|
Topics
• Edit Service Information
|
File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- File Import
- Quick Billing Rule Definition
Scenario 1: File Import: Quick Billing Rule Definition
Specific Setup:
- File Import:
- The 'Quick Billing Rule Definition' file type is added to the File Import.
- Create an import "File A" to add a new 'Quick Billing Rule Definition'
- Create an import "File B" to edit above 'Quick Billing Rule Definition'.
Steps
- Open the "File Import" form.
- Select the "Quick Billing Rule Definition" in the 'File Type' field.
- Select "Upload New File" in the 'Action' field.
- Click [Process Action].
- Select "File A".
- Select "Compile/Validate File" in the 'Action' field.
- Select "File A" in the 'Files(s)' field.
- Click [Process Action].
- Validate the message = 'Compiled'
- Click [OK].
- Select "Print File" in the 'Action' field.
- Select "File A" in the 'Files(s)' field.
- Click [Process Action].
- Validate the Report Viewer displays the contents of the file.
- Click [Close Report].
- Select "Post File" in the 'Action' field.
- Click [Process Action].
- Select "File A".
- Validate the message = 'Posted'
- Click [OK].
- Click [Discard].
- Click [Yes].
- Open the "Quick Billing Rule Definition" form.
- Click [Edit Existing] in Add New Or Edit Existing Rule Definition.
- Select Rule Description imported above from 'Rule' dropdown list.
- Validate the fields in the form.
- Click [Submit].
- Click [No].
- Follow steps 1-28,change the import file to "File B" for Edit Quick Billing Rule Definition File Import.
File Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- File Import
- Quick Billing Rule Definition
Scenario 1: File Import: Quick Billing Group Definition
Specific Setup:
- File Import:
- The 'Quick Billing Group Definition' file type is added to the File Import.
- Create an import "File A" to add a new 'Quick Billing Group Definition'
- Create an import "File B" to edit above 'Quick Billing Group Definition'.
Steps
- Open the "File Import" form.
- Select the "Quick Billing Group Definition" in the 'File Type' field.
- Select "Upload New File" in the 'Action' field.
- Click [Process Action].
- Select "File A".
- Select "Compile/Validate File" in the 'Action' field.
- Select "File A" in the 'Files(s)' field.
- Click [Process Action].
- Validate the message = 'Compiled'.
- Click [OK].
- Select "Print File" in the 'Action' field.
- Select "File A" in the 'Files(s)' field.
- Click [Process Action].
- Validate the Report Viewer displays the contents of the file.
- Click [Close Report].
- Select "Post File" in the 'Action' field.
- Click [Process Action].
- Select "File A".
- Validate the message = 'Posted'.
- Click [OK].
- Click [Discard].
- Click [Yes].
- Open the "Quick Billing Rule Definition" form.
- Click the [Quick Billing Group Definition] item.
- Click [Edit Existing] in Add New Or Edit Existing Group Definition.
- Select Group Definition imported above from 'Quick Billing Rule Group' dropdown list.
- Validate the fields in the form.
- Click [Submit].
- Click [No].
- Follow steps 1-28,change the import file to "File B" for Edit Quick Billing Group Definition File Import.
|
Topics
• Quick Billing
• File Import
• NX
|
'External Documents' widget - 'Care Team'
Scenario 1: 'External Documents' widget - Validate the 'Care Team' button
Specific Setup:
- The 'External Document' widget and 'Console Widget Viewer' are on the HomeView.
- A client has available CCD's (Client A).
Steps
- Select "Client A" and access the 'External Documents' widget.
- Click [Search].
- Validate a message is displayed stating: Match(es) found, # document(s) returned.
- Click [OK].
- Click [View] for any of the CCDs.
- Validate the CCD is displayed in the 'Console Widget Viewer'. Take note of the Care Team details.
- Click [Close All].
- Validate the CCD is no longer displayed.
- Click [Care Team] for the same CCD.
- Validate the Care Team details are displayed in the 'Console Widget Viewer' based on the Care Team section of the CCD.
- Click [Close All].
- Validate the Care Team details are no longer displayed.
'External Documents' widget - 'Status' column
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- External Documents Widget
Scenario 1: 'External Documents' widget - Validate the 'Status' column
Specific Setup:
- The 'External Document' widget and 'Console Widget Viewer' are on the HomeView.
- A client has available CCD's (Client A).
Steps
- Select "Client A" and access the 'External Documents' widget.
- Click [Search].
- Validate a message is displayed stating: Match(es) found, # document(s) returned.
- Click [OK].
- Validate that the 'External Documents' widget contains a new CCD.
- Validate the 'Status' field contains "New".
- Click [View] for the CCD.
- Validate the CCD detail is displayed in the 'Console Widget Viewer'.
- Validate the 'Status' field now contains "Viewed".
- Click [Save] in the 'Console Widget Viewer'.
- Validate a message is displayed stating: Saved.
- Click [OK].
- Validate the 'Status' field now contains "Saved".
- Click [Reconcile] in the 'Console Widget Viewer'.
- Validate the 'Clinical Reconciliation' form is displayed.
- Reconcile the desired items and file the form.
- Validate the 'External Documents' widget is displayed.
- Validate the 'Status' field now contains "Reconciled".
- Click [Close All].
Querying CCD's
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Query for External CCD
- CareConnect CCD Download
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].
- Validate message stating: "Match(es) found, # document(s) returned."
- Click [OK].
- 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 in a preview with CCD section details 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 that 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 that the 'provider_referred_to' field contains the provider ID selected in the previous steps.
- Validate that the 'provider_referred_to_name' field contains the provider name selected in the previous steps.
- Close the report.
Scenario 2: 'External Documents' widget - CCD Display
Specific Setup:
- The 'External Document' widget and 'Console Widget Viewer' are on the HomeView.
- A client has available CCD's (Client A).
Steps
- Select "Client A" and access the 'External Documents' widget.
- Click [Search].
- Validate a message is displayed stating: Match(es) found, # document(s) returned.
- Click [OK].
- Validate that the 'External Documents' widget contains a new CCD.
- Click [View].
- Validate that the CCD detail is displayed in the 'Console Widget Viewer'.
- Click [Save].
- Validate a message is displayed stating: Saved.
- Click [OK] and [Close All].
- Validate the CCD is no longer displayed in the 'Console Widget Viewer'.
- Validate the 'Status' for the CCD now contains "Saved".
- Click [View] for the same CCD.
- Validate that the CCD detail is displayed in the 'Console Widget Viewer'.
- Click [Save].
- Validate error message stated: "This document has already been saved".
- Click [OK] and [Close All].
Scenario 3: 'CareConnect CCD Download' - Search, Preview and Download CCDs
Specific Setup:
- A client must have available CCDs (Client A).
Steps
- Access the 'CareConnect CCD Download' form.
- Enter "Client A" in the 'Client Search' field.
- Validate message stating: "Match(es) found, # document(s) returned."
- Click [OK].
- Select any value in the 'Available CCD(s)' field.
- Click [Preview].
- Validate a 'Document Preview' of "Client A's" CCD is displayed.
- Click [Close All Documents and Exit].
- Enter the desired provider in the 'Provider Referred To' field.
- Select "Yes" in the 'Save for Reconciliation' field.
- Click [Download].
- Validate an "Information" message is displayed stating: Saved.
- Click [OK].
- 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 that 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 that the 'provider_referred_to' field contains the provider ID selected in the previous steps.
- Validate that the 'provider_referred_to_name' field contains the provider name selected in the previous steps.
- Close the report.
'External Documents' widget - 'Created Date To Display' filter
Scenario 1: 'External Documents' widget - Validate the 'Created Date To Display' filter
Specific Setup:
- The 'External Document' widget and 'Console Widget Viewer' are on the HomeView.
- A client has available CCD's that have been queried in the 'External Documents' widget on past dates (Client A).
Steps
- Select "Client A" and access the 'External Documents' widget.
- Click [Search].
- Validate a message is displayed stating: Match(es) found, # document(s) returned.
- Click [OK].
- Validate the 'Created Date to Display' field is displayed.
- Select "All" in the 'Created Date to Display' field.
- Validate the 'External Documents' widget displays all CCDs for the client from all dates.
- Select the current date in the 'Created Date to Display' field.
- Validate the 'External Documents' widget displays only CCDs from today.
- Click [View] for the desired CCD.
- Validate the CCD is displayed in the 'Console Widget Viewer'.
- Click [Close All].
'External Documents' widget - Document Status
Scenario 1: 'External Documents' widget - CCD Display
Specific Setup:
- The 'External Document' widget and 'Console Widget Viewer' are on the HomeView.
- A client has available CCD's (Client A).
Steps
- Select "Client A" and access the 'External Documents' widget.
- Click [Search].
- Validate a message is displayed stating: Match(es) found, # document(s) returned.
- Click [OK].
- Validate that the 'External Documents' widget contains a new CCD.
- Click [View].
- Validate that the CCD detail is displayed in the 'Console Widget Viewer'.
- Click [Save].
- Validate a message is displayed stating: Saved.
- Click [OK] and [Close All].
- Validate the CCD is no longer displayed in the 'Console Widget Viewer'.
- Validate the 'Status' for the CCD now contains "Saved".
- Click [View] for the same CCD.
- Validate that the CCD detail is displayed in the 'Console Widget Viewer'.
- Click [Save].
- Validate error message stated: "This document has already been saved".
- Click [OK] and [Close All].
Scenario 2: 'External Documents' widget - Validate the 'Status' column
Specific Setup:
- The 'External Document' widget and 'Console Widget Viewer' are on the HomeView.
- A client has available CCD's (Client A).
Steps
- Select "Client A" and access the 'External Documents' widget.
- Click [Search].
- Validate a message is displayed stating: Match(es) found, # document(s) returned.
- Click [OK].
- Validate that the 'External Documents' widget contains a new CCD.
- Validate the 'Status' field contains "New".
- Click [View] for the CCD.
- Validate the CCD detail is displayed in the 'Console Widget Viewer'.
- Validate the 'Status' field now contains "Viewed".
- Click [Save] in the 'Console Widget Viewer'.
- Validate a message is displayed stating: Saved.
- Click [OK].
- Validate the 'Status' field now contains "Saved".
- Click [Reconcile] in the 'Console Widget Viewer'.
- Validate the 'Clinical Reconciliation' form is displayed.
- Reconcile the desired items and file the form.
- Validate the 'External Documents' widget is displayed.
- Validate the 'Status' field now contains "Reconciled".
- Click [Close All].
|
Topics
• External Document Widget
• CCD's
• Query for External CCD
|
| |
