Client Search - Search on subscriber policy # or Medicaid #
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Admission
- Financial Eligibility
Scenario 1: Financial Eligibility - Client Search Change Subscriber Policy#
Specific Setup:
- Admit a test client.
- Using the "Financial Eligibility" form:
- Populate all required fields.
- Populate "Subscriber Policy#. Note the data.
- Populate "Subscriber Medicaid#". Note the data.
Steps
- Using the "Financial Eligibility" form:
- Change the "Subscriber Policy#" and "Subscriber Medicaid# values. Note the values.
- File the form.
- From the Home View, enter the value that was entered into "Subscriber Policy#" from Step 1.
- Validate it returns the correct result from the search on that value.
- From the Home View, enter the value that was entered into "Subscriber Medicaid#" from Step 1.
- Validate it returns the correct result from the search on that value.
Scenario 2: Financial Eligibility - Add/Edit/Delete financial eligibility record
Specific Setup:
- Guarantor/Payors:
- An existing guarantor is identified. Note the guarantor’s code/name.
- Admission:
- A new client is created, or an existing client is identified who does not have 'Fast Financial Eligibility', 'Family Financial Eligibility', 'Financial Eligibility', or 'Cross Episode Financial Eligibility' records created (Client A).
Steps
- Select "Client A" and open the 'Financial Eligibility' form.
- Validate the 'Admission Date', 'Episode Number', 'Program', and 'Social Security Number' fields are populated, disabled, and readable.
- Select the 'Guarantor Selection' tab.
- Validate the 'Guarantor Information' grid is required.
- Validate the 'Guarantor #' field is required.
- Select any value from the 'Guarantor #' field.
- Validate the 'Guarantor Plan' field is required.
- Select any value from the 'Guarantor Plan' field.
- Validate the 'Customize Guarantor Plan' field is required.
- Select any value from the 'Customize Guarantor Plan' field.
- Validate the 'Eligibility Verified' field is required.
- Select any value from the 'Eligibility Verified' field.
- Validate the 'Coverage Effective Date' field is required.
- Set the 'Coverage Effective Date' field to any value.
- Validate the 'Client's Relationship To Subscriber' field is required.
- Select "Self" from the 'Client's Relationship To Subscriber' field.
- Validate the 'Subscriber's Name', the 'Subscriber's Address - Street Line 1', the 'Subscriber Address - Zip', the 'Subscriber Address - City', the 'Subscriber Address - State', the 'Subscriber's Social Security #', and the 'Subscriber Sex' fields are required and populate with "Client A".
- Tab down until the 'Subscriber Address - County' field is in focus.
- Press the 'space' key.
- Validate the search field is in focus.
- Enter any value and validate the expected search results display.
- Click the 'Subscriber Address - County' field so it is in focus again.
- Press any letter and validate the expected result displays.
- Validate the 'Subscriber Assignment Of Benefits' field is required.
- Select any value from 'Subscriber Assignment Of Benefits' field.
- Validate the 'Subscriber Release of Info' field is required.
- Select any value from the 'Subscriber Release of Info' field.
- Validate the 'Subscriber's Covered Days' field is required.
- Validate the 'Maximum Covered Dollars' field is required.
- Select the 'Financial Eligibility' tab.
- Select the Guarantor previously defined in the 'Guarantor #1' field.
- Click [Submit].
- Select "Client A" and open the 'Financial Eligibility' form.
- Edit the financial eligibility record that was entered.
- Validate the data entered is retrieved and displayed.
- Click [Add New Item].
- Validate that a new blank row is added.
- Click [Delete Selected Item].
- Validate the "Are you Sure?" dialogue.
- Click [Yes].
- Validate that the blank row is deleted successfully.
- Exit the form.
|
Topics
• Admission
• Financial Eligibility
|
Web Services - PostingAdjustmentCodes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Posting/Adjustment Codes Definition
Scenario 1: 'PostingAdjustmentCodes' Web Service - Verification Of 'AddPostingAdjustmentCodes' and 'UpdatePostingAdjustmentCodes' filing
Specific Setup:
- Web service testing tool:
- SoapUI or any other web service testing tool needs to be set up to test this scenario.
Steps
- Create a SoapUI project for Avatar PM 'PostingAdjustmentCodes' web service.
- Submit a request for 'AddPostingAdjustmentCodes' method to add new posting adjustment code. Note the posting code/definition.
- Verify the 'PostingAdjustmentCodes' web service files successfully and responds with confirmation message for 'AddPostingAdjustmentCodes' method. <Message>Posting/Adjustment Codes Input web service has been filed successfully.</Message>.
- Verify the 'PostingAdjustmentCodes' web service responds with successful status value on successful filing of 'AddPostingAdjustmentCodes' method. Example: <Status>1</Status>.
- Open 'Posting/Adjustment Codes Definition' form.
- Verify the newly added posting adjustment code displays correctly with all the values entered through web service.
- Note the posting code and code definition.
- Navigate to the SoapUI.
- Submit a request for 'UpdatePostingAdjustmentCodes' method to update a code definition for the recently added posting adjustment code in above steps.
- Enter different code definition for the posting code added above. Note the posting definition.
- Verify the 'PostingAdjustmentCodes' web service files successfully and responds with confirmation message for 'UpdatePostingAdjustmentCodes' method. <Message>Posting/Adjustment Codes Input web service has been filed successfully.</Message>
- Verify the 'PostingAdjustmentCodes' web service responds with successful status value on successful filing of 'UpdatePostingAdjustmentCodes' method. Example: <Status>1</Status>.
- Open 'Posting/Adjustment Codes Definition' form.
- Verify the recently updated posting adjustment code displays correct code definition updated through web service.
Registry Settings - Enable Alternative Service Location Fields - Electronic billing validation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Ledger
- Electronic Billing
Scenario 1: 837 Error Report - Items outside of date range selected for billing
Specific Setup:
- Registry Setting:
- 'Enable Alternative Service Location Fields' is enabled.
- Note the fields that will be added to 'Edit Service Information'.
- Identify a client with unbilled services. Note the service date range and the guarantor.
- Edit the last service to add data for only the fields enabled by the above registry setting.
Steps
- Open ‘Electronic Billing’.
- Create a bill for the services that does not include the date of services for the edited service.
- Print the report.
- Validate that no error is reported for the date of service of the edited bill.
- Close the report.
- Close the form.
Scenario 2: Registry Settings - Enable Alternative Service Location Fields - Validating electronic billing
Specific Setup:
- Registry settings:
- The 'Avatar PM->Billing->Client Charge Input->->->Enable Alternative Service Location Fields' registry setting is enabled. Please note: This is a hidden registry setting and may require a Netsmart Support Associate's assistance in checking and setting.
- Guarantors/Payors:
- An existing guarantor is identified to be used. 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.
- 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.
- Diagnosis:
- An admission diagnosis record is created for the client.
- Client Charge Input:
- 5-6 services are rendered to the client in one month and other 5-6 services in another month. Note service dates, service code.
- Client Ledger:
- A service distributed correctly to the assigned guarantor.
Steps
- Open the 'Edit Service Information' form.
- Select a desired client.
- Validate the alternative service location fields listed on the form are. Facility Location Name, Facility Location State, Facility Location Code Qualifier, Facility Location Code Identifier, Facility Location Address Street, Facility Location City, Facility Location Zip Code.
- Click [Select Services to Edit].
- Select one of the service from the second month to be edited.
- Select / enter desired values for one of the new fields added via the registry setting.
- Leave other fields blank.
- File the form.
- Open the 'Electronic Billing' form.
- Select 837 Professional or 837 Institutional in 'Billing Form' field.
- Select values for 837 bill generation in the 'Type of Bill', 'Individual or All Guarantors' and 'Billing Type' fields.
- Select 'Sort File' in the 'Billing Options' field.
- Select/enter values for service inclusion in 'All Clients or Interim Billing Batch' and 'Program(s)' fields.
- Select only first month of service to bill.
- Select/enter values for 'Create Claims' (and 'Date of Claim' if 'Yes'), 'First Date of Service to Include' and 'Last Date of Service to Include' fields.
- Select/enter values for any other bill sorting criteria fields as required/desired.
- Click [Process].
- Verify the bill compiles successfully.
Guarantors/Payors - Database Management
Scenario 1: 'Guarantors/Payors' - Form Verification
Specific Setup:
- Avatar State Forms Registry Setting 'Enable Texas TMHP Billing' must be enabled.
Steps
- Open the Avatar PM 'Guarantors/Payors' form.
- Select Add or Edit action in 'Add New or Edit Existing Guarantor' field.
- Enter new (or select existing) Guarantor Code.
- Complete all required/desired fields in main section of 'Guarantors/Payors' form.
- Navigate to '837' section of 'Guarantors/Payors' form.
- Ensure that the 'TMHP Waiver Skip 2300-REF Segment' field is available in form.
- If 'Yes' is selected in this field, 837 Professional files sorted/created for this Guarantor via 'Electronic Billing' forms/functions (and subject to 'Enable Texas TMHP Billing' functionality/values) will conditionally skip/omit the 2300-REF segment/value for 'TMHP Waiver Reference Number'.
- Select value for 'TMHP Waiver Skip 2300-REF Segment' field (and any other desired fields in '837' section of form).
- Navigate to main section of 'Guarantors/Payors' form.
- Click 'File' button to save/file Guarantor/Payor definition information.
- Select 'Edit' action and select previously filed Guarantor Code.
- Navigate to '837' section of 'Guarantors/Payors' form.
- Ensure that previously selected/filed value for 'TMHP Waiver Skip 2300-REF Segment' field is present/selected in form.
Managed Care Authorizations - Monthly Limitation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Financial Eligibility
- Diagnosis
- Service Codes
- Managed Care Authorizations
Scenario 1: Managed Care Authorizations - Monthly Limitations - Scheduling Calendar
Specific Setup:
- Managed Care Authorizations:
- Identify a client with a 'Managed Care Authorization’ that contains a monthly limitation.
- Note the guarantor that the authorization is for.
- Note the limitation and if any of the units/dollars or visits have been used.
- Guarantors/Payors: Note the value of the ‘Verification Level For Authorizations For Appointment Scheduling’.
- ‘Warn User If Authorization Is Missing’ will display a warning in scheduling but allow the user to file the appointment.
- Disallow Service If Authorization Is Missing’ will display an error message and prevent the appointment from being filed.
Steps
- Open ‘Scheduling Calendar’.
- Schedule an appointment that will not cause the service to be over the monthly limitation.
- Validate that the appointment files successfully.
- Schedule an appointment on the same day, with a different service code, or on the following day that will cause the service to be over the monthly limitation.
- Validate that the appropriate warning message or error message displays.
- If the warning message displays, click [OK] and [Submit].
- Verify that the appointment filed successfully.
- If the error message displays, click [OK] and validate that the ‘Service Code’ field is null and discard the form.
- Validate that the ‘Are you sure you want to Close without saving’ message is received.
- Click [Yes].
- Click [Dismiss].
|
Topics
• Web Services
• 837 Professional
• 837 Institutional
• NX
• 835
• Guarantor/Payors
• Managed Care Authorizations
|
Form Bundler - CWS
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Form Bundler: Create and File a New Sequential Bundle
Specific Setup:
- User must have access to the form 'Form Bundler' in 'User Definition'.
- A client must be admitted to an active episode (Client A).
Steps
- Access the 'Form Bundler' form.
- Validate a "Form Bundler" dialog is displayed stating: Edit Existing Form Bundle or Create New Form Bundle.
- Click [Create New] and [Print Current Menu].
- Validate a "Form Bundler" menu is displayed.
- Click [Dismiss].
- Enter any value (Form Bundle A) in the 'Form Bundle Description' field.
- Select "Sequential" from the 'Type of Bundle' field.
- Select any value from the 'Menu to Place Form Bundle Under' field.
- Select the 'Included Forms' tab.
- Click [Add New Item].
- Select any value (ex. 'Call Intake') from the 'Form' field.
- Click [Add New Item].
- Select any value of the same entity database as the one selected in the previous step (ex. 'Assign Permanent MR#') from the 'Form' field.
- Click [Submit].
- Access the 'Display Form Bundle' form.
- Select "All" from the 'Individual or All Form Bundles' field.
- Click [Process].
- Validate a Display Form Bundle report is displayed
- Validate the report displays "Form Bundle A".
- Click [Dismiss].
- Validate a "Form Return" dialog is displayed stating: Processing report has completed. Do you wish to return to form?
- Click [No].
- Select "Client A" and access the form bundle.
- Select any value from the 'Select Episode' field.
- Click [Add].
- Validate that the first form in the bundle opens.
- Complete the required fields and click [Submit].
- Validate that the next form in the bundle opens for "Client A" with the episode that was selected upon entering the first form of the bundle.
- Click [Add]
- Complete the required fields and click [Submit].
- Validate that the next form in the bundle opens for "Client A" with the episode that was selected upon entering the first form of the bundle
- Click [Add]
- Complete the required fields and click [Submit].
- Compete each of the remaining forms in the bundle and click [Submit].
- Validate each form files successfully.
CCBHC PPS Compile Report
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- CCBHC PPS Compile
- Service Fee/Cross Reference Maintenance
- Diagnosis
- Financial Eligibility
- Service Codes
- Client Charge Input
- Client Ledger
- CCBHC PPS Service Definition
Scenario 1: CCBHC PPS Compile - field validation
Specific Setup:
- The agency processes CCBHC billing and the CCBHC setup is complete.
- Client 1 has the following:
- Is enrolled in a program on or after the CCBHC PPS Service Definition effective date.
- A financial eligibility record for a CCBHC guarantor.
- Three closed PPS non-enumerated services after the CCBHC PPS Service Definition effective date. Note each date of service.
- Client 2 has the following:
- Is enrolled in a program on or after the CCBHC PPS Service Definition effective date.
- A financial eligibility record for a CCBHC guarantor.
- Three closed PPS non-enumerated services after the CCBHC PPS Service Definition effective date, and after the dates of service for Client 1. Note each date of service.
- Client Ledger is viewed to ensure the service distributed to the correct guarantor.
Steps
- Open 'CCBHC PPS Compile'.
- Validate the 'Client ID' field exists.
- Enter the first date of service for Client 1 in 'Start Date'.
- Enter the last date of service for Client 1 in 'End Date'.
- Enter the 'Client ID' for Client 1.
- Click [Compile & Post Services].
- Validate that the 'CCBHC Compile Complete' message is received.
- Click [OK].
- Select the 'PPS Compile Report' section.
- Enter the first date of service for Client 1 in 'Start Date'.
- Enter the last date of service for Client 1 in 'End Date'.
- Enter the 'Client ID' for Client 1.
- Click [Run Report].
- Validate that the report contains only data for Client 1 and the services are within the 'Start Date' to 'End Date' range.
- Close the report.
- Select the 'PPS Compile' section.
- Enter the first date of service for Client 1 in 'Start Date'.
- Enter the last date of service for Client 2 in 'End Date'.
- Click [Compile & Post Services].
- Click [OK].
- Select the 'PPS Compile Report' section.
- Enter the first date of service for Client 1 in 'Start Date'.
- Enter the last date of service for Client 2 in 'End Date'.
- Click [Run Report].
- Validate that the report contains data for Client 1 and Client 2 and the services are within the 'Start Date' to 'End Date' range.
Client Charge Input - Incident-to-Practitioner
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Charge Input
- Practitioner Enrollment
- Practitioner Termination
Scenario 1: Client Charge Input - Incident-to-Practitioner - Terminated Practitioner
Specific Setup:
- Registry Setting: Enable Incident-To Practitioner = Y.
- Practitioner: Identify a terminated practitioner.
Steps
- Open ‘Client Charge Input’.
- Create a charge for any client using desired data.
- Enter the terminated practitioner in ‘Practitioner’.
- Validate that an error message is received.
- Click [OK].
- Enter an active practitioner in ‘Practitioner’.
- Enter the terminated practitioner in ‘Incident-to-Practitioner’.
- Validate that an error message is received.
- Click [OK].
- Enter an active practitioner in ‘Incident-to-Practitioner’.
- Click [Submit].
- Close the form.
Client Account Service Report
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Account Services Report
- Financial Eligibility
- Diagnosis
- Client Charge Input
- Electronic Billing
- Client Ledger
- Individual Cash Posting (PM)
- Service Codes
- Service Fee/Cross Reference Maintenance
- Create Interim Billing Batch File
- Front Desk Information
Scenario 1: Client Account Services Report - process and validate fields
Specific Setup:
- User Definition has been used to give the tester access to the report: Avatar PM > Client Management > Account Management > Client Payment History Report. Note the ‘User Description’.
- Client:
- In 'Financial Eligibility' the client is assigned a 'Self-Pay' guarantor and at least one non 'Self-Pay' guarantor.
- The client has services have been claimed by the non 'Self-Pay' guarantor and a portion has been distributed to the 'Self-Pay' guarantor.
- Note the 'Service Code Definition'.
- Note the service fees.
- Note the claim number and the date of the claim.
- Payments have been made on the services by the non 'Self-Pay' guarantor and the client.
- Note system date the payments were applied.
- Note the amounts applied and by which guarantor, And the amounts.
- Note the 'Posting/Adjustment Code Definition'.
- Use ‘Admission’ or ‘Admission (Outpatient)’ to note:
- ‘Episode’
- ‘Admit Date’
- 'Discharge Date’
- ‘Program’
- ‘Type of Admission’
Steps
- Open 'Client Account Services Report'.
- Enter the 'Client'.
- Enter the desired 'Service Start Date'.
- Enter the desired 'Service End Date'.
- Click [Process].
- Validate the admission information, which includes the 'Episode', Admit Program', 'Admit Type', 'Admit Date', and 'Discharge Date'.
- Validate the report data for the 'Client 'Payments', which includes the 'Payment Date', 'Description', 'Amount' and 'Notes'.
- Validate the service information, which includes the 'Service Date', 'Service Code Definition', 'Staff', 'Episode', 'Transaction Date', 'Transaction Type', 'Transaction Amount', 'Client Responsibility', 'Insurance Responsibility', 'Guarantor', 'Claim #' and 'Claim Date'.
Scenario 2: Client Account Services Report - Validating payment amount
Specific Setup:
- Guarantors/Payor:
- A self pay guarantor is identified. Note the guarantor's code/value.
- Client:
- An existing client, with the above guarantor in Financial Eligibility, is selected, or a new client is admitted and assigned the above guarantor in Financial Eligibility. Note the client's id, admission date and admission program.
- A diagnosis record is created for the client.
- Service Code:
- Select a service code that has a Service Fee/Cross Reference Maintenance record, noting the 'Fee’.
- Recurring Client Charge Input:
- Services are rendered to the client that will create charges that total more than $10,000.00. Note the service date range.
- Client Ledger:
- The service distributed to the self pay guarantor.
Steps
- Open desired form and post a payment greater than $10,000.00 to the client. Note the payment date.
- Validate that the generated receipt displays the full payment amount.
- Close the receipt.
- Close the form.
- Open the 'Client Ledger' for the client / payment date and validate that the full payment amount displays.
- Close the report.
- Close the form.
- Open 'Client Account Services Report'.
- Select the client and the payment date.
- Click [Process].
- Validate that the report displays the full payment amount.
- Close the report.
- Close the form.
- Repeat steps 1 -13 with a payment amount of less than $1,000.00.
|
Topics
• Diagnosis
• Chart View
• CCBHC
• Client Charge Input
• Practitioner
• NX
• Billing
|
File Import - [Support Only] Guarantor Nature
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Financial Eligibility
- Client Ledger
- File Import
- Guarantor Nature File Import
- Cross Episode Financial Eligibility
- Family Financial Eligibility
Scenario 1: File Import - [Support Only] Guarantor Nature – Non-contract guarantor to Contract - 'If Customized Retain Customization' = 'Y' in File Import and client has two guarantors
File Import - Service Authorization - Member
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- File Import
- Service Authorization
- Financial Eligibility
- Client Ledger
- Guarantor Nature File Import
- Cross Episode Financial Eligibility
- Family Financial Eligibility
Scenario 1: File Import - Service Authorization - Verification of Member Service Authorization
Specific Setup:
- Registry Setting:
- The 'Avatar MSO->Membership Management->Member Enrollment->->->Require Member Enrollment' registry setting is set to 'Y'.
- The 'Avatar PM->System Maintenance->File Import->->->Import File Delimiter' is set to '2'.
- Member Enrollment:
- An existing member is identified, or a new member is created who has a 'Funding Source' record in 'Member Specific Information' and has no 'Service Authorization' record for the 'Funding Source'. Note the member id and funding source.
- The 'File Import' file is created to add an 'MSO - Service Authorization - Member' for Member and the 'Funding Source.
- Access to 'Crystal Reports' or other SQL reporting tool.
- User Definition:
- Access permission to Avatar MSO SQL table 'SYSTEM.file_import_mem_svc_auth'.
Steps
- Open the 'File Import' form in Avatar PM.
- Select File Type '[Avatar MSO] Service Authorization - Member'.
- Validate ‘Upload File’ is selected in the ‘Action’.
- Select ‘[Avatar MSO] Service Authorization – Member’ in ‘File Type’.
- Click [Process Action].
- Select the file that will add the authorization for the member.
- Verify the file uploads successfully.
- Select ‘Compile/Validate File’ in ‘Action’.
- Select the file that is recently uploaded successfully.
- Click [Process Action].
- Verify the file compiles successfully.
- Select ‘Post File’ in ‘Action’.
- Select the file that is recently compiled successfully.
- Click [Process Action].
- Verify the file posted successfully.
- Open the 'Service Authorization' form.
- Select a client that is used in the file import file.
- Verify the new authorization record is created.
- Validate all the information entered during file import are displayed correctly in the form.
Scenario 2: File Import - [Support Only] Guarantor Nature – Non-contract guarantor to Contract - 'If Customized Retain Customization' = 'Y' in File Import and client has two guarantors
|
Topics
• Guarantor/Payors
• File Import
• NX
|
Remittance Functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Remittance Processing Widget
- Diagnosis
- Financial Eligibility
- Client Charge Input
- Create Interim Billing Batch File
- Electronic Billing
- Client Ledger
- Payment Acknowledgement
Scenario 1: Remittance Processing widget - Create/Edit/Delete Batch
|
Topics
• NX
|
Database Management - Tables
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Electronic Billing
- Create Interim Billing Batch File
- Client Ledger
Scenario 1: 837 Professional billilng when 'Enable Multiple Add-On Code Per Primary Code Functionality' = Y.
Specific Setup:
- The following registry setting has a value of 'Y': Avatar PM->System Maintenance->Service Code Maintenance->->->Enable Multiple Add-On Code Per Primary Code Functionality.
- Dictionary Update has been used to update 'Other Tabled File, 291, Service Code Type' to have a value of 'Yes' in the extended dictionary 'Allow Multiple Add-On Code Definition' for all dictionary codes.
- A 'Service Code' identified with a 'Service Code Category' of 'Primary Code' has at least two values selected in 'Select Multiple Add-On Code'.
- An outpatient client is identified. Note the program. The client has an active diagnosis record, and an active financial eligibility record, noting the financial class.
- A service has been created for the above 'Service Code'. Note the date of service. The service has been closed.
- Use 'Client Ledger' to note the fee for the 'Service Code' and for each 'Add-On Code'. Note the total fee.
Steps
- Open 'Electronic Billing'.
- Create an '837 Professional' bill for the service.
- Review the dump file to validate that the amount in the 'CLM' is equal to the total fee and that the amounts in the 'SV1' segments is equal to the total fee.
- Close the dump file.
- Close the form.
- Query the SYSTEM.billing_tx_master table. Locate the 'Service Code' selected in Setup.
- Validate that the 'multi_addon_svc_code' displays all add-on service code numbers selected in the primary service code .
- Validate that the 'multi_addon_svc_value' displays all add-on service code descriptions selected in the primary service code .
|
Topics
• Database Management
|
Chart View - Consent For Access
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Consent For Access - Validating chart view - Add/edit consent for access
Specific Setup:
- Have the 'Consent For Access' form added to a user's 'Chart View'.
- Have client with a record filed in form 'Consent For Access' form.
Steps
- Open the ‘Consent For Access’ form.
- Select the ‘External Network’ section.
- Click [Add A New Item].
- Select ‘Network’ in the ‘Consent For’ field.
- Select desired network in the ‘Network’ dropdown.
- Select desired value in the 'Consent to Opt In/ Opt Out' field.
- Set ‘Start Date’ to desired date.
- Select the ‘Referral’ section.
- Click [Add A New Item].
- Select desired value in the 'Provider' field.
- Select ‘Network’ in the ‘Consent For’ field.
- Select desired value in the 'Consent to Opt In/ Opt Out' field.
- Set ‘Start Date’ to desired date.
- Click [Submit].
- Open the ‘Consent For Access’ form.
- Validate the data displays as it was entered.
- Select the client that has a record filed in the 'Consent For Access' form.
- Open 'Chart View' for that client.
- Validate a 'Consent For Access' form is displayed in the left pane of the chart view.
- Click on the 'Consent For Access' form name.
- Validate all the information entered in the 'External Network' and 'Referral' tab of the 'Consent For Access' form are displayed correctly.
- Open the ‘Consent For Access’ form.
- Select the ‘External Network’ section.
- Add/update information for the client.
- Select the ‘Referral’ section.
- Add/update information for the client.
- Click [Submit].
- Open 'Chart View' for that client.
- Validate a 'Consent For Access' form is displayed in the left pane of the chart view.
- Click on the 'Consent For Access' form name.
- Validate all the information entered / updated in the 'External Network' and 'Referral' tab of the 'Consent For Access' form are displayed correctly.
|
Topics
• Consent for Access
• NX
|
Client Search - 'Alternate Lookup By Room' registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Validate the 'Alternate Lookup By Room' registry setting
Specific Setup:
- Two clients (Client A & Client B) must be admitted into inpatient episodes in the same room (Room A).
- The registry setting "Include Active Room Number with Client" is set to "1".
Steps
- Access the 'Registry Settings' form.
- Enter "Alternate Lookup By Room" in the 'Limit Registry Settings to the Following Search Criteria' field.
- Click [View Registry Settings].
- Validate the 'Registry Setting' field contains: Avatar PM->Client Information->Client Lookup->->->Alternate Lookup By Room.
- Validate the 'Registry Setting Detail' field contains: Selecting 'Y' will add an alternate search for clients by room number in the My Clients widget and Client Search. This must be an exact match and will look at the 'Include Active Room Number With Client Name' registry setting to potentially parse the room number. Select 'N' to disable this functionality.
- Enter "Y" in the 'Registry Setting Value' field.
- Click [Submit] and close the form.
- Search for "Room A" in the 'Search Clients' field.
- Validate both "Client A" and "Client B" are displayed.
- Access the 'Progress Notes (Group and Individual)' form.
- Enter "Room A" in the 'Select Client' field.
- Validate "Client A" and "Client B" are displayed.
- Close the form.
- Access the 'Client Ledger' form.
- Enter "Room A" in the 'Client ID' field.
- Validate "Client A" and "Client B" are displayed.
- Close the form.
- Access the 'Account Registration' form.
- Enter "Room A" in the 'Select Client' dialog.
- Validate "Client A" and "Client B" are displayed.
- Click [Cancel].
- Access the 'Service Authorization' form.
- Enter "Room A" in the 'Select Client' dialog.
- Validate "Client A" and "Client B" are displayed.
- Click [Cancel].
- Access the 'Registry Settings' form.
- Enter "Alternate Lookup By Room" in the 'Limit Registry Settings to the Following Search Criteria' field.
- Click [View Registry Settings].
- Validate the 'Registry Setting' field contains: Avatar PM->Client Information->Client Lookup->->->Alternate Lookup By Room.
- Enter "N" in the 'Registry Setting Value' field.
- Click [Submit] and close the form.
- Search for "Room A" in the 'Search Clients' field.
- Validate "Client A" and "Client B" are not displayed.
- Access the 'Progress Notes (Group and Individual)' form.
- Enter "Room A" in the 'Select Client' field.
- Validate "Client A" and "Client B" are not displayed.
- Close the form.
- Access the 'Client Ledger' form.
- Enter "Room A" in the 'Client ID' field.
- Validate "Client A" and "Client B" are not displayed.
- Close the form.
- Access the 'Account Registration' form.
- Enter "Room A" in the 'Select Client' dialog.
- Validate "Client A" and "Client B" are not displayed.
- Click [Cancel].
- Access the 'Service Authorization' form.
- Enter "Room A" in the 'Select Client' dialog.
- Validate "Client A" and "Client B" are not displayed.
- Click [Cancel].
|
Topics
• Registry Settings
• Client Search
|
Avatar PM - Support for Mobile CareGiver+
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Alternate Addresses
Scenario 1: Client Alternate Addresses - Form Validations
Specific Setup:
- The 'Enable Client Alternate Addresses' registry setting must be set to "Y".
- A client is admitted in an existing episode (Client A).
Steps
- Access the 'Client Alternate Addresses' form.
- Select "Client A" in the 'Client' field.
- Select "Add" in the 'Add/Edit' field.
- Enter the desired value in the 'Description' field.
- Enter the desired date in the 'Address Start Date' field.
- Enter the desired date in the 'Address End Date' field.
- Enter the desired value in the 'Address Line 1' field.
- Enter the desired value in the 'Address Line 2' field.
- Enter the desired value in the 'Zip' field.
- Enter the desired value in the 'City' field.
- Select the desired value in the 'State' field.
- Enter the desired value in the 'Contact Name field.
- Enter the desired value in the 'Contact Phone' field.
- Enter the desired value in the 'Address Notes' field.
- Select "Yes" in the 'Enabled' field.
- Click [File].
- Validate a message is displayed stating: Saved.
- Click [OK].
- Validate the 'Client' field contains "Client A".
- Select "Edit" in the 'Add/Edit' field.
- Validate the 'Select Existing Address' field contains the alternate address filed in the previous steps with the 'Address Start Date', 'Address End Date', and 'Description'.
- Select the address filed in the previous steps in the 'Select Existing Address' field.
- Validate all previously filed data is displayed.
- Close the form.
- Access Crystal Reports or other SQL Reporting Tool.
- Select the PM namespace.
- Create a report using the 'SYSTEM.client_alternate_address' SQL table.
- Validate there is a row for "Client A" will all previously filed data.
- Close the report.
Scenario 2: Validate the 'Enable Alternate Client Addresses' registry setting
Steps
- Access the 'Registry Settings' form.
- Enter "Client Alternate Addresses" in the 'Limit Registry Settings to the Following Search Criteria' field.
- Click [View Registry Settings].
- Validate the 'Registry Setting' field contains "Avatar PM->Client Management->Client Information->->->Enable Client Alternate Addresses".
- Validate the 'Registry Setting Detail' field contains "Selecting 'Y' will add the 'Client Alternate Addresses' form to the menu. Selecting 'N' will remove the form from the menu."
- Validate the 'Registry Setting Value' field contains "N" by default.
- Enter "Y" in the 'Registry Setting Value' field.
- Click [Submit] and close the form.
- Access the 'User Definition' form.
- Select the logged in user in the 'Select User' field.
- Select the "Forms and Tables" section.
- Click [Select Forms for User Access].
- Validate the 'Client Alternate Addresses' form is available for selection under "Avatar PM".
- Select read/write permissions for the form.
- Click [OK] and [Submit].
- Refresh forms.
- Access the 'Client Alternate Addresses' form.
- Validate the form displays as expected.
- Close the form.
- Access the 'Registry Settings' form.
- Enter "Client Alternate Addresses" in the 'Limit Registry Settings to the Following Search Criteria' field.
- Click [View Registry Settings].
- Validate the 'Registry Setting' field contains "Avatar PM->Client Management->Client Information->->->Enable Client Alternate Addresses".
- Enter "N" in the 'Registry Setting Value' field.
- Click [Submit] and close the form.
- Refresh forms.
- Validate the 'Search Forms' search no longer returns the 'Client Alternate Addresses' form since disabling the registry setting removes the form from the menu.
Scenario 3: Dictionary Update - Validate the 'Location' dictionary
Steps
- Access the 'Dictionary Update' form.
- Select "Client" in the 'File' field.
- Select "Data Element Number" in the 'Data Element' field.
- Select "(10006) Location" in the 'Data Element' field.
- Enter the desired value in the 'Dictionary Code' field.
- Enter the desired value in the 'Dictionary Value' field.
- Validate the 'Extended Dictionary Data Element' field contains "(587) Place Of Service (Mobile CareGiver+)".
- Select "(587) Place Of Service (Mobile CareGiver+)" in the 'Extended Dictionary Data Element' field.
- Select the desired value in the 'Extended Dictionary Value (Single Dictionary)' field.
- Click [Apply Changes] & Click [OK].
- Select the "Print Dictionary" section.
- Select "Client" in the 'File' field.
- Select "Data Element Number" in the 'Data Element' field.
- Select "(587) Place Of Service (Mobile CareGiver+)" in the 'Data Element' field.
- Click [Print Dictionary].
- Validate the location dictionary is displayed with the place of service filed in the previous steps.
- Click [Close] and close the form.
|
Topics
• Registry Settings
• Client Alternate Addresses
• Dictionary
|
837 Billing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Electronic Billing
- Client Ledger
- Spreadsheet Remittance Posting
Scenario 1: 837 Institutional Bill - - Running a bill for the PPS guarantor when the services are transferred to the PPS guarantor
Specific Setup:
- Client A: Has closed services that will bill to a primary guarantor that is not a PPS Guarantor. The client’s secondary guarantor is a PPS Guarantor.
- Crete Interim Billing Batch File is used to create a batch to use in billing.
Steps
- Open an 'Electronic Billing' form.
- Compile a Claimed 837 Institutional using the interim billing batch for the primary guarantor.
- Open the 'Spreadsheet Remittance Posting' for the client.
- Post a transfer service from the primary guarantor to the PPS guarantor.
- Open an 'Electronic Billing' form.
- Run an 837-Institutional bill for the PPS guarantor and the program.
- Fill out the date of service fields with the first date of service and the last date of service for the client's episode.
- Process the EB837 billing.
- Verify the bill compiles successfully.
- Verify that the correct services are contained in the dump file.
- Close the form.
|
Topics
• 837 Institutional
• NX
|
PM - CPT Codes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: 'CPT Code Definition' - Verification of American Medical Association-Provided CPT Code Values
Steps
- Open 'CPT Code Definition' form.
- Select 'Edit' action in 'Add/Edit/Delete CPT Code' field.
- In 'CPT Service Code' field, enter search term using CPT Code Description (AMA 'Consumer Descriptor' term) or CPT Code.
- Ensure 'CPT Service Code' field search results include American Medical Association-provided CPT Service Code(s) for search term/code entered.
- Select CPT Code from 'CPT Service Code' search results.
- Confirm value in 'CPT Code Description' field for selected CPT Service Code (from AMA 'Consumer Descriptor' term).
- Note - location of AMA copyright form field/labels may be affected by any Form Designer changes present for form
Scenario 2: 'CPT Code Definition' - Verification of American Medical Association Trademark/Copyright Notice Display
Steps
- Open 'CPT Code Definition' form.
- Verify the 'CPT Service Code' field in form contains the AMA Trademark 'CPT® Codes' label.
- Verify the following AMA copyright notice is displayed at the bottom of the form: 'CPT copyright 2021 American Medical Association. All rights reserved.'
- Note - location of AMA copyright form field/labels may be affected by any Form Designer changes present for form
|
Topics
• CPT Codes
|
Client Charge Input forms
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Program Maintenance
- Treatment Plan
- Client Charge Input
Scenario 1: Client Charge Input - Treatment Plan - Intervention - Assigned Services
Specific Setup:
- Client A: Select a client that has a ‘Treatment Plan’ with values in the ‘'Assigned Services' grid’ of the ‘Intervention’ section. The grid should contain the program and service codes at a minimum.
Steps
- Open ‘Client Charge Input’.
- Create a service for Client A, with the desired service code, and a service program that differs from the treatment plan.
- Validate that the service program is not permitted,
- Change the service program to the program that is in the treatment plan.
- Validate that the service can be submitted.
- Close the form.
|
Topics
• Treatment Plan
• Recurring Client Charge Input
• NX
• Client Charge Input
• Client Ledger
|
Payment Acknowledgement - Check/EFT
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Posting/Adjustment Codes Definition
- Payment Acknowledgement
- Service Codes
Scenario 1: Payment Acknowledgement - Post Payment Accounting Entry / Reverse Payment Accounting Entry
Specific Setup:
- Registry Setting:
- ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
- Dictionary Update:
- Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
- Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
- Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
- Posting/Adjustment Codes Definitions: Definitions exist for ‘Payment’.
- The definitions may have a value in the ‘Payment Acknowledgement Type’ field.
- All ‘Payment’ definitions will be available in the ‘Payment Acknowledgement’ form.
- Clients:
- Identify one or more clients that a balance due to a self-pay guarantor. Note the balance due amounts.
- Note the 'Treatment Setting' of the client's program.
Steps
- Open ‘Payment Acknowledgement’ form.
- Verify that ‘Action’ defaults to ‘New’.
- Verify that ‘Transaction Number’ is read only.
- Verify that ‘Entered By’ is read only and defaults to the signed in user.
- Enter desired value in ‘Batch Number’.
- Select desired ‘Posting Code’. All payment posting codes will display.
- Enter desired value in ‘Check/EFT Number’.
- Enter desired value in ‘Amount’.
- Select desired ‘Guarantor’. If a ‘Self-Pay' guarantor is selected, the ‘Client’ field will be enabled.
- Enter desired value in ‘Name/Source’.
- Enter desired value in ‘Client’, if enabled. The field is only available for ‘Self-Pay' guarantors.
- Enter desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
- Enter desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
- Enter desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
- Select desired ‘Treatment Service’.
- Select desired ‘Category’. Inactive dictionary codes will not display in this filed.
- Enter desired value in ‘Bank Ref #’.
- Enter desired value in ‘Comments’.
- Click [File].
- Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is 6. Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
- Click [Yes] to continue to Post Payment Accounting Entry section or [No] to remain in the ‘Payment Acknowledgement’ section.
- If [Yes] was clicked, go to step 30.
- If [No] was clicked, select ‘Edit or View’ in ‘Action, which will enable the ‘Payment Acknowledgement Search’ section.
- Enter data from the filed ‘Payment Acknowledgement’ into desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
- Click [Search].
- Select the desired item in the ‘Payment Acknowledgement’ grid.
- Click [OK] to continue or [Cancel] to end the search. Click [OK].
- The following ‘Payment Acknowledgement’ displays: Do you need to continue to Post Payment Accounting Entry?
- Click [Yes].
- Validate that the grid is not enabled.
- Click [New Row] in ‘Post Payment Accounting Entry’.
- Validate that the grid becomes enabled.
- Select desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
- Select desired ‘Program’. This is from ‘Other Table Files: (5521) Program’, not a program in ‘Program Maintenance’.
- Select desired ‘Account’.
- Select desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
- Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgement’.
- Select desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’ or the ‘Deposit Date’.
- If desired, enter a ‘Comment’.
- Validate that the ‘Posting Summary’ is correct.
- If desired, click [New Row] and repeat the steps.
- If desired, click [Delete Row]. A ‘Confirm Delete’ message will be displayed. Select desired value.
- Click [File].
- The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
- Click [Yes].
- Click the ‘Reverse’ checkbox in one row of the ‘Post Payment Accounting Entry’.
- Enter desired ‘Reversal Reason’.
- Click [Reverse].
- Validate that a message is received stating: Reversal Posting Date is required.
- Enter a ‘Reversal Posting Date’ that is on or after the ‘Posting Date’.
- Click [Reverse].
- Validate that a new row was added to the ‘Post Payment Accounting Entry’ grid and that it mirrors the row that was selected to reverse, except for ‘Amount’ displays in parentheses, indicating a negative amount. The ‘Comment’ for the new row will contain the ‘Reversal Reason’.
- Attempt to reverse the row that was previously reversed. Validate that a message is received that states: Rows selected to reverse that are already reversed: xx – where xx is the row number.
- If desired, add a new row to post an additional payment.
- Close the form.
Payment Acknowledgement - Post Payment Accounting Entry
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Posting/Adjustment Codes Definition
- Payment Acknowledgement
- Service Codes
Scenario 1: Payment Acknowledgement - Post Payment Accounting Entry / Reverse Payment Accounting Entry
Specific Setup:
- Registry Setting:
- ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
- Dictionary Update:
- Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
- Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
- Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
- Posting/Adjustment Codes Definitions: Definitions exist for ‘Payment’.
- The definitions may have a value in the ‘Payment Acknowledgement Type’ field.
- All ‘Payment’ definitions will be available in the ‘Payment Acknowledgement’ form.
- Clients:
- Identify one or more clients that a balance due to a self-pay guarantor. Note the balance due amounts.
- Note the 'Treatment Setting' of the client's program.
Steps
- Open ‘Payment Acknowledgement’ form.
- Verify that ‘Action’ defaults to ‘New’.
- Verify that ‘Transaction Number’ is read only.
- Verify that ‘Entered By’ is read only and defaults to the signed in user.
- Enter desired value in ‘Batch Number’.
- Select desired ‘Posting Code’. All payment posting codes will display.
- Enter desired value in ‘Check/EFT Number’.
- Enter desired value in ‘Amount’.
- Select desired ‘Guarantor’. If a ‘Self-Pay' guarantor is selected, the ‘Client’ field will be enabled.
- Enter desired value in ‘Name/Source’.
- Enter desired value in ‘Client’, if enabled. The field is only available for ‘Self-Pay' guarantors.
- Enter desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
- Enter desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
- Enter desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
- Select desired ‘Treatment Service’.
- Select desired ‘Category’. Inactive dictionary codes will not display in this filed.
- Enter desired value in ‘Bank Ref #’.
- Enter desired value in ‘Comments’.
- Click [File].
- Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is 6. Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
- Click [Yes] to continue to Post Payment Accounting Entry section or [No] to remain in the ‘Payment Acknowledgement’ section.
- If [Yes] was clicked, go to step 30.
- If [No] was clicked, select ‘Edit or View’ in ‘Action, which will enable the ‘Payment Acknowledgement Search’ section.
- Enter data from the filed ‘Payment Acknowledgement’ into desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
- Click [Search].
- Select the desired item in the ‘Payment Acknowledgement’ grid.
- Click [OK] to continue or [Cancel] to end the search. Click [OK].
- The following ‘Payment Acknowledgement’ displays: Do you need to continue to Post Payment Accounting Entry?
- Click [Yes].
- Validate that the grid is not enabled.
- Click [New Row] in ‘Post Payment Accounting Entry’.
- Validate that the grid becomes enabled.
- Select desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
- Select desired ‘Program’. This is from ‘Other Table Files: (5521) Program’, not a program in ‘Program Maintenance’.
- Select desired ‘Account’.
- Select desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
- Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgement’.
- Select desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’ or the ‘Deposit Date’.
- If desired, enter a ‘Comment’.
- Validate that the ‘Posting Summary’ is correct.
- If desired, click [New Row] and repeat the steps.
- If desired, click [Delete Row]. A ‘Confirm Delete’ message will be displayed. Select desired value.
- Click [File].
- The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
- Click [Yes].
- Click the ‘Reverse’ checkbox in one row of the ‘Post Payment Accounting Entry’.
- Enter desired ‘Reversal Reason’.
- Click [Reverse].
- Validate that a message is received stating: Reversal Posting Date is required.
- Enter a ‘Reversal Posting Date’ that is on or after the ‘Posting Date’.
- Click [Reverse].
- Validate that a new row was added to the ‘Post Payment Accounting Entry’ grid and that it mirrors the row that was selected to reverse, except for ‘Amount’ displays in parentheses, indicating a negative amount. The ‘Comment’ for the new row will contain the ‘Reversal Reason’.
- Attempt to reverse the row that was previously reversed. Validate that a message is received that states: Rows selected to reverse that are already reversed: xx – where xx is the row number.
- If desired, add a new row to post an additional payment.
- Close the form.
Payment Acknowledgement - Reverse Payment Accounting Entry
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Posting/Adjustment Codes Definition
- Payment Acknowledgement
- Service Codes
Scenario 1: Payment Acknowledgement - Post Payment Accounting Entry / Reverse Payment Accounting Entry
Specific Setup:
- Registry Setting:
- ‘Avatar PM->Billing->Remittance Processing->->->Enable Payment Acknowledgement’ has a ‘Registry Setting Value’ of ‘Y’.
- Dictionary Update:
- Other Table Files: (5521) Program - contains dictionary codes and dictionary values.
- Other Table Files: (5522) Account - contains dictionary codes, dictionary values and extended dictionary values.
- Other Table Files: (9712) Payment Acknowledgement Type – extended dictionary values have been added to the locked dictionary.
- Posting/Adjustment Codes Definitions: Definitions exist for ‘Payment’.
- The definitions may have a value in the ‘Payment Acknowledgement Type’ field.
- All ‘Payment’ definitions will be available in the ‘Payment Acknowledgement’ form.
- Clients:
- Identify one or more clients that a balance due to a self-pay guarantor. Note the balance due amounts.
- Note the 'Treatment Setting' of the client's program.
Steps
- Open ‘Payment Acknowledgement’ form.
- Verify that ‘Action’ defaults to ‘New’.
- Verify that ‘Transaction Number’ is read only.
- Verify that ‘Entered By’ is read only and defaults to the signed in user.
- Enter desired value in ‘Batch Number’.
- Select desired ‘Posting Code’. All payment posting codes will display.
- Enter desired value in ‘Check/EFT Number’.
- Enter desired value in ‘Amount’.
- Select desired ‘Guarantor’. If a ‘Self-Pay' guarantor is selected, the ‘Client’ field will be enabled.
- Enter desired value in ‘Name/Source’.
- Enter desired value in ‘Client’, if enabled. The field is only available for ‘Self-Pay' guarantors.
- Enter desired value in ‘Check/EFT Date’. Note the date cannot be a future date.
- Enter desired value in ‘Receipt Date’. Note the date cannot be before the ‘Check/EFT Date’,
- Enter desired value in ‘Deposit Date’. Note the date cannot be before the ‘Check/EFT Date’ or the ‘Receipt Date’.
- Select desired ‘Treatment Service’.
- Select desired ‘Category’. Inactive dictionary codes will not display in this filed.
- Enter desired value in ‘Bank Ref #’.
- Enter desired value in ‘Comments’.
- Click [File].
- Verify that the ‘Payment Acknowledgement’ message is received and states the following: Filed successfully. The Transaction Number is 6. Do you need to continue to Post Payment Accounting Entry? Note: The Transaction Number’ increments by one number with each filing.
- Click [Yes] to continue to Post Payment Accounting Entry section or [No] to remain in the ‘Payment Acknowledgement’ section.
- If [Yes] was clicked, go to step 30.
- If [No] was clicked, select ‘Edit or View’ in ‘Action, which will enable the ‘Payment Acknowledgement Search’ section.
- Enter data from the filed ‘Payment Acknowledgement’ into desired search fields. The ’Transaction Number’ and ‘Batch Number’ are specific to only one ‘Payment Acknowledgement’. The following fields may return results for more than one ‘Payment Acknowledgement’ when applicable: ‘Client’, ‘Guarantor’, ‘Amount Type’, ‘Check/EFT #’, ‘Check/EFT From Date’, ‘Check/EFT To Date’, ‘Deposit From Date’, and ‘Deposit To Date’.
- Click [Search].
- Select the desired item in the ‘Payment Acknowledgement’ grid.
- Click [OK] to continue or [Cancel] to end the search. Click [OK].
- The following ‘Payment Acknowledgement’ displays: Do you need to continue to Post Payment Accounting Entry?
- Click [Yes].
- Validate that the grid is not enabled.
- Click [New Row] in ‘Post Payment Accounting Entry’.
- Validate that the grid becomes enabled.
- Select desired ‘Treatment Service’. It will default if filed in the ‘Payment Acknowledgement’.
- Select desired ‘Program’. This is from ‘Other Table Files: (5521) Program’, not a program in ‘Program Maintenance’.
- Select desired ‘Account’.
- Select desired ‘Amount’. If the amount is an even dollar amount such as $500.00, enter '500' and validate that the field displays as '500.00'.
- Validate that the ‘Posting Code; defaulted from the ‘Payment Acknowledgement’.
- Select desired ‘Posting Date’. Note the date cannot be before the ‘Check/EFT Date’, the ‘Receipt Date’ or the ‘Deposit Date’.
- If desired, enter a ‘Comment’.
- Validate that the ‘Posting Summary’ is correct.
- If desired, click [New Row] and repeat the steps.
- If desired, click [Delete Row]. A ‘Confirm Delete’ message will be displayed. Select desired value.
- Click [File].
- The following ‘Payment Acknowledgement’ displays: Filed successfully. Do you need to continue with Post Payment Accounting Entry?
- Click [Yes].
- Click the ‘Reverse’ checkbox in one row of the ‘Post Payment Accounting Entry’.
- Enter desired ‘Reversal Reason’.
- Click [Reverse].
- Validate that a message is received stating: Reversal Posting Date is required.
- Enter a ‘Reversal Posting Date’ that is on or after the ‘Posting Date’.
- Click [Reverse].
- Validate that a new row was added to the ‘Post Payment Accounting Entry’ grid and that it mirrors the row that was selected to reverse, except for ‘Amount’ displays in parentheses, indicating a negative amount. The ‘Comment’ for the new row will contain the ‘Reversal Reason’.
- Attempt to reverse the row that was previously reversed. Validate that a message is received that states: Rows selected to reverse that are already reversed: xx – where xx is the row number.
- If desired, add a new row to post an additional payment.
- Close the form.
|
Topics
• NX
• Payment Acknowledgement
|
Change Program/Admission Date
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Change Program/Admission Date
- Change Program/Admission Date Dialogue
- Admission
Scenario 1: Change Program/Admission Date - verification of form filing
Specific Setup:
- Client must be admitted to an active episode (Client A).
Steps
- Access the 'Change Program/Admission Date' form.
- Select Client A in the 'Client ID' field.
- Select the desired episode in the 'Episode Number' field.
- Select the desired program in the 'New Program' field.
- Select the desired date in the 'New Admission Date' field.
- Select the desired time in the 'New Admission Time' field.
- Click [Submit].
- Validate that a 'Change Program/Admission Date' message is displayed stating "Admission Program and Date has been changed".
- Click [OK].
- Open the admission form for the client.
- Edit the episode,
- Validate that the admission date contains the new value.
- Close the form.
|
Topics
• Change Program/Admission Date
|
'Allow Spaces in Client Name' registry setting
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Update Client Data
- CareFabric Monitor
- Admission
Scenario 1: Update Client Data - Validate the 'Allow spaces in Client Name' registry setting
Specific Setup:
- The 'Client Demographics - Additional Fields' registry setting must be set to include "3" for 'Detailed Client Name'.
- The 'Allow Spaces in Client Name' registry setting is set to "Y".
- A client is enrolled in an existing episode (Client A).
Steps
- Select "Client A" and access the 'Update Client Data' form.
- Enter any name including one or more spaces in the 'Client Last Name' field (Ex. Last Name).
- Enter any name including one or more spaces in the 'Client First Name' field (Ex. First Name).
- Enter any name including one or more spaces in the 'Client Middle Name' field (Ex. Middle Name).
- Click [Submit].
- Select "Client A" and validate the name displays with spaces as entered in the 'Update Client Data' 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.
- Click [View Activity Log].
- Validate the 'CareFabric Monitor Report' is displayed.
- Validate a "ClientUpdated" record is displayed and click [Click To View Record].
- Validate the 'name' - 'first' field contains the first name with spaces entered in the previous steps.
- Validate the 'name' - 'last' field contains the last name with spaces entered in the previous steps.
- Validate the 'name' - 'middle' field contains the middle name with spaces entered in the previous steps.
- Navigate back to the 'CareFabric Monitor Report'.
- Validate a "ClientDemographicsCreated" record is displayed and click [Click To View Record].
- Validate the 'clientName' - 'first' field contains the first name with spaces entered in the previous steps.
- Validate the 'clientName' - 'last' field contains the last name with spaces entered in the previous steps.
- Validate the 'clientName' - 'middle' field contains the middle name with spaces entered in the previous steps.
- Close the report and the form.
|
Topics
• Registry Settings
• Update Client Data
|
Support tool stateless update
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Internal Test Only
|
Topics
• State Forms
• NX
|
Remittance Functionality
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Remittance Processing Widget
- Crystal Reports or other SQL Reporting tool (PM Namespace)
Internal Test Only
|
Topics
n/a
|
Consent for Access - External Network
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: "Consent for Access" form - Consent on External Network section
Specific Setup:
- An existing client must be identified, Client A.
Steps
- Open the 'Consent For Access' form for the client identified in the setup section.
- Select the "External Network" section.
- Click [Add New Item].
- Select "Network" in the 'Consent for' field.
- Select the desired network in the 'Network' field.
- Select "Grant" in the 'Consent to Opt In/Opt Out' field.
- Validate no warning message is displayed.
- Enter the desired date in the 'Start Date' field.
- Click [Add New Item].
- Select "Organization" in the 'Consent for' field.
- Select the desired organization in the 'Organization' field.
- Select "Grant" in the 'Consent to Opt In/Opt Out' field.
- Validate a "Warning" message is displayed stating: "Granting individual consent to an organization includes the granting of access to information covered under the 42 CFR Part 2. Do you want to continue?" Please note: This message will only be displayed when selecting "Grant" consent for an organization or referral provider.
- Click [Yes].
- Enter the desired date in the 'Start Date' field.
- Click [Submit].
- Access Crystal Reports or other SQL Reporting tool.
- Create a report using the 'SYSTEM.consent_for_access' table.
- Validate two rows are displayed for the consent records filed in the previous steps - One for Network and one for Organization. Validate all information is displayed correctly.
- Select the client identified in setup section and access the 'Consent For Access' form.
- Select the "External Network" section.
- Select one of the records created in the previous steps.
- Click [Edit Selected Item].
- Enter any new value in the 'Start Date' field.
- Click [Submit].
- Access Crystal Reports or other SQL Reporting tool.
- Refresh the report using the SYSTEM.consent_for_access table.
- Navigate to row associated to the consent record updated in the previous steps.
- Validate the 'data_entry_by' field contains the user who updated the record.
- Validate the 'data_entry_date' field contains the date the record was updated.
- Validate the 'data_entry_time' field contains the time the record was updated.
- Validate the 'start_date' field contains the new date.
- Close the report.
- Create a new report using the SYSTEM.audit_consent_for_access table.
- Validate a row is displayed for the consent record updated in the previous steps.
- Validate the 'PATID' field contains 'Client A' ID.
- Validate the 'audit_data_entry_section' field contains "Updated".
- Validate the 'audit_data_entry_by' field contains the user who updated the record.
- Validate the 'audit_date' field contains the date the record was updated.
- Validate the 'audit_time' field contains the time the record was updated.
- Validate the 'start_date' field contains the original start date filed, not the updated date.
- Validate all other fields contain the original data for the consent record.
- Close the report.
Scenario 2: Dictionary Update - Client file - Add/Edit/Print dictionary
Steps
- Open the 'Dictionary Update' form.
- Select 'Client' in the 'File' field.
- Select 'Location' in the 'Data Element' field.
- Enter desired code to the 'Dictionary Code' field. Note the code.
- Enter desired value to the 'Dictionary Value' field. Note the value.
- Enter in extended data elements as necessary.
- Click [Apply Changes].
- Validate that the 'Information' dialog contains 'Filed!'.
- Click [OK].
- Select 'Print Dictionary' section.
- Select 'Client' in the 'File' field.
- Select 'Individual Data Element' radio button.
- Select 'Location Status' from the 'Data Element' field.
- Click [Print Dictionary].
- Review the report.
- Verify the dictionary codes / values added in previous step display correctly.
- Close the report.
- Select 'Input Dictionary Code(s)' section.
- Verify the 'File' field contains 'Client'.
- Verify the 'Data Element' is set to the 'Location'.
- Select desired code which is added in previous step in the 'Dictionary Code' field.
- Verify the correct 'Dictionary Value' displays for the selected code.
- Update the value in the 'Dictionary Value' field.
- Click [Apply Changes].
- Validate that the 'Information' dialog contains 'Filed!'.
- Click [OK].
- Select 'Print Dictionary' section.
- Select 'Client' in the 'File' field.
- Select 'Individual Data Element' radio button.
- Select 'Location' from the 'Data Element' field.
- Click [Print Dictionary].
- Review the report.
- Verify the dictionary codes / values updated in previous step display correctly.
- Close the report.
- Close the form.
- Open the "Scheduling Calendar" form.
- Select an open time slot on the calendar and RightClick.
- Select "Add Appointment" from the dropdown.
- Note that the "Location" field contains the dictionary code(s)/value(s) entered in previous steps.
|
Topics
• Consent for Access
• Dictionary
|
| |