The nutrition request statuses are order (request) statuses – in the purview of placer, not filler.
The diagnostic report status is closer to the list relevant for a filler to manage.
What you want for filler status is closer to the diagnostic report and obs.status. Another example is our prior plans for handling obs exceptions.
As you’ve surmised, we should probably be aligning with FHIR’s ObservationStatus. But those apply to the result, so aren’t a perfect fit for the request.
- registered == received
- preliminary: more relevant for the result than the request, but could represent partially fulfilled
- final == completed
- cancelled: could lump exceptions into this, but I’d prefer to distinguish cancelled vs a problem occurred
It would be nice to have an “in process” to distinguish between received and actually being worked on.