healthcare tracker app: full report

Health Tracker

Healthcare Software Application

Dave Siegel

Oregon Tech

MIS 498: Senior Project Binder

Jeff Dickson

June 7, 2015

Senior Project Binder – MIS 498 Dave Siegel of 96

Table of Contents

Project Overview Statement …………………………………………………………………………………………..5

User Requirements ………………………………………………………………………………………………………...6

Critical Success Factors ………………………………………………………………………………………………….6

Project Scope ………………………………………………………………………………………………………………....7

Major Risks and Strategies …………………………………………………………………………………………….8

Approach …………………………………………………………………………………………………………………….....9

Project Plan Summary

Deliverable Summary ……………………………………………………………………………………….11

Gantt Chart (see attachment)

Work Breakdown Structure ………………………………………………………………………………11

PERT/CPM Probabilistic Time Estimates ………………………………………………………….13

PERT Network Diagram ……………………………………………………………………………………14

Feasibility Analysis …………………………………………………………………………………………………......15

Project Management Approach …………………………………………………………………………………...16

Cost Benefit Analysis ……………………………………………………………………………………………………17

Use Case Descriptions ……………………………………………………………………………………………........19

Use Case Diagrams ………………………………………………………………………………………………………43


Activity Diagrams ………………………………………………………………………………………………………..45

Document Analysis ………………………………………………………………………………………………………47

E-R Diagrams ……………………………………………………………………………………………………………….48

Data Dictionary ……………………………………………………………………………………………………………48

Dataflow Diagrams ……………………………………………………………………………………………………..49

Alternative Matrix ……………………………………………………………………………………………………….52

CRUDE Matrices……………………………………………………………………………………………………………53

Communication Diagrams …………………………………………………………………………………………..54

Sequence Diagrams ……………………………………………………………………………………………………..56

Project Storyboard……………………………………………………………………………………………………….57

Interface Design…………………………………………………………………………………………………………..57

Output Design ……………………………………………………………………………………………………………..57

Package Diagram ………………………………………………………………………………………………………..63

Physical Architecture …………………………………………………………………………………………………..64

Logical Architecture …………………………………………………………………………………………………....67

Testing Plan ………………………………………………………………………………………………………………...72

Alpha Stage of Application …………………………………………………………………………………………..73

Conversion Plan …………………………………………………………………………………………………………. 74

User’s Guide ……………………………………………………………………………………………………………….. 76


Administrative User Manual ……………………………………………………………………………………… 89

Miscellaneous Documentation …………………………………………………………………………………... 94

Training Plan …………………………………………………………………………………………………………….. 94

Implementation Strategy and Plan ………………………………………………………………………….... 95


Table of Figures

PERT/CPM Probabilistic Time Estimates……………………………………………………………………..13

PERT Network Diagram ……………………………………………………………………………………………….14

Use Case Diagrams ………………………………………………………………………………………………………43

Activity Diagrams ………………………………………………………………………………………………………..44

E-R Diagrams ……………………………………………………………………………………………………………….48

Dataflow Diagrams ……………………………………………………………………………………………………..49

Communication Diagrams …………………………………………………………………………………………..54

Sequence Diagrams ……………………………………………………………………………………………………..56

Package Diagram ………………………………………………………………………………………………………..64

Deployment Diagrams …………………………………………………………………………………………………66

Logical Architecture Diagrams ……………………………………………………………………………………68


Project Overview Statement

This binder contains the documents and diagrams detailing my Senior Project, a healthcare

application named Health Tracker.

This project addresses an opportunity to provide a tool which supports both patient and provider

in the personalization of the healthcare experience with the goal being optimization of overall

health and wellness.

The goal of this project is to provide a user with an application which will facilitate access to

providers, ensure that appointments are not missed, track current and new medications, simplify

connection to telehealth devices, display fitness regimens and goals, and also keep track of

dietary constraints. In addition, weekly summations of activity will provide a patient with

reassurance and encouragement in support of achieving health care goals.

This functionality will be achieved through the provision of a user-interface enabling access to a

patient portal, appointment tracker, Rx tracker, telehealth device, fitness tracker, and a dietary

tracker. This system will utilize notifications or alerts to ensure patient health and wellness.

This project will be successful when a software tool is produced which enables a patient to more

easily and effectively achieve optimal health and wellness.

There are several factors which can affect the outcome of this project. The technology

employed in this project may not be the most currently available when the project is complete. It

is difficult to tell if the patient market will embrace this tool. In addition, will this project create a

software tool with the most user-friendly interface possible for the target audience?


User Requirements

This project will deliver the set of functionalities described within the Project Scope. These are

necessary and sufficient conditions for satisfying the needs of the user as well as delivering

business value. Following are additional requirements necessary for the full implementation of

this software tool and its ultimate success.

Functional

A desktop computer, laptop, or a tablet

Internet access

Provider/patient portal availability

A telehealth device, e.g. cardiac monitor

Fitness tracking device, e.g. Fitbit

Dietician or Nutritionist provided dietary program

Non-functional

Basic computer-use skills (i.e. navigation, user name/password use, etc.)

Motivation to use a new software tool

Ability to read and understand a printed, online, or video user’s guide

Motivation to engage in an increased level of self-care

Understanding benefits of a patient portal

Critical Success Factors



health and wellness.

Success will be determined by comparison of a pre and post application use survey. A

significant percentage increase (80%) in the level of user satisfaction regarding their healthcare

experience, in addition to an improved sense of well-being will indicate success. Furthermore,

this survey will include queries regarding product and process improvement over currently

available systems. A significant percentage increase (80%) in user sense of efficiency and

effectiveness for these parameters will indicate business value for this tool.


Project Scope

Context



health and wellness. This system provides a dashboard enabling access to a patient portal,

appointment tracker, Rx tracker, telehealth device, fitness tracker, and a dietary tracker. In

addition, notifications or alerts will be utilized to ensure patient health and wellness. There are

many health-related applications currently available which provide the functionality of the

individual elements of this system. However, this application offers a complete set of features

designed to provide an efficient and effective means to achieve optimal health and wellness in

the most user-friendly format possible.

Inside of Scope

Software Components

Patient portal interface

Appointment tracker

Rx tracker

Telehealth device interface

Fitness tracker interface

Dietary tracker

Notifications or Alerts where appropriate

Non-software components

User Instructions in print as well as digital format including video

Outside of Scope

Provider/Patient portal

Telehealth device

Fitness-tracking device


Dietician or Nutritionist

Other healthcare-related software components

