Nemo-Q queuing system

jHIS™ system has been integrated with the Nemo-Q queuing system. For users with access to Nemo- Q, in the jHIS system in the top right corner of the window (with username) is displayed an icon with the letter "Q" opening in a new window queuing system’s panel.

After clicking on this icon, a window of queuing system’s panel is displayed. There is the login form in the window to the queuing system, where a queuing system and position can be selected. After selecting the position, jHIS system checks in the Nemo-Q system whether the position requires a login and if required system displays additional fields to select a user and provide the password. In both cases, after completing the form, press the "Login" button.

After logging, the form of recalling tickets is displayed. If there was any ticket already invoked, his number appears on the form. From the form it is possible to recall another ticket, to re-recall recently caused ticket and to recall any already served or still pending ticket (after selecting from the list and press "Call" button under the list). When recalling a ticket, on the form there is displaying a number of called ticket and above the form there is relevant information about the maneuver, and the display of queuing system also displays the number of called ticket (which also flashes and the queuing system emits a beep).

From the form, you can log out of the queuing system and close the window. Closing the window without logging off from queuing system does not result in breaking the connection to the queuing system - the re-opening of the window (or click on the icon "Q" with the user name in the top right corner of the jHIS system’s window) shows the form of calling ticket with visible recently called number.

ATTENTION!

  • If you recall tickets by the jHIS system then you should completely abandon the use of the WinPanel application (which is part of the Nemo-Q). Using the jHIS system from some positions and some from the WinPanel applications can lead to incompatibility of users’ sessions and as a result to errors in the jHIS software activity.