INTERNSHIP II / DISSERTATION II REPORT

HEALTH-CARE SYSTEM
(SUKUNA)

Submitted in partial fulfilment of the requirements for the degree of

Master of Technology Computer Science &

Engineering

By

SOURABH NAIDU
22MCS0031

Month Year
Jan 2023-24
 DECLARATION

I, SOURABH NAIDU hereby declare that the thesis entitled “HEALTH-

CARE SYSTEM (SUKUNA)” submitted to Vellore Institute of Technology
(VIT), Vellore for the award of the degree of Master of Technology
Computer Science & Engineering (CSE) is a record of bonafide work
carried out by me under the supervision of NAME OF THE GUIDE, Prof.
Dr. KALAAVATHI B. Designation, Name of the School/Centre, Vellore
Institute of Technology, Vellore.

I further declare that the work reported in this project report has not
been submitted and will not be submitted, either in part or in full, for the
award of any other degree or diploma in this institute or any other
institute or university.

Place: Vellore Signature of the Candidate

Date: 01/05/2024
 CERTIFICATE

This is to certify that the thesis entitled “Health-Care System (Sukuna)”

submitted by Sourabh Naidu, School or Centre, Vellore Institute of Technology,
Vellore for the award of the degree of Master of Technology in Computer Science
and Engineering, is a record of bonafide work carried out by him/her under my
supervision during the period, 03/01/2024 to 07/05/2024 as per the VIT code of
academic and research ethics.

The contents of this report have not been submitted and will not be submitted either
in partor in full, for the award of any other degree or diploma in this institute or any
other Institute or University. The dissertation fulfills the requirements and
regulations of the Institute and in my opinion meets the necessary standards for
submission.

Place: Vellore Name and Signature of the Guide

Date: 01/05/2024 School of Computer Science and
Engineering VIT
(Prof. Dr Kalaavathi B.)

Internal Examiner External Examiner

Head of the Department

 Programme

ABSTRACT

As technology becomes more and more integrated into healthcare systems.

Privacy and security issues with patient data are becoming more and more
significant. Hospitals require a safe healthcare system that makes use of
blockchain smart contracts in order to solve these problems. The suggested
solution would use Ethereum as the foundation for blockchain technology
development. Patients, healthcare professionals (doctor), and healthcare providers
(clinics, hospitals) are all part of the system. The patient's condition is tracked
online, and the blockchain automatically stores the data that is gathered. A
processing system that selectively saves medical device information based on
patient health state is needed to address concerns about data size and transaction
efficiency. This technique minimizes transaction costs and shrinks the blockchain
by screening data before committing it to the blockchain.

Any mistake in the sensor data is immediately recorded in the blockchain, causing the hospital or
doctor to receive an emergency message so they may take the appropriate action. The suggested
smart contract was verified within the Ethereum testing environment, and the system was put
into practice in an experimental environment using actual devices, showcasing its usefulness on
a limited scale.

The purpose of healthcare systems is to address the health issues that people experience.
Considering that traditional health care approaches frequently result in overworked hospitals and
insufficient assistance for the homebound in particular, remote monitoring of vital signs in real
time is seen as a solution that lessens the need for frequent doctor visits.

Healthcare systems are known to raise privacy and security issues, with a particular emphasis on
how susceptible devices are to online attacks. The authors suggest using blockchain-based smart
contracts to guarantee patient data security, stop data leaks, and preserve data integrity. The
study highlights the shortcomings of previous studies in this field and offers a thorough
healthcare tele-system that takes operational, security, and privacy concerns into account.

Key words: decentralization, scalability, blockchain, and health system

 ACKNOWLEDGEMENTS

With immense pleasure and a deep sense of gratitude, I wish to express my

sincere thanks to my supervisor DR. KALAAVATHI B Professor, SCOPE ,

