The handling and mapping of Lab Order status for the Lab Workflow

[mogoodrich (Mark Goodrich)]

@pmanko

The OpenMRS Order class also has a recent addition (since platform v2.2.0) of the attribute Order.fullfillerStatus , with the following fields:

• RECIEVED
• IN_PROGRESS
• EXCEPTION
• COMPLETED

I’m not sure where this attribute is being used, altough these concepts do seem to map directly to OpenELIS states. Notabely, the Ref app currently does not include this change, since it runs OpenMRS Platform v2.1.3.

I haven’t had a chance to review this in detail yet, but just as an fyi we did add the “fulfillerStatus” with the intent that it could be used to track information from a downstream fulfillment system, so it definitely seemed like it would be relevant to what you are mapping out here. We are using it in a new Lab Workflow OWA we built (GitHub - openmrs/openmrs-owa-labworkflow), but I don’t think there’s any particular core support for it. One key point is that unlike most parts of Order it is mutable.

Here’s some Talk posts with more details about adding FulFillerStatus:

"Order Tracking" OWA/module

I think we simply add orders.order_status as an Enum. My concern is, if we stop there, we are leaving it up to clients to define business logic, which could end up making things unpredictable or brittle. When we add “draft”, “received” (aka “in process”), and “cosign” (aka “needs cosign”) as additional statuses in the future, a growing number of order-related addons and reports break with each change. Do we try to predict up front all possible statuses we’ll use in the future and ask people to …

Adding "Order Status" to Orders

@wyclif… right, but you can’t do something like this: order.setDateStopped(new Date()) orderService.saveOrder(order) … because the saveOrder method explicitly fails when trying to operate on an order already being persisted: @darius there’s not a great analogy for stopOrder… there’s a utility method for changing the stopOrder, but it’s private and it looks like there’s no way to just individually change the stop date… the stopOrder method is only called via other workflow methods like disco…

I’ll make a note to review the rest of this post in detail in the coming days!

Take care, Mark