End-user training

End-user application troubleshooting

Desktop computer, Laptop, or Tablet

Major Risks and Strategies

Six significant risks have been identified. Of these, three are considered major. Mitigation

strategies will be described for these risks.

Major Risks

Need for personal training in use of the application.

Training will be made available through the healthcare provider.

Unfamiliar technologies.

Research into the technology behind each application component will be conducted and

knowledgeable personnel will be sought out where necessary.

Inadequately skilled personnel.

Any skills required will be attained and knowledgeable personnel will be sought out

where necessary.

Minor Risks

Unavailable Resources.

An acceptable risk with no mitigation strategy needed.

Application fails to demonstrate a significant percentage increase in user satisfaction

regarding their healthcare experience.


User doesn’t express a significant percentage increase in sense of efficiency and

effectiveness regarding product and process improvements over currently available

systems.



Approach

Context

This project addresses an opportunity to provide a software tool which supports both patient and

provider in the personalization of the healthcare experience with the goal being optimization of

overall health and wellness. While there are existing software tools which provide the

functionality present within any one of the components of this application, the objective of this

project is to create a tool which will facilitate access to multiple elements of the healthcare

experience from one user-interface thereby enabling a patient to more easily and effectively

achieve a state of optimal health and wellness.

Phases

Scoping

This project addresses the need to provide users with a simplified, efficient, and effective

means to achieve an optimal level of healthcare. This objective will be achieved by the

provision of an application which enables users to access the following features: a

patient portal, an appointment tracker, an Rx tracker, a telehealth device, a fitness

tracker, and a dietary tracker. Success criteria include measures of user satisfaction

regarding improvement in their healthcare experience, and user sense of product and

process improvement over currently available systems. Stakeholders include the project

sponsor, project manager, and the end-user.

Planning

This project will include software components which will enable access to the features

listed above, provide alerts and notifications where appropriate, create a weekly activity

summary, and display user instructions in both print and digital formats.

Monitoring and Controlling

Project performance will be monitored to ensure completion and full functionality of all

components. Project progress will be closely monitored to ensure that the major risks

which have been identified do not develop or are controlled effectively.


Closing

A successful project will be a fully functional software application which includes the

features previously described and provides the user with a tool to easily and effectively

achieve an optimal healthcare experience.

Project Plan Summary

Deliverable Summary

Identify available hardware and software vendors. Compare the features of available

products. Choose best-of-breed systems.

Identify available patient portals and arrange for their use in the context of this project.

Design several application interface layouts, test each, and choose ideal version for use.

Create a database for the creation of user summaries of appropriate application system

functionalities.

Test and troubleshoot all hardware and software components to ensure trouble-free use.

Create user instructions for application use in digital and printed formats.

Gantt Chart

NOTE: Please see attachment to document.

Work Breakdown Structure

1. Vendor Selection

1.1 Identify hardware and software vendors

1.2 Compare vendors

1.3 Analyze results and choose vendors

2. Patient Portal

2.1 Identify patient portal

2.2 Arrange use of patient portal


3. Interface Creation

3.1 Design application interface

3.2 Create alternative layouts

3.3 Test alternatives

3.4 Choose ideal layout

3.5 Code application interface

4. Database Creation

4.1 Create database for summaries

5. Application System Testing

5.1 Test hardware and software systems

5.2 Troubleshoot hardware and software systems

5.3 Retest hardware and software systems

6. Instructions

6.1 Create user instructions for application use


PERT/CPM – Probabilistic Time Estimates

Activity ID

Vendor Selection a

Patient Portal b

Interface Creation c

Database Creation d

Application System Testing e

User Instructions f


Critical Path is number three, highlighted below.

PERT Network Diagram


Feasibility Analysis

Problem

Provide a software application which enables the user to easily and efficiently access a

collection of healthcare tools which will both personalize the healthcare experience and optimize

overall health and wellness.

Problem Scope

Inside Scope

Provision of the following functionality: Patient portal interface, Appointment tracker, Rx tracker,

Telehealth device interface, Fitness tracker interface, Dietary tracker, and notifications or alerts

where appropriate.

Outside Scope

Provision of the following: A provider/patient portal, a telehealth device, a fitness-tracking

device, or a Dietitian.

Solution

A good solution will provide easy and efficient access to the functionality described within

”Inside Scope” above, notifications or alerts where appropriate, and weekly summations of

activity in order to support a user with reassurance and encouragement in the pursuit of health

care goals.

Alternatives

Provision of an application with less functionality.

Recommendations and Rationale

The ideal solution is to create the application containing the functionality described within ”Inside

Scope” above, along with the components described in “Solution” above. This collection of


elements addresses many important aspects of improving and maintaining a user’s well-being

and therefore achieves the goal of overall health and wellness.

Timetable and Expected Costs

This project plan will be complete at the end of Fall Quarter, 2014. A working prototype will be

complete at the end of Spring Quarter, 2015.

Costs will vary based on which hardware and software elements are used with this system. The

following mockup will be used to create an estimated cost for a typical implementation of this

software application.

Software Cost

Appointment tracker $0

Rx tracker $0

Dietary tracker $30

Interface software for user purchased components (Telehealth device, etc.) $0*

Additional software (Notifications, Alerts, Summaries) $0*

* Student application creator provided

Project Management Approach

This project is a Traditional Project Management type which will follow the Linear PMLC model

and use the Waterfall project approach. This is a Traditional Project type because it is of low

complexity, few scope changes are expected, the technologies involved are understood or

alternative strategies for project completion exist, it is of low risk and based on the requirements

and functionality, a complete project plan can be developed. The Linear PMLC model will be

used because this project has a clearly defined goal, solution, requirements, functions, and

features. Again, few scope changes are expected. Lastly, the activities of this project will be

repetitive. The Standard Waterfall model approach will be employed in this project both because

it is designed for software development projects and it is well established.


Cost and Benefit Analysis

Cost

Software Cost

Appointment tracker $0

Rx tracker $0

Dietary tracker $30

Interface software for user purchased components (Telehealth device, etc.) $0*

Additional software (Notifications, Alerts, Summaries) $0*

* Student application creator provided

Benefit

Tangible

80% increase in the level of user satisfaction regarding their healthcare experience

based upon pre and post application use surveys

80% increase in user sense of efficiency and effectiveness regarding product and

process improvement over currently available systems based upon pre and post

application use survey queries

Intangible

Improved sense of user well-being

Greater user level of satisfaction with their overall healthcare experience

