Exchanges Between the Patient Control System and the Medical Personnel Control System
*This figure illustrates the front end graphical user interface of our project.
Since there are many patients and the medical personnel includes doctors, nurses, and anyone involved in the treatment of patients, the network model is more like a mesh rather than a hub and spoke. We will go over the meal plan and meal-less protocols, the protocol for patients to ‘call doctor’.
Meal Plan Protocol:
Typically, glucagon (produced when blood glucose is low) leads to hunger. In our simulation, we have allowed patients to be able to select ‘Food Request’ during set times of the day – 7:00, 12:00, and 18:00. The ‘Food Request’ button is only available during those times because realistically, cafeteria would typically only be open during certain times in a hospital. When the patient clicks ‘Food Request’, patient’s blood glucose levels begin to decline from his or her basal glucose level (80 mg/dL) because obviously the patient is hungry. The glucagon rises correspondingly. While the ‘Food Request’ button has been clicked, the Medical Personnel must click ‘Accept Food Request’. Pressing this button simulates when a nurse has delivered food and saw that the patient was eating. The acceptance signifies that the patient has received food, and this leads to a spike in the patient’s blood glucose.
Meal-less Protocol:
If patient’s blood glucose level drops to 70 mg/dL, patient becomes hypoglycemic. The doctor is then notified that the patient has become glycemic and the Glucosystem automatically begins infusing patient with dextrose (a kind of sugar) to normalize blood glucose back. Upon normalization, the program will continue to run.
Call Medical Personnel:
Often times, a patient would want to call medical personnel for assistance or for an emergency. To simulate such a case, a patient will always have the option to press ‘Call the Doctor’. Upon pressing it, the medical personnel is notified of the patient having clicked the button. Once a medical personnel has taken care of the patient, the medical personnel must click ‘Resolved’.
Back to introduction
Meal Plan Protocol:
Typically, glucagon (produced when blood glucose is low) leads to hunger. In our simulation, we have allowed patients to be able to select ‘Food Request’ during set times of the day – 7:00, 12:00, and 18:00. The ‘Food Request’ button is only available during those times because realistically, cafeteria would typically only be open during certain times in a hospital. When the patient clicks ‘Food Request’, patient’s blood glucose levels begin to decline from his or her basal glucose level (80 mg/dL) because obviously the patient is hungry. The glucagon rises correspondingly. While the ‘Food Request’ button has been clicked, the Medical Personnel must click ‘Accept Food Request’. Pressing this button simulates when a nurse has delivered food and saw that the patient was eating. The acceptance signifies that the patient has received food, and this leads to a spike in the patient’s blood glucose.
Meal-less Protocol:
If patient’s blood glucose level drops to 70 mg/dL, patient becomes hypoglycemic. The doctor is then notified that the patient has become glycemic and the Glucosystem automatically begins infusing patient with dextrose (a kind of sugar) to normalize blood glucose back. Upon normalization, the program will continue to run.
Call Medical Personnel:
Often times, a patient would want to call medical personnel for assistance or for an emergency. To simulate such a case, a patient will always have the option to press ‘Call the Doctor’. Upon pressing it, the medical personnel is notified of the patient having clicked the button. Once a medical personnel has taken care of the patient, the medical personnel must click ‘Resolved’.
Back to introduction