Tell us about the solution you developed?
Owen: “Ryan created the frontend of the solution which displayed all of the patients on the virtual ward. This was essentially a simple mock up, pulling all the data from the backend which I built, which then pulled data from their servers. This meant that we were then able to add observations to each patient record, such as heart rate and blood pressure, which would be needed on a virtual ward.”
Ryan: “As Owen said, I built the frontend of the solution using Blazor to create a virtual ward, and we were given four NHS patient numbers to use. We then assigned each patient to the virtual ward and included functionality to add new patients as and when needed. They also provided a frontend to view the data and this gives you an idea of what the FHIR objects look like under the bonnet.
In our app you could search by a patient’s NHS number and then add the user to the virtual ward. Doing this creates an ‘episode of care’, confirming the user has been assigned to the virtual ward, which then notifies other clinicians that the patient has been registered and assigned to the virtual ward. Within the app we built, there is the ability to add observations about how the patient is responding to treatment, and a score is calculated based on the information that has been input to determine the most appropriate course of treatment or whether the patient can be discharged.”