| Literature DB >> 35346176 |
Abstract
BACKGROUND: Blockchain technology has the potential to revolutionize information sharing in companies. Many studies suggest using blockchain-powered platforms to replace existing mechanisms for health information exchange (HIE) across healthcare organizations. However, very few blockchain-based projects have been implemented in the healthcare sector. This study takes a qualitative approach to explore benefits, concerns, and barriers to the rollout of blockchain in HIE projects from physicians' perspectives.Entities:
Keywords: Barriers; Benefits; Blockchain technology; HIE; Interviews; Physicians
Mesh:
Year: 2022 PMID: 35346176 PMCID: PMC8962111 DOI: 10.1186/s12911-022-01815-8
Source DB: PubMed Journal: BMC Med Inform Decis Mak ISSN: 1472-6947 Impact factor: 2.796
Qualitative interview questions
| Category | Interview questions (baseline) |
|---|---|
| Evidence | Your current awareness of blockchain concepts and characteristics? Your general knowledge about blockchain-based projects in healthcare? Your prior experience with an HIE network? Your prior participation in a blockchain-based HIE solution? |
| Context | The key problems with information sharing among healthcare organizations? The main issues with exiting HIE efforts? Your opinions and reflections about using blockchain in healthcare? Your attitudes about integrating blockchain into HIE networks? |
| Facilitation | The potential benefits of using blockchain in HIE efforts? The concerns and risks associated with using blockchain in HIE efforts? Your suggestions about integrating blockchain in HIE efforts? Your recommendations about the successful rollout of blockchain-enabled HIE in healthcare institutions? |
Sample characteristics
| Variable | Categories | n (%) |
|---|---|---|
| Gender | Male | 24 (63) |
| Female | 14 (37) | |
| Age | Under 35 | 4 (10) |
| 35–44 | 11 (29) | |
| 45–54 | 18 (48) | |
| 55–64 | 3 (8) | |
| 65 or older | 2 (5) | |
| How long have you been practicing? (years) | 1–5 | 7 (18) |
| 6–10 | 8 (21) | |
| 11–15 | 16 (42) | |
| 16–20 | 4 (11) | |
| More than 20 | 3 (8) | |
| Specialty | Emergency medicine | 2 (5) |
| Family medicine | 7 (19) | |
| Psychiatry | 1 (3) | |
| Surgery | 5 (13) | |
| Anesthesiology | 4 (10) | |
| Pediatric | 3 (8) | |
| Internal medicine | 6 (16) | |
| Gynecology | 4 (10) | |
| Urology | 3 (8) | |
| General practitioner | 3 (8) | |
| Type of hospital/clinic | Public hospital | 12 (31) |
| Private hospital | 9 (24) | |
| Academic medical center | 4 (11) | |
| Nonprofit hospital | 4 (11) | |
| Clinics | 7 (18) | |
| Rehabilitation | 2 (5) | |
| Healthcare setting | Rural | 7 (18) |
| Urban | 28 (74) | |
| Community | 3 (8) | |
| Has the hospital/clinic you work in implemented or participated in an HIE program? (inclusion criteria) | Yes | 38 (100) |
| No | 0 | |
| Have you ever participated in an HIE network to share patients' information? (inclusion criteria) | Yes | 38 (100) |
| No | 0 |
Open codes for problems with existing HIE mechanisms used for information sharing
| Open codes | Common concept |
|---|---|
| Mainly focusing on EHRs, downtime issues, EHR-based exchange, not compatible EHRs, lack of standards, reliability of EHR systems, interoperability issues of uncertified EHRs | EHR-focused exchange |
| Centralization, central ownership, centralized authority, managed by a middleman | Centralized mechanism |
| lack of patient-provider interactions, lack of support for care coordination, delays in care delivery | Care coordination |
| Not transparent, fuzzy purposes of sharing, unclear permission process, lack of visibility of sharing process, ambiguous ownership transfer | Transparency of sharing mechanisms |
| Privacy concerns, security issues, data breach, a single point of failure, technical security measures | Privacy and security |
| Data are outdated in HIE databases, unavailability of patient data, incomplete or inaccurate patient information is stored in shared records, lack of real-time access to patient data, data inconsistency, duplicate data | Data quality |
| Trust issues, trust in recipients, trust-based systems, trust in networks | Trust |
| Data can be altered, medical records can be manipulated, information can be removed by any entities participating in HIE initiatives | Mutability |
Listing of constructs, definitions, anecdotal evidence, and count for issues with current HIEs
| Axial Codes (Constructs) | Definition | Sample Quotes | Count |
|---|---|---|---|
| EHR-focused exchange | The extent to which existing HIE systems are functional depending on EHR systems | “Many EHRs are used by various healthcare providers. If the EHR of sender or receiver is down, the exchange will be disrupted.” | 32 |
| Centralized mechanism | The extent to which existing HIE systems are centralized | “HIE systems are mainly centralized, meaning that an organization has the final decision-making authorities.” | 29 |
| Care coordination | The extent to which existing HIE systems may not support care coordination among multiple entities | “Current HIE mechanisms could take some beneficiaries out of the loop, such as patients.” | 25 |
| Transparency of exchange platforms | The extent to which existing HIE mechanisms and their policies may not be transparent | “Sometimes, it is not clear why certain personal health information should be shared.” | 23 |
| Privacy and security | The extent to which existing HIE may not use technical security measures to protect health information | “Security safeguards of current HIE cannot 100% guarantee the privacy and confidentiality of data.” | 21 |
| Data quality | The extent to which existing HIE systems may not maintain the quality of healthcare data | “Lots of medical records in HIE databases are not useful because they are not current data or they may have missing values.” | 20 |
| Trusting relationships | The extent to which existing HIE systems rely on shaped trust in networks | “Now, sharing health information through HIE needs a huge amount of trust in recipients.” | 16 |
| Mutability of data | The extent to which health data can be altered and manipulated in existing HIE systems | “It is possible that the content of a health record is changed during sharing process with no notification.” | 14 |
Selective codes representing problems with existing HIE systems
| Selective codes (themes) | Constructs involved | Definition |
|---|---|---|
| Data-related issues | Data quality + mutability of data | The extent to which existing HIE systems may not support data quality and maintain immutability of medical records during sharing processes |
| Exchange platform-related issues | EHR-focused exchange + centralized mechanism + privacy and security + transparency of exchange platforms | The extent to which centralized platforms used in existing HIE systems may not ensure transparency of information-sharing efforts and safeguard the privacy of health information |
| Network-related issues | Care coordination + trusting relationships | The extent to which existing HIE systems may not help care coordination and increase trusting relationships between involved entities |
Open codes for perceived benefits of using blockchain in HIEs
| Open codes | Common concept |
|---|---|
| ID control, access control, data protection and privacy, security, encryption, cryptographic keys, secure network infrastructure, the anonymity of all users in the blockchain system, blockchain protects user privacy, unhackable networks, identity management, confidential and private transactions, each transaction needs patient’s authorization, user information does not link with personal information, mitigating security and privacy issues | Encryption and control |
| Data integrity, data integration, helping with data storage and data aggregation, data consistency through immutability | Data management |
| Better coordination, improved coordination, resolving interoperability conflicts, real-time monitoring of patients’ health status | Interoperable mechanism |
| Decentralization, empowerment of end-users, accessibility, the democratization of data, new roles defined, more participants, sharing authority, decentralized decision-making power, availability of data in P2P networks | Decentralized system |
| Digital facilitation of negotiation, automated verification, computerized execution, and enforcement of contracts, automatic identification and authentication of all participants, sharing information through smart contracts without a third-party intermediary | Smart contracts |
| Transparency of sharing, data provenance, no repudiation, transparent transaction logs, clear mechanisms, no shady activities, transparent data sharing protocols | Transparent protocols |
| Reduced downtime, the system is always available, optimal uptime, systems less likely will fail to perform, network downtime, no inactive time, not offline period, No system breaks | System uptime |
| Reduced costs of transactions, no need to pay a middleman, lower transaction costs, lower costs of data preparation, increased speed of transactions, faster data exchange | Speed and cost of transactions |
Listing of constructs, definitions, anecdotal evidence, and count for perceived benefits of blockchain-based HIEs
| Axial Codes (Constructs) | Definition | Sample Quotes | Count |
|---|---|---|---|
| Encryption and control | The extent to which blockchain is secure to encrypt data, control access, and protect the privacy of health information during transactions | “Blockchain functions based on a secure network infrastructure that ensures confidentiality and privacy of sensitive health information.” | 35 |
| Data management | The extent to which blockchain can improve data storage, data aggregation, and data consistency | “Systems using blockchain can integrate data from different sources (such as patients) and effectively distribute them across different entities.” | 29 |
| Interoperable mechanism | The extent to which blockchain enables to communicate and exchange usable data across different parties in a network | “Blockchain technology can overcome the interoperability barriers of the current HIE systems and facilitate interoperable communications between different healthcare organizations.” | 27 |
| Decentralized system | The extent to which blockchain can distribute authority and decision-making power across various entities in a network | “Relying on a P2P network, more roles are defined, and more people will be in the loop of information provision, verification, and exchange.” | 23 |
| Smart contracts | The extent to which blockchain enables smart contracts to digitalize, control, and automate transactions | “Blockchain-powered networks can run programs and codes to verify and execute transactions automatically when predetermined conditions are met.” | 20 |
| Transparent protocols | The extent to which blockchain uses protocols to increase the transparency of information sharing transactions | “Users can visibly track where health data comes from, what happens to it, where it goes over time, and why it is shared.” | 17 |
| System uptime | The extent to which blockchain platforms could be free from network downtime and inactive time | “In the last decade, only blockchain platforms proved the claim of enhanced system uptime.” | 15 |
| Speed and cost of transactions | The extent to which blockchain could increase the effectiveness and efficiencies of information-sharing efforts | “blockchain is seen as being better than previous technologies in terms of reducing costs and improving the speed of transactions.” | 11 |
Selective codes representing benefits of blockchain-based HIEs
| Selective codes (themes) | Constructs involved | Definition |
|---|---|---|
| Innovative technological features | Encryption and control + smart contracts + transparent protocols + data management | The extent to which blockchain uses innovative features to improve encryption, access control, data management, transparency of sharing procedures, and automatic verification and execution of transactions |
| Collaborative ecosystem | Interoperable mechanism + decentralized system | The extent to which blockchain uses decentralized platforms to improve interoperability standards in healthcare |
| System performance | System uptime + speed and cost of transactions | The extent to which reliable blockchain-based networks could increase the effectiveness and efficiency of information sharing transactions |
Open codes for perceived concerns associated with using blockchain in HIEs
| Open codes | Common concept |
|---|---|
| Familiarity, knowledge, exposure, understanding, insights about the system | Awareness |
| Outsourcing, outsourced platforms, in-house, third-party supplier, system design phase, contracting with a vendor, designer contract, contract with an outside provider | Selection decision |
| Regulatory issues, unclear rules and regulations, lack of regulatory guidelines, lack of supporting laws, not regulated area, not aligned with HIPAA regulation privacy compliance metrics | Regulations and laws |
| Not doable projects, not feasible efforts, lack of support from managers, not aligned with hospital strategic directions, not backed by healthcare organizations' policymakers | Feasibility |
| Involvement of various entities, collaboration issues, patient roles, needs for a strong network of relationships, communications issues among different beneficiaries | Stakeholders participation |
| Blockchain architectures, public or private models, authority agency, various platforms, model conflicts, right model in healthcare, different model structures, different verification procedures, consensus algorithm | Blockchain model types |
| Resource allocations, workflow changes, installing a new system, integrating blockchain into healthcare, system installation, network infrastructure, implementation duration, implementation cost | Implementation |
| Lack of adoption in the market, competitors' adoption, other providers' acceptance, not popular in the market yet, challenge with the widespread adoption of blockchain, state of blockchain adoption | Industry traction |
| Lack of technical trust, untrustworthy technical underpinning, technological immaturity, unreliable foundation, technology in its infancy, instability, unscalable, errors | Trust in technology |
| Not easy to use, complicated foundations, confusing protocols, difficult platforms | Complexity |
Listing of constructs, definitions, anecdotal evidence, and count for perceived concerns of blockchain-based HIEs
| Axial Codes (Constructs) | Definition | Sample Quotes | Count |
|---|---|---|---|
| Lack of knowledge about blockchain technology | The extent to which healthcare providers may not be aware of blockchain applications in healthcare and why they could be useful | “Most of my colleagues don’t know what blockchain is… and how it can be used in healthcare practices.” | 34 |
| Implementation issues | The extent to which healthcare organizations may not have required resources and effective planning to integrate blockchain into routine healthcare practices | “Some managers are terrified by technical issues, time, cost, training, and value-added of blockchain projects.” | 32 |
| Regulatory issues | The extent to which physicians believe that using blockchain-based HIE is not fully regulated | “I don’t think blockchain applications are completely regulated in the healthcare space and still need laws to support it.” | 30 |
| Selection decision | The extent to which selecting blockchain platforms in healthcare is challenging when there are various alternatives (i.e., outsourced, in-house) | “Many outside providers can design blockchain-based exchange methods, but some managers believe they need to develop blockchain platforms in-house.” | 27 |
| Feasibility issues | The extent to which blockchain projects may not be a feasible effort from organizational perspectives | “I think blockchain integration is not a feasible endeavor for healthcare managers; that’s why many of them do not support these kinds of projects.” | 25 |
| Lack of collaboration among various stakeholders | The extent to which various stakeholders may not be willing to collaborate in blockchain-based HIE | “A number of entities got to collaborate in blockchain HIE, such as patients…. I am not sure if all agree on the role of patients in transactions.” | 23 |
| Blockchain model types | The extent to which healthcare providers may not deploy the right blockchain models (among various architectures) which is suitable in the healthcare domain (e.g., public, private, hybrid, federated) | “There are some blockchain architectures, but it is challenging to realize which one could be the most secure model with a robust infrastructure for information exchange in healthcare.” | 21 |
| Complicated system | The extent to which using blockchain may not be free of effort for users | “Technological foundations of the blockchain and smart contracts do not seem to be easy.” | 18 |
| Network effects | The extent to which competitors (such as large healthcare organizations) may not adopt blockchain | “We are scared that we are the only one [ | 15 |
| Lack of trust in blockchain technology | The extent to which healthcare providers believe that blockchain may not be a trustworthy, reliable, and error-free technology | “I think blockchain is still a new technology, still unstable and not scalable.” | 12 |
Selective codes representing concerns about blockchain-based HIE
| Selective codes (themes) | Constructs involved | Definition |
|---|---|---|
| Individual-related issues | Lack of knowledge about blockchain technology + lack of trust in blockchain technology | The extent to which physicians may not be familiar and aware of blockchain platforms and may not trust in the reliability of this technology |
| Technology-related issues | Complicated system + Blockchain model types | The extent to which developing the right type of blockchain architecture compatible with healthcare would be challenging, and that blockchain model may not be easy to use for HIE purposes |
| Organizational-related issues | Feasibility issues + selection decision + implementation issues | The extent to which healthcare organizations believe that blockchain projects may not be feasible, selecting blockchain-platform is challenging, and the required resources may not be available for a successful rollout |
| Market-related issues | Network effects + lack of collaboration among various stakeholders + regulatory issues | The extent to which regulations may not support blockchain applications, the healthcare market may not be receptive, and stakeholders may not fully participate in blockchain projects |
Fig. 1Guiding framework