NutrAlert
1) We will be developing a health and fitness app that adults of all ages can use. This
application will utilize information input by the user to track both nutritional and
medicinal information. Our product will contain a subscription-based model, where
individuals pay monthly fees in order to continue using the application’s features. Some
of the paid features of this application will allow users to track their daily ingestion of
calories, sugars, carbohydrates, etc. Additionally, this application will track all input food
allergies. Our application will have a barcode scanner that when scanned, returns
information about the product quickly. This information includes nutritional facts such as
calorie counts and the ingredients of the food. If the product contains ingredients the
individual is allergic to, it will notify the user so that they can avoid that product.
Individuals can also input medicinal schedules into the application. Both a notification
and accompanying image will be presented in the app when it is time to take medicine.
This would be especially useful for individuals who take various medications through the
day and have a hard time remembering which one to take. Going a step further, once the
medicine is running low the app will notify the local pharmacy so that the individual can
have their prescription refilled. Lastly, this application will be able to track blood
pressure, heart rate, blood sugar levels, etc. over time. Health metrics will be input by the
individual over the span of many months. Monthly reports can then be generated so that
individuals can monitor trends in their health. While this will be an optional feature,
many individuals may gain insight on when they’re most susceptible to persisting
ailments. As part of the paid subscription, individuals can link to their primary care
physician. This connection will allow reports to automatically be sent to physicians for
review. Physicians could use information from these reports to identify trends and better
understand each patient's physiology. Doctors can offer better treatment plans by making
data driven decisions, as opposed to simply relying on preexisting knowledge.
2) System Design:
a) Inputs:
i)
The System will require a variety of inputs by the end user. Upon initial
contact with the application, a login screen will be displayed. If no account
is currently made, there will be a prompt to ‘create’ an account. Account
creation will require inputting the user’s name, date of birth, and email
account. Email accounts must be verified to help avoid ‘spam’ account
creation. Due to the subscription-based model of the application, users will
be required to input credit card information. We may expand this
monetization model to include subscriptions from restaurants as well.
Upon completion, users will then begin inputting data about themselves
into the application. This data includes personal favorites and allergies.
Individuals will have the ability to scan barcodes into the system and
upload menus of their favorite restaurants as well. Additional inputs can
be used at the user’s discretion. One optional feature will be the
management of medicinal schedules. Individuals can input images of their
medicine as well as ingestion times into the system. The system will alert
users when it is time to take their medicine and also show what the
product looks like. Other optional inputs include modifying account
information such as changing payment information, modifying account
holder name, email, passwords, and allergies. At the start of account
creation there is quite a bit of manual user input. While this application
contains extensive data about multiple different areas, individuals can pick
their area of interest and input data for it one single time. Having a
comprehensive application as opposed to many separate applications will
create an all-in-one health management application.
b) Output:
i)
Outputs will be generated based on information input. For example, when
a user scans a product barcode, nutritional information will be displayed.
As part of this output any allergies will also be shown. Menu options will
allow users to view reports on their daily ingested calories, sugars,
carbohydrates, and etc. Images of medicine that is scheduled for
consumption will also appear. This allows individuals to ensure they
aren’t ingesting the wrong nutrients and that they are adhering to their
medicinal schedule.
c) Interactive Dialog
i) The application is extremely user friendly. It depends on the input of the user to
be functional. The need for interactive dialogue within the application is
necessary. After the user logs into their account, a personalized welcome message
asking the user if he/she would like to continue. In order to continue the cancel
button must be selected. The user is prompted to enter allergies into the
application which can be entered via keyboard or spoken via the use of the
microphone. Interactive dialogue allows the user to feel as if the application is
customized just for them.
d) Processing
Once a user inputs the login credentials, supplied details are stored in the LoginCredentials table
in the HealthAndFitness repository. User passwords are encrypted using SHA-256 algorithms for
higher security. The application validates the supplied credentials against encrypted credentials
stored in the database and the user is redirected to the home page on successful login. Unique
customer ID will be created for every customer to store, maintain and retrieve information of each
customer.
On navigating to the home screen, the user can navigate to different screens and the default screen
is Allergies. All the Allergies in the application are stored in the dbo.Allergy table, each row in the
table has an AllergyId and Name. If a user enters his/her allergies in the screen, they are saved in
the dbo.CustomerAllergy table, each row in this table has CustomerId, AllergyId linking allergies
to the customer. If the user has registered allergies the application pulls these allergies from the
dbo.CustomerAllgergy table using an HealthAndFitness API and the allergies are displayed in the
Allergies screen in a list view.
Users can then navigate to the tablet screen. All the tablets in the application are stored in the
dbo.tablets table, each row in the table has a tabletid and Name. If a user enters his/her tablets and
dosage on the screen, they are saved in the dbo.CustomerTablet table, each row in this table have
CustomerId, Tablet, dosage linking to the customer. If the user has mentioned tablets the
application pulls these tablets from the dbo.CustomerTablet table using an HealthAndFitness API
and the tablets are displayed in the tablets screen with the dosage and timing.
Navigating to the Reminders section in the Tablets screen, users can see the reminders about the
prescribed tablets. While scanning the prescriptions, the Quantity column in the
dbo.CustomerTablet is populated for each tablet customer combination. Application decreases the
quantity of the tablets in the column after notifying the user to take the tablet (application assumes
user takes the tablet as prescribed). Once the quantity of the tablet reduces to a configurable amount
(for example: 2) a notification is sent to the Drug store for the tablets on behalf of the user.
e) Databases & Files
f) Telecommunication Needs (Cody)
i)
Our application will need a way to communicate with pharmacies to let
them know when end user’s prescriptions need to be refilled. This can
either be processed as an automatic notification or manually done by the
end user in case they have accidently lost their medicine or improperly
taken it. Communication will be done via the internet, but delivery
methods may vary (email, RSS Feeds, etc.)
g) Mockup Screens for inputs, outputs, interactions
Figure 1 This would be the initial login screen with a link allowing the user to create a new account if necessary.
Figure 2 This would be the screen that the customer sees after the initial login page. It would have an interactive
dialogue box with a short message to the user. The user would be able to navigate to approximately four different
sections of the app which are All
Figure 3 This screen will allow the user to enter all known allergies into the application.
Figure 4 This screen will show a list of the allergies entered by the user. The app will then prompt the user to scan a
product to compare it to the known allergies.
Figure 5 This screen will allow the menus of the favorite restaurants to be uploaded into the app to make it easier to
compare the menu’s items to the known allergy list.
Figure 6 This screen would allow the user to edit the profile such as change password, delete payment method, and
access application settings.
Figure 7 This screen will allow the user to track/log basic health information.
3) Technology (hardware, software) requirements for implementation & vendors
The user would need a smartphone with adequate space to utilize the application. The camera
must also be in working condition in order to scan the products into the application. Operating
system must also be compatible with the application. The OS would need to at least be
Marshmallow 6.0 for androids, and IOS 10 for Apple products. Going further, we would like to
integrate it with iWatch and SmartWatch to track the heart rate, calories, blood pressure and
other fitness activities.