View Definition - widget
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- System Task Scheduler
- User Definition
- View Definition
- Dynamic Form - View Definition - Select Views
- Task Scheduler Status
Scenario 1: Widget - Task Scheduler Status
Specific Setup:
- System Task Scheduler:
- Note the data filed for a minimum of two active tasks and one inactive task.
- View Definition has been used to add the ‘Task Scheduler Status’ widget to the tester’s homeview.
Steps
- Access the ‘Task Scheduler Status’ widget.
- Validate that the widget can be undocked, refreshed, and either minimized (Non NX View) or removed (NX View).
- Validate that the widget contains the following columns: ‘Application’, ‘Task’. ‘Inactive’, ‘Recur’, ‘Start Date’, ‘End Date’, ‘Last Run Date’, ‘Last Run Time’, and ‘Last Run Status’.
- Validate the data in each column for the ‘System Task Scheduler’ data noted in ‘Setup’.
|
Topics
• Widgets
• System Task Scheduler
• NX
|
Registry Setting - Allow Roll-Up Rule Selection During Compile
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Ledger
- Compile/Edit/Post/Unpost Roll-Up Services Worklist
- Roll-Up Services Definition
- Dynamic Form - Roll-Up Group Definition
- Client Charge Input
Scenario 1: Registry Setting - Allow Roll-Up Rule Selection During Compile - Single Roll-Up
Specific Setup:
- Registry Setting: Allow Roll-Up Rule Selection During Compile has a value of ‘1’.
- Roll-Up Services Definition:
- Two single and two group roll-up definitions exist. Note the component service codes and any requirements.
- At a minimum, services that meet a single roll-up definition exist for a minimum of one client. Note the client ID. Note the dates of service.
Steps
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Verify that the only roll-up definitions that can be selected are single definitions.
- Enter the desired ‘From Date’ and ‘To Date’.
- Select the definitions for the services in ‘Setup’.
- Click [Compile Worklist].
- Click [OK].
- Select the ‘Post Roll-Up Services Worklist’ section.
- Select the desired ‘Through Date’.
- Select the desired 'Write Off Posting Code’.
- Click [Post Worklist].
- Click [OK].
- Close the form.
- Open ‘Client Ledger’ for the desired client and date range. Select ‘Simple’ in the ‘Ledger Type’
- Click [Process] and validate that the services for the rules within the rule group have the value of ‘Roll-Up’ in ‘CLAIM NUMBER’. Validate that the service created from the roll-up process has a value of ‘OPEN’ in ‘CLAIM NUMBER’.
- Close the report.
- Close the form.
Scenario 2: Registry Setting - Allow Roll-Up Rule Selection During Compile - Group Roll-Up
Specific Setup:
- Registry Setting: Allow Roll-Up Rule Selection During Compile has a value of ‘1’.
- Roll-Up Services Definition:
- Open the 'Roll-Up Group Definition' section:
- Click the light bulb on the ‘Post Roll-Up Rule Individually’ field. Validate that it contains:
- If 'No' is selected, each roll-up rule is compiled in the specified order of execution, then the entire compile is posted. This is the default behavior for roll-up processing.
- If 'Yes' is selected, each roll-up rule is compiled and posted in order of execution before the next roll-up rule is compiled.
- Create a minimum of two 'Roll-Up Group Definitions'. One definition must have a value of 'Yes' and one definition must have a value of 'No' in ‘Post Roll-Up Rule Individually’.
- At a minimum, services that meet both group roll-up definitions exist for a minimum of one client. Note the client ID. Note the dates of service.
- Open the 'Roll-Up Services Definition' section, select edit and note the value of 'Existing Roll-Up Definition' for at least one definition.
Steps
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Verify that the only roll-up definitions that can be selected are group definitions.
- Enter the desired ‘From Date’ and ‘To Date’ for the group definition with a value of 'Yes' in ‘Post Roll-Up Rule Individually’.
- Select the group definitions with a value of 'Yes' in ‘Post Roll-Up Rule Individually’.
- Click [Compile Worklist].
- Click [OK].
- Based on the light bulb message when 'Yes' is in ‘Post Roll-Up Rule Individually’, each roll-up rule is compiled and posted in order of execution before the next roll-up rule is compiled. This means that the user does not use the 'Post Roll-Up Services Worklist' section of the form.
- Close the form.
- Open ‘Client Ledger’ for the desired client and date range. Select ‘Simple’ in the ‘Ledger Type’
- Click [Process] and validate that the services for the rules within the rule group have the value of ‘Roll-Up’ in ‘CLAIM NUMBER’. Validate that the service created from the roll-up process has a value of ‘OPEN’ in ‘CLAIM NUMBER’.
- Close the report.
- Close the form.
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Enter the desired ‘From Date’ and ‘To Date’ for the group definition with a value of 'No' in ‘Post Roll-Up Rule Individually’.
- Select the group definitions with a value of 'Yes' in ‘Post Roll-Up Rule Individually’.
- Click [Compile Worklist].
- Click [OK].
- Based on the light bulb message when 'No' is in ‘Post Roll-Up Rule Individually’, each roll-up rule is compiled in the specified order of execution, then the entire compile is posted.
- Select the ‘Post Roll-Up Services Worklist’ section.
- Select the desired ‘Through Date’.
- Click [Post Worklist].
- Close the form.
- Open ‘Client Ledger’ for the desired client and date range. Select ‘Simple’ in the ‘Ledger Type’
- Click [Process] and validate that the services for the rules within the rule group have the value of ‘Roll-Up’ in ‘CLAIM NUMBER’. Validate that the service created from the roll-up process has a value of ‘OPEN’ in ‘CLAIM NUMBER’.
- Close the report.
- Close the form.
Scenario 3: Registry Setting - Allow Roll-Up Rule Selection During Compile - Single and Group Roll-Ups
Specific Setup:
- Registry Setting: Allow Roll-Up Rule Selection During Compile has a value of ‘172’.
- This value indicates that the option to select either individual or group 'Roll-Up Services Definitions' will be included on the form.
- When an individual definition is selected the user will be unable to select a group definition, or when a group definition is selected the user will be unable to select an individual definition.
- Roll-Up Services Definition:
- At a minimum, two single and two group roll-up definitions exist. Note the component service codes and any requirements.
In the group definitions: - If 'No' is selected, each roll-up rule is compiled in the specified order of execution, then the entire compile is posted. This is the default behavior for roll-up processing.
- If 'Yes' is selected, each roll-up rule is compiled and posted in order of execution before the next roll-up rule is compiled.
- At a minimum, services that meet a single roll-up definition, and services that will meet a group definition, exist for a minimum of one client. Note the client ID. Note the dates of service.
Steps
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Verify that the fields ‘Roll-Up Definitions’ and ‘Roll-Up Group’ are enabled.
- Enter the desired ‘From Date’ and ‘To Date’.
- Select a value in ‘Roll-Up Definitions’.
- Validate that no value can be selected in ‘Roll-Up Group’.
- Click [Compile Worklist].
- Click [OK].
- Select the ‘Post Roll-Up Services Worklist’ section.
- Select the desired ‘Through Date’.
- Select the desired 'Write Off Posting Code’.
- Click [Post Worklist].
- Click [OK].
- Close the form.
- Open ‘Client Ledger’ for the desired client and date range. Select ‘Simple’ in the ‘Ledger Type’
- Click [Process] and validate that the services for the rules within the rule group have the value of ‘Roll-Up’ in ‘CLAIM NUMBER’. Validate that the service created from the roll-up process has a value of ‘OPEN’ in ‘CLAIM NUMBER’.
- Close the report.
- Close the form.
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Enter the desired ‘From Date’ and ‘To Date’.
- Select a value in ‘Roll-Up Group’.
- Validate that no value can be selected in ‘Roll-Up Definitions’.
- Click [Compile Worklist].
- Click [OK].
- If the group definition is set to roll-up the definition individually, the compile will be posted.
- If the group definition is not set to roll-up the definition individually, the compile will not be posted. Post the compile.
- Close the form.
- Open ‘Client Ledger’ for the desired client and date range. Select ‘Simple’ in the ‘Ledger Type’
- Click [Process] and validate that the services for the rules within the rule group have the value of ‘Roll-Up’ in ‘CLAIM NUMBER’. Validate that the service created from the roll-up process has a value of ‘OPEN’ in ‘CLAIM NUMBER’.
- Close the report.
- Close the form.
Scenario 4: Registry Setting - Allow Roll-Up Rule Selection During Compile = zero - No options to select on form
Specific Setup:
- Registry Setting: Allow Roll-Up Rule Selection During Compile has a value of ‘0’.
- A value of '0' indicates that the option to select 'Roll-Up Services Definitions' will be removed from the form, and that only 'single' definitions will compile. No 'group definitions will compile.
- Roll-Up Services Definition:
- Two single and two group roll-up definitions exist. Note the component service codes and any requirements.
- At a minimum, services that meet a single roll-up definition, and services that will meet a group definition, exist for a minimum of one client. Note the client ID. Note the dates of service.
Steps
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Verify that no roll-up definitions can be selected.
- Enter the desired ‘From Date’ and ‘To Date’.
- Click [Compile Worklist].
- Click [OK].
- Select the ‘Post Roll-Up Services Worklist’ section.
- Select the desired ‘Through Date’.
- Select the desired 'Write Off Posting Code’.
- Click [Post Worklist].
- Click [OK].
- Close the form.
- Open ‘Client Ledger’ for the desired client and date range. Select ‘Simple’ in the ‘Ledger Type’
- Click [Process] and validate that the services for the rules within the rule group have the value of ‘Roll-Up’ in ‘CLAIM NUMBER’. Validate that the service created from the roll-up process has a value of ‘OPEN’ in ‘CLAIM NUMBER’.
- Close the report.
- Close the form.
Roll-Up Services Definition - Roll-Up Group Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Roll-Up Services Definition
- Dynamic Form - Roll-Up Group Definition
- Client Charge Input
- Compile/Edit/Post/Unpost Roll-Up Services Worklist
- Client Ledger
Scenario 1: Registry Setting - Allow Roll-Up Rule Selection During Compile - Group Roll-Up
Specific Setup:
- Registry Setting: Allow Roll-Up Rule Selection During Compile has a value of ‘1’.
- Roll-Up Services Definition:
- Open the 'Roll-Up Group Definition' section:
- Click the light bulb on the ‘Post Roll-Up Rule Individually’ field. Validate that it contains:
- If 'No' is selected, each roll-up rule is compiled in the specified order of execution, then the entire compile is posted. This is the default behavior for roll-up processing.
- If 'Yes' is selected, each roll-up rule is compiled and posted in order of execution before the next roll-up rule is compiled.
- Create a minimum of two 'Roll-Up Group Definitions'. One definition must have a value of 'Yes' and one definition must have a value of 'No' in ‘Post Roll-Up Rule Individually’.
- At a minimum, services that meet both group roll-up definitions exist for a minimum of one client. Note the client ID. Note the dates of service.
- Open the 'Roll-Up Services Definition' section, select edit and note the value of 'Existing Roll-Up Definition' for at least one definition.
Steps
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Verify that the only roll-up definitions that can be selected are group definitions.
- Enter the desired ‘From Date’ and ‘To Date’ for the group definition with a value of 'Yes' in ‘Post Roll-Up Rule Individually’.
- Select the group definitions with a value of 'Yes' in ‘Post Roll-Up Rule Individually’.
- Click [Compile Worklist].
- Click [OK].
- Based on the light bulb message when 'Yes' is in ‘Post Roll-Up Rule Individually’, each roll-up rule is compiled and posted in order of execution before the next roll-up rule is compiled. This means that the user does not use the 'Post Roll-Up Services Worklist' section of the form.
- Close the form.
- Open ‘Client Ledger’ for the desired client and date range. Select ‘Simple’ in the ‘Ledger Type’
- Click [Process] and validate that the services for the rules within the rule group have the value of ‘Roll-Up’ in ‘CLAIM NUMBER’. Validate that the service created from the roll-up process has a value of ‘OPEN’ in ‘CLAIM NUMBER’.
- Close the report.
- Close the form.
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Enter the desired ‘From Date’ and ‘To Date’ for the group definition with a value of 'No' in ‘Post Roll-Up Rule Individually’.
- Select the group definitions with a value of 'Yes' in ‘Post Roll-Up Rule Individually’.
- Click [Compile Worklist].
- Click [OK].
- Based on the light bulb message when 'No' is in ‘Post Roll-Up Rule Individually’, each roll-up rule is compiled in the specified order of execution, then the entire compile is posted.
- Select the ‘Post Roll-Up Services Worklist’ section.
- Select the desired ‘Through Date’.
- Click [Post Worklist].
- Close the form.
- Open ‘Client Ledger’ for the desired client and date range. Select ‘Simple’ in the ‘Ledger Type’
- Click [Process] and validate that the services for the rules within the rule group have the value of ‘Roll-Up’ in ‘CLAIM NUMBER’. Validate that the service created from the roll-up process has a value of ‘OPEN’ in ‘CLAIM NUMBER’.
- Close the report.
- Close the form.
Scenario 2: Registry Setting - Allow Roll-Up Rule Selection During Compile - Single and Group Roll-Ups
Specific Setup:
- Registry Setting: Allow Roll-Up Rule Selection During Compile has a value of ‘172’.
- This value indicates that the option to select either individual or group 'Roll-Up Services Definitions' will be included on the form.
- When an individual definition is selected the user will be unable to select a group definition, or when a group definition is selected the user will be unable to select an individual definition.
- Roll-Up Services Definition:
- At a minimum, two single and two group roll-up definitions exist. Note the component service codes and any requirements.
In the group definitions: - If 'No' is selected, each roll-up rule is compiled in the specified order of execution, then the entire compile is posted. This is the default behavior for roll-up processing.
- If 'Yes' is selected, each roll-up rule is compiled and posted in order of execution before the next roll-up rule is compiled.
- At a minimum, services that meet a single roll-up definition, and services that will meet a group definition, exist for a minimum of one client. Note the client ID. Note the dates of service.
Steps
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Verify that the fields ‘Roll-Up Definitions’ and ‘Roll-Up Group’ are enabled.
- Enter the desired ‘From Date’ and ‘To Date’.
- Select a value in ‘Roll-Up Definitions’.
- Validate that no value can be selected in ‘Roll-Up Group’.
- Click [Compile Worklist].
- Click [OK].
- Select the ‘Post Roll-Up Services Worklist’ section.
- Select the desired ‘Through Date’.
- Select the desired 'Write Off Posting Code’.
- Click [Post Worklist].
- Click [OK].
- Close the form.
- Open ‘Client Ledger’ for the desired client and date range. Select ‘Simple’ in the ‘Ledger Type’
- Click [Process] and validate that the services for the rules within the rule group have the value of ‘Roll-Up’ in ‘CLAIM NUMBER’. Validate that the service created from the roll-up process has a value of ‘OPEN’ in ‘CLAIM NUMBER’.
- Close the report.
- Close the form.
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Enter the desired ‘From Date’ and ‘To Date’.
- Select a value in ‘Roll-Up Group’.
- Validate that no value can be selected in ‘Roll-Up Definitions’.
- Click [Compile Worklist].
- Click [OK].
- If the group definition is set to roll-up the definition individually, the compile will be posted.
- If the group definition is not set to roll-up the definition individually, the compile will not be posted. Post the compile.
- Close the form.
- Open ‘Client Ledger’ for the desired client and date range. Select ‘Simple’ in the ‘Ledger Type’
- Click [Process] and validate that the services for the rules within the rule group have the value of ‘Roll-Up’ in ‘CLAIM NUMBER’. Validate that the service created from the roll-up process has a value of ‘OPEN’ in ‘CLAIM NUMBER’.
- Close the report.
- Close the form.
Scenario 3: Registry Setting - Allow Roll-Up Rule Selection During Compile = zero - No options to select on form
Specific Setup:
- Registry Setting: Allow Roll-Up Rule Selection During Compile has a value of ‘0’.
- A value of '0' indicates that the option to select 'Roll-Up Services Definitions' will be removed from the form, and that only 'single' definitions will compile. No 'group definitions will compile.
- Roll-Up Services Definition:
- Two single and two group roll-up definitions exist. Note the component service codes and any requirements.
- At a minimum, services that meet a single roll-up definition, and services that will meet a group definition, exist for a minimum of one client. Note the client ID. Note the dates of service.
Steps
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Verify that no roll-up definitions can be selected.
- Enter the desired ‘From Date’ and ‘To Date’.
- Click [Compile Worklist].
- Click [OK].
- Select the ‘Post Roll-Up Services Worklist’ section.
- Select the desired ‘Through Date’.
- Select the desired 'Write Off Posting Code’.
- Click [Post Worklist].
- Click [OK].
- Close the form.
- Open ‘Client Ledger’ for the desired client and date range. Select ‘Simple’ in the ‘Ledger Type’
- Click [Process] and validate that the services for the rules within the rule group have the value of ‘Roll-Up’ in ‘CLAIM NUMBER’. Validate that the service created from the roll-up process has a value of ‘OPEN’ in ‘CLAIM NUMBER’.
- Close the report.
- Close the form.
File Import - Roll-Up Services Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- File Import
- Roll-Up Services Definition
- Dynamic Form Delete File
Scenario 1: File Import - Roll-Up Services Definition
Specific Setup:
- File Import:
- The ‘Avatar_PM_File_Import_Record_Layouts_Roll_Ups’ document is included in the posted zip file.
- Import files have been created to add, edit, and delete a Roll-Up Services Definition.
Steps
- Open ‘File Import’.
- Select 'Roll-Up Services Definition' in ‘File Type’.
- Click [Upload New File] in ‘Action’.
- Click [Process Action].
- Upload the file that will add the 'Roll-Up Services Definition'.
- Click [Compile/Validate File] in ‘Action’.
- Select the uploaded file.
- Click [Process Action].
- If there are errors, click [Print Errors] in ‘Action’.
- Select the compiled file.
- Click [Process Action].
- Review the report and upload and compile again to resolve the errors.
- Click [Print File] in ‘Action’.
- Click [Process Action].
- Review the report to validate the data.
- Click [Post File] in ‘Action’.
- Select the compiled file.
- Click [Process Action].
- If desired, Click [Delete File] in ‘Action’.
- Select the posted file.
- Click [Process Action].
- The ‘Delete File’ message will display.
- Click desired value. If [Yes], the ‘Confirm message will display. Click [OK]. If [No], the ‘Delete File’ message is removed.
- Close the form.
- Open 'Roll-Up Services Definition'.
- Validate that the definition imported with the correct values.
- Close the form.
- Repeat steps 1-24 for the file that will edit the 'Roll-Up Services Definition'.
- Open 'Roll-Up Services Definition'.
- Validate that the edited definition contains the correct values in the edited fields.
- Close the form.
- Repeat steps 1-24 for the file that will delete the 'Roll-Up Services Definition'.
- Open 'Roll-Up Services Definition'.
- Validate that the deleted definition does not exist.
- Close the form.
Compile/Edit/Post/Unpost Roll-Up Services Worklist - Unpost Selected Roll-Up Services
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Ledger
- Compile/Edit/Post/Unpost Roll-Up Services Worklist
Scenario 1: Compile/Edit/Post/Unpost Roll-Up Services Worklist - Unpost Selected Roll-Up Services
Specific Setup:
- Compile/Edit/Post/Unpost Roll-Up Services Worklist:
- A minimum of two Roll-Up Services Worklists have been posted, containing a minimum of two clients.
- Note the 'Roll-Up Posting Date', 'Roll-Up Dates of Service' and the client IDs.
- Use ‘Client Ledger’ to validate that the rill-up service was created.
Steps
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Select the ‘Unpost Selected Roll-Up Services’ section.
- Select desired value in ‘Select By Posting Date or Date of Service’.
- Enter desired value in ‘From Date’.
- Enter desired value in ‘To Date’.
- Select ‘Individual Client’ in ‘All or Individual Client’.
- Select the desired 'Client'.
- Select desired ‘Roll-Up Worklists’.
- Click [Select Roll-Ups to Unpost].
- Select desired rows in the ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’ grid.
- Click [Save].
- Click [Unpost Roll-Ups].
- Click [OK].
- Validate the date in the report and close the report.
- Close the form.
- Open ‘Client Ledger’.
- Process the ledger for the date range of the rolled-up services and the client that was selected to be unposted.
- Validate that the services are not rolled-up.
- Close the report.
- Process the ledger for the date range of the rolled-up services and the client that was not selected to be unposted.
- Validate that the services are rolled-up.
- Close the report.
- Close the form.
Registry Setting - Default Write Off Posting Code
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Ledger
- Compile/Edit/Post/Unpost Roll-Up Services Worklist
- Client Charge Input
Scenario 1: Registry Setting - Allow Roll-Up Rule Selection During Compile - Single Roll-Up
Specific Setup:
- Registry Setting: Allow Roll-Up Rule Selection During Compile has a value of ‘1’.
- Roll-Up Services Definition:
- Two single and two group roll-up definitions exist. Note the component service codes and any requirements.
- At a minimum, services that meet a single roll-up definition exist for a minimum of one client. Note the client ID. Note the dates of service.
Steps
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Verify that the only roll-up definitions that can be selected are single definitions.
- Enter the desired ‘From Date’ and ‘To Date’.
- Select the definitions for the services in ‘Setup’.
- Click [Compile Worklist].
- Click [OK].
- Select the ‘Post Roll-Up Services Worklist’ section.
- Select the desired ‘Through Date’.
- Select the desired 'Write Off Posting Code’.
- Click [Post Worklist].
- Click [OK].
- Close the form.
- Open ‘Client Ledger’ for the desired client and date range. Select ‘Simple’ in the ‘Ledger Type’
- Click [Process] and validate that the services for the rules within the rule group have the value of ‘Roll-Up’ in ‘CLAIM NUMBER’. Validate that the service created from the roll-up process has a value of ‘OPEN’ in ‘CLAIM NUMBER’.
- Close the report.
- Close the form.
Scenario 2: Registry Setting - Default Write Off Posting Code
Specific Setup:
- Registry Setting: Default Write Off Posting Code has desired value without a “#” appended to it.
- Roll-Up Services Definition exists. Note the component service codes and any requirements.
- Services that meet the Roll-Up Services Definition exist for a minimum of one client. Note the client ID. Note the dates of service.
Steps
- Open ‘Compile/Edit/Post/Unpost Roll-Up Services Worklist’.
- Compile the worklist for the dates of service and the Roll-Up Service Definition.
- Click [OK].
- Select the ‘Post Roll-Up Services Worklist’ section.
- Select the desired compile in ‘Through Date’.
- Validate that the posting code from the ‘Default Write Off Posting Code’ registry setting displays in ‘Write Off Posting Code‘.
- Change the posting code to a different value.
- Click [Post Worklist].
- Click [OK].
- Close the form.
- Open ‘Client Ledger’.
- Select the client.
- Select ‘All Episodes’ in ‘Claim/Episode/All Episodes’.
- Enter the dates of service.
- Select the ‘Simple’ in ‘Ledger Type’.
- Click [Process].
- Validate that the posting code is the posting code that was selected when posting the worklist.
- Close the report.
- Close the form.
|
Topics
• Registry Settings
• Compile/Edit/Post/Unpost Roll-up Services Worklist
• Roll-Up Services Definition
• NX
• File Import
• myAvatar/myAvatar NX
|
Consent For Access - No CareConnect
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Consent For Access form - External Network - No CareConnect
Specific Setup:
- For this test to be valid, the system must not be connected to CareConnect.
Steps
- Open the "Consent For Access" form.
- On the "External Network" section, click "Add A New Item" button.
- Select "Network" in the "Consent For" field.
- Select a network in the "Network" dropdown.
- Make a selection in the "Consent to Send" radio group.
- Set "Start Date" to "Current Date".
- Click "Submit" button to file data.
- Open the "Consent For Access" form.
- Validate the data displays as it was data entered.
Scenario 2: Consent for Access - External Network - CareConnect
Specific Setup:
- System must be connected to CareConnect.
Steps
- Open the "Consent For Access" form.
- On the "External Network" section, click "Add A New Item" button.
- Select "Organization" in the "Consent For" field.
- Select an organization in the "Organization" dropdown.
- Make a selection in the "Consent to Query" radio group.
- Set "Start Date" to "Current Date".
- Click "Submit" button to file data.
- Open the "Consent For Access" form.
- Validate the data displays as it was data entered.
- Close the form.
|
Topics
• Consent for Access
• NX
|
Avatar PM 'Claim Follow-Up' Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: 'Claim Follow-Up' - Verification of Submission
Specific Setup:
- Avatar PM Registry Setting 'Claim Follow-Up' must be enabled
- Client with claim(s)/service(s) eligible for 'Claim Follow-Up' entry
Steps
- Open Avatar PM 'Claim Follow-Up' form; select client record for Claim Follow-Up entry.
- Select 'Add' in 'Add, Edit Or Delete Claim Follow-Up' field (or select 'Edit' for review/update of existing entry).
- Select value in 'Guarantor' field.
- Select value in 'Claim' field.
- Select value in 'Denial Type' field.
- Select value in 'Service(s)', 'Insurance Based Denial Reason' and '835 Denial Reason' if desired.
- Select value in 'Assign Claim For Electronic Re-Billing' field (and 'Claim Submission Reason Code' field if applicable).
- In Follow-Up Status/Comments form sub-section, select 'Add' in 'Add, Edit or Delete Row' field (or select 'Edit' for view/update of existing Follow-Up Status/Comments entry).
- Select value in 'Follow-Up Status' and 'Followed Up' fields.
- Enter/select values in 'Denial CRN#', 'Current CRN#', 'Next Follow-Up Date' and 'Completion Date' fields if desired.
- Enter value in 'Comments' field.
- Click 'Update Row' button to save Follow-Up Status/Comments entry.
- Click 'Submit' button to file 'Claim Follow-Up' form/record.
- Ensure filing confirmation dialog noting 'Claim Follow-Up has completed. Do you wish to return to form?' is presented; click 'Yes' button to return to 'Claim Follow-Up' form.
- Select 'Edit' in 'Add, Edit Or Delete Claim Follow-Up' field for review of existing entry.
- Select existing entry in 'Select Claim Follow-Up To Edit Or Delete' field.
- Ensure values for all fields are present in 'Claim Follow-Up' form as previously entered/field for selected entry, including rows/entries in the Follow-Up Status/Comments form sub-section.
|
Topics
• Claim Follow-up
• NX
|
837 Institutional - Service diagnosis when the 'Include Services with and Without Diagnosis Entry' option is selected
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Dictionary Update (PM)
- Guarantors/Payors
- Program Maintenance
- Admission (Outpatient)
- Recurring Client Charge Input (Diagnosis Entry)
- Client Ledger
- Electronic Billing
- Dynamic Form - Edit Service Fee Definition
- Dynamic form- Social Security Number
- Client Charge Input With Diagnosis Entry
- Service Codes
Scenario 1: 837 Professional - HCFA-1500/837-P Billing Options - Outpatient client
Specific Setup:
- Client 1:
- Is admitted to an outpatient program. Note the program.
- Has an active ‘Financial Eligibility’ record. Note the ‘Guarantor’ and ‘Financial Class’ for the guarantor.
- Has an active ‘Diagnosis’ record. Note the diagnosis code.
- Two charges, in the same month, have been entered in ‘Client Charge Input’. Note the last service date.
- Two charges, in the same month as above, have been entered in ‘Client Charge Input With Diagnosis Entry. Enter a code in ‘Diagnosis 1’ that is not the same diagnosis code as in the ‘Diagnosis’ record. The last date of service is before the last date of service entered in ‘Client Charge Input’.
- Client 2:
- Is admitted the same outpatient program. Note the program.
- Has an active ‘Financial Eligibility’ record for the same guarantor.
- Has an active ‘Diagnosis’ record. Note the diagnosis code.
- Two charges, in the same month, have been entered in ‘Client Charge Input’. Note the last service date.
- Two charges, in the same month as above, have been entered in ‘Client Charge Input With Diagnosis Entry. Enter a code in ‘Diagnosis 1’ that is not the same diagnosis code as in the ‘Diagnosis’ record. The last date of service is after the last date of service entered in ‘Client Charge Input’.
- Use ‘Close Charges’ to close the charges.
- The 'Guarantor/Program Billing Defaults' template for the guarantor and program combination has a value of '1' in '837 Professional', 'Maximum Service Information Per Claim Information (Maximum LX Per CLM)'.
- 'Form Designer' has been used to revert the 'Electronic Billing' section of the 'Electronic Billing' for to 'Netsmart Produced Changes'.
Steps
- Open 'Electronic Billing'.
- Select '837-Professional' in 'Billing Form'.
- Select 'Include Services With and Without Diagnosis Entry' in 'UB/837-I Billing Options'.
- Select 'Diagnosis Entry' in 'HCFA-1500/837-P Billing Options'.
- Verify that an 'Error' message is received stating: The 'Diagnosis Entry' and 'Include Services With and Without Diagnosis Entry' billing options cannot be used together.
- Click [OK].
- Verify that 'Include Services With and Without Diagnosis Entry' is still selected in 'HCFA-1500/837-P Billing Options'.
- Select the guarantor 'Financial Class' in 'Type' of Bill'.
- Select 'Individual' in 'Individual Or All Guarantors'.
- Select the desired 'Guarantor'.
- Select 'Outpatient' in 'Billing Type'.
- Select 'Sort File' in 'Billing Options'.
- Enter the desired 'File Description'.
- Select 'All Clients' in 'All Clients Or Interim Billing Batch'.
- Select the desired 'Program'.
- Select 'No' in 'Create Claims'.
- Enter the 'First Date of Service To Include'.
- Enter the 'Last Date of Service To Include'.
- Click [Process].
- Click [OK].
- Select 'Dump File' in 'Billing Options'.
- Select 'Print' in 'Print Or Delete Report'.
- Select the desired 'File'.
- Validate that four services are output for Client 1.
- Validate that for the two services created in 'Client Charge Input', that the 'HI* segments include only the diagnosis code from the 'Diagnosis' record.
- Validate that for the two services created in 'Client Charge Input With Diagnosis Entry', that the 'HI' segments include the diagnosis entered in 'Client Charge Input With Diagnosis Entry'.
- Validate that four services are output for Client 2.
- Validate that for the two services created in 'Client Charge Input', that the 'HI* segments include only the diagnosis code from the 'Diagnosis' record.
- Validate that for the two services created in 'Client Charge Input With Diagnosis Entry', that the 'HI' segments include the diagnosis entered in 'Client Charge Input With Diagnosis Entry'.
- Close the report.
- Close the form.
Scenario 2: Electronic Billing - UB/837-I Billing Options - Inpatient bill for an outpatient client
Specific Setup:
- Admission:
- A new client is admitted to an outpatient program. Note the program.
- Financial Eligibility:
- The client has an active ‘Financial Eligibility’ record. Note the ‘Guarantor’ and ‘Financial Class’ for the guarantor.
- Diagnosis:
- The client has an active ‘Diagnosis’ record with three diagnosis codes. (i.e. 1st row - F10.10 (Primary), 2nd row - F19.10 (Secondary), 3rd row - F70). Note the diagnosis codes.
- Client Charge Input With Diagnosis Entry:
- A service is rendered to the client. Enter a code in ‘Diagnosis 1’ that is not the same diagnosis code as in the ‘Diagnosis’ record. Note the date of service.
- Close Charges:
- Close the charges.
- The 'Guarantor/Program Billing Defaults' template for the guarantor and program combination has a value of '1' in '837 Institutional', 'Maximum Service Information Per Claim Information (Maximum LX Per CLM)'.
Steps
- Open 'Electronic Billing'.
- Select '837-Institutional' in 'Billing Form'.
- Select 'Include Services With and Without Diagnosis Entry' in 'UB/837-I Billing Options'.
- Verify that an 'Error' message is received stating: The 'Diagnosis Entry' and 'Include Services With and Without Diagnosis Entry' billing options cannot be used together.
- Select the guarantor 'Financial Class' in 'Type' of Bill'.
- Select 'Individual' in 'Individual Or All Guarantors'.
- Select the desired 'Guarantor'.
- Select 'Outpatient' in 'Billing Type'.
- Select 'Sort File' in 'Billing Options'.
- Enter the desired 'File Description'.
- Select 'All Clients' in 'All Clients Or Interim Billing Batch'.
- Select the desired 'Program'.
- Select 'No' in 'Create Claims'.
- Enter the 'First Date of Service To Include'.
- Enter the 'Last Date of Service To Include'.
- Click [Process].
- Click [OK].
- Select 'Dump File' in 'Billing Options'.
- Select 'Print' in 'Print Or Delete Report'.
- Select the desired 'File'.
- Validate that for the service created in the 'Client Charge Input With Diagnosis Entry', that the 'HI*ABF' segment includes the diagnosis entered in 'Client Charge Input With Diagnosis Entry'.
- Close the report.
- Close the form
Functional or Implementation Acknowledgment (997/999) - loading an Implementation Acknowledgment (999) file
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Functional or Implementation Acknowledgement (997/999)
Scenario 1: Functional or Implementation Acknowledgment (997/999) - Load / Compile an Implementation Acknowledgment (999) file
Specific Setup:
- This scenario needs to be tested in the system that has multiple root system codes (not sub-system codes).
- Create a 999 file to load/compile. Note the File name/ Path of the 999 file.
Steps
- Open the 'Functional or Implementation Acknowledgement (997/999)' form.
- Load the 999 file.
- Verify the file loads successfully.
- Compile the recently loaded file.
- Verify that there is no hard error found during compile the file.
- Close the report.
- Close the form.
CCBHC Billing – Transferring services to a secondary guarantor
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Guarantors/Payors
- Service Codes
- Admission (Outpatient)
- Dictionary Update (PM)
- Client Charge Input
- CCBHC PPS Compile
- Client Ledger
- Electronic Billing
- Individual Cash Posting (PM)
- Dynamic Form - Individual Cash Posting - Information
- Dynamic Form - Individual Cash Posting - Alert
- Dynamic Form - Individual Cash Posting - Client
- Dynamic Form - Edit Service Fee Definition
Scenario 1: CCBHC Billing - 837 Professional for the secondary guarantor when the enumerated and partial service transferred to secondary guarantor - CCBHC Claim grouping =Same
Specific Setup:
- CCBHC setup has been completed.
- Dictionary Update:
- Two new covered charge categories are created in Client File - Data Element # 10021.
- Category 1: Is to be used for the CCBHC-Enumerated service. Give it the desired name. Set Type Of Billing Category attribute to 'Ancillary/Outpatient/Other'.
- Category 2: Is to be used for the CCBHC-PPS service. Give it the desired name. Set Type Of Billing Category attribute to 'Ancillary/Outpatient/Other'.
- Guarantors/Payors 1:
- Is a CCBHC Guarantor. Note the guarantor's code/name/financial class of the guarantor.
- The Financial Class does not equal Self-Pay.
- Allow Customization of Guarantor Plan = Yes.
- Select Category 1 in the 'Categories Available For Reviews'.
- Guarantors/Payors 2: Note the guarantor's code/name/financial class of the guarantor.
- Is a CCBHC Guarantor.
- The Financial Class does not equal Self-Pay and is the same financial class of Guarantor 1.
- Allow Customization of Guarantor Plan = Yes.
- Select Category 2 in the 'Categories Available For Reviews'.
- Admission:
- A client is enrolled in an outpatient program. Note the program.
- Diagnosis:
- Client has an active diagnosis record. Note the diagnosis code.
- Financial Eligibility: The financial eligibility record is:
- ‘Guarantor 1 is set up as a primary guarantor.
- The 'Customize Guarantor Plan' has a value of 'Yes'.
- In the 'Customize Plan' section the Category 1 is selected in the 'Covered Charge Categories'.
- ‘Guarantor 2 is set up as a secondary guarantor.
- The 'Customize Guarantor Plan' has a value of 'Yes'.
- In the 'Customize Plan' section the Category 2 is selected in the 'Covered Charge Categories'.
- Service Code 1:
- Is a CCBHC enumerated service code. Select Category 1 in the 'Covered Charge Category.' field. Note the Covered Charge Category.
- Has a fee definition in Service Fee/Cross Reference Maintenance.
- Service Code 2:
- Is a CCBHC non-enumerated service code. Select Category 2 in the 'Covered Charge Category.' field. Note the Covered Charge Category.
- Has a fee definition in Service Fee/Cross Reference Maintenance.
- Client Charge Input:
- A service for Service Code 1 is rendered to the client.
- Client Ledger:
- Services have liability distributed to Guarantor 1. Note the service dates. Note the 'CHG' amount.
- Use 'Close Charges' to close the charges.
- CCBHC PPS Definition:
- The CCBHC PPS service definition is created for the CCBHC PPS non-enumerated service code.
- Create the 'CCBHC PPS Compile' for the client/the dates of service. Review the report to verify that the client is included with no errors.
- Client Ledger:
- The CCBHC PPS service for the client is distributed to the secondary guarantor. Do not close that charge.
- 'Guarantor/Program Billing Defaults' for the CCBHC guarantor and the program for Client:
- CCBHC Claim Grouping = None
- Maximum Service Information Per Claim Information (Maximum LX Per CLM)’ = blank
- Create an interim billing batch to include services for the financial class defined for the guarantors assigned to the client.
Steps
- Open 'Electronic Billing'.
- Compile the 837 Professional bill for the financial class without claiming.
- Set the 'All Or Individual Guarantor' field to 'All'.
- Select the interim billing batch.
- Set the 'Include CCBHC Services' to 'Yes'.
- Compile the bill.
- Verify the bill compiles successfully.
- Select 'Run Report' in 'Billing Options'.
- Select 'Print' in Print Or Delete Report'.
- Select the 'File'.
- Click [Print 837 Report].
- Verify that the correct primary guarantor is included for the CCBHC Enumerated service.
- Click [X].
- Click [X].
|
Topics
• 837 Professional
• NX
• 837 Institutional
• Functional or Implementation Acknowledgement (997/999)
|
AR Console User Defaults Setup - Programs
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- AR Console User Defaults Setup
- HomeView.Accounts Receivable Console
Scenario 1: AR Console User Defaults Setup - field validation
Specific Setup:
- The following registry setting has a value of Y: Avatar PM->Billing->Accounts Receivable Management->->->Enable Accounts Receivable Management Functionality.
- User Definition has been used to give the signed in user access to the form: Avatar PM / Billing / AR Management / AR Console User Defaults Setup.
- View Definition / NX View Definition has been used to place the widget on the tester's home view.
- Note the ID of two additional users.
Steps
- Open ‘AR Console User Defaults Setup’.
- Click ‘New Row’ and add a row for the signed in user, or if the signed in user exists in a row select the row.
- Click ‘All’ in the following fields: ‘Financial Class(es)’, ‘Guarantor(s)’, ‘Treatment Setting(s)’ ‘Program(s)’ and ‘Client Last Name Initials to be Worked’.
- Add desired value to ‘Aged Over # Days’.
- Click ‘New Row’ and add a row for the first additional user from ‘Setup’, or if the user exists in a row select the row.
- Make any desired changes.
- Note the values of each field.
- Click ‘New Row’ and add a row for the second additional user from ‘Setup’, or if the user exists in a row select the row.
- Make any desired changes.
- Note the values of each field.
- Click [Submit].
- Open ‘AR Console User Defaults Setup’.
- Select the row for the signed in user.
- Validate that the following fields have every available item in the checklist selected: ‘Financial Class(es)’, ‘Guarantor(s)’, ‘Treatment Setting(s)’ ‘Program(s)’ and ‘Client Last Name Initials to be Worked’.
- Select the row for the first additional user.
- Validate that the values that were submitted were retained.
- Select the row for the second additional user.
- Validate that the values that were submitted were retained.
- Click [Discard].
|
Topics
• Accounts Receivable Management
• NX
|
835 Health Care Claim Payment/Advice - EFT Trace Number
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Admission (Outpatient)
- Client Charge Input
- Client Ledger
- Dynamic Form - Edit Service Fee Definition
- Electronic Billing
- 835 Health Care Claim Payment/Advice (PM)
Scenario 1: 835 Health Care Claim Payment/Advice - Duplicated TRN segment error message validation.
Specific Setup:
- 835 Health Care Claim Payment/Advice:
- Copy the 'TRN' segment from a file that has been posted to an unloaded file.
Steps
- Open '835 Health Care Claim Payment/Advice'.
- Load the unloaded file from Setup.
- Compile the file.
- Post the file.
- Validate that the following message is received, noting that some information will vary: "An EFT Trace Number (TRN-02) / Payer Identifier (TRN-03) combination found in this file is present in an existing file that is already posted: Status: Posted - Date: 05/18/2022 - Time: 03:33:57PM - By: TEMPORARY SYSTEM ADMINISTRATOR Load aborted."
- Close the form.
Scenario 2: 835 Health Care Claim Payment/Advice - No error messge when TRN segment is not duplicated.
Specific Setup:
- 835 Health Care Claim Payment/Advice:
- Two unloaded files exist and the 'TRN' segments in the files are not the same.
Steps
- Open '835 Health Care Claim Payment/Advice'.
- Load the first unloaded file from Setup.
- Compile the file.
- Post the file.
- Load the second unloaded file from Setup.
- Compile the file.
- Post the file.
- No error message is received stating that the 'TRN' segment is duplicated.
|
Topics
• 835 Health Care Claim Payment/Advice
• NX
|
Disclosure Management - Future Dates
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Disclosure Management - Future Dates
Specific Setup:
- Using 'Site Specific Section Modeling' the following fields must be set accordingly:
- "Request Date" set to a 'warning' ("Warning").
- "'Request For Information Start Date" set to an error dialog when future dates are selected ("Error").
- "'Request For Information End Date" set to an error dialog when future dates are selected ("Error").
- "Authorization Start Date" set to a warning ("Warning").
- "Authorization End Date" set to a warning ("Warning").
- "Disclosure Date" set to a warning ("Warning").
- A client must be enrolled in an existing episode (Client A).
Steps
- Select "Client A" and access the 'Disclosure Management' form.
- Set the 'Request Date' field to a future date.
- Validate the 'Warning' Dialog is displayed and click [Cancel].
- Set the 'Request Date' field to the current date.
- Validate the 'Request Date' field is set to the current date.
- Set the 'Request For Information Start Date' field to a future date.
- Validate the 'Error' Dialog is displayed and click [OK].
- Set the 'Request For Information Start Date' field to a date in the past.
- Validate the 'Request For Information Start Date' field is set a date in the past.
- Set the 'Request For Information End Date' field to a future date.
- Validate the 'Error' Dialog is displayed and click [OK].
- Set the 'Request For Information End Date' field to the current date.
- Validate the 'Request For Information End Date' field is set to the current date.
- Select desired episodes from the 'Request Episode(s)' field.
- Select desired items from the 'Requested Chart Items' field.
- File and save an Organization.
- Select 'Authorization'.
- Set the 'Authorization Start Date' field to a future date.
- Validate the 'Warning' Dialog is displayed and click [Cancel].
- Set the 'Authorization Start Date' field to a date in the past.
- Validate the 'Authorization Start Date' field is set a date in the past.
- Set the 'Authorization End Date' field to a future date.
- Validate the 'Warning' Dialog is displayed and click [Cancel].
- Set the 'Authorization End Date' field to the current date.
- Validate the 'Authorization End Date' field is set to the current date.
- Select desired episodes from the 'Authorization Episode(s)' field.
- Select "Yes" and click [Update Chart Items Authorized for Disclosure].
- Click [Save].
- Select 'Disclosure'.
- Set the 'Disclosure Date' field to a future date.
- Validate the 'Warning' Dialog is displayed and click [Cancel].
- Set the 'Disclosure Date' field to the current date.
- Set the 'Disclosure Time' to the current time.
- Select desired charts from the 'Chart Disclosure Information'.
- Select 'Electronic' and click [Process].
- Select "Client A" and access the 'Disclosure Management' form.
- Validate a new disclosure was filed.
|
Topics
• Disclosure
|
Quick Action - Update Client Data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- View Definition
- Dynamic Form - View Definition - Select Views
- NX View Definition
- Dynamic Form - NX View Definition
- MPI Search
- Admission
- Quick Actions Page
- Update Client Data
Scenario 1: Quick Action - Update Client Data - 9 digit zip code
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Admit a test client.
Steps
- Select the test client.
- Navigate to the "Quick Actions" widget.
- Locate the "Update Client Data" Quick Action.
- Click "Add" button.
- Enter an address with a 9-digit zip code.
- Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
- Click "Save".
- Click "Add" on the "Update Client Data" Quick Action.
- Validate the "Zip Code", "City" and "State" fields display appropriately.
- Open the "Update Client Data" form.
- Validate the same fields all display in uppercase letters.
Scenario 2: Quick Action - Update Client Data - 5 digit zip code
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Admit a test client.
Steps
- Select the test client.
- Navigate to the "Quick Actions" widget.
- Locate the "Update Client Data" Quick Action.
- Click "Add" button.
- Enter an address with a 5-digit zip code.
- Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
- Click "Save".
- Click "Add" on the "Update Client Data" Quick Action.
- Validate the "Zip Code", "City" and "State" fields display appropriately.
- Open the "Update Client Data" form.
- Validate the same fields all display in uppercase letters.
Scenario 3: Quick Action - Update Client Data - 9 digit zip code
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Admit a test client.
Steps
- Select the test client.
- Navigate to the "Quick Actions" widget.
- Locate the "Update Client Data" Quick Action.
- Click "Add" button.
- Enter an address with a 9-digit zip code.
- Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
- Click "Save".
- Click "Add" on the "Update Client Data" Quick Action.
- Validate the "Zip Code", "City" and "State" fields display appropriately.
- Open the "Update Client Data" form.
- Validate the same fields all display in uppercase letters.
Scenario 4: Quick Action - Update Client Data - 5 digit zip code
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Admit a test client.
Steps
- Select the test client.
- Navigate to the "Quick Actions" widget.
- Locate the "Update Client Data" Quick Action.
- Click "Add" button.
- Enter an address with a 5-digit zip code.
- Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
- Click "Save".
- Click "Add" on the "Update Client Data" Quick Action.
- Validate the "Zip Code", "City" and "State" fields display appropriately.
- Open the "Update Client Data" form.
- Validate the same fields all display in uppercase letters.
Quick Action - Update Client Data
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- View Definition
- Dynamic Form - View Definition - Select Views
- NX View Definition
- Dynamic Form - NX View Definition
- MPI Search
- Admission
- Quick Actions Page
- Update Client Data
Scenario 1: Quick Action - Update Client Data - 9 digit zip code
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Admit a test client.
Steps
- Select the test client.
- Navigate to the "Quick Actions" widget.
- Locate the "Update Client Data" Quick Action.
- Click "Add" button.
- Enter an address with a 9-digit zip code.
- Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
- Click "Save".
- Click "Add" on the "Update Client Data" Quick Action.
- Validate the "Zip Code", "City" and "State" fields display appropriately.
- Open the "Update Client Data" form.
- Validate the same fields all display in uppercase letters.
Scenario 2: Quick Action - Update Client Data - Convert Client Address to All Uppercase enabled
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Admit a test client.
- Enable registry setting "Convert Client Address To All Uppercase".
Steps
- Select the test client.
- Navigate to the "Quick Actions" widget.
- Locate the "Update Client Data" Quick Action.
- Click "Add" button.
- Enter "Address - Street", "Apartment or Unit", and "City" in all lower case letters.
- Validate that once you tab out of the field, it's converted to all uppercase letters.
- Click "Save".
- Click "Add" on the "Update Client Data" Quick Action.
- Validate the data that displays in "Address - Street", "Apartment or Unit", and "City" are all uppercase letters.
- Open the "Update Client Data" form.
- Validate the same fields all display in uppercase letters.
Scenario 3: Quick Action - Update Client Data - Validate name change
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Admit a test client.
Steps
- Select the test client.
- Navigate to the "Quick Actions" widget.
- Locate the "Update Client Data" Quick Action.
- Click "Add" button.
- Change the client's first and last name.
- Fill in all other fields.
- Click "Save".
- Open the "Update Client Data" form.
- Validate the first and last name are changed.
- Using SQL, validate the name change is reflected in the columns, patient_name, patient_name_first, patient_name_last in SYSTEM.patient_current_demographics SQL.
Scenario 4: Quick Action - Update Client Data - 5 digit zip code
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Admit a test client.
Steps
- Select the test client.
- Navigate to the "Quick Actions" widget.
- Locate the "Update Client Data" Quick Action.
- Click "Add" button.
- Enter an address with a 5-digit zip code.
- Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
- Click "Save".
- Click "Add" on the "Update Client Data" Quick Action.
- Validate the "Zip Code", "City" and "State" fields display appropriately.
- Open the "Update Client Data" form.
- Validate the same fields all display in uppercase letters.
Scenario 5: Quick Action - Update Client Data - Update Financial Eligibility Data enabled
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Select a client who has existing financial eligibility data.
- Enable the registry setting "Update Financial Eligibility Data".
Steps
- Navigate to the "Quick Action" widget.
- Click "Add" on the "Update Client Data" item.
- Enter a new name and address for the client with existing financial eligibility data.
- Enter the following SQL statement to view the listed fields in SYSTEM.billing_guar_subs_data: SELECT subs_name,subs_name_first,subs_name_last,subs_address_street1,subs_address_street2,subs_address_city,subs_address_state,subs_addess_zip FROM SYSTEM.billing_guar_subs_data to validate that these columns were changed when the Quick Action was filed.
Scenario 6: Quick Action - Update Client Data - Update Financial Eligibility Data disabled
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Select a client who has existing financial eligibility data.
- Disable the registry setting "Update Financial Eligibility Data".
Steps
- Navigate to the "Quick Action" widget.
- Click "Add" on the "Update Client Data" item.
- Enter a new name and address for the client with existing financial eligibility data.
- Enter the following SQL statement to view the listed fields in SYSTEM.billing_guar_subs_data: SELECT subs_name,subs_name_first,subs_name_last,subs_address_street1,subs_address_street2,subs_address_city,subs_address_state,subs_addess_zip FROM SYSTEM.billing_guar_subs_data to validate that these columns were not changed when the Quick Action was filed.
Scenario 7: Quick Action - Update Client Data - 9 digit zip code
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Admit a test client.
Steps
- Select the test client.
- Navigate to the "Quick Actions" widget.
- Locate the "Update Client Data" Quick Action.
- Click "Add" button.
- Enter an address with a 9-digit zip code.
- Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
- Click "Save".
- Click "Add" on the "Update Client Data" Quick Action.
- Validate the "Zip Code", "City" and "State" fields display appropriately.
- Open the "Update Client Data" form.
- Validate the same fields all display in uppercase letters.
Scenario 8: Quick Action - Update Client Data - Convert Client Address to All Uppercase enabled
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Admit a test client.
- Enable registry setting "Convert Client Address To All Uppercase".
Steps
- Select the test client.
- Navigate to the "Quick Actions" widget.
- Locate the "Update Client Data" Quick Action.
- Click "Add" button.
- Enter "Address - Street", "Apartment or Unit", and "City" in all lower case letters.
- Validate that once you tab out of the field, it's converted to all uppercase letters.
- Click "Save".
- Click "Add" on the "Update Client Data" Quick Action.
- Validate the data that displays in "Address - Street", "Apartment or Unit", and "City" are all uppercase letters.
- Open the "Update Client Data" form.
- Validate the same fields all display in uppercase letters.
Scenario 9: Quick Action - Update Client Data - 5 digit zip code
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Admit a test client.
Steps
- Select the test client.
- Navigate to the "Quick Actions" widget.
- Locate the "Update Client Data" Quick Action.
- Click "Add" button.
- Enter an address with a 5-digit zip code.
- Validate that once you tab out of the field, it populates with the "City" and "State" values appropriate for the zip code.
- Click "Save".
- Click "Add" on the "Update Client Data" Quick Action.
- Validate the "Zip Code", "City" and "State" fields display appropriately.
- Open the "Update Client Data" form.
- Validate the same fields all display in uppercase letters.
Scenario 10: Quick Action - Update Client Data - Update Financial Eligibility Data enabled
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Select a client who has existing financial eligibility data.
- Enable the registry setting "Update Financial Eligibility Data".
Steps
- Navigate to the "Quick Action" widget.
- Click "Add" on the "Update Client Data" item.
- Enter a new name and address for the client with existing financial eligibility data.
- Enter the following SQL statement to view the listed fields in SYSTEM.billing_guar_subs_data: SELECT subs_name,subs_name_first,subs_name_last,subs_address_street1,subs_address_street2,subs_address_city,subs_address_state,subs_addess_zip FROM SYSTEM.billing_guar_subs_data to validate that these columns were changed when the Quick Action was filed.
Scenario 11: Quick Action - Update Client Data - Update Financial Eligibility Data disabled
Specific Setup:
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the Quick Action for "Update Client Data".
- Select a client who has existing financial eligibility data.
- Disable the registry setting "Update Financial Eligibility Data".
Steps
- Navigate to the "Quick Action" widget.
- Click "Add" on the "Update Client Data" item.
- Enter a new name and address for the client with existing financial eligibility data.
- Enter the following SQL statement to view the listed fields in SYSTEM.billing_guar_subs_data: SELECT subs_name,subs_name_first,subs_name_last,subs_address_street1,subs_address_street2,subs_address_city,subs_address_state,subs_addess_zip FROM SYSTEM.billing_guar_subs_data to validate that these columns were not changed when the Quick Action was filed.
Quick Action - Emergency Contact Information
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- View Definition
- Dynamic Form - View Definition - Select Views
- NX View Definition
- Dynamic Form - NX View Definition
- Quick Actions Page
Scenario 1: Quick Action - Emergency Contact Information - Sort Episodes by Admission Date registry setting enabled
Specific Setup:
- Registry Setting "Sort Episodes By Admission Date" is enabled.
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the "Emergency Contact Information" form to the available "Quick Actions".
Steps
- Select a test client.
- Navigate to the "Quick Actions" widget.
- Select the "Emergency Contact Information Quick Action".
- Fill out the form, noting that the Episodes are sorted in admission date order.
Scenario 2: Quick Action - Emergency Contact Information - Sort Episodes by Admission Date disabled
Specific Setup:
- Registry Setting "Sort Episodes By Admission Date" is disabled.
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the "Emergency Contact Information" form to the available "Quick Actions".
Steps
- Select a test client.
- Navigate to the "Quick Actions" widget.
- Select the "Emergency Contact Information Quick Action".
- Fill out the form, noting that the Episodes aren't sorted in admission date order.
Scenario 3: Quick Action - Emergency Contact Information - Sort Episodes by Admission Date registry setting enabled
Specific Setup:
- Registry Setting "Sort Episodes By Admission Date" is enabled.
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the "Emergency Contact Information" form to the available "Quick Actions".
Steps
- Select a test client.
- Navigate to the "Quick Actions" widget.
- Select the "Emergency Contact Information Quick Action".
- Fill out the form, noting that the Episodes are sorted in admission date order.
Scenario 4: Quick Action - Emergency Contact Information - Sort Episodes by Admission Date disabled
Specific Setup:
- Registry Setting "Sort Episodes By Admission Date" is disabled.
- Using the "View Definition" form, add the "Quick Actions" widget to the user's HomeView.
- Using the "NX View Definition" form, add the "Emergency Contact Information" form to the available "Quick Actions".
Steps
- Select a test client.
- Navigate to the "Quick Actions" widget.
- Select the "Emergency Contact Information Quick Action".
- Fill out the form, noting that the Episodes aren't sorted in admission date order.
|
Topics
• Update Client Data
• NX
|
Delete Last Movement
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Orders This Episode
- Delete Last Movement
- Treatment Plan
- Admission
- Patient Account Number Maintenance
- HL7 Connection Monitor
Scenario 1: Validate 'Delete Last Movement' can be completed when a client has an active order and 'Prevent Delete Admission Movement on Clients with Clinical Data' set to "N".
Specific Setup:
- The 'Avatar PM->System Maintenance->Client Maintenance->->->Prevent Delete Admission Movement on Clients with Clinical Data' registry setting must be set to "N".
- Please log out of the application and log back in after completing the above configuration.
- A client must have an active inpatient episode. (Client A)
- “Client A” must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
Steps
- Select "Client A" and access the Order Entry Console.
- Search for and select "GOOD NEIGHBOR PHARMACY NAPROXEN SODIUM 220 MG CAPSULE, LIQUID FILLED ORAL" in the 'New Order' field.
- Set the 'Dose' field to "1".
- Select "Tablet" in the 'Dose Unit' field.
- Select "As Needed" in the 'Freq' field.
- Set the 'Duration' field to "10" and click [Days].
- Click [Add to Scratchpad] and [Sign].
- Validate the 'Order grid' contains an order for "GOOD NEIGHBOR PHARMACY NAPROXEN SODIUM 220 MG ORAL CAPSULE, LIQUID FILLED 1 Tablet, AS NEEDED".
- Access the 'Delete Last Movement' form.
- Validate a message is displayed stating "Deletion of any movement will remove the client from any bed they may be in. If a client needs to be in a bed, it needs to be entered via Unit/Room/Bed Assignment." and click [OK].
- Select "Episode # 1" in the 'Episode Number' field.
- Validate a message is displayed stating "There is data submitted within the associated CWS application for this episode number. Do you want to continue?" and click [OK].
- Validate the 'Client Information' field contains all information pertaining to "Client A" and their episode.
- Click [Submit].
- Validate a message is displayed stating "You are about to delete an Admission movement for episode 1. Do you want to continue?" and click [Yes]
- Validate the 'Client Name' Header contains "Client A's First Name Last Name (PATID)".
- Validate the 'Header Episode' does not contain a value.
Scenario 2: Validate Delete Last Movement does not undo an Admission when a client has information filed in 'Treatment Plan' and 'Prevent Delete Admission Movement on Clients with Clinical Data'="Y"
Specific Setup:
- The 'Avatar PM->System Maintenance->Client Maintenance->->->Prevent Delete Admission Movement on Clients with Clinical Data' registry setting to "Y".
- Please log out of the application and log back in after completing the above configuration.
- A client must have an active Inpatient episode. (Client A).
Steps
- Select "Client A" and access the 'Treatment Plan' form.
- Select the current date in the 'Plan Date' field.
- Set the 'Plan Name' field to any value.
- Select any value in the 'Plan Type' field.
- Select "Final" in the 'Treatment Plan Status' field and click [Submit].
- Validate the 'Document Routing' dialog is displayed and click [Accept].
- Set the 'Password' field to the password for the user who is logged into the application and click [Verify].
- Access the 'Delete Last Movement' form.
- Validate a message is displayed "Deletion of any movement will remove the client from any bed they may be in. If a client needs to be in a bed, it needs to be entered via Unit/Room/Bed Assignment." and click [OK].
- Select "Episode # 1" in the 'Episode Number' field.
- Validate a message is displayed stating "There is data submitted within the associated CWS application for this episode number. Cannot continue." and click [OK].
;
Scenario 3: Validate Delete Last Movement via HL7 Inbound ADT message does not undo an Admission when a client has 'Treatment Plan' info and 'Prevent Delete Admission Movement on Clients with Clinical Data'="Y"
Specific Setup:
- An Inbound ADT connection must exist.
- The 'Avatar PM->System Maintenance->Client Maintenance->->->Prevent Delete Admission Movement on Clients with Clinical Data' registry setting must be set to "Y".
- Please log out of the application and log back in after completing the above configuration.
Steps
- Access the 'Admission' form.
- Set the 'Last Name' field to any value and press Tab.
- Set the 'First Name' field to any value and press Tab.
- Select any value in the 'Sex' field.
- Set the 'Social Security Number' field to any value and press Tab.
- Set the 'Date of Birth' field to any value and press Tab.
- Click [Search] and [New Client].
- Validate a message is displayed stating "Auto Assign Next ID Number?" and click [Yes].
- Validate the 'Client Name' field contains the value entered in the 'Last Name' and 'First Name' fields in the format of Last Name,First Name.
- Fill out all required fields, ensuring to select an Inpatient program in the 'Program' field, and that the 'Admitting Practitioner' field contains the staff member associated with the user who is logged into the application.
- Select the 'Demographics' section and fill out the 'Address - Street', 'Zipcode', and 'Home Phone' fields.
- Select the 'Inpatient/Partial/Day Treatment' section and select a value in the 'Unit', 'Room', 'Bed', and 'Room And Board Billing Code' fields and click [Submit].
- Validate that the client created above is selected and access the 'Treatment Plan' form.
- Select the current date in the 'Plan Date' field.
- Set the 'Plan Name' field to any value.
- Select any value in the 'Plan Type' field.
- Select "Draft" in the 'Treatment Plan Status' field and click [Submit].
- Access the 'Patient Account Number Maintenance' form
- Search for and select "Client A" in the 'Client ID' field.
- Select "Episode # 1" in the 'Episode' field.
- Select "Add" in the 'Action' field.
- Set the 'Effective Date' field to the current date.
- Validate a message is displayed stating "By default the effective date for the first patient account number filed should not be later than the admission date. This is to ensure that for any services rendered there is an associated patient account number on file." and click [OK].
- Set the 'Patient Account Number' field to any unique value. (IA0000022559) and click [Submit].
- Validate a message is displayed stating "Patient Account Number Maintenance has completed. Do you wish to return to form?" and click [No].
- The 'External Client ID Maintenance' form must contain a unique id for the client created above. This is a Netsmart Staff only form.
- An Inbound ADT-11 (Cancel Admission) message comes into the application via Avatar HL7 for the client and episode above.
- Access the 'HL7 Connection Monitor' form and select the "ADT-INBOUND" connection.
- Click [Show Transaction Log].
- Validate there is a message with an 'Event Type' of "A11" for the client created above with a message of "There is data submitted within the associated CWS application for this episode number. Cannot continue."
- Close the report and the form.
Scenario 4: Validate Delete Last Movement does not undo an Admission when a client has orders and 'Prevent Delete Admission Movement on Clients with Clinical Data'="Y"
Specific Setup:
- The 'Avatar PM->System Maintenance->Client Maintenance->->->Prevent Delete Admission Movement on Clients with Clinical Data' registry setting to "Y".
- Please log out of the application and log back in after completing the above configuration.
Steps
- Access the 'Admission' form.
- Set the 'Last Name' field to any value and press Tab.
- Set the 'First Name' field to any value and press Tab.
- Select any value in the 'Sex' field.
- Set the 'Social Security Number' field to any value and press Tab.
- Set the 'Date of Birth' field to any value and press Tab.
- Click [Search] and [New Client].
- Validate a message is displayed stating "Auto Assign Next ID Number?" and click [Yes].
- Validate the 'Client Name' field contains the value entered in the 'Last Name' and 'First Name' fields in the format of Last Name,First Name.
- Fill out all required fields, ensuring to select an Inpatient program in the 'Program' field, and that the 'Admitting Practitioner' field contains the staff member associated with the user who is logged into the application.
- Select the 'Demographics' section and fill out the 'Address - Street', 'Zipcode', and 'Home Phone' fields.
- Select the 'Inpatient/Partial/Day Treatment' section and select a value in the 'Unit', 'Room', 'Bed', and 'Room And Board Billing Code' fields and click [Submit].
- Access the Order Entry Console.
- Search for and select "ADVIL COLD & SINUS 200 MG-30 MG TABLET ORAL" in the 'New Order' field.
- Set the 'Dose' field to "1".
- Validate the 'Dose Unit' field contains "Tablet".
- Select "As Needed" in the 'Freq' field.
- Set the 'Duration' field to "28" and click [Days].
- Validate the 'Days Supply' field contains "28".
- Validate the 'Dispense Qty' field contains "28"
- Select "Tablet" in the 'Dispense Qty Unit' field.
- Click [Add to Scratchpad] and [Final Review].
- Validate the 'Interactions' dialog is displayed
- Override all interactions and click [Save Override and Exit].
- Validate the 'Final Review' dialog is displayed.
- Select "None" in the 'Output' field and click [Sign].
- Validate the 'Order grid' contains an order for "ADVIL COLD & SINUS 200 MG-30 MG ORAL TABLET1 Tablet, AS NEEDED".
- Access the 'Delete Last Movement' form.
- Validate a message is displayed stating "Deletion of any movement will remove the client from any bed they may be in. If a client needs to be in a bed, it needs to be entered via Unit/Room/Bed Assignment." and click [OK].
- Select "Episode 1" in the 'Episode Number' field.
- Validate a message is displayed stating "There is data submitted within the associated CWS application for this episode number. Cannot continue." and click [OK].
- Close the form.
Scenario 5: Validate Delete Last Movement via an HL7 Inbound ADT message does not undo an Admission when a client has orders and 'Prevent Delete Admission Movement on Clients with Clinical Data'="Y"
Specific Setup:
- The 'Avatar PM->System Maintenance->Client Maintenance->->->Prevent Delete Admission Movement on Clients with Clinical Data' registry setting to "Y".
- Please log out of the application and log back in after completing the above configuration.
- A client must have an active inpatient episode. (Client A)
- The 'External Client ID Maintenance' form must contain a unique value for "Client A". This is a Netsmart Staff only form.
Steps
- Access the 'Patient Account Number Maintenance' form
- Search for and select "Client A" in the 'Client ID' field.
- Select "Episode # 1" in the 'Episode' field.
- Select "Add" in the 'Action' field.
- Set the 'Effective Date' field to the current date.
- Validate a message is displayed stating "By default the effective date for the first patient account number filed should not be later than the admission date. This is to ensure that for any services rendered there is an associated patient account number on file." and click [OK].
- Set the 'Patient Account Number' field to any unique value. (IA0000022559) and click [Submit].
- Validate a message is displayed stating "Patient Account Number Maintenance has completed. Do you wish to return to form?" and click [No].
- Select "Client A" and access the Order Entry Console.
- Search for and select "ADVIL COLD & SINUS 200 MG-30 MG TABLET ORAL" in the 'New Order' field.
- Set the 'Dose' field to "1".
- Validate the 'Dose Unit' field contains "Tablet".
- Select "As Needed" in the 'Freq' field.
- Set the 'Duration' field to "28" and click [Days].
- Validate the 'Days Supply' field contains "28".
- Validate the 'Dispense Qty' field contains "28"
- Select "Tablet" in the 'Dispense Qty Unit' field.
- Click [Add to Scratchpad] and [Final Review].
- Validate the 'Interactions' dialog is displayed
- Override all interactions and click [Save Override and Exit].
- Validate the 'Final Review' dialog is displayed.
- Select "None" in the 'Output' field and click [Sign].
- Validate the 'Order grid' contains an order for "ADVIL COLD & SINUS 200 MG-30 MG ORAL TABLET1 Tablet, AS NEEDED".
- An Inbound ADT "A11" (Cancel Admission) message comes into the application via Avatar HL7.
- Access the 'HL7 Connection Monitor' form.
- Select the Inbound ADT connection in the 'Select Row' field.
- Set the 'Search Pattern 1" field to "Client A's Last Name".
- Click [Show Transaction Log].
- Validate the 'HL7 Inbound Transaction Report' is displayed.
- Validate there is a row for an 'Event Type' of "A11" with a 'Message Received' of "There is data submitted within the associated CWS application for this episode number. Cannot continue."
- Close the report and the form.
Scenario 6: Validate 'Delete Last Movement' can be completed when a client has an active Treatment Plan and 'Prevent Delete Admission Movement on Clients with Clinical Data' set to "N".
Specific Setup:
- The 'Avatar PM->System Maintenance->Client Maintenance->->->Prevent Delete Admission Movement on Clients with Clinical Data' registry setting must be set to "N".
- Please log out of the application and log back in after completing the above configuration.
- A client must have an active inpatient episode. (Client A)
Steps
- Select "Client A" and access the 'Treatment Plan' form.
- Set the 'Plan Date' field to the current date.
- Set the 'Plan Name' field to any value.
- Select any value in the 'Plan Type' field.
- Select "Final" in the 'Treatment Plan Status' field and click [Submit].
- Validate the 'Document Routing' dialog is displayed and click [Accept].
- Set the 'Password' field to the password of the user that is logged into the application and click [Verify].
- Validate that "Client A" is selected and access the 'Delete Last Movement' form.
- Validate a message is displayed stating "Deletion of any movement will remove the client from any bed they may be in. If a client needs to be in a bed, it needs to be entered via Unit/Room/Bed Assignment." and click [OK].
- Select "Episode # 1" in the 'Episode Number' field.
- Validate a message is displayed stating "There is data submitted within the associated CWS application for this episode number.Do you want to continue?" and click [OK].
- Validate the 'Client Information' field contains information pertaining to "Client A" and "Episode #1".
- Click [Submit].
- Validate a message is displayed stating "You are about to delete an Admission movement for episode 1. Do you want to continue?" and click [Yes]
- Validate the 'Client Name' Header contains "Client A's First Name Last Name (PATID)".
- Validate the 'Header Episode' does not contain a value.
|
Topics
• Delete Last Movement
• NX
• Treatment Plan
• myAvatar/myAvatar NX
• HL7
• Admission
• Order Entry Console
|
Avatar NX - 'Emergency Contact' quick action
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Quick Actions Page
- Update Client Data
Scenario 1: Validate accessing various 'Quick Actions' from the 'Client Dashboard'
Specific Setup:
- A client must be admitted to an active episode (Client A).
- "Client A" must not have data saved in the 'Smoking Assessment' quick action.
- 'Update Client Data', 'Smoking Assessment', 'Problem List', 'Emergency Contact', and 'Alerts' Quick Actions must be assigned to the user in the 'NX View Definition' form.
- This scenario must be tested in an Avatar NX system.
Steps
- Select "Client A" and launch the 'Client Dashboard'.
- Validate there is no grey box behind the client's name.
- Navigate to the 'Quick Actions' widget.
- Click [Update Client Data - Add].
- Click outside of the 'Update Client Data' dialog.
- Validate the dialog is fixed and centered in the screen.
- Enter "LASTNAME, FIRSTNAME" in the 'Name' field and press the "Tab" key.
- Validate the space is automatically removed after the comma.
- Click the 'State' field and validate the states are listed alphabetically.
- Populate the required and desired fields.
- Click [Save].
- Click [Emergency Contact - Add].
- Click outside of the 'Emergency Contact' dialog.
- Validate the dialog is fixed and centered in the screen.
- Enter "LASTNAME, FIRSTNAME" in the 'Emergency Contact Name' field and press the "Tab" key.
- Validate the space is automatically removed after the comma.
- Fill out any required any desired fields.
- Click [Save].
- Click [Smoking Assessment - Add].
- Click outside of the 'Smoking Assessment' dialog.
- Validate the dialog is fixed and centered in the screen.
- Populate the required fields.
- Click [Save].
- Click [Problems List - Add].
- Click outside of the 'Problems List' dialog.
- Validate the dialog is fixed and centered in the screen.
- Click [Cancel].
- Click [Alerts - Add].
- Select "Warning (Custom)" in the 'Type of Alert' field.
- Select "All Episodes" in the 'Episode(s)' field.
- Enter any value with a special character in the 'Custom Message' field.
- Validate an error message and click [OK].
- Enter any value in the 'Custom Message' field.
- Select "No" in the 'Disabled' field.
- Select "Active for Date Range" in the 'Active or Active for Date Range' field.
- Validate the 'Start Date' and 'End Date' field populate with the current date.
- Click [End Date Y].
- Validate an 'Error' dialog stating: "Please choose an end date on or after the start date." and click [OK].
- Validate the 'End Date' field contains the current date.
- Enter any future value in the 'End Date' field.
- Select any form in the 'Applicable Forms' field (Form A).
- Validate the 'Applicable Forms' are listed alphabetically.
- Click [Save].
- Close the 'Client Dashboard'.
- Access 'Form A'.
- Validate the 'Client Alert' message is displayed and contains the message entered in the previous steps.
- Click [OK].
- Close the form.
Avatar NX - 'Alerts' quick action
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Alerts (PM)
- Quick Actions Page
- Update Client Data
Scenario 1: 'Alert Types' - validate data populates in 'Client Alerts' and the 'Alerts' quick action
Specific Setup:
- A client must be enrolled in an existing episode (Client A).
- The 'Alerts' quick action must be set up on a user's view.
- User must select a form to access (Form A).
Steps
- Access the 'Alert Types' form.
- Enter any value in the 'Alert Type ID' field.
- Enter any value in the 'Description' field.
- Enter any value in the 'Message' field.
- Select "Error" in the 'Type of Alert' field.
- Select "Active for Date Range" in the 'Active or Active for Date Range' field.
- Select "No" in the 'Community Alert' field.
- Select "Form A" in the 'Applicable Forms' field.
- Click [Submit].
- Access the 'Client Alerts' form.
- Select "Client A".
- Select the value entered in the previous steps in the 'Type of Alert' field.
- Validate the form populates.
- Validate the 'Start Date' and 'End Date' fields contain the current date.
- Click [End Date Y].
- Validate the 'Error' dialog stating: "Please choose an end date on or after the start date."
- Click [OK].
- Validate the 'End Date' field contains the current date.
- Click [Discard] and [Yes].
- Select "Client A" and navigate to the 'Alerts' quick action.
- Click [Add].
- Select the value entered in the previous steps in the 'Type of Alert' field.
- Validate the form populates.
- Select "All Episodes" in the 'Episode(s)' field.
- Validate the 'Start Date' and 'End Date' fields contain the current date.
- Click [Save] and [Close].
- Access "Form A".
- Validate the 'Client Alert' dialog containing the message entered in the previous steps.
- Click [OK]
- Validate the 'Error' dialog stating: "Canceled!"
- Click [OK]
- Validate the form closes and the user is returned to the myDay view.
Scenario 2: Validate accessing various 'Quick Actions' from the 'Client Dashboard'
Specific Setup:
- A client must be admitted to an active episode (Client A).
- "Client A" must not have data saved in the 'Smoking Assessment' quick action.
- 'Update Client Data', 'Smoking Assessment', 'Problem List', 'Emergency Contact', and 'Alerts' Quick Actions must be assigned to the user in the 'NX View Definition' form.
- This scenario must be tested in an Avatar NX system.
Steps
- Select "Client A" and launch the 'Client Dashboard'.
- Validate there is no grey box behind the client's name.
- Navigate to the 'Quick Actions' widget.
- Click [Update Client Data - Add].
- Click outside of the 'Update Client Data' dialog.
- Validate the dialog is fixed and centered in the screen.
- Enter "LASTNAME, FIRSTNAME" in the 'Name' field and press the "Tab" key.
- Validate the space is automatically removed after the comma.
- Click the 'State' field and validate the states are listed alphabetically.
- Populate the required and desired fields.
- Click [Save].
- Click [Emergency Contact - Add].
- Click outside of the 'Emergency Contact' dialog.
- Validate the dialog is fixed and centered in the screen.
- Enter "LASTNAME, FIRSTNAME" in the 'Emergency Contact Name' field and press the "Tab" key.
- Validate the space is automatically removed after the comma.
- Fill out any required any desired fields.
- Click [Save].
- Click [Smoking Assessment - Add].
- Click outside of the 'Smoking Assessment' dialog.
- Validate the dialog is fixed and centered in the screen.
- Populate the required fields.
- Click [Save].
- Click [Problems List - Add].
- Click outside of the 'Problems List' dialog.
- Validate the dialog is fixed and centered in the screen.
- Click [Cancel].
- Click [Alerts - Add].
- Select "Warning (Custom)" in the 'Type of Alert' field.
- Select "All Episodes" in the 'Episode(s)' field.
- Enter any value with a special character in the 'Custom Message' field.
- Validate an error message and click [OK].
- Enter any value in the 'Custom Message' field.
- Select "No" in the 'Disabled' field.
- Select "Active for Date Range" in the 'Active or Active for Date Range' field.
- Validate the 'Start Date' and 'End Date' field populate with the current date.
- Click [End Date Y].
- Validate an 'Error' dialog stating: "Please choose an end date on or after the start date." and click [OK].
- Validate the 'End Date' field contains the current date.
- Enter any future value in the 'End Date' field.
- Select any form in the 'Applicable Forms' field (Form A).
- Validate the 'Applicable Forms' are listed alphabetically.
- Click [Save].
- Close the 'Client Dashboard'.
- Access 'Form A'.
- Validate the 'Client Alert' message is displayed and contains the message entered in the previous steps.
- Click [OK].
- Close the form.
|
Topics
• Emergency Contact Information
• NX
• Quick Actions
• Client Alerts
|
Avatar PM - Team Caseload Assignment
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Avatar PM - Team Caseload Assignment
Specific Setup:
- The 'RADplus->System Security->Team Definition->->->Update Physician Team Caseload based on Admitting or Attending Practitioner' registry setting must be set to "Y".
- Please log out of the application and log back in after completing the above configuration.
- Three practitioners must exist (Practitioner A) (Practitioner B) (Practitioner C).
- Three users must exist (User A) (User B) (User C).
- "User A" must be associated with "Practitioner A", "User B" must be associated with "Practitioner B", and "User C" must be associated with "Practitioner C".
- Two teams must exist. (Team 1) (Team 2).
- In the "Team Definition" form "Team 1" must have 'Active', 'Physician Team', and 'Disable Adding Clients to Caseload' all set to "Yes".
- In the "Team Definition" form assign "User A" and "User B" to "Team 1".
- In the "Team Definition" form "Team 2" must have 'Active' and 'Physician Team' set to "yes" and 'Disable Adding Clients to Caseload' set to "No".
- In the "Team Definition" form assign "User A" and "User C" to "Team 2".
Steps
- Access the 'Admission' form and admit a new client (Client A).
- Assign "Practitioner A" as "Client A's" admitting practitioner and administering practitioner.
- Access the 'Admission' form and admit a new client (Client B).
- Assign "Practitioner B" as "Client B's" admitting practitioner and administering practitioner.
- Access the 'Admission' form and admit a new client (Client C).
- Assign "Practitioner C" as "Client C's" admitting practitioner and administering practitioner.
- Access the 'Admission' form and admit a new client (Client D).
- Assign "Practitioner B" as "Client D's" admitting practitioner and "Practitioner C" as "Client D's" administering practitioner.
- Log out and then log back in under "User A"
- Validate that the 'Client and Data' widget contains "Client A", "Client C", and "Client D".
- Log out and then log back in under "User B"
- Validate that the 'Client and Data' widget contains "Client B" and "Client D".
- Log out and then log back in under "User C"
- Validate that the 'Client and Data' widget contains "Client A", "Client C", and "Client D".
|
Topics
• NX
• myAvatar/myAvatar NX
|
Registry Setting - Disable Demographics Section On Discharge Form
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Registry Setting - Disable Demographics Section On Discharge Form
Steps
- Access the 'Registry Settings' form.
- Set the 'Limit Registry Settings to the Following Search Criteria' field to "disable demographics" and click [View Registry Settings].
- Validate the 'Registry Setting' field is equal to "Avatar PM->Client Information->Client Demographics->->->Disable Demographics Section On Discharge Form".
- Validate the 'Registry Setting Value' field is equal to "N" and close the form.
- Select any client and access the 'Discharge' form.
- Select the 'Demographics' section.
- Validate fields in the 'Demographics' section are not disabled and close the form.
- Access the 'Registry Settings' form.
- Set the 'Limit Registry Settings to the Following Search Criteria' field to "disable demographics" and click [View Registry Settings].
- Validate the 'Registry Setting' field is equal to "Avatar PM->Client Information->Client Demographics->->->Disable Demographics Section On Discharge Form".
- Set the 'Registry Setting Value' field to "Y" and click [Submit].
- Log out of the application and log back in.
- Select any client and access the 'Discharge' form.
- Select the 'Demographics' section.
- Validate all fields are disabled.
|
Topics
• Registry Settings
• NX
|
Print Bill - UB-04
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Print Bill - Form = UB-04
Specific Setup:
- Client:
- Client is enrolled in an inpatient program, has an active diagnosis record and a financial eligibility record. Note the guarantor.
- Client has unclaimed, closed services with the fee distributed to the guarantor. Note the episode and dates of service.
Steps
- Open ‘Print Bill’.
- Enter desired date in ‘Print Charge Thru’.
- Select desired value in ‘Create Claims’. If yes is selected, enter a value in ‘Date of Claim’ and verify that the claim number exists in the ‘Client Ledger’ beginning in step # 15.
- Select ‘UB-04’ in ‘Print For What Form’.
- Select ‘No’ in ‘Print For Interim Batch’.
- Select desired value in ‘Guarantor’.
- Select ‘Individual’ in ‘Print For An Individual or All Clients’.
- Enter the desired ‘Client ID’.
- Select desired value in ‘Print All Episodes’. If ‘No’ is selected, select the ‘Episode Number’.
- Select desired value in ‘Print Summary By Revenue Code’ If ‘Yes’ is selected, select desired value in ‘Summary By Revenue Code or Revenue Code And Charge’.
- Click [Process].
- Review the report for accuracy.
- Close the report.
- Close the form.
- Open ’Client Ledger’ for the client.
- Select ‘All Episodes’ in ‘Claim/Episode/All Episodes’/
- Select ‘Simple’ in ‘Ledger Type’.
- Enter desired values in ‘From Date’ and ‘To Date’.
- Click [Process].
- Review the report to validate that the services contain a value in ‘CLAIM NUMBER.
- Close the report.
- Close the form.
|
Topics
• Print Bill
• NX
|
Program Maintenance - 'EVV Provider Organization ID' field
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- File Import
- Program Maintenance
- SoapUI - ProgramMaintenance - AddProgramMaintenance
- SoapUI - ProgramMaintenance
Scenario 1: 'File Import' - Verification of 'Program Maintenance' Import
Specific Setup:
- Have a valid 'Program Maintenance' import file (File A) created that contains a data row for a program with the following:
- A value populated in the 'EVV Provider Organization ID' field
- Value(s) in the 'Associated Service Programs' field
- The 'Enable Mobile CareGiver+' field must be set to "Yes" in the 'Electronic Visit Verification' section of the 'CarePOV Management' form.
Steps
- Access the 'File Import' form.
- Select "Program Maintenance" in the 'File Type' field.
- Select "Upload New File" in the 'Action' field.
- Click [Process Action].
- Navigate to the location of "File A" and click [Open].
- Select "Compile/Validate File" in the 'Action' field.
- Select "File A" in the 'File(s)' field.
- Click [Process Action].
- Validate a message is displayed stating "Compiled" and click [OK].
- Select "Print File" in the 'Action' field.
- Select "File A" in the 'File(s)' field.
- Click [Process Action].
- Validate a report is displayed for the program data in "File A".
- Close the report.
- Select "Post File" in the 'Action' field.
- Select "File A" in the 'File(s)' field.
- Click [Process Action].
- Validate a message is displayed stating "Posted" and click [OK].
- Close the form.
- Access the 'Program Maintenance' form.
- Select "Edit" in the 'Add Or Edit Program' field.
- Select the program imported via 'File Import' in the 'Program' field.
- Validate all imported data is populated as expected.
- Validate the 'Associated Service Programs' field contains the programs imported in the previous steps.
- Validate the 'EVV Provider Organization ID' field contains the value imported in the previous steps.
- Close the form.
Scenario 2: 'WEBSVC.ProgramMaintenance' - add a program
Specific Setup:
- The 'Enable Mobile CareGiver+' field must be set to "Yes" in the 'Electronic Visit Verification' section of the 'CarePOV Management' form.
Steps
- Access SoapUI for the 'ProgramMaintenance' - 'AddProgramMaintenance' web service.
- Enter the system code that will be used to log into Avatar in the 'SystemCode' field.
- Enter the user name that will be used to log into Avatar in the 'UserName' field.
- Enter the password that will be used to log into Avatar in the 'Password' field.
- Enter "Y" in the 'Active' field.
- Enter the desired value in the 'Description' field.
- Enter the desired value in the 'Location' field.
- Enter the desired value in the 'Program' field.
- Enter the desired value in the 'ProgramCode' field.
- Enter the desired value in the 'ProgramType' field.
- Enter the desired value in the 'RRG' field.
- Enter the desired value in the 'ReqAdmitPract' field.
- Enter the desired value in the 'TreatmentService' field.
- Enter the desired value in the 'TreatmentSetting' field.
- Enter the desired value in the 'UsageType' field.
- Enter the desired value in the 'EVVProviderOrgID' field.
- Populate any other desired fields.
- Click [Run].
- Validate the response contains: Program Maintenance web service has been filed successfully.
- Access the 'Program Maintenance' form.
- Select "Edit" in the 'Add Or Edit Program' field.
- Select the program added in the previous steps in the 'Program' field.
- Validate all previously filed data is displayed.
- Validate the 'EVV Provider Organization ID' field contains the value filed in the previous steps.
- Close the form.
Scenario 3: Single Program Maintenance - Add/Edit Program
Specific Setup:
- The 'Enable Single Program Maintenance' registry setting must be enabled.
- The 'Enable Mobile CareGiver+' field must be set to "Yes" in the 'Electronic Visit Verification' section of the 'CarePOV Management' form.
Steps
- Access the 'Single Program Maintenance' form.
- Search for any new value and click [New Program].
- Enter the desired value in the 'Description' field.
- Populate all other required and desired fields.
- Validate the 'EVV Provider Organization ID' field is displayed.
- Enter the desired value in the 'EVV Provider Organization ID' field.
- Click [Submit].
- Access the 'Single Program Maintenance' form.
- Search for and select the program added in the previous steps.
- Validate all previously filed data is displayed.
- Validate the 'EVV Provider Organization ID' field contains the value entered in the previous steps.
- Update any desired fields.
- Click [Submit].
Scenario 4: Program Maintenance - Add/Edit program
Specific Setup:
- The 'Enable Mobile CareGiver+' field must be set to "Yes" in the 'Electronic Visit Verification' section of the 'CarePOV Management' form.
Steps
- Access the 'Program Maintenance' form.
- Select "Add" in the 'Add Or Edit Program' field.
- Enter the desired value in the 'Program Code' field.
- Enter the desired value in the 'Description' field.
- Populate all other required and desired fields.
- Validate the 'EVV Provider Organization ID' field is displayed.
- Enter the desired value in the 'EVV Provider Organization ID' field.
- Click [File Program].
- Select "Edit" in the 'Add Or Edit Program' field.
- Select the program added in the previous steps in the 'Program' field.
- Validate all previously filed data is displayed.
- Validate the 'EVV Provider Organization ID' field contains the value entered in the previous steps.
- Update any desired fields.
- Click [File Program] and close the form.
'File Import' - Program Maintenance
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- File Import
- Program Maintenance
Scenario 1: 'File Import' - Verification of 'Program Maintenance' Import
Specific Setup:
- Have a valid 'Program Maintenance' import file (File A) created that contains a data row for a program with the following:
- A value populated in the 'EVV Provider Organization ID' field
- Value(s) in the 'Associated Service Programs' field
- The 'Enable Mobile CareGiver+' field must be set to "Yes" in the 'Electronic Visit Verification' section of the 'CarePOV Management' form.
Steps
- Access the 'File Import' form.
- Select "Program Maintenance" in the 'File Type' field.
- Select "Upload New File" in the 'Action' field.
- Click [Process Action].
- Navigate to the location of "File A" and click [Open].
- Select "Compile/Validate File" in the 'Action' field.
- Select "File A" in the 'File(s)' field.
- Click [Process Action].
- Validate a message is displayed stating "Compiled" and click [OK].
- Select "Print File" in the 'Action' field.
- Select "File A" in the 'File(s)' field.
- Click [Process Action].
- Validate a report is displayed for the program data in "File A".
- Close the report.
- Select "Post File" in the 'Action' field.
- Select "File A" in the 'File(s)' field.
- Click [Process Action].
- Validate a message is displayed stating "Posted" and click [OK].
- Close the form.
- Access the 'Program Maintenance' form.
- Select "Edit" in the 'Add Or Edit Program' field.
- Select the program imported via 'File Import' in the 'Program' field.
- Validate all imported data is populated as expected.
- Validate the 'Associated Service Programs' field contains the programs imported in the previous steps.
- Validate the 'EVV Provider Organization ID' field contains the value imported in the previous steps.
- Close the form.
Scenario 2: Program Maintenance - Add/Edit program
Specific Setup:
- The 'Enable Mobile CareGiver+' field must be set to "Yes" in the 'Electronic Visit Verification' section of the 'CarePOV Management' form.
Steps
- Access the 'Program Maintenance' form.
- Select "Add" in the 'Add Or Edit Program' field.
- Enter the desired value in the 'Program Code' field.
- Enter the desired value in the 'Description' field.
- Populate all other required and desired fields.
- Validate the 'EVV Provider Organization ID' field is displayed.
- Enter the desired value in the 'EVV Provider Organization ID' field.
- Click [File Program].
- Select "Edit" in the 'Add Or Edit Program' field.
- Select the program added in the previous steps in the 'Program' field.
- Validate all previously filed data is displayed.
- Validate the 'EVV Provider Organization ID' field contains the value entered in the previous steps.
- Update any desired fields.
- Click [File Program] and close the form.
Single Program Maintenance - Add new program
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Single Program Maintenance - Add/Edit Program
Specific Setup:
- The 'Enable Single Program Maintenance' registry setting must be enabled.
- The 'Enable Mobile CareGiver+' field must be set to "Yes" in the 'Electronic Visit Verification' section of the 'CarePOV Management' form.
Steps
- Access the 'Single Program Maintenance' form.
- Search for any new value and click [New Program].
- Enter the desired value in the 'Description' field.
- Populate all other required and desired fields.
- Validate the 'EVV Provider Organization ID' field is displayed.
- Enter the desired value in the 'EVV Provider Organization ID' field.
- Click [Submit].
- Access the 'Single Program Maintenance' form.
- Search for and select the program added in the previous steps.
- Validate all previously filed data is displayed.
- Validate the 'EVV Provider Organization ID' field contains the value entered in the previous steps.
- Update any desired fields.
- Click [Submit].
Scenario 2: Program Maintenance - Add/Edit program
Specific Setup:
- The 'Enable Mobile CareGiver+' field must be set to "Yes" in the 'Electronic Visit Verification' section of the 'CarePOV Management' form.
Steps
- Access the 'Program Maintenance' form.
- Select "Add" in the 'Add Or Edit Program' field.
- Enter the desired value in the 'Program Code' field.
- Enter the desired value in the 'Description' field.
- Populate all other required and desired fields.
- Validate the 'EVV Provider Organization ID' field is displayed.
- Enter the desired value in the 'EVV Provider Organization ID' field.
- Click [File Program].
- Select "Edit" in the 'Add Or Edit Program' field.
- Select the program added in the previous steps in the 'Program' field.
- Validate all previously filed data is displayed.
- Validate the 'EVV Provider Organization ID' field contains the value entered in the previous steps.
- Update any desired fields.
- Click [File Program] and close the form.
|
Topics
• Program Maintenance
• File Import
• Web Services
• NX
|
Allow For Number of Days Since Last Claim - Option added to Inhibit services
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Service Codes
- Default Guarantor Assignment
- Guarantors/Payors
- Dynamic form- Social Security Number
- Admission (Outpatient)
- Client Charge Input
- Client Ledger
- Crystal Self Pay Bill
- No Information Found
- Inhibited Services For Billing Report
- Individual Cash Posting (PM)
- Dynamic Form - Individual Cash Posting - Information
- Dynamic Form - Individual Cash Posting - Alert
- Dynamic Form - Individual Cash Posting - Client
- Inhibit Billing By Service
- Dynamic Form - Un-Inhibit services - Please review your selections to Un-Inhibit service
- Dynamic Form - File Service Inhibit Information
- Progressive Self Pay Dunning Messages
- Update Client Data
- SQL Query/Reporting
- Admission
- Dynamic Form - Edit Service Fee Definition
Scenario 1: Crystal Self Pay Bill - Previous claim date within the 'Number Of Days Since Last Claim' - Registry Setting 'Allow For Number of Days Since Last Claim' = I
Specific Setup:
- Registry Settings:
- Set the 'Allow For Number Of Days Since Last Claim' set to 'I'.
- Guarantors/Payor:
- The self pay guarantor is identified. Note the guarantor code/value.
- Enter desired days in the 'Number Of Days Since Last Claim' field. Note the number of days.
- Admission:
- A new client is admitted. Note the client id, admission date and admission program.
- Financial Eligibility:
- A self pay guarantor is assigned to the client. Note the guarantor code.
- Diagnosis:
- The diagnosis record is created for the client.
- Client Charge Input:
- The service is rendered to the client. Note the service date and service code.
- Client Ledger:
- The service distributed to the self pay guarantor.
Steps
- Open the 'Crystal Self Pay Bill' form.
- Enter/select values for 'Print Charges Thru' field such that it covers the service rendered to the client. Note the date.
- Select 'Yes' in the 'Create Claims Y/N' field.
- Enter desired date to the 'Date Of Claim' field such that it is after the service date. Note the claim date for further testing.
- Select 'No' in the 'Print for Interim Batch' field. Please note the 'Number Of Days Since Last Claim' functionality does not support batch.
- Select 'All Clients' in the 'Print For An Individual Or All Clients'.
- Click [Compile Self Pay Bill].
- Verify the 'Compile Complete' message displayed.
- Navigate to the 'Print Crystal Self Pay Bill' section of the form.
- Select value for 'Select By Client Or File' field.
- Select compiled bill file or client record for bill data display.
- Click [Print Self Pay Bill].
- Ensure that it displays the Self Pay Bill report/information.
- In the Self Pay Bill report/information display, ensure that the 'Current Charges' section includes claim/service information for all services meeting bill generation criteria selection, with service date/description/amount values, as well as charge total information.
- Open the 'Client Charge Input' form.
- Render a service to the client. Note the date of the service.
- Verify the service distributed correctly to the self pay guarantor assigned to the client.
- Close charges.
- Open the 'Crystal Self Pay Bill' form.
- Enter/select values for 'Print Charges Thru' field such that it covers the service rendered to the client and it is within the number of days since last claim defined in the 'Guarantors/Payor' from the claim date. Note the date.
- Select 'Yes' in the 'Create Claims Y/N' field.
- Enter desired date to the 'Date Of Claim' field such that it is after the previous claim date.
- Select 'No' in the 'Print for Interim Batch' field. Please note the 'Number Of Days Since Last Claim' functionality does not support batch.
- Select 'All Clients' in the 'Print For An Individual Or All Clients'.
- Click [Compile Self Pay Bill].
- Verify the 'No Information Found. Cancel OK No Information Was Found For Inclusion On The Bill.' message displayed.
- Click [Close Report].
- Click [Discard].
- Open the 'Inhibited Services For Billing Report' form.
- Enter 'Start Date'.
- Enter 'End Date'.
- Select the client from the previous steps.
- Click [Process report].
- Verify the report contains all the services for the client for the episode inhibited from the billing.
- Close the report.
- Open the 'Crystal Self Pay Bill' form.
- Enter/select values for 'Print Charges Thru' field such that it covers the service rendered to the client and it is after the number of days defined in the 'Number Of Days Since Last Claim' field in the 'Guarantors/Payors. Note the date.
- Select 'Yes' in the 'Create Claims Y/N' field.
- Enter desired date to the 'Date Of Claim' field such that it is after the service date. Note the claim date for further testing.
- Select 'No' in the 'Print for Interim Batch' field. Please note the 'Number Of Days Since Last Claim' functionality does not support batch.
- Select 'All Clients' in the 'Print For An Individual Or All Clients'.
- Click [Compile Self Pay Bill].
- Verify the 'Compile Complete' message displayed.
- Navigate to the 'Print Crystal Self Pay Bill' section of the form.
- Select value for 'Select By Client Or File' field.
- Select compiled bill file or client record for bill data display.
- Click [Print Self Pay Bill].
- Ensure that it displays the Self Pay Bill report/information.
- Verify the report displays the recently claimed service in the report.
- Close the report.
- Close the form.
Scenario 2: Crystal Self Pay Bill - Previous claim date within the 'Number Of Days Since Last Claim' - Make payments so that the self pay balance for that client/episode is zero
Specific Setup:
- Registry Settings:
- Set the 'Allow For Number Of Days Since Last Claim' set to 'I'.
- Guarantors/Payor:
- The self pay guarantor is identified. Note the guarantor code/value.
- Enter desired days in the 'Number Of Days Since Last Claim' field. Note the number of days.
- Admission:
- A new client is admitted. Note the client id, admission date and admission program.
- Financial Eligibility:
- A self pay guarantor is assigned to the client. Note the guarantor code.
- Diagnosis:
- The diagnosis record is created for the client.
- Client Charge Input:
- The service is rendered to the client. Note the service date and service code.
- Client Ledger:
- The service distributed to the self pay guarantor.
Steps
- Open the 'Crystal Self Pay Bill' form.
- Enter/select values for 'Print Charges Thru' field such that it covers the service rendered to the client. Note the date.
- Select 'Yes' in the 'Create Claims Y/N' field.
- Enter desired date to the 'Date Of Claim' field such that it is after the service date. Note the claim date for further testing.
- Select 'No' in the 'Print for Interim Batch' field. Please note the 'Number Of Days Since Last Claim' functionality does not support batch.
- Select the self pay guarantor assigned to the client.
- Select 'All Clients' in the 'Print For An Individual Or All Clients'.
- Click [Compile Self Pay Bill].
- Verify the 'Compile Complete' message displayed.
- Navigate to the 'Print Crystal Self Pay Bill' section of the form.
- Select value for 'Select By Client Or File' field.
- Select compiled bill file or client record for bill data display.
- Click [Print Self Pay Bill].
- Ensure that it displays the Self Pay Bill report/information.
- In the Self Pay Bill report/information display, ensure that the 'Current Charges' section includes claim/service information for all services meeting bill generation criteria selection, with service date/description/amount values, as well as charge total information.
- Open the 'Client Charge Input' form.
- Render a service to the client. Note the date of the service.
- Verify the service distributed correctly to the self pay guarantor assigned to the client.
- Close charges.
- Open the 'Crystal Self Pay Bill' form.
- Enter/select values for 'Print Charges Thru' field such that it covers the service rendered to the client and it is within the number of days since last claim defined in the 'Guarantors/Payor' from the claim date. Note the date.
- Select 'Yes' in the 'Create Claims Y/N' field.
- Enter desired date to the 'Date Of Claim' field such that it is after the previous claim date.
- Select 'No' in the 'Print for Interim Batch' field. Please note the 'Number Of Days Since Last Claim' functionality does not support batch.
- Select 'All Clients' in the 'Print For An Individual Or All Clients'.
- Click [Compile Self Pay Bill].
- Verify the 'No Information Found. Cancel OK No Information Was Found For Inclusion On The Bill.' message displayed.
- Click [Close Report].
- Click [Discard].
- Open the 'Inhibited Services For Billing Report' form.
- Enter 'Start Date'.
- Enter 'End Date'.
- Select the client from the previous steps.
- Click [Process report].
- Verify the report contains all the services for the client for that episode inhibited from the billing.
- Close the report.
- Open the 'Individual Cash Posting' form.
- Enter the 'Client' identified in the setup section.
- Select desired value in 'Post By'.
- Review 'Start Date' and 'Stop Date'. Change the values if desired.
- Click [Select Item(s) to Post Against].
- Highlight the first two services.
- Click [OK]. Note the 'balance due'.
- Click [OK].
- Enter the 'Posting Date'.
- Enter the 'Date of Receipt'.
- Enter the 'balance due' in 'Dollar Amount To Be Posted'.
- Enter the 'Posting Code'.
- Click [Update Temporary File]'.
- Click [OK].
- Click [Submit].
- Click [Yes].
- Click [No].
- Open 'Client Ledger'.
- Enter the 'Client ID'.
- Select 'All Episodes' in 'Claim/Episode/All Episodes'.
- Select 'Simple' in 'Ledger Type'.
- Set the 'From Date' to the first date of service.
- Set the 'To Date' to the last date of service.
- Click [Process].
- Services one and two have been paid in full. The 'LINE BALANCE' is '0.00'.
- The balance for the 'Self Pay' guarantor is 0.00.
- Open the 'Crystal Self Pay Bill' form.
- Enter/select values for 'Print Charges Thru' field such that it covers the service rendered to the client and it is within the number of days defined in the 'Number Of Days Since Last Claim' field in the 'Guarantors/Payors. Note the date.
- Select 'Yes' in the 'Create Claims Y/N' field.
- Enter desired date to the 'Date Of Claim' field such that it is after the service date. Note the claim date for further testing.
- Select 'No' in the 'Print for Interim Batch' field. Please note the 'Number Of Days Since Last Claim' functionality does not support batch.
- Select 'All Clients' in the 'Print For An Individual Or All Clients'.
- Click [Compile Self Pay Bill].
- Verify the 'Compile Complete' message displayed.
- Navigate to the 'Print Crystal Self Pay Bill' section of the form.
- Select value for 'Select By Client Or File' field.
- Select compiled bill file or client record for bill data display.
- Click [Print Self Pay Bill].
- Ensure that it displays the Self Pay Bill report/information.
- Verify the report displays the recently claimed service in the report.
- Close the report.
- Close the form.
Scenario 3: Compile Self Pay bill - Previous claim date does not fall within the 'Number Of Days Since Last Claim' - Validating registry setting 'Allow For Number of Days Since Last Claim'
Specific Setup:
- Registry Settings:
- Set the 'Allow For Number Of Days Since Last Claim' set to 'I'.
- Guarantors/Payor:
- The self pay guarantor is identified. Note the guarantor code/value.
- Enter desired days in the 'Number Of Days Since Last Claim' field. Note the number of days.
- Admission:
- A new client is admitted. Note the client id, admission date and admission program.
- Financial Eligibility:
- A self pay guarantor is assigned to the client. Note the guarantor code.
- Diagnosis:
- The diagnosis record is created for the client.
- Client Charge Input:
- The service is rendered to the client. Note the service date and service code.
- Client Ledger:
- The service distributed to the self pay guarantor.
- Close Charges:
- Services rendered to the client are closed.
Steps
Scenario 4: Progressive Self Pay Dunning Messages - Form validation - Validating registry setting 'Enable Progressive Self-Pay Dunning Messages'
Specific Setup:
- Registry Settings:
- The registry setting 'Enable Progressive Self-Pay Dunning Messages' is added.
- The registry setting 'Enable Progressive Self-Pay Dunning Messages' is set to 'Y'.
- The registry setting 'Allow For Number Of Days Since Last Claim' set to 'I'.
- User Definition:
- Verify the form 'Progressive Self Pay Dunning Messages' is added to the system.
- Select the form and submit the user definition.
- Form Search:
- Verify the form 'Progressive Self Pay Dunning Messages' is available in the system.
- Guarantors/Payor:
- The self pay guarantor is identified. Note the guarantor code/value.
- Enter desired days in the 'Number Of Days Since Last Claim' field. Note the number of days.
- Admission:
- A new client is admitted. Note the client id, admission date and admission program.
- Financial Eligibility:
- A self pay guarantor is assigned to the client. Note the guarantor code.
- Diagnosis:
- The diagnosis record is created for the client.
- Client Charge Input:
- 6-7 services are rendered to the client. Note the service date and service code.
- Client Ledger:
- The services distributed to the self pay guarantor.
- Close Charges:
- Services are closed.
Steps
- Open the 'Progressive Self Pay Dunning Messages' form.
- Select the guarantor.
- Verify the first message field is enabled.
- Verify that each subsequent message field enables when the prior field has a value.
- File data for multiple guarantors.
- Print the information for the selected guarantor.
- Verify the report displays data for all the guarantors.
- Select a desired guarantor.
- Click [Print Only the selected guarantor].
- Verify the report includes data filed for the selected guarantor.Open the 'Crystal Report' or any other SQL Data Viewer.
- Query the SQL table SYSTEM.billing_prog_sp_dunn_msg.
- Verify the data files successfully and correctly as entered through the form.
- Select a desired guarantor.
- Click [Delete].
- Verify the data filed for the guarantor deleted.
- Open the 'Crystal Self Pay Bill' form.
- Enter/select values for 'Print Charges Thru' field such that it covers the service rendered to the client. Note the date.
- Select 'Yes' in the 'Create Claims Y/N' field.
- Enter desired date to the 'Date Of Claim' field such that it is after the service date. Note the claim date for further testing.
- Select 'No' in the 'Print for Interim Batch' field. Please note the 'Number Of Days Since Last Claim' functionality does not support batch.
- Select 'All Clients' in the 'Print For An Individual Or All Clients'.
- Click [Compile Self Pay Bill].
- Verify the 'Compile Complete' message displayed.
- Navigate to the 'Print Crystal Self Pay Bill' section of the form.
- Select value for 'Select By Client Or File' field.
- Select compiled bill file or client record for bill data display.
- Click [Print Self Pay Bill].
- Ensure that it displays the first message defined in the form in the Self Pay Bill report/information.
- Run the bill for the second service.
- Ensure that it displays the second message defined in the form in the Self Pay Bill report/information.
- Run the bill for the second service.
- Ensure that it displays the third message defined in the form in the Self Pay Bill report/information.
- Run the bill for the second service.
- Ensure that it displays the fourth message defined in the form in the Self Pay Bill report/information.
- Run the bill for the second service.
- Ensure that it displays the fifth message defined in the form in the Self Pay Bill report/information.
- Close the report.
- Close the form.
Scenario 5: Crystal Self Pay Bill - Previous claim date within the 'Number Of Days Since Last Claim' - Validating new billing cycle - Updating client's address using the 'Update Client Data' form - Inpatient client - Multiple guarantors
Specific Setup:
- Registry Settings:
- Set the 'Allow For Number Of Days Since Last Claim' set to 'I'.
- Guarantors/Payor:
- The self pay guarantor is identified to be assigned to the client as a secondary guarantor. Note the guarantor code/value.
- Enter desired days in the 'Number Of Days Since Last Claim' field. Note the number of days.
- Any other existing guarantor is identified to be assigned to the client as a primary guarantor. Note the guarantor code/value.
- Admission:
- A new client is admitted. Note the client id, admission date and admission program.
- Financial Eligibility:
- The guarantor identified above is assigned to the client as a primary guarantor.
- A self pay guarantor is assigned to the client as a secondary guarantor. Note the guarantor code.
- The 'Coverage Effective Date' of the primary guarantor is set to the date that comes after the 'Service Date' and the primary guarantor does not cover the services rendered to the client and they distributed to the next guarantor.
- Diagnosis:
- The diagnosis record is created for the client.
- Client Charge Input:
- The service is rendered to the client such that it comes prior to coverage effective date of the primary guarantor. Note the service date and service code.
- Client Ledger:
- The service distributed to the self pay guarantor.
- Close Charges:
- The services rendered to the client are closed.
Steps
- Open the 'Crystal Self Pay Bill' form.
- Enter/select values for 'Print Charges Thru' field such that it covers the service rendered to the client. Note the date.
- Select 'Yes' in the 'Create Claims Y/N' field.
- Enter desired date to the 'Date Of Claim' field such that it is after the service date. Note the claim date for further testing.
- Select 'No' in the 'Print for Interim Batch' field. Please note the 'Number Of Days Since Last Claim' functionality does not support batch.
- Select 'All Clients' in the 'Print For An Individual Or All Clients'.
- Click [Compile Self Pay Bill].
- Verify the 'Compile Complete' message displayed.
- Navigate to the 'Print Crystal Self Pay Bill' section of the form.
- Select value for 'Select By Client Or File' field.
- Select compiled bill file or client record for bill data display.
- Click [Print Self Pay Bill].
- Ensure that it displays the Self Pay Bill report/information.
- In the Self Pay Bill report/information display, ensure that the 'Current Charges' section includes claim/service information for all services meeting bill generation criteria selection, with service date/description/amount values, as well as charge total information.
- Open the 'Client Charge Input' form.
- Render a service to the client. Note the date of the service.
- Verify the service distributed correctly to the self pay guarantor assigned to the client.
- Close charges.
- Open the 'Crystal Self Pay Bill' form.
- Enter/select values for 'Print Charges Thru' field such that it covers the service rendered to the client and it is within the number of days since last claim defined in the 'Guarantors/Payor' from the claim date. Note the date.
- Select 'Yes' in the 'Create Claims Y/N' field.
- Enter desired date to the 'Date Of Claim' field such that it is after the previous claim date.
- Select 'No' in the 'Print for Interim Batch' field. Please note the 'Number Of Days Since Last Claim' functionality does not support batch.
- Select 'All Clients' in the 'Print For An Individual Or All Clients'.
- Click [Compile Self Pay Bill].
- Verify the 'No Information Was Found For Inclusion On The Bill.' message displayed.
- Click [Close Report].
- Click [Discard].
- Open the 'Inhibited Services For Billing Report' form.
- Enter 'Start Date'.
- Enter 'End Date'.
- Select the client from the previous steps.
- Click [Process report].
- Verify the report contains all the services for the client for the episode inhibited from the billing.
- Close the report.
- Open the 'Update Client Data' form for the client.
- Navigate to 'Demographics' section of form.
- Change any of the Client's Address field.
- Click [Submit].
- Open the 'Crystal Self Pay Bill' form.
- Enter/select values for 'Print Charges Thru' field such that it covers the service rendered to the client and it is within the number of days defined in the 'Number Of Days Since Last Claim' field in the 'Guarantors/Payors. Note the date.
- Select 'Yes' in the 'Create Claims Y/N' field.
- Enter desired date to the 'Date Of Claim' field such that it is after the service date. Note the claim date for further testing.
- Select 'No' in the 'Print for Interim Batch' field. Please note the 'Number Of Days Since Last Claim' functionality does not support batch.
- Select 'All Clients' in the 'Print For An Individual Or All Clients'.
- Click [Compile Self Pay Bill].
- Verify the 'Compile Complete' message displayed.
- Navigate to the 'Print Crystal Self Pay Bill' section of the form.
- Select value for 'Select By Client Or File' field.
- Select compiled bill file or client record for bill data display.
- Click [Print Self Pay Bill].
- Ensure that it displays the Self Pay Bill report/information.
- Verify the report displays the recently claimed service in the report.
- Close the report.
- Close the form.
Scenario 6: Crystal Self Pay Bill - Previous claim date within the 'Number Of Days Since Last Claim' - Validating services that are transferred to the Self-Pay guarantor
Specific Setup:
- Registry Settings:
- Set the 'Allow For Number Of Days Since Last Claim' set to 'I'.
- Guarantors/Payor:
- The self pay guarantor is identified to be assigned to the client as a secondary guarantor. Note the guarantor code/value.
- Enter desired days in the 'Number Of Days Since Last Claim' field. Note the number of days.
- Any other existing guarantor is identified to be assigned to the client as a primary guarantor. Note the guarantor code/value.
- Admission:
- A new client is admitted. Note the client id, admission date and admission program.
- Financial Eligibility:
- A self pay guarantor is assigned to the client as a secondary guarantor. Note the guarantor code.
- The other guarantor identified above is assigned to the client as a primary guarantor.
- Diagnosis:
- The diagnosis record is created for the client.
- Client Charge Input:
- The service is rendered to the client. Note the service date and service code.
- Client Ledger:
- The service distributed to the primary guarantor.
Steps
- Open the 'Crystal Self Pay Bill' form.
- Enter/select values for 'Print Charges Thru' field such that it covers the service rendered to the client. Note the date.
- Select 'Yes' in the 'Create Claims Y/N' field.
- Enter desired date to the 'Date Of Claim' field such that it is after the service date. Note the claim date for further testing.
- Select 'No' in the 'Print for Interim Batch' field. Please note the 'Number Of Days Since Last Claim' functionality does not support batch.
- Select 'All Clients' in the 'Print For An Individual Or All Clients'.
- Click [Compile Self Pay Bill].
- Verify the 'Compile Complete' message displayed.
- Navigate to the 'Print Crystal Self Pay Bill' section of the form.
- Select value for 'Select By Client Or File' field.
- Select compiled bill file or client record for bill data display.
- Click [Print Self Pay Bill].
- Ensure that it displays the Self Pay Bill report/information.
- In the Self Pay Bill report/information display, ensure that the 'Current Charges' section includes claim/service information for all services meeting bill generation criteria selection, with service date/description/amount values, as well as charge total information.
- Open the 'Client Charge Input' form.
- Render a service to the client. Note the date of the service.
- Verify the service distributed correctly to the self pay guarantor assigned to the client.
- Close charges.
- Open the 'Crystal Self Pay Bill' form.
- Enter/select values for 'Print Charges Thru' field such that it covers the service rendered to the client and it is within the number of days since last claim defined in the 'Guarantors/Payor' from the claim date. Note the date.
- Select 'Yes' in the 'Create Claims Y/N' field.
- Enter desired date to the 'Date Of Claim' field such that it is after the previous claim date.
- Select 'No' in the 'Print for Interim Batch' field. Please note the 'Number Of Days Since Last Claim' functionality does not support batch.
- Select 'All Clients' in the 'Print For An Individual Or All Clients'.
- Click [Compile Self Pay Bill].
- Verify the 'No Information Was Found For Inclusion On The Bill.' message displayed.
- Click [Close Report].
- Click [Discard].
- Open the 'Inhibited Services For Billing Report' form.
- Enter 'Start Date'.
- Enter 'End Date'.
- Select the client from the previous steps.
- Click [Process report].
- Verify the report contains all the services for the client for the episode inhibited from the billing.
- Close the report.
- Open the 'Update Client Data' form for the client.
- Navigate to 'Demographics' section of form.
- Change client's address field.
- Click [Submit].
- Open the 'Crystal Self Pay Bill' form.
- Enter/select values for 'Print Charges Thru' field such that it covers the service rendered to the client and it is within the number of days defined in the 'Number Of Days Since Last Claim' field in the 'Guarantors/Payors. Note the date.
- Select 'Yes' in the 'Create Claims Y/N' field.
- Enter desired date to the 'Date Of Claim' field such that it is after the service date. Note the claim date for further testing.
- Select 'No' in the 'Print for Interim Batch' field. Please note the 'Number Of Days Since Last Claim' functionality does not support batch.
- Select 'All Clients' in the 'Print For An Individual Or All Clients'.
- Click [Compile Self Pay Bill].
- Verify the 'Compile Complete' message displayed.
- Navigate to the 'Print Crystal Self Pay Bill' section of the form.
- Select value for 'Select By Client Or File' field.
- Select compiled bill file or client record for bill data display.
- Click [Print Self Pay Bill].
- Ensure that it displays the Self Pay Bill report/information.
- Verify the report displays the recently claimed service in the report.
- Close the report.
- Close the form.
|
Topics
• Registry Settings
• Inhibit Billing
• NX
• 837 Professional
• Crystal Self Pay Bill
|
Avatar PM 'Aged Accounts Report'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: 'Aged Accounts Report' - Verification of .CSV format report results
Steps
- Open Avatar PM 'Aged Accounts Report' form (under 'Avatar PM / Billing / Billing Reports / Monthly Closeout Reports' menu).
- Enter/select values for 'Effective Date', 'Date of Payments', 'Age From Date' and all other required/desired report criteria fields.
- Select 'Detail Report' in 'Summary Or Detail Report' field.
- Ensure 'Export Detail Information to CSV' field is present in form, with 'Yes' checkbox/selection available.
- The 'Export Detail Information to CSV' field is only enabled/available for selection when 'Detail Report' is selected (in 'Summary Or Detail Report' field)
- No selection in the 'Export Detail Information to CSV' field will render report results in the default report format
- Selecting 'Yes' in the 'Export Detail Information to CSV' field will display report results in .CSV (comma-separated value) format (allowing user to export/save 'Aged Accounts Report' Detail Report results for external use)
- Click 'Process' button to run report/render result data.
- If no value is selected in 'Export Detail Information to CSV' field, ensure that 'Aged Accounts Report' results ('Summary Report' and/or 'Detail Report') are rendered/displayed in the default report format.
- If 'Yes' is selected for 'Export Detail Information to CSV' field, ensure that 'Aged Accounts Report' Detail Report results are rendered/displayed in .CSV format within myAvatar/Avatar NX, with following header and columns/fields present:
- 'Aged Accounts Report' Detail Report .CSV format data header (first row in report data results) will contain the following data elements:
- 'Sort By' (if 'Additional Sort' = 'Yes', otherwise '(0 = No Sort)')
- 'Client ID #'
- 'Client Last Name'
- 'Client First Name'
- 'Episodes'
- 'Guarantor ID #'
- Guarantor Name'
- 'Guarantor Balance'
- Aging Categories (default or custom entered/edited values as defined in 'Aging Category' report criteria field; 'Aging 30', 'Aging 60', 'Aging 180', 'Aging 365', etc.)
- Header row examples:
- "Sort By (0 = No Sort),Client ID #,Client Last Name,Client First Name,Episodes,Guarantor ID #,Guarantor Name,Guarantor Balance,Aging 0,Aging 30,Aging 60,Aging 90,Aging 120"
- "Sort By (22 = Date Of Birth),Client ID #,Client Last Name,Client First Name,Episodes,Guarantor ID #,Guarantor Name,Guarantor Balance,Aging 10,Aging 45,Aging 90,Aging 110,Aging 300,Aging 365,Aging 720"
- "Sort By (94 = Client's Address - Zipcode),Client ID #,Client Last Name,Client First Name,Episodes,Guarantor ID #,Guarantor Name,Guarantor Balance,Aging 0,Aging 30,Aging 60,Aging 90,Aging 120"
- 'Aged Accounts Report' Detail Report .CSV format individual data rows (second and all subsequent rows in report data results) will contain report data for each element, one row per result.
- Data row examples:
- "0,485,AGED,ONE,1,4,Medicaid,410,110,100,0,10,0"
- "0,486,AGED,TWO,1,1,BCBS,40,10,10,0,0,20"
- "01/01/1972,485,AGED,ONE,1,4,Medicaid,410,210,0,0,0,100,100,0"
- "01/01/1972,486,AGED,TWO,1,1,BCBS,40,20,0,0,0,10,10,0"
- "48197,50,AGED,THREE,1,1,BCBS,-1284.84,0,0,0,0,-1284.84"
- "90255,486,AGED,TWO,1,1,BCBS,40,10,10,0,0,20"
- In 'Aged Accounts Report' results display, click 'Export All Pages' or 'Export Page' button to export/save .CSV format report data to file.
- Open/review exported .CSV format file, ensuring that data header and all individual data rows are present in file as displayed/defined above.
|
Topics
• Aged Accounts Report
• NX
|
Registry Setting - Enable Payment Acknowledgement
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Posting/Adjustment Codes Definition
- Dictionary Update (PM)
- Dynamic Form - Dictionary Update - Locked Dictionary
Scenario 1: 'Posting/Adjustment Codes Definition' form - 'Enable Payment Acknowledgement' registry setting validation
Specific Setup:
- Registry Setting: Enable Payment Acknowledgement = N
Steps
- Open ‘Posting/Adjustment Code Definition’
- Select ‘Edit’ and select any posting code.
- Verify that the 'Payment Acknowledgement Type' field is not displayed on the form.
- Close the form.
- Open ‘Registry Settings’.
- Search for 'Enable Payment Acknowledgement' and set the value to ‘Y’.
- Refresh forms.
- Open ‘Posting/Adjustment Code Definition’
- Select ‘Add’ to create a new posting code, or ’Edit’ to select an existing code.
- Verify that the 'Payment Acknowledgement Type' field is located on the form.
- If adding a new code, fill out desired values in all fields, including 'Payment Acknowledgement Type'.
- If editing an existing code, add desired value to ‘Payment Acknowledgement Type'.
- Click [File Posting/Adjustment Code].
- Select ‘Edit’ and select the code that was filed.
- Validate that the 'Payment Acknowledgement Type' field contains the value that was previously selected.
Scenario 2: 'Posting/Adjustment Codes Definition' web services - 'Enable Payment Acknowledgement' registry setting validation
Specific Setup:
- Registry Setting:
- Enable Payment Acknowledgement = N
- Web Service Request
- The ‘AddPostingAdjustmentCodes’ request has been sent to add a new Posting/Adjustment Code Definition and it includes a value in ‘PaymentAckTyp’.
- Verify that the request files successfully.
Steps
- Open ‘Posting/Adjustment Code Definition’
- Select ‘Edit’ and select the posting code created by the web service request.
- Verify that the 'Payment Acknowledgement Type' field is not displayed on the form.
- Close the form.
- Open ‘Registry Settings’.
- Search for 'Enable Payment Acknowledgement' and set the value to ‘Y’.
- Refresh forms.
- Copy the ‘AddPostingAdjustmentCodes’ request to an ‘Update PostingAdjustmentCodes’ request and file the request.
- Verify that the request files successfully.
- Open ‘Posting/Adjustment Code Definition’
- Select ‘Edit’ and select the posting code created by the web service request.
- Verify that the 'Payment Acknowledgement Type' field contains the value sent in the request.
- Close the form.
|
Topics
• Posting/Adjustment Codes Definition
• NX
• Web Services
|
Avatar PM 'Summary Trial Balance Report'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Summary Trial Balance Report
Scenario 1: 'Summary Trial Balance Report' - Verification of .CSV format report results
Steps
- Open Avatar PM 'Summary Trial Balance Report' form (under 'Avatar PM / Billing / Billing Reports / Monthly Closeout Reports' menu).
- Enter/select values for 'Summary Balance As Of ', 'Aging Category' and 'Include Bad Debt Information' report criteria fields.
- Ensure 'Export Detail Information to CSV' field is present in form, with 'Yes' checkbox/selection available.
- No selection in the 'Export Detail Information to CSV' field will render report results in the default report format
- Selecting 'Yes' in the 'Export Detail Information to CSV' field will display report results in CSV (comma-separated value) format (allowing user to export/save 'Summary Trial Balance Report' results for external use)
- Click 'Process' button to run report/render result data.
- If no value is selected in 'Export Detail Information to CSV' field, ensure that 'Summary Trial Balance Report' results are rendered/displayed in the default report format.
- If 'Yes' is selected for 'Export Detail Information to CSV' field, ensure that 'Summary Trial Balance Report' results are rendered/displayed in .CSV format within myAvatar/Avatar NX, with following header and individual data rows present:
- 'Summary Trial Balance Report' .CSV format data header (first row in report data results) will contain the following data elements:
- 'RRG'
- 'RRG Description'
- 'Financial Class'
- 'Financial Class Description'
- 'Unbilled In-House'
- 'Unbilled Disch'
- 'Days'
- Aging Categories (default or custom entered/edited values as defined in 'Aging Category' report criteria field; 'Aging 0', 'Aging 30', 'Aging 60', 'Aging 120', etc.)
- Header row examples:
- "RRG,RRG Description,Financial Class,Financial Class Description,Unbilled In-House,Unbilled Disch,Days,Billed/Aging Category 0,Billed/Aging Category 30,Billed/Aging Category 60,Billed/Aging Category 90,Billed/Aging Category 120,Total"
- "RRG,RRG Description,Financial Class,Financial Class Description,Unbilled In-House,Unbilled Disch,Days,Billed/Aging Category 5,Billed/Aging Category 10,Billed/Aging Category 20,Billed/Aging Category 30,Billed/Aging Category 40,Billed/Aging Category 50,Billed/Aging Category 60,Total"
- 'Total'
- 'Summary Trial Balance Report' .CSV format individual data rows (second and all subsequent rows in report data results) will contain report data for each element, one row per result.
- Data row examples:
- "5,Outpatient Substance Abuse,7,Medicare Part A,2397.15,0.00,0,1181.21,0.00,0.00,0.00,815.00,4393.36"
- "1,Inpatient Psychiatric,10,Non-Recoverable,18635.12,6000.50,0,3360.52,88.00,1500.00,200.00,6526.80,40022.44"
- "5,Outpatient Psychiatric,3,Blue Cross,1176903.89,0.00,0,1476.11,0.00,0.00,0.00,0.00,0.00,12365.15,1190745.15"
- In 'Summary Trial Balance Report' results display, click 'Export All Pages' or 'Export Page' button to export/save .CSV format report data to file.
- Open/review exported .CSV format file, ensuring that data header and all individual data rows are present in file as displayed/defined above.
|
Topics
• Summary Trial Balance Report
• NX
|
The SQL file 'data_entry_by' in the 'History_Bed_Assignment' table is updated.
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Change Program/Admission Date
Scenario 1: 'Change Program/Admission Date' SQL data verification.
Steps
For internal testing only.
|
Topics
• Change Program/Admission Date
|
Prevent 'staff only' appointments from being opened by multiple users at one time.
Scenario 1: Scheduling Calendar - Staff Only appointments: validate 'Details/Edit' can only be edited by one user at a time.
Specific Setup:
- For Avatar PM facilities: Avatar PM 2022 Update 66 is required to resolve this issue.
- For Avatar Cal-PM facilities: Avatar Cal-PM Update 35 is required to resolve this issue.
- Two users (User 1 and User 2) have permissions to view other practitioner's schedules in the "Scheduling Calendar".
- A 'Staff Only' appointment has been added to one of the practitioner's schedule.
- Both users are logged in.
Steps
- Both users should have the 'Scheduling Calendar' opened.
- User 1: right click on the 'Staff Only' appointment.
- Select 'Details/Edit'. Do not change anything, and leave the form open.
- User 2: right click on the same 'Staff Only' appointment.
- Select 'Details/Edit'.
- User 2 will see a message: 'The appointment is currently locked by: User 1. Editing is unavailable at this time.'
- Click [OK] to exit the message.
- User 1: exit the form.
- User 2: right click on the same 'Staff Only' appointment.
- Select 'Details/Edit'. The form will open for User 2.
|
Topics
• Scheduling Calendar
• NX
|
AR Console - Claim Follow-Up Entry
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- AR Console Configuration
- AR Console User Defaults Setup
- Client Ledger
- Client Charge Input
- Guarantors/Payors
- Electronic Billing
- System Task Scheduler
- User Definition
- Dynamic Form - Add To Problem List
- Program Maintenance
Scenario 1: Account Receivable Console - Add Claim Follow-Up/Notes
Specific Setup:
- Note the tester's 'User Definition', 'User Description'.
- Registry Setting:
- Set the 'Avatar PM->Billing->Accounts Receivable Management->->->Enable Accounts Receivable Management Functionality' registry setting to "Yes".
- Accounts Receivable functionality has been defined.
- Identify a client with three or more unpaid claims.
- Note the client's last name initial, ID, admission program.
- Note the guarantor the claim liability distributed to.
- 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.
Steps
- Access the ‘AR Console’.
- Enter the desired ‘Client’.
- Enter desired dates in ‘Service Date From’ and ‘Service Date To’.
- Click [Search].
- Validate that the claims display in the ‘Claims with Outstanding Receivables’ grid.
- Select one claim row, noting the claim number.
- Click [Add Claim Follow-Up/Notes].
- Validate that ‘Claim Follow-Up’ contains the selected claim number.
- Enter desired value in ‘Edit Payer ICN#’.
- Select desired value in ‘Claim Submission Reason Code’.
- Go to the ‘Follow-Up Notes’ section.
- Verify that a row has been created for the current date and with a comment of ‘AR Console Follow-Up Created’.
- Click [New Row].
- Enter desired values for ‘Follow-Up Date’ and ‘Comments’ at a minimum. Data may be added to other fields if desired.
- Click [File Updates].
- Click [OK].
- Click [AR List] to return to the first section of the form.
- Select the same claim in the ‘Claims with Outstanding Receivables’ grid.
- Click [Add Claim Follow-Up/Notes].
- Validate that the data added to the ‘Edit Payer ICN#’ and 'Claim Submission Reason Code’ fields displays correctly.
- Go to the ‘Follow-Up Notes’ section.
- Verify that the row created by with the comment of ‘AR Console Follow-Up Created’ displays correctly.
- Verify that the new row that was added displays the submitted data correctly.
- Click [AR List] to return to the first section of the form.
- Repeat steps 6 -24, selecting a minimum of two claims in the ‘Claims with Outstanding Receivables’ grid, and toggling between the claims in the ‘Claim Follow-Up Entry' section.
|
Topics
• Accounts Receivable Management
• NX
|
Avatar PM 'Payment/Adjustment Report'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Payment/Adjustment Report
Scenario 1: Payment/Adjustment Report - Verification of .CSV format report results - By Revenue Group, Payment/Adjustment, & Financial Class
Steps
- Open Avatar PM 'Payment/Adjustment Report' form (under 'Avatar PM / Billing / Billing Reports / Ad Hoc Reports' menu).
- Enter/select values for 'From Date', 'Thru Date', 'Individual Or All Or Grouped Codes' and all other required/desired report criteria fields.
- Ensure 'Export Detail Information to CSV' field is present in form.
- No selection in the 'Export Detail Information to CSV' field will render report results in the default report format
- Selecting 'By Revenue Group, Payment/Adjustment, & Financial Class' in the 'Export Detail Information to CSV' field will display Payment/Adjustment Report Revenue Group/Payment/Financial Class summary results in CSV (comma-separated value) format (allowing user to export/save 'Summary Trial Balance Report' results for external use)
- Selecting 'By Revenue Group, Financial Class, Group Code & Service Code' in the 'Export Detail Information to CSV' field will display Payment/Adjustment Report Revenue Group/Financial Class/Group Code/Service Code detail results in CSV (comma-separated value) format (allowing user to export/save 'Summary Trial Balance Report' results for external use)
- Click 'Process' button to run report/render result data.
- If no value is selected in 'Export Detail Information to CSV' field, ensure that 'Payment/Adjustment Report' results are rendered/displayed in the default report format.
- If 'By Revenue Group, Payment/Adjustment, & Financial Class' is selected for 'Export Detail Information to CSV' field, ensure that 'Payment/Adjustment Report' results are rendered/displayed in .CSV format within myAvatar/Avatar NX, with following header and individual data rows present:
- 'Payment/Adjustment Report' .CSV format data header (first row in report data results) will contain the following data elements:
- 'Revenue Group Code'
- 'Revenue Group Description'
- 'Payment/Adjustment Code'
- 'Payment/Adjustment Description'
- 'Financial Class Code'
- 'Financial Class Description'
- 'Amount'
- Header row example:
- "Revenue Group Code,Revenue Group Description,Payment/Adjustment Code,Payment/Adjustment Description,Financial Class Code,Financial Class Description,Amount"
- 'Payment/Adjustment Report' .CSV format individual data rows (second and all subsequent rows in report data results) will contain report data for each element, one row per result.
- Data row examples:
- "4,"Outpatient Psychiatric",380,"Administrative Discount",3,"Medicaid",1687.50"
- "5,"Outpatient Substance Abuse",200,"Transfer",9,"Blue Cross",45.75"
- "7,"Partial Substance Abuse",100,"Payment - Check",5,"Commercial",280.00"
- If 'By Revenue Group, Financial Class, Group Code & Service Code' is selected for 'Export Detail Information to CSV' field, ensure that 'Payment/Adjustment Report' results are rendered/displayed in .CSV format within myAvatar/Avatar NX, with following header and individual data rows present:
- 'Payment/Adjustment Report' .CSV format data header (first row in report data results) will contain the following data elements:
- 'Revenue Group Code'
- 'Revenue Group Description'
- 'Client Name'
- 'Client MR #'
- 'Client Episode #'
- 'Client Claim #'
- 'Transaction Date'
- 'Post Date'
- 'Payment Adjustment Code'
- 'Payment Adjustment Description'
- 'Service Code'
- 'Service Code Description'
- 'Amount'
- 'Financial Class Code'
- 'Financial Class Description'
- 'Posted By'
- Header row example:
- "Revenue Group Code,Revenue Group Description,Client Name,Client MR #,Client Episode #,Client Claim #,Transaction Date,Post Date,Payment Adjustment Code,Payment Adjustment Description,Service Code,Service Code Description,Amount,Financial Class Code,Financial Class Description,Posted By"
- 'Payment/Adjustment Report' .CSV format individual data rows (second and all subsequent rows in report data results) will contain report data for each element, one row per result.
- Data row examples:
- "4,"Outpatient Psychiatric","LASTNAME,FIRSTNAME","464",1,"137",10/18/2021,10/18/2021,310,"Contractual Adjustment - CR",600,"Brief Visit",25.00,3,"Medicaid","SYSTEM USER ONE""
- "5,"Outpatient Substance Abuse","ZLASTNAME,ZFIRSTNAME","465",1,"Unbilled",01/29/2022,01/29/2022,100,"Payment - Check",700,"Intensive Visit",400.00,3,"Medicaid","SYSTEM USER TWO""
- In 'Payment/Adjustment Report' results display, click 'Export All Pages' or 'Export Page' button to export/save .CSV format report data to file.
- Open/review exported .CSV format file, ensuring that data header and all individual data rows are present in file as displayed/defined above.
|
Topics
• Payment/Adjustment Report
• NX
|
Avatar PM 'Earned Income Report'
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: 'Earned Income Report' - Verification of .CSV format report results
Steps
- Open Avatar PM 'Earned Income Report' form (under 'Avatar PM / Billing / Billing Reports / Monthly Closeout Reports' menu).
- Enter/select values for 'From Month/Year' and 'Thru Month/Year' report criteria fields.
- Ensure 'Export Detail Information to CSV' field is present in form.
- No selection in the 'Export Detail Information to CSV' field will render report results in the default report format
- Selecting 'By Revenue Group and Service Group' in the 'Export Detail Information to CSV' field will display Revenue Code/Service Group report detail results in CSV (comma-separated value) format (allowing user to export/save 'Earned Income Report' results for external use)
- Selecting 'By Revenue Group, Financial Class and Service Group' in the 'Export Detail Information to CSV' field will display Revenue Code/Financial Class/Service Group report detail results in CSV (comma-separated value) format (allowing user to export/save 'Earned Income Report' results for external use)
- Click 'Process' button to run report/render result data.
- If no value is selected in 'Export Detail Information to CSV' field, ensure that 'Earned Income Report' results are rendered/displayed in the default report format.
- If 'By Revenue Group and Service Group' is selected for 'Export Detail Information to CSV' field, ensure that 'Earned Income Report' results are rendered/displayed in .CSV format within myAvatar/Avatar NX, with following header and individual data rows present:
- 'Earned Income Report' .CSV format data header (first row in report data results) will contain the following data elements:
- 'Revenue Group Code'
- 'Revenue Group Description'
- 'Service Group Code'
- 'Service Group Description'
- 'Earned Income Amount'
- Header row example:
- "Revenue Group Code,Revenue Group Description,Service Group Code,Service Group Description,Earned Income Amount"
- 'Earned Income Report' .CSV format individual data rows (second and all subsequent rows in report data results) will contain report data for each element, one row per result.
- Data row examples:
- "1,"Inpatient Psychiatric",1,"Room & Board",51575.00"
- "5,"Outpatient Substance Abuse",2,"Professional Services",170466.98"
- If 'By Revenue Group, Financial Class and Service Group' is selected for 'Export Detail Information to CSV' field, ensure that 'Earned Income Report' results are rendered/displayed in .CSV format within myAvatar/Avatar NX, with following header and individual data rows present:
- 'Earned Income Report' .CSV format data header (first row in report data results) will contain the following data elements:
- 'Revenue Group Code'
- 'Revenue Group Description'
- 'Financial Class Code'
- 'Financial Class Description'
- 'Service Group Code'
- 'Service Group Description'
- 'Earned Income Amount'
- Header row example:
- "Revenue Group Code,Revenue Group Description,Financial Class Code,Financial Class Description,Service Group Code,Service Group Description,Earned Income Amount"
- 'Earned Income Report' .CSV format individual data rows (second and all subsequent rows in report data results) will contain report data for each element, one row per result.
- Data row examples:
- "1,"Inpatient Psychiatric",7,"Medicare A",1,"Room & Board",22740.00"
- "5,"Outpatient Substance Abuse",3,"Medicaid",2,"Professional Services",103799.11"
- In 'Earned Income Report' results display, click 'Export All Pages' or 'Export Page' button to export/save .CSV format report data to file.
- Open/review exported .CSV format file, ensuring that data header and all individual data rows are present in file as displayed/defined above.
|
Topics
• Earned Income Report
• NX
|
CCBHC PPS Compile – CCBHC PPS Service Definition
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Guarantors/Payors
- Service Codes
- Dictionary Update (PM)
- Program Maintenance
- Practitioner Numbers By Guarantor And Program
- CCBHC PPS Service Definition
- Admission (Outpatient)
- Dynamic Form Address Validation
- Update Client Data
- Client Charge Input
- Dynamic Form - Plan
- Client Ledger
- CCBHC PPS Compile
Scenario 1: CCBHC PPS-1 Compile - Primary guarantor has no guarantor PPS definition - Secondary guarantor has a guarantor PPS definition
Specific Setup:
- Dictionary Update: Client - 10006 - Location
- Note at least one location that is a CCBHC location.
- Service Codes:
- 1: CCBHC Enumerated service. Note the ‘Covered Charge Category’.
- 2: CCBHC Non- Enumerated service in the same ‘Covered Charge Category’ as 1.
- 3: CCBHC Enumerated service in a different ‘Covered Charge Category’ than 1 & 2.
- 4: CCBHC Non- Enumerated service in the same ‘Covered Charge Category’ as 3.
- Benefit Plan:
- 1: The ‘Covered Charge Category’ for Service Codes 1 & 2 is included. The ‘Covered Charge Category’ for Service Codes 3 & 4 is not included.
- 2: The ‘Covered Charge Category’ for Service Codes 3 & 4 is included. The ‘Covered Charge Category’ for Service Codes 1 & 2 is not included.
- Guarantors/Payors: Both guarantors have a value of ‘Yes’ in CCBHC Guarantor. They can be in the same or different financial classes.
- 1: The ‘Default Guarantor Plan’ is Benefit Plan 1.
- 2: The ‘Default Guarantor Plan’ is Benefit Plan 2.
- CCBHC PPS Service Definition:
- 1: Note the effective date. The PPS-1 Service code is Service Code 2.
- 2: Note the effective date. The Guarantor is guarantor 2. The PPS-1 Service code is Service Code 4.
- Client:
- Client's primary guarantor is guarantor 1.
- Client's secondary guarantor is guarantor 2.
- Client has an active diagnosis record.
- Client has enumerated services, provided at a CCBHC location, for services codes 1 & 3. The dates of service must be on or after the CCBHC PPS Service Definition effective date. Note the dates of service.
- Client Ledger has been used to verify that the service liability distributed to the correct guarantor.
- Close Charges has been used to close the charges.
Steps
- Open ‘ CCBHC PPS Compile.
- Enter the desired ‘Start Date’.
- Enter the desired ‘End Date’.
- Enter the desired ‘Client ID’.
- Click [Compile & Post Services].
- Close the form.
- Open ‘Client Ledger’.
- Enter the desired ‘Client ID’.
- Select ‘All Episodes’ in ‘Claim/Episode/All Episodes’.
- Select ‘ Simple’ in ‘Ledger Type’.
- Enter the desired ‘From Date’.
- Enter the desired ‘ To Date’.
- Click [Process].
- Validate that the correct guarantor was selected for each CCBHC Non- Enumerated service.
- Close the report.
- Close the form.
|
Topics
• CCBHC
• NX
|
Default 'Add to Problem List' field on 'Diagnosis' form.
Scenario 1: Diagnosis - Verify Registry Setting "Default 'Add To Problem List'"
Specific Setup:
- Avatar 2022 CWS Update 69 is required for full functionality.
- Avatar 2022 CareFabric Update 54 is required for full functionality.
Steps
- Open 'Registry Settings' form.
- Set 'Limit Registry Settings to the Following Search Criteria' field to 'add to problem list'.
- Click [View Registry Settings].
- Verify 'Registry Setting' contains 'Avatar PM->Client Information->Diagnosis->->->Default 'Add To Problem List' to "Yes" on New Diagnosis'
- Confirm the 'Registry Setting Value' is defaulted to 'Y'. Selecting 'Y' defaults the value for the field 'Add To Problem List' to "Yes" when adding new diagnosis record.
- Click [Submit].
- Open the 'Diagnosis' form for a test client (Client A).
- Set the 'Type Of Diagnosis' to any value.
- Set the 'Date Of Diagnosis' to the current date.
- Set the 'Time Of Diagnosis' to the current time.
- Click [New Row].
- Verify the 'Add To Problem List' field is defaulted to 'Yes'.
- Click the 'Problem Classification' field.
- Verify the values for 'Problem Classification' are displayed. Note that this field can be made required by setting 'Registry Setting' 'Avatar CWS->Problem List->->->->Problem Classification Required' to 'R'. Please see the description in the Registry Setting for more information.
- Complete the fields as needed and file the diagnosis.
- Open the 'Diagnosis' form for the same client.
- Select the diagnosis record entered above.
- Verify the fields contain the data as filed.
- Click [Close Form].
- Return to the 'Registry Settings' form and select "Default 'Add To Problem List'".
- Change the setting to 'N'.
- Return to the 'Diagnosis' form.
- Set the 'Type Of Diagnosis' to any value.
- Set the 'Date Of Diagnosis' to the current date.
- Set the 'Time Of Diagnosis' to the current time.
- Click [New Row].
- Verify the 'Add To Problem List' field is not defaulted.
- Verify the Click the 'Problem Classification' field is disabled.
- Exit the form.
|
Topics
• Diagnosis
• NX
|
Patient/PCP Association - Search Results
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- PCP Definition and Communication Preferences
- Dynamic Form PCP Definition
- Admission
- Patient/PCP Association
Scenario 1: 'PCP Definition and Communications Preferences'.
Steps
- Open 'PCP Definition And Communication Preferences'
- Fill out and submit the form.
- Open 'PCP Definition And Communication Preferences'
- Validate that the new PCP Definition has been created.
Scenario 2: PCP/Patient Association
Specific Setup:
- Admit a new client or select an existing client with multiple episodes.
- Note the programs the client is admitted to.
Steps
- Using the "PCP Definition and Communication Preference" form, enter in 50+ primary care physicians with the same last name.
- Check the PCP search to validate that the search will search on 3 characters of the last name,1st 3 characters of the first name.
- Open the "Patient/PCP Association" form.
- Enter the test client.
- Search the PCP field.
- Validate that the results returned only include the providers who are associated with the same program(s) as the client is enrolled in.
- Select a PCP for the client.
- File the form.
|
Topics
• NX
|
Quick Billing Rule Definition - new fields
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- User Definition
- Guarantors/Payors
- Client Charge Input
- Practitioner Enrollment
- Practitioner Numbers By Guarantor And Program
- Quick Billing Rule Definition
- Quick Billing
- Program Maintenance
- Client Ledger
Scenario 1: Qucik Billing Rule Definition - 'Include "errors.txt" File' and 'File Location' for "errors.txt".
Specific Setup:
- Client:
- Select a client that has missing data that will prevent it from being billed. This example will use a missing ‘Policy Number’ in Financial Eligibility’. Note the guarantor.
- Create services for the client and validate that the fee distributed to the above guarantor. Note the service code, program, and dates of service.
- Quick Billing Rue Definition:
- A quick billing rule definition is defined that will include the guarantor, service code, and program.
- ‘Send Generated Bill To' = File.
- Note the ‘File Location’ value.
- ‘Include “errors.txt” File’ = ‘No’.
Steps
- Open ‘Quick Billing’.
- Select ‘Add’ in ‘Add New Or Edit Existing Quick Billing Batch’.
- Enter desired ‘First Date Of Service To Include’.
- Enter desired ‘Last Date Of Service To Include’.
- Select desired ‘Billing Rule To Execute’.
- Select ‘Create Batch’, ‘Close Charges ’, and ‘Generate Bills’ in ‘Quick Billing Tasks to Execute’.
- Enter desired ‘Date Of Claim‘.
- Validate that the ‘Compile Complete’ message indicates that errors were found.
- Close the form.
- Go to the ‘File Location’ and verify that no error file was created.
- Open ‘Quick Billing Rule Definition’ and edit the rule from ‘Setup’.
- Change the ‘Include “errors.txt” File’ to ‘Yes’.
- Submit the form.
- Open ‘Quick Billing’.
- Select ‘Add’ in ‘Add New Or Edit Existing Quick Billing Batch’.
- Enter desired ‘First Date Of Service To Include’.
- Enter desired ‘Last Date Of Service To Include’.
- Select desired ‘Billing Rule To Execute’.
- Select ‘Create Batch’, ‘Close Charges’, and ‘Generate Bills’ in ‘Quick Billing Tasks to Execute’.
- Enter desired ‘Date Of Claim‘.
- Validate that the ‘Compile Complete’ message indicates that errors were found.
- Close the form.
- Go to the ‘File Location’ and verify that the error file was created.
- Open ‘Quick Billing Rule Definition’ and edit the rule from ‘Setup.
- Change the ‘Include “errors.txt” File’ to ‘In Separate Location’.
- Enter a value in ‘File Location for "errors.txt" File’ that differs from the ‘File Location’ value’.
- Submit the form.
- Open ‘Quick Billing’.
- Select ‘Add’ in ‘Add New Or Edit Existing Quick Billing Batch’.
- Enter desired ‘First Date Of Service To Include’.
- Enter desired ‘Last Date Of Service To Include’.
- Select desired ‘Billing Rule To Execute’.
- Select ‘Create Batch’, ‘Close Charges’, and ‘Generate Bills’ in ‘Quick Billing Tasks to Execute’.
- Enter desired ‘Date Of Claim‘.
- Validate that the ‘Compile Complete’ message indicates that errors were found.
- Close the form.
- Go to the ‘File Location for "errors.txt" File’ and verify that the error file was created.
- Fix the client data, in this example the missing ‘Policy Number’ in Financial Eligibility’.
- Open ‘Quick Billing’.
- Select ‘Add’ in ‘Add New Or Edit Existing Quick Billing Batch’.
- Enter desired ‘First Date Of Service To Include’.
- Enter desired ‘Last Date Of Service To Include’.
- Select desired ‘Billing Rule To Execute’.
- Select ‘Create Batch’, ‘Close Charges’, ‘Generate Bills’, and 'Create Claims' in ‘Quick Billing Tasks to Execute’.
- Enter desired ‘Date Of Claim‘.
- Validate that the ‘Compile Complete’ message indicates that no errors were found.
- Go to the ‘File Location’ and verify that the billing file was created.
- Open 'Client Ledger' for the client and validate that the claim number displays.
|
Topics
• Quick Billing
• NX
|
| |
