uc and prototyping

Health Care Self Insurance and consulting Group

ASSIGNMENT 3: UC and Prototyping (Wellness Activity Tracking System)

JASH MEHTA

GROUP 3

Mentor: Kshitij Chug

Weekly meeting time (Group meeting): Wednesday 3-4pm

Weekly meeting time (Group + Mentor meeting): Wednesday 4-5pm

Venue: Ice Box, Hinds Hall

Jash Mehta 1


CONTEXT

Overview of the company, current scenario and the future.

Healthcare in the USA is going through a serious crisis. The spending of the USA on healthcare is 2X per capita than other industrialized nations. Medical bills are a major factor in more in more than 60% of the personal bankruptcies in the

USA, 75% have health insurance. Between 2000 and 2006 health insurance premiums rose 87% and the average wages rose by

3.8%. In spite of this the USA ranks 37th in healthcare system. The fully insured plans are expensive and hence one of the reason for the crisis in healthcare

economy. The alternative to fully insured plan is the self-insured plan. In this, the employer retains a

portion of the risk and instead of large premiums the employer pays the administrative bills and stop loss company’s bills which are generally much lower than the monthly premium of fully insured.

Healthcare self-insurance and consulting Group offer customers with variety of services to our clients. We encourage many wellness activities, promote self-management through healthcare Apps and increased patient clinician interaction. Providing such services requires building an IT infrastructure and systems which can support huge volume of customers. In this document we have designed the use case diagram and a prototype. The purpose of the use case diagram in this document is to describe the system from perspective of all stakeholders. The use case diagram brings out all the requirements of the system from the viewpoint of all the stakeholders. The actor glossary, use case glossary, use case table and the use case narrative are provided along with the diagram to understand the diagram in detail.

This document also includes a prototype for the login, browsing and customer RSVP.

Our company is the only consulting group which uses various technologies so it becomes necessary to remain competitive in the market. In short the UC and prototype brings out the requirements from the viewpoint of the stakeholders.

Jash Mehta 2


Jash Mehta 3


Actor DescriptionWellness Activity and Planning Centre (WAPC)

The WAPC plans all the wellness activities based on the alerts generated by MTAS system. It decides to plan for nutrition seminar if the MTAS alerts that many customers are suffering from diabetes/ heart disease. It sends these plans to Enrollment Department (ED). Based on the RSVP count of the patients it finalizes the plans with the nutrition specialists and decided venue, time etc. After the wellness activity it also collects online feedbacks from customers. It also collects feedback from MTAS regarding health of the customers post the wellness activity. This department analyses these feedbacks and creates success reports based on the feedbacks.

Enrollment Department (ED)

It receives the initial plans of the wellness activities from the WAPC. The ED gives the access of its system information (database) to the NAF component of the wellness activity tracking system. The information from this Database contains the information of all the customers enrolled in the university.

Medical Tracking and Alerts System (MTAS)

This system also gives access to the ED regarding the medical information based on this information WAPC plans activities. This system also gives the access to the NAF component of the wellness activity tracking system. The information from this Database contains information regarding the health of the customers. People having diabetes will be alerted by NAF regarding an upcoming nutrition activity. This system is also responsible for reporting the health status of the customers post the wellness activities as feedbacks. This helps WAPC determine the success of the seminar.

Verification and Validation (V&V)

This component in the wellness tracking system has two responsibilities: 1) Authentication when user login in the system 2)Testing eligibility of the customers for the RSVP (if someone has breathing problems he/she cannot participate in the marathon wellness activity)

Finance Department

The job of this department to access the information from the of the wellness activity tracking system to determine the RSVP customers. Based on the RSVP count the budget for the wellness activities can be decided.

Customers (University)

The user/customer will receive notifications via healthcare Apps or Web Portal. The user/customer will login in order to RSVP for the seminar provided that the customer is registered user. Once he/she successfully logs in then he/she can RSVP for wellness activities based on the eligibility, this notification is sent to NAF component which registers into the DB. When the customer is attending the wellness activity he/she should swipe the ID card in the system, this gives an idea of how many customers turned up for the seminar after RSVP. Customers can also provide ID no. on the website if they are attending live or recorded webinars. After the wellness activity the customers will be asked to fill online forms which will be a short survey/feedback. These feedback are received by WAPC.

Notification and Fetch (NAF)