Vellore Institute of Technology (VIT), Vellore without his motivation and
continuous encouragement, this research would not have been successfully
completed.
I am grateful to the Chancellor of VIT, Dr. G. Viswanathan, the Vice
Presidents, and the Vice Chancellor for motivating me to carry out research in the
Vellore Institute of Technology.
It would be no exaggeration to say that the Dean of SCOPE, Prof Ramesh
Babu K, was always available to clarify any queries and clear the doubts I had
during the course of my project.
I would also like to acknowledge the role of the HoD, Dr Swathi J.N,
who was instrumental in keeping me updated with all necessary formalities and
posting all the required formats and document templates through the mail, which I
was glad to have had.
Finally, I would like to thank Vellore Institute of Technology for
providing me with infrastructural facilities, a flexible choice and for supporting
my research and execution related to the dissertation work.

Place: Vellore NAME OF SCHOLAR

Date: 01/05/2024 SOURABH NAIDU

 TABLE OF CONTENTS

ABSTRACT i
ACKNOWLEDGEMENTS iii
LIST OF FIGURES v
LIST OF TABLES vi
LIST OF SYMBOLS AND ABBREVIATIONS viii

1 INTRODUCTION 1
1.1 Overview 1
1.2 Objectives 3
1.3 Organization of the report 7

2 LITERATURE REVIEW 9
2.1 Subsection Name – 1 10
2.2 Subsection Name - 2 12
2.3 Summary 14

3 METHODOLOGY 15
3.1 Brief Introduction 15
3.2 Architecture of the proposed system 16
3.2.1 Limitations of Existing System 16
3.2.2 Proposed system 17
3.2.3 Advantages of Proposed System 19
3.3 Description of the used algorithm 21
3.4 Module Description 24
3.5 Dataset Description 26

4 ANALYSIS AND DESIGN 27

4.1 Brief Introduction 27
4.2 Requirement Analysis 28
4.2.1 Software Requirement 28
4.2.2 Hardware Requirement 29
4.3 Detailed Design 30
 4.3.1 System Design 31
4.3.2 Dataflow Diagram 32
4.3.3 Class Diagram 34
4.3.4 Use Case Diagram 36
4.3.5 Sequence Diagram 37

5 IMPLEMENTATION & RESULT ANALYSIS 38

5.1 Tools Used 38
5.2 Methodology 39
5.3 Graphs / Tables 42
5.4 Output Screens 44
5.5 Comparative Analysis with Existing works 46
6 CONCLUSION AND FUTURE ENHANCEMENTS 48
REFERENCES 50
LIST OF PUBLICATIONS / PATENTS 53
Appendices
Appendix A TABLE 54
Appendix B SAMPLE CODE AND ALGORITHM 55
 LIST OF FIGURES

5.1 Picture 18
5.2 Graph 19
 LIST OF TABLES

1.1 Table caption 7

LIST OF SYMBOLS AND ABBREVIATIONS

BC - BLOCK CHAIN

HCS HEALTH-CARE SYSTEM

 Chapter 1

INTRODUCTION

1.1 Overview

As technology becomes more and more integrated into healthcare systems. Privacy and security issues with
patient data are becoming more and more significant. Hospitals require a safe healthcare system that makes
use of blockchain smart contracts in order to solve these problems. The suggested solution would use
Ethereum as the foundation for blockchain technology development. Patients, healthcare professionals
(doctor), and healthcare providers (clinics, hospitals) are all part of the system. The patient's condition is
tracked online, and the blockchain automatically stores the data that is gathered. A processing system that
selectively saves medical device information based on patient health state is needed to address concerns about
data size and transaction efficiency. This technique minimizes transaction costs and shrinks the blockchain by
screening data before committing it to the blockchain.

Any mistake in the sensor data is immediately recorded in the blockchain, causing the hospital or doctor to
receive an emergency message so they may take the appropriate action. The suggested smart contract was
verified within the Ethereum testing environment, and the system was put into practice in an experimental
environment using actual devices, showcasing its usefulness on a limited scale.

The purpose of healthcare systems is to address the health issues that people experience. Considering that
traditional health care approaches frequently result in overworked hospitals and insufficient assistance for the
homebound in particular, remote monitoring of vital signs in real time is seen as a solution that lessens the
need for frequent doctor visits.

