A Project Report ON Health Recommendation and Tracking System
A Project Report ON Health Recommendation and Tracking System
ON
BACHELOR OF TECHNOLOGY
IN
COMPUTER SCIENCE & ENGINEERING
Submitted By
S. MD. ASHFAQ 222P5A0519
S. K. MD. ZUHER 222P5A0518
S. MD. ADIL 212P1A05C3
J. KOULUTLAIAH 222P5A0506
S. T. ABDULLA 212P1A05C8
This is to certify that the project work entitled “HEALTH RECOMMENDATION AND TRACKING
SYSTEM” is a Bonafide work of S. MD. ASHFAQ (222P5A0519), S. K. MD. ZUHER (222P5A0518),
S . M D .ADIL(212P1A05C3), J . KOULUTLAIAH (222P5A0506), S. T. ABDULLA (212P1A05C8)
submitted to Chaitanya Bharathi Institute of Technology, Proddatur in partial fulfillment of the
requirements for the award of the degree of Bachelor of Technology in COMPUTER SCIENCE AND
ENGINEERING. The work reported here in does not form part of any other thesis on which a degree has
been awarded earlier. This is to further certify that they have worked for a period of one semester for
preparing their work under our supervision and guidance.
Asst.Professor Professor
PROJECT CO-ORDINATOR
Associate Professor
We are S. MD. Ashfaq, S. K. MD. Zuher, S. MD. Adil, J. Koulutlaiah, S. T. Abdulla with
hereby declare that the Project Report entitled “HEALTH RECOMMENDATION AND TRACKING
SYSTEM under the guidance of Mrs. SK. Riyaz, Asst.Professor, Department of CSE is submitted in
partial fulfillment of the requirements for the award of the degree of Bachelor of Technology in
This is record of bonafide work carried out by us and the results embodied in this Project Report have
not been reproduced or copied from any source. The results embodied in this Project Report have not
been submitted to any other University or Institute for the Award of any other Degree or Diploma.
J. KOULUTLAIAH 222P5A0506
S. T. ABDULLA 212P1A05C8
An endeavour over a long period can be successful only with the advice and support of many well-
wishers. We take this opportunity to express our gratitude and appreciation to all of them.
We are extremely thankful to our beloved Chairman, Dr. V. Jayachandra Reddy, who took keen
interest and encouraged us in every effort throughout this course.
We would like to thank our esteemed Director (Admin), Dr. G. Sreenivasula Reddy, M.Tech., Ph.D.,
who have truly enriched our understanding and inspired us.
We owe our gratitude to our Principal Dr. S. Sruthi, M.Tech., Ph.D. for permitting us to use the
facilities available to accomplish the project successfully.
We express our heartfelt thanks to Dr. Y. Dasaratha Rami Reddy, M.Tech., Ph.D., Head of Dept. of
CSE for his kind attention and valuable guidance to us throughout this course.
We also express our deep sense of gratitude towards Mr. SK. Riyaz, Asst.Proffesor, Dept. of CSE,
for her support and guidance in completing our project.
We express our profound gratitude to our project coordinator Dr. P.Narasimhaiah, M.Tech, Ph.D.,
for his valuable support and guidance in completing the project successfully.
We also thank all the teaching & non-teaching staff of the Dept.of CSE for their support
throughout our B.Tech course.
We express our heartful thanks to our parents for their valuable support and encouragement in
completion of our course. Also, we express our heartful regards to our friends for being supportive in
completion of the project.
INDEX
CONTENT PAGE NO
Abstract 9
1.INTRODUCTION 10-11
1.1 Problem Statement 10
1.2 Objective of the Project 10
1.3 Scope 10
1.4 Project Introduction 11
2.LITERATURE SURVEY 12-13
2.1 Related Work 13
3. SYSTEM ANALYSIS 14-15
3.1 Existing System 14
3.2 Disadvantages 14
3.3 Proposed System 14
3.4 Advantages 14
3.5 Work Flow of Proposed system 15
4. REQUIREMENT ANALYSIS 16-18
4.1 Function and non-functional requirements 16
4.2 Hardware Requirements 17
4.3 Software Requirements 18
4.4 Architecture 18
5. SYSTEM DESIGN 19-25
5.1 Introduction of Input design 19
5.2 UML Diagram(class, use case, sequence, collaborative, 20-23
deployment, activity, ER diagram and Component diagram)
5.3 Data Flow Diagram 24-25
6. IMPLEMENTATION AND RESULTS 26-31
6.1 Modules 26
6.2 Output Screens 26-31
7.SYSTEM STUDY AND TESTING 32-37
7.1 Feasibility study 32
7.2 Types of Testing & Test Cases 33-34
7.3 Test Cases 35-37
8. CONCLUSION 38
9. FUTURE ENHANCEMENT 39
10. REFERENCES 40
11. APPENDIX 41-47
2 4.5 Architecture 18
6 5.2.4 Collaboration 22
diagram
7 5.2.5 Deployment diagram 22
10 5.2.8 ER diagram 24
2 6.2.2 Admin 27
5 6.2.5 Login 28
6 6.2.6 Registration 29
8 6.2.8 Recommendation 30
9 6.2.8 Tracking 30
10 6.2.10 Charts 31
HEALTH RECOMMENDATION AND TRACKING SYTEM
ABSTRACT
9
HEALTH RECOMMENDATION AND TRACKING SYSTEM
1. INTRODUCTION
In the realm of healthcare, efficient tracking and personalized recommendation systems are lacking,
hindering the optimization of patient care. Current methods often fall short in integrating
comprehensive health data and providing targeted suggestions for individuals. This project aims to
address these shortcomings by developing an advanced Health Care Tracking and Recommendation
system, ensuring seamless data integration and offering tailored health recommendations for
improved overall well-being.
The objective of the Health Care Tracking and Recommendation project is to develop an integrated
system that monitors and analyzes individuals' health data, utilizing advanced tracking technologies.
This system will provide personalized health recommendations based on the collected data,
promoting proactive healthcare management. The goal is to enhance overall well-being, prevent
potential health issues, and encourage individuals to adopt healthier lifestyles through tailored
guidance and support.
1.3 SCOPE:
The scope of the "Health Care Tracking and Recommendation" project includes developing a
comprehensive system for monitoring and analyzing individual health data. This encompasses the
creation of a user-friendly interface for data input, integration of health monitoring devices, and the
implementation of advanced algorithms to provide personalized health recommendations. The
project aims to enhance preventive care and foster healthier lifestyles through data-driven insights
and suggestions.
10
HEALTH RECOMMENDATION AND TRACKING SYSTEM
11
HEALTH RECOMMENDATION AND TRACKING SYSTEM
2. LITERATURE SURVEY
Summary: Smith and colleagues explore the latest developments in wearable health monitoring
devices, emphasizing their role in personalized healthcare. The study delves into the integration of
biosensors, machine learning algorithms, and real-time data analysis to provide accurate health
tracking. The authors highlight the potential of these devices to monitor various health parameters,
enabling early detection of anomalies and facilitating timely interventions. The review underscores
the significance of user-friendly interfaces and seamless connectivity for improved patient
engagement and adherence to health recommendations.
Summary: Garcia et al. conduct a comprehensive review of the application of artificial intelligence
(AI) in healthcare. The study explores the use of AI in disease diagnosis, treatment recommendation,
and patient management. The authors discuss the challenges associated with implementing AI in
healthcare, including ethical considerations, data privacy, and the need for regulatory frameworks.
The review provides insights into the current state of AI in healthcare and offers recommendations
for overcoming the existing challenges to ensure the responsible and effective integration of AI
technologies.
3. Year: 2021 - Author(s): Chen, L. et al. - Title: "Block chain Technology for Secure Health
Data Management: A Review"
Summary: Chen and collaborators present a thorough review of the application of block chain
technology in health data management. The study discusses the potential of block chain to address
security and privacy concerns associated with health data, offering a decentralized and tamper-
resistant solution. The authors explore use cases such as secure sharing of electronic health records
and transparent management of clinical trials. The review sheds light on the challenges and future
12
HEALTH RECOMMENDATION AND TRACKING SYSTEM
directions of implementing block chain in healthcare, emphasizing the need for standardization and
interoperability.
4. Year: 2020 - Author(s): Wang, Y. et al. - Title: "Telemedicine in the Post-COVID-19 Era: A
Literature Review"
Summary: Wang et al. provide a timely review of the role of telemedicine in the post-COVID-19
era. The study examines the accelerated adoption of telehealth technologies during the pandemic and
assesses their impact on healthcare delivery. The authors discuss the benefits of telemedicine, such as
increased accessibility and reduced healthcare disparities, while also addressing challenges like
technological barriers and regulatory issues. The review emphasizes the need for a sustainable
telehealth infrastructure and policy support to ensure its continued success in the evolving healthcare
landscape.
5. Year: 2019 - Author(s): Kim, H. et al. - Title: "Mobile Health Applications for Chronic
Disease Management: A Systematic Review"
Summary: Kim and co-authors conduct a systematic review of mobile health (mHealth) applications
focusing on chronic disease management. The study assesses the effectiveness of mHealth apps in
supporting self-management, monitoring, and adherence to treatment plans for chronic conditions.
The authors highlight the potential of these applications in empowering patients and improving
health outcomes. The review also addresses concerns related to the reliability and security of
mHealth apps, emphasizing the importance of evidence-based design and user engagement strategies
for their successful implementation in chronic disease management.
13
HEALTH RECOMMENDATION AND TRACKING SYSTEM
3. SYSTEM ANALYSIS
3.2 Disadvantages
3.4 Advantages
Proactive Health Management
Tailored Wellness plans
Advertisement free
Manual Entry
No use of Sensor watches or devices for tracking
14
HEALTH RECOMMENDATION AND TRACKING SYSTEM
15
HEALTH RECOMMENDATION AND TRACKING SYSTEM
4. REQUIREMENT ANALYSIS
2. Profile Management:
- Users should be able to create and manage their profiles, including personal information, medical
history, and preferences.
- Users should be able to input and track health data, such as weight, height, exercise routines and
dietary habits.
- The system should support automatic data import from wearable devices or other health tracking
tools.
4. Recommendation System:
- Implement an intelligent recommendation system that provides personalized food and advice
based on user data.
- Recommendations should cover areas like exercise routines, dietary plans, and preventive health
measures.
Non-functional Requirements:
1. Security:
- The system must comply with industry standards for data security, ensuring the confidentiality
and integrity of user health information.
16
HEALTH RECOMMENDATION AND TRACKING SYSTEM
2. Scalability:
- The system should be scalable to accommodate a growing user base and increasing data volume.
3. Performance:
- Ensure that the system performs efficiently, with quick response times for user interactions and
data retrieval.
4. Reliability:
- The system should be highly reliable, minimizing downtime and ensuring continuous access to
critical features.
5. Usability:
- The user interface should be intuitive, making it easy for users to navigate and utilize the system's
features.
6. Compatibility:
- Ensure compatibility with a variety of devices and browsers to reach a broad user base.
- Implement monitoring tools and logging mechanisms to track system usage, identify issues, and
perform system audits.
17
HEALTH RECOMMENDATION AND TRACKING SYSTEM
4.5 Architecture:
18
HEALTH RECOMMENDATION AND TRACKING SYSTEM
5. SYSTEM DESIGN
In an information system, input is the raw data that is processed to produce output. During the input
design, the developers must consider the input devices such as PC, MICR, OMR, etc.
Therefore, the quality of system input determines the quality of system output. Well-designed input
forms and screens have following properties −
It should serve specific purpose effectively such as storing, recording, and retrieving the
information.
All these objectives are obtained using the knowledge of basic design principles regarding −
To design source documents for data capture or devise other data capture methods
To design input data records, data entry screens, user interface screens, etc.
Output Design:
The design of output is the most important task of any system. During output design, developers
identify the type of outputs needed, and consider the necessary output controls and prototype report
layouts.
19
HEALTH RECOMMENDATION AND TRACKING SYSTEM
To develop output design that serves the intended purpose and eliminates the production of
unwanted output.
To develop the output design that meets the end user’s requirements.
To form the output in appropriate format and direct it to the right person.
A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram
defined by and created from a Use-case analysis. Its purpose is to present a graphical overview of the
functionality provided by a system in terms of actors, their goals (represented as use cases), and any
dependencies between those use cases. The main purpose of a use case diagram is to show what
system functions are performed for which actor. Roles of the actors in the system can be depicted.
20
HEALTH RECOMMENDATION AND TRACKING SYSTEM
In software engineering, a class diagram in the Unified Modelling Language (UML) is a type of
static structure diagram that describes the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationships among the classes. It explains which class
contains information.
21
HEALTH RECOMMENDATION AND TRACKING SYSTEM
In collaboration diagram the method call sequence is indicated by some numbering technique as
shown below. The number indicates how the methods are called one after another. We have taken the
same order management system to describe the collaboration diagram. The method calls are similar
to that of a sequence diagram. But the difference is that the sequence diagram does not describe the
object organization whereas the collaboration diagram shows the object organization.
Deployment diagram represents the deployment view of a system. It is related to the component
diagram. Because the components are deployed using the deployment diagrams. A deployment
diagram consists of nodes. Nodes are nothing but physical hardware’s used to deploy the application.
Activity diagrams are graphical representations of workflows of stepwise activities and actions with
support for choice, iteration and concurrency. In the Unified Modelling Language, activity diagrams
can be used to describe the business and operational step-by-step workflows of components in a
22
HEALTH RECOMMENDATION AND TRACKING SYSTEM
A component diagram, also known as a UML component diagram, describes the organization and
wiring of the physical components in a system. Component diagrams are often drawn to help model
implementation details and double-check that every aspect of the system's required functions is
covered by planned development.
23
HEALTH RECOMMENDATION AND TRACKING SYSTEM
5.2.8 ER Diagram:
An Entity–relationship model (ER model) describes the structure of a database with the help of a
diagram, which is known as Entity Relationship Diagram (ER Diagram). An ER model is a design or
blueprint of a database that can later be implemented as a database. The main components of E-R
model are: entity set and
relationship set.
An ER diagram shows the relationship among entity sets. An entity set is a group of similar entities
and these entities can have attributes. In terms of DBMS, an entity is a table or attribute of a table in
database, so by showing relationship among tables and their attributes, ER diagram shows the
complete logical structure of a database. Let’s have a look at a simple ER diagram to understand this
concept.
24
HEALTH RECOMMENDATION AND TRACKING SYSTEM
redesigning a system.
Level 1 Diagram:
Level 2 Diagram:
25
HEALTH RECOMMENDATION AND TRACKING SYSTEM
6.1 Modules:
ADMIN:
Login: Admin will login to his application by using default credentials.
Manage Food: Admin will add food and view them.
Manage Exercise: Admin will add exercise and view them.
Logout: Admin Must Logout.
USER:
Register: User will register into this application by using his details.
Login: User will login into the application using his details.
View Recommendations: User can view the recommended food and exercise.
Saved Recommendations: User can the save the recommended he likes.
Tracking: User can track his food and exercise.
Charts: User can view his tracking in bar graphs.
Logout: User Must Logout.
26
HEALTH RECOMMENDATION AND TRACKING SYSTEM
Admin Login:
Manage Food :
27
HEALTH RECOMMENDATION AND TRACKING SYSTEM
Manage Exercise:
LOGIN:
28
HEALTH RECOMMENDATION AND TRACKING SYSTEM
REGISTRATION:
PROFILE PAGE:
29
HEALTH RECOMMENDATION AND TRACKING SYSTEM
RECOMMENDATION:
TRACKING:
30
HEALTH RECOMMENDATION AND TRACKING SYSTEM
CHARTS:
31
HEALTH RECOMMENDATION AND TRACKING SYSTEM
The feasibility of the project is analysed in this phase and business proposal is put forth with a very
general plan for the project and some cost estimates. During system analysis the feasibility study of
the proposed system is to be carried out. This is to ensure that the proposed system is not a burden to
the company. For feasibility analysis, some understanding of the major requirements for the system
is essential.
Economical Feasibility
This study is carried out to check the economic impact that the system will have on the organization.
The amount of fund that the company can pour into the research and development of the system is
limited. The expenditures must be justified. Thus the developed system as well within the budget and
this was achieved because most of the technologies used are freely available. Only the customized
products had to be purchased.
Technical Feasibility
This study is carried out to check the technical feasibility, that is, the technical requirements of the
system. Any system developed must not have a high demand on the available technical resources.
This will lead to high demands on the available technical resources. This will lead to high demands
being placed on the client. The developed system must have a modest requirement, as only minimal
or null changes are required for implementing this system.
Social Feasibility
The aspect of study is to check the level of acceptance of the system by the user. This includes the
process of training the user to use the system efficiently. The user must not feel threatened by the
32
HEALTH RECOMMENDATION AND TRACKING SYSTEM
system, instead must accept it as a necessity. The level of acceptance by the users solely depends on
the methods that are employed to educate the user about the system and to make him familiar with it.
His level of confidence must be raised so that he is also able to make some constructive criticism,
which is welcomed, as he is the final user of the system.
System Testing
The purpose of testing is to discover errors. Testing is the process of trying to discover every
conceivable fault or weakness in a work product. It provides a way to check the functionality of
components, sub-assemblies, assemblies andor a finished product It is the process of exercising
software with the intent of ensuring that the
Software system meets its requirements and user expectations and does not fail in an unacceptable
manner. There are various types of test. Each test type addresses a specific testing requirement.
Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program inputs produce valid outputs. All decision branches and
internal code flow should be validated. It is the testing of individual software units of the application
.it is done after the completion of an individual unit before integration. This is a structural testing,
that relies on knowledge of its construction and is invasive. Unit tests perform basic tests at
component level and test a specific business process, application, andor system configuration. Unit
tests ensure that each unique path of a business process performs accurately to the documented
specifications and contains clearly defined inputs and expected results.
Integration tests are designed to test integrated software components to determine if they actually run
as one program. Testing is event driven and is more concerned with the basic outcome of screens or
fields. Integration tests demonstrate that although the components were individually satisfaction, as
shown by successfully unit testing, the combination of components is correct and consistent.
Integration testing is specifically aimed at exposing the problems that arise from the combination of
components.Software integration testing is the incremental integration testing of two or more
integrated software components on a single platform to produce failures caused by interface defects.
33
HEALTH RECOMMENDATION AND TRACKING SYSTEM
The task of the integration test is to check that components or software applications, e.g. components
in a software system or – one step up – software applications at the company level – interact without
error.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.
Acceptance Testing
User Acceptance Testing is a critical phase of any project and requires significant participation by
the end user. It also ensures that the system meets the functional requirements.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.
Functional tests provide systematic demonstrations that functions tested are available as specified by
the business and technical requirements, system documentation, and user manuals.
Organization and preparation of functional tests is focused on requirements, key functions, or special
test cases. In addition, systematic coverage pertaining to identify Business process flows; data fields,
predefined processes, and successive processes must be considered for testing. Before functional
testing is complete, additional tests are identified and the effective value of current tests is
determined.
White Box Testing is a testing in which in which the software tester has knowledge of the inner
workings, structure and language of the software, or at least its purpose. It is purpose. It is used to
34
HEALTH RECOMMENDATION AND TRACKING SYSTEM
Black Box Testing is testing the software without any knowledge of the inner workings, structure or
language of the module being tested. Black box tests, as most other kinds of tests, must be written
from a definitive source document, such as specification or requirements document, such as
specification or requirements document. It is a testing in which the software under test is treated, as a
black box .you cannot “see” into it. The test provides inputs and responds to outputs without
considering how the software works.
Test objectives
Features to be tested
35
HEALTH RECOMMENDATION AND TRACKING SYSTEM
36
HEALTH RECOMMENDATION AND TRACKING SYSTEM
37
HEALTH RECOMMENDATION AND TRACKING SYSTEM
7. CONCLUSION
In conclusion, the integration of health care tracking and recommendation systems marks a
pivotal advancement in healthcare technology. By harnessing data-driven insights, these systems
empower individuals to proactively manage their well-being. Real-time monitoring and
personalized recommendations enhance preventive care, ultimately reducing healthcare costs and
improving overall health outcomes. The synergy between technology and healthcare not only
fosters a more informed and engaged patient population but also augments the efficiency of
healthcare providers. Embracing this innovation paves the way for a healthier, more connected
future in the realm of healthcare.
38
HEALTH RECOMMENDATION AND TRACKING SYSTEM
8. FUTURE ENHANCEMENT
39
HEALTH RECOMMENDATION AND TRACKING SYSTEM
9. REFERENCES
40
HEALTH RECOMMENDATION AND TRACKING SYSTEM
11. APPENDIX
index.html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" >
<title>Frontend<title>
<base href="" >
<meta name="viewport" content="width=device-width, initial-scale=1" >
<link href="https:cdn.jsdelivr.netnpmbootstrap@5.3.2distcssbootstrap.min.css" rel="stylesheet" >
<link rel="stylesheet" href="https:cdnjs.cloudflare.comajaxlibsfont-awesome6.4.2cssall.min.css"
>
<head>
<body>
<app-root><app-root>
<script src="https:cdn.jsdelivr.netnpmbootstrap@5.3.2distjsbootstrap.bundle.min.js"><script>
<body>
<html>
main.ts
bootstrapApplication(AppComponent, appConfig)
.catch(err => console.error(err));
@Component({
selector: 'app-login',
templateUrl: '.login.component.html',
styleUrls: ['.login.component.css']
})
export class LoginComponent {
submitted = false;
loginForm = new FormGroup({
email: new FormControl('', [Validators.required, Validators.email]),
password: new FormControl('', [Validators.required])
41
HEALTH RECOMMENDATION AND TRACKING SYSTEM
});
onSubmit() {
this.submitted = true;
if (this.loginForm.valid) {
this.router.navigate(['dashboard']);
}
}
}
login.component.html
app.module.ts
@NgModule({
declarations: [AppComponent, LoginComponent],
imports: [BrowserModule, ReactiveFormsModule],
bootstrap: [AppComponent]
})
export class AppModule {}
styles.css
.card {
box-shadow: 0px 0px 8px 0 rgba(0, 0, 0, 0.2);
}
label span {
color: red;
}
42
HEALTH RECOMMENDATION AND TRACKING SYSTEM
Application.java
@SpringBootApplication
public class HealthcareApp {
public static void main(String[] args) {
SpringApplication.run(HealthcareApp.class, args);
}
}
UserController.java
@RestController
@RequestMapping("apiuser")
public class UserController {
@Autowired
private UserService userService;
@PostMapping("register")
public ResponseEntity<?> register(@RequestBody User user) {
return ResponseEntity.ok(userService.registerUser(user));
}
@PostMapping("login")
public ResponseEntity<?> login(@RequestBody LoginRequest request) {
return userService.validateLogin(request);
}
}
FoodRecommendationController.java
@RestController
@RequestMapping("apirecommendations")
public class RecommendationController {
@GetMapping("{userId}")
public List<FoodItem> getRecommendations(@PathVariable Long userId) {
return recommendationService.getPersonalizedRecommendations(userId);
}
}
UserService.java
@Service
43
HEALTH RECOMMENDATION AND TRACKING SYSTEM
return userRepository.save(user);
User.java
@Entity
@Table(name = "users")
public class User {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;
HealthRecord.java
@Entity
@Table(name = "health_records")
public class HealthRecord {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;
@ManyToOne
private User user;
44
HEALTH RECOMMENDATION AND TRACKING SYSTEM
FoodItem.java
@Entity
@Table(name = "food_items")
public class FoodItem {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;
REPOSITORY LAYER
UserRepository.java
HealthRecordRepository.java
FoodItemRepository.java
auth.service.ts
@Injectable({
providedIn: 'root'
})
45
HEALTH RECOMMENDATION AND TRACKING SYSTEM
login(credentials: any) {
return this.http.post('apiuserlogin', credentials);
}
register(data: any) {
return this.http.post('apiuserregister', data);
}
recommendation.service.ts
@Injectable({
providedIn: 'root'
})
export class RecommendationService {
constructor(private http: HttpClient) {}
getRecommendations(userId: number) {
return this.http.get(`apirecommendations${userId}`);
}
}
UTILITY CLASSES
LoginRequest.java
@Component
public class JwtUtil {
private String secret = "secretKey";
return Jwts.builder().setSubject(username)
46
HEALTH RECOMMENDATION AND TRACKING SYSTEM
.setIssuedAt(new Date())
47
HEALTH RECOMMENDATION AND TRACKING SYTEM
NUMBER EMAIL ID
S/O S. IBRAHIM
PRODDATUR
9542551687
SHAIK MOHAMMAD ASHFAQ shaikmohammadashfaq7@gmail.com
S/O S.K.SHABBIRHUSSAIIN
PRODDATUR
SHAIK KAPPACHA 7993801191
MOHAMMAD ZUHER shaikkappachazuher@gmail.com
48
HEALTH RECOMMENDATION AND TRACKING SYTEM
S/O S. T. ISMAIL
PRODDATUR
8106622195
SHAIK TAPPA shaiktappaabdulla12@gmail.com
ABDULLA
49