Nfc-Based Health Monitoring System PDF

VISVESVARAYA TECHNOLOGICAL UNIVERSITY
JNANA SANGAMA, BELAGAVI– 590018, KARNATAKA, INDIA
A PROJECT REPORT
on
“NFC-BASED HEALTH MONITORING SYSTEM”

Submitted in partial fulfillment of the requirements for the award of
BACHELOR OF ENGINEERING
in
COMPUTER SCIENCE & ENGINEERING
Submitted By
Name USN
SHARADA DEVI S.A 4VP14CS081
SHREYA RAI S 4VP14CS090
DEEKSHA B 4VP13CS015
LAXMI INGALAKI 4VP15CS406
Under the Guidance of
Mrs. ASHWINI P
Assistant Professor
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

VIVEKANANDA COLLGE OF ENGINEERING & TECHNOLOGY
[A Unit of Vivekananda Vidyavardhaka Sangha Puttur (R)]
Affiliated to Visvesvaraya Technological University and Approved by AICTE New Delhi & Govt., of Karnataka
Nehru Nagar, Puttur - 574 203, DK, Karnataka, India.
May 2018
VIVEKANANDA COLLEGE OF ENGINEERING & TECHNOLOGY
[A Unit of Vivekananda VidyavardhakaSangha Puttur (R)]
Affiliated to Visvesvaraya Technological University and Approved by AICTE New Delhi & Govt. of Karnataka
Nehru Nagar, Puttur - 574203, DK, Karnataka, India
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
CERTIFICATE
Certified that the project work entitled “NFC-Based Health Monitoring System” is carried
out by Miss. Sharada Devi.S A, Miss. Shreya Rai S, Miss. Deeksha B, Miss. Laxmi Ingalaki.
bearing USNs 4VP14CS081, 4VP14CS090, 4VP13CS015 and 4VP15CS406, respectively bonafide
students of Vivekananda College of Engineering & Technology, Puttur in partial fulfillment for
the award of Bachelor of Engineering in Computer Science & Engineering of the Visvesvaraya
Technological University, Belagavi during the year 2017-18. It is certified that all
corrections/suggestions indicated during Internal Assessment have been incorporated in the report
deposited in the departmental library.
The project report has been approved as it satisfies the academic requirements in respect of
Project work prescribed for the said Degree.
____________________ ____________________ ______________________
Signature of the Guide

Signature of the HOD Signature of the Principal
Mrs. Ashwini P
Prof. Mahesh Prasanna K Dr. M. S. Govinde Gowda
Assistant Professor
HOD, Dept. of CSE Principal, VCET.
EXTERNAL VIVA
Name of the Examiners Signature with date
1…………………………….............. ....................................
2…………………………….............. ....................................
DECLARATION
We, Sharada Devi S A (4VP14CS081), Shreya Rai S (4VP14CS090), Deeksha B

(4VP13CS015), and Laxmi Ingalaki (4VP15CS406)students of B.E. 8th Semester in
Computer Science &Engineering, Vivekananda College of Engineering & Technology,
Puttur, hereby declare that the project work entitled “NFC-Based Health Monitoring
System” has been carried out by us at VCET, Puttur, under the guidance of Mrs.
Ashwini P., Assistant Professor, Department of Computer Science &Engineering,
Vivekananda College of Engineering & Technology, Puttur, and submitted in partial
fulfilment of the requirements for the award of degree in Bachelor of Engineering in
Computer Science & Engineering by Visvesvaraya Technological University,
Belagavi during the academic year 2017-2018.
Name of the students USN Signature with date
SHARADA DEVI S A 4VP14CS081
SHREYA RAI S 4VP14CS090
DEEKSHA B 4VP13CS015
LAXMI INGALAKI 4VP15CS406
Date: 07.05.2018
Place: VCET, Puttur
ABSTRACT
From past few years, in almost every country across the world, significant financial
resources have been allocated to the health care sector. The two factors that triggered this
shift are modern technology developments and also the latest medicine practices. Most of
the developed countries are facing currently the problem off middle and older aged
marketplace from a largely youth-driven marketplace. Due to this trend there is a great
competition among health care providers and also there is a great demand for the health
services. Due to this competition there is a huge effort put by the health care providers
through different ways.
From the management point of view the cost of the medical services in hospitals can be
controlled through high operational efficiency and also by providing improved access to
public that too at an affordable cost. In order to achieve these goals of lowering costs and
improving efficiency the intelligent systems can play a crucial role at this stage.
Compared to other industries the efficiency of the health care sector is poor, this mainly
due to lack proper maintenance which is caused due to many reasons. Now-a -days there
is a huge increase in the number of health issues being reported across different parts of
the world. The hospitals have not been able to manage this increase due to lack of proper
monitoring system.
ACKNOWLEDGEMENT
We take this opportunity to express our deep heartfelt gratitude to all those people who
have helped us in the successful completion of the project.
First and foremost, we would like to express our sincere gratitude to our guide, Assistant
Prof. Ashwini P for providing excellent guidance, encouragement and inspiration
throughout the project work. Without his invaluable guidance, this work would never
have been a successful one.
We would like to express my sincere gratitude to our Head of the Department of

