BEHR - Review (1) - For Merge

Blockchain-Based Electronic Health Records Management
ABSTRACT
Electronic Health Records (EHRs) are electronically-stored health information in a digital
format. EHRs are typically shared among healthcare stakeholders and face power failure, data
misuse, lack of privacy, security, and audit trail. On the other hand, blockchain is the
revolutionary invention of the twentieth century that offers a distributed and decentralized
setting to communicate among nodes in a list of networks without a central authority. It can
address the limitations of EHRs management and provide a safer, secured, and decentralized
environment for exchanging EHRs data. Three categories of blockchain-based potential
solutions have been proposed by researchers to handle EHRs: conceptual, prototype, and
implemented. This project focused on a Systematic Literature Review (SLR) to find and
analyze articles submitted either conceptual or implemented to manage EHRs using
blockchain. The project examined papers that were collected from various publication
categories. The deep technical analysis focused on evaluating articles based on privacy,
security, scalability, accessibility, cost, consensus algorithms, and the type of blockchain
used. The SLR found that blockchain technology promises to provide decentralization,
security, and privacy that traditional EHRs often lack. Moreover, results obtained from the
detailed studies would provide potential researchers with the type of blockchain for future
research.
INTRODUCTION
Blockchain has been a buzzword in Information and Communication Technology industry in
recent years. The rise of this new technology has greater potentials to solve data privacy,
security, and integrity issues. The word blockchain came in the front line after the publication
of the Bitcoin white paper by Satoshi Nakamoto in 2008. The fundamental mechanism
behind Bitcoin is to make financial transactions possible without the intervention of a trusted
third party. The technology is mainly considered a distributed Peer to Peer (P2P) network
where digital data may publicly or privately be allocated to all users on the web in a secure
and verifiable way. In traditional financial transactions, both sender and receiver need to
depend on a Trusted Third Party (TTP), e.g., bank. It involves a few security issues and
operational difficulties. For instance, a TTP gets access to a user’s financial data, which
indicates the lack of user privacy. Moreover, the time involved in a TTP transaction is
lengthy as there are many steps in between the operation. Furthermore, users need to pay the
TTP for their service. Bitcoin solves the above limitations and makes the TTP vanish for a
successful transaction between two users
Tons of healthcare data would be highly beneficial for healthcare providers if
analyzed. These data can help us in fighting the virus through medical assistance, early
notification, and recommendation. However, it has become a big challenge for researchers to
store and analyze health data because most are incomplete and imperfect. Therefore
verification and validation of such data are crucial for reporting, and recommendation.
Blockchain technology has great potentials to tackle the pandemic crisis. It can help build a
decentralized data tracking system that can be retrieved when necessary. In addition, this big
healthcare data, especially EHRs, is vulnerable to privacy and security breaches. Starting
from the COVID-19 outbreak, healthcare providers and academic organizations faced several
complex cyberattacks. The International Criminal Police Organization (INTERPOL)
published a report about cyber-attacks related to COVID-19 in April 2020 Healthcare
industries have been severely affected alongside others by these attacks. On 6 May 2020,
INTERPOL released an awareness campaign where various cyber-attacks during pandemic
were listed. Therefore, it is crucial to take the necessary steps to tackle these threats
By considering the above scenario, this project aims to identify the potentiality of
blockchain to manage EHRs and show the challenges and future scopes. This systematic
review only explores research that offers conceptual solutions, experimental results,
prototypes, and blockchain implementations for managing EHRs.
LITERATURE SURVEY
1. Title : A systematic review of blockchain in healthcare: Frameworks, prototypes, and

implementations
Author : L Garg
Description : Blockchain, a form of distributed ledger technology has attracted the interests
of stakeholders across several sectors including healthcare. Its' potential in the multi-
stakeholder operated sector like health has been responsible for several investments, studies,
and implementations. Electronic Health Records (EHR) systems traditionally used for the
exchange of health information amongst healthcare stakeholders have been criticised for
centralising power, failures and attack-points with exchange data custodians. EHRs have
struggled in the face of multi-stakeholder and system requirements while adhering to
security, privacy, ethical and other regulatory constraints. Blockchain is promising amongst
others to address the many EHR challenges, primarily trustless and secure exchange of health
information amongst stakeholders. Many blockchain-in-healthcare frameworks have been
proposed; some prototyped and/or implemented. This study leveraged the PRISMA
framework to systematically search and evaluate the different models proposed; prototyped
and/or implemented.
2. Title : Measuring data quality through a source data verification audit in a clinical research
setting
Author : Y Probst
Description : Health data has long been scrutinised in relation to data quality and integrity
problems. Currently, no internationally accepted or "gold standard" method exists measuring
data quality and error rates within datasets. conducted a source data verification (SDV) audit
on a prospective clinical trial dataset. An audit plan was applied to conduct 100% manual
verification checks on a 10% random sample of participant files. A quality assurance rule was
developed. Error was coded: correct, incorrect (valid or invalid), not recorded or not entered.
Audit-1 had a total error of 33% and audit-2 36%. The physiological section was the only
audit section to have 5% error. Data not recorded to case report forms had the greatest impact
on error calculations. A significant association (p=0.00) was found between audit-1 and
audit-2 and whether or not data was deemed correct or incorrect. Our study developed a
straightforward method to perform a SDV audit. An audit rule was identified and error
coding was implemented. Findings demonstrate that monitoring data quality by a SDV audit
can identify data quality and integrity issues within clinical research settings allowing quality
improvement to be made. The authors suggest this approach be implemented for future
research.
3. Title : A novel architecture for tamper proof electronic health record management system
using blockchain wrapper
Author : A Boras and S Rahman
Description : In this paper, present a novel architecture of blockchain-based tamper-proof
electronic health record (EHR) management system. Recording electronic health data in
cloud-based storage systems always pose a threat to information security. Intruders can delete
or tamper EHR of patients, giving benefits to insurance companies or hiding medical
malpractices (e.g. misdiagnosis and delayed diagnosis). A tamper-proof EHR management
system is required that would essentially solve such issues. The blockchain is an emerging
technology that can be adapted to develop a tamper-proof data management system.
However, establishing a new blockchain based system replacing the existing system is
expensive. In our proposed architecture, we introduce a wrapper layer integration mechanism,
named as the blockchain handshaker, between the existing cloud-based EHR management
system and public blockchain network to develop a tamper-proof health record management
system.
4. Title : Secure and transparent KYC for banking system using IPFS and blockchain
technology
Author : M Kaisar and R Hasan
Description : Know your client (KYC) is a rule for the financial framework to approve a
client based on character, propriety, and risk assessment when establishing a financial
relationship. With the growing concern about security, the KYC cycle is perplexing and
includes a significant cost for completing for a single client. Through InterPlanetary File
System(IPFS) and blockchain innovation, we propose anaffordable, quick, secure, and simple
stage for KYC archive check for the Banking framework. The proposed framework allows a
client to open a record at one bank, complete the KYC cycle there, and generate a hash value
using the IPFS organization and distribute it via the blockchain method. After obtaining the
confidential key, anyBank/monetary association can recover and securely store client
information (i.e., KYC) utilizing the IPFS organization if the client wishes to open another
account with that Bank/monetary association. The proposed framework can save time,
money, and tedious work during the KYC cycle when someone tries to open a record at
multiple banks.
5. Title : A framework for pandemic prediction using big data analytics