Healthcare systems are known to raise privacy and security issues, with a particular emphasis on how
susceptible devices are to online attacks. The authors suggest using blockchain-based smart contracts to
guarantee patient data security, stop data leaks, and preserve data integrity. The study highlights the
shortcomings of previous studies in this field and offers a thorough healthcare tele-system that takes
operational, security, and privacy concerns into account.
 Objectives
Blockchain is a distributed system that makes transactions safe, transparent, and unchangeable. By doing away
with a central authority and distributing data among network computers, a decentralized system can be more
resistant to hacking and the manipulation of credential verification.
Blockchain applications such voting identity verification and supply chain management are mostly known for
recording bitcoin transactions.
Important characteristics:
1.2.1 Decentralization: The lack of a centralized organization strengthens the defenses against fraud and
censorship.
1.2.2 Transparency: The system is extremely transparent because every transaction is made public.
1.2.3 Immutability: Adding data makes it unchangeable, which adds to the environment's high level of security.
when the technology is still in its infancy.It has enormous promise for a number of sectors. Because of its built-
in qualities, it's a powerful instrument for creating more transparent, safe, and effective systems.
How the healthcare system can use blockchain technology
Data Integrity and Security: The danger of unwanted access and manipulation can be decreased by using
blockchain technology to keep patient information in a safe and unchangeable way. By giving authorization to
healthcare professionals when required, patients may manage who has access to their health information,
improving security and privacy.
Interoperability: Blockchain makes it possible for various healthcare providers to see patient records
uniformly and unifiedly, enhancing interoperability and expediting information transmission.
Medication Traceability and Supply Chain Administration By guaranteeing authenticity and transparency,
blockchain technology may be used to track the whole pharmaceutical supply chain, lowering the possibility of
fake medications.
Clinical Trials: Blockchain can maintain the integrity of data in clinical trials, lowering the danger of data
tampering by documenting every stage on the blockchain.
Billing and Claims Processing: By offering an auditable and transparent record of transactions, blockchain
technology helps expedite the processing of bills and claims while lowering fraud and billing mistakes.
Identity Management: Managing patient identities across various healthcare providers and systems may be
made easier with the use of blockchain technology, which can provide a safe, decentralized way of patient
identification.
Research and Data Sharing: Patients may exchange health information for research reasons using blockchain
technology, allowing them to decide who can access the information. Data sharing incentives can be offered
using smart contracts.
Remote patient monitoring and telemedicine By securely logging patient-generated data in real-time on the
blockchain, blockchain can improve the security of data transfer in telemedicine and remote patient
monitoring.

Overall, blockchain technology has the potential to revolutionize the healthcare industry by improving security
transparency, and efficiency. As the technology continues to develop, we can expect to see even more
innovative uses for blockchain in this sector.

BLOCKCHAIN IN HEALTHCARE
Talking about the effects of technology on the healthcare industry, with an emphasis on EHR and EMR systems
in particular. You seem to be emphasizing the security, user experience, and general advancement of
healthcare that these systems offer. You do note, though, that there are still some problems with the current
systems, including data integrity, user data ownership, and security vulnerabilities.
You suggest that blockchain technology, which offers a safe and impenetrable platform for storing medical
records and other healthcare-related data, can provide an answer to these problems. With its immutable and
decentralized structure, blockchain technology may be able to help existing EHR systems overcome some of
their problems.
The historical transition from paper-based medical record systems to electronic health record (EHR) systems
is then covered, with a focus on the drawbacks and security vulnerabilities of paper-based systems. EHR
systems were developed to address these issues, with the goals of enhancing information availability,
preventing mistakes, and improving patient safety.
You point out that despite the advantages, EHR systems have encountered several challenges, such as those
with dependability, usability, and failure to produce the desired results. You mention a research done in
Finland that discovered issues with the usability and dependability of EHR systems, suggesting that difficulties
are still present in the adoption and application of these technologies.

