This is a potential problem: the underlying OpenMRS platform doesn’t exactly support “urgent”. FHIR models the request priorities in increasing order as
stat, but in OpenMRS we currently only support the first and last. As a quick hack we could use “stat” in place of “urgent”, though it’s intended to mean “The request should be actioned immediately - highest possible priority. E.g. an emergency”.
@burke, @jteich, what do you think about adding some additional Order.urgency levels in OpenMRS core? (Currently we just support: ROUTINE, STAT, ON_SCHEDULED_DATE.)
To get this into v0.90 we would either need to do the quick hack mentioned above (use “stat” to mean just “urgent”) or else we’d need to:
- make this (tiny) change in openmrs-core
- do a maintenance release of openmrs-core
- make an 0.90 patch release that depends on openmrs-core 2.1.3
(As to the business requirement, yes, it’s definitely part of medical practice to be able to request lab tests, or orders in general, with different levels of priority. OpenMRS might want to have a short discussion to set a consensus on this, but I would expect that we’d definitely want to add “urgent”, and we’d probably also add “asap”, to match the FHIR consensus.)