Computer Science & Engineering, Prof. Mahesh Prasanna K for his guidance and
inspiration.
We would like to thank our Principal, Dr. M. S. Govinde Gowda for providing all the
facilities and a proper environment to work in the college campus.
We are thankful to all the teaching and non-teaching staff members of

Computer/Information Science &Engineering Department for their help and needed
support rendered throughout the project.
TABLE OF CONTENTS
Title Page No
List of Figures I
List of Tables II
CHAPTER 1 INTRODUCTION 1
1.1 Introduction to the Project 2
1.1.1 Project Idea 3
1.2 Literature survey 3
1.3 Comparison with Existing System 5
1.4 Proposed System 5
CHAPTER 2 REQUIREMENT SPECIFICATION

7
AND ANALYSIS
2.1 Introduction 8
2.2 Functional Requirements 8
2.3 Non Functional Requirements 9
2.4 User Interfaces 10
2.5 Hardware Requirements 10
2.6 Software Requirements 10
CHAPTER 3 SYSTEM DESIGN 12

3.1 Introduction 13
3.2 Modules 13
3.2.1 Admin Module 13
3.2.2 Doctor Module 13
3.2.3 Patient Module 14
3.4 Class Diagram 14
3.5 Use Case Diagram 15
3.6 Sequence Diagram 16

CHAPTER 4 SYSTEM IMPLEMENTATION 18
4.1 Introduction 19
4.2 ER Diagram 19
CHAPTER 5 SYSTEM TESTING AND

21
EXPERIMENTAL RESULTS
5.1 Introduction 22
5.2 Black Box Testing 22
5.2.1 Unit Testing 22
5.2.2 Integration Testing 23
5.3 Validation Testing 23
5.4 Platform Testing 23
5.5 Experimental Results 25
CHAPTER 7 SCREENSHOTS 26
CHAPTER 8 CONCLUSION AND SCOPE FOR 34
FUTURE ENHANCEMENT
REFERENCES 36
PERSONAL PROFILE 38
LIST OF FIGURES
Figure No. Caption Page No.
2.1 NFC tags 10
3.1 Class Diagram for NFC based health monitoring system 14
3.2 Use case Diagram of NFC based health monitoring system 15
3.3 Sequence Diagram for NFC based health monitoring system 16
4.1 ER Diagram for NFC based health monitoring system 20
I
LIST OF TABLES
Table No Caption Page No
5.1 Test Case for login page 24
5.2 Test Case for registration 24
II
NFC Based Health Monitoring System 2017-18
INTRODUCTION
Dept.of CSE, VCET Puttur Page 1

CHAPTER 1
INTRODUCTION
1.1 Introduction to the Project
Near Field Communication (NFC) is a simple and two-way interaction between electronic
devices which allows performing contactless transactions. It is a technology used to automate
health care monitoring using a smart-phone (android). In hospital, every patient has different
illness and different symptoms. When doctors operate on patient there are chances of getting
confusion between patient’s disease and treatment which can turn into fatal mislead in medical
treatment of a patient and can also lead to death, along with this issue patient health records and
reports are retained on paper which is difficult to maintain and unreliable .If a robust healthcare
system is made using NFC it may protect patient from such fatal medical mistakes.
The NFC-TAGs can store some information using a unique ID or number. NFC is a
technology which allows exchange of information between devices. NFC is nothing but an
offshoot of radio frequency identification (RFID) which combines interface of a smartcard and a
reader into a single device. The main advantage of NFC over Bluetooth is that it requires short
setup time as the connection between two NFC enabled devices is established at once under one
tenth of a second. NFC communicates by making magnetic field induction where two loop
antennas which are located close to each other forms an air-core transformer. This feature of
NFC tag can be used for Real Time Applications.
NFC standard has three distinct modes of operation depending on what kind of
information is to be exchanged. Perhaps the most commonly used is peer-to-peer mode which
allows the two NFC enabled devices to transmit data between each other. In peer to peer both
devices are active when they send data and become passive when they receive data. Read/write
mode is the other mode of operation in which the active NFC device possibly mobile phone
established a link with another device to read data from it.

1.1.1 Project Idea

