UK Core Implementation Guide STU3 Sequence - Sprint 6 Review

status

It is expected that most implementations will require the use of status to support workflow.

The status can be used to determine the overall status of dispense request; however, it does not cater for the granularity that prescription tracking software can offer.

It is recommended that the MedicationDispense.status is used to indicate the status at a high-level so that integrated systems can determine how to represent this information.

Status FHIR Definition Implementation Guidance
preparation The core event has not started yet, but some staging activities have begun (e.g. initial compounding or packaging of medication). Preparation stages MAY be tracked for billing purposes. Consider how the status preparation is presented to the end-user to avoid confusion with in-progress.
in-progress The dispensed product is ready for pickup. Consider how the status in-progress is presented to the end-user to avoid confusion with complete when dispensed medication is in-transit to a ward, or to a patient via a delivery service.
cancelled The dispensed product was not and will never be picked up by the patient. Avoid the use of this status value where possible as very similar to stopped and therefore potentially confusing.
on-hold The dispense process is paused while waiting for an external event to reactivate the dispense. For example, new stock has arrived or the prescriber has called. Probably most useful as a pharmacy-facing status. If exposed to users outside the pharmacy, such users may want to know how long the dispensing event will be on hold in case alternative dispensing arrangements need to be identified.
completed The dispensed product has been picked up. This would be a suitable trigger to post / share the medication dispense with the requesting ePMA system.
entered-in-error The dispense was entered in error and therefore nullified. Not to be used unless specific use-cases can be identified.
stopped Actions implied by the dispense have been permanently halted, before all of them occurred. A MedicationDispense.statusReason SHOULD be populated with a coded reason for stopping the medication administration. This would be a suitable trigger to post / share the medication dispense with the requesting ePMA system.
declined The dispense was declined and not performed This would be a suitable trigger to post / share the declined medication dispense event with the requesting ePMA system.
unknown The authoring system does not know which of the status values applies for this medication dispense. Note: this concept is not to be used for other - one of the listed statuses is presumed to apply, it's just not known which one. Avoid the use of this status value where possible.


back to top