I played with the Orders REST endpoints more and noticed that order objects are actually immutable. That is, when you attempt to modify an order, it stops the existing order (essentially voiding it) and creates a new order object that references the existing one as its previousOrder. In that sense, I think having Discontinue actions batched into the order basket is fine, even in the case where the user is entering an order on another clinician’s behalf (like in RDE.)
Batching orders all at once into a single encounter might make sense for outpatient visit, but I think we need a different behavior for inpatient, when it’s not unusual for the visit to span multiple days, with orders placed on different days. In this old thread, we talked about using the EMRAPI’s endpoint to handle the logic of grouping encounters, and I think we’ll need that in the long term.