Author : M Ahmed and I Ahmed
Description :IoT (Internet of Things) devices and smart sensors are used in different life
sectors, including industry, business, surveillance, healthcare, transportation, communication,
and many others. These IoT devices and sensors produce tons of data that might be valued
and beneficial for healthcare organizations if it becomes subject to analysis, which brings big
data analytics into the picture. Recently, the novel coronavirus pandemic (COVID-19)
outbreak is seriously threatening human health, life, production, social interactions, and
international relations. In this situation, the IoT and big data technologies have played an
essential role in fighting against the pandemic. The applications might include the rapid
collection of big data, visualization of pandemic information, breakdown of the epidemic
risk, tracking of confirmed cases, tracking of prevention levels, and adequate assessment of
COVID-19 prevention and control. In this paper, demonstrate a health monitoring framework
for the analysis and prediction of COVID-19. The framework takes advantage of Big data
analytics and IoT. We perform descriptive, diagnostic, predictive, and prescriptive analysis
applying big data analytics using a novel disease real data set, focusing on different pandemic
symptoms. This work's key contribution is integrating Big Data Analytics and IoT to analyze
and predict a novel disease. The neural network-based model is designed to diagnose and
predict the pandemic, which can facilitate medical staff. predict pandemic using neural
networks and also compare the results with other machine learning algorithms.
6. Title : Healthcare cyber-attacks and the COVID-19 pandemic: An urgent threat to global
health
Author : K Stevenson
Description : The Coronavirus Disease 2019 (COVID-19) pandemic has resulted in
widespread disruption to the healthcare industry. Alongside complex issues relating to
ensuring sufficient healthcare capacity and resourcing, healthcare organisations and
universities are now also facing heightened cyber-security threats in the midst of the
pandemic. Since the outbreak began various healthcare providers and academic institutions
across the world have been targeted in a variety of complex and coordinatized cyber-attacks.
International and national regulatory bodies have stressed the urgent need for healthcare
providers and universities to protect themselves against cyber-attacks during COVID-19,
recognising that a growing number of cyber-criminals are seeking to capitalise on the
vulnerabilities of the healthcare sector during this period. This includes a desire to steal
intellectual property such as data relating to COVID-19 vaccine development, modelling and
experimental therapeutics. It is therefore essential that healthcare providers and universities
ensure they are informed, protected and prepared to respond to any cyber-threat. This article
outlines key COVID-19 cyber-security principles for both healthcare organisations and
academic institutions.
7. Title : Electronic medical record security sharing model based on blockchain

Author : S Wu and J Du
Description : The emergence of electronic medical records has provided great convenience
for the storage and analysis of medical data. However, electronic medical records contain a
large amount of personal privacy information, it is still very difficult to share medical
information among various medical institutions. As the underlying technology of Bitcoin,
blockchain technology has the characteristics of decentralization, security, trustworthiness,
collective maintenance, and cannot be tampered, it is suitable for data protection and sharing.
In this paper, data masking technology and Inter Planetary File System (IPFS) are introduced
to build a safe and efficient electronic medical record sharing model based on blockchain.
The model can not only guarantee the security of medical data, but also save resources in
blockchain.
8. Title : Scalable architecture for sharing EHR using the hyperledger blockchain
Author : F Horitha and V Rocha
Description : Blockchain technology has been applied in several areas, ranging from
financial to health. Although this technology offers benefits, for instance the immutability,
anonymity, and decentralization of information, its use presents some problems, been the
scalability in terms of storage size one of them. This paper presents a scalable architecture for
sharing electronic health records using a multi-channel hyperledger blockchain. The
architecture uses one blockchain to record patient visits and one blockchain for each health
institution to record links that point to Electronic Health Records (EHRs) stored in external
systems. Among the main conclusions, the final results highlight the scalability of the
proposed architecture, when compared to the related work models in the heterogeneous
network.
9. Title : Proof of vote: A highperformance consensus protocol based on vote mechanism &
consortium blockchain
Author : K Li and H Li
Description : Bitcoin introduces a revolutionary decentralized consensus mechanism.
However, Bitcoin-derived consensus mechanisms applied to public blockchain are inadequate
for the deployment scenarios of budding consortium blockchain. We propose a new
consensus algorithm, Proof of Vote (POV). The consensus is coordinated by the distributed
nodes controlled by consortium partners which will come to a decentralized arbitration by
voting. The key idea is to establish different security identity for network participants, so that
the submission and verification of the blocks are decided by the agencies' voting in the league
without the depending on a third-party intermediary or uncontrollable public awareness.
Compared with the fully decentralized consensus-Proof of Work (POW), POV has
controllable security, convergence reliability, only one block confirmation to achieve the
transaction finality, and low-delay transaction verification time.
10. Title : Consumer experience with and attitudes toward health information technology
Author : R Kaushal and M Miller
Description : Electronic health records (EHR) are becoming more common because of the
federal EHR incentive programme, which is also promoting electronic health information
exchange (HIE). To determine whether consumers' attitudes toward EHR and HIE are
associated with experience with doctors using EHR, a nationwide random-digit-dial survey
was conducted in December 2011. Of 1603 eligible people contacted, 1000 (63%)
participated. Most believed EHR and HIE would improve healthcare quality (66% and 79%,
respectively). Respondents whose doctor had an EHR were more likely to believe that these
technologies would improve quality (for EHR, OR 2.3; for HIE, OR 1.7). However,
experience with physicians using EHR was not associated with privacy concerns. Consumers
whose physicians use EHR were more likely to believe that EHR and HIE will improve
healthcare when compared to others. However, experience with a physician using an EHR
had no relationship with privacy concerns.
SYSTEM ARCHITECTURE
Server
Login,
View All Hospitals and
Authorize,
View All Clients and
Authorize,
Add Block chain Code,
View All Block chain Code,
View All Patient Details,
View All Transactions,
View All SK Request and
Response Details,
View All SK Requests and
Permit,
View All Credential Attackers
Details,
Trace and View All Disease
Records by Block chain,
Process all User View No. of Same Disease in
queries Chart,
View Patient Searched Rank in

