Project Charter
Project Title
Health Metric Sharing System
Product/Process Impacted
Start Date
Target Completion Date
1/20/2016
4/15/2016
Organization/Department
Champion
Doctor/Patient
Interaction
(Information
Sharing)
Health care
Description
1. Project Description
What problem is the team addressing? What problems do customers have?
The project team is giving customers of wearable technology the ability to store their health data on their mobile
devices (collected by electronic health tracking system). The user can then share/export their data to their
physicians, and have an open conversation about their health data. This “open conversation” means that both the
doctor and user have a place (outside of the doctor’s office) to converse about their health data once it is shared.
The application will create a place to share test results, health data, and any questions regarding a patient’s health.
2. Project Scope
What areas are inside and/or outside the work of the team? What are the boundaries (start and end points)? What
specific parts of the overall problem will you focus on?
The team will work on exporting the health data from the wearable technologies applications. The team will also
build an application for health physicians, and consumers to help communicate and discuss the data that is
collected. Our app will focus on an information sharing system between doctor and patient with the ability to share
notes on health metrics. This app will not provide users with any information other than their health, metrics &
dietary intakes, and only allow the patient and the party they agree to share data with access to their data
Metrics
(propose specific
metrics for your
project, e.g., cost
Baseline
Current
Goal
3
1. Project Goal and Deliverables
What must the team deliver to be successful?
Does the team goal link to the key performance
parameters established by the sector leadership
teams? What is the baseline performance? How
will the goal be measured?
The team must deliver a way for health
physicians, and patients to share data
collected from wearable technology. The
team must deliver a way to have
conversations about the data collected.
reduction, time
reduction, customer
satisfaction, etc.)
Time reduction in
the doctor’s office
(Doctor will
already have insight
into patients data
allowing them to
prepare for
appointment prior
to said
appointment)
More accurate data
to discuss patient
health
Open
communication
with the health
physician
5. Team members
1.5 Hours
.5 hours
assumptions
made by each
party
assumptions
made by each
party
accurate data from
wearable technology
2 hours
2 hours
.5 by reply of an email
using the application
We want to better the lives of our customers first and foremost. Our application will be marketed strictly to
doctors (specifically physicians, PCPs). We plan on creating revenue through a subscription service. We will
charge a subscription fee for our service to doctors; these doctors will then charge a fee to their patients that
choose to use our application.
There are many other ways that we plan on creating revenue if our application is a success in our target market
(doctors). Including…
 An idea similar to that of Progressive’s “snapshot” where a customer is given benefits or a reduced charge
if their health metrics exceed the standards that we would have each health insurance company create
independently.
Who is this team accountable to? Who is your champion? Who is on this team? What are the specific skills/roles of each
team member? Who can the team turn to for expert guidance?
Megan Gallagher: JustInMind experience
Eric Miller: JustInMind experience
Melissa Mulvey: Experience using FitBit and their applications
Luckily our team members have been on the same teams for projects in the MIS program in the past. We know that Megan
and Eric both have used JustInMind before and will be asked to build the Prototype for our application. Melissa is a
firsthand user of FitBit so she will be or SME on all things related to the FitBit technology. All members have familiarized
themselves with the capabilities of FitBit and JustinMind so we can each provide our own unique insights on each aspect of
the project.
4
4. Business Results
Expected
1.5 hours
6. Support Required
and risks
What additional resources does the team need? What obstacles does the team see, and how can they be resolved?
The team will need access to health application data, which will require users to enter agreement with Fitness connect to
access and share their data with ONLY the parties the user agrees to. (For example Eric may say his data is only to be
shared with primary physician and no other medical practitioners) The team may be able to get a hold of the health
application data by contacting FitBit (or other health metric tracking device) and seeing if there is a way to merge the two
applications. The team has done their research and found that the sharing of this information does not violate any HIPPA
laws or other laws related to doctor/patient confidentiality or information sharing.
8. Technology
Architecture
How will this project help the customer of the organization? Could improvements have a negative impact on the customer?
Our customers will be able to receive more accurate diagnosis’ from their doctor’s which can result in a healthier patient.
Because of their ability to have an open channel of communication who can offer insights on the patients’ health based on
their health data. We will also be decreasing the amount of time a doctor will have to meet with his patients because he will
already be updated weekly/monthly ext. on their health status so there is less time needed to talk, diagnose and recommend
treatment for each patient. Reducing time in the doctor’s office is good for the doctor because they can see more patients in
a day and the patients will be able to allocate more of their time to other activities.
What are the specific tools/technologies you will be using? What is the experience of team members with these tools?
We will be using a FitBit as our form of health metric tracking device, other health metric tracking tools can/will be used
for testing.
JustInMind will be the main program we use to display and create the prototype for this application
9. Overall schedule/Work Breakdown
Structure (Key milestones & dates)
Responsible
individual
Planning
Entire Team
Date completed or
Output (notes, diagrams, Date started if in
date completion is
interviews, screen prints) progress
Or Expected
expected
completion date
Completed
February 16
Diagrams, notes
Analysis
Eric,Melissa
Notes, interviews
In progress
March 15
Design
Eric
Screen prints
In Progress
April 13
5
7. Customer Benefits
Megan
Diagrams
March 14
April 16
Implementation: Testing
Melissa
Notes
April 10th
April 18
Installation
Megan
Screen prints
April 12
April 18
6
Implementation: Construction
7