Null Values Are Supported In "Collateral Relationship"
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Referral Search
- Referral Information Form Set
- Agency Referral Personal Information [EDIT]
- Race Subform
- Members Personal Form [EDIT]
- Import Services Form Set
- Import File Templates
- ImportFileLog
- Benefit Assignment [EDIT]
- Referral to Programs from Outside - People Edit Subform
- Referral to Agency [EDIT]
Scenario 1: EPICADT04 and EPICADT08- Preadmit AND Update Patient- NK 1.3 - Validate "Collateral Relationship" Updates Records
Specific Setup:
- The referral record to be added into the system, with no Collateral Relationship, NK1.3 Segment.
- A second referral record to update a preexisting referral in the system, with no Collateral Relationship, NK1.3 Segment.
- The Import File Templates have a default value for the Collateral Relationship.
- The user knows the values in the fields.
Steps
- Import a record that is missing the NK1.3 segment. This is the collateral relationship field.
- Navigate to "Taskbar > System Maintenance > Import Services > Import File Log".
- Select the template used.
- Validate no errors occurred for the import.
- Validate the record was created or changes took place, based on the import file used.
- Validate a collateral exists that contains the default value that was used in the precondition.
|
Topics
• CareConnect
|
ECS-55618
Summary
|
Details
11.0.0000.08, 11.0.0025.04, 11.0.0050.01, 11.0.0075
Place of Service Code and Calculate Rate
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Claim Output Form Set
- Claim Output
- Place of Service Location Link Subform
- Location Table (Service)
- Billing Place of Service Code Setup [EDIT]
- Billing Batches Management
- Billing Batch Management 2.0 Form Set
- BillingProcessHistory
- FinanceClaims
- Claim 2.0 [EDIT]
- Claims Maintenance NX Form Set
- Claim Submission 2.0 [EDIT]
- Claim Service Lines NX Subform
- Claim/Invoice Batch [VIEW]
- Claim Output Ready
- AR Management
- Cash Receipts for Remittance
- Claims Submission For Remittance NX [EDIT]
- All Clients With Security Listing by PeopleID
- Billing Request Action Based Run [ADD]
- Action Based Run - Claim Action Types
- ActionsView
Scenario 1: Validate Place of Service Updates After Changes To Finance Setup
Specific Setup:
- Client has two Benefit Assignments.
- Service is billable to both Benefit Assignments.
- Service has Location information.
Steps
- Navigate to "Finance > Claim/Invoice Processing > Batch Listing > Billing Batches Management".
- Create a "Billing Run" to capture "Service" from preconditions.
- Upon completion of "Billing Execution Interval", create "837 File".
- Validate "Place of Service" information is present for the "Claim".
- Mark "Batch" as sent.
- Navigate to "Finance > Remittance Processing > Remittance Application > Apply Receipt to Claims".
- Select "Check".
- Set "Filters" to search on "Claim".
- Click "Deny" and "Add Action".
- Select "Resubmit to Other" and use "Calculate Rate", save.
- Upon completion of "Billing Execution Interval", click on "Submission" and "Batch", create "837 File".
- Validate "Place of Service" information is present for the "Claim".
Scenario 2: Validate Place Of Service Code Saves When Using Calculate Rate
Specific Setup:
Requires a service that was billed and "Location/Place of Service" was changed after billing.
Steps
- Navigate to "Finance > Remittance Processing > Remittance Application > AR Management".
- Select desired "Remittance".
- Set parameters to search for desired claim.
- Click "Add Action".
- "Resubmit" the claim using "Calculate Rate".
- Validate "Place of Service" field contains desired place of service code.
- Save.
- Wait for billing to run.
- Open the new submission.
- Validate "Place of Service" contains desired place of service code.
- Click on the "Batch" link.
- Click "Open Batch"
- Click on "Create Output".
- Download the "837 Output".
- Validate the "CLM" line contains desired place of service code.
|
Topics
• Finance
• Finance Setup
|
ECS-56716
Summary
|
Details
11.0.0075, 11.0.0050.02, 11.0.0025.05, 11.0.0000.09
Held Claim For Service Not Approved
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Billing Batches Management
- FinanceClaims
- SupervisorModule
- All Clients With Security Listing by PeopleID
- Immediate Billing Run Request [ADD]
- Submitter Information
- Billing Run Request Limit People Subform
- All People with Benefit Assignments with LOS
- Billing Batch Management 2.0 Form Set
- BillingProcessHistory
- Agency [EDIT]
Scenario 1: Validate Claim Held For Service Not Approved Is Released
Specific Setup:
- Requires a claim that is held for "Service Not Approved".
- Scenario works with a service that has been submitted to supervisor, but not yet approved.
Steps
- Navigate to "Taskbar > Supervisor > Supervisor > Service/Case Notes & Planning Approval".
- Validate desired service is listed.
- Click "Actions" button and select "Approve".
- Save.
- Navigate to "Finance > Claim/Invoice Processing > Batch Listing > Billing Batches Management".
- Click "New Run".
- Select "Immediate Run".
- Fill in required fields to generate desired billing run.
- Save.
- Wait for billing to run.
- Validate the billing contains desired claim and it is no longer in "Held" status.
Scenario 2: Validate Claim Held For Service Not Approved Is Released With New Claim Number
Specific Setup:
- Requires a claim that is held for "Service Not Approved".
- Scenario works with a service that has been submitted to supervisor, but not yet approved.
Steps
- Navigate to "Agency Setup > Agency > Agency > Agency Information".
- Check the flag "Delete Held Claims".
- Save.
- Navigate to "Taskbar > Supervisor > Supervisor > Service/Case Notes & Planning Approval".
- Validate desired service is listed.
- Click "Actions" button and select "Approve".
- Save.
- Navigate to "Finance > Claim/Invoice Processing > Batch Listing > Billing Batches Management".
- Click "New Run".
- Select "Immediate Run".
- Fill in required fields to generate desired billing run.
- Save.
- Wait for billing to run.
- Validate the billing contains desired claim with a new claim number and it is no longer in "Held" status.
|
Topics
• Finance
|
ECS-56968
Summary
|
Details
11.0.0000.08, 11.0.0025.04, 11.0.0050.01, 11.0.0075
New Referral/Client Wizard
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Search
- Person Information [ADD]
- Wizard
- Merge Utility
- People Search
- Referral Search
Scenario 1: Validate Cannot Create New Client With Duplicate Social Security Number to Another Client
Specific Setup:
Known social security number for a Client in the system.
Steps
- Navigate to "Client > Client Information > Personal Information > Demographics".
- Click the "Select Client" search box.
- Click New and Intake - New.
- Enter any Last Name, First Name, Gender.
- Enter a Social Security number you know is in use already (do not use blank or all zeros).
- Click Proceed.
- Confirm that the search includes the client that has the SSN you entered listed.
- Check "Create new record..." box and click Proceed.
- Confirm that an alert opens showing
- Error(s) occurred on save:
- New Person record cannot be saved, return to search to address:
- Duplicate Social Security #: [SSN ENTERED]
- Close alert and Confirm that the Results window is still active (not locked, does not proceed).
- Click Previous to return to the Search page.
- Enter a valid SSN and client info.
- Click Proceed.
- Check "Create new record..." box and click Proceed.
- Confirm the Wizard continues to the Personal Information page with the new information without validations.
Scenario 2: Validate Cannot Create New Referral With Duplicate Social Security Number to Another People Record
Specific Setup:
Known social security number for a People Record in the system.
Steps
- Navigate to "Referral > Agency Referral > Referral Information > Demographics".
- Click Search for Referrals.
- Click New Referrals Wizard.
- Enter any Last Name, First Name, Gender.
- Enter a Social Security number you know is in use already (not blank or all 0s, these are ignored).
- Click Proceed.
- Confirm that the search includes the client that has the SSN you entered listed.
- Check "Create new record..." box and click Proceed.
- Confirm that an alert opens showing
- Error(s) occurred on save:
- New Person record cannot be saved, return to search to address errors:
- Duplicate Social Security #: [SSN ENTERED]
- Close alert and Confirm that the Results window is still active (not locked, does not proceed).
- Click Previous to return to the Search page.
- Enter a valid SSN and client info.
- Click Proceed.
- Check "Create new record..." box and click Proceed.
- Confirm the Wizard continues to the Personal Information page with the new information without errors.
|
Topics
• Client
• Referral Application
|
Immunization MSH-16
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Historical Immunizations Registry - Public Health [EDIT]
- Vaccine Lookup
- Client Search
- Immunization Query [ADD]
- Service Facilities Listing
Scenario 1: UpdateVaccination - applicationAcknowledgementTypeCode
Scenario 2: QueryVaccination - applicationAcknowledgementTypeCode
|
Topics
• Third Party Solution
|
Call Center Anchored Menu Items
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Call Disposition with Intake [EDIT]
- Call Center Search Forms [ADD]
- Call Center Search Forms [EDIT]
- Call Center Form Test [EDIT]
Scenario 1: Call Center – Validate Anchors in Call Center Event Navigation Panel Display After Minimizing/Saving
Steps
- Navigate to "Taskbar > Call Center > Call Center > Call Center".
- Create a new call, select client, click Save and Close.
- Take note of anchored items.
- Open existing call from Incomplete Calls.
- Validate anchored items still displaying.
- Click Minimize and re-open call from Unsaved Calls.
- Validate anchored items still displaying.
- Select an event from the call.
- Take note of anchored items.
- Save and Close with the event selected.
- Re-open the call from Incomplete Calls.
- Validate all anchored items still displaying.
- Save and Close the call.
- Re-open the call from Call Center Table.
- Validate all anchored items still displaying.
- Minimize the call.
- Re-open the call from Unsaved Calls.
- Validate all anchored items still displaying.
- Fill remaining required information and Mark and Save Completed.
- Open completed call.
- Validate all anchored items still displaying.
Scenario 2: Call Center - Validate Changing Event Replaces Tree Event Links
Steps
- Navigate to "Taskbar > Call Center > Call Center > Call Center".
- Start a new call.
- Fill form and select an event.
- Change the event.
- Validate event links on left get replaced instead of creating new rows indefinitely.
|
Topics
• Call Center
• Taskbar
|
Lab Results From OrderConnect
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Program Enrollments For Use With OrderConnect
- Client Search
- OrderConnect Member Sign-On
- OrderConnect Current Medication Profile
- OrderConnect Current Order Profile
- OrderConnect - Lab Result Detail -- Webpage Dialog
Scenario 1: OrderConnect - Validate Result Dates in Lab Orders
Steps
- Navigate to "Client > Public Health > Labs and Medication > Lab Results".
- Search and select desired Client.
- Click Actions.
- Select "OC e-Prescription" from the Actions drop down list.
- Verify the pop-up window for OrderConnect exist.
- Click "Continue".
- Select the "Orders" tab.
- Click the "Add Result" link.
- Fill out required fields.
- Click Save.
- Close out of OrderConnect.
- Click "Refresh" button in myEvolv NX.
- Verify information entered in OrderConnect is listed in the Listing.
|
Topics
• OrderConnect
|
Uploading via Client Information Screen
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- My Client Information Form Set
- Placement Disruptions: Unknown Location [ADD]
- Select File for Upload
- Client Search
- Client Information Screen Form Set
- FrontDeskCheckIn
- Personal Information - All Form Set
Scenario 1: Validate Image Can Be Uploaded via Client Information Screen
Specific Setup:
- Three different clients must be used for testing, one for each location:
- My Client Widget
- Client Module Header
- Front Desk
- Event service form available with upload document, image upload, signature capture.
- Available Client scheduled event in Front Desk.
Steps
- Navigate to "Taskbar > My Homeview > Homeview Launcher > Homeview".
- Select My Clients widget.
- Click the Open Client Formset (red box and arrow) for desired Client.
- Navigate to desired event form.
- Add new event form.
- Click "Click to Upload Image" > Upload File.
- Select a file and upload.
- Validate file is uploaded.
- Validate Event Form window is still displaying.
- Close and Navigate to "Client > Client Information > Personal Information > Demographics".
- Search for a different client.
- Click the Client name in the header.
- Navigate to desired event form.
- Add new event form.
- Click "Click to Upload Document" > Upload File.
- Select a file and upload.
- Validate file is uploaded.
- Validate Event Form window is still displaying.
- Close and Navigate to "Taskbar > Attendance Check In/Out > Check In/Out > Front Desk NX".
- Click the Client name in the scheduled event.
- Navigate to desired event form.
- Add new event form.
- Click "Click to Upload Document" > Upload File.
- Select a file and upload.
- Validate file is uploaded.
- Validate Event Form window is still displaying.
Scenario 2: Validate Signature Can Be Uploaded via Client Information Screen
Specific Setup:
- Three different clients must be used for testing, one for each location:
- My Client Widget
- Client Module Header
- Front Desk
- Event service form available with upload document, image upload, signature capture.
- Available Client scheduled event in Front Desk.
Steps
- Navigate to "Taskbar > My Homeview > Homeview Launcher > Homeview".
- Select My Clients widget.
- Click the Open Client Formset (red box and arrow) for desired Client.
- Navigate to desired event form.
- Add new event form.
- Click "Click to Upload Image" > Upload File.
- Select a file and upload.
- Validate file is uploaded.
- Validate Event Form window is still displaying.
- Close and Navigate to "Client > Client Information > Personal Information > Demographics".
- Search for a different client.
- Click the Client name in the header.
- Navigate to desired event form.
- Add new event form.
- Click "Click to Upload Document" > Upload File.
- Select a file and upload.
- Validate file is uploaded.
- Validate Event Form window is still displaying.
- Close and Navigate to "Taskbar > Attendance Check In/Out > Check In/Out > Front Desk NX".
- Click the Client name in the scheduled event.
- Navigate to desired event form.
- Add new event form.
- Click "Click to Upload Document" > Upload File.
- Select a file and upload.
- Validate file is uploaded.
- Validate Event Form window is still displaying.
Scenario 3: Validate Document Can Be Uploaded via Client Information Screen
Specific Setup:
- Three different clients must be used for testing, one for each location:
- My Client Widget
- Client Module Header
- Front Desk
- Event service form available with upload document, image upload, signature capture.
- Available Client scheduled event in Front Desk.
Steps
- Navigate to "Taskbar > My Homeview > Homeview Launcher > Homeview".
- Select My Clients widget.
- Click the Open Client Formset (red box and arrow) for desired Client.
- Navigate to desired event form.
- Add new event form.
- Click "Click to Upload Document" > Upload File.
- Select a file and upload.
- Validate file is uploaded.
- Validate Event Form window is still displaying.
- Close and Navigate to "Client > Client Information > Personal Information > Demographics".
- Search for a different client.
- Click the Client name in the header.
- Navigate to desired event form.
- Add new event form.
- Click "Click to Upload Document" > Upload File.
- Select a file and upload.
- Validate file is uploaded.
- Validate Event Form window is still displaying.
- Close and Navigate to "Taskbar > Attendance Check In/Out > Check In/Out > Front Desk NX".
- Click the Client name in the scheduled event.
- Navigate to desired event form.
- Add new event form.
- Click "Click to Upload Document" > Upload File.
- Select a file and upload.
- Validate file is uploaded.
- Validate Event Form window is still displaying.
|
Topics
• Client
|
Held Claims in Action Based Runs
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Cash Receipts for Remittance
- AR Management
- Billing Batches Management
- FinanceClaims
- Client Search
- Immediate Billing Run Request [ADD]
- Submitter Information
- Billing Run Request Limit People Subform
- All People with Benefit Assignments with LOS
- Billing Batch Management 2.0 Form Set
- BillingProcessHistory
- All Clients With Security Listing by PeopleID
- Claim/Invoice Batch [VIEW]
- Claim Output Ready
- Client Service Entry
- MB Activity Event [EDIT]
Scenario 1: Validate Action Based Claim Is Released After Held
Specific Setup:
- Requires a claim that can be remitted.
- Service/Claim should be set up so that upon the "Resubmit" action it is in "Held" state.
Steps
- Navigate to "Finance > Remittance Processing > Remittance Application > AR Management".
- Select desired remittance.
- Set parameters to search for desired claim.
- Add desired status and "Resubmit" Action to the claim.
- Select "Calculate Rate".
- Validate "Claim service line" row appears and has a "Held Reason".
- Check the "Claim Line".
- Save.
- Wait for billing to run.
- Navigate to "Finance > Claim/Invoice Processing > Batch Listing > Billing Batches Management".
- Validate the claim is captured in an "Action Based Run" and status is "Held".
- Resolve the reason for hold.
- Create a new "Manual Billing" run.
- After billing is complete, validate it does not contain the "Action Based Clam.
- Validate the "Action Based Run" no longer contains the "Held Claim".
- Reprocess the "Manual Billing Run".
- After billing is complete, validate it does not contain the "Action Based Clam".
- Validate the "Action Based Run" contains the "Action Based Claim" and it is no longer "Held".
|
Topics
• Finance
|
HL7 Messages for MPI Search
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Search
- Client Intake Wizard
- Placement Events by Agency/Program - People2
- Provider Sites by Program (Vacancy)
Scenario 1: SearchExternalMPIClient Message - HL7
Scenario 2: GetExternalMPIClient - HL7
|
Topics
• Third Party Solution
|
HL7 Demographic Messages
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Search
- Person Information [ADD]
- Gender Table
- Wizard
- WizardMPISearch
- New Client Personal Information [EDIT]
- Initial Enrollment for New Person [ADD]
- Managing Offices By Agency Operated
- Referral Reason Table
- Program Listing By Agency and Worker
- Placement Events by Agency/Program - People2
- Provider Sites by Program (Vacancy)
- Worker Role (to a client or in a workgroup) Table
- Ethnicity Table
- Race Subform
- Race Table
- Religion Table
- Marital History Sub Form Subform
- Marital Status Table
Scenario 1: MPI Search Includes HL7 Configurations
Scenario 2: Validate MPI Search Demographic Codes
Scenario 3: Validate MPI Search Demographic Codes
|
Topics
• Client
• Setup
• Third Party Solution
|
MPI Intake Wizard
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Search
- Person Information [ADD]
- Gender Table
- Wizard
- WizardMPISearch
- New Client Personal Information [EDIT]
- Initial Enrollment for New Person [ADD]
- Managing Offices By Agency Operated
- Referral Reason Table
- Program Listing By Agency and Worker
- Provider Sites by Program (Vacancy)
- Ethnicity Table
- Race Subform
- Race Table
- Religion Table
- Marital History Sub Form Subform
- Marital Status Table
- Placement Events by Agency/Program - People2
- Worker Role (to a client or in a workgroup) Table
Scenario 1: Validate MPI Search Demographic Codes
Scenario 2: Validate Adding Client With Existing MPI
Steps
- Navigate to "Client > Client Information > Personal Information > Demographics".
- Click "Select Client" button.
- Click "New".
- Select "Intake - New" from the New drop down list.
- In the New Client Wizard:
- Set the "Last Name", "First Name" input boxes to desired Client name.
- Set the Gender input box to desired gender code.
- Click "Proceed".
- Select desired Client name cell that does NOT have a date of birth.
- Click "Proceed".
- Verify the Client name has an existing MPI with a date of birth.
- Click "Proceed".
- Fill out remaining required fields.
- Click "Finish".
- Validate the Client name appears with the date of birth.
- Click "Select Client" button.
- Click "New".
- Select "Intake - New" from the New drop down list.
- Set the "Last Name", "First Name" input boxes to different desired Client name.
- Set the Gender input box to desired gender code.
- Click "Proceed".
- Check the "New Client" checkbox.
- Click "Proceed".
- Verify the Client name has an existing MPI with a date of birth.
- Click "Proceed".
- Fill out remaining required fields.
- Click "Finish".
- Validate the different Client name appears with the date of birth.
|
Topics
• Client
|
ECS-57741
Summary
|
Details
11.0.0075, 11.0.0050.02, 11.0.0025.05, 11.0.0000.09
Netsmart Identity Access Manager (NIAM)
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Staff Listing - Agency Employees (By People ID)
- Staff Information Form Set
- Staff with Security [EDIT]
Scenario 1: Validate "Use NIAM Authentication" Field
Specific Setup:
- Staff A has "Use NIAM Authentication" is set within "Agency > Staff & Security > Staff Information > Staff Profiles with Security".
- Staff B has access to Staff Profiles with Security.
Steps
- As Staff B, navigate to " Agency > Staff & Security > Staff Information > Staff Profiles with Security".
- Select Staff A.
- Uncheck "Use NIAM Authentication".
- Save and log out.
- Set "Username" as Staff A.
- Click the "Next" button.
- Validate the text "NIAM authentication is not enabled for user" displays.
- Log in as Staff B.
- Navigate to " Agency > Staff & Security > Staff Information > Staff Profiles with Security".
- Select Staff A, and check "Use NIAM Authentication".
- Save and logout.
- Log in as Staff A.
- Click the "Next" button.
- Verify new window appears and enter the password.
- Click the "Verify" button.
- Click on the person icon within the upper right section of the page and verify logged in staff is the appropriate NIAM staff (i.e. staff A).
|
Topics
• Agency
• Staff
|
RXA-5 Segment
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Search
- Historical Immunizations Registry - Public Health [ADD]
- Standard Codes - disease with Presumed Immunity
- Standard Codes - Immunization Form Entry
- Serological Evidence of Immunity
- Historical Immunizations Registry - Public Health [EDIT]
Scenario 1: RXA-5 HL7 Segment - Validate The Values Entered In The "Historical Immunizations Registry- Public Health" Form Allow Proper Segment Values
Steps
- Navigate to "Client > Client Information > Health Information > Immunizations - Public Health".
- Add a new record for "Historical Immunizations Registry - Public Health".
- Click on the "Disease with Presumed Immunity" and select a value.
- Validate the "Vaccine" field automatically populates to "998 no vaccine administered".
- Validate the "Vaccine" field is disabled.
- Validate the "Disease with Serological Evidence of Immunity" field is disabled.
- Select the "Disease with Presumed Immunity"
- On the look up table that displays select "Clear".
- Validate the three fields above become enabled.
- Validate the three fields above are cleared of any data.
- Select a value for the "Disease with Serological Evidence of Immunity"
- Validate the "Vaccine" field automatically populates to "998 no vaccine administered".
- Validate the "Vaccine" field is disabled.
- Validate the ""Disease with Presumed Immunity" is disabled.
- Select the ""Disease with Serological Evidence of Immunity"
- On the look up table that displays select "Clear".
- Validate the three fields above become enabled.
- Validate the three fields above are cleared of any data.
- Select the "Vaccine" field
- Select a "CVX Code" of "998".
- Validate the "Disease with Serological Evidence of Immunity" and "Disease with Presumed Immunity" are enabled.
- Select the "Disease with Presumed Immunity" and choose a value.
- Validate the "Vaccine" and the "Disease with Serological Evidence of Immunity" are disabled.
- Clear the value in the "Disease with Presumed Immunity".
- Valdiate the three fields above are cleared and enabled.
- Select the "Vaccine" field
- Select a "CVX Code" of "998".
- Validate the "Disease with Serological Evidence of Immunity" and "Disease with Presumed Immunity" are enabled.
- Select the "Disease with Serological Evidence of Immunity" and choose a value.
- Validate the "Vaccine" and the "Disease with Presumed Immunity" are disabled.
- Clear the value.
- Validate the three fields are enabled and blank.
- Fill in the "Vaccine" field using "998"
- Enter a value in one of the 2 look up tables.
- Fill in any of the other required fields.
- Save the record.
- Validate the messages are sent to the registry.
- Validate with the registry the value for the field is accurate.
- Repeat the above steps while editing an existing record.
- Validate the results are the same.
|
Topics
• CareConnect
• Immunizations
|
Import Forms Containing Test/Assessment(s)
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Interface Design Form Set
- FormDesigner
- Test Header Setup Lookup
- Sub Reports for Users - All
- Forms
- Form Families
- Columns Pick List NX
- All Look-up Tables Listing (filtered)
- NX Sub Form [ADD]
- NX Test [EDIT]
- FileUploadForm
Scenario 1: Form Designer: Validate Form Export Operations
Specific Setup:
The following User-Defined elements must be created in order to be added to a Form: Look-Up Table, Domain & Test, SubReport, and SubForm.
Steps
- Navigate to "Setup > User Tools > Interface Designer > Form Designer".
- Select desired "Form Family".
- Select desired System Form.
- Validate the "Export" option is not present under the "Actions" menu.
- Select "Copy" from the "Actions" menu.
- Set desired "Form Name" and "Form Code".
- Add desired "Form Elements".
- Fill out required fields for each "Form Elements".
- Click "Save".
- Validate saving was successful.
- Select "Export" from the "Actions" menu on the custom "Form".
- Validate a JSON file was created.
Scenario 2: Validate Importing an In Use Test Code Into Form Designer Displays Duplication Error
Specific Setup:
Available UDF form to export from Form Designer.
Steps
- Navigate to "Setup > User Tools > Interface Design > Form Designer".
- Select a Form Family.
- Export a UDF form.
- Navigate to "Setup > User Tools > Interface Design > Import Forms".
- Upload the exported file.
- Validate "Following Test code(s) in file FormExport.json already exists and in use. Please enter a new test code and try again..." error message.
- Validate "Form already exists in system:..." error message.
Scenario 3: Validate Ability To Import Forms With Test/Assessments
Specific Setup:
4 forms available to import: - Existing form with existing test/assessment that is not in use.
- Existing form with existing test/assessment that is in use.
- New form without a test/assessment.
- New form with a new test assessment.
Steps
- Navigate to "Setup > User Tools > Interface Design > Import Forms".
- Import each type form.
- For existing form with existing test/assessment that is not in use:
- Validate "Form already exists in system:..."
- For existing form with existing test/assessment that is in use:
- Validate "Following Test code(s) in file ... already exists and in use. Please enter a new test code and try again".
- Validate "Form already exists in system:..."
- For new form without a test/assessment:
- Validate successful upload of form.
- For new form with a new test assessment:
- Validate successful upload of form and test/assessment.
|
Topics
• Forms
• Setup
|
Social Security Number Length
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Search
- Immunization Query [ADD]
- Service Facilities Listing
Scenario 1: Send Social Security Number via CareFabric
|
Topics
• Third Party Solution
|
Medication Refills
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Agency [EDIT]
- Client Search
- Medication Complete Form [ADD]
- Facility Enrollment Client
- Drug Library Table
- Method Drug/Substances taken
- Drug Dispense Units
- Medication Complete Form [EDIT]
Scenario 1: "Refills Remaining" Calculations With "Auto-Decrement" in Medication Administration
Specific Setup:
- Staff login with Medication Dispensing credentials.
- Client enrolled with medications available to add.
- Staff access to "Agency Setup > Agency > Agency > Agency Information".
- Validate the checkbox for "Auto-decrement Refills Remaining" is set within "Agency Setup > Agency > Agency > Agency Information".
Steps
- Navigate to "Client > Client Information > Health Information > Medications".
- Select desired client.
- Click "Add New" to add a "Medications" event.
- Set the "Facility" field.
- Enter desired "Drug Name", "Start Date", "Take/sig".
- Set the "Quantity" field to "10", and set the desired "Dispense Units".
- Set the "Refills" input box to "10"
- Click "Save".
- Open the medication even that was just entered.
- Validate the "Quantity" is "10".
- Validate the "Refills Remaining" is disabled.
- Validate the "Quantity Remaining" is 10.
- Set the "Refills" to 10
- Set the "Refills Given to 15.
- Click on "Save"
- Validate alert fires, "Number of Refills should be greater than Refills Given. Number of Refills minus Number of Refills Given cannot be a negative number", and click the "OK" button.
- Set the "Refills Given" to "-15", and click the "Save" button.
- Validate alert fires, "Number of Refills should be greater than Refills Given. Number of Refills minus Number of Refills Given cannot be a negative number", and click the "OK" button.
- Set the "Refills" to "10".
- Set the "Refills Given" to "1".
- Click "Save".
- Click/Open the medication event that was just entered.
- Validate the "Refills is "10".
- Validate the "Refills Remaining" is disabled, and set to "9".
- Set the "Refills" to "0"
- Click "Save".
- Validate the alert fires, Number of Refills should be greater than Refills Given. Number of Refills minus Number of Refills Given cannot be a negative number", and click the "OK" button.
- Click the "Cancel" button.
- Validate the alert fires "Cancelling will discard all changes. Are you sure?", and click "OK".
Scenario 2: "Refills Remaining" Without "Auto-Decrement" in Medication Administration
Specific Setup:
- Staff login with Medication Dispensing credentials.
- Client enrolled with medications available to add.
- Access to "Agency Setup > Agency > Agency > Agency Information".
Steps
- Navigate to "Agency Setup > Agency > Agency > Agency Information".
- Uncheck the checkbox for "Auto-decrement Refills Remaining" in the "Agency-Specific Settings" and click "Save".
- Navigate to "Client > Client Information > Health Information > Medications".
- Select the desired client.
- Click "Add New" to add a "Medications" event.
- Validate the "Refills Remaining" field is enabled.
- Save the "Medications" event.
- Validate the "Refills Remaining" entry was saved.
Scenario 3: "Refills Remaining" Calculations With "Auto-Decrement" in Medication Administration
Specific Setup:
- Staff login with Medication Dispensing credentials.
- Client enrolled with medications available to add.
- Staff access to "Agency Setup > Agency > Agency > Agency Information".
- Validate the checkbox for "Auto-decrement Refills Remaining" is set within "Agency Setup > Agency > Agency > Agency Information".
Steps
- Navigate to "Client > Client Information > Health Information > Medications".
- Select desired client.
- Click "Add New" to add a "Medications" event.
- Set the "Facility" field.
- Enter desired "Drug Name", "Start Date", "Take/sig".
- Set the "Quantity" field to "10", and set the desired "Dispense Units".
- Set the "Refills" input box to "10"
- Click "Save".
- Open the medication even that was just entered.
- Validate the "Quantity" is "10".
- Validate the "Refills Remaining" is disabled.
- Validate the "Quantity Remaining" is 10.
- Set the "Refills" to 10
- Set the "Refills Given to 15.
- Click on "Save"
- Validate alert fires, "Number of Refills should be greater than Refills Given. Number of Refills minus Number of Refills Given cannot be a negative number", and click the "OK" button.
- Set the "Refills Given" to "-15", and click the "Save" button.
- Validate alert fires, "Number of Refills should be greater than Refills Given. Number of Refills minus Number of Refills Given cannot be a negative number", and click the "OK" button.
- Set the "Refills" to "10".
- Set the "Refills Given" to "1".
- Click "Save".
- Click/Open the medication event that was just entered.
- Validate the "Refills is "10".
- Validate the "Refills Remaining" is disabled, and set to "9".
- Set the "Refills" to "0"
- Click "Save".
- Validate the alert fires, Number of Refills should be greater than Refills Given. Number of Refills minus Number of Refills Given cannot be a negative number", and click the "OK" button.
- Click the "Cancel" button.
- Validate the alert fires "Cancelling will discard all changes. Are you sure?", and click "OK".
|
Topics
• Medications
|
ECS-57869
Summary
|
Details
11.0.0000.08, 11.0.0025.04, 11.0.0050.01, 11.0.0075
LA IBHIS Outpatient Episodes
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Program Setup - No Care Day/Respite [EDIT]
- Client Search
- Critical Information
- LA County Client Information [EDIT]
- Program Enrollment From Service Track [ADD]
- Program Listing By Agency and Worker
- Placement Events by Agency/Program - People2
- Provider Sites by Program (Vacancy)
- Worker Role (to a client or in a workgroup) Table
- Program Enrollment [Edit]
- Type of Admission
- Admission Necessity Code
- Yes No Unknown Table
- Level of Hold
- Conservator Court Status
- Source Of Admission
- AXIS IV (Psychosocial and Environmental Problems) [ADD]
- Diagnosis - (Axis IV problems)
- Diagnosis General - LA DMH SF Subform
- Diagnosis Search Service
- Priority Table
- Diagnosis Status
- Type of Diagnosis
- Staff - All (by Staff ID)
- Primary Diagnosis for a Person (by People_ID)
- Type Of Discharge
Scenario 1: LA IBHIS - Allow Outpatient Episodes To Be Opened With Multiple Legal Entities
Specific Setup:
- A client will exist that has all the needed information filled in to Admit into the LA IBHIS System.
- At least two outpatient programs assigned to the IBHIS code of "00543" in the myEvolv System. In this example they will be the "Outpatient Program1" and "Outpatient Program2".
- At least one outpatient program assigned to the IBHIS code of "01946" in the myEvolv System. In this example this will be "Outpatient Program3".
- At least one inpatient program assigned to the IBHIS code of "00543" in the myEvolv System. In this example it will be "Inpatient Program1".
- An enrollment record is created for an outpatient program, "Outpatient Program1". This client has not been admitted into the IBHIS System.
Steps
- Navigate to the " LA County Client Information" form.
- Validate the enrollment record in the precondition displays in the "IBHIS Related Program Enrollments on Record" SubReport. In this example "Outpatient Program1".
- Validate there is no episode attached to the record.
- Navigate to the IBHIS System.
- Admit the client.
- Validate an episode number is generated, In this example it will be "1".
- Refresh the myEvolv form.
- Validate the episode displays on the "IBHIS Related Program Enrollments on Record" SubReport. This will be on the "Outpatient Program1" record.
- Enroll the client into the third outpatient program, assigned to "01946". In this example this will be "Outpatient Program3".
- Admit the client into the IBHIS system.
- Validate this program has the next episode number assigned. In this example it will be "2".
- Refresh the myEvolv Form.
- Validate the sub report is updated with the correct episode number.
- Add a 3rd enrollment record to a third outpatient program, assigned to "00543". In this example it will be "Outpatient Prorgram2".
- Admit the client to this program in the "IBHIS" system.
- Validate the episode number is the same episode as in the first program. In this example it will be "1". In this example "Outpatient Program2" and "Outpatient Program1" will have the same episode number.
- Refresh the myEvolv Form.
- Validate the episode number is updated with the correct episode number.
- Add an inpatient program enrollment record to IBHIS Code "0543". In this example "Inpatient Program1".
- Admit the client to the IBHIS System.
- Validate the episode number is the next incremented value. In this example "3".
- Refresh the myEvolv Form.
- Validate the episode number is updated with the correct episode number.
Scenario 2: LA IBHIS - Validate Diagnosis Functions With Multiple Episodes
Specific Setup:
- A client will exist that is enrolled in at least three episodes, At least one inpatient episode and 1 outpatient episode will exist.
- One of the episodes will be for a program code of "00543" in the myEvolv system, the other "01946".
- The diagnosis will occur after the start dates of the episodes.
Steps
- Navigate to the "LA County Information" form.
- Validate the Diagnosis in the precondition exists on the form.
- Access the link for sending data to LA County.
- Select the first episode.
- Validate the "Evolv Diagnosis Information" displays the diagnosis from the precondition.
- Validate the "LA County Diagnosis Returned By GetClientDiagnosis" displays "No records to display".
- Select the "Create Client Diagnosis".
- Wait for the process to complete.
- Validate the "LA County Diagnosis Returned By GetClientDiagnosis" contains the same information as the "Evolv Diagnosis Information".
- Redo the above steps with each episode.
- Validate the information is updated in the "LA County Diagnosis Returned By GetClientDiagnosis" section.
Scenario 3: LA IBHIS - Validate Discharging and Enrolling Creates A New Episode
Specific Setup:
- A client exists that has multiple programs in the same episode.
- The same client has other episodes that exist for other programs.
Steps
- Navigate to the "Enrollment" form.
- Discharge the client from the 2 programs that share the same episode.
- Set the discharge date to an earlier date and time then the current date.
- Fill in the required fields for the IBHIS system, in myEvolv, that need to be filled in.
- Navigate to the IBHIS system.
- Select the episode and discharge the client.
- Validate the myEvolv system shows the two programs that shared the episode as discharged.
- Create a new enrollment record for a program that the client was discharged from.
- Set the enrollment date after the discharge date above.
- Validate the myEvolv SubForm shows no episode on that program.
- Enter the IBHIS system and admit the client.
- Validate the episode is the next incremental value on the list.
- Validate the episode number is not duplicated for this enrollment.
|
Topics
• LA IBHIS
|
MPI IDs Are Supported By CareConnect
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Agency [EDIT]
- Client Personal Information [VIEW]
- Client Search
- Person Information [ADD]
- Wizard
- WizardMPISearch
- New Client Personal Information [EDIT]
- Initial Enrollment for New Person [ADD]
- Referral Reason Table
- Program Listing By Agency and Worker
- Placement Events by Agency/Program - People2
- Provider Sites by Program (Vacancy)
- Client Personal Information [EDIT]
Scenario 1: MPI - Adding A Client Via Selecting An Existing MPI Client
Specific Setup:
- MPI is configured for the system by Netsmart.
- The "MPI ID" field is configured to be visible on the "Demographics" form by Netsmart.
- The client name being entered will display search results on the MPI Search form.
Steps
- Navigate to the "Client > Client Information > Personal Information > Demographics".
- Intake a new client.
- In the wizard, fill in the "Search" parameters for the client.
- Click the "Proceed" button.
- Click the "Create new record with information entered" option.
- Click the "Proceed" button.
- Validate the "MPI Search Results" tab displays.
- Select a client found in the "MPI search results" form.
- Note the "MPI Number".
- Finish out the intake process.
- Validate the demographics form displays the value in the "MPI ID" number field.
|
Topics
• CareConnect
• Client
|
Delete Group
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Select Group
- New Group [ADD]
- Agency/Programs Table
- Provider Sites by Agency/Program
- Support Group Classes Subform
- Schedules - Group Subform
- Group Management [EDIT]
- Group Header
- New Group
- Support Group Classes
- Schedules - Group
- Staff - Service Providers (Caseloads)
- Worker Assignment Groups (New Group)
- Workgroup Assignments Groups B2
- Groups > Group > Information > General Information
- Groups > Group > Information > Enrollments
- Wizard Process - Support Group Enrollment
- Groups > Group > Information > Worker Assignments
- Worker Assignment Groups
- Groups > Group > Information > Work Group Assignments
- Groups > Service Management > Service Management > Activities
- Activities - Group Activities
- Materials Provided
- Get Date Time
- Activities Short Form wo Acts(Read Only)
Scenario 1: Validate Group Can Be Created/Deleted
Steps
- Navigate to "Groups > Group > Information > General Information".
- Click Select Group.
- Click New button.
- Populate any required fields and save your new group.
- Click Delete
- Click OK when prompted if you really want to delete.
- Validate Group deletes.
- Attempt to search for deleted group.
- Validate "No Information Found.".
Scenario 2: Groups - Enter Group Activity via the Activities Listing in Groups Module
Specific Setup:
- Must have a scheduled group activity for test user.
- The group activity has "Has Single Note" setting checked under "Agency Setup > Event Setup > Groups & Case > Events Setup."
- At least three clients must be enrolled in the group for this scheduled date.
Steps
- Navigate to "Groups > Service Management > Service Management > Activities."
- Select your test group and appropriate Unit/Class.
- Click "Add New."
- Click "Add Event" and select your test group activity.
- Enter "Actual Date/Time."
- Click "Update."
- The group activities form will now open. Validate that the "Contact Type" is equal to the group activity you selected.
- Validate the "Actual Date/Time" matches what was just entered.
- Enter the "Duration."
- Validate the "Program Providing Service" is equal to the program associated with the group.
- Enter the "Facility Providing Service" field.
- Enter desired text in the "Progress Note" field.
- Validate that all expected clients are listed in the "Group Members" SubForm.
- Check the top "Present?" checkbox.
- Validate that "Present?" is now checked for all clients
- Validate that the "Start Time" matches the "Actual Time" for all clients.
- Validate that the "End Time" matches the "Actual Time" plus the "Duration" for all clients.
- Uncheck the "Present?" checkbox for one of the clients; validate that the "Start Time" and "End Time" are no longer populated.
- Uncheck the "Present?" checkbox for another client and then check the "No Show" checkbox.
- Save your group activity.
- Confirm that your newly entered group activity is visible in the Activities listing.
- Click on this group activity to open it.
- Validate that fields on the group activities form are populated as expected.
- Click "View Service" button for one of the clients marked present; validate information is present on the client form as expected.
- Click "View Service" button for the client marked as no-show; validate that the "No Show" checkbox is checked on the client form.
- Close client form and group activity form.
- If desired, delete test group activity created during this scenario.
|
Topics
• Groups
|
Address Overwrite on Claim Output
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Claim Output Ready
- Claim/Invoice Batch [VIEW]
- FinanceClaims
- Claim 2.0 [EDIT]
- Service Facilities Listing
- Service Facility [EDIT]
- Payor-Facility License Link Subform
- Payor-Facility License Link [EDIT]
- Claim Receivers Setup Form Set
- Receiver Information - All
- Receiver Information X12 Submissions [EDIT]
Scenario 1: Validate Payer License Address Overwrite On Service Facility Outputs On 837 Claim Output
Specific Setup:
Requires a billing run with at least one claim that is set to output "837P".
Steps
- Navigate to "Finance Setup > Agency Setup > Claim Receivers Setup > Receiver Setup X12".
- Select desired "Receiver".
- Check the flag "Output Service Facility in 837 as Service Facility".
- Save.
- Navigate to "Agency > Service Locations > Sites/Residentials > General Information".
- Select desired "Facility".
- Navigate to "Licensing Info".
- Add desired "Payer Specific Information" in the SubForm.
- Expand the SubForm for to add an "Overwrite Address".
- Validate "Do not Output as Rendering Provider" is not checked.
- Save.
- Navigate to "Finance > Claim/Invoice Processing > Batch Listing > Billing Batches Management".
- Select desired "Billing Run".
- Open the billing run to generate the output.
- Validate NM1*77 row contains desired "Facility".
- Validate N3 and N4 row contain the overwrite address.
- Navigate to "Agency > Service Locations > Sites/Residentials > General Information".
- Select desired "Facility".
- Navigate to "Licensing Info".
- Check the flag "Do not Output as Rendering Provider".
- Save.
- Repeat steps 12-14.
- Validate NM1*77 row contains desired "Facility".
- Validate N3 and N4 row contain the overwrite address.
|
Topics
• Agency
• Finance
|
Collection Type
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- AR Management
- Claims Maintenance NX Form Set
Scenario 1: Submission Balance and Expected Amount - Collection
Specific Setup:
- Collection Submitter and Receiver are configured.
- Collections Processing is configured within the Self Pay Plan.
- Collection billing batch must be marked as sent.
- User has access to Finance module.
Steps
- Navigate to "Finance > Remittance Processing > Remittance Application > AR Management".
- Click on the "View Filters" button.
- Within the Search Parameters, check off the "Show Claims Flagged for Collections" and "Include No Remit Claims" fields.
- Click on the "Search" button.
- On desired claim, click on the "Add Action" link.
- Within the "Action" field, select "Resubmit to CCU".
- Set the "Amount Type" to "Remaining Balance".
- Set the desired "Transaction Month", and click "Save".
- Navigate to "Finance > Claim Maintenance > Automatic > Submissions".
- Enter the claim for the resubmit that was just performed.
- For the collection submission, validate the "Claim Submission Balance" matches the same amount displayed within the "Amount Expected" field.
|
Topics
• Finance
|
"Inventory Site Transfer" Performance Improvement
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Inventory Site Transfer [ADD]
- Service Facilities Listing
- Transferable Inventory Item
- Inventory Container Transfer Subform
- Inventory Container Transfer [NEW]
- Inventory Site Transfer [VIEW]
- Inventory Container Transfer [ADD]
Scenario 1: Inventory Site Transfer - "Inventory Item" Field
Specific Setup:
- At least 2 facility sites exist that use inventory. They will be referred to as "Site1" and "Site 2".
- An Inventory Type exists with containers.
- A different Inventory Type then the one above.
- The user knows the medication item and the container to transfer.
Steps
- Navigate to "Agency > Inventory Management > Inventory Item Transfer > Inventory Site Transfer".
- Click the "Add New" button and select "Inventory Site Transfer".
- Set the desired "From Site" as "Site 1", and "To Site" as "Site 2".
- Validate the SubForm does not display any records when selecting the sites.
- Validate "Inventory Item" field contains a "star" in the label.
- Set the "Inventory Item" field to the value in the precondition.
- Validate the SubForm refreshes and displays the containers that match the medication type selected for the "From" facility.
- Add a check mark to the desired "Inventory Container" to transfer.
- Click the "Save" button.
- Validate the screen refreshes to the listing.
- Select the item and validate the fields are the same as the saved values. In this example the "From Site" will be "Site 1", the "To Site" will be "Site 2".
- Exit off this form.
- Do another Site Transfer with the same parameters from the start.
- Validate the transferred container does not display in the original "From Site", "Site 1".
- Set the "From Site" to "Site 2". Do not modify the other values.
- Validate the "Container" SubForm refreshes.
- Validate the container transferred displays.
- Change the "From Site" back to "Site 1".
- Validate the "Containers" SubForm refreshes.
- Validate the containers in "Site 1" display.
- Modify the "Inventory Item" to a different value.
- Validate the "Containers" SubForm refreshes.
- Validate the "Inventory Item" that was previous does not display on the "Containers" SubForm.
- Validate the containers that display belong to that "Site" and "Inventory Type". If no containers exist for that site, the SubForm will be blank.
|
Topics
• Inventory - Medications
|
UB-04 Output
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- AR Management
- Cash Receipts for Remittance
- Claims Submission For Remittance NX [EDIT]
- FinanceClaims
- Claim/Invoice Batch [VIEW]
- Claim Output Ready
- Claim Output
Scenario 1: Validate Primary Payor Information Displays On UB-04 After Waterfall
Specific Setup:
- Requires a claim that can be waterfalled to "Secondary Payer".
- Receiver on "Secondary Payer" should be set up to output "UB-04".
Steps
- Navigate to "Finance > Remittance Processing > Remittance Application > AR Management".
- Select desired remittance.
- Set parameters to search for desired claim.
- Add desired "Payment".
- Click "Add Action".
- Select "Resubmit To Other/Waterfall".
- Save.
- Wait for billing to run.
- Open the batch to the new submission.
- Click on "Create Output".
- Open the "UB-04" output.
- Validate it contains desired payment and "Primary Payer" information.
|
Topics
• Finance
|
Clinic Scheduled Events and On Demand Billing
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Checks for a Clients Self Pay in Front Desk Entry [EDIT]
- FrontDeskCheckIn
- FinanceClaims
- Checks for a Clients Self Pay in Front Desk Entry [ADD]
- AR Management
- Client Search
- Client Service Entry
- Client Related Task - New [ADD]
- Immunizations - Public Health [ADD]
- Vaccines In Inventory
- Vaccine Funding Source
- VFC Eligibility
- Inventory Container By Vaccine
- Med Administration - Public Health [ADD]
- Facility Enrollment Client
- Medications In Inventory
- Inventory Container by Drug
- Drug Dispense Units
- Service and Attendance Facilities Listing
- All People Agency
- FrontDeskCalendar
- Front Desk Calendar Appointment [ADD]
- Front Desk People Search
Scenario 1: Validate On Demand Billing With Clinic Appointments
Specific Setup:
- Requires a client with a "Self Pay Benefit Assignment".
- Requires a service that set up in "Self Pay" and flagged for "On Demand Billing".
- Requires a "Facility" to be set up with a "Clinic Schedule".
Steps
- Navigate to "Taskbar > Attendance Check In/Out > Check In/Out > Front Desk NX".
- Click on "View Calendar".
- Click "Clinic" tab.
- Check off desired "Clinic".
- Right click on desired "Appointment Slot" row to schedule an appointment.
- Fill in required fields for the scheduled event.
- Save.
- Close the calendar.
- Click "Refresh".
- Validate the event is listed.
- Click "Check In".
- Click "Complete Task".
- Fill in required fields to complete the event.
- Save.
- Validate the event moves to the "In Progress" column.
- Validate "Run On Demand Billing" button is visible.
- Click the "Run On Demand Billing" button.
- Wait for billing to run.
- Click on "Review Claims".
- Validate the desired claim was generated.
|
Topics
• Finance
• Front Desk
|
Immunization History Records PID-3 ID Values
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Search
- Historical Immunizations Registry - Public Health [EDIT]
- Standard Codes - disease with Presumed Immunity
- Historical Immunizations Registry - Public Health [ADD]
- Standard Codes - Immunization Form Entry
- Vaccine Lookup
Scenario 1: UpdateVaccination - PID 3 - Validate ID Is Agency ID Of Client
Specific Setup:
- The system was configured by Netsmart to the newest method of sending SDK file types.
- The Agency ID was configured by Netsmart to be the PID 3 Identifier.
Steps
- Navigate to "Client > Client Information > Health Information > Immunizations - Public Health".
- Select the event "Historical Immunizations Registry - Public Health".
- Fill the form in with a vaccine used.
- Do not fill in the "Disease With Presumed Immunity" or the "Disease with Seriological Evidence of Immunity".
- Set the "Patient Registry Status" to "Active".
- Set the "Immunization Registry Status" to "Ready for Submission".
- Set the "History" to "New Immunization record".
- Save the form.
- The message will be transmitted.
- Have the third party validate the HL7 file, id in segment PID 3.1 is the "Agency Id" of the client.
|
Topics
• CareConnect
• Immunizations
|
ECS-58253
Summary
|
Details
11.0.0025.04, 11.0.0050.01, 11.0.0075, 11.0.0000.09
270 Eligibility Files
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Claim Receivers Setup Form Set
- Receiver Information - All
- Receiver Information 270-271 Setup [EDIT]
- EligibilityManager
- 270 Output Ready
- 270 Output File
- Billing Batches Management
- Billing Batch Claims Review
- Finance > Claim/Invoice Processing > Batch Listing > Billing Batches Management
- Finance > Imports/Exports > Exports > Eligibility Requests (270)
Scenario 1: Validate 270 Output File Honors "Output 270 in 5010 format" Option
Specific Setup:
Available Claim receiver to edit under "Finance Setup > Agency Setup > Claim Receivers Setup > Receiver Setup 270/271".
Steps
- Navigate to "Finance Setup > Agency Setup > Claim Receivers Setup > Receiver Setup 270/271".
- Select a receiver and enable:
- Break File on Max Clients
- Break File on new Provider
- Output 270 in 5010 format.
- Click Save.
- Navigate to "Finance > Imports/Exports > Exports > Eligibility Requests (270)".
- Find/create request 270 file with receiver from step 2.
- Select "Generate Output File".
- Validate the output zip has multiple files and they all have "5010" present in output file.
- Validate "4010" is not present in output file.
- Navigate to "Finance Setup > Agency Setup > Claim Receivers Setup > Receiver Setup 270/271".
- Select same receiver and disable:
- Break File on Max Clients
- Break File on new Provider
- Output 270 in 5010 format.
- Click Save.
- Navigate to Finance > Imports/Exports > Exports > Eligibility Requests (270)
- Select "Generate Output File" for the same 270.
- Validate the output has single file and has "4010" present in file.
Scenario 2: Send 270 to RevConnect From Billing Run
Specific Setup:
Claim receiver "Output 270 in 5010 format" enabled under "Finance Setup > Agency Setup > Claim Receivers Setup > Receiver Setup 270/271".
Steps
- Navigate to "Finance > Claim/Invoice Processing > Batch Listing > Billing Batches Management".
- Filter for desired Receiver.
- Take note of "Run Description".
- Click Actions > Request Eligibility (270).
- Download the file.
- Validate the output has single file and has "5010" in the code.
- Validate the output does not have "4010" in the code.
- Click Send to RevConnect.
- Validate "270 submitted to SFTP" message.
- Click the Claims link.
- Click "Request Eligibility (270)".
- Download the file.
- Validate the output has single file and has "5010" in the code.
- Validate the output does not have "4010" in the code.
- Click Send to RevConnect.
- Validate "270 submitted to SFTP" message.
- Navigate to "Finance > Imports/Exports > Exports > Eligibility Requests (270)".
- Validate Description cell matches step 3.
- Validate Status "File Sent".
|
Topics
• Finance
• Finance Setup
|
ECS-58276
Summary
|
Details
11.0.0075, 11.0.0050.02, 11.0.0025.05, 11.0.0000.09
835 Remittance Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- FinanceImportListing
- Finance File Import
- Report: Claim Remittance Report
- Claims Maintenance NX Form Set
- Claim Submission 2.0 [EDIT]
- Claim Remittance Transactions Subform
- Report: Claim Details Report
- Claims Maintenance Form Set
- AR Management
- Cash Receipts for Remittance
- ActionsView
Scenario 1: Validate 835 Payment Withdrawal and Full Payment
Specific Setup:
- Requires an "835 Remittance" with valid claims.
Steps
- Navigate to "Finance > Imports/Exports > Imports > Remittance Imports".
- Click "Upload File" button.
- Select "Upload 835".
- Select desired "835 Remittance" file.
- Set "Deposit Date".
- Click "Upload" button.
- Wait for "835 File" to process.
- Click "Actions" button.
- Select "Remittance Report".
- Click on desired "Claim" link.
- Click "Submissions" tab.
- Validate the "Claim Remittance Status" contains "Paid".
- Validate the "Claim Submission Balance" contains $0.00".
- Repeat steps 2-6 for same file.
- Validate "This remittance has already been processed." message.
Scenario 2: Validate Remittance With Multiple Payments On Same Service Line
Specific Setup:
- Requires a "Multi Service Line" claim.
- Requires a "Remittance" with multiple payments for one of the service lines.
Steps
- Navigate to "Finance > Imports/Exports > Imports > Remittance Imports".
- Click "Upload File" and select "Upload 835".
- Select desired remittance file.
- Click "Upload".
- Validate file uploaded.
- Navigate to "Finance > Claim Maintenance > Automatic > Submissions".
- Select desired claim from remittance.
- Open the submission.
- Validate the "Submission" contains both payment statuses from the remittance.
Scenario 3: Validate Remittance Upload With CAS Info In Service Line
Specific Setup:
An 835 file that includes CAS information at service line level for single service line claim(s).
Steps
- Navigate to "Finance > Imports/Exports > Imports > Remittance Imports".
- Upload 835 file.
- Validate that the CAS information has been applied to the claim.
|
Topics
• Finance
|
Routes Including Immediate Supervisor Drop-Down
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Search
- Client Service Entry
Scenario 1: Validate Immediate Supervisor Drop Down On Basic Approval Route
Specific Setup:
- Requires an event that is set up with the route "Basic Approval".
- Scenario works with "Original Routing" setup.
Steps
- Navigate to "Client > Case Management > Service Management > Service Entry".
- Select desired client.
- Click "Add Event" and select desired event.
- Fill in required fields.
- Save.
- Re-open the event.
- Click "Routing" button to begin route.
- Under "Submit to Supervisor" enter the desired supervisor.
- Validate the desired staff appears.
- Select the supervisor.
- Enter a note.
- Click "Submit to Supervisor".
- Save.
- Login as the "Supervisor".
- Navigate to "Client > Case Management > Service Management > Service Entry".
- Select the client.
- Open the event.
- Click the "Routing" button.
- Validate route is assigned to the "Supervisor".
- Approve the route.
|
Topics
• Client
|
835 Import
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- FinanceImportListing
- Finance File Import
- Report: Claim Remittance Report
- Report: Claim Details Report
- Claims Maintenance NX Form Set
Scenario 1: Validate Remittance Upload With CAS Info In Service Line
Specific Setup:
An 835 file that includes CAS information at service line level for single service line claim(s).
Steps
- Navigate to "Finance > Imports/Exports > Imports > Remittance Imports".
- Upload 835 file.
- Validate that the CAS information has been applied to the claim.
|
Topics
• Finance
|
Medication Issued Orders
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Agency [EDIT]
- Client Search
- Medication Complete Form [ADD]
- Facility Enrollment Client
- Drug Library Table
- Method Drug/Substances taken
- Drug Dispense Units
- Medication Complete Form [EDIT]
- OrderConnect Medication Form [EDIT]
- PH Labs and Medication Form Set
- Medication - PH [ADD]
- Programs by Services & Enrollment
- People Medications - Active Medications
- Inventory Container by Drug
Scenario 1: "Refills Remaining" Calculations With "Auto-Decrement" in Medication Administration
Specific Setup:
- Staff login with Medication Dispensing credentials.
- Client enrolled with medications available to add.
- Staff access to "Agency Setup > Agency > Agency > Agency Information".
- Validate the checkbox for "Auto-decrement Refills Remaining" is set within "Agency Setup > Agency > Agency > Agency Information".
Steps
- Navigate to "Client > Client Information > Health Information > Medications".
- Select desired client.
- Click "Add New" to add a "Medications" event.
- Set the "Facility" field.
- Enter desired "Drug Name", "Start Date", "Take/sig".
- Set the "Quantity" field to "10", and set the desired "Dispense Units".
- Set the "Refills" input box to "10"
- Click "Save".
- Open the medication even that was just entered.
- Validate the "Quantity" is "10".
- Validate the "Refills Remaining" is disabled.
- Validate the "Quantity Remaining" is 10.
- Set the "Refills" to 10
- Set the "Refills Given to 15.
- Click on "Save"
- Validate alert fires, "Number of Refills should be greater than Refills Given. Number of Refills minus Number of Refills Given cannot be a negative number", and click the "OK" button.
- Set the "Refills Given" to "-15", and click the "Save" button.
- Validate alert fires, "Number of Refills should be greater than Refills Given. Number of Refills minus Number of Refills Given cannot be a negative number", and click the "OK" button.
- Set the "Refills" to "10".
- Set the "Refills Given" to "1".
- Click "Save".
- Click/Open the medication event that was just entered.
- Validate the "Refills is "10".
- Validate the "Refills Remaining" is disabled, and set to "9".
- Set the "Refills" to "0"
- Click "Save".
- Validate the alert fires, Number of Refills should be greater than Refills Given. Number of Refills minus Number of Refills Given cannot be a negative number", and click the "OK" button.
- Click the "Cancel" button.
- Validate the alert fires "Cancelling will discard all changes. Are you sure?", and click "OK".
Scenario 2: Validate Medication Administration Is Preventing Multiple Dispenses for Orders With 0 Refills
Specific Setup:
- The "Auto-decrement Refills Remaining" setting in Agency Settings must be set to True.
- You will need an OrderConnect medication record with one refill created for a client, and that client should be enrolled and ready to enter medication administration records.
Steps
- Navigate to "Client > Public Health > Labs and Medication > Medication Administered/Issued".
- Add a "Medication Issued" record.
- Confirm that the Dose/Quantity field is read-only.
- Choose the medication created from setup.
- Fill remaining form and Save the record.
- Navigate to "Client > Public Health > Labs and Medication > Medication History".
- Open the OrderConnect medication record created in the setup.
- Confirm that the "Refills Remaining" field has 1 remaining.
- Navigate back to "Client > Public Health > Labs and Medication > Medication Administered/Issued".
- Create another "Medication Issued" record repeating steps 2-5.
- Navigate to "Client > Public Health > Labs and Medication > Medication History".
- Open the OrderConnect medication record created in the setup.
- Confirm that the Refills Remaining field has been decremented by one.
- Navigate back to "Client > Public Health > Labs and Medication > Medication Administered/Issued".
- Create another "Medication Issued" record repeating steps 2-5.
- Try to save the record, and confirm that saving is disallowed, with the message "Medication cannot be administered as there are not enough refills remaining." returned.
|
Topics
• Agency Setup
• Client
|