chart,
Store and retrievals
Hospital client
Registering
the User
Register and Login, Register and Login,

View Profile,
View Profile,
Search Patient,
Upload Patient Details,
Search Patients by Age,
View All Uploaded Patient Details,
View All SK Requests and
Response,
View All SK Permitted and

Download,
METHODOLOGY
Tons of healthcare data would be highly beneficial for healthcare providers if analyzed.
These data can help us in fighting the virus through medical assistance, early notification, and
recommendation. However, it has become a big challenge for researchers to store and analyze
health data because most are incomplete and imperfect. Therefore verification and validation
of such data are crucial for reporting, and recommendation. Blockchain technology has great
potentials to tackle the pandemic crisis. It can help build a decentralized data tracking system
that can be retrieved when necessary. In addition, this big healthcare data, especially EHRs, is
vulnerable to privacy and security breaches. Starting from the COVID-19 outbreak,
healthcare providers and academic organizations faced several complex cyberattacks. The
International Criminal Police Organization (INTERPOL) published a report about cyber-
attacks related to COVID-19 in April 2020 Healthcare industries have been severely affected
alongside others by these attacks. On 6 May 2020, INTERPOL released an awareness
campaign where various cyber-attacks during pandemic were listed. Therefore, it is crucial to
take the necessary steps to tackle these threats .By considering the above scenario, this
project aims to identify the potentiality of blockchain to manage EHRs and show the
challenges and future scopes. This systematic review only explores research that offers
conceptual solutions, experimental results, prototypes, and blockchain implementations for
managing EHRs.
MODULES
Server
In this module, the Admin has to login by using valid user name and password. After login
successful he can do some operations such as Login, View All Hospitals and Authorize,
View All Clients and Authorize, Add Block chain Code, View All Block chain Code, View
All Patient Details, View All Transactions, View All SK Request and Response Details,
View All SK Requests and Permit, View All Credential Attackers Details, Trace and View
All Disease Records by Block chain, View No. of Same Disease in Chart, View Patient
Searched Rank in chart, View Patient File Rank in chart, View No. Of Attackers on Patient.
Client
In this module, there are n numbers of users are present. User should register with group
option before doing some operations. After registration successful he has to wait for admin
to authorize him and after admin authorized him. He can login by using authorized user name
and password. Login successful he will do some operations like Register and Login, View
Profile, Search Patient, Search Patients by Age, View All SK Requests and Response, View
All SK Permitted and Download,
Hospital
In this module, there are n numbers of users are present. Hospitaluser should register with
group option before doing some operations. After registration successful he has to wait for
admin to authorize him and after admin authorized him. He can login by using authorized
user name and password. Login successful he will do some operations like Register and
Login, View Profile,Upload Patient Details, View All Uploaded Patient Details,
DESIGN
UML DIAGRAMS
The Unified Modelling Language (UML) is a standard language for specifying, visualizing,
constructing, and documenting the artifacts of software systems, as well as for business
modeling and other non-software systems. The UML represents a collection of best
engineering practices that have proven successful in the modeling of large and complex
systems. The UML is a very important part of developing objects oriented software and the
software development process. The UML uses mostly graphical notations to express the
design of software projects. Using the UML helps project teams communicate, explore
potential designs, and validate the architectural design of the software.
As the strategic value of software increases for many companies, the industry looks for
techniques to automate the production of software and to improve quality and reduce cost and
time-to-market. These techniques include component technology, visual programming,
patterns and frameworks. Businesses also seek techniques to manage the complexity of
systems as they increase in scope and scale. In particular, they recognize the need to solve
recurring architectural problems, such as physical distribution, concurrency, replication,
security, load balancing and fault tolerance. Additionally, the development for the World
Wide Web, while making some things simpler, has exacerbated these architectural problems.
The Unified Modeling Language
(UML) was designed to respond to these needs. Simply, Systems design refers to the process
of defining the architecture, components, modules, interfaces, and data for a system to satisfy
specified requirements which can be done easily through UML diagrams.
Object-Oriented Concepts
UML can be described as the successor of object-oriented (OO) analysis and design.
An object contains both data and methods that control the data. The data represents the state
of the object. A class describes an object and they also form a hierarchy to model the real-
world system. The hierarchy is represented as inheritance and the classes can also be
associated in different ways as per the requirement.
Objects are the real-world entities that exist around us and the basic concepts such as
abstraction, encapsulation, inheritance, and polymorphism all can be represented using
UML.
UML is powerful enough to represent all the concepts that exist in object-oriented analysis
and design. UML diagrams are representation of object-oriented concepts only. Thus, before
learning UML, it becomes important to understand OO concept in detail.
Following are some fundamental concepts of the object-oriented world −
 Objects − Objects represent an entity and the basic building block.
 Class − Class is the blue print of an object.
 Abstraction − Abstraction represents the behavior of an real world entity.
 Encapsulation − Encapsulation is the mechanism of binding the data together and

hiding them from the outside world.
 Inheritance − Inheritance is the mechanism of making new classes from existing

ones.
 Polymorphism − It defines the mechanism to exists in different forms.
OO Analysis and Design
OO can be defined as an investigation and to be more specific, it is the investigation of

objects. Design means collaboration of identified objects.
Thus, it is important to understand the OO analysis and design concepts. The most important
purpose of OO analysis is to identify objects of a system to be designed. This analysis is also
done for an existing system. Now an efficient analysis is only possible when we are able to
start thinking in a way where objects can be identified. After identifying the objects, their
relationships are identified and finally the design is produced.
The purpose of OO analysis and design can described as −
 Identifying the objects of a system.
 Identifying their relationships.
 Making a design, which can be converted to executables using OO languages.

