Requirements

Great Ormond Street Hospital (GOSH), an international centre of excellence in child healthcare. Since its formation in 1852, the hospital has been dedicated to children’s healthcare and to finding new and better ways to treat childhood illnesses.

At the moment, there is no monitoring system in GOSH to help clinicians to get insights into patients’ treatment and see if the target feeding amount has been hit. Since the information is not digitalised, it is hard to track the overall condition of the patient and lose crucial information on how effective is the current treatment plan.

Having a dashboard with customisable metric graphs of infusion pump data (such as rate over time, volume over time, etc.) can give a better insight into the patient’s body. This greatly helps to analyse the data by reflecting on the effectiveness of each treatment plan, and therefore, evaluate a plan that suits the patients the most.

Our client also provided us with some examples of flowsheets they have on their current electronic health record system to help us come up with the general idea.

Data visualisation tool from Infusion Pumps in a form of a web application. The authorised users will be able to log in to the system to visualise the dashboards of the patients they are treating.

Graphs and Charts must be customisable, having several different metrics, and with the ability to view the prescribed vs. actual rates of feed the patient is receiving.

There must be a high level of data security since we are dealing with medical information and clinicians/parents will only see the dashboards of patients they were assigned.

After understanding some background information about the project, we agreed on the time to regularly meet on Teams and came up with several general questions to ask from the clients during the meeting.

Below are some questions we prepared:

• What metrics should we focus on?
• How should we record that data?
• Who will have access to the dashboard?
• Will it be linked to NHS’ database? SSO? Any APIs?
• Should we put in place some sort of alerting systems?
• How long would you like to keep the patients' data?

Semi-structured interview was conducted to gather user requirements, which allowed to ask more detailed questions based on the given response.

Q: What do you want to monitor?

A: I want to monitor the total volume that is being delivered at specific time spots over the day. I also want to know the rates at which the food or medications are being given. In addition, I want a graph showing the relationship between the prescribed feed and the actual given feed on the patient's dashboard. Monitoring the volume and the rate will give insights on how the patient is tolerating the medications, how often the rates are adjusted, which will help to understand any problems and readjust the treatment plan.

Q: Does GOSH have a system for hosting this application?

A: Yes, MyGOSH. We can focus on making the application web-based, keeping in mind the growing interest in on-device applications, to achieve the highest levels of security.

Q: Would you want to have some alerting systems in place? 

A: Sounds like a good idea, but the practicalities should be discussed further. It might be useful to have algorithms that will analyse the data patterns and raise alerts if something doesn’t look right. It will be appreciated If the system could provide any actionable insights based on historical trends of the data.

Q: How long would the data be stored in the database?

A: I would say it will be cumulative over time. You don't need a short fixed period of time, and I would also suggest that the longer period of time you're collecting the data, the more meaningful it becomes.

After having clearer requirements of the system and with our newly learned HCI material, we created personas that will be using the application and the scenarios within which it will be used.

After we spent some time thinking about different edge-cases, we scheduled a meeting to confirm with our client. With some fine adjustments, we have agreed on this finalised MoSCoW requirements list: