Understanding HL7 v2 ORC-9: Date/Time of Transaction in Practice
ORC-9 records when this specific message's event happened, not when the order was first placed — and code that reuses it as the original order date quietly rewrites order history every time a status-change message comes through.
ORC-9 is the ninth field of the HL7 v2 ORC segment — a timestamp marking when the transaction described by this ORC segment occurred. On a new order it typically matches the order's placement time, but on a cancel, status-change, or other follow-up message it reflects that later event instead.
What this field contains
Example
20260726090000 in ORC-9 marks when this transaction occurred: July 26, 2026 at 9:00:00 AM. Synthetic timestamp — not from a real order.
Where this trips people up
A test suite that only ever generates a single ORC message per order never has a reason to distinguish ORC-9 from the order's original creation timestamp, since on that first message they're identical. The gap only appears once a second message — a cancellation, a status update — comes in with a later ORC-9, and any code that was quietly treating ORC-9 as an immutable order-creation date starts overwriting the original order time with whatever the latest transaction happened to carry. Order history and audit views are the most common place this shows up, usually as an order that appears to have been placed at the moment it was canceled.