There are three basic steps where the OO concepts are applied and implemented. The steps
can be defined as
OO Analysis → OO Design → OO implementation using OO languages
The above three points can be described in detail as −
 During OO analysis, the most important purpose is to identify objects and describe
them in a proper way. If these objects are identified efficiently, then the next job of
design is easy. The objects should be identified with responsibilities. Responsibilities
are the functions performed by the object. Each and every object has some type of
responsibilities to be performed. When these responsibilities are collaborated, the
purpose of the system is fulfilled.
 The second phase is OO design. During this phase, emphasis is placed on the
requirements and their fulfilment. In this stage, the objects are collaborated
according to their intended association. After the association is complete, the design
is also complete.
 The third phase is OO implementation. In this phase, the design is implemented using
OO languages such as Java, C++, etc.
Role of UML in OO Design
UML is a modeling language used to model software and non-software systems. Although
UML is used for non-software systems, the emphasis is on modeling OO software
applications. Most of the UML diagrams discussed so far are used to model different aspects
such as static, dynamic, etc. Now whatever be the aspect, the artifacts are nothing but
objects.
Hence, the relation between OO design and UML is very important to understand. The OO
design is transformed into UML diagrams according to the requirement.
In this project ,basic UML diagrams have been explained
 Use Case Diagram

 Class Diagram
 Sequence Diagram
 Collaboration Diagram
 Activity Diagram
 Deployment Diagram
1. . Use case diagram

A use case diagram in the Unified Modelling Language (UML) is a type of behavioural
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.
A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. The use case is made up of a set of possible sequences of interactions between
systems and users in a particular environment and related to a particular goal. It consists of a
group of elements (for example, classes and interfaces) that can be used together in a way
that will have an effect larger than the sum of the separate elements combined. The use case
should contain all system activities that have significance to the users. A use case can be
thought of as a collection of possible scenarios related to a particular goal, indeed, the use
case and goal are sometimes considered to be synonymous.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.
Parts of Use Case Diagram
System boundary boxes (optional)
A rectangle is drawn around the use cases, called the system boundary box, to indicate the
scope of system. Anything within the box represents functionality that is in scope and
anything outside the box is not Relationships.
Include
In one form of interaction, a given use case may include another. "Include is a Directed
Relationship between two use cases, implying that the behavior of the included use case is
inserted into the behavior of the including use case”.
The first use case often depends on the outcome of the included use case. This is useful for
extracting truly common behaviours from multiple use cases into a single description. The
notation is a dashed arrow from the including to the included use case, with the label
"«include»". This usage resembles a macro expansion where the included use case behavior is
placed inline in the base use case behavior. There are no parameters or return values. To
specify the location in a flow of events in which the base use case includes the behavior of
another, you simply write include followed by the name of use case you want to include, as in
the following flow for track order.
Extend
In another form of interaction, a given use case (the extension) may extend another. This
relationship indicates that the behavior of the extension use case may be inserted in the
extended use case under some conditions. The notation is a dashed arrow from the extension
to the extended use case, with the label "«extend»". The notes or constraints may be
associated with this relationship to illustrate the conditions under which this behavior will be
executed. Modelers use the «extend» relationship to indicate use cases that are "optional" to
the base use case. Depending on the modeler’s approach "optional" may mean "potentially
not executed with the base use case" or it may mean "not required to achieve the base use
case goal".
Associations
Associations between actors and use cases are indicated in use case diagrams by solid lines.
An association exists whenever an actor is involved with an interaction described by a use
case. Associations are modelled as lines connecting use cases and actors to one another, with
an optional arrowhead on one end of the line. The arrowhead is often used to indicate the
direction of the initial invocation of the relationship or to indicate the primary actor within
the use case. The arrowheads imply control flow and should not be confused with data flow.
STEPS TO DRAW USE CASES
 Identifying Actor
 Identifying Use cases
 Review your use case for completeness

Login, View All Hospitals and Authorize, View All
Clients and Authorize,
Add Block chain Code, View All Block chain Code, View All
Patient Details,
View All Transactions, View All SK Request and

Response Details, View All SK Requests and Permit,
View All Credential Attackers Details, Trace and View

All Disease Records by Block chain, View No. of Same
Disease in Chart,
Register and Login, View Profile,
Cloud Server
Hospital
Upload Patient Details, View All
Uploaded Patient Details, Register and
Login
,View My Details
View Time Delay Results, View

Throughput Results,
Client
Register and Login, View Profile
,View My Details
Search Patient, Search Patients by Age,
View All SK Requests and Response,

View All SK Permitted and Download,
2. Class Diagram
UML class diagrams model static class relationships that represent the fundamental
architecture of the system. Note that these diagrams describe the relationships between
classes, not those between specific objects instantiated from those classes. Thus the diagram
applies to all the objects in the system.
A class diagram consists of the following features:
 Classes: These titled boxes represent the classes in the system and contain information
about the name of the class, fields, methods and access specifies. Abstract roles of the
Class in the system can also be indicated
 Interfaces: These titled boxes represent interfaces in the system and contain
information about the name of the interface and its methods. Relationship Lines that
model the relationships between classes and interfaces in the system.
 Dependency: A dotted line with an open arrowhead that shows one entity depends on
the behavior of another entity. Typical usages are to represent that one class
instantiates another or that it uses the other as an input parameter
 Aggregation: Represented by an association line with a hollow diamond at the tail
end. An aggregation models the notion that one object uses another object without
"owning" it and thus is not responsible for its creation or destruction.
 Inheritance: A solid line with a solid arrowhead that points from a sub-class to a
super class or from a sub-interface to its super-interface.
 Implementation: A dotted line with a solid arrowhead that points from a class to the
interface that it implement
 Composition: Represented by an association line with a solid diamond at the tail end.
A composition models the notion of one object "owning" another and thus being
responsible for the creation and destruction of another object.
Server Hospital
Login, View All Hospitals and Authorize, View All