This component is a part of the wellness tracking system. It receives notification from various actors and also send notifications to various actors. It sends notifications to the customers via healthcare Apps and web portals. Also, in the case of erroneous login credentials or error in RSVP, this component notifies the customer regarding the error.

Actor Glossary

Jash Mehta 4


Use Case Glossary

Use Case Name Use Case Description Participating Actors Accessing Database of Wellness System

This use case describes the event where the WAPC or/and Finance Department access Database of the wellness tracking system. This database is accessed to get an estimate of how many customers will attend the following wellness activity. Depending on this estimate the WAPC finalizes (venue, time etc.). Also, depending on this estimate the Finance Department decides the budget for the event.

Finance Department, Wellness Activity Planning Center (WAPC)

Planning Wellness Activities

This use case describes the event where the WAPC creates initial plans for the wellness activities. This wellness activities could be planning a yoga session, marathons or nutrition seminar. The WAPC reaches out to the sponsors, yoga teacher or dietician to conduct seminars. However, these are rough plans (approximate data and venue).

Wellness Activity Planning Center (WAPC)

Planning Mental Health Activities

This use case describes the event of planning activities like Yoga sessions and Meditation sessions.


Planning Physical Fitness Activities

This use case describes the event of planning physical activities such as marathons, morning jogs, gym training etc.


Planning Nutrition activities

This use case describes the event of planning seminars with dieticians.


Sending Plans This use case describes the event where the initial or rough plans of WAPC are sent to the Enrollment Department.


Finalizing based on RSVP

This use case describes the event where the WAPC finalizes (date, venue, time etc.) plans based on RSVP count. This use case comes into the picture after the wellness activity tracking system’s information is accessed by the WAPC.


Receive Feedback This use case describes the event where the WAPC receives feedback from the customers. Customers write online feedbacks for the wellness activities they have attended. The WAPC also receives the medical health information, of the customers, as a feedback from the MTAS on regular basis.


Analyze Feedback This use case describes the event where the WAPC analyzes the feedback given by the customers. It also analyzes the medical health information which is the feedback given by


Jash Mehta 5


MTAS. Analyzing these feedbacks helps to decide whether the wellness activities are going well and it is on the right track.

Generate success Reports

This use case describes the event post analyses stage. It basically generates reports for each wellness activity for the top management of the company. These reports are generated based on the number of people attended the wellness activity, positive or negative feedback given by the customers, positive or negative medical health information received from MTAS.


Receive Plans This use case describes the event where the ED receives the initial or the rough plans from the WAPC. As soon as the department receives the plans it know it has to give the access of the information of the customers enrolled in the company. The access is given to the NAF component of the wellness activity tracking system.


Giving Access of DB to NAF component

This use case describes the event where the ED gives access of the customer information to NAF component. Giving access means giving important information of the customers (customer ID, customer name etc.) via which they can be notified. The MTAS also gives access of its system information to the NAF component. For example: suppose the NAF component finds set of customers with diabetes and the upcoming wellness activity is nutrition seminar, in this case NAF will send special notifications to these customers.

Enrollment Department (ED) & Medical Tracking and Alerts System (MTAS)

Tracking Medical Information and giving alerts to WAPC

This use case describes the event where the medical information of the customers is tracked regularly. Each visit to a doctor is tracked and the results of the medical health are recorded. This system also tracks the medical health of the patient post the wellness activities. This system also sends alerts to various systems. For example: If there are set of customers who have problems in concentrating or anger management then this will be alerted to the WAPC. The WAPC can use this information to make rough plans OF Yoga Sessions in the future.

Medical Tracking and Alerts System(MTAS)

Reporting Medical Health of customers

This use case describes the event where the MTAS monitors the health of the patient post


Jash Mehta 6


post wellness activities as a feedback to WAPC

wellness activities. This can be achieved by asking the customer to update the health information in their system. This information is sent to the WAPC. WAPC uses this information to determine the success of the wellness activities and also to plan future activities after analyzing the health information of the customers.

Checking Authenticity and Eligibility

This use case describes the event where V&V just have the job of authenticating the login and verifying the eligibility for RSVP.


Deciding Budget based on RSVP

This use case describes the event where the Finance department decides the budget based on the RSVP count.

Finance Department

Login This use case describes the event where the user/customer logs in to the system via the healthcare Apps or the website.

Customers(University)

RSVP This use case describes the event wherein after logging in the system, the user/customer RSVP wellness activity.