An efficient Patient recognition and diagnosis technique has been implemented using NFC-chip
of the NFC standards. Every patient is registered to the admin and is provided with a Unique ID.
The data is stored and maintained in a Database instead of conventional Paper-file system. The
patients' entire details are retrieved through a unique ID which is stored in the NFC-Tag. The
details are stored and maintained in a Database instead of conventional Paper-file system. The ID
provision overcomes ambiguity in identification of the patients bearing same name and thus
prevents wrong medications.
1.2 Literature Survey

A Standalone RFID and NFC based Healthcare System which reduces the chances of getting
confusion between patients disease. NFC allows treatment of patients with a single touch of
microchip in an unambiguous manner. The treatment also allows performing contactless
transactions. Also it provides an ease to connect devices with a single touch [1]. One
preventable aspect is the data insertion in which the attacker inserts messages into the data
exchange between 2 devices. But this is possible only when the answering device has high
response time. NFC requires just one tenth of a second to perform transaction. Technical
development and modern medicine practices are among the outstanding factors triggering this
shift. This trend is resulting in a greater demand of healthcare related services and greater
competition among healthcare providers. Achieving a high operational efficiency in the
healthcare sector is an essential goal for organizational performance evolution.
Robust healthcare is a requirement for both developed countries, where the cost of
healthcare is high, security and privacy are critical issues and developing countries like India,
where there is a mass population to handle in hospitals and robust healthcare procedures are
required [2]. Identification of objects for secure medical procedures is very essential for a secure
workflow. Along with this issue the patient health record management is important both for
patients as well as hospital management. Health card on a mobile device can be helpful in
developed countries also, where healthcare cost is high and privacy and security are critical.
Mobile phones had already several communication options with the external environments
before the introduction of NFC technology. When the mobile phones were initially introduced,

the primary goal was to enable voice communication with the mobile and wired phones [3].
Bluetooth technology was introduced later to create personal area wireless networks that connect
peripherals with computing device including mobile phones. NFC Technology brings innovation,
opportunities to make communications. It enables two users to easily communicate and exchange
data simply by touching two mobile phones to each other. Moreover, NFC Technology gives
NFC reader capability to Mobile phones.
Appointment scheduling attracts increasing attention as a demand for healthcare. Due to

the increasing number of patients visiting hospitals, there is a high demand for the introduction
of intelligence and automation in respect of hospital related processes such as appointment
scheduling and medicine collection [4]. This is with a view to cub on the long waiting time,
queuing for medicine and the complexity in hospital administration and this will increase the
efficiency of treatment and also increase patient satisfaction. There are two ways of getting the
medical consultation. One is the Walk-in appointment and the other is the conventional
scheduling an appointment. The call in walk-in appointment will be received by an individual at
the hospital, who will store the appointment details and the request in either a large book or in
the Database.
The privacy and security problems arise from RFID Tag. Limitations such as small
memory and low computation power [5]. Due to such limitations, data transmission between
RFID Tags and Readers are unencrypted. In addition, RFID Tag provides no tamper resistance.
That is, the RFID Tags and Readers communicate with each other using insecure Wireless
channels. Recent papers have reported that RFID systems have to achieve the following
requirements such as: Indistinguishability, Forward security.

1.2 Comparison with the existing system

The most prominent and popular tool for connectivity is Bluetooth. The main advantage of NFC
over Bluetooth is that NFC requires much low power consumption than the new Bluetooth as
well. NFC has a range of around 10cm while Bluetooth can transmit data up to 10 meters or
more. When it comes to speed, NFC has faster connectivity. As NFC uses inductive coupling and
there is no manual pairing, it takes not more than one tenth of a second for a connection between
two devices. One of the common concerns with NFC technology is data corruption or data
manipulation. This may occur when a third party intercepts the signal being sent and tries to alter
it which may leads to modification of data or corruption of data. The removal of NFC tag from
the tagged item or wrapping the tag in metal foil causing to shield RF signal may also lead to
unrecognizing of the tag Another aspect is the data insertion in which the attacker inserts
messages into the data exchange between two devices. For detecting errors in NFC it uses the
CRC technique (Cyclic Redundancy Check) which permits devices to check whether the
received data has been corrupted or not.
1.3 Proposed system

In the proposed system the use of NFC tag and card is done in such a way that it contains all the
features and benefits of the NFC and smart phones. The use of NFC tag or bands with the NFC
enabled mobile gives the advancement of storing the digital data of patient to a server in a single
tap. Hence the scope of project lies in the use of NFC tags in desktop based application as well as
mobile based application.
 The phones must be enabled with NFC.

 The patient and doctor both must register to the admin.
 The Admin manages the read and write operations from and to the NFC tag.
 The patient taps to the doctor’s phone to get identified by a unique number stored using