Greater user sense of ownership over their healthcare experience


Use Case Descriptions

UC_01 – User Navigates to Patient Portal

Use Case Name: User navigates to Patient Portal ID: UC_01 Importance Level: High

Primary Actor: System User Use Case Type: Detail, Essential

Stakeholders and Interests:

System User - wants to navigate to Patient Portal

Brief Description: This use case describes how a user navigates to a Patient Portal.

Trigger: User clicks link to Patient Portal

Type: External

Relationships:

Association: System User

Include:

Extend:

Generalization:

Normal Flow of Events:

1. The user clicks on link to Patient Portal.

Subflows:

Alternate/Exceptional Flows:


UC_02 – User Logs On to Patient Portal

Use Case Name: User logs on to Patient Portal ID: UC_02 Importance Level: High



System User - wants to log on to Patient Portal

Provider - wants to meet patient needs

Brief Description: This use case describes how a user logs on to Patient Portal.

Trigger: User enters user name and password

Type: External

Relationships:

Association:

Include:

Extend: User Navigates to Patient Portal (UC_01)

Generalization:



2. The user enters user name and password.

3. System validates information.

4. User logged on to system.

Subflows:


1. System deems user information invalid.

2. User denied log on.


UC_03 – User Messages Provider

Use Case Name: User Messages Provider ID: UC_03 Importance Level: High



System User - wants to message Provider


Brief Description: This use case describes how a user messages a Provider.

Trigger: User clicks on Messaging link

Type: External

Relationships:


Include:

Extend:

Generalization:






5. User clicks link to Messaging.

6. User enters Provider name.

7. User composes and sends message.

8. Message is received by Provider.

Subflows:





UC_04 - User Views, Downloads, or Transmits Health Summary

Use Case Name: User Views, Downloads, or ID: UC_04 Importance Level: High

Transmits Health Summary



System User - wants to access Health Summary


Brief Description: This use case describes how a user accesses a Health Summary.

Trigger: User clicks Health Summary link

Type: External

Relationships:


Include:

Extend:

Generalization:






5. User clicks on Health Summary link.

6. User clicks View, Download, or Transmit link.

Subflows:





UC_05 – User Requests Appointment

Use Case Name: User Requests Appointment ID: UC_05 Importance Level: High



System User - wants to request appointment


Brief Description: This use case describes how a user requests an appointment.

Trigger: User clicks on Appointment link

Type: External

Relationships:


Include:

Extend:

Generalization:






5. User clicks link to Appointment.


7. User selects purpose of appointment.

8. User selects available appointment time.

9. Selected time entered into system.

Subflows:





UC_06 – User Views Test Results

Use Case Name: User Views Test Results ID: UC_06 Importance Level: High



System User - wants to view test results


Brief Description: This use case describes how a user views test results.

Trigger: User clicks on Test Results link

Type: External

Relationships:


Include:

Extend:

Generalization:






5. User clicks link to Test Results.

6. User selects test results to view.

7. System displays selected test results.

Subflows:





UC_07 – User Views Appointment History

Use Case Name: User Views Appointment History ID: UC_07 Importance Level: High



System User - wants to view appointment history


Brief Description: This use case describes how a user views appointment history.

Trigger: User clicks on Appointment History link

Type: External

Relationships:


Include:

Extend:

Generalization:






5. User clicks link to Appointment History.

6. User selects appointment history to view.

7. System displays selected appointment history.

Subflows:





UC_08 – User Records Appointment Time and Date

Use Case Name: User Records Appointment Time ID: UC_08 Importance Level: High

and Date



System User - wants to record appointment time and date

Brief Description: This use case describes how a user records an appointment time and date.

Trigger: User clicks Appointment Time and Date link

Type: External

Relationships:


Include:

Extend:

Generalization:


1. User clicks link to Appointment Tracker.

2. User clicks Appointment Time and Date link.

3. User enters appointment time and date.

4. System records appointment time and date.

Subflows:



UC_09 – User Enters Provider Name

Use Case Name: User Enters Provider Name ID: UC_09 Importance Level: High



System User - wants to enter Provider name

Brief Description: This use case describes how a user enters a Provider name.

Trigger: User clicks Provider link

Type: External

Relationships:


Include:

Extend:

Generalization:



2. User clicks Provider link.


4. System records Provider name.

Subflows:



UC_10 – User Enters Location

Use Case Name: User Enters Location ID: UC_10 Importance Level: High



System User - wants to enter location

Brief Description: This use case describes how a user enters a location.

Trigger: User clicks Location link

Type: External

Relationships:


Include:

Extend:

Generalization:



2. User clicks Location link.

3. User enters Location.

4. System records Location.

Subflows:



UC_11 – User Enters Purpose of Appointment

Use Case Name: User Enters Purpose of ID: UC_11 Importance Level: High

Appointment



System User - wants to enter purpose of appointment

Brief Description: This use case describes how a user enters the purpose of an appointment.

Trigger: User clicks Appointment Purpose link

Type: External

Relationships:


Include:

Extend:

Generalization:



2. User clicks Appointment Purpose link.

3. User enters purpose of appointment.

4. System records purpose of appointment.

Subflows:



UC_12 – User Enters Appointment Instructions

Use Case Name: User Enters Appointment ID: UC_12 Importance Level: High

Instructions



System User - wants to enter appointment instructions

Brief Description: This use case describes how a user enters appointment instructions.

Trigger: User clicks Appointment Instructions link

Type: External

Relationships:


Include:

Extend:

Generalization:



2. User clicks Appointment Instructions link.

3. User enters appointment instructions.

4. System records appointment instructions.

Subflows:



UC_13 – User Enters Questions for Provider

Use Case Name: User Enters Questions for Provider ID: UC_13 Importance Level: High



System User - wants to enter questions for Provider

Brief Description: This use case describes how a user enters questions for Provider.

Trigger: User clicks Provider Questions link

Type: External

Relationships:


Include:

Extend:

Generalization:



2. User clicks Provider Questions link.

3. User enters questions for Provider.

4. System records questions for Provider.

Subflows:



UC_14 – User Records Rx Name

Use Case Name: User Records Rx Name ID: UC_14 Importance Level: High



System User - wants to enter Rx name

Brief Description: This use case describes how a user enters an Rx name.

Trigger: User clicks Rx Name link

Type: External

Relationships:


Include:

Extend:

Generalization:


1. User clicks link to Rx Tracker.

2. User clicks Rx Name link.

3. User enters Rx name.

4. System records Rx name.

Subflows:



