| Literature DB >> 33185553 |
Keehyuck Lee1,2, Kahyun Lim1, Se Young Jung1,2, Hyerim Ji1, Kyungpyo Hong1, Hee Hwang1,2, Ho-Young Lee1,3.
Abstract
BACKGROUND: Although the electronic health record system adoption rate has reached 96% in the United States, implementation and usage of health information exchange (HIE) is still lagging behind. Blockchain has come into the spotlight as a technology to solve this problem. However, there have been no studies assessing the perspectives of different stakeholders regarding blockchain-based patient-centered HIE.Entities:
Keywords: blockchain; health information exchange; qualitative study
Year: 2020 PMID: 33185553 PMCID: PMC7695529 DOI: 10.2196/18582
Source DB: PubMed Journal: J Med Internet Res ISSN: 1438-8871 Impact factor: 5.428
Demographic characteristics of participants (N=21).
| Characteristic | n (%) | |
|
|
| |
|
| Patients | 7 (33) |
|
| Doctors | 7 (33) |
|
| Developers | 7 (33) |
|
|
| |
|
| Male | 16 (76) |
|
| Female | 5 (24) |
|
|
| |
| <30 | 0 (0) | |
|
| 30-39 | 4 (19) |
|
| 40-49 | 11 (52) |
|
| 50-59 | 5 (24) |
|
| 60-69 | 0 (0) |
|
| ≥70 | 1 (5) |
|
|
| |
| 1-4 | 1 (7) | |
|
| 5-10 | 4 (29) |
|
| 11-15 | 5 (36) |
|
| 16-20 | 3 (21) |
|
| ≥21 | 1 (7) |
aDoctors and developers only (N=14).
Summary of the interviews for each component of the Promoting Action on Research Implementation in the Health Service (PARiHS) framework.
| PARiHS Component | Patients | Physicians | ITa developers | ||||
|
|
|
|
| ||||
|
| Awareness of health blockchain and the concepts of HIEb and PHRc | No | Yes | Yes | |||
|
| Prior experience with HIE | Yes, sharing information (self, parents, children) | Yes, sharing patient information | Yes, developed a related service | |||
|
|
|
|
| ||||
|
| Existing problems in exchanging health information | Was not guided by the hospital | Too much unnecessary information; not all patients/hospitals participate | No problem in the system; the utilization is low | |||
|
| Attitudes about blockchain-based patient-centered HIE | Positive | Somewhat positive | Somewhat positive | |||
|
|
|
|
| ||||
|
| Perceived Risk | Difficult to use | Concerned about security issue; possibility of legal conflicts if all information is shared. Difficult to edit data. Health care professionals would become more conservative during treatment | Possibility of data loss due to users’ inexperience. Data standardization needs to be done at each institution/corporation | |||
|
| Perceived Risk (information safety) | No | Yes | Yes | |||
|
|
|
|
| ||||
|
| Function | Guardian controlling information on behalf of a patient (eg, elderly parent, underage children). | Recruiting patients for clinical trials, receiving only the requested information | Distributed storage of actual data, setting managing entity for metadata | |||
|
| Utilization measures | Ease of use, education for usage, and recommendation by health care professionals | Government leadership at initial stabilization stage (incentive system, etc) | None | |||
| Data exchanging institutions |
| Hospital: Yes; Clinical Research Institute: Yes; | Hospital: Yes; Clinical Research Institute: Yes; | Hospital: Yes; Clinical Research Institute: Yes; | |||
aIT: information technology.
bHIE: hospital information exchange.
cPHR: personal health record.
Prior experience related to the awareness of blockchain, hospital information exchange (HIE), and personal health record (PHR) systems.
| Group | Quotes |
| Patients | “My parents who live in Gangneung were ill, therefore they needed to be taken care of by the family. So, my parents and I transferred the records from a hospital in Gangneung to Bundang [where the participant lives]. I submitted the health records when making an insurance claim. I had to go to the hospital in Gangneung where my parents used to attend just to get the documents I needed. I submitted the documents for the insurance company through fax. It was too far, so I had to take a day off from work. It was too complicated and inconvenient. I had to see the doctor again to get issued documents, and could not get all the necessary documents from one place. I would have not done this if it was not for my parents’ health.” |
| Physicians | “I’m aware of such a service, and I sometimes look up patient information on a health information exchange system. But I don’t use it often.” |
| Developers | “I was involved in the development process. Aside from the development itself, data mapping can proceed only if we understand the business. So, the hardest part was to discuss this with busy doctors and to make them understand it fully.” |
Opinions about existing problems in hospital information exchange (HIE).
| Group | Quotes |
| Patients | “I was told to do so. Administrative procedures at the hospital seem pretty complicated, so I just did what they told me to do without any doubts. I didn’t know about such a great system [HIE service] because no one told me. I would have used it if I knew…” |
| Physicians | “There is too much unnecessary information. The time is limited, and I get confused because some of the information is not what I need for treatment. It would be great if the exam results are related to the actual referral be highlighted.” |
| Developers | “No improvement is necessary in terms of the system. The biggest problem is that its utilization is low. Legal or systematic actions should be taken to standardize data exchange and make it mandatory.” |
Attitudes on blockchain-based patient-centered hospital information exchange (HIE).
| Group | Quotes |
| Patients | “So now I can just use my phone to send my information to wherever I want without having to visit the hospital after going through the consent process. It’s less work for everyone. Not just for hospitals but it’s easier to send documents to insurance companies as well.” |
| Physicians | “I think that the most ideal way is to exchange patient-centered medical information through blockchain.” |
| Developers | “Blockchain is expected to be used a lot in the health care fields. Right now, the PHR [personal health record] only has a simple prescription record and a diagnostic record, but I think it would be helpful for you at the enterprise level if you could obtain a lot of data related to health care.” |
Perceived risks of a blockchain-based hospital information exchange (HIE) system.
| Group | Quotes |
| Patients | “I’m not too concerned about the security. I don’t think it would be a huge risk for me even if my health information is leaked. An old saying goes, ‘the more serious the illness, the more you should tell people’.” |
| Physicians | “Considering the situation in Korea, doctor shopping [the practice of visiting different hospitals to get a diagnosis because they don’t trust a doctor’s diagnosis for their pathological symptoms] would happen more commonly because of the convenient HIE system.” |
| Developers | “If consent is given through apps, there is a risk of health data being leaked when a mobile phone is lost or an app is hacked. In cryptocurrency systems, people cannot withdraw their money if their personal key or mobile phone is lost. The fact that the patient cannot find their own health information should be taken very seriously.” |
Suggested functions of a blockchain-based hospital information exchange (HIE) system.
| Group | Quotes |
| Patients | “Those who really need this service are my parents and they have dementia. It may not always be the right decision to give authorization for sharing information to oneself. Sometimes it’s better to ask for consent from the guardian.” |
| Physicians | “Recruiting clinical trial participants is very difficult, and I think that will be most useful when using blockchain in health care. Recruiting participants appropriate for each stage and conducting follow up are the hardest parts.” |
| Developers | “Patient data will be generated from so many places. Who will be responsible for managing such a vast amount of data? It’ll be most convenient if the data are stored in the central location at the national level, but it’s not possible for the central government to manage PGHD [patient-generated health data]. It’s more efficient to store metadata in the central location, and the data itself should be saved on users’ mobile phone or other storage media.” |