Blockchain technology has been extensively studied, and many different businesses are utilizing its benefits.
Using the security, privacy, secrecy, and decentralization that blockchain technology offers, the healthcare
industry in particular is set to profit greatly from it. Electronic health record (EHR) systems have difficulties
with data security, integrity, and efficient administration in spite of these benefits.
This article explores how integrating blockchain technology into EHR systems may revolutionize them and
address the aforementioned problems. A framework that is intended to make the integration of blockchain
technology into electronic health records easier is described. This framework has two main goals: first, it will
leverage blockchain technology to EHRs; second, it will create fine-grained access controls for users inside the
framework.
Ensuring the safe keeping of electronic documents is the main objective. Additionally, the framework tackles
typical scalability problems with blockchain technology, which frequently result from using off-chain storage
for records. In doing so, this framework provides the EHR system with the benefits of a scalable, secure, and
integrated blockchain-based solution in addition to resolving scaling issues.

The medical sector is one of the many areas of human existence that is undergoing rapid technological change.
Systems for electronic medical records (EMR) and health records (EHR) are essential for delivering
advantages including enhanced security and patient experience. But problems like data integrity, user data
ownership, and medical record security still exist. Blockchain technology has shown to be a creative answer,
offering a safe and impenetrable platform for health data storage.
Health care historically depended on paper-based methods, which resulted in data duplication, ambiguity, and
inefficiency.
Paper-based and electronic records were combined in an effort to overcome these problems during the
transition to an EHR system. EHR systems have been widely adopted, however they have been criticized for
not living up to expectations and raising questions regarding usability and dependability. Nurses' experiences
with HER systems revealed problems including low dependability and poor use, according to a Finnish
research. In conclusion, blockchain technology is developing as a viable alternative to increase security and
tackle current medical record management concerns, even though technology has substantially improved
healthcare delivery.
 Smart Contracts

Description: Ethereum smart contracts are automatically running programs with built-in criteria.The
Ethereum Virtual Machine (EVM), which powers these, plays a key part in the architecture. Smart contracts
simplify blockchain interactions, automate procedures, and enforce contracts.
Implementation: Create smart contracts in Solidity or a language that is compatible with Ethereum.

Decentralized Applications (DApps): DApps are web apps that interface with Ethereum blockchain smart
contracts. DApps play a variety of roles in the architecture, allowing users to engage with the blockchain and
DApps to exchange data with smart contracts for different purposes. Implementation: Use web technologies
like HTML, CSS, and JavaScript to create his DApp. You may use ethers.js or web3.js to connect to Ethereum.

User Interface (UI): UI serves as the user's interface for interacting with his DApp. Its function in the
architecture is as follows: makes it simple for people to engage with his DApp and, by extension, the Ethereum
blockchain through an intuitive UI. Implementation: Use front-end frameworks like React, Angular, and Vue.js
to create responsive and understandable user interface components.

Web3 Library: The Web3 Library facilitates communication between DApps and plays a crucial role in the
design of the Ethereum blockchain. makes it easier for UI/DApps to communicate with Ethereum nodes so
they can read and write on the blockchain. Implementation: To manage Ethereum transactions and contract
interactions, use web3.js or ethers.js into your DApp.

Ethereum Nodes: Ethereum nodes are members of the network who uphold a replica of the whole blockchain
and carry out the function of transactions in the architecture. Specifically, nodes verify and disseminate
transactions to guarantee network consensus.

Implementation: To take part in the Ethereum network, set up an Ethereum node. Two well-known
Ethereum node implementations are Geth and Parity. Mechanism of Consensus: Description: Ethereum 2.0 will
switch to a Proof-of-Stake (PoS) consensus process from the present Proof-of-Work (PoW) method. Function
in the architecture: Guarantees that participating nodes agree on the blockchain's current state.
Execution: Is contingent upon the Ethereum network version. Set up your nodes appropriately.

Interplanetary File System (IPFS): Function in the architecture is to provide decentralized and secure
storage for files or data that do not need to be kept directly on the Ethereum blockchain. IPFS is a distributed
file system that can be used to store huge files and data off-chain. Implementation: For effective off-chain data
storage, include IPFS into your DApp. Security Procedures: Apply standard practices for security to guard
against common vulnerabilities. The architecture's responsibility is to guarantee the security and integrity of
user interactions, DApps, and smart contracts. Implementation: Conduct audits, utilize Truffle for testing, and
adhere to best practices for Ethereum development and security.
 Chapter 2