Swiping Cards in the System

This use case describes the event where the customers attending the seminar swipes the card to register in the system his/her presence for the wellness activity.


Providing ID no. for webinars

This use case describes the event where the customer provides the ID card no. in the event of attending webinar for the wellness activity.


Providing online feedback

This use case describes the event when the wellness activity has concluded. The customers are asked to fill the online feedback regarding the wellness activity. The customer can fill the survey/feedback form via Apps or Website.


Receive / Send Notification

This use case describes the event where the customer gets notification regarding the wellness activity from the wellness tracking system and the wellness tracking system gets notification from the customers in terms of RSVP.

Customers(University) & Notification and Fetch (NAF)

Fetch Information of Customers from ED and MTAS for sending notifications

This use case describes the event where NAF fetches information from ED and MTAS for sending notifications to the customers.


Notifying erroneous credentials

This use case describes the event when the user/customer logs in through wrong credentials or there is some error while RSVP.


Jash Mehta 7


Use Case Table

Actor/External agent

Event Trigger Dependency Responses

Finance Department, Wellness Activity Planning Center (WAPC)

Accessing Information of Wellness Tracking System

Adhoc(These department accesses the information from the databases when required)

IT admin must give proper controls in order to access the information.

The information of the customers is sent across these departments


Planning Wellness Activities

Adhoc(WAPC makes rough plans for the wellness activity)

These plans are made based on the availability of wellness experts and wellness partners.

These plans are then sent to the ED


Planning Mental Health Activities


These plans are made based on the regular feedback received from the MTAS.Also these plans are made after discussing the schedule with yoga firms, yoga experts, meditation experts and meditation firms.



Planning Physical Fitness Activities


These plans are made based on the regular feedback received from the MTAS. Also these plans are made after discussing the schedule with gyms, Zumba


Jash Mehta 8


experts, and Zumba firms.


Planning Nutrition Seminars


These plans are made based on the regular feedback received from the MTAS. Also these plans are made after discussing the schedule with dieticians and nutrition experts.



Sending Plans Adhoc(The plans are sent across to the ED via a click of a button)

Before sending out the plans the plans need to be reviewed by Wellness planning center.

The plans are received by the ED at the other end


Finalizing based on RSVP

Adhoc(The plans are finalized and posted in the system via a button click)

This requires the RSVP count of the customers attending the seminar.Confirming and booking the schedule with wellness partners and giving them a count of people that will attend the event.

The final plans are posted on the website and Apps


Receive Feedback Adhoc(The WAPC receives feedback into its system via button click from customers and MTAS)

The customers should fill relevant feedback and the MTAS should be up to date with the medical health information

WAPC has customer and MTAS feedback critical for analyzes

Wellness Activity Planning Center

Analyze Feedback Adhoc(The WAPC

To analyze feedback, the

The analysis of the wellness activity is done and the

Jash Mehta 9


(WAPC) analyzes feedback and raw data by the tools they have in their system)

WAPC must receive feedback in the desired format which makes analysis very easy.

reports are to be prepared


Generate success Reports

Adhoc(After analyzing feedback, success reports are generated which are sent to the higher management in the company)

In order to generate reports analysis of information of customer feedback and medical health status is necessary.

The reports are generated for the higher management


Receive Plans Adhoc(Received via a button click from WAPC)

A rough/initial plan should be made by the WAPC such that it can be notified to the customers

Plans are received thus ED realizes to give permission to NAF to access the information from its system.

Enrollment Department (ED) & Medical Tracking and Alerts System (MTAS)

Giving Access of information from ED and MTAS to NAF component

Adhoc(Giving permission to access the information via a button click)

The reports of medical health should be ready with the MTAS. The ED should have complete information of enrolled customers

The NAF has all the information in order to send notification to the customers.

Medical Tracking and Alerts System(MTAS)

Tracking Medical Information and giving alerts to WAPC

Adhoc(This is achieved by doctor or customer entering their health details into the system)

Someone needs to feed the correct medical information to track the information.

The information is tracked in order to make regular health reports.


Reporting Medical Health of customers post wellness activities as a feedback to WAPC

Adhoc/ Time(As regularly the medical health info is updated in the system. At regular intervals the medical health is reported to the WAPC)

Proper medical health information should be captured in the system.

The health reports are regularly sent to the WAPC so they can track success of wellness activities and also plan future wellness activities.

Jash Mehta 10