NFC.
 The number helps to retrieve all the details of a particular patient using database.
 Once the information is understood by the doctor, the medical report can be made.
 The doctor can either agree with the patient health, if not the medications can be initiated.

 The server is filled with the details of necessary medicines related to the patient’s health
issues.
 Added to this, the patient can also login and update his/her health profile by the aid of
check instruments.
 Once the details are delivered to the hospital, the doctors staying far away can quickly
interact to the patient. Thus, it is time-saving.
 Prescriptions can be made very easy by avoiding travel.

REQUIREMENTS
SPECIFICATION &
ANALYSIS

CHAPTER 2
REQUIREMENTS SPECIFICATION & ANALYSIS

2.1 Introduction
A functional requirement defines a function of a system and its components. A function is
described as a set of inputs, the behavior, and outputs .Functional requirements may be
calculations, technical details, data manipulation and processing and other specific functionality
that define what a system is supposed to accomplish.
A non-functional requirement is a requirement that specifies criteria that can be used to

judge the operation of a system, rather than specific behaviors. They are contrasted with that
define specific behavior or functions.
The most common set of requirements defined by any operating system or software
application is the physical computer resources, also known as hardware. A hardware
requirements list is often accompanied by a hardware compatibility list (HCL), especially in case
of operating systems. An HCL lists tested, compatible, and sometimes incompatible hardware
devices for a particular operating system or application.
A software requirements specification is a description of a software system to be

developed. It lays out functional and non-functional requirements, and may include a set of use
cases that describe user interactions that the software must provide.
2.2 Functional Requirements

 Near Field Communication which is a standards-based, short range wireless technology.
Use of NFC for unique identification of patients in enabled.
 NFC is a simple and two-way interaction between electronic devices which allows
performing contactless transactions and provides an ease to connect devices with a single
touch.

 A technology which allows exchange of information between devices which are in a 10

cm range although NFC-tags require 1 cm range for tapping.
 Nothing but an offshoot of radiofrequency identification (RFID) which combines
interface of a smartcard and a reader into a single device.
2.3 Non-Functional Requirements

Usability and Maintainability:
The ease with which a software system or component can be modified to correct faults, improve
performance or other attributes, or adapt to a changed environment.
Reliability:
The ability of a system to consistently perform its intended operation or required function, on
demand and without failure or degradation is reliability.
Availability:
The degree to which a system, subsystem or equipment is in a specified operable and
committable state at the start of mission, when the mission, when the mission is called for at an
unknown, i.e. a random, time.
Safety and Security:

Safety and security are the two essential aspects of systems and software. It is secure because we
make user of authorization and authentication techniques. It is a process of ensuring that
software is designed to operate at a level of security that is consistent with the potential harm that
could result from the loss, inaccuracy, and alteration.
2.4 User Interfaces

The design of a user interface affects the amount of effort the user must expend to provide input
for the system .NFC is an offshoot of RFID which combines interface of a microchip and a
reader into a single device. We use android studio for smart phones.

2.5 Hardware Requirements

NFC Tag:
NFC tags are smart little chips that enable exchanging digital information with smart phone at
short range. NFC tags are passive devices which operate without a power supply of their own
and are reliant on an active device to come into range before they are activated.
Fig 2.1: NFC Tags
2.6 Software Requirement

Android Studio:
Android Studio is the official integrated development environment for Google’s Android
operating system built on Jet Brains IntelliJ IDEA software and designed specifically for android
development. Android Studio supports all the same programming languages of IntelliJ and Py
Charm for example Python and Android Studio support “Java 7 language features and a subset of
Java 8 language features that vary by platform version.
PHP
PHP is a server-side scripting language designed primarily for web development but also used as
a general-purpose programming language. Originally created by Rasmus Lerdorf in 1994, the
PHP reference implementation is now produced by the PHP Development Team. PHP originally
stood for Personal Home Page, but now it stands for the recursive acronym PHP: Hypertext
Preprocessor.

PHP code may be embedded into HTML Code, or it can be used in combination with various
web template systems, web content management systems and web frameworks. PHP code is
usually processed by a PHP interpreter implemented as a module in the web server or as a
Common Gateway Interface (CGI) executable. The web server combines the results of the
interpreted and executed PHP code, which may be any type of data, including images, with the
generated web page. PHP code may also be executed with a command-line interface (CLI) and
can be used to implement standalone graphical applications.
The standard PHP interpreter, powered by the Zends Engine, is free software released
under the PHP License. PHP has been widely ported and can be deployed on most web servers
on almost every operating system and platform, free of charge. The PHP Language evolved
without a written formal specification or standard until 2014, leaving the canonical PHP
interpreter as a de facto standard. Since 2014, work has gone on to create a formal PHP
specification.
JAVA
Initially the language was called “oak” but it was renamed as “java” in 1975. The primary
motivation of this language was the need for a platform-independent language that could be used
to create software to be embedded in various consumer electronic devices.