UC_15 – User Enters Rx Schedule

Use Case Name: User Enters Rx Schedule ID: UC_15 Importance Level: High



System User - wants to enter Rx schedule

Brief Description: This use case describes how a user enters an Rx schedule.

Trigger: User clicks Rx Schedule link

Type: External

Relationships:


Include:

Extend:

Generalization:



2. User clicks Rx Schedule link.

3. User enters Rx schedule.

4. System records Rx schedule.

Subflows:



UC_16 – User Enters Rx Dosage

Use Case Name: User Enters Rx Dosage ID: UC_16 Importance Level: High



System User - wants to enter Rx dosage

Brief Description: This use case describes how a user enters an Rx dosage.

Trigger: User clicks Rx Dosage link

Type: External

Relationships:


Include:

Extend:

Generalization:



2. User clicks Rx Dosage link.

3. User enters Rx dosage.

4. System records Rx dosage.

Subflows:



UC_17 – User Enters Bottle Pill Count

Use Case Name: User Enters Bottle Pill Count ID: UC_17 Importance Level: High



System User - wants to enter bottle pill count

Brief Description: This use case describes how a user enters a bottle pill count.

Trigger: User clicks Pill Count link

Type: External

Relationships:


Include:

Extend:

Generalization:



2. User clicks Pill Count link.

3. User enters pill count.

4. System records pill count.

Subflows:



UC_18 – User Activates Telehealth Device

Use Case Name: User Activates Telehealth Device ID: UC_18 Importance Level: High



System User - wants to take a biometric reading

Brief Description: This use case describes how a user activates a telehealth device.

Trigger: User presses button to perform test

Type: External

Relationships:


Include:

Extend:

Generalization:


1. User clicks link to Telehealth Device.

2. User presses button on telehealth device to perform test.

3. Device transmits biometric readings by Bluetooth connection to computer.

Subflows:



UC_19 – Users Transmits Telehealth Device Results to Provider

Use Case Name: User Transmits Telehealth Device ID: UC_19 Importance Level: High

Results to Provider



System User - wants to take transmit telehealth device results to Provider

Brief Description: This use case describes how a user transmits telehealth device results to a Provider.

Trigger: User clicks Transmit Results button to send biometric readings to Provider

Type: External

Relationships:


Include:

Extend:

Generalization:


1. User clicks link to Telehealth Device.

2. User presses button on telehealth device to perform test.

3. Device transmits biometric readings by Bluetooth connection to computer.

4. User clicks Transmit Results button to send biometric readings to Provider.

Subflows:



UC_20 – User Enters Fitness and Dietary Data

Use Case Name: User Enters Fitness and Dietary Data ID: UC_20 Importance Level: High



System User - wants to enter Fitness and Dietary data

Brief Description: This use case describes how a user enters basic Fitness and Dietary data.

Trigger: User clicks Personal Fitness and Dietary Data button

Type: External

Relationships:


Include:

Extend:

Generalization:


1. User clicks link to Fitness and Dietary Tracker.

2. User clicks Personal Fitness and Dietary Data button.

3. Users enters height, weight, age, gender, and activity level.

4. System records and processes personal fitness and dietary data.

Subflows:



UC_21 – User Enters Fitness and Dietary Goal

Use Case Name: User Enters Fitness and Dietary Goal ID: UC_21 Importance Level: High



System User - wants to enter a Fitness and Dietary goal

Brief Description: This use case describes how a user enters a Fitness and Dietary goal.

Trigger: User clicks Fitness and Dietary Goal button

Type: External

Relationships:


Include:

Extend:

Generalization:



2. User clicks Fitness and Dietary Goal button.

3. Users checks Lose Weight, Maintain Weight, or Gain Weight.

4. System records and processes user selection.

Subflows:



UC_22 – User Enters Foods Eaten

Use Case Name: User Enters Foods Eaten ID: UC_22 Importance Level: High



System User - wants to enter a foods eaten

Brief Description: This use case describes how a user enters foods eaten.

Trigger: User clicks Foods Eaten button

Type: External

Relationships:


Include:

Extend:

Generalization:



2. User clicks Foods Eaten button.

3. Users enters foods eaten.

4. System records and processes user entries.

Subflows:



UC_23 – User Enters Physical Activities

Use Case Name: User Enters Physical Activities ID: UC_23 Importance Level: High



System User - wants to enter physical activities

Brief Description: This use case describes how a user enters physical activities.

Trigger: User clicks Physical Activities button

Type: External

Relationships:


Include:

Extend:

Generalization:



2. User clicks Physical Activities button.

3. User enters physical activities.

4. System records and processes user entries.

Subflows:



UC_24 – User Connects to Activity Tracking Device

Use Case Name: User Connects to Activity Tracking ID: UC_24 Importance Level: High

Device



System User - wants to connect to an activity tracking device

Brief Description: This use case describes how a user connects to an activity tracking device.

Trigger: User clicks Activity Device button

Type: External

Relationships:


Include:

Extend:

Generalization:



2. User clicks Activity Device button.

3. User activates activity device.

4. System records and processes activity device data transmitted by Bluetooth connection.

Subflows:



Use Case Diagrams

Appointment Tracker System

Rx Tracker System


Telehealth Device System

Patient Portal System


Fitness and Dietary Tracker

Activity Diagrams

Record an Appointment


Enter Personal Data to Fitness/Dietary Tracker

Message Provider

Record Rx Name


Send Telehealth Device Results

Documentation Analysis

Since there is not an as-is system to examine documentation for, the documentation for

software systems bearing similar functionalities to the application envisioned for this project

were reviewed. The following websites provided information useful in determining functionality

that would be most beneficial to include in this project.

http://www.lifewatch.com/Telehealth-Products

https://play.google.com/store/apps/details?id=com.medisafe.android.client&hl=en

http://www.mytransplantlife.com/pdf/my-transplant-life-appointment-tracker.pdf

https://play.google.com/store/apps/details?id=com.myfitnesspal.android

http://www.lifewatch.com/Telehealth-Products

https://play.google.com/store/apps/details?id=com.medisafe.android.client&hl=en

http://www.mytransplantlife.com/pdf/my-transplant-life-appointment-tracker.pdf

https://play.google.com/store/apps/details?id=com.myfitnesspal.android


Entity Relationship Diagrams

Data Dictionary

The columns within the Appointments and Fitness Tables are self-explanatory so the following

data dictionary contains only information on the remaining tables.


Dataflow Diagrams

Appointment Tracker Dataflow Diagram

