Health Hub - User Guide

In this patch, the functionality to register new health workers into the application has been implemented. Users may now also add new requests from patients into Health Hub for future assignment using the assign command.

For more explicit information on the add command, visit Section 5, “Features”, under Adding a Health Worker/Request.

Version 1.2 provides more utility to the application through the implementation of the edit and delete commands that allow the user to modify and remove requests and health workers from the application.

For more explicit information on the edit command, visit Section 5, “Features”, under Editing a Health Worker/Request.

With the release of version 1.3, we have set out to improve the already simple and easy to use Health Hub with command shortcuts, as well as filter command to easily search for staff with the skillset you are looking for.

Shortcuts:

Filtering requests and health workers:

Other enhancements made to Health Hub include:

For more explicit information on the filter,setreminder and undo/redo command, visit Section 5, “Features”, under Filtering Health Workers/Requests.

With the release of version 1.4, we decided to improve our current features by making them more dynamic and automated to reduce the manual work of changing the data.

After the release of v1.4, the team have planned for future enhancements to Health Hub to improve its existing functionalities, by also considering different aspects such as the ethical part of handling sensitive patient information within and outside of the app.

For data management, it will be upgraded to an even higher level of encryption by professional standards to ensure that sensitive information is handled cautiously to prevent data leaks.

For account management, hospital administrative staff will have to start logging in to their accounts (accounts which are given to them when they first joined the department) in order to use the app. These accounts are created and managed by a higher authority personnel, to add a second layer of security.

So far, with the releases of v1.2 to v1.4, the focus is on registering the requests into the system and assigning them. In v2.0, there will be additional details added to health workers such as their availability to visit the home care patients, that will add value to when the user is assigning an open request.

Last but not least, it is important that we gather our users' feedback from time to time to understand their frustrations and needs with the app. As such, there will be a "Feedback" option in v2.0 for users to submit their feedback to the developers of Health Hub.

Upon first starting the application as a new user, or perhaps a returning user, you may open up the help menu using the help command.

Upon entering the help command, the help menu renders separately from the Health Hub main application. Therefore, you do not have to worry about losing any existing work on Health Hub when you are viewing the help menu!

Format: help

The help menu displays a list of available commands for Health Hub, their parameters and their functions. Should you ever forget the commands for Health Hub, feel free to enter the help command to revisit this guide.

The list command is a simple and basic command that on entering, displays all health workers/requests in the Health Hub GUI.

Format: list <type>

Before you can jump right into the core feature of our application and streamline the process of adding requests from patients and to assign requests to experts in the medical field, it is essential to first ensure that the respective health staff and patients are registered in the system with all the key information.

Add a request, health worker or patient to the application based on the <type> parameter accepted, using the add command, to register new health staff, patients and requests.

Format: add <type> <additional_parameters>…​

Sometimes, information on a request of health staff may be keyed in wrongly into the application, or you may need to update existing outdated information.

To do this, you can replace the current information with the new one using the edit command to modify existing personnel records or request descriptions in Health Hub.

The edit may come in handy when there is a need update to a request’s status, patient’s condition or a health worker’s skills, based on the <type> parameter accepted.

The prefixes and valid values for the edit command for both health worker and request modes follow the same format as in the add command.

When identifying health workers to assign to an open request, or to look for a particular patient details in certain requests, it may be useful to only display items in a list that match a particular constraint.

Using the filter command, you can set the GUI to display health workers and requests whose fields match the keywords`that are specified in the `filter command, allowing you to find the doctors who are experts in cardiology much quicker.

Format: filter <type> <keyword> [<more_keywords>]…​

Should there be any invalid or expired request, health worker or patient in the application, you may also remove them to prevent cluttering of unnecessary data by using the delete command to remove them from the application based on the`<type>` parameter accepted, according to the index of the respective type shown using the list command, or the index displayed on the GUI.

Format: delete <type> <index>

After registering a new request using the add request command, you may proceed to assign an existing health worker in the system to handle the request, allocating medical resources to it and closing the request using the simple assign command