Clients and Authorize, Add Block chain Code,
Methods View All Block chain Code, View All Patient
Register and Login, View Profile, Upload Patient
Details, View All Transactions, View All SK
Details, View All Uploaded Patient Details,
Request and Response Details, View All SK Methods
Requests and Permit, View All Credential
Attackers Details, Trace and View All Disease
Records by Block chain, View No. of Same
Disease in Chart, View Patient Searched Rank in Patient Name, Email Id, Mobile Number,
chart, View Patient File Rank in chart, View No. Patient Address, Date of Birth, Hospital Name,
Blood Group, Disease Name, Disease
Of Attackers on Patient. Members
Symptom, Age, Select Patient Picture.
Patient Name, Email Id, Mobile Number, Patient
Members
Address, Date of Birth, Hospital Name, Blood Group,
Disease Name, Disease Symptom, Age, Select Patient
,View Keyword Search Results
Picture.
Login
Register
Login (), Reset (),
Methods Methods Register (), Reset ()
Register ().
User Name, Password. User Name, Password, E-

Members Members mail, Mobile, Address, DOB,
Gender, Pin code, Image
Client
Register and Login ,View Profile, Search Patient, Search Patients by Age, View All SK Requests and
Methods Response, View All SK Permitted and Download,
Patient Name, Email Id, Mobile Number, Patient Address, Date of Birth, Hospital Name, Blood
Group, Disease Name, Disease Symptom, Age, Select Patient Picture.
Members
3. Sequence Diagram
A sequence diagram in Unified Modelling Language (UML) is a kind of interaction diagram

that shows how processes operate with one another and in what order. It is a construct of a
Message Sequence Chart. A Sequence diagram depicts the sequence of actions that occur in a
system. The invocation of methods in each object, and the order in which the invocation
occurs is captured in a Sequence diagram. This makes the Sequence diagram a very useful
tool to easily represent the dynamic behavior of a system.
Elements of sequence diagram
The sequence diagram is an element that is used primarily to showcase the interaction that
occurs between multiple objects. This interaction will be shown over certain period of time.
Because of this, the first symbol that is used is one that symbolizes the object.
Lifeline
A lifeline will generally be generated, and it is a dashed line that sits vertically, and the top
will be in the form of a rectangle. This rectangle is used to indicate both the instance and the
class. If the lifeline must be used to denote an object, it will be underlined.
Messages
To showcase an interaction, messages will be used. These messages will come in the form of
horizontal arrows, and the messages should be written on top of the arrows. If the arrow has a
full head, and it’s solid, it will be called a synchronous call. If the solid arrow has a stick
head, it will be an asynchronous call. Stick heads with dash arrows are used to represent
return messages.
Objects
Objects will also be given the ability to call methods upon themselves, and they can add net
activation boxes. Because of this, they can communicate with others to show multiple levels
of processing. Whenever an object is eradicated or erased from memory, the "X" will be
drawn at the lifeline's top, and the dash line will not be drawn beneath it. This will often
occur as a result of a message. If a message is sent from the outside of the diagram, it can be
used to define a message that comes from a circle that is filled in. Within a UML based
model, a Super step is a collection of steps which result from outside stimuli.
Steps to Create Sequence Diagram
 Set the stage for the interaction by identifying which

objects play a role in interaction.
 Set the lifetime for each object.
 Start with the message that initiates the interaction.
 Visualize the nesting of messages or the points in

time during actual computation.
Hospital Server Client
Register and Login, Register and Login,
View Profile,
View Profile, Search Patient,
Search Patients by Age,
Upload Patient View All SK Requests

Details, and Response,
View All Uploaded
Login, View All

Hospitals and
Authorize, View All
Clients and
Authorize, Add Block
chain Code, View All
Block chain Code,
View All Patient
Details, View All
Transactions, View
All SK Request and
Response Details,
View All SK Requests
and Permit, View All
Credential Attackers
Details, Trace and
View All Disease
Records by Block
chain, View No. of
Same Disease in
Chart, View Patient
Searched Rank in
chart,
4. Deployment Diagram
Deployment diagram represents the deployment view of a system. It is

relatedtothecomponentdiagram.Becausethecomponentsaredeployedusingthedeploymentdiagra
ms. A deployment diagram consists of nodes. Nodes are nothing but physical hardwares used
to deploy the application.
5. DATAFLOW DIAGRAM
A data flow diagram (DFD) maps out the flow of information for any process or system. It
uses defined symbols like rectangles, circles and arrows, plus short text labels, to show data
inputs, outputs, storage points and the routes between each destination. Data flowcharts can
range from simple, even hand-drawn process overviews, to in-depth, multi-level DFDs that
dig progressively deeper into how the data is handled. They can be used to analyze an
existing system or model a new one. Like all the best diagrams and charts, a DFD can often
visually “say” things that would be hard to explain in words, and they work for both technical
and nontechnical audiences, from developer to CEO. That’s why DFDs remain so popular
after all these years. While they work well for data flow software and systems, they are less
applicable nowadays to visualizing interactive, real-time or database-oriented software or
systems.
Using any convention’s DFD rules or guidelines, the symbols depict the four
components of data flow diagrams.
1. External entity: an outside system that sends or receives data, communicating with the
system being diagrammed. They are the sources and destinations of information entering or
leaving the system. They might be an outside organization or person, a computer system or a
business system. They are also known as terminators, sources and sinks or actors. They are
typically drawn on the edges of the diagram.
2. Process: any process that changes the data, producing an output. It might perform
computations, or sort data based on logic, or direct the data flow based on business rules. A
short label is used to describe the process, such as “Submit payment.”
3. Data store: files or repositories that hold information for later use, such as a database table
or a membership form. Each data store receives a simple label, such as “Orders.”
4. Data flow: the route that data takes between the external entities, processes and data stores.
It portrays the interface between the other components and is shown with arrows, typically
labeled with a short data name, like “Billing details.”
Login, View All Hospitals and
Authorize, View All Clients and
Authorize, Add Block chain Code,
View All Block chain Code, View All

Patient Details, View All
Transactions,View All SK Request and
Response Details,
Register, Add
Restaurants Search Documents,
Server System
View All SK Requests and Permit, View All Response

Credential Attackers Details, Trace and Register with the
View All Disease Records by Block chain system
Register and Login, View
Profile, Search Patient,
Request
View No. of Same Disease in Chart, View
Patient Searched Rank in chart, View Client Search Patients by Age, View All SK
Patient File Rank in chart, View No. Of
Requests and Response, View All SK
Attackers on Patient.
Permitted and Download,
.
Register and Login, View Profile,