Fitness/Dietary Tracker Dataflow Diagram


Patient Portal Dataflow Diagram

Rx Tracker Dataflow Diagram


Telehealth Device Dataflow Diagram


Alternative Matrix

Criteria Option 1 Option 2 Option 3

Platform Desktop or Laptop Tablet Smartphone

Distribution Internet Internet or App Store App Store

Information Displayed High High Medium to Low

Operating System Windows Windows or Android Android

Network Access Required Wired or Wireless Wireless Wireless

Pros Large screen Ample screen size Easily portable

Physical keyboard Touch screen Touchscreen

Mouse Attachable keyboard

Virtual keyboard

Easily portable

Cons May or may not be portable Small screen

Touchscreen unusual Virtual keyboard

Conclusions A large screen size and a An amply-sized touch screen A small screen and

physical keyboard with mouse

with the ability to add a physical

no physical keyboard

make this a good option. keyboard combined with high option make this

portability make this the ideal choice the least

option. desirable.


As is clear from the matrix, a tablet would be the ideal platform on which to use this software application

due to its ample screen size, convenient touch-screen, portability, and the ability to add a physical keyboard.

A desktop or laptop would be a close second, particularly a laptop. However, a laptop would not be as

convenient to use, nor as portable as a tablet.

CRUDE Matrices

Patient Portal System

Appointment Tracker System


Rx Tracker System

Telehealth Device System

Communication Diagrams

User Generates Appointment Record


User Utilizes Fitness/Dietary Tracker

User Accesses Patient Portal


User Generates Rx Record

User Activates Telehealth Device

Sequence Diagrams (Generic-type)

User Generates Appointment Record


User Utilizes Fitness/Dietary Tracker

User Accesses Patient Portal


User Generates Rx Record

User Activates Telehealth Device


Project Storyboard, Interface and Output Designs

My Senior Project is the creation of an application called Health Tracker which is designed to

enable a user to easily access five separate software components through one interface thereby

simplifying the task optimizing overall health and wellness. These five components include a

Patient Portal, an Appointment Tracker, an Rx Tracker, a Telehealth Device (a glucose monitor

for this project), a Fitness Tracker (a Fitbit Flex for this project), and a Dietary Tracker (the Fitbit

Flex syncs to the Dietary Tracker so I’m considering both components as one unit).

The image displayed above is the icon that will serve as a hyperlink (“shortcut”) to the

application from a user’s tablet computer (the ideal platform) and will take the user to the Health

Tracker application home page seen in the next image.

This is the Health Tracker home page. There are five image hyperlinks the user can select from

to link to the five software components of the app. This storyboard will progress through each of

these five components displaying the interface designs of each component while describing

possible user scenarios for each component. The user can exit back to the home page from any

component.


The first component is the Telehealth Device, the Glucose Monitor. The image above shows the

hyperlink for the glucose monitor component.

Clicking the link to the glucose monitor component will launch the application associated with

this component. At this point, the user will connect the glucose monitor by Bluetooth to the

user’s tablet computer. After taking a blood sample, the device will upload the data to the tablet.

The user can take samples before and after a meal and have the resulting data recorded on the

tablet.

The image above shows a weekly graphical report of recorded data readings the user can view

and decide whether or not to share with a provider.

The image above shows the hyperlink to the second component, the Patient Portal.

I mentioned previously that I was unable to get a user log in to Kaiser Permanente which I was

planning on using for this component. However, I was able to gather enough information to

create the following scenario.


The image below shows the first page a user will reach upon clicking the Patient Portal

hyperlink, the log in page.

A successful log in will link the user to the page shown by the next image. From here, the user

can choose from three options (hyperlinks) to connect to one of three additional pages:

Message Center, Medical Records, or Appointment Center.

The image below shows the Message Center page which enables the user to send email to, or

receive email from a provider.

The next image shows the Medical Records page which allows the user to view any of the four

items displayed.


The following image shows the Appointment Center page which enables the user to either

manage appointments or prescriptions.

The next image shows the hyperlink to the third component, the Rx Tracker.

Upon clicking this link, the user will be taken to the Rx Tracker home page shown below. This

page will indicate the time of day when medication is due to be taken. In addition, this page will

contain hyperlinks which will enable connection to pages where a medication can be added

(plus sign icon), a “medicine cabinet” list of current medications will be displayed (briefcase

icon), and lastly, a page showing the number of days left in a medication supply will be indicated

(document icon).


The next image shows the hyperlink to the fourth component, the Fitness and Dietary Tracker.

Upon clicking the link above, the user is taken to the Fitness and Dietary Tracker home page

shown below. It has hyperlinks to a daily Food Diary page, a Nutrition Detail page, a Recipe and

Food List page, a Progress page, and a Goals page. A fitness monitor such as a Fitbit Flex can

be synced to this component and the data from the device reflected in the Progress and Goals

pages.

The next image shows the hyperlink to the last component, the Appointment Tracker.

Upon clicking the link above, the user will be taken to the home page of this component

displayed below. A user can indicate an Office Visit, Hospital Visit, or a Lab Test, and link to a

calendar showing existing events also displayed below.


Events will be indicated in red. A user can click on an indicated event day for a full description of

the event(s) occurring on that day.


Package Diagram

This package diagram depicts UML use-case diagram systems organized into packages

indicating dependency relationships between packages. The following lists describe the

contents of each package:

Medical Therapy package

Rx Tracker system

Telehealth Device system

Health Management package

Appointment Tracker system

Patient Portal system

Health Promotion package

Fitness & Dietary Tracker system


Physical Architecture

Architectural Components

Software

Presentation logic

Application logic

Data access logic

Data storage

Hardware

Client computer: tablet computer

Servers

Network

Client-Server Architecture

This type of architecture will balance the processing between the client and the server. The

server will provide the majority of the processing resulting in a “thin-client” design. That is, the

web browser on the client side will perform presentation processing with minimal application

logic processing, while the server side will process application logic, data access logic, and data

storage.

Client-Server Tiers

Application logic will be divided between the client and the server in two possible ways: a three-

tiered architecture, or an n-tiered architecture.

Three-tiered architecture employs three sets of computers. Software on the client

computer will perform presentation logic. One or more application servers will process

application logic. Lastly, one or more database servers will perform data access logic

and data storage.

N-tiered architecture employs more than three sets of computers. The client computer

will perform presentation logic. Database servers will process data access logic and data

storage. Lastly, two or more different sets of servers will perform application logic.


Deployment Diagram

The following diagrams will represent how the software components are deployed over two

