Resolving Unmatched Results in the Dashboard

Last updated: November 17, 2026

Unmatched Results becomes available to all lab testing customers on December 1, 2026. From December 1, Junction will no longer resolve unmatched results in Slack. They'll appear only in your dashboard and email notifications. Want access sooner? Contact your Customer Success Manager.

Overview

When a lab sends Junction a result, we match it to the order it belongs to before it reaches your patient's record. Most results match automatically. A small number can't be matched with confidence — the requisition was already used, the patient attended a different lab, or the details on the result don't line up with the order.

These results appear in Unmatched Results in the Junction dashboard, where your team reviews the case and decides what should happen. Until someone resolves the case, the result is not attached to an order and does not reach the patient's record.

Previously, Junction resolved these cases and contacted you over Slack when we needed input. Your team now owns the decision directly, which removes the back-and-forth and gets results released faster. From December 1, the dashboard is the standard way to resolve unmatched results for all customers.

Building against the API instead? See the Unmatched Results Integration Guide for webhooks, endpoints, and payloads.

Before December 1

  • Store the order_transaction_id with every order. Resolving a result for a cancelled or completed order creates a replacement order with a new order ID, linked to the original by an order transaction. If your system looks up results by the original order ID only, plan the update now. See Understanding Order Transactions.

  • Set a notification recipient in Organization or Team config. Nothing is sent until a recipient is set. See Unmatched Results Notifications.

  • Decide who will work the queue. Review critical results as soon as they arrive, and clear other cases within 0-3 days.

Accessing Unmatched Results

  1. Sign in at app.junction.com.

  2. Confirm you're in the correct environment and team.

  3. Select Unmatched Results from the left navigation.

You'll see these queues:

  • Needs Action — cases waiting on a decision from your team.

  • Critical — cases where the result contains a critical value. Work these first.

  • Junction Reviewing — cases your team has sent to Junction for investigation.

A badge on the navigation item shows how many cases are waiting.

Critical results

Unmatched results that contain critical values are flagged in the dashboard and grouped in a dedicated critical queue. Each critical case shows the markers that triggered the flag, with their values and reference ranges.

Because a patient can't see a critical result until the case is resolved, review critical cases as soon as they arrive. Critical results are also sent to your notification recipients immediately rather than in the daily digest.

Rejecting a critical result requires you to record a reason.

Reviewing a case

Each case shows the incoming result, the patient details the lab sent, the markers included, and the candidate patients and orders Junction found (when applicable). Where more than one order could be a match, Junction shows up to three suggested orders so you can pick the right one.

Work through a case in this order:

  1. Read the reason. It tells you what blocked automatic matching.

  2. Check the patient. Confirm the patient on the result is a patient of yours.

  3. Check the suggested orders. Compare the markers, lab, and collection date against each order. If the correct order isn't suggested, you can enter its order ID directly — for example, an order your team created after the original was cancelled.

  4. Resolve any demographic differences. Where the patient details on the result differ from the order (for example, a misspelled name or a different date of birth), the differences are highlighted. Choose whether to keep the order's details or update them to match the result.

  5. Review the recommended resolution and choose an action.

Available actions

The actions offered vary by case. If an action isn't shown, it isn't valid for that case.

Accept

Accept applies the resolution Junction recommends for the case. The recommended resolution is shown on the case before you confirm, and it depends on what blocked automatic matching:

Recommended resolution

When you'll see it

What happens when you accept

Attach to existing order

The result belongs to an order that can still receive it — for example, after you've selected the correct suggested order or resolved a demographic mismatch

The result is attached to that order and released to the patient's record

Create a new order

The test was performed without a matching requisition — for example, the patient is found but no order carries this sample ID

Junction creates a new order for the patient and attaches the result to it

Create a replacement order

The matching order can no longer receive the result — for example, it was cancelled, already completed, or written for a different lab

Junction creates a replacement order to carry the result. The original order is not reactivated, and both orders are linked under the same order transaction

Use Accept when you're confident the recommended resolution is correct for the patient and order shown. If it isn't, choose a different suggested order, enter the correct order ID, or send the case to Junction.

Accepting may produce a new order ID. When Junction creates a new or replacement order, it's grouped with any related orders under a single order transaction, so the full history stays connected. If you store order IDs in your own system, keep both — don't overwrite the original. Even better: store the order_transaction_id (see Understanding Order Transactions).

Redraws and results for orders that were already completed or cancelled: use Accept to create the replacement order. Don't ask Junction to release the result to the original order — orders are not reactivated, and the replacement order keeps a clear audit trail.

Reject

Use Reject when the result doesn't belong to one of your patients, or shouldn't be attached to any order — for example, results for an account that isn't live yet, or for patients you order for outside Junction. The case is marked resolved and the result is not attached.

To clear several cases at once, select them in the queue and reject them in bulk. Critical results must be reviewed and rejected individually, with a reason.

Send to Junction

Use this when you can't confirm the patient's identity or the correct order, and need us to investigate. Add a note explaining what your team found — it's key context the investigating team has. If you've found the right order in your own system, entering its order ID directly (see Reviewing a case) is usually faster than sending the case to Junction.

The case moves to Junction Reviewing, where your notes stay visible while we work it. Junction resolves the case from there.

Reasons a result can't be matched

Reason shown

What happened

What to check

Order already completed

The sample matched an order that has already been completed and resulted

Whether this is a genuinely new result for the same patient and test

Order was cancelled

The sample matched an order that had been cancelled before the result arrived

Whether the collection was valid and the result should be released

Order not marked as collected

The order isn't in a state where it can receive a result

Whether the collection actually happened, and that the order is the right one

Open order at a different lab

The patient matches, but their open order is written for a different central lab

Which lab performed the draw, and that the patient and test are correct

Matches more than one patient

The demographics match more than one patient in your account

Which patient is correct — send to Junction if identity can't be confirmed

Order found, but patient details don't match

The sample ID matched an order, but the demographics on the result don't

The demographic conflict, and which details are correct, before attaching anything

Patient found, but no matching order

The patient is identified, but no order carries this sample ID

Which of the suggested orders is correct, if any — enter the order ID yourself, or accept to create a new order if the test was performed without a requisition

No match found

Neither a patient nor an order could be identified confidently

Whether this is your patient at all — reject or send to Junction

The same labels appear in the dashboard and in email notifications.

A note on cancelled orders

Where an order was cancelled before the result arrived, the resolution is a replacement order — Junction does not reactivate cancelled orders. A cancelled order that has been un-cancelled isn't a valid state, and results released that way lose their audit trail. Accepting the case creates a replacement order that carries the result and stays linked to the original through the order transaction.

Notifications

Your team can receive a daily email digest of cases awaiting review, with results flagged critical sent immediately. Nothing is sent until a recipient address is configured in Organization or Team config.

See Unmatched Results Notifications for setup. We recommend configuring a recipient before December 1 so critical results reach your team right away.

How quickly should we action these?

Review critical results as soon as they arrive. Aim to clear all other cases within 0-3 days of receipt.

Cases stay in Needs Action until someone resolves them — they don't expire, and they don't return to Junction automatically. Any case still outstanding continues to appear in your daily digest under "Waiting from earlier."

The result isn't in the patient's record while the case is open, so an unactioned case is a patient waiting on a result.

Getting help

Share feedback or report a problem through your shared Slack channel with Junction or your Customer Success Manager. For a specific case, include:

  • the patient name or sample ID on the result

  • what you expected to happen and what actually happened

For cases you can't confidently resolve, use Send to Junction rather than Slack — it keeps the case and your notes together.

Related articles