Patient Queueing in Refapp

Here is a Wiki to the Module. Kindly feel free to supplement to requirements. https://wiki.openmrs.org/display/projects/Patient+Queueing+In+Reference+Application

Thanks @slubwama for putting this up. Though it seems to be dealing with more than just patient queueing, correct?

Yes. I also Has a Clinician Dashboard which comes in handy for Clinicians to See their workload of the day

Hi @slubwama, thanks for sharing this.

Is there already a POC to look at, or this is still being designed?

@mksd This is Still work in progress. Thou the first commit of code is ready. When the Repo is created by @dkayiwa I will commit it for review and in the process People can contribute more.

This could have a great opportunity of being reused if it could be plugged elsewhere, will this come as an OWA?

Its Scaffolded as a module other than an owa. But If Its demanded, I could look into it.

I’m afraid a good old module with GSP pages and fragments will hit the wall at some point.

Because of all what’s happening between OpenMRS React Components and the move to micro frontends, I would really strongly suggest to embrace all this.

Your views should be living in a reusable UI library (such as OpenMRS React Components), and the whole thing should be packaged as an OWA. As for the backend, it should be RESTful.

If your UI development is not too far yet and that it’s possible to go for the above, please yes, I would advocate for it.

Just adding to the mix :slight_smile: , OWA is an obsolete standard. An amazing future for OpenMRS

So If OWA is an obsolete standard Who do you Advise I work around this.

Looping in @joeldenning who is leading the microfrontends squad: https://wiki.openmrs.org/x/pQFiDQ

Yes it’s an obsolete standard but 1) it is SPA/micro-frontend friendly, meaning that developing through an OWA will not cause troubles down the line, there is a clear path to SPA and 2) GSP is completely obsolete.

I would put your UI components in OpenMRS React Components, if you do so, the place where you eventually bundle them for final delivery becomes much more of a detail, whether wrapped inside a GSP or bundled in an OWA.

Well This discussion seems to be Interesting. I will follow on from this. Let me put in some research to see how I transform what I have to be micro-front end friendly.

Consider also joining in with the work that is going on in the microfrotennd squad discussing patient queuing & appointments.

The Talk thread is below, and there is a SLACK channel that has most of the more current discussion.

Yeah I’m happy to chat about how your work could fit in with the microfrontends initiative. Feel free to DM me about it. Right now we’re still in the decision making and early implementation phase. Things aren’t quite ready for everyone to start using immediately. But if you’d like to get involved, let me know.

@joeldenning isn’t there some high levels dos and donts can be shared already in order to not slam the door to a future integration?

My 2 cents would be: 1) avoid GSP and 2) use something like Angular or React and package the result in a standard way. I would assume that an OWA fed from something like OpenMRS React Components would for instance ensure all that.

@slubwama Are you still moving ahead with this module? How far have you gone?

@c.antwi @mksd @joeldenning @gschmidt @dkayiwa @wyclif @ssmusoke this module has been released with a 1.0.0 out. Documentation of this module can be found here https://wiki.openmrs.org/display/docs/Patient+Queueing+Module. Will begin the next sprint for this module.

1 Like

Thanks for the heads up @slubwama, and all the work put into this so far.

@jesplana, wondering if that something you might be interested in for our hospital program?

Yes! Definitely! We have a triage form that is going to be developed in the next couple of sprints.