possible physical architecture formats.

Three-tiered architecture

N-tiered architecture


Hardware and Software Specifications for Client

Operating System

Android 4.0 >

Google Chrome or Internet Explorer

Hardware

1 GB RAM

1 GB HDD

iHealth Gluco-Monitoring System

Fitbit Flex fitness band

Network

100 Mbps Ethernet (wired or wireless)


Logical Architecture

Note: Arrows represent Data Flows in the following diagrams.

Appointment Tracker

List of processes:

User enters Time and Date

User enters Provider

User enters Location

User enters Purpose of Appointment

User enters Appointment Instructions

User enters Questions for Provider

Data processed by application on server

User Requests Appointment Data

Appointment Data returned


Fitness/Dietary Tracker

List of processes:

User syncs data from Fitbit to application on browser

User enters Biometric Data

User enters Weight Goal

User enters Foods Eaten

User enters Physical Activities

Data processed by application on server and any requested data returned

User views any requested data


Patient Portal

List of processes:

User logs on

Application on server verifies user identity

User requests to View or Download Health Summary

User transmits Health Summary

User requests Test Results

User requests Appointment History

User Messages Provider

User requests Appointment



Rx Tracker

List of processes:

User enters Rx

User enters Rx Schedule

User enters Rx Dosage

User enters Pill Count

User requests Rx Data



Telehealth Device

List of processes:

User Bluetooth connects Glucose Monitor to tablet computer

After user takes a blood sample, Glucose Monitor uploads data to application on tablet

computer

Data is processed by application on server and processed data returned

User can choose to send test results data to provider


Testing Plan

Unit, Integration, System, and Acceptance testing will be performed for each of the main

components of this application: Patient Portal interface, Appointment Tracker, Rx Tracker,

Telehealth Device interface, and Fitness & Dietary Tracker.

Unit Testing

All functions of each component will be individually tested to determine whether they are fit for

use, meet design requirements, and behave as intended.

Integration Testing

Each component will be tested as a whole system to verify functional and performance

requirements. A type of Big Bang Integration testing called Usage Model testing will be

employed to test each component. This approach utilizes realistic, user-like scenarios to test a

system as a whole, while individual functions are tested indirectly through their use. This

strategy will make evident any problems within a system. The creation of accurate, user-like

testing scenarios is essential for this strategy in order to ensure a system will meet actual user

expectations.

System Testing

Each component will be tested for problems which may exist between functional elements as

well as within each component system as a whole. System design, behavior, and expectations

of the user will be examined. Graphical user interface, usability, and software performance

testing will be conducted.

Acceptance Testing

A User Acceptance Testing approach will be employed to ensure that each component of this

application meets user expectations. Users of this application will perform tests which reflect

real-life scenarios. This testing approach will provide final verification that this system meets

required functionality.


Alpha Stage of Application

I will perform the role of a prospective system user and utilize real-life scenarios in the testing of

each component of this application.

External user acceptance testing will be employed to perform similar tests to ensure this

application has few faults. This will provide beta testing of this application.

Conversion Plan

Conversion is typically a process by which a new system replaces an old one. In the case of this

project, the Health Tracker application is original and not expected to be a replacement for

another system. Conversion includes a migration plan. While migration plans include technical

and organizational aspects, conversion focuses on the technical aspects of this plan. For this

project, this will include hardware and software installation of the to-be system. At this time

migration plan activities will be performed by me as the need arises.

A conversion plan involves three steps before a new system becomes operational: hardware

installation, software installation, and data conversion. For this project, hardware installation

may include the purchase of a client computer, networking equipment, and possibly a printer.

Installation of the Health Tracker application and any additional software needed to make the

system operational will be installed next. The last step, data conversion, will not be required

since there will be no conversion of data from an as-is system to a to-be system. Once this

process is complete, the system will be tested to ensure proper operation.

Conversion is also described by three dimensions: conversion style, conversion location, and

conversion modules. This project will employ a direct conversion style which typically involves

the deployment of a new system to replace an old one. In this case, a new system will simply be

deployed. Conversion location describes the physical location where conversion will take place.

With regards to this application, deployment will occur anywhere it is desired, at any time.

Conversion modules refers to component parts of a system that may not all be installed at the

same time. In the case of this project, a whole-system conversion will take place. That is, the

system in its entirety will be deployed at one time.

Lastly, it is important to consider risk, cost, and time required when choosing a conversion

strategy. This project will employ a direct conversion style which is considered the most risky


because this is the last opportunity to catch any bugs before the system goes live. However, this

risk is mitigated by alpha and beta testing of the system thereby rendering risk factor less

significant to the decision of which conversion strategy to use. The conversion methods this

project will employ will incur the least cost relative to other conversion strategies. Finally, direct

conversion is the fastest of the conversion strategies.


Health Tracker

User’s Guide

An online version of this guide is available at http://www.healthtracker.com

Dave Siegel

Oregon Tech

27500 SW Parkway Ave

Wilsonville, OR 97070


Table of Contents

About Health Tracker ……………………………………………………………………………………………… 78

Chapter Contents …………………………………………………………………………………………………….. 78

Installing Health Tracker ………………………………………………………………………………………...79

Quick Start ……………………………………………………………………………………………………………….79

Chapter 1: Telehealth Device …………………………………………………………………………………...80

Chapter 2: Patient Portal …………………………………………………………………………………………80

Chapter 3: Prescription Tracker ……………………………………………………………………………...82

Chapter 4: Dietary and Fitness Tracker …………………………………………………………………..85

Chapter 5: Appointment Tracker …………………………………………………………………………….85


About Health Tracker

Congratulations on your decision to play an integral role in the optimization of your health and

wellness. This tool will simplify the tasks of accessing health care providers, keeping track of

appointments, keeping track of current and new medications, using telehealth devices,

displaying fitness regimens and goals, and lastly, keeping track of dietary restrictions. These

functions are accessed through a simple five icon interface.

Chapter Contents

The following is a short description of each chapter in this guide.

Chapter 1: Telehealth Device

Health Tracker can be configured to accommodate one of several commonly used telehealth

devices such as a glucose monitor, a cardiac monitor, or a blood pressure monitor.

Chapter 2: Prescription Tracker

This component enables the tracking of new and current medications including dosage, time of

consumption, and supply remaining.

Chapter 3: Appointment Tracker

Appointments including office visits, hospital visits, or lab tests can be tracked as well as

additional information relating to these events.

Chapter 4: Patient Portal

