Published On February 13, 2023
Journal Issue LJRCST Volume 23 Issue 1

A Blockchain Technology to Secure Electronic Health Records in Healthcare System

Abdul Hannan
Abdul Hannan
¶ ∐
Article Fingerprint
Research ID 0L85C

IntelliPaper

Abstract

The study proposes a blockchain-based patient-centric EHR solution for India. The proposed framework would provide a secure health infrastructure system, make data tampering impossible, enable just-in-time availability of healthcare information, remove handwritten prescriptions, and offer end-to-end monitoring, and increase patient privacy and record management. The research connects to hospital databases to incorporate previous handwritten prescriptions into the new system. In the Hyperledger Fabric-based design, patients will view, write, and control authorization to their medical information through a web or mobile interface. During implementation, we used a network model with three companies and three peers. When write block duration is raised from 250ms to 2s, 250tps throughput improves by 4x. Block size 20 is 50% faster than block size 40, improving network performance. 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.

Explore Digital Article Text

I. INTRODUCTION

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 . For us to meet this challenge, we'll need to manage our resources efficiently.

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 . 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 .

II. LITERATURE SURVEY

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.

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 .

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.

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.

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 .

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.[6].

2.1 Healthcare Records Security Breaches

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 1 shows 500+ Healthcare Data breaches from 2009 to 2020.

{"image_source":{"path":"images/807a7e62bf80c12e199a82b74b7119bf60a235085565da9d89851992805df7de.jpg"},"content":"","chart_caption":[{"type":"text","content":"Figure 1: 500+ Healthcare Data Breaches Spanning 2009-2020"}],"chart_footnote":[]} 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.

2.2 Electronic Health Record (HER) Benefits

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 .

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 .

Figure 2: Typical Features of an Ideal EHR System

A Blockchain Technology to Secure Electronic Health Records in Healthcare System

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 [9]. Even in industrialized countries, the need to enhance healthcare is evident. Before the epidemic, EHR implementation faced difficult hurdles.

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 . It's impractical to assume ideal efficiency in the early phases of EHR deployment, although training may boost user competency.

2.3 Blockchain Technology: From Centralized to Decentralized System

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 .

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[12].

2.4 Permissionless or Public Blockchain

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 . 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 .

2.5 Permissioned or private Blockchain

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.

Permissioned blockchain uses a membership structure to admit users. In permissioned Blockchains , 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 .

2.6 Electronic Health Record (EHR) Is a Social Need

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 .

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.[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 .

III. RESEARCH METHODOLOGIES

Health concerns that are common in India were the focus of the research. Below is a key point of the main healthcare concerns:

  • 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.

  • 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.

  • A lack of a secure, immutable, auditable, and traceable health infrastructure system

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).

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.

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:

  • Health records should be readily available at the point of service and updated in real time to help medical professionals make more educated choices.

  • Paper prescriptions are a common source of human mistake, but digitizing them and incorporating them into an existing system has many benefits.

  • Data manipulation is impossible with secure, immutable, auditable, and traceable health infrastructure solutions.

  • Integrated Health Record (EHR) Systems and Local Hospitals

  • A patient-centered framework that protects sensitive information and gives individuals control over their own health records.

IV. RESULTS AND ANALYSIS

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.

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.

4.1 Experiment With Varying Transaction

Measurements with varying transaction: Write modes:

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).

Table 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.

Table 1: Total Completed Transactions for Three Configuration Models Over Four Minutes

Time in min ->1234
1 Firm 1 Peer801190939015005
2 Firm 2 Peer701160035004509
3 Firm 3 Peer601145233034001

Latency in a Blockchain network is the time between submitting a transaction and receiving network confirmation. Equation (1) measures blockchain write transaction delay.

\[W_{l} = (C_{t} * N_{th}) - S_{t}\tag{1}\]

Where : Write transaction latency, Ct: confirmation time, Nth: Network threshold, St: Submission Time.

Table 2 illustrates 1 Firm 1 Peer, 2 Firm 2 Peer, and 3 Firm 3 Peer average latency for varying transaction rates. It grows with the firms and peers. TPS grows proportionally to delay. 1 Firm 1 Peer has the lowest latency at 50TPS with 20.0098, whereas 2firm2peer and 3firm3peer have 35.009 and 46.1 correspondingly. Tables 1 and 2 show that delay increased with additional firms and peers.