Format: assign hw/<health_worker_index> r/<request_index>…​

Where the <request_index> and <health_worker_index> are as shown in the respective health worker and requests lists in the Health Hub GUI.

Notes:

Examples:

After closing all existing requests, you also have the option of clearing all requests from the request list, regardless of the state of the request, upon entering the clr command.

Format: clr

After an assigned task has been completed by the assigned health staff, who has administered the necessary medical treatment, you can mark the request as closed, using the complete command.

Format: complete <request_index>

Upon entering the complete command, you should notice the status of the request at position <request_index> changed to COMPLETED, marking the request closed.

Notes:

Examples:

If you wish to undo a mistake that you had made while entering commands, you can restore the lists to the state before the command was called using the undo command.

Format: undo

If you wish to redo a command that you have previously undone, you can use the redo command.

Format: redo

In the case where you have been using the application for a while now, and wish to track and see the past commands that you have entered into the application, or where you have taken over the application from another person, you can do so using the history command.

Using the history command, you can view the previous commands entered in the application in chronological order, allowing you to identify the order in which commands are keyed in previously.

Format: history

With the flexibility in managing and adding, editing and deleting requests, existing functionality for the user to view the details of requests in Health Hub has also been implemented to improve the user experience.

Format: select <request_index>

Shortcut: sr <request_index>

Entering the select command allows the application to select the request at the specified <request_index>, and displays the full details of the selected request on the GUI.

Sometimes when you have too many tasks at hand, it can be quite cumbersome to remember what tasks you need to complete for the day. You might want to phone up a patient to remind him of an appointment before the health worker visits his home, because you recall that this patient was not at home the last time the health worker visited. The phone call from you can prepare him to be at his home when the health worker arrives, so he can provide the necessary health care services. It can also remind you when it is lunch time, so you can avoid the peak period!

Format: setreminder t/<hh:mm:ss> m/<customised_message>

Using the setreminder command, you can set a reminder alert to notify you at a certain time of the day, with your own message that you can customise to remind yourself.

In the example below, a reminder has been set to notify the user at 6.30PM with the customised message to "to call patient Tan Ah Hock for his appointment later at night".

Figure 5.14.1 shows the format of the setreminder command in the text field.

Figure 5.14.2 shows the result of the reminder alert in the GUI after it is time for the app to notify the user.

We understand that it is imperative for you to know which health conditions have been seeing an increasing trend, as well as take note of those which have been experiencing a decline. The statistics command allows you to view all health conditions that have been registered on HealthHub, and also their respective numbers of occurrences.

Format: statistics → this command displays a list of all health conditions that you have typed into HealthHub, and shows each health condition’s related number of occurrences.

Example of usage:

Let’s say that no commands have been issued yet and HealthHub is on a clean slate with no prior records of requests. Suppose as an administrative staff, you input the following commands as your first 2 requests for home care into HealthHub:

add request n/John Doe i/S8974421C p/98765432 a/123 Brick Road, #01-01 dt/01-01-2019 14:50:00 c/Diabetes c/Physiotherapy

add request n/Dohn Joe i/S9874421C p/98675432 a/Sheares Hall, #01-01 dt/06-05-2019 10:10:00 c/AIDS c/Physiotherapy

You can then subsequently type in the following command:

statistics

Voila! A list of health conditions (namely, the ones which were typed in the 2 abovementioned requests Physiotherapy, Diabetes, AIDS) will be generated and will be displayed in descending order of occurrences. The following screen is what you can expect to see after typing in the 3 commands.

Once you are done using the application, you can exit the application by entering the exit command, hereby saving any information at the current point in time before shutting down.

Format: exit

All application data are saved in the hard disk automatically after exiting the application, removing the need to save manually.

Changes to the data in the application are also saved that any command that modifies application parameters, making sure that minimal data is lost should any unforeseen circumstances happen.

Attempting to read a corrupted data file will show an empty book. If the application is unable to find any data files, it will create books based on its sample data.