API

​

What’s New

• Interpretation Filter – Filter orders by clinical result interpretation using the new “Interpretation” dropdown filter
• Critical Value Indicators – The orders table now displays visual indicators for orders with critical results
• Enhanced Order Details – Order detail views now include interpretation badges highlighting critical findings

​

Filter Options

• Normal – Orders with results within normal reference ranges
• Abnormal – Orders with results outside normal ranges but not critically urgent
• Critical – Orders with results requiring immediate clinical attention

​

Visual Enhancements

​

Orders Table

• Critical value indicators help you quickly spot high-priority results that need immediate attention
• Clear visual distinction between normal, abnormal, and critical interpretations

​

Order Details View

• Prominent badges display the interpretation status for easy identification
• Critical results are highlighted with distinctive styling to ensure they don’t go unnoticed

• Rename panel names
• Archive outdated or unused panels to keep things clean
• View archived panels using the “Status” filter and “unarchive” to make panels active again

1. Look for areas in your code where you take an action based on the values of a Junction-defined enum. For example, you might have Python code like this:

match status:
    case OrderStatus.TESTKIT_ORDERED:
        handle_ordered()
    case OrderStatus.TESTKIT_AWAITING_REGISTRATION:
        handle_awaiting_registration()
        # other cases...

2. Check unknown values in your code paths are handled gracefully—for example, by using default cases. Logging unknown values can help you stay informed.

match status:
    # previous cases...
    case unknown_status:
        logger.warning(f"Unknown status received: {repr(unknown_status)}")

3. Make sure you’re running the latest version of our SDK.
4. You’re good to go. Once you’ve checked the code paths won’t break if Junction-defined enums start including new values, no further action is needed.