Checking Authenticity and Eligibility

Adhoc(This is done only when user/customer clicks on submit button while logging in or when clicking on RSVP seminar)

The customer must attempt to login into the system.

Verification is done as a result the user/customer is able to perform his routine tasks or an error is thrown due any error.


Login Adhoc(Click on a button)

The user must be registered to login into the system.

The user/customer logs in as a result he gets access to the system.


RSVP Adhoc(Click on RSVP button)

The customer must have successfully logged into the system in order to Login.

As the user/customer logs in the user can browse different wellness activities and can RSVP the seminar. The RSVP is registered for the customers in the system.


Swiping Cards in the System

Adhoc(Swipe Cards into the device)

The customer must have ID cards

As a result the system registers that the customer attended the activity.


Providing ID no. for webinars

Adhoc(Provide ID and click on submit to view webinars)

The customer is not able to attend the seminar and would like to take benefit of the seminar from his/her workplace or home via webinar.

As a result the system registers that the customer attended the activity via the webinar.


Providing online feedback

Adhoc(customer clicks on the button after writing the feedback)

The customer should have attended the seminar in order to fill the feedback.

As a result the system registers the customer feedback into the system.

Customers(University) & Notification and Fetch (NAF)

Receive / Send Notification

Adhoc/Time(The customer clicks on button to RSVP. The NAF component sends the notification when it is triggered by other

For sending and receiving notification the customer must be logged into the system.

As a result the system gets notified when the customer clicks on RSVP. When the system sends the notification, the customer gets notified via healthcare Apps and website.

Jash Mehta 11


actors or components in/of the system)


Fetch Information of Customers from ED and MTAS for sending notifications

Time(The NAF component fetches the information when it is triggered by other actors or components in/of the system)

ED and MTAS should give access request from WAPC.

The information is successfully fetches as result of granting permission to the respective actors


Notifying erroneous credentials

Adhoc(This use case is performed when the user clicks on the button with wrong credentials )

There should be some error while logging in or while registering for the seminar

The customer is notified for the erroneous credentials or error in RSVP.

Use Case Narrative:Use-Case Name Tracking Medical Information and giving alerts to WAPC

Priority High

Actor (Primary): Medical Tracking & Alerts System

Interested Stakeholders: Medical Tracking & Alerts System – The MTAS is interested stakeholder because this system keeps track of all the health parameters. This system works with Wellness Tracking System in order to fetch and store historical medical history.

Description: This use case in our system is very important as this is the point where the medical health history of the customer comes into the picture. This use case deals with storing and analysing past medical history. This is a point where.

Pre-condition: Customer must be updating their health parameters in the system via periodical feedback

Jash Mehta 12


Hospitals or Doctors must be updating patients’ health parameters regularly.

Trigger: The event is triggered when the user/ customer fills the periodical feedback/ survey form. Or when the customer visits any health services, physicians or hospitals in the network the physician/health services updates the information in the system.

Typical Course Event: Actor Action: System Action/ResponseStep 1:As soon as the customer fills the feedback/ surveys the system captures the health history.

Step 2:This health history/ information’s access is given to Wellness Activity Planning Centre’s Database.Step 3:The historical medical data and current medical data is analysed and then the patient satisfaction is determined.

Alternate Course: Alternate step 3a: If the Medical Tracking system is not able to give access to wellness tracking system then the data need to be sent via a private secured networkAlternate step 3b: If the data needs to be sent via private secured network, employees need to track the transfer of huge volumes of data.

Conclusion: This use case concludes when the Medical Tracking system successfully captures the medical data and gives the access to WAPC.

Post Condition: After the MTAS has given access to WAPC, it is the WAPC’s job to analyse the past medical data to determine improvement/ deterioration in the patient’s health.

Business Rule: The system should allow the user to enter the health parameters in the feedback/ survey forms.

The backend system must capture the health parameters into the Medical Tracking system.

The system should allow the WAPC to compare the current data with past data.

The system should point out the trends from the current and the past data.

Implementation Constrains & Specifications:

The medical tracking system is very sensitive system as it contains medical data of the patients.

Giving access to another system may have serious security implications.

Assumption: The Medical Data Tracking System and Capturing system are compatible.

Open Issues: Need strong security algorithms to avoid attacks such as brute force so that access is not given to any unauthorized user.

Jash Mehta 13


Jash Mehta 14

uc and prototyping

Data & Analytics