SYSTEM DESIGN

CHAPTER 3
SYSTEM DESIGN
3.1 Introduction
System design is a process through which requirements are translated into a representation of
software. Initially, the representation depicts a holistic view of software. Subsequent refinement
leads to a design representation that is very close to source code. The importance of design can
be started with a single Word-Quality.
Design is the place where quality is fostered in software development. The design phase
can be defined as the process of applying various techniques and rules for the purpose of
defining the process or system in document for the software to the development is available.
3.2 Modules
There are 3 modules in our system.
3.2.1. Admin Module
The admin is the authority who registers both doctor as well as the patient. He also updates the
details of the corresponding patient and assigns each patient with a unique number. Only he has
the power to write into the NFC tag
.
3.2.2. Doctor Module
The doctor has to register himself through the admin in order to view the patient details. He has
the power to update the information regarding the patient. He can also view his own profile. He
can update his profile with name, email-id, etc.
3.2.3. Patient Module

The patient can successfully update his own profile with the details and also he is enabled with a
facility to update sensitive details like rate of heartbeat or even the blood-pressure level.

3.3 Class diagram

A class diagram is an illustration of the relationships and source code dependencies among
classes in the Unified Modeling Language (UML). In this context, a class defines the methods
and variables in an object, which is a specific entity in a program or the unit of code representing
that entity.
Fig. 3.1: Class Diagram for NFC based health monitoring system
The admin has username and password as attributes. The class can control all activities
using login function. Both the doctor as well as the patient must register to the admin. The doctor
registration class is associated with the doctor and can register the patients. The patient
registration class is associated with the patient who has to provide all his details to the doctor.

3.4 Use case diagram

It shows a set of use cases and actors. Use case diagram give us overall view as well as behavior
of system. A use case diagram can identify the different types of users of a system and the
different use cases and will often be accompanied by other types of diagrams as well. These
diagrams are prospective about modeling and organizing of the system.
Fig.3.2: Use case Diagram of NFC based health monitoring system
The use case consists of three main actors. They are the admin, the doctor and the patient.
All the three are facilitated to login and perform desired activities and finally logout safely. The
admin can perform tasks like doctor registration, patient registration and updation of health
details and write tag. The writing into the NFC tag is done by the Admin only. The doctor can
view patient's details, update patient's information and later view patient's profile.

3.5 Sequence diagram

A sequence diagram is an interaction diagram that shows how objects operate with one another
and in what order. It is a construction of a message sequence chart. A sequence diagram shows
object interactions arranged in time sequence. Sequence diagrams are sometimes called event
diagram, event scenarios and timing diagrams.
Each actor as well as system is represented by the vertical line called lifeline and each
message is represented by horizontal arrow from sender to receiver. The time will proceed from
top to bottom in this diagram. The period of time of an object exists but are not active are shown
by dashed line.
Fig. 3.3: Sequence Diagram for NFC based health monitoring system
The dynamics of the figure gives us a clear working of the system with respect to time.
The admin has to login to the system and register both admin and the patient. Here, it is clear that
when the patient needs to be admitted to a hospital, the receptionist will initiate this system by
performing the registrations of the patient and his corresponding doctor. Once this is successful,
the doctor reads the ID stored in the tag. The ID of the patient to identify with every patient with
a unambiguous number. The doctor receives the health issues of the patient and updates the
prescriptions online. The doctor can even review the patient's profile and modify as per the need.

SYSTEM
IMPLEMENTATION

CHAPTER 4
SYSTEM IMPLEMNTATION
4.1 Introduction
System implementation is the construction of the new system and the delivery of that system into
production. In our project web application and android application are implemented. The web
application is used by the admin. Where he can login into the system using username and
password and he maintains overall system. The main is the admin who registers doctor and
patient and also updates health details and writes the patient NFC tag.
The doctor has to register himself through the admin in order to view the patient details.
He has the power to update the information regarding the patient. He can also view his own
profile. The doctor registers name, password, email-id, select specialist and also mobile number.
The patient can successfully update his own profile with the details and also he is enabled
with a facility to update sensitive details like rate of heartbeat or even the blood-pressure level.
The admin register the patient with patient Id, name, password and email-Id and then select the
disease with corresponding doctor, mobile number, blood pressure, heartbeat etc. Then click
register button it will update with id and registration successful.
The doctor can view the patient details and he can update medicine for particular disease. The
doctor can view the old records of the patient tapping by NFC card on his NFC enabled phone.
NFC card will stored the all information about the patient with patient-Id.
4.2 ER Diagram
An Entity-Relationship model describes inter-related things of interest in specific domain of
knowledge. An ER model composed of entity types and specifies relationships that can exist
between instances of those entity types.

