Understanding Order Transactions
Last updated: June 1, 2026
Order Transactions provide a way to track the complete diagnostic journey across related lab orders.
While traditional lab workflows often treat each order as an isolated event, real-world testing frequently involves multiple orders that are all part of the same patient experience. Order Transactions allow Junction to maintain the relationship between those orders while providing a single view of the overall testing journey.
Why Order Transactions Exist
Diagnostic testing doesn’t always follow a perfectly linear path.
Patients may:
require a redraw
visit the wrong collection site
have unsolicited results returned from a laboratory
need replacement orders
encounter other workflow exceptions
Historically, each of these events often resulted in a new order being created. Over time, this created multiple disconnected records representing what was ultimately a single patient testing experience.
Order Transactions solve this problem by grouping related orders together under a shared transaction.
How Order Transactions Work
An Order Transaction represents a single diagnostic journey.
Within a transaction, there may be one or more orders.
For example:
Transaction
├── Original Order
├── Redraw Order
└── Replacement Order
Each order maintains its own:
order ID
requisition
lifecycle states
collection events
results
While remaining associated with the broader transaction.
This allows customers to view both individual orders and the complete testing journey.
The First Workflow: Redraws
The first major workflow powered by Order Transactions is redraw support.
When a redraw is required, Junction can:
create a new linked redraw order
generate a new requisition
send updated patient communications
track redraw progress independently
while maintaining the relationship to the original order.
This provides clearer visibility into redraw workflows and creates a more reliable experience for both patients and operational teams.
Learn more:📄 Redraw Workflows in Junction
Future Workflows
Order Transactions establish a foundation for future workflows including:
unsolicited results
wrong-lab collections
replacement orders
advanced exception handling
future diagnostic automation workflows
As Junction expands support for these workflows, Order Transactions will serve as the underlying model that connects related testing events.
Benefits
Simplified Patient Journeys
Track a patient’s complete testing experience instead of managing disconnected orders.
Improved Exception Handling
Support workflows such as redraws and future exception scenarios without requiring custom order reconciliation.
Cleaner Result Management
Maintain relationships between original orders, replacement orders, and final results.
Better Operational Visibility
Understand how a patient arrived at a final result, even when multiple orders were involved.
Do I Need Order Transactions?
Customers who plan to use redraw workflows should implement support for Order Transactions.
Future Junction workflows will increasingly leverage the transaction model to represent complex diagnostic journeys.
We strongly recommend adopting Order Transactions as the primary mechanism for tracking lab testing workflows going forward.
Implementation Considerations
Customers using:
webhooks
custom order tracking systems
requisition-based reconciliation
internal patient journey tracking
should review how Order Transactions fit into their implementation.
Orders can continue to be tracked individually, but customers who adopt the transaction model will be better positioned to support future Junction workflows with minimal changes.