See Talk thread at:
There is a feature that exists in the Order Entry API that allows one to distinguish between a real-time Order and a retrospectively-entered Order:
The "saveRetrospectiveOrder" method saves with a specific flag that changes validation rules. In particular, it allows for stopping/discontinuing an Order for a date prior to it’s auto-expire date, even if that auto-expire date is currently in the past.
However, currently in the Encounter Service, all nested Orders are saved by invoking the non-retrospective method:
This needs to be modified in order to ensure that if an Encounter and Orders are entered retrospectively, that the appropriate retrospective order processing is invoked.