Fig. 4.1 ER Diagram for NFC based health monitoring system

SYSTEM TESTING AND

EXPERIMENTAL RESULTS

CHAPTER 5
SYSTEM TESTING
5.1 Introduction
In system testing the behavior of whole system/product is tested as defined by the scope of the
development project or product. It gets all the integrated modules of the various components
from the integration testing phase and combines all the different parts into a system which is then
tested. Testing is then done on the system as all the parts are now integrated into one system the
testing phase will now have to be done on the system to check and any errors or bugs.
5.2 Black Box Testing

Black-box testing is a method of software testing that examines the functionality of an
application without peering into its internal structures and workings. Another name for black-box
testing is functional testing because mathematical functions can be specified using only there
inputs and outputs. This method of test can be applied virtually to every level of software testing:
unit, integration, system and acceptance which are included in our project. It typically comprises
most if not all higher level testing, but can also embody unit testing.
5.2.1 Unit Testing

The primary goal of unit testing is to take the smallest piece of testable software in the
application, isolate it from the remainder of the code and determine whether it behaves exactly as
you expect. Each unit is tested separately before integrating them into modules to test the
interface between modules. Unit testing has proven its value in that a large percentage of defects
are identified during its use. Unit testing is a verification and validation method where the
programmer gains confidence that individual units of source code are fit for use. A unit is the
smallest testable part of an application. In procedural programming a unit may be individual
program, function , procedure, etc.., while in object class, abstract class or derived/child class.

5.2.2 Integration Testing

Integration Testing is phase in software testing in which individual software modules are
combined and tested as a group. It occurs after unit testing and before validation testing.
Integration testing takes as its input module but has been unit tested, groups them in larger
aggregates, applies tests defined in integration test plan to those aggregates and delivers as its
output the integrated system ready for system testing. The purpose of integration testing is to
verify functional, performance, and reliability requirements placed on major design items. These
design items that is assemblages are exercised through their interface using black-box testing,
success and error cases being simulated via appropriate parameter and data inputs.
There are two major ways of carrying out an integration test called the bottom-up method and the
top-down method. Bottom-up integration testing begins with unit testing followed by tests of
progressively higher-level combination of units called modules or builds. In top-down
integration testing, the highest-level modules are tested first and progressively lower-level
modules are tested after that. In the comprehensive software development environment, bottom-
up testing is usually done first, followed by top-down testing.
5.3 Validation Testing

At the conclusion of integration testing software is completely assembled as a package,
interfacing errors have been uncovered and corrected and a final series of software tests begins,
validation test begins. Validation test can be defined in many ways. But the simple definition is
that validation succeeds when the software function in a manner that can reasonably expected by
the user.
5.4 Platform Testing

Testing of applications on Mobile platform and applications testing for cross-browser
compatibility are concerned. Platform can refer to the type of processor or other hardware on
which a given operating system or application runs, the type of operating system on computer or
the combination of the type of hardware and type of operating system running on it.

Test Cases
It is a set of test inputs, execution conditions and expected results developed for a particular
objective, such as to exercise a particular program path or to verify compliance with a specific
requirement. The point of running the tests is to gain information, for example whether the
program will pass or fail the test.
Table 5.1
Test Case for login page
Test Case ID Input Expected Output Actual Results
Run the Login Page Display Login Page As Expected

1
Enter Username and Valid Users Login As Expected
2 Password
Invalid Username or Display Message As Expected
3 Password about Invalid
Username or
Password
Table 5.2
Test Case for registration
Test Case ID Input Expected Output Actual Results
Run the Register Register Page As Expected

1 Page Display
When all the fields Registered As Expected
2 are correctly filled successfully
When some fields left Appropriate message As Expected
3 blank is displayed
Click on Login Login Page Display As Expected
4 button to Login Page

5.5 Experimental Results

An application using NFC has been successfully installed in smart phones and the patient details
have been successfully retrieved using the NFC Tag.
Thereby, NFC Technology has been helpful in tracking the patient information by
collecting and transmitting data in real-time. Also, data from variable health related devices like
pressure sensor; temperature sensor etc. can be retrieved using NFC devices. An inexpensive
technical assistance is made, which support people with physical disabilities and to overcome
travel issues.
NFC-based appointment system has speed with accuracy and can be used for a reliable
patient health record and for automation of healthcare as well.

SCREENSHOTS

CHAPTER 7
SCREENSHOTS
Fig 7.1: Home Page
Fig 7.2: Admin Login Page

Fig 7.3: Admin Home Page
Fig 7.4: Page for Doctor Registration