Hospital
Upload Patient Details, View All Uploaded

Patient Details,
IMPLEMENTATION
CODING
Index.html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Home Page</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link href="css/style.css" rel="stylesheet" type="text/css" />
<link rel="stylesheet" type="text/css" href="css/coin-slider.css" />
<script type="text/javascript" src="js/cufon-yui.js"></script>
<script type="text/javascript" src="js/cufon-aller.js"></script>
<script type="text/javascript" src="js/jquery-1.4.2.min.js"></script>
<script type="text/javascript" src="js/script.js"></script>
<script type="text/javascript" src="js/coin-slider.min.js"></script>
<style type="text/css">

</style>
</head>
<body>
<div class="main">
<div class="header">
<div class="header_resize">
<div class="logo">
<h1><a href="index.html" class="style1">Blockchain Based Electronic Health Records

Management A Comprehensive Review and Future Research Direction </a></h1>
</div>
<div class="menu_nav">
<ul>
<li class="active"><a href="index.html"><span>Home Page</span></a></li>
<li><a href="Hospital_login.jsp"><span>Hospital</span></a></li>
<li><a href="user_login.jsp"><span>Client</span></a></li>
<li><a href="cs_login.jsp"><span>Server</span></a></li>
</ul>
</div>
<div class="clr"></div>
<div class="slider">
<div id="coin-slider"> <a href="#"><img src="images/slide1.jpg" width="960" height="320"

alt="" /> </a> <a href="#"><img src="images/slide2.jpg" width="960" height="320" alt="" /> </a>
<a href="#"><img src="images/slide3.jpg" width="960" height="320" alt="" /> </a> </div>
</div>
</div>
</div>
<div class="content">
<div class="content_resize">
<div class="mainbar">
<div class="article">
<h2>Blockchain Based Electronic Health Records Management A Comprehensive Review and

Future Research Direction </h2>
<p class="infopost style4">EHR, blockchain, P2P, DLT, encryption, interoperability,

distributed ledger technology, distributed computing, eHealth.</p>
<p class="infopost style4"><img src="images/img2.jpg" width="512" height="294" /></p>
</div>
</div>
<div class="sidebar">
<div class="gadget">
<h2 class="star"><span>Sidebar</span> Menu</h2>
<ul class="sb_menu">
<li><a href="index.html"><span>Home Page</span></a></li>
<li><a href="au_login.jsp"><span></span></a></li>
</ul>
</div>
<h2 class="star"><span>Concepts</span></h2>
<ul class="ex_menu"><li class="style3">EHR, blockchain, P2P, DLT, encryption,

interoperability, distributed ledger technology,<br />
distributed computing, eHealth.</li>
</ul>
</div>
</div>
</div>
</div>
<div class="fbg">
<div class="fbg_resize">
</div>
</div>
<div class="footer">
<div class="footer_resize">
<div style="clear:both;"></div>
</div>
</div>
</div>
<div align=center></div>
</body>
</html>
Ow_main.jsp

<head>
<title>Hospital Main</title>
<script language="javascript" type="text/javascript">
</script>

</style>
</head>
<body>
<div class="main">
<div class="logo">
<h1><a href="index.html" class="style1 style2">Blockchain Based Electronic Health Records

Management A Comprehensive Review and Future Research Direction <br />
</a></h1>
</div>
<ul>
<li class="active"><a href="Hospital_login.jsp"><span>Hospital</span></a></li>
</ul>
</div>

</div>
</div>
</div>
<h2 align="center"> Welcome to Hospital Main : <span class="style3"><

%=application.getAttribute("ow")%></span></h2>
<p align="center"><img src="images/Owner.jpg" width="433" height="240"

/></p>
</div>
</div>
<h2 class="star"><span>Hospital</span> Menu</h2>
<ul class="sb_menu style4">

<li><a href="ow_profile.jsp">View Profile</a></li>
<li><a href="ow_upload_patientt.jsp">Upload Patient Details </a></li>
<li><a href="ow_patient_det.jsp">View All Uploaded Patient Details </a></li>
<li><a href="Hospital_login.jsp">Log Out</a></li>
</ul>
</div>
</div>
</div>
</div>
<div class="fbg"></div>
</div>
</div>
</div>
</body>
</html>
ow_profile.jsp

<head>
<title>Hospital Profile</title>
</script>

</style>
</head>
<body>
<div class="main">
<div class="logo">

</a></h1>
</div>
<ul>
</ul>
</div>

</div>
</div>
</div>
<h2 align="center"> My Profile!!! </h2>
<p align="center"> </p>
<table width="547" border="1.5" align="center" cellpadding="0" cellspacing="0" >
<%@ include file="connect.jsp" %>
<%@ page import="org.bouncycastle.util.encoders.Base64"%>
<%
String user=(String )application.getAttribute("ow");
String s1,s2,s3,s4,s5,s6,s7;
int i=0;
try
String query="select * from Hospital where

name='"+user+"'";
Statement st=connection.createStatement();
ResultSet rs=st.executeQuery(query);
if ( rs.next() )
i=rs.getInt(1);
s2=rs.getString(2);
//s3=rs.getString(3);
s4=rs.getString(4);
s5=rs.getString(5);
s6=rs.getString(6);
s7=rs.getString(7);
%>
<tr>
<td width="230" rowspan="6" ><div class="style7" style="margin:10px 13px 10px 13px;"

><a class="#" id="img1" href="#" >
<input name="image" type="image" src="ow_Pic.jsp?id=<%=i%>" style="width:200px;

height:200px;" />
</a></div></td>
</tr>
<tr>
<td width="145" height="40" valign="middle" bgcolor="#FF0000" style="color:

#2c83b0;"><div align="left" class="style14 style15 style20 style8 style9 style5 style3"
style="margin-left:20px;"><strong>Hospital Name </strong></div></td>
<td width="164" valign="middle" height="40" style="color:#000000;"><div align="left"

class="style23 style9 style10 style6" style="margin-left:20px;">
<%out.println(s2);%>
</div></td>
</tr>
<tr>
<td width="145" height="40" valign="middle" bgcolor="#FF0000" style="color:

#2c83b0;"><div align="left" class="style14 style15 style20 style8 style9 style5 style3"
style="margin-left:20px;"><strong>Department</strong></div></td>
<td width="164" valign="middle" height="40"><div align="left" class="style23 style9

