Queue services, priorities, and statuses

Development
1

Hi all, particularly @grace , @akanter , @fanderson, @minimalist, @ibacher and @ball -

I’ve been working to get the Queue module set up for evaluation at PIH, and there is some basic concept metadata that is required to get this module functional. I wanted to check with you as to whether we an come to a common understanding of what these (especially services) represent, and whether there are some standard CIEL constructs that we might share, at least for a starter set.

Basically, a Queue in OpenMRS requires configuration of these three things:

  1. Concept Set + Concepts defining the super-set of all Services that one might represent with a Queue. Basically those things that a patient might be Queued for at a given Location. this is still a little fuzzy to me in terms of how this should be configured, but I’ve seen the refapp configure this with “Triage” and “Clinical Consultation”. I could also imagine this being more specific to a type of service that might be offered in multiple locations, like “Mental Health” or “Pediatrics”. I’d be interested in discussing more how this should be set up.

  2. Concept Set + Concepts defining the super set of all Priorities associated with a patient’s position in a Queue. For example, “Normal” and “Emergency”.

  3. Concept Set + Concepts defining the super set of all Statuses associated with a patient’s position in a Queue. For example “Waiting” and “In Service”.

I’m wondering if we can define a reasonable super-set of each of these that would be a good starting point / default for an implementation.

I have found a number of concepts that seem well-suited for Priority in OCL (see CIEL 161238), which is a Q-and-A concept in CIEL named “Procedure/Test priority”, with answers of “Delayed priority (status)”, “Normal priority (status)”, “Emergency (status)”, and “STAT (statim) - Immediate”.

I have found a number of concepts that seem well-suited for Status and Service in OCL (see CIEL 167406, which is a Q-and-A concept in CIEL named “Patient care administration status”, with answers of “Waiting”, “In Service”, “Finished Service”, “Clinical consulatation”, and “Triage service”.

I’m also seeing a lot of custom stuff in DemoQueueConcepts in the openmrs source created for the refapp. I’m hoping we might all transition to something a little more standard than this.

What do you think about creating some concepts in CIEL to represent the 3 concept sets needed, which contain a reasonable set of these concepts that implementations could use? Something like:

  • Queue Services Default Set: TBD
  • Queue Priorities Default Set: “Normal”, “Emergency”, “STAT”
  • Queue Statuses Default Set: “Waiting”, “In Service”, “Finished Service”

This would help implementations get up and running more quickly and in a more standardized way, and also provide a means for us to provide a better set of default configurations in the reference application than we are currently able to do.

NOTE: I’d also like to discuss further whether these are the right concepts for these sets, or whether a different and/or broader set of concepts can be identified. I’m basing this mostly on what I see in the refapp configurations.

Thanks, Mike

2 Likes
2

I am 100% on board with this idea.

FWIW Here’s what I set up I think over a year ago as the sample starter-pack for O3 Queue Metadata, based on terms used in the original User Testing. This was never meant to be exhaustive but just to be a quick-start at the time.

Happy to change this to better CIEL codes than the custom starter-pack I made way back when this O3 queues project first started.

I believe @minimalist used these at the beginning; @minimalist what codes are you using at Palladium now?

3

We use what you have highlighted for priorities and status, there a few services that we added eg Lab service and Pharmacy service to support our users

1 Like