Fig 7.5: Page for registration successful
Fig 7.6: Page for Patient Registration

Fig 7.7: Page for Update Patient Health Details
Fig 7.8: Page for Doctor Login Page

Fig 7.9: Page for Doctor Home Page
Fig 7.10: Page for Doctor Update the Patient Health Details

Fig 7.11: Page for Doctor Read the NFC tag By Patient ID
Fig 7.12: Page for Doctor Profile

Fig 7.13: Page for Patient Login Page
Fig 7.14: Page for Patient Update his Health Details

CONCLUSION AND
SCOPE FOR FUTURE

ENHANCEMENT

CHAPTER 8
CONCLUSION AND
SCOPE FOR FUTURE ENHANCEMENT
8.1 Conclusion
NFC based health monitoring and controlling system is the attempt to inculcate use of NFC
technology and its benefits when used with mobiles to efficiently, accurately and ease the
process of patient management in healthcare.
Healthcare has a vast future scope so new additional features can be added to proposed
system like dynamic data of patient. Patient has to wear wearable ECG sensors that will monitor
and control patient's health parameters at runtime. Due to this sensors patient's heartbeats, blood
pressure records etc. will be stored on the server periodically. ECG sensors will continuously
monitor patient’s health even if doctors are not nearby. If after discharge patient wears these
ECG sensors and same thing is happen that is he/she has heart attack then android phone will
automatically call ambulance and doctor along with a SMS with patients’ current location will be
sent to its relatives.

REFERENCES
[1] Amol D. Potgantwar, Vijay M. Wadhai, “A Standalone RFID and NFC based
Healthcare System”. vol. 7, Issue 2, April 2013.
[2] Sethia, D.; Gupta, D.; Mittal, T. Arora U, Saran, H., "NFC based secure mobile
healthcare system," 2014 Sixth International Conference on Communication Systems
and Networks (COMSNETS), pp.1,6, 6-10 Jan. 2014
[3] Mareli M, Rimer S, Paul, B.S Ouahada, K Pitsillides A, "Experimental evaluation of
NFC reliability between an RFID tag and a smartphone," AFRICON, 2013, pp.1, 5, 9-
12 Sept. 2013.
[4] Gautam J, Kumar Y, Gupta A, "Existing scenario of near field communication in
transport sector," Signal Processing and Integrated. Networks (SPIN), 2014
International Conference on, pp.327,332, 20-21 Feb. 2014
[5] A. Alzahrani, A Alqhtani, H. Elmiligi, F. Gebali, M. S. Yasein, “NFC Security
Analysis and Vulnerabilities in Healthcare Applications”, IEEE Pacific Rim
Conference of Communications, Computers and Signal Processing (PACRIM),
ISBN: 978-1-4799 1501-9, 27-29 Aug. 2013, pp. 302 – 305.
[6] Adam Marcus, Guido Davidzony, Denise Law, Namrata Venna, Rich Fletcher, Aamir
Khanz and Luis Sannenta, "Using NFC-enabled Mobile Phones for Public Health in
Developing Countries", IEEE Proceedings on First International Workshop on Near
Field Communication, pp. 3035. 2009.
[7] Lahtela A, Hassinen M. and Iylha, V, "RFID and NFC in healthcare: Safety of
hospitals medication care", IEEE proceedings on Pervasive Computing Technologies
for Healthcare, pp. 241-244, 2008.
[8] Gune A, Bhat, A Pradeep, A., "Implementation of Near Field Communication based
healthcare management system," Industrial Electronics and Applications (ISIEA),
2013 IEEE Symposium on , pp.195,199, 22-25 Sept. 2013.
[9] AlZuhair M.S, Najjar A.B, Kanjo, E, "NFC based applications for visually impaired
people - A review," Multimedia and Expo Workshops (ICMEW), 2014 IEEE
International Conference on, pp.1, 6, 14-18 July 2014.

[10] Sankarananrayanan S, Wani, S.M.A., "NFC enabled intelligent hospital appointment

and medication scheduling," Information and Communication Technology (ICoICT),
2014 2nd International Conference, pp. 24, 29, 28-30 May 2014.
[11] Gerhard de Koning Gans, Jaap-Henk Hoepman, and Flavio D. Garcia, "A Practical
Attack on the MIFARE Classic", Smart Card Research and Advanced Applications.
LNCS, vol. 5189, pp. 267-282, 2008.
[12] Divyashikha Sethia, Shantanu .lain and Himadri Kakkar, "AutomatedNFC enabled
Rural Healthcare for reliable patient record maintenance”, Proceedings of Global
Telehealth Conference, vol. 182, pp. 104-113, 2012.
[13] Jason Wu, Lin Q, Ram Shankar Siva Kumar, Nishant Kumar, and Patrick Tague, "S-
SPAN: Secure Smart Posters in Android using NFC",IEEE International Symposium
on World of Wireless, Mobile and Multimedia Networks, pp. 1-3, IEEE Press, 2012.