style10 style6" style="margin-left:20px;">
</div></td>
</tr>
<tr>
<td width="145" height="40" align="left" valign="middle" bgcolor="#FF0000"

style="color: #2c83b0;"><div align="left" class="style14 style15 style20 style8 style9 style5 style3"
style="margin-left:20px;"><strong>Specilisation</strong></div></td>
<td width="164" align="left" valign="middle" height="40"><div align="left" class="style23

style9 style10 style6" style="margin-left:20px;">
</div></td>
</tr>
<tr>
<td width="145" height="51" align="left" valign="middle" bgcolor="#FF0000"

style="color: #2c83b0;"><div align="left" class="style14 style15 style20 style8 style9 style5 style3"
style="margin-left:20px;"><strong>Status</strong></div ></td>
<td width="164" align="left" valign="middle" height="51" style="color: #2c83b0;"><div

align="left">
<div align="left" class="style23 style9 style10 style6" style="margin-left:20px;">
</div>
</div></td>
</tr>
<%
connection.close();
catch(Exception e)
out.println(e.getMessage());
%>
</table>
<p align="center"><a href="ow_main.jsp" class="style14">Back</a></p>
</div>
</div>
<h2 class="star"><span>Hospital</span> Menu</h2>
<li><a href="ow_main.jsp"><span>Hospital Main</span></a></li>
<li><a href="Hospital_login.jsp"><span>Log Out</span></a></li>
</ul>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>
ow_register.jsp

