ECS-53343
Summary
|
Details
11.0.0100, 11.0.0025.07, 11.0.0050.04, 11.0.0075.01
Closed Inventory Container Utility
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Open Closed Containers Form Set
- Closed Inventory Container [EDIT]
- UpdateHistory
- Alerts - Send [ADD]
- Print Preview
- Closed Inventory Containers
- Inventory Container Management Form Set
- Inventory Container
- Container Transaction [ADD]
Scenario 1: Open Closed Container - Opening A Container To Be Used With the "Closed Inventory Container"
Specific Setup:
- A container that is in the "Empty" status for an "Immunization" item.
- A container that is in the "Empty" status for a "Medication" item.
- A container that is in the "Empty" status for a "Supply" item.
Steps
- Navigate to "Agency > Inventory Management > Open Closed Containers > Closed Inventory Container".
- Click the "Select Container" button.
- Search for the "Empty" container in the precondition.
- Select the container.
- Check the "Is Open" check box.
- Click the "Save" button.
- Validate the form refreshes and the container displays.
- Select the "Select Container" button.
- Validate the container does not display in the look up table.
- Navigate to "Agency > Inventory Management > Container Management > Container Transactions".
- Click the "Inventory Container" button.
- Search for the container that just had the status changed.
- Validate the "Status" is "Active".
- Select the container.
- Add an adjustment to make the value greater than zero.
- Search for the container and validate the remaining amount in the look up table indicates the valued entered.
|
Topics
• Inventory - Immunizations
• Inventory - Medications
• Inventory - Supplies
|
DFT Outbound IN1 Segment
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- HL7 Outbound v2.0 Form Set
- HL7 Document Types Setup Link
- HL7 Outbound [ADD]
- HL7 Outbound [EDIT]
Scenario 1: DFT IN1 Segment Outbound - Exporting Generated Claims - Not Self Pay
Specific Setup:
- The system is configured to send data to third parties via HL7 formats.
- Set the event up on the Program level to have "Allow HL7 Outbound" flag is checked.
- A Client will exist that will be used to create a service.
- That service has a claim generated and the values are known.
- The "HL7 Outbound Setup" is created via the Agency Setup > Other Setups > HL7 Outbound Setup > HL7 Outbound Setup.
- This will transmit data to a third party application.
- The client is not a self pay client.
Steps
- Navigate to "State Reporting > Files Processing/Generation > HL7 Outbound v2.0 > HL7 Outbound v2.0".
- Click "Select HL7Outbound" button, and select the "Document Type" configured for this process.
- Add a new record.
- Check the "Check Off to Process" check box.
- Save.
- Processing will start.
- When this completes, the data will be sent to the third party application.
- Have the data reviewed to determine it is accurate.
Scenario 2: IN1 Segment Outbound - Exporting Generated Claims - Self Pay
Specific Setup:
- The system is configured to send data to third parties via HL7 formats.
- Set the event up on the Program level to have "Allow HL7 Outbound" flag is checked.
- A Client will exist that will be used to create a service.
- The client has a Self Pay Benefit Assignment only.
- That service has a claim generated and the values are known.
- The "HL7 Outbound Setup" is created via the Agency Setup > Other Setups > HL7 Outbound Setup > HL7 Outbound Setup.
- This will transmit data to a third party application.
Steps
- Navigate to "State Reporting > Files Processing/Generation > HL7 Outbound v2.0 > HL7 Outbound v2.0".
- Click "Select HL7Outbound" button, and select the "Document Type" configured for this process.
- Add a new record.
- Check the "Check Off to Process" check box.
- Save.
- Processing will start.
- When this completes, the data will be sent to the third party application.
- Have the data reviewed to determine it is accurate.
|
Topics
• CareConnect
• State Reporting
|
HL7 Standard Codes for Religion
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Standard Codes Maintenance Form Set
- Value Set
- Value Sets Maintenance [EDIT]
- Code System Maintenance [EDIT]
- Client Personal Information [EDIT]
- Religion Table
- Standard Codes [EDIT]
- Tables Maintenance - Simple Form Set
- Look-up Tables Maintenance - Simple
- GenericBrowse
Scenario 1: Validate RELIGION (HL7) Look Up Table
Scenario 2: HL7 Religion ADT PID-17 Segment
|
Topics
• Setup
• Third Party Solution
|
HL7 Outbound DFT Segment PR1-3.3 "CPT" Code Value
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- HL7 Outbound v2.0 Form Set
- HL7 Document Types Setup Link
- HL7 Outbound [ADD]
- HL7 Outbound [EDIT]
Scenario 1: DFT Outbound PR1-3.3 - Validate Code Value Is "CPT"
|
Topics
• CareConnect
|
FIS - Void Payments
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- FIS Billing Solutions - Payment Entry
- FIS Billing Solutions - Payment Review
- FIS Billing Solutions - Receipt
- Cash Received - Credit Card [EDIT]
- Credit Card Payments Form Set
- Credit Card Devices - All
- Cash Received - Credit Card [ADD]
- All Client Guarantors - Self Pay
- All Clients By Guarantor - Self Pay
- Credit Card Brand
Scenario 1: FIS - Validate Void Transactions
Steps
- Navigate to "Finance > Remittance Processing > Credit Card Payments > Payments".
- Click the "Add New" button.
- Select "Cash Received - Credit Card" from the "Add New" drop down list.
- Fill out required fields.
- Click Save.
- After clicking save, it will re-direct you to the "FIS Billing Solutions" page.
- Fill out required fields.
- Click "Process Payment".
- Verify the payment has been processed and click "Finish".
- Close out of the webpage.
- Click the "Refresh" button.
- Verify the FIS payment is listed.
- Click on the payment.
- Click the "Void Payment" checkbox.
- Click "Save".
- Verify the payment void action has been saved.
|
Topics
• Finance
|
Staff ID Number in HL7 messages
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Immunizations - Public Health [ADD]
- Program Listing by Agency and Service Event
- Service Facilities Listing
- Vaccines In Inventory
- Staff Distinct Listing by Agency (Staff ID)
- Vaccine Funding Source
- VFC Eligibility
- Inventory Container By Vaccine
Scenario 1: HL7 Outbound - Validate Sending Staff ID Numbers
|
Topics
• Third Party Solution
|
Formatting The "HIV Diagnosis Date", Segment "ZHI-3"
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Header
- Select Client
- PH MV Sexual History [EDIT]
- PH MV HIV Risk Assessment [EDIT]
- Client Personal Information [EDIT]
- GenericBrowse
Scenario 1: HL7 Outbound - Sending HIV Information In ClientEventUpdate Message
|
Topics
• CareConnect
|
Insurance Payload Messages Integrate OrderConnect
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Self Pay [ADD]
- Relationship - Family Table
- Self Pay [Edit]
Scenario 1: OrderConnect - Validate Payor Information Messages
|
Topics
• OrderConnect
|
ECS-57321
Summary
|
Details
11.0.0100, 11.0.0025.07, 11.0.0050.04, 11.0.0075.01
Sliding Fee And Calculate Rate
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Yearly Income (SF) myInsight Subform
- Income Source Table
- Sliding Fee Eligibility [EDIT]
- FrontDeskCheckIn
- FinanceClaims
- AR Management
- Cash Receipts for Remittance
- Claims Submission For Remittance NX [EDIT]
- Claim/Invoice Batch [VIEW]
- Claim Output Ready
- Claim 2.0 [EDIT]
Scenario 1: Validate Calculate Rate Honors Sliding Fee After Partial Payment
Specific Setup:
- Requires a client with a "Self Pay Benefit Assignment" that is flagged to "Use Automated Sliding Fee Scale".
- Self Pay should be set up with a rate to bill the service.
- Client should have "Sliding Fee Eligibility" set up.
- Sliding Fee Scale should be set up for the program client is enrolled in.
Steps
- Navigate to "Finance > Remittance Processing > Remittance Application > AR Management".
- Select desired remittance.
- Set parameters to search for desired claim.
- Add a partial payment to the claim.
- Click "Add Action".
- Select "Resubmit to Other/Waterfall".
- Validate the "Submit To" field is the "Self Pay Benefit Assignment".
- Under "Amount Type" select "Calculate Rate".
- Validate "Calculate Rate" return the desired "Amount" based of the clients "Sliding Fee" setup.
- Save.
- Wait for billing to run.
- Open the second submission.
- Validate it was generated for the desired amount.
|
Topics
• Finance
|
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:
- Historical Immunizations Registry - Public Health [EDIT]
- Standard Codes - disease with Presumed Immunity
- Historical Immunizations Registry - Public Health [ADD]
- Program by Client's Service Track and Service
- Provider Sites by Program
- 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 Serological 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-59266
Summary
|
Details
11.0.0100, 11.0.0025.07, 11.0.0050.04, 11.0.0075.01
CareConnect HL7 PID 5.7
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Client Personal Information [EDIT]
- Name Type (HL7)
- Agency [EDIT]
- Historical Immunizations Registry - Public Health [EDIT]
Scenario 1: Validate ImmunizationUpdate useCode Field and PID-5.7 CareConnect HL7 Payload Messages
|
Topics
• Client
|