PERSONAL PROFILE
Mrs. Ashwini P received her BE degree in

Computer Science and Engineering from
PES School of Engineering, Bengaluru in the
year 2010 and MTech degree in Computer
Science and Engineering from Sahyadri
College of Engineering, Mangalore and
Management in the year 2016. She has about
7 years of industrial experience and has
recently chosen teaching as profession. Her
subjects of interest are Data Structure,
DBMS and Programming with C/C++, Java
programming and Networking.
Sharada Devi S A
4VP14CS081
D/O Venkatesha Bhat A
ShriRameshwara Temple Road
Chamarajpet, Bengaluru
Karnataka-560018
E-mail ID: sharadadevi7sa@gmail.com
Phone No:9483628757

Shreya Rai
4VP14CS090
D/O Jayarama Rai
Sarya beedu house
Beliyoorkatte Post
Puttur -574203
E-mail ID: raishreya836@gmail.com
Phone No:9902703643
Deeksha B
4VP13CS015
D/O Sanjeev Rai
Megina Belinja House
Yethadka Post
Kasaragod Kerala 671551
E-mail ID: deeksharaib5@gmail.com
Phone No:7899584036

Laxmi Ingalaki
4VP15CS406
D/O Rudra Gowda Ingalaki
Near Basava Temple, Kalkoppa
Post: Pala
Tq:mundgod D:karwar-581349
E-mail ID: lakshmiri6600@gmail.com
Phone No:9164816535

Nfc-Based Health Monitoring System PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Nfc-Based Health Monitoring System PDF

Hochgeladen von

Copyright:

Verfügbare Formate

VISVESVARAYA TECHNOLOGICAL UNIVERSITY

JNANA SANGAMA, BELAGAVI– 590018, KARNATAKA, INDIA

“NFC-BASED HEALTH MONITORING SYSTEM”

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

____________________ ____________________ ______________________

Signature of the Guide

We, Sharada Devi S A (4VP14CS081), Shreya Rai S (4VP14CS090), Deeksha B

Name of the students USN Signature with date

SHARADA DEVI S A 4VP14CS081

SHREYA RAI S 4VP14CS090

LAXMI INGALAKI 4VP15CS406

We would like to express my sincere gratitude to our Head of the Department of

We are thankful to all the teaching and non-teaching staff members of

1.2 Literature survey 3

1.3 Comparison with Existing System 5

1.4 Proposed System 5

CHAPTER 2 REQUIREMENT SPECIFICATION

2.2 Functional Requirements 8

2.3 Non Functional Requirements 9

2.4 User Interfaces 10

2.5 Hardware Requirements 10

2.6 Software Requirements 10

CHAPTER 3 SYSTEM DESIGN 12

3.4 Class Diagram 14

3.5 Use Case Diagram 15

3.6 Sequence Diagram 16

CHAPTER 5 SYSTEM TESTING AND

5.3 Validation Testing 23

5.4 Platform Testing 23

5.5 Experimental Results 25

Figure No. Caption Page No.

2.1 NFC tags 10

3.1 Class Diagram for NFC based health monitoring system 14

3.2 Use case Diagram of NFC based health monitoring system 15

3.3 Sequence Diagram for NFC based health monitoring system 16

4.1 ER Diagram for NFC based health monitoring system 20

Table No Caption Page No

5.1 Test Case for login page 24

5.2 Test Case for registration 24

Dept.of CSE, VCET Puttur Page 1

Dept.of CSE, VCET Puttur Page 2

1.1.1 Project Idea

1.2 Literature Survey

Dept.of CSE, VCET Puttur Page 3

Appointment scheduling attracts increasing attention as a demand for healthcare. Due to

Dept.of CSE, VCET Puttur Page 4

1.2 Comparison with the existing system

1.3 Proposed system

 The phones must be enabled with NFC.

Dept.of CSE, VCET Puttur Page 5

Dept.of CSE, VCET Puttur Page 6

Dept.of CSE, VCET Puttur Page 7

REQUIREMENTS SPECIFICATION & ANALYSIS

A non-functional requirement is a requirement that specifies criteria that can be used to

A software requirements specification is a description of a software system to be

2.2 Functional Requirements

Dept.of CSE, VCET Puttur Page 8

 A technology which allows exchange of information between devices which are in a 10

2.3 Non-Functional Requirements

Safety and Security:

2.4 User Interfaces

Dept.of CSE, VCET Puttur Page 9

__