Health Tracker can be configured to link to any patient portal.

Chapter 5: Dietary and Fitness Tracker

This component will track foods consumed and the nutritional value of those foods. The

nutritional value of recipes and many popular foods can be displayed. Nutritional goals can be

set and a progress report of those goals will be displayed. In addition, any of several wearable

fitness devices such as a Fitbit can be synced to this component and recorded activity will be

reflected in the reports displayed.


Installing Health Tracker

Requirements

Desktop computer, or laptop

Microsoft Windows 95/98/2000, Windows NT 4.0, or higher

Minimum RAM: 16 MB (32 MB for Windows NT)

Minimum hard drive space required: 60 MB

Internet access

Patient portal availability

Telehealth device, such as a glucose or blood pressure monitor

Fitness tracking device, such as a Fitbit

Dietary program provided by a dietician if desired

Basic computer-use skills, such as navigation and user/password use

Software Installation

This application can be downloaded from http://www.healthtracker.com or installed by DVD. Follow

on-screen instructions to complete installation.

Quick Start

Users with basic computer-use skills, as well as instruction manuals for a chosen telehealth

device and wearable fitness device, will find the interface of this application very user-friendly

and should feel confident to explore the application’s components using the remainder of this

guide as a reference.

Simply click on the Health Tracker shortcut icon to begin.

http://www.healthtracker.com/


Chapter 1: Telehealth Device

Clicking the Health Tracker icon shown above will take the user to the main

interface of the application shown at left. The arrow on the image indicates

the location of an icon link for a telehealth device, in this case a glucose

monitor. Clicking on the link will take the user to that component. Since this

application can be configured with one of several different telehealth

devices, the user should refer to the documentation supplied with a given

telehealth device for further instructions on its use. After use of the

component is complete, the user can return to the main interface by clicking the X in the upper

right of the browser window displaying the component, thereby returning to the Health Tracker

main page.

Chapter 2: Prescription Tracker

Clicking the icon link indicated by the arrow will take the user to the

Prescription Tracker component. The home page displayed offers the user

a number of options to choose from including My Meds, Pill Time, and Log.

These are the essential functions, but in addition, there are To Do, 911

Info, and Help buttons.

Choosing My Meds will take the user to a window where medication names, dosages, provider

name, and other related information can be recorded. Simply enter all desired information for

each medication in the appropriate text boxes. Click the “New Med” button on the lower right

when finished to record the entries. To delete all information regarding a medication, click the

“Delete” button at the bottom of the window. Only one medication can be entered at a time.


From this window, or the home page of this component, the user can click the Pill Time tab at

the top of the window to connect to the Pill Time function. This feature offers a dual window. On

the left side is presented a list of medications due on today’s date. On the right, a user can set

up a monthly schedule of medications to be taken on a given day. Entries in these two displays

can be modified by clicking the appropriate button at the bottom of each display.

From this window, or the home page of this component, the user can click the Log button at the

top of the window to connect to the Log function. This feature offers a means to keep track of

whether or not a medication has been taken, and when it was taken. This log can be cleared by

clicking the Purge Log button at the bottom right.


The remaining features of this component operate in the same manner. After use of this

component is complete, the user can return to the main interface by clicking the X in the upper

right of the browser window displaying the component, thereby returning to the Health Tracker

main page.

Chapter 3: Appointment Tracker

Clicking the icon link indicated by the arrow will take the user to the

Appointment Tracker component. This component opens to a calendar

home page where the user can choose from among several options. For

appointment creation and tracking, the user should focus on the New

Event, New Recurring Event, Today, Calendar, and Events buttons.


Clicking the New Event button at the top left of the window will take the user to a window where

a non-recurring appointment can be recorded. The user will enter appropriate information in the

text boxes provided, and click the “Save and Close” button at the top left of the window when

finished.

Clicking the New Recurring Event button will take the user to a window where a recurring

appointment can be recorded. Information will be entered, and recorded in the same manner as

the New Event window.


The user can click the Today button at the bottom left to view appointments scheduled on the

current date.

The user can click the Calendar button at the bottom left to view appointments scheduled over

the course of a given month (Please see first image of this chapter).

Lastly, the user can click the Events button to view all events recorded, the current day’s events,

events forthcoming in the next 7 or 30 days, and overdue events.


Once finished recording appointments, the user can close the component by clicking the X in

the upper right of the browser window displaying the component, thereby returning to the Health

Tracker main page.

Chapter 4: Patient Portal

Clicking the icon link indicated by the arrow will take the user to the Patient

Portal component. The interface and operation of this component will vary

based on the Patient Portal available from a given provider. Documentation

from a user’s provider will provide detail on the use and content of any

Patient Portal that is configured for this application. After use of this

component is complete, the user can return to the main interface by

clicking the X in the upper right of the browser window displaying the

component, thereby returning to the Health Tracker main page.

Chapter 5: Dietary and Fitness Tracker

Clicking the icon link indicated by the arrow will take the user to the Dietary

and Fitness Tracker component. This component opens to a home page

which offers the user several options from which to choose. The user

should focus on the Food, Exercise, and Reports tabs located at the top of

the window.


Clicking the Food tab will take the user to a window where a daily diary of foods consumed over

the course of a day can be recorded and the nutritional value of those foods tracked. Users click

on the “Add Food” link located under a desired meal time such as “Breakfast,” enter a food

consumed in the provided text box, click the “Search” button to add detail to the entry, and then

click the “Add Food To Diary” button on the bottom right of the window to record that food and

track its nutritional value.

Clicking the Exercise tab will take the user to a window where cardiovascular and/or strength

training exercises performed on a given day can be recorded. Users click the “Add Exercise”

link under “Cardiovascular” or “Strength Training” categories, enter an exercise in the provided


text box, click the “Search” button to add detail to the entry, and then click the “Add Exercise”

button on the bottom right of the window to record the exercise and track calories burned.

Clicking the Reports tab will take the user to a window where the user can view a report

reflecting various aspects of “Progress,” “Nutrition,” or “Fitness,” such as weight, calories

consumed, or calories burned, respectively. To choose a report, the user clicks the down arrow

on the text box at the top of the window, and clicks on a topic from the “Progress,” “Nutrition,” or

“Fitness” categories. A graphical report of the topic chosen will then be displayed in the Reports

window.


The user can close this component by clicking the X in the upper right of the browser window

displaying the component, thereby returning to the Health Tracker main page.

In addition, an activity tracker such as a Fitbit band can be synced to this application

component, and any recorded activity along with the calories burned will be reflected in the

