Mini Project Documentation
Mini Project Documentation
Submitted By
VAKAPALLI RAJESH
19555F0086
CERTIFICATE
Thisis to certify that this Mini project “Cloud Based Health-Care Services” is being
submitted by VAKAPALLI RAJESH (19555F0086) in partial fulfilment of the
requirements for IV Semester of MASTER OF COMPUTER APPLICATIONS in the
academic year 2019-2020 to the GIET AUTONOMOUS is a bonafide work carried out him
under my guidance and supervision.
The result embodied in this project has not been submitted to any other University or
Institute for the award of degree
CO-ORDINATOR SUPERVISOR
ACKNOWLEDGEMENT
It is privilege for me to have under taken the project “CLOUD BASED HEALTH-CARE
SERVICES” in GIET (A), Rajahmundry.
I avail this opportunity to express my deep sense of gratitude and heart full thanks to
Mr. K. SASI KIRAN VARMA, Honorable managing director of GODAVARI
INSTITUTE OF ENGINEERING & TECHNOLOGY, RAJAHMUNDRY.
Although a leaflet title “Acknowledgement” cannot represent my true feelings for all
these persons, I feel very much thankful to all of them and also to my PARENTS and
FRIENDS for encouraging and giving me all the moral support required for making this
endeavour a reality.
VAKAPALLI RAJESH
(19555F0086)
DECLARATION
I VAKAPALLI RAJESH (PIN 19555F0086) declare that the mini project title
“CLOUD BASED HEALTH-CARE SERVICES” is a bonafide work carried out by me
and has not been submitted to any other university or college for the award of degree.
VAKAPALLI RAJESH
(19555F0086)
TABLE OF CONTENTS
Title Page.No
CHAPTER-1: INTRODUCTION
1.2 Scope 2
CHAPTER-2: SYSTEMANALYSIS
References 29
ABSTRACT
In the healthcare sector, the growing demand for and adoption of software development in the
cloud environment to cope with and fulfill current and future demands in healthcare services.
In this paper, we propose a flexible, secure, cost-effective, and privacy preserved cloud-based
framework for the healthcare environment. A secure and efficient framework for the
government EHR system, in which fine-grained access control can be afforded based on
multi-authority cipher text-policy attribute-based encryption (CP-ABE), together with a
hierarchical structure, to enforce access control policies. The proposed framework will allow
decision-makers in Saudi Arabia to develop the healthcare sector and to benefit from the
existing e-government cloud computing platform ``Yasser,'' which is responsible for
delivering shared services through a highly efficient, reliable, and safe environment. This
framework aims to provide health services and facilities from the government to citizens
(G2C). Furthermore, multifactor applicant authentication has been identified and proofed in
cooperation with two trusted authorities. The security analysis and comparisons with the
related frameworks have been conducted.
CHAPTER-1
INTRODUCTION
1.1 Purpose
The traditional health system has been replaced by an electronic health information
system because the traditional system has been found to be ineffective due to a number of
issues, including low storage capacity, high operating and maintenance costs, and system
integration. The computerized health system was then replaced by cloud computing because
it relies on a more efficient infrastructure, as well as the many benefits of cloud computing in
IT, such as cost, scalability, flexibility, and other features. The use of cloud computing in
electronic health records reduces costs in the provision of health services, maintenance costs,
networks, licensing fees, and infrastructure in general, and this will therefore encourage
developers to adopt the cloud in healthcare.
The rapid shift to the cloud and its use in healthcare systems has raised concerns
about crucial issues of privacy and information security. The adoption of the cloud in IT
increases the focus and concern of healthcare providers on clinical and patient-related
services and reduces attention on infrastructure management. The sharing of personal and
health information across the Internet and various servers outside the safe environment of the
healthcare institution has led to a number of problems related to privacy, security, access, and
compliance issues.
In the literature, there are no existing powerful frameworks that clearly address all
viable schemes and interrelationships between cloud computing and health- care technology.
Improving the framework for healthcare in cloud computing has been studied by several
researchers. Further developments and solutions in these challenges will increase the
adoption of cloud health- care and encourage healthcare providers to move forward with
cloud-based services. Our contributions can be summarized as follows:
1. Applying, using, and modifying the most recent encryption and decryption mechanisms
suited for cloud-based EHR systems. The proposed scheme does not use the standard
encryption system, which is not suited to the cloud environment.
1.2 Scope
A new idea in encryption called attribute-based encryption (ABE). In the ABE scheme,
cipher texts and users’ secret keys are associated with a set of attributes. A user can decrypt a
cipher text if, and only if, there is a match between its secret key and the cipher text. ABE has
been applied and tested in many cloud-based applications.
2.1Existing System
These health problems could be prevented before they occur or their complications prevented
by early detection. This is due to a combination of factors: planning, operational, and
technical. If we were able to overcome them, this would lead to significant progress in the
level of health care. In addition, there is a weakness and lack of available hospital
information systems, which is some of the most advanced software that directly serves all
technical and administrative healthcare activities, ensuring that the medical institution has full
control over all its activities and resources. The successes of these advanced systems do not
depend on the exact selection of equipment and software for storage. Rather, their success
depends on their suitability for different users from healthcare providers, such as doctors,
nurses,technicians, and even administratorsfiwhere the vision and priorities of each of these
categories differ, and their information needs vary, as do the benefits of each of these
systems.
2.1.1 Disadvantages
The traditional health system (paper) has been replaced by an electronic health information
system because the traditional system has been found to be ineffective due to a number of
issues, including low storage capacity, high operating and maintenance costs, and system
integration.
In the literature, there are no existing powerful frameworks that clearly address all viable
schemes and interrelationships between cloud computing and healthcare technology
Advantages
1.Data privacy
2.Fine grained access control
Modules Description
The Patient
The patient is the main entity in our proposed framework. The patient has the following main
tasks:
A new patient must apply for an authentication request to the trusted authority to get his or
her identification number (ID), and then he or she will be able to use the system services.
Creates the patient history record (PHR) and stores it at the cloud server.
Ensures the PHR is fully secured and protected by defining an (attribute-based) access policy
that can be used for encrypting the data before it is distributed.
Healthcare Providers
Healthcare providers are individuals who provide healthcare services of all kinds in an
organized manner to all members of a community. The healthcare providers could include the
following members: health practitioners and specialists, physicians, nurses, pharmacists,
surgeons, medical technicians,
laboratory workers, and other employees. Each of these members must have access to some
part of the patient records for specific purposes.
Each healthcare provider must complete the following tasks:
Apply for an identification number (ID) from the trusted authority to be able to access
specific parts of the
patient's record.
Apply a request for the secret key attached with the appropriate parameters.
Be able to decrypt, modify, and encrypt the same document with the same key.
Trusted Authority
• Technical Feasibility
• Operational Feasibility
• Economical Feasibility
ECONOMIC FEASIBILITY
A system can be developed technically and that will be used if installed must still be a
good investment for the organization. In the economical feasibility, the development cost in
creating the system is evaluated against the ultimate benefit derived from the new systems.
Financial benefits must equal or exceed the costs.
The system is economically feasible. It does not require any addition hardware or
software. Since the interface for this system is developed using the existing resources and
5 Department of Computer Applications, GIET (A), Rajamahendravaram
technologies available at NIC, There is nominal expenditure and economical feasibility for
certain.
OPERATIONAL FEASIBILITY
Proposed projects are beneficial only if they can be turned out into information
system. That will meet the organization’s operating requirements. Operational feasibility
aspects of the project are to be taken as an important part of the project implementation.
Some of the important issues raised are to test the operational feasibility of a project includes
the following: -
The well-planned design would ensure the optimal utilization of the computer resources and
would help in the improvement of performance status.
TECHNICAL FEASIBILITY
The technical issue usually raised during the feasibility stage of the investigation
includes the following:
SYSTEM REQUIREMENTS
HSP(Owner):
HSP Upload Patient Details, view all previously uploaded documents and view public keys.
Usability
The system is designed with completely automated process hence there is no or less user
intervention.
Reliability
The system is more reliable because of the qualities that are inherited from the chosen
platform java. The code built by using java is more reliable.
Performance
This system is developing in the high level languages and using the advanced front-end and
back-end technologies it will give response to the end user on client system with in very less
time.
Supportability
SYSTEM DESIGN
The purpose of the design phase is to plan a solution of the problem specified by the
requirement document. This phase is the first step in moving from the problem domain to the
solution domain. In other words, starting with what is needed, design takes us toward how to
satisfy the needs. The design of a system is perhaps the most critical factor affection the
quality of the software; it has a major impact on the later phase, particularly testing,
maintenance. The output of this phase is the design document. This document is similar to a
blueprint for the solution and is used later during implementation, testing and maintenance.
The design activity is often divided into two separate phases System Design and Detailed
Design. System Design also called top-level design aims to identify the modules that should
be in the system, the specifications of these modules, and how they interact with each other to
produce the desired results.
System Model
Introduction to UML
The unified Modeling Language (UML) is a standard language for writing software
blueprints. The UML may be used to visualize, specify , construct and document the artifacts
of software-intensive system.
The goal of UML is to provide a standard notation that can be used by all object - oriented
methods and to select and integrate the best elements .UML is itself does not prescribe or
advice on how to use that notation in a software development process or as part of an object -
design methodology. The UML is more than just bunch of graphical symbols. Rather , behind
each symbol in the UML notation is well-defined semantics.
The system development focuses on three different models of the system.
➔ Functional model
➔ Object model
➔ Dynamic model
Functional model in UML is represented with use case diagrams , describing the
functionality of the system from user point of view.
Object model in UML is represented with class diagrams , describing the structure of the
system in terms of objects , attributes , associations and operations
A graphical tool used to describe and analyze the moment of data through a system manual or
automated including the process, stores of data, and delays in the system. Data Flow
Diagrams are the central tool and the basis from which other components are developed. The
transformation of data from input to output, through processes, may be described logically
and independently of the physical components associated with the system. The DFD is also
DFDs are the model of the proposed system. They clearly should show the requirements on
which the new system should be built. Later during design activity this is taken as the basis
for drawing the system’s structure charts. The Basic Notation used to create a DFD’s are as
follows:
2. Process: People, procedures, or devices that use or produce (Transform) Data. The
SYSTEM IMPLEMENTATION
The following Java technology lets developers, designers, and business partners develop and
deliver a consistent user experience, with one environment for applications on mobile and
embedded devices. Java meshes the power of a rich stack with the ability to deliver
customized experiences across such devices.
Java APIs are libraries of compiled code that you can use in your programs. They let you add
ready-made and customizable functionality to save you programming time.
Java programs are run (or interpreted) by another program called the Java Virtual Machine.
Rather than running directly on the native operating system, the program is interpreted by the
Java VM for the native operating system. This means that any computer system with the Java
VM installed can run Java programs regardless of the computer system on which the
applications were originally developed.
In the Java programming language, all source code is first written in plain text files ending
with the .java extension. Those source files are then compiled into .class files by the javac
compiler. A .class file does not contain code that is native to your processor; it instead
Because the Java VM is available on many different operating systems, the same .class files
are capable of running on Microsoft Windows, the Solaris TM Operating System (Solaris
OS), Linux, or Mac OS.
The Java programming language is a high-level language that can be characterized by all of
the following buzzwords:
span.psw {
float: right;
padding-top: 16px;
}
/* The Modal (background) */
.modal {
display: none; /* Hidden by default */
position: fixed; /* Stay in place */
z-index: 1; /* Sit on top */
left: 0;
top: 0;
width: 100%; /* Full width */
height: 100%; /* Full height */
overflow: auto; /* Enable scroll if needed */
background-color: rgb(0,0,0); /* Fallback color */
background-color: rgba(0,0,0,0.4); /* Black w/ opacity */
padding-top: 60px;
}
/* Modal Content/Box */
.modal-content {
background-color: #fefefe;
margin: 5% auto 15% auto; /* 5% from the top, 15% from the bottom and centered */
border: 1px solid #888;
width: 80%; /* Could be more or less, depending on screen size */
}
@keyframes animatezoom {
from {transform: scale(0)}
to {transform: scale(1)}
}
/* Change styles for span and cancel button on extra small screens */
@media screen and (max-width: 300px) {
span.psw {
<label for="password"><b>Password</b></label>
<input type="text" placeholder="Enter Password" name="password" required>
<label for="email"><b>Email</b></label>
<input type="text" placeholder="Enter Email" name="email" required>
<label for="dob"><b>Date Of Birth</b></label>
<input type="date" placeholder="Enter dob" name="dob" required>
<br/>
<label for="mobile"><b>Mobile</b></label>
<input type="text" placeholder="Enter Mobile" name="mobile" pattern="{1}[789]{9}[0-
9]" title="Please Enter Mobile Number" maxlength="10" required>
<button type="submit">Sign UP</button>
</div>
<div class="container" style="background-color:#f1f1f1">
<button type="button" onclick="document.getElementById('id02').style.display='none'"
class="cancelbtn">Cancel</button>
</div>
</form>
</div>
CHAPTER-6
TESTING METHODOLOGIES
o Unit Testing.
o Integration Testing.
o User Acceptance Testing.
o Output Testing.
o Validation Testing.
Unit Testing
Unit testing focuses verification effort on the smallest unit of Software design that is
the module. Unit testing exercises specific paths in a module’s control structure to ensure
complete coverage and maximum error detection. This test focuses on each module
individually, ensuring that it functions properly as a unit. Hence, the naming is Unit Testing.
During this testing, each module is tested individually and the module interfaces are
verified for the consistency with design specification. All important processing path are
tested for the expected results. All error handling paths are also tested.
Integration Testing
Integration testing addresses the issues associated with the dual problems of
verification and program construction. After the software has been integrated a set of high
order tests are conducted. The main objective in this testing process is to take unit tested
modules and builds a program structure that has been dictated by design.
This method begins the construction and testing with the modules at the lowest level
in the program structure. Since the modules are integrated from the bottom up, processing
required for modules subordinate to a given level is always available and the need for stubs is
eliminated. The bottom up integration strategy may be implemented with the following steps:
▪ The low-level modules are combined into clusters into clusters that perform a
specific Software sub-function.
▪ A driver (i.e.) the control program for testing is written to coordinate test case input
and output.
▪ The cluster is tested.
▪ Drivers are removed and clusters are combined moving upward in the program
structure
The bottom up approaches tests each module individually and then each module is module is
integrated with a main module and tested for functionality.
User Acceptance of a system is the key factor for the success of any system. The system
under consideration is tested for user acceptance by constantly keeping in touch with the prospective
system users at the time of developing and making changes wherever required. The system developed
provides a friendly user interface that can easily be understood even by a person who is new to the
system.
Output Testing
After performing the validation testing, the next step is output testing of the proposed system,
since no system could be useful if it does not produce the required output in the specified format.
Asking the users about the format required by them tests the outputs generated or displayed by the
system under consideration. Hence the output format is considered in 2 ways – one is on screen and
another in printed format.
CHAPTER-7
The proposed scheme can be adopted by any government that has a cloud computing
infrastructure and provides treatment services to the majority of citizen patients. Future work
includes implementing and evaluating the proposed scheme in a real-world environment