Table 2: Variable Transaction Rates Affect Average Latency Measurements (50 Tps Through 250 Tps)

TPS->50100150200250
1 Firm 1 Peer20.009834.009840.0950.0855.09
2 Firm 2 Peer35.00944.008749.00968.0970.1
3 Firm 3 Peer46.155.160.00975.0978.009

Table 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 3 showed 182 for 2 firm 2 peer and 180 for 3 firm 3 peers.

Table 3: Variable Transaction Rate Throughput Readings (50 Tps Through 250 Tps)

TPS->50100150200250
1 Firm 1 Peer4090150175190
2 Firm 2 Peer3582140170182
3 Firm 3 Peer3377135165180

Write transaction throughput on a block chain network is given by:

\[W _ {t} = (W _ {c t} / T _ {t s}) * N _ {c n}\tag{...... (2}\]

Where : Write transaction throughput, : transaction committed on the entire network, : Total transaction time, : committed node.

Measurements with varying transaction- Read modes:

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 (3).

\[R_{l}=R_{t}-S_{t}...\tag{3}\]

Where

: Read transaction latency, Rt: Response time, Submission time Equation (4) measures read transaction throughput from a blockchain network.

\[\mathrm{R}_{t} = \mathrm{R}_{0} / \mathrm{T}_{t}\]

......(4) Where : Read transaction throughput, : Total number of reading operations, . Reading or querying is quicker than writing a transaction, as seen in tables 4 and 5.

Table 4: Read Average Delay for Different Transaction Rates

TPS->50100150200250
1 Firm 1 Peer2.023.013.00024.00085.129
2 Firm 2 Peer6.00217.00328.009810.008711.021
3 Firm 3 Peer7.00988.008710.009811.09812.099

Table 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.

Table 5: Average Throughput with Varying Transaction Rate for Read

TPS->50100150200250
1 Firm 1 Peer80150200250280
2 Firm 2 Peer60130180230250
3 Firm 3 Peer50110170220240

Experiment with Varying block time

Measurements with varying block time: Write modes:

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%.

Minimum latency for 50 tps is 40s, down from 80s. Table 6 shows that 250 tps has 60s latency, down from 89s. Changing hyperledger's default network setup improves performance.

Table 6: Average Latency with Varying Block Time for Write

TPS->50100150200250
250ms Block time40.00145.0250.0249.0360.05
2s Block time80.00790.985.00890.0689.6

Table 7 depicts transaction throughput, which increases commit time and transaction success rate due to the network's variable block time policy. At 50 tps, throughput has grown 2.5-fold, from 20 to 49. Similarly, increasing block duration from 250 ms to 2s quadruples 250 tps throughput.

Table 7: Average Throughput with Varying Block Time for Write

TPS->50100150200250
250ms Block time2025222515
2s Block time5070556065

Measurements with varying block time: Read modes

The read transaction mode reads transactions at a set interval. Modifying the network's endorsement policy and block time for transaction reading improves system speed. Variable block generation time optimizes blockchain for reading and querying transactions. Table 8 shows transaction rate and latency optimizations. Changing the policy and block time by 2s increases average delay by 9s. The default block time for 250 tps is 37s, however with the modified setup, it's 30s.

Table 8: Average Latency with Varying Block Time for Read

TPS->50100150200250
250 ms Block time20.0925.0230.0331.0138.1
2s Block time9.114.220.125.130.4

Latency is inversely related to throughput; changing the block time and policy increases read throughput. Table 9 shows that 50 tps transaction throughput is 49 and 250 tps is 77. Read throughput has risen 1.3 times.

Table 9: Average Throughput with Varying Block Time for Read

TPS->50100150200250
250ms Block time5055556057
2s Block time7072788076

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 10 shows completed transactions for block sizes 20 and 40 over time. Table 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 11 shows those 20-byte blocks have less latency than 40-byte blocks. Reducing block size will reduce network latency, which may improve performance.

Table 10: Number of Completed Transactions with Varying Block Size

Time->00:1500:3000:4501:0001:1501:3001:4502:00
Block Size:4070100150225250400600725
Block Size:206090140210245390590710

Table 11: Average Latency with varying Block size

TPS->50100150200250
Block Size:408090859089
Block Size:204045504960

Transaction per second for an individual node

Transactions per second measures transaction volume (TPS). It may be approximated based on the number of test transactions and then recalculated.

Transactions per Second of can be calculated by the following equation (5)

\[T P S _ {u} = \frac {\operatorname{Count} \left(T _ {x} i n \left(t _ {i} , t _ {j}\right)\right)}{t _ {j} - t _ {i}} (t x s / s)\tag{......(5}\]

Where Tx: Number of transactions, , 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.

Caliper estimates CPU use, RAM, incoming/outgoing traffic, and disc read/write. Table 12 shows four rounds of transactions into our hypothetical blockchain network with a 1000-transaction ledger.

Table 12 shows CPU use by network model. The network models' CPU utilization varied with transaction rates.

Table 12: Four Experiments' Resource Use

Round-1
TypeNameCPU (avg.)Memory (avg)Traffic inTraffic outDisc write
Dockerpeero.firm1.example.com36.6284.5MB10.4MB4.5MB4.2MB
Dockerpeero.firm2.example.com28.4280.0MB10.5M5.6MB4.2MB
Dockerpeero.firm3.example.com25.1275.5MB12.5MB9.8MB4.2MB
DockerOrderer.example.com19.3450.0MB2.5MB1.2MB1.2MB

Round-2

TypeNameCPU(avg.)Memory(avg.)Traffic InTraffic OutDisc Write
Dockerpeer0.firm1.example.com38.8274.5MB19.4MB9.5MB9.2MB
Dockerpeer0.firm2.example.com29.5270.5MB15.5M15.6MB9.25MB
Dockerpeer0.firm3.example.com26.19262.5MB15.5MB19.8MB10.25MB
DockerOrderer.example.com20.451.0MB4.5MB1.25MB2.2MB
Round-3
TypeNameCPU(avg.)Memory(avg.)Traffic InTraffic OutDisc Write
Dockerpeer0.firm1.example.com45.9272.0MB20.4MB10.5MB10.2MB
Dockerpeer0.firm2.example.com29.79268.5MB20.5M17.8MB11.7MB
Dockerpeer0.firm3.example.com26.6260.5MB22.5MB21.8MB14.5MB
DockerOrderer.example.com20.951.5MB4.5MB1.9MB2.2MB
Dockerpeero.firm1.example.com47.3282.0MB21.4MB11.5MB11.25MB
Dockerpeero.firm2.example.com30.8270.5MB21.5MB18.8MB11.7MB
Dockerpeero.firm3.example.com27.5262.5MB25.5MB22.8MB14.5MB
DockerOrderer.example.com21.155.5MB5.5MB2.9MB3.2MB

Round-3

Peer1.firm1.example.com had the greatest CPU use at 200 transactions per second, while peer0.firm1.example.com had the lowest at 100.

Table 13: Average CPU Use (%) for the Network Model After 3 Rounds

TPS->50100150200250
peer0.firm1.example.com4032333840
peer1.firm1.example.com3540394542
peer2.firm1.example.com3335364044
orderer.example.com1820192122

Table 13 is a network heatmap. Simulations reveal a large data volume transmission between peers since caliper generates and approves transactions. No traffic means green diagonals. The orderer distributes blocks to all peers, causing Firm 1's Peer 0 to get 8.25MB and send 1.3MB.

V. RESULT AND DISCUSSION ABOUT EXPERIMENTAL ANALYSIS

  • 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.

  • 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.

  • Block size 20 is 50% faster than block size 40, improving network performance.

  • 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.

VI. CONCLUSION

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.

Conflict of Interest

The authors declare no conflict of interest.

Ethical Approval

Not applicable

Data Availability

The datasets used in this study are openly available at [repository link] and the source code is available on GitHub at [GitHub link].

Funding

This work did not receive any external funding.

References

18 Cites in Article

Cite this article

Generating citation...

Related Research

  • DDC Code: 332.178 LCC Code: HG1710
  • Version of record

    v1.0

  • Issue date

    13 February 2023

  • Language

    en

Iconic historic building with domed tower in London, UK.
Open Access
Research Article
CC-BY-NC 4.0
Views 743
Downloads 39
Special Issue

Launch a focused special issue to highlight research, emerging trends, and expert insights in your academic field.

Support