The In-Network – Inbound tab on the Network Dashboard is where you, as a provider (CSP), manage test requests submitted by requesters (TPAs) who are using their own lab, MRO, and supplies. These are considered in-network tests.
In this workflow, you are responsible for collecting the specimen and ensuring it is processed according to the requester’s instructions. The requester’s accounts and vendors handle all downstream steps such as laboratory analysis and MRO review.
Tab Structure
This tab contains three tables that support each stage of your involvement in an in-network test request:
1. In-Network Service Requests Received
This section shows pending test requests that have been sent to you but are awaiting your approval.
- Review test request details, including requested date, time, and location
- Accept or decline based on your availability and capabilities
- Initiate communication with the requester if further clarification is needed
2. In-Network Service Requests
This table includes all approved requests you are currently fulfilling.
- Coordinate and perform the collection at the requested time
- Ensure the sample is properly packaged and shipped to the requester’s designated lab
- Follow the requester’s supply and documentation protocols
3. Networked Collection Sites
This section lists all your collection sites that have been added to other requester networks.
- Track which requesters have you listed in their in-network site lists
- Manage relationships and understand your role within their testing workflows
- Maintain accurate contact and service information to remain discoverable
Key Considerations
- Use the requester’s lab and MRO accounts and follow their chain of custody procedures
- Make sure to use the supplies provided or approved by the requester
- Once the specimen is collected and sent, your responsibility for the test is complete
- Prompt collection and shipping ensure faster turnaround and better network performance ratings
This tab allows you to efficiently manage and fulfill in-network service requests while maintaining alignment with requester-specific testing processes and expectations.