LITERATURE REVIEW

2.1 Review of Literature

Rexford N et al. :

● Approach: Proposed a cryptography approach utilizing the hash process.

● Objective: Confirm and approve the health information framework with base clinical
information.
● Technology: Involves a distributed framework approach, including blockchain.

R. M. Parizi et al. :

● Approach: Blockchain programming as a focus technique.

● Objective: Provides records of the "code is law," demonstrating arrangements among parties.
● Technology: Involves smart contracts and establishes trust among platform partners.

Matthew. N.O et al. :

● Description: Blockchain technology is described as a static record of online transactions.

● Functionality: It is a distributed sealed dataset, shared and maintained by multiple parties.
● Potential Impact: Expected to revolutionize various industries, including healthcare.

OmniPHR et al. :

● Framework: Proposed a patient-driven framework based on blockchain.

● Control: Gives the patient full control of their record while providing a comprehensive view
for providers.
● Data Storage: Information is encrypted and stored on blockchain data blocks.

Holbl M et al.:

● Proposal: Hybrid blockchain design to manage blocks of data.

● Focus: Addresses high-value data and involves a federated blockchain.
● Privacy: Ensures public and private data have proper access controls based on live medical
data policy.

Wang et al.:

● Development Stage: Proposes monitoring human and technical sector-related issues during
the development stage.
● Enterprise Resources: Organization with enterprise resources developed and migrated to
blockchain-based systems.
Azaria et al. :

● Proposal: Introduces MedRec for controlling a large quantity of medical information in EMR.
● Innovation: Uses a unique approach in the log system for access and audit of records.
● Reward System: Data miners have rewards for sharing information on the network.

Ramani V et al. :

● Mechanism: Proposes a mechanism for authorized entities to access patient clinical data in a
trusted manner.
● Security Measures: Utilizes a distributed system and elliptic curve cryptography (ECC) to
protect patient privacy.

Lee and Yang et al. :

● System: Proposes an analysis management system using blockchain and microscopic sensor
technology.
● Technology Use: Microscopic sensors and image processing to capture and monitor nail
images.
● Privacy: Ledger used to maintain patient record management privacy.

Xueping Liang et al. :

● Reported System: ProvChain implemented to incorporate provenance data into blockchain

transactions.
● Stages: Involves data proof collection, authentication, and storage.
● Security Features: Provides features like consumer secrecy, ambiguous data province, low
overhead integrity, and improved performance.

Zhang et al. :

● Reported System: PSN-based healthcare system allowing sharing of health information

obtained by sensors.
● Protocols: Two protocols for authentication between sensors and electronic devices
connected to WBAN.
● Transaction Handling: Miners take care of transaction validation, verification, and creation
of new block
2.2
 Chapter 3

METHODOLOGY

MERN STACK
 System design

The proposed framework comprises three main entities or modules, each serving a specific role in
the system.

1. User Layer:
o Definition: Users include patients, doctors, administrators, and nursing staff, each
assigned granular access levels based on their roles.
o Functionality: Users interact with the system through a DApp (Decentralized
Application) browser, which houses the graphical user interface (GUI) of the proposed
system.
2. Blockchain Layer:
o Components:
▪ Blockchain Assets: Transactions in the Ethereum blockchain involve updating
the state of records or information. These transactions are treated as assets,
representing pieces of information that users can send or store.
▪ Governance Rules: The system follows consensus rules, employing the Proof
of Work (PoW) consensus algorithm in Ethereum to maintain governance
through consent from trusted nodes.
▪ Network: Ethereum blockchain operates on a peer-to-peer network, ensuring
equal status and rights for all connected nodes, avoiding centralization.
3. Transactions:
o The system facilitates several transactions:
▪ Add Records: Creates patient medical records on the DApp, storing basic
information along with an IPFS hash containing additional medical
records.
▪ Update Records: Modifies basic patient information, excluding the non-
updateable IPFS hash for record security.
 ▪ View Records: Allows users (both doctors and patients) to view relevant
