Geaux Getters Diabetes Database

1. Geaux Getters Diabetes Database ISDS 3110- SUZANNE PAWLOWSKI Section 1 Jason Byrd – Kevin Tran – mike semko – de’jon dickerson – brad weeks

2. Design: ERD Diagram

3. Table design - Relational schema Here we have the relational schema as it appears in the database

4. Data dictionary

5. Introduction: uses of database • The main uses of the database is to keep track of: • Glucose levels • Weight over time • Caloric intake • Medication dosage amounts • Types of food eaten Main user welcome screen

6. Data entry Forms – enter new data • Upon navigating to the “enter new data” form, users are greeted with a main log screen which includes: • Medication Log • Weight Log • Glucose Log • Food Log

7. Medication log • Here, patients are able to enter their medication type and other fields that are required are: • Date medication was taken • Time medication was taken • Dosage • Delivery Method (oral, injection, or pump)

8. Weight log • On the weight log form we have: • USER ID • Date weight is logged • Weight being logged From this table, a user can generate averages and keep track of their weight over time

9. Glucose log • Under glucose log, we have the date and time in which the data was logged. Other required entries are: • Amount of glucose recorded in user’s body • Ketone levels (lower is better) • Test type (fasting, post prandial, random)

10. Food log • In the food logs form, the user selects their USER ID, followed by the date and time in which the food is logged. Entries include: • Food eaten • Number of servings • Which meal (Breakfast, Lunch, Dinner, Other)

11. View report screen • On the welcome screen, there is also a view report button that brings the user to a summary of reports that conveniently show different reports a user can print out • Glucose levels • Total carbs: with ketones present • Total Carbs: Post prandial out of normal limits

12. Report #1 – glucose levels • Amount of glucose • Whether ketones are present • Type of test performed • Red = Low • Green = Normal • Blue = High

13. Report #2 - On report #2, we have a listing of the days in which ketones are present, as well as the daily total carbs that the user took in for that day.

14. Report #3 – total carbs post prandial • Report #3 shows the dates in which levels after the meal are out of normal limits, and again the total carbs that were taken. • The user can use this information to later adjust how they eat their eating habits

15. Report #4 – Weight / Calorie Trend Here we have a graphical report that shows the trends of both weight and calorie logs over time. On the non graphical report, there are averages of each trend

16. Report #5 - Calories and Food Exceeding Prandial Limit • Our last report deals with foods that exceed the prandial limit • Food Type • Date • Total calories

17. Database Security • Main Security Features include • Restricted Access • User Name / Password • Guided Entries • Access doesn’t allow user level security, but for the purpose of our database there can be multiple users. (user entity was created for further implementation)