<head>
<title>Hospital Reister</title>
function valid()
var na3=document.s.userid.value;
if(na3=="")
alert("Please Enter Hospital Name");
document.s.userid.focus();
return false;
else
var na4=document.s.pass.value;
if(na4=="")
alert("Please Enter Password");
document.s.pass.focus();
return false;
var na9=document.s.dept.value;
if(na9=="--Select--")
alert("Please Select Your Department");
document.s.dept.focus();
return false;
var na99=document.s.spec.value;
{
alert("Please Select Your Specialist");
document.s.spec.focus();
return false;
var na6=document.s.email.value;
if(na6=="")
alert("Please Enter the Email");
document.s.email.focus();
return false;
if (na6.indexOf("@", 0) < 0)
alert("Please enter a valid e-mail address.");
document.s.T3.focus();
return false;
if (na6.indexOf(".", 0) < 0)
alert("Please enter a valid e-mail address.");

document.s.T3.focus();
return false;
var na7=document.s.mobile.value;
if(na7.length!=10)
alert("Please Enter Valid Mobile number or Enter 10 Digit number");
document.s.mobile.focus();
return false;
if(na7=="")
alert("Please Enter Mobile number");
document.s.mobile.focus();
return false;
var na5=document.s.address.value;
if(na5=="")
{
alert("Please Enter Your address");
document.s.address.focus();
return false;
var dob=document.s.dob.value;
if(dob=="")
alert("please Enter Your Date Of Birth");
document.s.dob.focus();
return false;
var na9=document.s.gender.value;
alert("Please Enter Your Gender");
document.s.gender.focus();
return false;
var na10=document.s.pincode.value;
if(na10=="")
{
alert("please Enter Your Pincode");
document.s.pincode.focus();
return false;
var na11=document.s.pic.value;
if(na11=="")
alert("Please Select Picture");
document.s.pic.focus();
return false;
</script>

</style>
</head>
<body>
<div class="main">
<div class="logo">

</a></h1>
</div>
<ul>
</ul>
</div>
</div>
</div>
</div>
<p align="center"><img src="images/Register.jpg" width="343" height="65" /></p>
<form name="s" action="ow_RegIns.jsp" method="post" enctype="multipart/form-data"

onSubmit="return valid()" ons target="_top">
<label for="name">
<span class="style3"><strong>User Name (required)<br />
</strong></span></label>
<p class="style3"><strong>
<input id="name" name="userid" class="text" />
</strong></p>
<span class="style3">
<label for="password">
Password (required)<br />
</label>
</span>
<input type="password" id="password" name="pass" class="text" />
</strong></p>
<span class="style3"><strong>
<label for="gender"> Department (required)<br />
</label>
</strong></span>
<select id="s1" name="dept" class="text" style="width:170px;">
<option>--Select--</option>
<option>Cardiology</option>
<option>Neurology</option>
<option>Nephrology</option>
</select>
</strong></p>
<label for="gender"> Specialist (required)<br />
</label>
</strong></span>
<select id="s1" name="spec" class="text" style="width:170px;">
<option>--Select--</option>
<option>Heart</option>
<option>Brain</option>
<option>Kidney</option>
</select>
</strong></p>
<label for="email">Email Address (required)<br />
</label>
</strong></span>
<input id="email" name="email" class="text" />
</strong></p>
<label for="mobile">Mobile Number (required)<br />
</label>
</strong></span>
<input id="mobile" name="mobile" class="text" />
</strong></p>
<label for="address">Your Address<br />
</label>
</strong></span>
<textarea name="address" cols="50" id="address"></textarea>
</strong></p>
<label for="dob">Date of Birth (required)<br />
</label>
</strong></span>
<input id="dob" name="dob" class="text" />
</strong></p>
<label for="gender">Select Gender (required)<br />
</label>
</strong></span>
<select id="s1" name="gender" class="text">
<option>-Select-</option>
<option>Male</option>
<option>Female</option>
</select>
</strong></p>
<label for="pincode">Enter Pincode (required)<br />
</label>
</strong></span>
<input id="pincode" name="pincode" class="text" />
</strong></p>
<label for="pic">Select Profile Picture (required)</label>
</strong></span>
<span class="style3">
<label for="pic"></label>
</span>
<strong>
<label for="pic"></label>
</strong>
<label for="pic"><br />
</label>
<p>
<input type="file" id="pic" name="pic" class="text" />
</p>
<p>
<input name="submit" type="submit" value="REGISTER" />
</p>
<p align="right"><a href="Hospital_login.jsp">Back</a></p>
</form>
<p> </p>
</div>
</div>
<h2 class="star"><span>Sidebar</span> Menu</h2>
</ul>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>
Connect.jsp
<%@ page import="java.sql.*"%>
<%@ page import="java.util.*" %>
<%
Connection connection = null;
try {
Class.forName("com.mysql.jdbc.Driver");
connection =
DriverManager.getConnection("jdbc:mysql://localhost:3306/bbeh","root","root");
String sql="";
catch(Exception e)
System.out.println(e);
%>
SCREENSHOTS
Fig 1. Home page
Fig 2. Hospital login page

Fig 3. Hospital main page
Fig 4. View profile

Fig 5. server login
Fig 6. Server main page

Fig 7. View all hospital
Fig 8. view all clients

Fig 9. View all blockchain code
Fig 10.View all patient details

Fig 11. View all transaction
REFERENCES
[1] S. Nakamoto, ‘‘Bitcoin: A peer-to-peer electronic cash system,’’ Decentralized Bus. Rev.,
2008, Art. no. 21260.
[2] A. A. Vazirani, O. O’Donoghue, D. Brindley, and E. Meinert, ‘‘Implementing
blockchains for efficient health care: Systematic review,’’ J. Med. Internet Res., vol. 21, no.
2, Feb. 2019, Art. no. e12439.
[3] M. Hölbl, M. Kompara, A. Kamišalić, and L. N. Zlatolas, ‘‘A systematic review of the
use of blockchain in healthcare,’’ Symmetry, vol. 10, no. 10, p. 470, Oct. 2018.
[4] C. C. Agbo, Q. H. Mahmoud, and J. M. Eklund, ‘‘Blockchain technology in healthcare: A
systematic review,’’ Healthcare, vol. 7, no. 2, p. 56, Apr. 2019.
[5] E. Chukwu and L. Garg, ‘‘A systematic review of blockchain in healthcare: Frameworks,
prototypes, and implementations,’’ IEEE Access, vol. 8, pp. 21196–21214, 2020.
[6] S. Khezr, A. Yassine, and R. Benlamri, ‘‘Blockchain technology in healthcare: A
comprehensive review and directions for future research,’’ Appl. Sci., vol. 9, no. 9, p. 1736,
2019.
[7] I. Ahmed, M. Ahmad, G. Jeon, and F. Piccialli, ‘‘A framework for pandemic prediction
using big data analytics,’’ Big Data Res., vol. 25, Jul. 2021, Art. no. 100190.
[8] R. Vaishya, M. Javaid, I. H. Khan, and A. Haleem, ‘‘Artificial intelligence (AI)
applications for COVID-19 pandemic,’’ Diabetes Metabolic Syndrome: Clin. Res. Rev., vol.
14, no. 4, pp. 337–339, Jul. 2020.
[9] L. Houston, Y. Probst, and A. Humphries, ‘‘Measuring data quality through a source data
verification audit in a clinical research setting,’’ Stud. Health Technol. Inform., vol. 214, pp.
13–107, Jan. 2015.
[10] M. Muthuppalaniappan and K. Stevenson, ‘‘Healthcare cyber-attacks and the COVID-19
pandemic: An urgent threat to global health,’’ Int. J. Qual. Health Care, vol. 33, no. 1, Feb.
2021.
[11] M. S. Rahman, I. Khalil, P. C. Mahawaga Arachchige, A. Bouras, and X. Yi, ‘‘A novel
architecture for tamper proof electronic health record management system using blockchain
wrapper,’’ in Proc. ACM Int. Symp. Blockchain Secure Crit. Infrastruct. (BSCI), 2019, pp.
97–105.
[12] H. Wu, Y. Shang, L. Wang, L. Shi, K. Jiang, and J. Dong, ‘‘A patient-centric
interoperable framework for health information exchange via blockchain,’’ in Proc. 2nd Int.
Conf. Blockchain Technol. Appl., Dec. 2019, pp. 76–80.

BEHR - Review (1) - For Merge

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BEHR - Review (1) - For Merge

Uploaded by

Copyright:

Available Formats

Blockchain-Based Electronic Health Records Management

1. Title : A systematic review of blockchain in healthcare: Frameworks, prototypes, and

5. Title : A framework for pandemic prediction using big data analytics

7. Title : Electronic medical record security sharing model based on blockchain

View Patient Searched Rank in

Register and Login, Register and Login,

View All SK Permitted and

Following are some fundamental concepts of the object-oriented world −

 Objects − Objects represent an entity and the basic building block.

 Class − Class is the blue print of an object.

 Abstraction − Abstraction represents the behavior of an real world entity.

 Encapsulation − Encapsulation is the mechanism of binding the data together and

 Inheritance − Inheritance is the mechanism of making new classes from existing

 Polymorphism − It defines the mechanism to exists in different forms.

OO Analysis and Design

OO can be defined as an investigation and to be more specific, it is the investigation of

The purpose of OO analysis and design can described as −

 Identifying the objects of a system.

 Identifying their relationships.

 Making a design, which can be converted to executables using OO languages.

OO Analysis → OO Design → OO implementation using OO languages

The above three points can be described in detail as −

Role of UML in OO Design

In this project ,basic UML diagrams have been explained

 Use Case Diagram

1. . Use case diagram

STEPS TO DRAW USE CASES

 Identifying Use cases

 Review your use case for completeness

View All Transactions, View All SK Request and

View All Credential Attackers Details, Trace and View

Register and Login, View Profile,

View Time Delay Results, View

Register and Login, View Profile

Search Patient, Search Patients by Age,

View All SK Requests and Response,

A class diagram consists of the following features:

Login, View All Hospitals and Authorize, View All

User Name, Password. User Name, Password, E-

A sequence diagram in Unified Modelling Language (UML) is a kind of interaction diagram

Steps to Create Sequence Diagram

 Set the stage for the interaction by identifying which

 Start with the message that initiates the interaction.

 Visualize the nesting of messages or the points in

Hospital Server Client

Register and Login, Register and Login,

View Profile, Search Patient,

Search Patients by Age,

Upload Patient View All SK Requests

View All Uploaded

Login, View All

Deployment diagram represents the deployment view of a system. It is

View All Block chain Code, View All

View All SK Requests and Permit, View All Response

Register and Login, View Profile,

Upload Patient Details, View All Uploaded

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<link href="css/style.css" rel="stylesheet" type="text/css" />

<link rel="stylesheet" type="text/css" href="css/coin-slider.css" />

<script type="text/javascript" src="js/cufon-yui.js"></script>

<script type="text/javascript" src="js/cufon-aller.js"></script>

<script type="text/javascript" src="js/jquery-1.4.2.min.js"></script>