medical records, ensuring patients only access their own records.
▪ Delete Records: Permits authorized users, typically doctors, to delete patient
records stored on the blockchain.
▪ Grant Access: Certain transactions require specific user roles, such as only
doctors or nursing staff having the authority to add or update records

USER INTERACTION

Implementation and Usage Overview:

Ethereum has been used in the implementation phase; its predicted block time is between 10 and 19
seconds. The block time indicates how long it will take to produce a new block. Transaction
confirmation times for smart contracts typically take 38 seconds, depending on the gas price that is
chosen.
Ethereum has a gas limit as opposed to a block size constraint, unlike Bitcoin. The cost of gas and the
gas limit were covered in detail in earlier sections. Depending on the amount of data, the "Add
Patient Record" function (Algorithm 1) takes one to two minutes. Retrieval functions, including
"View Patient Record," take around fifty seconds to complete.

Transaction Size Analysis:

The average transaction size is determined to be around 0.2 KB, assuming an hourly average of
31,474 transactions and 269 blocks. It's important to remember that these are Ethereum blockchain
network-specific real-time information.

Usage Scenario:

Two main entities are involved in the proposed framework: the Administrator and the User, which
includes patients and clinicians. The administrator, who is usually a member of the administrative
staff at the hospital, defines granular access by assigning roles to users. Role assignment, user-
requested activities, Roles List validation, system processing, and Ethereum blockchain transactions
are all part of the use scenario. Users see transaction success messages in the DApp browser. This
procedure guarantees a verified and safe interaction inside the suggested framework.
 Chapter 4

ANALYSIS AND DESIGN

Average Latency

Throughput of user
DApp Workflow
 Chapter 5

IMPLEMENTATION & RESULT ANALYSIS

Ganache

Dashboard

28
UI of Doctor Page

Home Page

29
Meta mask

Meta mask

30
Medic Plus and Admin Page

Add Doctor Function Page

31
IPFS and IPFS hash in BlockChain

Add Patient Record

32
 View Patient Record

Update Patient Record

33
 Delete Patient Record

Patient Medical Record

34
 Medical Record

Patient
Architecture

35
 Doctor Architecture

Data Pay-load and transaction

36
 Transaction Size

Proposed framework vs past work

37
 Chapter 6

CONCLUSION AND FUTURE ENHANCEMENTS

The application of blockchain technology in healthcare, especially electronic health

records (EHR).

Notwithstanding technical developments in his EHR systems and improvements in

healthcare, unsolved issues prompted the exploration of blockchain as a potential new
remedy.To establish a system that is easy to use, the proposed framework intends to
integrate well-defined access rules with secure record storage.This framework makes use of
IPFS's off-chain storage capability to solve data storage issues.Information asymmetry in EHR
systems is eliminated via role-based access, which guarantees that only reliable parties have
access to medical records.

Interoperability:

● Challenge: Integrating blockchain with existing healthcare systems and achieving

interoperability with different platforms and standards.
● Impact: Incompatibility can hinder seamless data exchange and collaboration
between different healthcare providers.

Scalability:

● Challenge: Blockchain networks, especially public ones, may face scalability issues as
the number of transactions and participants grows.
● Impact: Slower transaction processing times and increased costs can limit the
system's ability to handle a large number of users and data transactions.

Data Privacy and Security:

● Challenge: Balancing the transparency of blockchain with the need to protect

sensitive patient health information.
● Impact: Ensuring that only authorized individuals have access to specific patient data
while maintaining the integrity of the overall system.

Regulatory Compliance:

● Challenge: Adhering to complex healthcare regulations and data protection laws.

● Impact: Failure to comply with regulations can lead to legal issues, fines, and loss of
trust among users and stakeholders.

Integration with Legacy Systems:

pg.
 ● Challenge: Connecting blockchain systems with existing legacy healthcare IT
infrastructure.
● Impact: Difficulty in seamless data flow and collaboration, as many healthcare
organizations still rely on traditional systems.

Smart Contract Security:

● Challenge: Ensuring the security and correctness of smart contracts that govern
automated processes within the blockchain.
● Impact: Vulnerabilities in smart contracts can lead to unauthorized access, data
breaches, and financial losses.

User Adoption and Education:

● Challenge: Educating healthcare professionals and users about blockchain

technology and encouraging adoption.
● Impact: Resistance to change and lack of understanding may hinder the
successful implementation of blockchain-based healthcare systems.

Costs and Resources:

● Challenge: The initial costs associated with implementing blockchain technology and
ongoing maintenance.
● Impact: Limited budgets and resource constraints may slow down the adoption of
blockchain solutions, especially for smaller healthcare organizations.

Immutable Data:

● Challenge: Ensuring that the immutability of blockchain data does not lead to
problems in the case of errors or outdated information.
● Impact: Incorrect or outdated data may persist in the blockchain, affecting the
accuracy of healthcare records.

Ethical and Legal Issues:

● Challenge: Addressing ethical concerns related to consent, ownership, and the

sharing of sensitive health data.
● Impact: Failure to address ethical considerations can lead to a lack of trust among
patients and healthcare professionals

pg.
Future Scope

The future scope of healthcare systems using blockchain technology is promising and
encompasses various areas that can revolutionize the industry. Some key aspects include:

1. Data Interoperability:
o Blockchain can enhance data interoperability by providing a secure and
standardized platform for sharing patient information across different
healthcare providers. This can lead to more comprehensive and efficient
patient care.
2. Patient Control and Ownership:
o Blockchain allows patients to have greater control and ownership of their
health data. Patients can securely share their medical history with healthcare
providers while maintaining control over who accesses their information.
3. Security and Privacy:
o Blockchain's decentralized and tamper-resistant nature enhances the security
and privacy of health records. This can help in preventing unauthorized access,
data breaches, and ensuring the integrity of medical information.
4. Supply Chain Management:
o Blockchain can be utilized for the transparent and traceable management of
pharmaceutical supply chains. This ensures the authenticity of drugs, prevents
counterfeit medicines, and improves overall drug safety.
5. Streamlined Processes and Reduced Costs:
o Implementing blockchain can streamline administrative processes, reduce
paperwork, and minimize the need for intermediaries. This efficiency can lead
to cost savings for healthcare providers and, in turn, potentially reduce the
overall cost of healthcare services.
6. Clinical Trials and Research:
o Blockchain can facilitate transparent and secure sharing of clinical trial data
among researchers, ensuring data integrity and reducing fraud. This could
accelerate the research and development of new medical treatments.
7. Smart Contracts for Healthcare Agreements:
o Smart contracts can automate and enforce healthcare agreements between
different parties. This includes insurance claims, billing processes, and
adherence to treatment plans, reducing administrative overhead.
8. Telemedicine and Remote Patient Monitoring:
o Blockchain can play a role in securing and validating data from telemedicine
visits and remote patient monitoring devices. This ensures the integrity of data
transmitted from these sources, supporting accurate diagnosis and treatment
decisions.
9. Global Healthcare Networks:
o Blockchain can enable the creation of global healthcare networks where
patient data can be securely shared across borders. This can be especially
beneficial in emergency situations or when patients seek medical attention
while traveling.
10.Integration with Emerging Technologies:
o The combination of blockchain with other emerging technologies like artificial
intelligence (AI) and the Internet of Things (IoT) could lead to more advanced
and interconnected healthcare systems.

pg.
 Appendix A

SAMPLE CODE
ALGORITHM

The algorithm outlines the functionality of a smart contract designed for managing patient
records. It consists of five functions responsible for role definition, addition, viewing,
updating, and deletion of records.

◆ Define Roles:function DefineRoles(NewRole, NewAccount)

// Add a new role and account to the roles mapping

end function

◆ Add Data:function AddPatientRecord(contains variables to add data)

if (msg.sender == doctor) then

// Add data to a particular patient's record

else Abort session

end if

end function

◆ Retrieve Data:function

ViewPatientRecord(patientId) if (msg.sender == doctor

pg.
|| patient) then

if (patientId) == true then

pg.
// Retrieve data from the specified patient (id)

