HL7 v2 ORC-1 (Order Control): Format, Values, and Testing Notes
Most order-handling code gets written and tested against NW (new order) and nothing else, so the first cancel or status-change message a system receives in production is often the first one it has ever actually parsed.
ORC-1 is the first field of the HL7 v2 ORC segment — a required coded value that identifies what kind of order event the message represents, such as a new order, a cancellation, or a status update.
Valid code values
Example
NW in the first field marks this as a brand-new order. Synthetic order — not from any real facility.
Where this trips people up
Test suites built around a single ORC-1 value (almost always NW) leave the cancel, discontinue, and status-change paths completely unexercised. In production, a CA or DC message that arrives at a system expecting only NW often gets treated as a brand-new order instead of a cancellation of an existing one — which is a far more dangerous failure than a dropped message, because it can leave a canceled order still active in a downstream queue.