\documentclass[11pt,twoside]{article}\makeatletter \IfFileExists{xcolor.sty}% {\RequirePackage{xcolor}}% {\RequirePackage{color}} \usepackage{colortbl} \usepackage{wrapfig} \usepackage{ifxetex} \ifxetex \usepackage{fontspec} \usepackage{xunicode} \catcode`⃥=\active \def⃥{\textbackslash} \catcode`❴=\active \def❴{\{} \catcode`❵=\active \def❵{\}} \def\textJapanese{\fontspec{Noto Sans CJK JP}} \def\textChinese{\fontspec{Noto Sans CJK SC}} \def\textKorean{\fontspec{Noto Sans CJK KR}} \setmonofont{DejaVu Sans Mono} \else \IfFileExists{utf8x.def}% {\usepackage[utf8x]{inputenc} \PrerenderUnicode{–} }% {\usepackage[utf8]{inputenc}} \usepackage[english]{babel} \usepackage[T1]{fontenc} \usepackage{float} \usepackage[]{ucs} \uc@dclc{8421}{default}{\textbackslash } \uc@dclc{10100}{default}{\{} \uc@dclc{10101}{default}{\}} \uc@dclc{8491}{default}{\AA{}} \uc@dclc{8239}{default}{\,} \uc@dclc{20154}{default}{ } \uc@dclc{10148}{default}{>} \def\textschwa{\rotatebox{-90}{e}} \def\textJapanese{} \def\textChinese{} \IfFileExists{tipa.sty}{\usepackage{tipa}}{} \fi \def\exampleFont{\ttfamily\small} \DeclareTextSymbol{\textpi}{OML}{25} \usepackage{relsize} \RequirePackage{array} \def\@testpach{\@chclass \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else \ifnum \@lastchclass=7 5 \else \ifnum \@lastchclass=8 \tw@ \else \ifnum \@lastchclass=9 \thr@@ \else \z@ \ifnum \@lastchclass = 10 \else \edef\@nextchar{\expandafter\string\@nextchar}% \@chnum \if \@nextchar c\z@ \else \if \@nextchar l\@ne \else \if \@nextchar r\tw@ \else \z@ \@chclass \if\@nextchar |\@ne \else \if \@nextchar !6 \else \if \@nextchar @7 \else \if \@nextchar (8 \else \if \@nextchar )9 \else 10 \@chnum \if \@nextchar m\thr@@\else \if \@nextchar p4 \else \if \@nextchar b5 \else \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi \fi \fi \fi \fi \fi \fi \fi \fi \fi \fi \fi \fi} \gdef\arraybackslash{\let\\=\@arraycr} \def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}} \def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}} \def\abbr{} \def\corr{} \def\expan{} \def\gap{} \def\orig{} \def\reg{} \def\ref{} \def\sic{} \def\persName{}\def\name{} \def\placeName{} \def\orgName{} \def\textcal#1{{\fontspec{Lucida Calligraphy}#1}} \def\textgothic#1{{\fontspec{Lucida Blackletter}#1}} \def\textlarge#1{{\large #1}} \def\textoverbar#1{\ensuremath{\overline{#1}}} \def\textquoted#1{‘#1’} \def\textsmall#1{{\small #1}} \def\textsubscript#1{\@textsubscript{\selectfont#1}} \def\textxi{\ensuremath{\xi}} \def\titlem{\itshape} \newenvironment{biblfree}{}{\ifvmode\par\fi } \newenvironment{bibl}{}{} \newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par } \newenvironment{citbibl}{}{\ifvmode\par\fi } \newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi } \newenvironment{docDate}{}{\ifvmode\par\fi } \newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi } \newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par } \newenvironment{msHead}{\vskip 6pt}{\par} \newenvironment{msItem}{\vskip 6pt}{\par} \newenvironment{rubric}{}{} \newenvironment{titlePart}{}{\par } \newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}} \newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}} \newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}} \newcolumntype{P}[1]{){\arraybackslash}p{#1}} \newcolumntype{B}[1]{){\arraybackslash}b{#1}} \newcolumntype{M}[1]{){\arraybackslash}m{#1}} \definecolor{label}{gray}{0.75} \def\unusedattribute#1{\sout{\textcolor{label}{#1}}} \DeclareRobustCommand*{\xref}{\hyper@normalise\xref@} \def\xref@#1#2{\hyper@linkurl{#2}{#1}} \begingroup \catcode`\_=\active \gdef_#1{\ensuremath{\sb{\mathrm{#1}}}} \endgroup \mathcode`\_=\string"8000 \catcode`\_=12\relax \usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry} \usepackage{framed} \definecolor{shadecolor}{gray}{0.95} \usepackage{longtable} \usepackage[normalem]{ulem} \usepackage{fancyvrb} \usepackage{fancyhdr} \usepackage{graphicx} \usepackage{marginnote} \renewcommand{\@cite}[1]{#1} \renewcommand*{\marginfont}{\itshape\footnotesize} \def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif} \pagestyle{fancy} \usepackage[pdftitle={A Blockchain Technology to Secure Electronic Health Records in Healthcare System}, pdfauthor={}]{hyperref} \hyperbaseurl{} \paperwidth210mm \paperheight297mm \def\@pnumwidth{1.55em} \def\@tocrmarg {2.55em} \def\@dotsep{4.5} \setcounter{tocdepth}{3} \clubpenalty=8000 \emergencystretch 3em \hbadness=4000 \hyphenpenalty=400 \pretolerance=750 \tolerance=2000 \vbadness=4000 \widowpenalty=10000 \renewcommand\section{\@startsection {section}{1}{\z@}% {-1.75ex \@plus -0.5ex \@minus -.2ex}% {0.5ex \@plus .2ex}% {\reset@font\Large\bfseries}} \renewcommand\subsection{\@startsection{subsection}{2}{\z@}% {-1.75ex\@plus -0.5ex \@minus- .2ex}% {0.5ex \@plus .2ex}% {\reset@font\Large}} \renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}% {-1.5ex\@plus -0.35ex \@minus -.2ex}% {0.5ex \@plus .2ex}% {\reset@font\large}} \renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}% {-1ex \@plus-0.35ex \@minus -0.2ex}% {0.5ex \@plus .2ex}% {\reset@font\normalsize}} \renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}% {1.5ex \@plus1ex \@minus .2ex}% {-1em}% {\reset@font\normalsize\bfseries}} \def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt} \@tempdima 1.5em \begingroup \parindent \z@ \rightskip \@pnumwidth \parfillskip -\@pnumwidth \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par \endgroup} \def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}} \def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}} \def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}} \def\l@subparagraph{\@dottedtocline{5}{10em}{5em}} \@ifundefined{c@section}{\newcounter{section}}{} \@ifundefined{c@chapter}{\newcounter{chapter}}{} \newif\if@mainmatter \@mainmattertrue \def\chaptername{Chapter} \def\frontmatter{% \pagenumbering{roman} \def\thechapter{\@roman\c@chapter} \def\theHchapter{\roman{chapter}} \def\thesection{\@roman\c@section} \def\theHsection{\roman{section}} \def\@chapapp{}% } \def\mainmatter{% \cleardoublepage \def\thechapter{\@arabic\c@chapter} \setcounter{chapter}{0} \setcounter{section}{0} \pagenumbering{arabic} \setcounter{secnumdepth}{6} \def\@chapapp{\chaptername}% \def\theHchapter{\arabic{chapter}} \def\thesection{\@arabic\c@section} \def\theHsection{\arabic{section}} } \def\backmatter{% \cleardoublepage \setcounter{chapter}{0} \setcounter{section}{0} \setcounter{secnumdepth}{2} \def\@chapapp{\appendixname}% \def\thechapter{\@Alph\c@chapter} \def\theHchapter{\Alph{chapter}} \appendix } \newenvironment{bibitemlist}[1]{% \list{\@biblabel{\@arabic\c@enumiv}}% {\settowidth\labelwidth{\@biblabel{#1}}% \leftmargin\labelwidth \advance\leftmargin\labelsep \@openbib@code \usecounter{enumiv}% \let\p@enumiv\@empty \renewcommand\theenumiv{\@arabic\c@enumiv}% }% \sloppy \clubpenalty4000 \@clubpenalty \clubpenalty \widowpenalty4000% \sfcode`\.\@m}% {\def\@noitemerr {\@latex@warning{Empty `bibitemlist' environment}}% \endlist} \def\tableofcontents{\section*{\contentsname}\@starttoc{toc}} \parskip0pt \parindent1em \def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}} \newenvironment{reflist}{% \begin{raggedright}\begin{list}{} {% \setlength{\topsep}{0pt}% \setlength{\rightmargin}{0.25in}% \setlength{\itemsep}{0pt}% \setlength{\itemindent}{0pt}% \setlength{\parskip}{0pt}% \setlength{\parsep}{2pt}% \def\makelabel##1{\itshape ##1}}% } {\end{list}\end{raggedright}} \newenvironment{sansreflist}{% \begin{raggedright}\begin{list}{} {% \setlength{\topsep}{0pt}% \setlength{\rightmargin}{0.25in}% \setlength{\itemindent}{0pt}% \setlength{\parskip}{0pt}% \setlength{\itemsep}{0pt}% \setlength{\parsep}{2pt}% \def\makelabel##1{\upshape ##1}}% } {\end{list}\end{raggedright}} \newenvironment{specHead}[2]% {\vspace{20pt}\hrule\vspace{10pt}% \phantomsection\label{#1}\markright{#2}% \pdfbookmark[2]{#2}{#1}% \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}% }{} \def\TheFullDate{1970-01-01 (revised: 01 January 1970)} \def\TheID{\makeatother } \def\TheDate{1970-01-01} \title{A Blockchain Technology to Secure Electronic Health Records in Healthcare System} \author{}\makeatletter \makeatletter \newcommand*{\cleartoleftpage}{% \clearpage \if@twoside \ifodd\c@page \hbox{}\newpage \if@twocolumn \hbox{}\newpage \fi \fi \fi } \makeatother \makeatletter \thispagestyle{empty} \markright{\@title}\markboth{\@title}{\@author} \renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@ \belowdisplayskip \abovedisplayskip \abovedisplayshortskip \z@ plus2\p@ \belowdisplayshortskip 4\p@ plus2\p@ minus2\p@ \def\@listi{\leftmargin\leftmargini \topsep 2\p@ plus1\p@ minus1\p@ \parsep 2\p@ plus\p@ minus\p@ \itemsep 1pt} } \makeatother \fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm} \fancyhf{} \setlength{\headheight}{14pt} \fancyhead[LE]{\bfseries\leftmark} \fancyhead[RO]{\bfseries\rightmark} \fancyfoot[RO]{} \fancyfoot[CO]{\thepage} \fancyfoot[LO]{\TheID} \fancyfoot[LE]{} \fancyfoot[CE]{\thepage} \fancyfoot[RE]{\TheID} \hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true} \fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}} \date{} \usepackage{authblk} \providecommand{\keywords}[1] { \footnotesize \textbf{\textit{Index terms---}} #1 } \usepackage{graphicx,xcolor} \definecolor{GJBlue}{HTML}{273B81} \definecolor{GJLightBlue}{HTML}{0A9DD9} \definecolor{GJMediumGrey}{HTML}{6D6E70} \definecolor{GJLightGrey}{HTML}{929497} \renewenvironment{abstract}{% \setlength{\parindent}{0pt}\raggedright \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}} \vskip16pt \textcolor{GJBlue}{\large\bfseries\abstractname\space} }{% \vskip8pt \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}} \vskip16pt } \usepackage[absolute,overlay]{textpos} \makeatother \usepackage{lineno} \linenumbers \begin{document} \affil[1]{ } \renewcommand\Authands{ and } \date{\small \em Received: 1 January 1970 Accepted: 1 January 1970 Published: 1 January 1970} \maketitle \begin{abstract} \end{abstract} \keywords{} \begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) \textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark} \end{textblock*} \begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) \textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}} \end{textblock*} \begin{textblock*}{10cm}(1.05cm,3cm) {{\textit{CrossRef DOI of original article:}} \underline{}} \end{textblock*}\let\tabcellsep& \section[{I. INTRODUCTION}]{I. INTRODUCTION}\par The SARS-CoV-2 virus, responsible for the greatest epidemic in millennia, has posed a serious threat to healthcare systems throughout the world. In addition to the immediate problems caused by the virus, the pandemic has revealed flaws in even the most modern healthcare systems, such as the inability to keep track of individuals with pre-existing diseases. Although industrialized nations like the United States were better equipped than others in responding to the epidemic, nearly one million Americans lost their lives as a result of the virus. Pre-pandemic research revealed flaws in the world's top healthcare systems, which impeded the most effective response to SARS-CoV-2. While wealthy countries' healthcare systems have their flaws, those in underdeveloped or underprivileged areas, such as India, are far more at risk. Long-term needs for hospital facilities, support personnel, and manpower are created by this sort of viral pandemic, all of which are often in limited supply in developing nations \hyperref[b0]{[1]}. For us to meet this challenge, we'll need to manage our resources efficiently.\par The potential effect of SARS-CoV-2 on the Indian Subcontinent, and India in particular, has been recognized ever since the breakout of the virus \hyperref[b1]{[2]}. Big data is the capability to manage a huge volume of disparate data, at the right speed, and within the right time frame to allow real-time analysis and reaction. Big data is an evolving term that describes any amount of structured, semi-structured and unstructured data that has the potential to be mined for information \hyperref[b2]{[3]}. \section[{II. LITERATURE SURVEY}]{II. LITERATURE SURVEY}\par With a population of close to 1.4 billion, India is one of the most populous countries on Earth. Before the epidemic, India's healthcare system already had significant challenges that were wreaking havoc on the country. Major public health issues include HIV/AIDS, malaria, and TB. As the income gap widens between the affluent and poor, another key worry is the availability and cost of decent healthcare. This problem has been exacerbated by statewide lockdowns. Recent studies have shown that the immediate effects of the lockdown would be a decrease in healthcare availability and an adverse effect on the population's physical and mental health and social well-being.\par The widespread use of handwritten prescriptions especially in rural areas without computer systems and the almost complete lack of integration between healthcare and insurance systems are just a few of the widespread problems that have arisen as a result of the fragmented nature of the healthcare industry's information, communication, and tracking infrastructure \hyperref[b3]{[4]}.\par Poor healthcare professional accountability is exacerbated by inadequate facilities, further straining doctor-patient ties. Paper records are more prone to human errors, such as illegibility or the loss of the physical object, which may lead to delays in treatment and perhaps preventable deaths.\par Prescriptions and insurance coverage data are just two examples of the kinds of critical information that healthcare and insurance providers may share with pharmacies to expedite the delivery of pharmaceuticals to patients. It is difficult to achieve large-scale coordinated performance using paper-based information, but this is made possible by integrated healthcare system synchronization, which allows for patient-oriented monitoring capabilities and refill requests.\par Any healthcare system that lacks the modern infrastructure essential to facilitating effective communication between healthcare practitioners, insurance providers, and patients would benefit greatly from implementing an Electronic Health Record (EHR) system. The influence of EHR will grow as the worldwide effort to disseminate and administer the Coronavirus vaccination continues \hyperref[b4]{[5]}.\par Electronic health record systems will be crucial in managing the massive amounts of information sharing and monitoring that will be necessary to accomplish this massive task. \hyperref[b5]{[6]}. \section[{Healthcare Records Security Breaches}]{Healthcare Records Security Breaches}\par Between 2009 and 2020, the HHS Office for Civil Rights received 3,705 allegations of healthcare data breaches involving 500 or more records. 268,189,693 healthcare records have been lost, stolen, leaked, or unlawfully released. 81.72 percent of the US population. In 2018, one breach involving 500 or more records was recorded each day. The rate doubled by 2020. In 2020, 1.76 breaches occurred daily. Figure \hyperref[fig_0]{1} shows 500+ Healthcare Data breaches from 2009 to 2020. As our digital infrastructure develops, privacy concerns rise. Due to the sensitivity of healthcare information, a system breach might endanger a patient's identity and the providers' reputation. Statistically, scammers value patient data. \section[{Electronic Health Record (HER) Benefits}]{Electronic Health Record (HER) Benefits}\par Electronic Health Record (EHR) is a computerized compilation of medical information and other data that can be readily shared. EHR has numerous promises, including lowering morbidity and mortality, enhancing continuity of care, boosting efficiency, and minimizing adverse medication reactions. Electronic health records (EHR) provide real-time data that can be accessed and shared securely \hyperref[b6]{[7]}.\par Transmitting information swiftly helps healthcare personnel to effectively support patients based on their individual medical requirements while dealing with the unpredictable Coronavirus, which disproportionately affects persons with underlying health concerns. EHR enabled patients and providers with major advances \hyperref[b7]{[8]}. \section[{Figure 2: Typical Features of an Ideal EHR System}]{Figure 2: Typical Features of an Ideal EHR System}\par EHRs have been used in industrialized countries for over 50 years. Since the early 2000s, more U.S. doctors have joined HER incentive schemes. The dramatic increase of EHR utilization during this era is not surprising given EHR competitive benefits and the government's drive to strengthen EHR usage in healthcare IT infrastructure. The loss of life during the Coronavirus pandemic would have been substantially greater without EHR technologies to support healthcare services \hyperref[b8]{[9]}. Even in industrialized countries, the need to enhance healthcare is evident. Before the epidemic, EHR implementation faced difficult hurdles.\par People may complicate EHR systems; skepticism and disillusionment with technology are common, and EHR systems are no exception. Older medical workers and patients may resist change, particularly new technology. Minor EHR system glitches might demotivate hesitant participants. When we consider challenges new users may encounter while completing crucial jobs, including external communications, the situation becomes frustrating. Developed nations have several EHR service providers for offices, hospitals, clinics, and pharmacies. Without a proper referral, healthcare providers may overlook vital patient medical history information. Introducing a new workflow may be stressful for all workers, regardless of tech familiarity. HER systems must be adapted to user needs \hyperref[b9]{[10]}. It's impractical to assume ideal efficiency in the early phases of EHR deployment, although training may boost user competency. \section[{Blockchain Technology: From Centralized to Decentralized System}]{Blockchain Technology: From Centralized to Decentralized System}\par Blockchain technology generates a transparent, immutable, append-only record of network transactions. Digitally signed and broadcast transactions are organized and timestamp into blocks. A Block contains hashed and encoded valid transactions in a Merkle tree. The preceding block's hash is included. The Blockchain's Genesis Block may be found using the previous hash. The blockchain seeks maximal length. Changing one block's hash makes the next block invalid and reduces the blockchain's size. Due to the blockchain's purpose of maintaining the longest chain possible, it is immutable \hyperref[b10]{[11]}.\par Each blockchain member has Public and Private keys. Public key is users shared identification. Only the user knows the private key. Digital signatures deterministically verify a message's origin and content. The 15 user signs the message using his private key, and others may verify it with his public key. Blockchain adds a new block using the consensus process. Consensus protocols distribute requests across nodes so each runs the identical sequence on its service instance. Popular consensus protocols include PoW and PoS. Digitalized technology has widely changed today's world. Depending upon this technology, starting from the day-to-day workings to the financial transactions, all can be controlled through the fingertip. By following the same fashion, the transition of the stock market is directly switching to the online platform and hence, the rate of the randomized investment rate in the stock is getting higher \hyperref[b11]{[12]} . \section[{Permissionless or Public Blockchain}]{Permissionless or Public Blockchain}\par Anyone may submit and confirm transactions on a permissionless blockchain. Transactions may be submitted by anybody who can pay fees. Anyone may be a validator by verifying transactions. This must be available to anybody who practices reasonably. Everyone who submits properly signed transactions to the network should expect it to execute them without fear of a group or firms banning them \hyperref[b12]{[13]}. Blockchain technology is currently generating a lot of buzz among banks, businesses, and government agencies. Nearly every day, new initiatives and various collaboration agreements on Blockchain applications are announced in the economic press. This includes projects run by governments and central banks as well as banks and private enterprises \hyperref[b13]{[14]}. \section[{Permissioned or private Blockchain}]{Permissioned or private Blockchain}\par Permissioned or private Blockchains don't allow open involvement in submitting or verifying transactions, thus participants can't trust the network to withstand censorship. This means not all participants have a realistic assurance that their transactions won't be discriminated against.\par Permissioned blockchain uses a membership structure to admit users. In permissioned Blockchains \hyperref[b14]{[15]}, nodes verify transactions using the originator's credentials. Permissioned blockchain technology's architectural design assures privacy and security. The Sybil Attack, 51\% attack, and blockchain endpoint vulnerability affect public or permissionless Blockchains. We exclusively explore permissioned blockchain because we believe it can handle sensitive healthcare data \hyperref[b15]{[16]}. \section[{Electronic Health Record (EHR) Is a Social Need}]{Electronic Health Record (EHR) Is a Social Need}\par An electronic health record (EHR) is a collection of electronically controlled health information that many users may access. A patient's record traditionally documented their medical care. Smart care services urge doctors to consider the full patient, including wellness, sickness, and rehabilitation \hyperref[b16]{[17]}.\par The main important risks and critical issues in a conventional healthcare system include a single point of failure, data modification, high chances of different malicious cyber attacks, centralized authority, high data management, keeping storage as well as cost, and databases that are not transparent. To address these issues, researchers have proposed numerous blockchain-based solutions. \hyperref[b17]{[18]} The record must include health and illness information from multiple doctors in different locations. Data should be kept so that hospitals, pharmacies, insurance companies, and academics may get different views. EHR systems offer clinical reminders and alerts, information assets for healthcare decision support, and aggregate data analysis for care administration and research. To extract clinical information from a paper medical record, the reader must edit data mentally or on paper. EHR systems give computer-based capabilities to organize, analyze, and respond to data \hyperref[b18]{[19]}. \section[{III. RESEARCH METHODOLOGIES}]{III. RESEARCH METHODOLOGIES}\par Health concerns that are common in India were the focus of the research. Below is a key point of the main healthcare concerns:\par ? The absence of a comprehensive end-to-end electronic health record (EHR) system interlinking among separate, stand-alone hospital record systems, as well as the lack of just-in-time record updating ? Because of the prevalence of handwritten prescriptions, an abundance of fake medications have entered the market.\par ? Unauthorized hospital administrators may access and change patients' information stored in insecure hospital databases, and caregivers aren't held accountable for any harm that may result.\par ? A lack of a secure, immutable, auditable, and traceable health infrastructure system\par The potential of an electronic health record system built on the Blockchain to resolve these problems is also highlighted. This study suggests a Blockchain-based HER system that can reliably identify users by their national ID, allows users access to and control over their health records, prevents malicious data manipulation, and can be easily scaled. As a result of the synergy, massive data like CT scans and X-ray reports may be kept in the cloud for easy access. A patient-centric electronic health record (EHR) system will need unique identifiers in order to accurately identify patients. When it comes to government-issued IDs like Aadhar and PAN, there is presently no comprehensive EHR system (Permanent Account Number).\par It is also essential that the proposed system include unique identifiers such as national IDs for patients to ensure accurate identification. Users need to be able to exercise control over their health information, such as authorizing updates, and this can only be achieved with secure identification.\par Blockchain's cutting-edge safety features prevent unauthorized changes to medical records. With the suggested scalable system, previous paper-based medical records may be migrated into the new system while also benefiting from useful features such as a mobile app-based interface for translating paper prescriptions to text using Natural Language Processing (NLP) algorithms. Therefore, the purpose of this thesis is to suggest a patient-centered EHR design that can communicate with other, separate healthcare systems and parse out information from paper prescriptions. The issues addressed by the suggested architecture are as follows:\par ? Health records should be readily available at the point of service and updated in real time to help medical professionals make more educated choices.\par ? Paper prescriptions are a common source of human mistake, but digitizing them and incorporating them into an existing system has many benefits.\par ? Data manipulation is impossible with secure, immutable, auditable, and traceable health infrastructure solutions. \section[{? Integrated Health Record (EHR) Systems and Local Hospitals}]{? Integrated Health Record (EHR) Systems and Local Hospitals}\par ? A patient-centered framework that protects sensitive information and gives individuals control over their own health records. \section[{IV. RESULTS AND ANALYSIS}]{IV. RESULTS AND ANALYSIS}\par The study's goals were strictly adhered to throughout every step of the process, from framework execution through data collecting and analysis to system design. In this section, we also use benchmarks and other forms of evaluation to figure out how well the suggested architectural framework works. Hyperledger caliper is an instrument for measuring the efficiency of blockchain systems. This works with many different hyperledger frameworks. The performance of the system and its many metrics, including latency and throughput, may be tested and operated with the use of caliper.\par System evaluation measures including latency, throughput, CPU utilization, memory, disc write/read, and network I/O are also checked and executed. The experiment was run with both read-and write-transaction modes, as well as with blocks of varied sizes and durations. \section[{Experiment With Varying Transaction}]{Experiment With Varying Transaction} \section[{Measurements with varying transaction: Write modes:}]{Measurements with varying transaction: Write modes:}\par In simulation, we employed 3 firms with 3 peers each and 1 Orderer. The experiment uses 1000 writing transactions at 50, 100, 150, 200, and 250 per second. 1 Firm 1 Peer, 2 Firm 2 Peer, and 3 Firm 3 Peer are tested for transaction performance. Each round consists of 1000 transactions at different per-second speeds (tps).\par Table \hyperref[tab_0]{1} shows the time needed to perform transactions in the atypical network arrangement. 1 firm 1 peer's 5005th transaction takes 240 seconds. 2firm2peer completes 4509 transactions in 240 seconds, but 3 firm 3 peer completes just 4001. Latency in a Blockchain network is the time between submitting a transaction and receiving network confirmation. Equation (1) measures blockchain write transaction delay. \section[{??? (1)}]{??? (1)}\par Where W l : Write transaction latency, Ct: confirmation time, Nth: Network threshold, St: Submission Time.\par Table \hyperref[tab_1]{2 illustrates} \hyperref[tab_0]{1} and\hyperref[tab_1]{2} show that delay increased with additional firms and peers. Table \hyperref[tab_2]{3} shows throughput for different transaction rates and the number of transactions per minute for three network types. 1 Firm and 1 Peer had the lowest average latency, fastest throughput per transaction rate, and most jobs per minute. The 3 Firm and 3 Peer network architecture had the greatest average latency, lowest throughput per transaction rate, and completed the fewest jobs per minute. The 2 Firm/2 Peer network concepts were in between. 1 firm 1 peer throughput is 190; however it decreases with more firms and peers. Table \hyperref[tab_2]{3} showed 182 for 2 firm 2 peer and 180 for 3 firm 3 peers. Write transaction throughput on a block chain network is given by:??????.. (\textbf{2})\par Where W t : Write transaction throughput, W ct : transaction committed on the entire network, T ts : Total transaction time, N cn : committed node. \section[{Measurements with varying transaction-Read modes:}]{Measurements with varying transaction-Read modes:}\par Five hyperledger caliper measurements were collected. The configuration file sets read mode to 50,100,150,200,250 tps. The delay for reading from a blockchain network may be calculated using equation \hyperref[b2]{(3)}.R l = R t -S t ? ???????. (\textbf{3})\par WhereVolume 23 | Issue 1 | Compilation 1.0 \section[{London Journal of Research in Computer Science and Technology}]{London Journal of Research in Computer Science and Technology}\par A Blockchain Technology to Secure Electronic Health Records in Healthcare System R l : Read transaction latency, Rt: Response time, S t = Submission time Equation ( \hyperref[formula_5]{4}) measures read transaction throughput from a blockchain network.R t = R o /T t ???????\textbf{(4)}\par Where R t : Read transaction throughput, R o : Total number of reading operations, T t = total time in sec. Reading or querying is quicker than writing a transaction, as seen in tables 4 and 5. Table \hyperref[tab_1]{2} shows that 3 firm 3 peer's maximum write latency was 78.009 seconds, while its greatest read latency was 12.099 seconds. Maximum read throughput for 1 firm 1 peer was 280, while write throughput was 180. The greatest read throughput with changing transaction rate was 240 for 3 firm 3 peer, compared to 180 for writes. Experiment with Varying block time \section[{Measurements with varying block time: Write modes:}]{Measurements with varying block time: Write modes:}\par This experiment tries to assess network latency and throughput. Hyperledger caliper's EHR system block formation time was modified between 250ms and 2s with variable outcomes. To reduce 3 firm 3 peer transaction latency, optimization metrics were used. Caliper defaults to block time after rising endorse policy block creation time. Switching from 250ms to 2s reduces latency by 35-50\%.\par Minimum latency for 50 tps is 40s, down from 80s. Table \hyperref[tab_5]{6} shows that 250 tps has 60s latency, down from 89s. Changing hyperledger's default network setup improves performance. Latency is inversely related to throughput; changing the block time and policy increases read throughput. Table \hyperref[tab_9]{9} shows that 50 tps transaction throughput is 49 and 250 tps is 77. Read throughput has risen 1.3 times. Experiment with Varying block size A blockchain's block size affects its performance. Changing block size improves performance. We analyzed 20 and 40-block sizes. Table \hyperref[tab_10]{10} shows completed transactions for block sizes 20 and 40 over time. Table \hyperref[tab_10]{10} shows those bigger blocks with a block size of 40 indicate more completed transactions, meaning a negligibly greater number of transactions per second. Our second experiment measured delay and block size as tps changed. We're using 50, 100, 150, 200, or 250 transactions per second. The assessment uses 20-by-40-blocks. Table \hyperref[tab_11]{11} shows those 20-byte blocks have 50\% less latency than 40-byte blocks. Reducing block size will reduce network latency, which may improve performance. Transaction per second for an individual node\par Transactions per second measures transaction volume (TPS). It may be approximated based on the number of test transactions and then recalculated.\par Transactions per Second of peer u can be calculated by the following equation ( {\ref 5}) ????????? ( {\ref 5})\par Where Tx: Number of transactions, t i , t j are initial and final time, respectively Average TPS of N peers, we can take the calculated by: CPU utilization CPU use is another key metric. It's the most essential OS number during tweaking. Almost all operating systems display user and system CPU use. These supplementary stats help determine CPU activity.\par Caliper estimates CPU use, RAM, incoming/outgoing traffic, and disc read/write. Table \hyperref[tab_12]{12} shows four rounds of transactions into our hypothetical blockchain network with a 1000-transaction ledger.\par Table \hyperref[tab_12]{12} shows CPU use by network model. The network models' CPU utilization varied with transaction rates. \section[{V. RESULT AND DISCUSSION ABOUT EXPERIMENTAL ANALYSIS}]{V. RESULT AND DISCUSSION ABOUT EXPERIMENTAL ANALYSIS}\par ? The simulation phase used a network model with three companies and three peers. As the number of firms, block size, and block duration rose, throughput and latency were assessed. ? Adding more firms and peers increases network latency. Read/query latency is lower than write latency.\par ? Increasing block time decreases latency, boosting network efficiency and throughput. When write block duration is raised from 250 ms to 2s, 250 tps throughput improves by 4x.\par ? Block size 20 is 50\% faster than block size 40, improving network performance.\par ? Since the network model's CPU utilization has remained steady over time, a drop in block size and an increase in block time will lead to a considerable decrease in network latency, boosting network performance. \section[{VI. CONCLUSION}]{VI. CONCLUSION}\par Blockchain is vital in today's healthcare systems. It may lead to automated data collection and verification procedures, accurate and aggregated data from varied sources, and a lesser risk of cyberattacks. Distributed data, redundancy, and failure tolerance are also possible. Blockchain might be an alternative to documenting transactions and sending data via a trusted third party. Blockchain may ease transparency and security concerns, such as third-party trust, at every level of a transaction, eliminating intermediaries or third parties. This book addresses contemporary healthcare business challenges, focusing on the Indian subcontinent. We propose system architecture and methodology for permission EHR that communicates with local freestanding EHR systems, checks users against national citizen databases like UIDAI, and collects data from handwritten prescriptions. The suggested framework's performance findings are impressive and might transform EHR systems throughout the Indian subcontinent.\begin{figure}[htbp] \noindent\textbf{1}\includegraphics[]{image-2.png} \caption{\label{fig_0}Figure 1 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{4}\includegraphics[]{image-3.png} \caption{\label{fig_1}© 2023 London Journals Press 4}\end{figure} \begin{figure}[htbp] \noindent\textbf{11}\includegraphics[]{image-4.png} \caption{\label{fig_2}1 Firm 1}\end{figure} \begin{figure}[htbp] \noindent\textbf{1} \par \begin{longtable}{P{0.4416666666666667\textwidth}P{0.08333333333333333\textwidth}P{0.10833333333333332\textwidth}P{0.10833333333333332\textwidth}P{0.10833333333333332\textwidth}} Time in min ->\tabcellsep 1\tabcellsep 2\tabcellsep 3\tabcellsep 4\\ 1 Firm 1 Peer\tabcellsep 801\tabcellsep 1909\tabcellsep 3901\tabcellsep 5005\\ 2 Firm 2 Peer\tabcellsep 701\tabcellsep 1600\tabcellsep 3500\tabcellsep 4509\\ 3 Firm 3 Peer\tabcellsep 601\tabcellsep 1452\tabcellsep 3303\tabcellsep 4001\end{longtable} \par \begin{quote} © 2023 London Journals Press 6 Volume 23 | Issue 1 | Compilation 1.0 A Blockchain Technology to Secure Electronic Health Records in Healthcare System\end{quote} \caption{\label{tab_0}Table 1 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{2} \par \begin{longtable}{P{0.2671428571428571\textwidth}P{0.11535714285714284\textwidth}P{0.1275\textwidth}P{0.12142857142857141\textwidth}P{0.10928571428571428\textwidth}P{0.10928571428571428\textwidth}} TPS->\tabcellsep 50\tabcellsep 100\tabcellsep 150\tabcellsep 200\tabcellsep 250\\ 1 Firm 1 Peer\tabcellsep 20.0098\tabcellsep 34.0098\tabcellsep 40.09\tabcellsep 50.08\tabcellsep 55.09\\ 2 Firm 2 Peer\tabcellsep 35.009\tabcellsep 44.0087\tabcellsep 49.009\tabcellsep 68.09\tabcellsep 70.1\\ 3 Firm 3 Peer\tabcellsep 46.1\tabcellsep 55.1\tabcellsep 60.009\tabcellsep 75.09\tabcellsep 78.009\end{longtable} \par \caption{\label{tab_1}Table 2 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{3} \par \begin{longtable}{P{0.3855670103092783\textwidth}P{0.07010309278350516\textwidth}P{0.0788659793814433\textwidth}P{0.10515463917525773\textwidth}P{0.10515463917525773\textwidth}P{0.10515463917525773\textwidth}} TPS->\tabcellsep 50\tabcellsep 100\tabcellsep 150\tabcellsep 200\tabcellsep 250\\ 1 Firm 1 Peer\tabcellsep 40\tabcellsep 90\tabcellsep 150\tabcellsep 175\tabcellsep 190\\ 2 Firm 2 Peer\tabcellsep 35\tabcellsep 82\tabcellsep 140\tabcellsep 170\tabcellsep 182\\ 3 Firm 3 Peer\tabcellsep 33\tabcellsep 77\tabcellsep 135\tabcellsep 165\tabcellsep 180\end{longtable} \par \caption{\label{tab_2}Table 3 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{4} \par \begin{longtable}{P{0.2579310344827586\textwidth}P{0.10551724137931034\textwidth}P{0.11137931034482759\textwidth}P{0.1289655172413793\textwidth}P{0.1289655172413793\textwidth}P{0.11724137931034483\textwidth}} TPS->\tabcellsep 50\tabcellsep 100\tabcellsep 150\tabcellsep 200\tabcellsep 250\\ 1 Firm 1 Peer\tabcellsep 2.02\tabcellsep 3.01\tabcellsep 3.0002\tabcellsep 4.0008\tabcellsep 5.129\\ 2 Firm 2 Peer\tabcellsep 6.0021\tabcellsep 7.0032\tabcellsep 8.0098\tabcellsep 10.0087\tabcellsep 11.021\\ 3 Firm 3 Peer\tabcellsep 7.0098\tabcellsep 8.0087\tabcellsep 10.0098\tabcellsep 11.098\tabcellsep 12.099\end{longtable} \par \caption{\label{tab_3}Table 4 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{5} \par \begin{longtable}{P{0.374\textwidth}P{0.068\textwidth}P{0.102\textwidth}P{0.102\textwidth}P{0.102\textwidth}P{0.102\textwidth}} TPS->\tabcellsep 50\tabcellsep 100\tabcellsep 150\tabcellsep 200\tabcellsep 250\\ 1 Firm 1 Peer\tabcellsep 80\tabcellsep 150\tabcellsep 200\tabcellsep 250\tabcellsep 280\\ 2 Firm 2 Peer\tabcellsep 60\tabcellsep 130\tabcellsep 180\tabcellsep 230\tabcellsep 250\\ 3 Firm 3 Peer\tabcellsep 50\tabcellsep 110\tabcellsep 170\tabcellsep 220\tabcellsep 240\end{longtable} \par \caption{\label{tab_4}Table 5 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{6} \par \begin{longtable}{P{0.2919191919191919\textwidth}P{0.1202020202020202\textwidth}P{0.10303030303030303\textwidth}P{0.1202020202020202\textwidth}P{0.11161616161616163\textwidth}P{0.10303030303030303\textwidth}} TPS->\tabcellsep 50\tabcellsep 100\tabcellsep 150\tabcellsep 200\tabcellsep 250\\ 250ms Block time\tabcellsep 40.001\tabcellsep 45.02\tabcellsep 50.02\tabcellsep 49.03\tabcellsep 60.05\\ 2s Block time\tabcellsep 80.007\tabcellsep 90.9\tabcellsep 85.008\tabcellsep 90.06\tabcellsep 89.6\end{longtable} \par \caption{\label{tab_5}Table 6 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{7} \par \begin{longtable}{} \end{longtable} \par \begin{quote} © 2023 London Journals Press 8 Volume 23 | Issue 1 | Compilation 1.0 A Blockchain Technology to Secure Electronic Health Records in Healthcare System\end{quote} \caption{\label{tab_6}Table 7}\end{figure} \begin{figure}[htbp] \noindent\textbf{7} \par \begin{longtable}{P{0.6008620689655172\textwidth}P{0.04396551724137931\textwidth}P{0.05129310344827586\textwidth}P{0.05129310344827586\textwidth}P{0.05129310344827586\textwidth}P{0.05129310344827586\textwidth}} TPS->\tabcellsep 50\tabcellsep 100\tabcellsep 150\tabcellsep 200\tabcellsep 250\\ 250ms Block time\tabcellsep 20\tabcellsep 25\tabcellsep 22\tabcellsep 25\tabcellsep 15\\ 2s Block time\tabcellsep 50\tabcellsep 70\tabcellsep 55\tabcellsep 60\tabcellsep 65\\ \multicolumn{3}{l}{Measurements with varying block time: Read modes}\tabcellsep \tabcellsep \tabcellsep \end{longtable} \par \caption{\label{tab_7}Table 7 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{8} \par \begin{longtable}{P{0.3233695652173913\textwidth}P{0.09239130434782608\textwidth}P{0.1108695652173913\textwidth}P{0.1108695652173913\textwidth}P{0.1108695652173913\textwidth}P{0.10163043478260869\textwidth}} TPS->\tabcellsep 50\tabcellsep 100\tabcellsep 150\tabcellsep 200\tabcellsep 250\\ 250 ms Block time\tabcellsep 20.09\tabcellsep 25.02\tabcellsep 30.03\tabcellsep 31.01\tabcellsep 38.1\\ 2s Block time\tabcellsep 9.1\tabcellsep 14.2\tabcellsep 20.1\tabcellsep 25.1\tabcellsep 30.4\end{longtable} \par \caption{\label{tab_8}Table 8 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{9} \par \begin{longtable}{P{0.425\textwidth}P{0.075\textwidth}P{0.0875\textwidth}P{0.0875\textwidth}P{0.0875\textwidth}P{0.0875\textwidth}} TPS->\tabcellsep 50\tabcellsep 100\tabcellsep 150\tabcellsep 200\tabcellsep 250\\ 250ms Block time\tabcellsep 50\tabcellsep 55\tabcellsep 55\tabcellsep 60\tabcellsep 57\\ 2s Block time\tabcellsep 70\tabcellsep 72\tabcellsep 78\tabcellsep 80\tabcellsep 76\end{longtable} \par \caption{\label{tab_9}Table 9 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{10} \par \begin{longtable}{P{0.23247863247863249\textwidth}P{0.06538461538461539\textwidth}P{0.07264957264957266\textwidth}P{0.07991452991452991\textwidth}P{0.07991452991452991\textwidth}P{0.07991452991452991\textwidth}P{0.07991452991452991\textwidth}P{0.07991452991452991\textwidth}P{0.07991452991452991\textwidth}} Time->\tabcellsep 00:15\tabcellsep 00:30\tabcellsep 00:45\tabcellsep 01:00\tabcellsep 01:15\tabcellsep 01:30\tabcellsep 01:45\tabcellsep 02:00\\ Block Size:40\tabcellsep 70\tabcellsep 100\tabcellsep 150\tabcellsep 225\tabcellsep 250\tabcellsep 400\tabcellsep 600\tabcellsep 725\\ Block Size:20\tabcellsep 60\tabcellsep 90\tabcellsep 140\tabcellsep 210\tabcellsep 245\tabcellsep 390\tabcellsep 590\tabcellsep 710\end{longtable} \par \caption{\label{tab_10}Table 10 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{11} \par \begin{longtable}{P{0.4053846153846154\textwidth}P{0.07846153846153846\textwidth}P{0.09153846153846154\textwidth}P{0.09153846153846154\textwidth}P{0.09153846153846154\textwidth}P{0.09153846153846154\textwidth}} TPS->\tabcellsep 50\tabcellsep 100\tabcellsep 150\tabcellsep 200\tabcellsep 250\\ Block Size:40\tabcellsep 80\tabcellsep 90\tabcellsep 85\tabcellsep 90\tabcellsep 89\\ Block Size:20\tabcellsep 40\tabcellsep 45\tabcellsep 50\tabcellsep 49\tabcellsep 60\end{longtable} \par \caption{\label{tab_11}Table 11 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{12} \par \begin{longtable}{P{0.85\textwidth}} Round-1\end{longtable} \par \caption{\label{tab_12}Table 12 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{13} \par \begin{longtable}{P{0.5377551020408163\textwidth}P{0.05782312925170068\textwidth}P{0.06360544217687075\textwidth}P{0.06360544217687075\textwidth}P{0.06360544217687075\textwidth}P{0.06360544217687075\textwidth}} TPS->\tabcellsep 50\tabcellsep 100\tabcellsep 150\tabcellsep 200\tabcellsep 250\\ peer0.firm1.example.com\tabcellsep 40\tabcellsep 32\tabcellsep 33\tabcellsep 38\tabcellsep 40\\ peer1.firm1.example.com\tabcellsep 35\tabcellsep 40\tabcellsep 39\tabcellsep 45\tabcellsep 42\\ peer2.firm1.example.com\tabcellsep 33\tabcellsep 35\tabcellsep 36\tabcellsep 40\tabcellsep 44\\ orderer.example.com\tabcellsep 18\tabcellsep 20\tabcellsep 19\tabcellsep 21\tabcellsep 22\end{longtable} \par \caption{\label{tab_13}Table 13 :}\end{figure} \begin{figure}[htbp] \noindent\textbf{13} \par \begin{longtable}{} \end{longtable} \par \caption{\label{tab_14}Table 13}\end{figure} \label{foot_0}\footnote{\label{foot_0} © 2023 London Journals Press} \backmatter \begin{bibitemlist}{1} \bibitem[Xu et al. (2017)]{b18}\label{b18} ‘A taxonomy of blockchain-based systems for architecture design’. X Xu , I Weber , M Staples , L Zhu , J Bosch , L Bass . \textit{Proceedings of 2017 IEEE International Conference on Software Architecture}, (2017 IEEE International Conference on Software ArchitectureGothenburg, Sweden) 2017 Apr 3-7. p. . \bibitem[Shaikh and Hannan (2022)]{b13}\label{b13} ‘An Examination of the Blockchain Technology: Challenges and Future Opportunities’. Abdul Shaikh , Hannan . \textit{International Journal of Engineering and Computer Science} 09 November2022. 11 p. . \bibitem[Shaikh and Hannan (2016)]{b1}\label{b1} ‘An Overview of Big Data and Hadoop’. Abdul Shaikh , Hannan . \textit{International Journal of Computer Application} -0975-887. November 2016. New York, USA. 154 (10) . \bibitem[Dagher et al. ()]{b2}\label{b2} \textit{Ancile: privacy-preserving framework for access control and interoperability of electronic health records using blockchain technology}, G G Dagher , J Mohler , M Milojkovic , P B Marella . 2018. Sustain Cities Soc. 39 p. . \bibitem[Minoli and Occhiogrosso (2018)]{b9}\label{b9} \textit{Blockchain mechanisms for IoT security. Internet of Things}, D Minoli , B Occhiogrosso . 2018 Sep. 1 p. . \bibitem[Shaikh and Hannan (2023)]{b5}\label{b5} ‘Challenges of Blockchain Technology using Artificial Intelligence in Healthcare System’. Abdul Shaikh , Hannan . \textit{International Journal of Innovative Research in Science, Engineering and Technology (IJIRSET)} Jan 2023. 12 p. . (Issue 01) \bibitem[Shaikh and Hannan (2023)]{b17}\label{b17} ‘Challenges of Blockchain Technology using Artificial Intelligence in Healthcare System’. Abdul Shaikh , Hannan . \textit{International Journal of Innovative Research in Science, Engineering and Technology (IJIRSET)} Jan 2023. 12 p. . (Issue 01) \bibitem[Neal (2011)]{b10}\label{b10} ‘Choosing an electronic health records system: professional liability considerations’. D Neal . \textit{Innov Clin Neurosci} 2011 Jun. 8 (6) p. . \bibitem[Xhafa et al. (2014)]{b16}\label{b16} ‘Designing cloud-based electronic health record system with attribute-based encryption’. F Xhafa , J Li , G Zhao , J Li , X Chen , D S Wong . \textit{Multimed Tools Appl} 2014 Feb 11. 74 (10) p. . \bibitem[Prasad et al.]{b11}\label{b11} ‘Detailed Investigation of the role of Artificial Intelligence in stock market predictions’. Arun Prasad , Shaikh Abdul Hannan , Kavita Panjwani , Muthe Ramu , Kawaender Singh Sidhu , Nagabhusanam Tida . \textit{British Journal of Administrative Management} UK. 58. (Issue 06, 6 th Sept 2022) \bibitem[Mcmullen et al. (2014)]{b8}\label{b8} ‘Electronic Medical Records and Electronic Health Records: Overview for Nurse Practitioners’. P C Mcmullen , W O Howie , N Philipsen , V C Bryant , P D Setlow , M Calhoun , Z D Green . \textit{The Journal for Nurse Practitioners} 2014 Oct. 10 (9) p. . \bibitem[Nugent et al. ()]{b12}\label{b12} ‘Improving data transparency in clinical trials using blockchain smart contracts’. T Nugent , D Upton , M Cimpoesu . \textit{F1000Res} 2016. 5 p. 2541. \bibitem[Van Der Linden et al. ()]{b15}\label{b15} ‘Interorganizational future proof EHR systems: a review of the security and privacy related issues’. H Van Der Linden , D Kalra , A Hasman , J Talmon . \textit{Int J Med Inform} 2009. 78 (3) p. . \bibitem[Kierkegaard (2012)]{b7}\label{b7} \textit{Medical data breaches: Notification delayed is notification denied. Computer Law \& Security Review}, P Kierkegaard . 2012 Apr. 28 p. . \bibitem[Dubovitskaya et al. ()]{b3}\label{b3} ‘Secure and Trustable Electronic Medical Records Sharing using Blockchain’. A Dubovitskaya , Z Xu , S Ryu , M Schumacher , F Wang . \textit{AMIA Annu Symp Proc} 2017. 2017 p. . \bibitem[Dubovitskaya et al. ()]{b4}\label{b4} ‘Secure and trustable electronic medical records sharing using Blockchain’. A Dubovitskaya , Z Xu , S Ryu , M Schumacher , F Wang . \textit{AMIA Annu Symp Proc} 2018. 2017 p. . \bibitem[Ichikawa et al. (2017)]{b6}\label{b6} \textit{Tamper-Resistant Mobile Health Using Blockchain Technology. JMIR Mhealth Uhealth}, D Ichikawa , M Kashiyama , T Ueno . 2017 Jul 26. 5 p. 111. \bibitem[Rifi et al. ()]{b14}\label{b14} ‘Towards using blockchain technology for eHealth data access management’. N Rifi , E Rachkidi , N Agoulmine , N C Taher . \textit{Fourth International Conference on Advances in Biomedical Engineering (ICABME); October 19-21}, (Beirut, Lebanon) 2017. 2017. \bibitem[Azaria et al. ()]{b0}\label{b0} ‘Using Blockchain for Medical Data Access and Permission Management’. A Azaria , A Ekblaw , T Vieira , Medrec . \textit{nd International Conference on Open and Big Data (OBD)}, (Vienna, Austria) August 22-24, 2016. 2016. p. . \end{bibitemlist} \end{document}