return (patient record) to the account that requested the retrieve operation

else Abort session

end if

end if

end function

◆ Update Data:function UpdatePatientRecord(contains variables to update data)

if (msg.sender == doctor) then

if (id == patientId && name == patientName) then

// Update data for a particular patient's record

return success

else return fail

end if

else Abort session

end if

end function

pg.
 Index.js
<!doctype html>

<html lang="en">

<head>

<meta charset="utf-8">

<title>Ehr2.0</title>

<base href="/">

<meta name="viewport" content="width=device-width, initial-scale=1">

<link rel="icon" type="image/x-icon" href="favicon.ico">

<link rel="preconnect" href="https://fonts.googleapis.com">

<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>

<!-- font awesome icons -->

<link rel="stylesheet" href="https://pro.fontawesome.com/releases/v5.10.0/css/all.css"

integrity="sha384-

AYmEC3Yw5cVb3ZcuHtOA93w35dYTsvhLPVnYs9eStHfGJvOvKxVfELGroGkvsg+p"

crossorigin="anonymous" />

<!-- Fonts: Roboto,Popins -->

<link

href="https://fonts.googleapis.com/css2?family=Poppins:wght@200;300;400;500;600;800&

family=Roboto:wght@100;300;400;500;700&display=swap"

rel="stylesheet">

pg.
<!-- JavaScript Bundle with Popper -->

<script

src="https://cdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.bundle.min.js"

integrity="sha384-

ka7Sk0Gln4gmtz2MlQnikT1wXgYsOg+OMhuP+IlRH9sENBO0LRn5q+8nbTov4+1p"

crossorigin="anonymous">

</script>

<style>

*{

margin: 0px;

padding: 0px;

</style>

</head>

<body>

<app-root></app-root>

</body>

</html>

Doctor.js

import { NgModule } from '@angular/core';

pg.
import { CommonModule } from '@angular/common';

import { DoctorRoutingModule } from './doctor-routing.module';

import { DoctorDashboardComponent } from './doctor-dashboard/doctor-

dashboard.component';

import { SidebarComponent } from './doctor-dashboard/sidebar/sidebar.component';

import { HeaderComponent } from './doctor-dashboard/header/header.component';

import { DashboardHomeComponent } from './dashboard-home/dashboard-

home.component';

import { UtilsModule } from 'src/utils/utils.module';

import { ConsultationComponent } from './consultation/consultation.component';

import { FormsModule } from '@angular/forms';

import { PatientRecordComponent } from './consultation/patient-record/patient-

record.component';

import { ViewRecordComponent } from './view-record/view-record.component';

import { RecordComponent } from './view-record/record/record.component';

@NgModule({

declarations: [

DoctorDashboardComponent,

SidebarComponent,

HeaderComponent,

DashboardHomeComponent,

ConsultationComponent,

PatientRecordComponent,

ViewRecordComponent,

RecordComponent,

],

pg.
imports: [CommonModule,FormsModule, DoctorRoutingModule, UtilsModule],

})

export class DoctorModule {}

Patient.js
import { NgModule } from '@angular/core';

import { CommonModule } from '@angular/common';

import { PatientRoutingModule } from './patient-routing.module';

import { PatientDashboardComponent } from './patient-dashboard/patient-

dashboard.component';

import { DashboardHomeComponent } from './dashboard-home/dashboard-

home.component';

import { UtilsModule } from 'src/utils/utils.module';

import { HeaderComponent } from './patient-dashboard/header/header.component';

import { SidebarComponent } from './patient-dashboard/sidebar/sidebar.component';

import { AppointmentsComponent } from './appointments/appointments.component';

import { ViewRecordsComponent } from './view-records/view-records.component';

import { RecordComponent } from './view-records/record/record.component';

@NgModule({

declarations: [

PatientDashboardComponent,

DashboardHomeComponent,

HeaderComponent,

pg.
SidebarComponent,

AppointmentsComponent,

ViewRecordsComponent,RecordComponent

],

imports: [

CommonModule,

PatientRoutingModule,UtilsModule

})

export class PatientModule { }

pg.