Reports function results. A list of activity trackers that are compatible with this component are

listed under the Apps tab located at the top of the component window.


Health Tracker

Administrative User Manual

Dave Siegel

Oregon Tech

27500 SW Parkway Ave

Wilsonville, OR 97070


Table of Contents

Introduction ……………………………………………………………………………………………………………… 91

Installation and Configuration of Health Tracker ……………………………………………………. 91

Testing ……………………………………………………………………………………………………………………… 92

Documentation and Instruction ……………………………………………………………………………….. 92


Introduction

This manual provides a guide to follow in order to complete the process of installation of the

Health Tracker application for an end user. Note: Please complete all steps.

Installation and Configuration of Health Tracker

Installation and configuration of this application will vary based on the needs of the user with

respect to the following three components: Telehealth Device, Patient Portal, and Fitness

Tracker. Documentation associated with these components will need to be provided by the user

in order to complete their installation and configuration.

Step 1: Verify the user meets the following requirements:

Has a desktop or laptop computer

Microsoft Windows 95/98/2000, Windows NT 4.0, or higher is installed

Minimum RAM: 16 MB (32 MB for Windows NT)

Minimum hard drive space required: 60 MB

Internet access

Patient portal availability and user documentation (if functionality is desired)

Telehealth device and user documentation (if functionality is desired)

Fitness tracking device (if functionality is desired)

Dietary program provided by a dietician (if desired)

Step 2: Software Installation

Download and install the Health Tracker application to the user’s computer from

http://www.healthtracker.com , or install application with the DVD included with the product

documentation purchased by the user. Follow on-screen instructions to complete installation.

If the user has Patient Portal availability, and associated documentation, configuration will be

required for this component, but there is no software that will require installation.

If the user has a Telehealth Device, and associated documentation, this component can be

installed by following the documentation provided. Installation will completed by connection of

the device to the user’s computer, software download from the device manufacturer, or by DVD

included with the device.

http://www.healthtracker.com/


If the user has a Fitness Tracker device, and associated documentation, this component can be

installed by following the documentation provided. Installation will be completed by download of

an application associated with the device from the device manufacturer, or the “Apps” tab on the

Dietary Tracker component of the Health Tracker application. Next, a USB antenna stub

associated with the device will be connected to the user’s computer.

Step 3: Configuration

The Telehealth Device, Patient Portal, and Fitness Tracker will require configuration based on

the needs of a particular user with respect to each of these components. After installation of any

required software is complete, the programming code behind the image hyperlinks which

connects the user from the Health Tracker home page to the Telehealth Device and Patient

Portal components must be modified to enable these components to activate on request from

the user. Changes made to the programming code will be dependent on a particular Telehealth

Device or Patient Portal. The Fitness Tracker will need to be linked to the Dietary Tracker

component of the Health Tracker application. This task can be completed from within the

Dietary Tracker component itself, and enables all activity recorded on the Fitness Tracker to be

reflected in the Dietary Tracker component.

Step 4: Testing

After installation and configuration of the Health Tracker application is complete, each

component will be tested with the direct involvement of the user. This step serves two purposes:

First, it tests the functionality of each component; second, it gives the user an introductory

lesson in application use.

If any component is not operating up to required functionality, troubleshooting will be performed

until the component is functioning up to specifications. Any components requiring

troubleshooting will be retested once troubleshooting is complete to verify required functionality

has been met.

Step 5: Documentation and Instruction

The User’s Guide and relevant documentation should be referred to while the user is being

guided through the execution of each component of the Health Tracker application. The user

should be directly operating each component of the application while any necessary instruction


is provided. Each component of the application should be executed three times in this manner

to ensure confident operation on the part of the user, as well as provide a final user test of the

system.

After instruction is complete, indicate that any further questions or customer service needs

should be directed to the website at http://www.healthtracker.com.


Miscellaneous Documentation

Miscellaneous documentation for the Health Tracker application will vary based on particular

user needs or choice. This will include documentation for the following: a Telehealth Device; a

Patient Portal; and a Fitness Tracker.

Training Plan

Users

This training plan would focus on users with little or no computer literacy. Users of the Health

Tracker application who fall into this group would be coupled with a trainer who would utilize the

Administrative User Manual to instruct the user on how to use this application. The trainer would

follow the procedures laid out in this manual thereby enabling the user to employ the full

functionality of this application.

The trainer would follow up with the user two weeks after the initial training session, and two

weeks thereafter. Troubleshooting or other support would be provided at these times. In

addition, the trainer would remind the user that the website at http://www.healthtracker.com is

always available if any questions arise, or further assistance is needed.

Trainers

Individuals selected to provide training would possess moderate computer literacy prior to

hiring. These individuals would be fully trained in the use, installation, and configuration of the

Health Tracker application. Configuration skills would include knowledge regarding how to

modify portions of the programming code on which the application operates so that each

installation can be tailored to a particular user. In addition, these trainers would receive

instruction on how to effectively interact with users of various age groups and computer skill

levels.


Implementation Strategy and Plan

Implementation

The Health Tracker software application implementation strategy and plan will follow a “Big

Bang” style of adoption in that the entire system will be released to the user at one time. This

allows for a shorter implementation time, and any pain or frustration on the part of the user will

be condensed into one time period, versus being drawn out. In addition, this approach would

result in lower costs where training is required.

Users with a basic level of computer literacy could purchase and use this application with no

assistance necessary; users with little or no computer literacy would be provided with a trainer

at minimal cost.

Users/Customers

Potential users of the Health Tracker application would be found from within the ranks of

patients associated with care providers. Relationships with providers would be forged by

demonstrating the utility and many benefits this application could provide to patients thereby

motivating providers to encourage patients to purchase and use this application. This would

form the primary distribution path for this application. Other avenues which may yield users

include insurance companies and medical journals. A marketing effort could be extended to

insurance companies wherein a strategy similar to that used with providers could motivate a

drive to further encourage providers to suggest this software application to patients. From the

insurance company perspective, this software system could lower medical costs.

Advertisements placed in medical journals could also generate interest for this software

application.

Time Frame

Users who possess a basic level of computer literacy can purchase, install, and expect to gain a

full understanding in the use of this application within two days. Users who possess little or no

computer literacy can expect to develop a basic understanding in the use of this application

within one day with the instruction of a trainer. A full understanding may require two additional

instructional sessions, spaced at two weeks after the initial instructional session, and again at


four weeks after the initial instructional session. Each of these instructional sessions will require

less than one day.