Testing Unmatched Results in Junction Sandbox
Last updated: November 5, 2026
Overview

The Unmatched Results workflow allows your team to review lab results that Junction could not automatically match to a single order with complete confidence.
Instead of coordinating with Junction over Slack, your team reviews the case directly in the Junction dashboard, chooses the appropriate resolution, or sends the case to Junction for review when additional investigation is needed. Starting December 1, this is how all unmatched results are resolved.
This guide covers testing the dashboard experience in Sandbox, so your team can get comfortable with the workflow before using it in Production.
Building against the API instead? See the Unmatched Results Integration Guide for webhooks, testing APIs, and endpoint documentation.
Before you begin
To test this feature, your Sandbox team must have Unmatched Results enabled. Contact your Customer Success Manager to enable it and to request representative test cases for your team.
Sandbox testing does not affect your production environment.
Accessing Unmatched Results

Sign in to your Junction account.
Make sure you are in Sandbox.
Select Unmatched Results from the left navigation.
You’ll see these queues:
Needs Action — results awaiting a decision from your team.
Critical — results that contain a critical value. These should be reviewed first.
Junction Reviewing — results your team has escalated to Junction for investigation.
What to test

We recommend reviewing several different unmatched-result scenarios.
For each case:
Review why the result requires attention.
Review the suggested patient and the suggested orders (up to three).
If the right order isn't suggested, try entering an order ID directly.
Where patient details differ between the result and the order, choose which details are correct.
Review the recommended resolution.
Complete one of the available actions.
We also recommend testing:
a critical result, to see how it's flagged and what's required to reject it
bulk rejection, by selecting several non-critical cases at once
accepting a result for a cancelled or completed order, then opening the new order to see how it's linked to the original under the same order transaction
Available actions
Depending on the type of unmatched result, you may be able to:
Accept the recommended resolution

Use this when you’re confident the suggested resolution is correct.
Depending on the case, Junction may:
attach the result to an existing order,
create a replacement order,
recreate an order, or
cancel an incorrect order as part of resolving the case.
When a new order is created, it's linked to the original order under the same order transaction — the original order is not reactivated. See Understanding Order Transactions.
Reject the result

Reject the result if it does not belong to one of your patients or should not be attached to an order. You can reject several cases at once from the queue. Critical results must be rejected individually, with a reason.
Send to Junction


If additional investigation is needed, send the case to Junction with a note explaining what your team found.
The case will move into Junction Reviewing, where you’ll be able to review your submitted notes while the investigation is in progress.
Notifications
You can be notified by email when results need review. Nothing is sent until someone configures a recipient address — if no email is set for your team or organization, you won't receive anything.


Setting up email notifications
Go to Organization config → Notifications (Org Admins) or Team config → Notifications (Team Admins).
Confirm the environment picker is set to Sandbox. Sandbox and Production preferences are configured separately — setting one does not set the other.
Select the Unmatched Results notification type and enter the email address that should receive notifications.
Setting a recipient at the org level gives you one email covering every team in your organization, so you don't need to switch into each team to check for outstanding items. Team-level recipients receive only that team's results.
Remember to set up Production recipients too before December 1.
For the daily digest, critical alerts, reason labels, and webhooks, see Unmatched Results Notifications.
Known limitations
Sandbox test data is retained and is not automatically cleaned up.
Sending feedback
We'd love to hear how testing goes — especially anything that was unclear, anything that made you leave the workflow to investigate elsewhere, or any information you needed to confidently choose a resolution.
Share feedback through your shared Slack channel or your Customer Success Manager. When possible, include:
whether you’re reporting a bug or product feedback
the unmatched result you were reviewing
what you expected to happen
what actually happened
screenshots or screen recordings, when helpful
If reporting a bug, please also include any error messages you encountered.