Good discussion on today’s design forum (notes here). Here are some quick takeaways (I believe @mogoodrich is going to provide a summary).
Introduce Order.fulfillerStatus
now:
-
received
- order fulfiller has received the request -
exception
- an error or exception occurred during processing -
completed
- the request has been completed by fulfiller
Consider also introducing Order.status
(aligning with FHIR status fields):
-
draft
- unsigned, work in progress -
active
- order that may be acted upon -
completed
- all activity related to the request has been completed -
stopped
- request terminated
Some additional thoughts during the discussion:
- We haven’t yet modeled how we would handle orders needing cosign.
- Verbal orders will be deferred. Would be
active
and probably have a separate property to track authorizing signature. - We would not plan on supporting
on hold
orsuspended
(risk of medical errors, encourage stop and re-write instead). - We would not plan on implementing FHIR’s
cancelled
orentered in error
statuses (close enough to OpenMRS voiding). - We wouldn’t support
unknown
status (would use null for this if needed later).
More details in the notes.