<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v22i8e19657</article-id>
      <article-id pub-id-type="pmid">32795988</article-id>
      <article-id pub-id-type="doi">10.2196/19657</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Developing a Mobile App for Monitoring Medical Record Changes Using Blockchain: Development and Usability Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Kim</surname>
            <given-names>Min-Gul</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Choi</surname>
            <given-names>Chang Min</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Sung</surname>
            <given-names>MinDong</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5217-8877</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Park</surname>
            <given-names>SungJun</given-names>
          </name>
          <degrees>BS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7842-9582</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Jung</surname>
            <given-names>Sungjae</given-names>
          </name>
          <degrees>MS</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8266-0480</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>Eunsol</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3997-4756</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>Jaehoon</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0813-9878</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Park</surname>
            <given-names>Yu Rang</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Department of Biomedical Systems Informatics</institution>
            <institution>Yonsei University College of Medicine</institution>
            <addr-line>50-1 Yonsei-ro</addr-line>
            <addr-line>Seodaemun-gu</addr-line>
            <addr-line>Seoul, 03722</addr-line>
            <country>Republic of Korea</country>
            <phone>82 2 22228 2493</phone>
            <email>yurangpark@yuhs.ac</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4210-2094</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Biomedical Systems Informatics</institution>
        <institution>Yonsei University College of Medicine</institution>
        <addr-line>Seoul</addr-line>
        <country>Republic of Korea</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Medibloc Inc</institution>
        <addr-line>Seoul</addr-line>
        <country>Republic of Korea</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Intermountain Healthcare</institution>
        <addr-line>Salt Lake City, UT</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Department of Biomedical informatics</institution>
        <institution>University of Utah</institution>
        <addr-line>Salt Lake City, UT</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Yu Rang Park <email>yurangpark@yuhs.ac</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>8</month>
        <year>2020</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>14</day>
        <month>8</month>
        <year>2020</year>
      </pub-date>
      <volume>22</volume>
      <issue>8</issue>
      <elocation-id>e19657</elocation-id>
      <history>
        <date date-type="received">
          <day>27</day>
          <month>4</month>
          <year>2020</year>
        </date>
        <date date-type="rev-request">
          <day>12</day>
          <month>6</month>
          <year>2020</year>
        </date>
        <date date-type="rev-recd">
          <day>25</day>
          <month>6</month>
          <year>2020</year>
        </date>
        <date date-type="accepted">
          <day>25</day>
          <month>6</month>
          <year>2020</year>
        </date>
      </history>
      <copyright-statement>©MinDong Sung, SungJun Park, Sungjae Jung, Eunsol Lee, Jaehoon Lee, Yu Rang Park. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 14.08.2020.</copyright-statement>
      <copyright-year>2020</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on http://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="http://www.jmir.org/2020/8/e19657/" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Although we are living in an era of transparency, medical documents are often still difficult to access. Blockchain technology allows records to be both immutable and transparent.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>Using blockchain technology, the aim of this study was to develop a medical document monitoring system that informs patients of changes to their medical documents. We then examined whether patients can effectively verify the monitoring of their primary care clinical medical records in a system based on blockchain technology.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We enrolled participants who visited two primary care clinics in Korea. Three substudies were performed: (1) a survey of the recognition of blockchain medical records changes and the digital literacy of participants; (2) an observational study on participants using the blockchain-based mobile alert app; and (3) a usability survey study. The participants’ medical documents were profiled with HL7 Fast Healthcare Interoperability Resources, hashed, and transacted to the blockchain. The app checked the changes in the documents by querying the blockchain.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A total of 70 participants were enrolled in this study. Considering their recognition of changes to their medical records, participants tended to not allow these changes. Participants also generally expressed a desire for a medical record monitoring system. Concerning digital literacy, most questions were answered with “good,” indicating fair digital literacy. In the second survey, only 44 participants—those who logged into the app more than once and used the app for more than 28 days—were included in the analysis to determine whether they exhibited usage patterns. The app was accessed a mean of 5.1 (SD 2.6) times for 33.6 (SD 10.0) days. The mean System Usability Scale score was 63.21 (SD 25.06), which indicated satisfactory usability.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Patients showed great interest in a blockchain-based system to monitor changes in their medical records. The blockchain system is useful for informing patients of changes in their records via the app without uploading the medical record itself to the network. This ensures the transparency of medical records as well as patient empowerment.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>blockchain</kwd>
        <kwd>monitoring app</kwd>
        <kwd>clinical documents</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>We currently live in an era of data management and often pursue goals of open access and transparency, which means that anyone can usually find information promptly based on their specific needs. One exception to such transparency is medical data [<xref ref-type="bibr" rid="ref1">1</xref>]; although medical records entered by clinicians and stored in clinical information systems legally belong to patients [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref3">3</xref>], many patients realistically find it difficult to gain full and transparent access to their own medical records.</p>
      <p>Patient empowerment has long been emphasized and was recently highlighted in the “2020-2025 Federal Health IT Strategic Plan” from the Office of the National Coordinator for Health Information Technology (ONC). To improve patient empowerment, electronic health records (EHRs) should be shared with patients. However, there are several potential threats to EHRs that could undermine trust in data on these systems. First, records can be altered or lost, either accidentally or intentionally, such as through hacking. Even though redundancy exists in database systems, these redundancies are often obscure to outside observers. Second, data can be fabricated or manipulated by medical staff intent on committing fraud. A possible solution to overcoming these dilemmas is blockchain technology, which uses distributed and cryptographically secure ledgers to ensure immutability, transparency, and decentralization. Bitcoin is a well-known example of blockchain in the field of cryptocurrency [<xref ref-type="bibr" rid="ref4">4</xref>]. Blockchain also provides logs of when data are created, changed, or deleted. Thus, providing all data logs can overcome the two primary threats to EHRs.</p>
      <p>Some previous studies have reported the implementation of blockchain to health care [<xref ref-type="bibr" rid="ref5">5</xref>]. Most of these approaches focus on storing and sharing institutional medical data between EHRs [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref9">9</xref>] and personal health records (PHRs) [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>]. In addition, blockchain has been implemented for sharing and storing clinical trial data [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. Most of these existing works proposed a well-organized architecture or frameworks and a few demonstrated the performance of the prototype developed during the study. However, no study has yet revealed the actual benefits of developing an EHR system using blockchain. We could consider that such a system using blockchain, which features characteristics of transparency and immutability, would be transparent and immutable.</p>
      <p>Therefore, in this study, we used blockchain technology to develop a medical document monitoring system that notifies patients of changes in their medical records. The system was then tested with simulation data and the proof-of-concept study was performed in primary care clinics in Korea.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Design</title>
        <p>This is a proof-of-concept study consisting of three substudies: (1) a survey of the recognition of blockchain medical records changes and the digital literacy of participants; (2) an observational study on participants using the blockchain-based mobile alert app; and (3) a usability survey study. The study was approved by the Institutional Review Board of Yonsei University Health System (Y-2019-0127) and all participants provided informed consent.</p>
        <p>Before proceeding with the design and development of the mobile app, since the EHR systems used in each hospital setting differ, the documents used in the EHR systems were profiled using HL7 Fast Healthcare Interoperability Resources (FHIR; see <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>) [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. Although it is reasonable that patients are notified of any changes in medical records, patients might be overwhelmed by too many notifications whenever any change occurs. Moreover, to improve the usability of the mobile app, changes should be summarized. Therefore, medical documents were divided into three types according to their importance and impact, and the mobile app was designed so that patients are notified of only high-risk changes in documents according to the following three risk levels: risk 1, medical information and other critical items that should not be changed; risk 2, medical information and other items that are allowed to be changed; and risk 3, nonmedical information. These risk levels were also considered in the profiles created.</p>
        <p>The mobile app used in this study leverages the blockchain network MediBloc Panacea [<xref ref-type="bibr" rid="ref17">17</xref>] that was developed based on the Tendermint blockchain [<xref ref-type="bibr" rid="ref18">18</xref>]. The blockchain uses the delegated proof-of-stake method implemented by the practical Byzantine fault tolerance algorithm to create blocks. In this system, “delegated” refers to delegated nodes that perform and validate transactions and blocks. Validators are selected through voting. Normally, one block is generated per second, and all transaction history transmitted over the network is stored in the generated block. Further, similar to other blockchains, once created, blocks cannot be reversed. We used four different properties in the blockchain transaction: (1) writer of the transaction, which can only be specific clinics; (2) topic that is assigned per individual patient; (3) key; and (4) value. Key and value have the following five attributes: (1) hash value for medical documents, (2) document URL for the FHIR profile in which the document was transformed, (3) hash value before the medical document was changed, (4) risk and number of documents with changes, and (5) date to represent when the document was created. As soon as the document is created, the health information system spontaneously hashes and transacts the metadata of the document to the blockchain network (<xref rid="figure1" ref-type="fig">Figure 1</xref>). The mobile app provides users with logs of changes in medical records. The app has been available on the Google Play Store [<xref ref-type="bibr" rid="ref19">19</xref>] since October 23, 2019.</p>
        <p/>
        <p>Before the proof-of-concept study was deployed, we simulated the app to evaluate how it captures fake medical records caused by fraudulent actions. We created five fake medical documents for the purpose of simulation. All except for one dataset were assumed to have changes in the documents. The risk levels of the changes were set differently for each dataset. We transacted the datasets and checked how the mobile app worked.</p>
        <p>The study was conducted at two primary care clinics specializing in pediatrics in Korea. Only outpatients of these two clinics were enrolled in the study. Anyone who visited the selected clinics was eligible to participate in the study. Because young patients were not interested in their own medical records, whereas their guardians were more interested, the guardians of patients enrolled in the study on their behalf.</p>
        <p>When patients launch the mobile app from their devices, the user is authenticated according to a username and password. After login, the patient can see their own profile and events, which include when the records were created as well as which and how many items at high risk were changed. This information was obtained by querying blockchain using Owner and Topic values that were stored in the backend server of the mobile app.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Structure of the medical document monitoring system.</p>
          </caption>
          <graphic xlink:href="jmir_v22i8e19657_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Substudies</title>
        <p>To investigate participants’ level of recognition of blockchain, medical records changes, and their digital literacy, questionnaires were completed by all participants (<xref rid="figure2" ref-type="fig">Figure 2</xref>). The primary survey consisted of items regarding the recognition of blockchain, thoughts and experiences of changes in medical records, and digital literacy. There were six questions that measured blockchain recognition; these were based on virtual currency questions from a 2014 Survey of Consumer Payment Choice [<xref ref-type="bibr" rid="ref20">20</xref>]. The second part of the questionnaires consisted of four questions. The first two questions were related to the recognition of medical record changes and the need for a monitoring system for medical record changes. These two questions were answered on a 5-point response scale. The other two questions addressed the participants’ experience of medical record changes. The third part, digital literacy, consisted of 10 questions answered on a 5-point response scale. These questions were taken from other digital literacy questions [<xref ref-type="bibr" rid="ref21">21</xref>], modified for the mobile app, and condensed to 10 questions. A higher score represents a higher level of digital health literacy, except in the case of two questions. The questionnaire ended with demographic characteristics (age, sex, and occupation). All 5-point questions were answered, with responses ranging from very negative to very positive (ranging between 1 and 5).</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Flow diagram of study participants.</p>
          </caption>
          <graphic xlink:href="jmir_v22i8e19657_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>Usage patterns of the app were measured by the number of logins, duration that indicated the difference in days between the first and the last logins, and an event log, which indicated how many items were changed and how important they were. These usage patterns were observed in participants who logged in more than once and for a duration of more than 28 days.</p>
        <p>After 28 days of using the app, participants were invited via the app to take part in the secondary survey, which included a System Usability Scale (SUS) survey. For the evaluation of learnability and usability, we used the modified SUS, a reliable, low-cost usability scale that can be used for global assessments of systems usability (see <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>) [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. Bangor et al [<xref ref-type="bibr" rid="ref23">23</xref>] described the adjective ratings associated with SUS scores as follows: worst possible (mean SUS score 25), poor (39.17), satisfactory (52.01), good (72.75), excellent (85.58), and best possible (100).</p>
      </sec>
      <sec>
        <title>Statistical Analysis</title>
        <p>Categorical variables are presented as numbers and percentages and were compared using the Chi-square test and the Fisher exact test. Continuous variables are expressed as mean (SD) and were compared using the Student unpaired <italic>t</italic>-test, analysis of variance, Wilcoxon signed-rank test, or Mann-Whitney <italic>U</italic> test as appropriate. Surveys answered by a Likert-type scale and scores are expressed as the mode as well as numbers and percentages. All statistical analyses were performed using R version 3.6.1 (R Foundation for Statistical Computing, Vienna, Austria) and 2-tailed tests. Results with <italic>P</italic>&#60;.05 were considered to be statistically significant.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>Before the proof-of-concept study was performed, metadata from the 5 original documents and the 4 changed documents were transacted into the blockchain. The simulation metadata and transaction metadata are described in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>. App screenshots are provided in <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>.</p>
      <p>A total of 70 patients were enrolled in this study. Patient characteristics are shown in <xref ref-type="table" rid="table1">Table 1</xref>. There were more female patients, and the majority of patients were in their thirties. Thirty-two participants were guardians of the patients, and the occupation of nearly half of the participants was housework or parenting (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
      <table-wrap position="float" id="table1">
        <label>Table 1</label>
        <caption>
          <p>Demographic characteristics of participants.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="30"/>
          <col width="290"/>
          <col width="0"/>
          <col width="190"/>
          <col width="0"/>
          <col width="190"/>
          <col width="0"/>
          <col width="160"/>
          <col width="0"/>
          <col width="140"/>
          <thead>
            <tr valign="top">
              <td colspan="2">Characteristic</td>
              <td colspan="2">Hospital A (n=40)</td>
              <td colspan="2">Hospital B (n=30)</td>
              <td colspan="2">Total (N=70)</td>
              <td colspan="2"><italic>P</italic> value</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td colspan="2">
                <bold>Sex, n (%)</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">.29</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Male</td>
              <td colspan="2">9 (23)</td>
              <td colspan="2">3 (10)</td>
              <td colspan="2">12 (17)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Female</td>
              <td colspan="2">31 (77)</td>
              <td colspan="2">27 (90)</td>
              <td colspan="2">58 (83)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td colspan="2">
                <bold>Respondent, n (%)</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">.47</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Guardian</td>
              <td colspan="2">19 (47)</td>
              <td colspan="2">18 (60)</td>
              <td colspan="2">37 (53)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Patient</td>
              <td colspan="2">21 (53)</td>
              <td colspan="2">12 (40)</td>
              <td colspan="2">33 (47)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td colspan="2">
                <bold>Age groups (years), n (%)</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">.40</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">19-20</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">1 (3)</td>
              <td colspan="2">1 (1)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">20-29</td>
              <td colspan="2">5 (12)</td>
              <td colspan="2">1 (3)</td>
              <td colspan="2">6 (9)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">30-39</td>
              <td colspan="2">22 (55)</td>
              <td colspan="2">17 (57)</td>
              <td colspan="2">39 (56)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">40-49</td>
              <td colspan="2">12 (30)</td>
              <td colspan="2">10 (33)</td>
              <td colspan="2">22 (31)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">50-59</td>
              <td colspan="2">1 (3)</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">1 (1)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">&#62;60</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">1 (3)</td>
              <td colspan="2">1 (1)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td colspan="2">
                <bold>Occupation, n (%)</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">.24</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Information technology</td>
              <td colspan="2">1 (3)</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">1 (1)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Office job</td>
              <td colspan="2">5 (12)</td>
              <td colspan="2">5 (17)</td>
              <td colspan="2">10 (14)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Management</td>
              <td colspan="2">2 (5)</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">2 (3)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Professional</td>
              <td colspan="2">4 (10)</td>
              <td colspan="2">3 (10)</td>
              <td colspan="2">7 (10)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Housework/parenting</td>
              <td colspan="2">13 (32)</td>
              <td colspan="2">17 (57)</td>
              <td colspan="2">30 (43)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Sales</td>
              <td colspan="2">2 (5)</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">2 (3)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Student</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">1 (3)</td>
              <td colspan="2">1 (1)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Unemployed</td>
              <td colspan="2">2 (5)</td>
              <td colspan="2">1 (3)</td>
              <td colspan="2">3 (4)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Other</td>
              <td colspan="2">11 (28)</td>
              <td colspan="2">3 (10)</td>
              <td colspan="2">14 (20)</td>
              <td>
                <break/>
              </td>
            </tr>
          </tbody>
        </table>
      </table-wrap>
      <p>Recognition of blockchain concepts differed depending on the type of question (ie, whether it refers to bitcoin or blockchain). The majority of participants stated that they were aware of bitcoin, whereas less than half were aware of blockchain. Similarly, respondents were more familiar with bitcoin than with blockchain. However, respondents had less trust in bitcoin than in blockchain. In terms of the recognition of medical record changes, participants tended to not allow changes in their medical records. Subsequently, participants stated a need for a medical record monitoring system. There was only one participant who reported having experienced medical document changes in the first questionnaire. The medical records were changed to correct the wrong information entered previously. In terms of digital literacy, most of the questions were answered as “good” digital literacy (<xref ref-type="table" rid="table2">Table 2</xref>).</p>
      <table-wrap position="float" id="table2">
        <label>Table 2</label>
        <caption>
          <p>Distribution, n (%), of primary survey responses and modes of Likert scale scores (N=70).</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="30"/>
          <col width="220"/>
          <col width="0"/>
          <col width="140"/>
          <col width="0"/>
          <col width="140"/>
          <col width="0"/>
          <col width="100"/>
          <col width="0"/>
          <col width="120"/>
          <col width="0"/>
          <col width="120"/>
          <col width="0"/>
          <col width="130"/>
          <thead>
            <tr valign="top">
              <td colspan="2">Survey question</td>
              <td colspan="2">1</td>
              <td colspan="2">2</td>
              <td colspan="2">3</td>
              <td colspan="2">4</td>
              <td colspan="2">5</td>
              <td colspan="2">Mode</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td colspan="2">
                <bold>Awareness of blockchain</bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Have you heard of bitcoin?</td>
              <td colspan="2">63 (90)</td>
              <td colspan="2">7 (10)</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">0 (0)</td>
              <td>1</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">How familiar are you with bitcoin and how it works?</td>
              <td colspan="2">17 (24)</td>
              <td colspan="2">21 (30)</td>
              <td colspan="2">24 (34)</td>
              <td colspan="2">6 (8.6)</td>
              <td colspan="2">2 (2.9)</td>
              <td>3</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">How much do you trust bitcoin?</td>
              <td colspan="2">10 (14)</td>
              <td colspan="2">29 (41)</td>
              <td colspan="2">26 (37)</td>
              <td colspan="2">3 (4.3)</td>
              <td colspan="2">2 (2.9)</td>
              <td>2</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Have you heard of blockchain?</td>
              <td colspan="2">32 (46)</td>
              <td colspan="2">38 (54)</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">0 (0)</td>
              <td>2</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">How familiar are you with blockchain and how it works?</td>
              <td colspan="2">37 (53)</td>
              <td colspan="2">14 (20)</td>
              <td colspan="2">10 (14)</td>
              <td colspan="2">7 (10.0)</td>
              <td colspan="2">2 (2.9)</td>
              <td>1</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">How much do you trust blockchain?</td>
              <td colspan="2">19 (27)</td>
              <td colspan="2">11 (16)</td>
              <td colspan="2">29 (41)</td>
              <td colspan="2">7 (10.0)</td>
              <td colspan="2">4 (5.7)</td>
              <td>3</td>
            </tr>
            <tr valign="top">
              <td colspan="3">
                <bold>Recognition of medical document changes</bold>
              </td>
              <td colspan="1">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Do you think changing medical records should be allowed?</td>
              <td colspan="2">42 (60) </td>
              <td colspan="2">7 (10) </td>
              <td colspan="2"> 11 (16) </td>
              <td colspan="2">9 (13) </td>
              <td colspan="2">1 (1) </td>
              <td>1</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Do you think we need a medical records falsification monitoring system?</td>
              <td colspan="2">1 (1) </td>
              <td colspan="2">2 (3) </td>
              <td colspan="2">6 (9) </td>
              <td colspan="2">18 (26) </td>
              <td colspan="2">43 (61) </td>
              <td>5</td>
            </tr>
            <tr valign="top">
              <td colspan="2">
                <bold>Digital literacy<sup>a</sup></bold>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
              <td colspan="2">
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Can you use the internet?</td>
              <td colspan="2">1 (1)</td>
              <td colspan="2">5 (7)</td>
              <td colspan="2">18 (26)</td>
              <td colspan="2">29 (41)</td>
              <td colspan="2">17 (24)</td>
              <td>4</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Can you use digital technology?</td>
              <td colspan="2">2 (3)</td>
              <td colspan="2">8 (11)</td>
              <td colspan="2">29 (41)</td>
              <td colspan="2">20 (29)</td>
              <td colspan="2">11 (16)</td>
              <td>3</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Can you use the app well on your phone?</td>
              <td colspan="2">1 (1)</td>
              <td colspan="2">3 (4)</td>
              <td colspan="2">21 (30)</td>
              <td colspan="2">22 (31)</td>
              <td colspan="2">23 (33)</td>
              <td>5</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Can you use the camera well on your phone?</td>
              <td colspan="2">1 (1)</td>
              <td colspan="2">1 (1)</td>
              <td colspan="2">6 (9)</td>
              <td colspan="2">15 (21)</td>
              <td colspan="2">47 (67)</td>
              <td>5</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Can you download and install apps from your phone?</td>
              <td colspan="2">1 (1)</td>
              <td colspan="2">1 (1)</td>
              <td colspan="2">9 (13)</td>
              <td colspan="2">16 (23)</td>
              <td colspan="2">43 (61)</td>
              <td>5</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">I feel comfortable using digital technology</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">3 (4)</td>
              <td colspan="2">10 (14)</td>
              <td colspan="2">30 (43)</td>
              <td colspan="2">27 (39)</td>
              <td>4</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">I am active in learning digital technology</td>
              <td colspan="2">3 (4)</td>
              <td colspan="2">13 (19)</td>
              <td colspan="2">21 (30)</td>
              <td colspan="2">24 (34)</td>
              <td colspan="2">9 (13)</td>
              <td>4</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">I feel threatened when others talk about digital technology<sup>b</sup></td>
              <td colspan="2">18 (26)</td>
              <td colspan="2">30 (43)</td>
              <td colspan="2">16 (23)</td>
              <td colspan="2">4 (6)</td>
              <td colspan="2">2 (3)</td>
              <td>2</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">I feel behind other people my age in terms of digital technology<sup>b</sup></td>
              <td colspan="2">6 (9)</td>
              <td colspan="2">23 (33)</td>
              <td colspan="2">32 (46)</td>
              <td colspan="2">7 (10)</td>
              <td colspan="2">2 (3)</td>
              <td>3</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">I believe that it is important for me to learn how to use digital technology</td>
              <td colspan="2">0 (0)</td>
              <td colspan="2">3 (4)</td>
              <td colspan="2">17 (24)</td>
              <td colspan="2">20 (29)</td>
              <td colspan="2">30 (43)</td>
              <td>5</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table2fn1">
            <p><sup>a</sup>A high score represents a high level of digital literacy, unless otherwise indicated.</p>
          </fn>
          <fn id="table2fn2">
            <p><sup>b</sup>A low score represents a high level of digital health literacy.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <p>Only 44 participants were included in the analysis of usage patterns and the secondary survey. During the study period, the app had been accessed a mean of approximately 5 times. The duration of app use, which was indicated by the difference between the first login and the last login, was approximately 34 days. However, there were no medical document changes during this period. The mean SUS score indicated “satisfactory” usability. The number of logins and the duration were significantly higher in hospital A than in hospital B. Moreover, the duration was significantly different according to occupations. There were no document changes during the study period (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
      <table-wrap position="float" id="table3">
        <label>Table 3</label>
        <caption>
          <p>Usage patterns and System Usability Scale (SUS) scores of app users.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="30"/>
          <col width="210"/>
          <col width="210"/>
          <col width="210"/>
          <col width="170"/>
          <col width="170"/>
          <thead>
            <tr valign="top">
              <td colspan="2">Group</td>
              <td>Participants, n (%)</td>
              <td>Number  <break/>  
                of logins, mean (SD)</td>
              <td>Duration  <break/>  
                (days), mean (SD)</td>
              <td>SUS score, mean (SD)</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td colspan="2">Total</td>
              <td>44 (100)</td>
              <td>5.10 (2.60)</td>
              <td>33.60 (10.00)</td>
              <td>64.60 (16.00)</td>
            </tr>
            <tr valign="top">
              <td colspan="2">
                <bold>Hospital</bold>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Hospital A</td>
              <td>24 (55)</td>
              <td>5.88 (2.71)</td>
              <td>34.63 (11.14)</td>
              <td>67.50 (16.32)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Hospital B</td>
              <td>20 (45)</td>
              <td>4.10 (2.07)</td>
              <td>32.34 (8.55)</td>
              <td>61.12 (15.36)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td><italic>P</italic> value<sup>a</sup></td>
              <td>
                <break/>
              </td>
              <td>.02</td>
              <td>.05</td>
              <td>.16</td>
            </tr>
            <tr valign="top">
              <td colspan="2">
                <bold>Gender</bold>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Male</td>
              <td>7 (16)</td>
              <td>4.57 (2.94)</td>
              <td>31.12 (3.09)</td>
              <td>68.21 (19.08)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Female</td>
              <td>37 (84)</td>
              <td>5.16 (2.53)</td>
              <td>34.06 (10.8)</td>
              <td>63.92 (15.6)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td><italic>P</italic> value</td>
              <td>
                <break/>
              </td>
              <td>.45</td>
              <td>.98</td>
              <td>.54</td>
            </tr>
            <tr valign="top">
              <td colspan="2">
                <bold>Age group (years)</bold>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>20-30</td>
              <td>6 (14)</td>
              <td>6.50 (2.88)</td>
              <td>36.95 (13.98)</td>
              <td>67.08 (15.61)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>30-40</td>
              <td>23 (52)</td>
              <td>4.87 (2.85)</td>
              <td>34.52 (11.21)</td>
              <td>63.48 (17.4)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>40-50</td>
              <td>14 (32)</td>
              <td>4.86 (1.96)</td>
              <td>30.86 (5.2)</td>
              <td>65.54 (15.42)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>50-60<sup>b</sup></td>
              <td>1 (2)</td>
              <td>4.00</td>
              <td>30.09</td>
              <td>62.50</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td><italic>P</italic> value</td>
              <td>
                <break/>
              </td>
              <td>.49</td>
              <td>.38</td>
              <td>.90</td>
            </tr>
            <tr valign="top">
              <td colspan="2">
                <bold>Respondent</bold>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Guardian</td>
              <td>27 (61)</td>
              <td>4.70 (2.61)</td>
              <td>35.29 (12.33)</td>
              <td>67.13 (17.29)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Patient</td>
              <td>17 (39)</td>
              <td>5.65 (2.47)</td>
              <td>30.89 (3.03)</td>
              <td>60.59 (13.3)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td><italic>P</italic> value</td>
              <td>
                <break/>
              </td>
              <td>.15</td>
              <td>.57</td>
              <td>.19<sup>c</sup></td>
            </tr>
            <tr valign="top">
              <td colspan="2">
                <bold>Occupation</bold>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Housework/parenting</td>
              <td>23(52)</td>
              <td>4.96 (2.69)</td>
              <td>31.44 (7.84)</td>
              <td>63.15 (16.52)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Professional</td>
              <td>4 (9)</td>
              <td>4.25 (2.22)</td>
              <td>29.44 (1.17)</td>
              <td>54.38 (2.39)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Sales</td>
              <td>2 (5)</td>
              <td>3.00 (1.41)</td>
              <td>33.46 (5.01)</td>
              <td>57.50 (21.21)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Office job</td>
              <td>7 (16)</td>
              <td>5.57 (2.51)</td>
              <td>41.30 (14.53)</td>
              <td>74.29 (19.02)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Unemployed</td>
              <td>2 (5)</td>
              <td>6.00 (4.24)</td>
              <td>30.04 (0.10)</td>
              <td>72.50 (3.54)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Other</td>
              <td>6 (14)</td>
              <td>5.83 (2.64)</td>
              <td>36.82 (13.95)</td>
              <td>65.42 (14.44)</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td><italic>P</italic> value</td>
              <td>
                <break/>
              </td>
              <td>.70</td>
              <td>.03</td>
              <td>.40<sup>d</sup></td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table3fn1">
            <p><sup>a</sup>Mann-Whitney <italic>U</italic> test and Kruskal-Wallis rank-sum test were used to calculate <italic>P</italic> values between two groups and three groups, respectively, unless otherwise indicated.</p>
          </fn>
          <fn id="table3fn2">
            <p><sup>b</sup>SD not available since there is only one value.</p>
          </fn>
          <fn id="table3fn3">
            <p><sup>c</sup>Calculated using the <italic>t</italic> test.</p>
          </fn>
          <fn id="table3fn4">
            <p><sup>d</sup>Calculated using analysis of variance.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This proof-of-concept study applied a blockchain-based medical document monitoring system in two primary care clinics. Although there was a lack of recognition of the concept of blockchain (compared with bitcoin), participants’ trust level in blockchain was higher than that in bitcoin. Moreover, although there were few people who had experienced changes in their medical documents, the participants considered that medical records should not be changed, and therefore that this monitoring system is necessary.</p>
        <p>There have been some blockchain-based implementations for managing medical records. Ariel C Ekblaw designed MedRec—a decentralized record management system for EHRs—and implemented the pilot system in the Beth Israel Deaconess Medical Center [<xref ref-type="bibr" rid="ref24">24</xref>]. Zhang et al [<xref ref-type="bibr" rid="ref9">9</xref>] designed the architecture of DApp, named FHIRChain, based on 5 key requirements provided by the ONC interoperability roadmap and demonstrated the prototype. Roehrs et al [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>] designed a distributed architecture model to integrate PHRs, which was called OmniPHR, and showed the performance of the prototypes. However, most of these models focus on data storage and sharing, whereas our study focused on monitoring changes in medical documents themselves.</p>
        <p>There are some concerns about creating blockchain-based EHR systems because sensitive data—such as medical records—are protected by the General Data Protection Regulation legislation [<xref ref-type="bibr" rid="ref25">25</xref>], which ensures that full control of data are given to data owners. Four rule-of-thumb principles that entrepreneurs and innovators can consider when designing blockchain-based apps have been proposed. Among these principles, the second states that personal data should be avoided on blockchain using data obfuscation, encryption, and aggregation techniques [<xref ref-type="bibr" rid="ref26">26</xref>]. To comply with this principle, we used the hash value of the document using SHA-256—which is considered to be one of the most popular hashing algorithms in the world—to make it difficult to reverse the original.</p>
        <p>Some blockchain systems ensure privacy and confidentiality using zero knowledge proofs (ZKPs) such as Zerocash [<xref ref-type="bibr" rid="ref27">27</xref>]. ZKPs allow data to be verified without revealing the data. Although the app does not have access to the exact medical document contents, it can show whether the medical document has been changed or not. Our system therefore satisfies the concept of ZKPs because the app only identifies whether the item was changed or not, without knowledge of the item’s content.</p>
        <p>Medical records may be often falsified to hide medical accidents [<xref ref-type="bibr" rid="ref28">28</xref>] or to claim insurance by fraud [<xref ref-type="bibr" rid="ref29">29</xref>]. In Korea, the Medical Service Act states that “Where any medical personnel or the founder of a medical institution makes an addition or revision to electronic medical records, he/she shall separately keep the access logs thereof, as prescribed by Ordinance of the Ministry of Health and Welfare” [<xref ref-type="bibr" rid="ref30">30</xref>]. This act was implemented in September 2018 and the situation is likely to be similar in other countries. Most of the tertiary hospitals in Korea have well-integrated EHR systems that can manage changes in medical documents. However, primary care clinics use vendor-dependent EHR systems, which are not equipped to track changes in documents. Therefore, we chose a primary care clinic to trace changes in records.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>This study has several limitations that should be noted. All logs in the system indicate that there were no changes to medical documents during the study period owing to the short duration and small sample size. In fact, there were not many documents in primary clinics to work with compared with those available at tertiary hospitals; the fewer the documents in primary clinics, the fewer the changes in documents. Nevertheless, this study demonstrated that the app functions as designed when using simulation data. Additionally, the selection of the hospitals was biased toward pediatric clinics. Finally, the SUS scores in this study were low. Because there were no changes in medical documents, the participants barely had a chance to realize the value of the app.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This study introduced an app that notifies patients of changes in medical records using blockchain technology. Blockchain helps the app to inform patients of changes in their documents without uploading the medical record itself to the network. Therefore, blockchain can help ensure the transparency of medical records and advance patient empowerment.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>FHIR Profiles of EHR Data.</p>
        <media xlink:href="jmir_v22i8e19657_app1.png" xlink:title="PNG File , 258 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Modified System Usability Scale (SUS).</p>
        <media xlink:href="jmir_v22i8e19657_app2.docx" xlink:title="DOCX File , 14 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Transaction metadata with simulation data.</p>
        <media xlink:href="jmir_v22i8e19657_app3.docx" xlink:title="DOCX File , 13 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>Screenshots of medical document changes app tested with simulation data.</p>
        <media xlink:href="jmir_v22i8e19657_app4.docx" xlink:title="DOCX File , 115 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">FHIR</term>
          <def>
            <p>Fast Healthcare Interoperability Resources</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">ONC</term>
          <def>
            <p>Office of the National Coordinator for Health Information Technology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">PHR</term>
          <def>
            <p>personal health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">SUS</term>
          <def>
            <p>System Usability Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">ZKP</term>
          <def>
            <p>zero knowledge proof</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This study was supported by the Foundational Technology Development Program (NRF2019M3E5D406468212) of the Ministry of Science and ICT, Republic of Korea, and a grant of the Korea Health Technology Research and Development Project through the Korea Health Industry Development Institute (KHIDI), funded by the Ministry of Health &#38; Welfare, Republic of Korea (KHIDIHI19C1015010020).</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>MS, EL, and YP all had a role in the study concept and design. MS, SP, and SJ had a role in acquisition, analysis, or interpretation of data. MS, EL, JL, and YP drafted the manuscript, and MS, EL, JL, and YP critically revised the manuscript. YP and EL obtained funding. SP and SJ provided technical support. All authors had access to the data and together had the final responsibility regarding the decision to submit for publication.</p>
      </fn>
      <fn fn-type="conflict">
        <p>EL is the employer of Medibloc, Inc, and SJ is an employee of Medibloc, Inc. JL provided informatics consultation services to the Yonsei University School of Medicine and MediBloc Inc since 2018.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Scheurer</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Hospitalists Should Embrace Advances, Transparency in Health Record Technology</article-title>
          <source>The Hospitalist</source>
          <year>2015</year>
          <month>07</month>
          <access-date>2020-07-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.the-hospitalist.org/hospitalist/article/122299/hospitalists-should-embrace-advances-transparency-health-record">https://www.the-hospitalist.org/hospitalist/article/122299/hospitalists-should-embrace-advances-transparency-health-record</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="web">
          <article-title>The Health Insurance Portability and Accountability Act (HIPAA)</article-title>
          <source>United States Department of Labor</source>
          <access-date>2020-07-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://purl.fdlp.gov/GPO/gpo10291">http://purl.fdlp.gov/GPO/gpo10291</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <article-title>Overview of the national laws on electronic health records in the EU Member States and their interaction with the provision of cross-border eHealth services: Final report and recommendations</article-title>
          <source>Health Programme of the European Union</source>
          <access-date>2020-07-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ec.europa.eu/health/sites/health/files/ehealth/docs/laws_report_recommendations_en.pdf">https://ec.europa.eu/health/sites/health/files/ehealth/docs/laws_report_recommendations_en.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wright</surname>
              <given-names>CS</given-names>
            </name>
          </person-group>
          <article-title>Bitcoin: A Peer-to-Peer Electronic Cash System</article-title>
          <source>SSRN</source>
          <year>2019</year>
          <month>10</month>
          <day>19</day>
          <fpage>1</fpage>
          <lpage>10</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ssrn.com/abstract=3440802"/>
          </comment>
          <pub-id pub-id-type="doi">10.2139/ssrn.3440802</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hussien</surname>
              <given-names>HM</given-names>
            </name>
            <name name-style="western">
              <surname>Yasin</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Udzir</surname>
              <given-names>SNI</given-names>
            </name>
            <name name-style="western">
              <surname>Zaidan</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Zaidan</surname>
              <given-names>BB</given-names>
            </name>
          </person-group>
          <article-title>A Systematic Review for Enabling of Develop a Blockchain Technology in Healthcare Application: Taxonomy, Substantially Analysis, Motivations, Challenges, Recommendations and Future Direction</article-title>
          <source>J Med Syst</source>
          <year>2019</year>
          <month>09</month>
          <day>14</day>
          <volume>43</volume>
          <issue>10</issue>
          <fpage>320</fpage>
          <pub-id pub-id-type="doi">10.1007/s10916-019-1445-8</pub-id>
          <pub-id pub-id-type="medline">31522262</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-019-1445-8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>A framework for secure and decentralized sharing of medical imaging data via blockchain consensus</article-title>
          <source>Health Informatics J</source>
          <year>2019</year>
          <month>12</month>
          <day>25</day>
          <volume>25</volume>
          <issue>4</issue>
          <fpage>1398</fpage>
          <lpage>1411</lpage>
          <pub-id pub-id-type="doi">10.1177/1460458218769699</pub-id>
          <pub-id pub-id-type="medline">29692204</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McFarlane</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Beer</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Prendergast</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Patientory: A Healthcare Peer-to-Peer EMR Storage Network v1</article-title>
          <source>Entrust Inc</source>
          <year>2017</year>
          <month>04</month>
          <access-date>2020-07-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://patientory.com/wp-content/uploads/2017/04/Final-Patientory_Whitepaper.pdf">https://patientory.com/wp-content/uploads/2017/04/Final-Patientory_Whitepaper.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Tao</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Blockchain-Based Data Preservation System for Medical Data</article-title>
          <source>J Med Syst</source>
          <year>2018</year>
          <month>06</month>
          <day>28</day>
          <volume>42</volume>
          <issue>8</issue>
          <fpage>141</fpage>
          <lpage>112</lpage>
          <pub-id pub-id-type="doi">10.1007/s10916-018-0997-3</pub-id>
          <pub-id pub-id-type="medline">29956058</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-018-0997-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>White</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Schmidt</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Lenz</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenbloom</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>FHIRChain: Applying Blockchain to Securely and Scalably Share Clinical Data</article-title>
          <source>Comput Struct Biotechnol J</source>
          <year>2018</year>
          <volume>16</volume>
          <fpage>267</fpage>
          <lpage>278</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2001-0370(18)30037-0"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.csbj.2018.07.004</pub-id>
          <pub-id pub-id-type="medline">30108685</pub-id>
          <pub-id pub-id-type="pii">S2001-0370(18)30037-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC6082774</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rahmadika</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rhee</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Blockchain technology for providing an architecture model of decentralized personal health information</article-title>
          <source>Int J Engin Bus Manage</source>
          <year>2018</year>
          <month>08</month>
          <volume>10</volume>
          <fpage>184797901879058</fpage>
          <pub-id pub-id-type="doi">10.1177/1847979018790589</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Roehrs</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>da Costa</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>da Rosa Righi</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>OmniPHR: A distributed architecture model to integrate personal health records</article-title>
          <source>J Biomed Inform</source>
          <year>2017</year>
          <month>07</month>
          <volume>71</volume>
          <fpage>70</fpage>
          <lpage>81</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(17)30108-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2017.05.012</pub-id>
          <pub-id pub-id-type="medline">28545835</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(17)30108-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Roehrs</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>da Costa</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>da Rosa Righi</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>da Silva</surname>
              <given-names>VF</given-names>
            </name>
            <name name-style="western">
              <surname>Goldim</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Schmidt</surname>
              <given-names>DC</given-names>
            </name>
          </person-group>
          <article-title>Analyzing the performance of a blockchain-based personal health record implementation</article-title>
          <source>J Biomed Inform</source>
          <year>2019</year>
          <month>04</month>
          <volume>92</volume>
          <fpage>103140</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(19)30058-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2019.103140</pub-id>
          <pub-id pub-id-type="medline">30844481</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(19)30058-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Maslove</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>Klein</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Brohman</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Using Blockchain Technology to Manage Clinical Trials Data: A Proof-of-Concept Study</article-title>
          <source>JMIR Med Inform</source>
          <year>2018</year>
          <month>12</month>
          <day>21</day>
          <volume>6</volume>
          <issue>4</issue>
          <fpage>e11949</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2018/4/e11949/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/11949</pub-id>
          <pub-id pub-id-type="medline">30578196</pub-id>
          <pub-id pub-id-type="pii">v6i4e11949</pub-id>
          <pub-id pub-id-type="pmcid">PMC6320404</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>DR</given-names>
            </name>
            <name name-style="western">
              <surname>Bhattacharya</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Butte</surname>
              <given-names>AJ</given-names>
            </name>
          </person-group>
          <article-title>Prototype of running clinical trials in an untrustworthy environment using blockchain</article-title>
          <source>Nat Commun</source>
          <year>2019</year>
          <month>02</month>
          <day>22</day>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>917</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/30796226"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41467-019-08874-y</pub-id>
          <pub-id pub-id-type="medline">30796226</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41467-019-08874-y</pub-id>
          <pub-id pub-id-type="pmcid">PMC6384889</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bender</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sartipi</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>HL7 FHIR: An Agile and RESTful approach to healthcare information exchange</article-title>
          <year>2013</year>
          <conf-name>Proceedings of the 26th IEEE international symposium on computer-based medical systems</conf-name>
          <conf-date>June 20-22, 2013</conf-date>
          <conf-loc>Porto, Portugal</conf-loc>
          <publisher-name>IEEE</publisher-name>
          <pub-id pub-id-type="doi">10.1109/cbms.2013.6627810</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>YR</given-names>
            </name>
          </person-group>
          <article-title>Hospital Information System - MediBloc</article-title>
          <source>Simplifier.Net</source>
          <access-date>2020-07-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://simplifier.net/hospitalinformationsystem-medibloc2">https://simplifier.net/hospitalinformationsystem-medibloc2</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
          <article-title>MediBloc Panacea-Core</article-title>
          <source>GitHub</source>
          <access-date>2020-07-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/medibloc/panacea-core">https://github.com/medibloc/panacea-core</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <article-title>Tendermint Core (BFT Consensus) in Go</article-title>
          <source>GitHub</source>
          <access-date>2020-07-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/tendermint/tendermint">https://github.com/tendermint/tendermint</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
          <article-title>Medical record change log app</article-title>
          <source>Google Play Store</source>
          <access-date>2020-07-25</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://play.google.com/store/apps/details?id=org.medibloc.panacea">https://play.google.com/store/apps/details?id=org.medibloc.panacea</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schuh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Shy</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>US consumers adoption and use of Bitcoin and other virtual currencies</article-title>
          <year>2016</year>
          <month>04</month>
          <day>21</day>
          <conf-name>DNB Payments Conference 2016 - Retail Payments: Mapping Out The Road Ahead</conf-name>
          <conf-date>April 21-22, 2016</conf-date>
          <conf-loc>Amsterdam</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Son</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Robb</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Charismiadji</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Computer literacy and competency: a survey of Indonesian teachers of English as a foreign language</article-title>
          <source>Comput Lang Learn Electron J</source>
          <year>2011</year>
          <volume>12</volume>
          <issue>1</issue>
          <fpage>26</fpage>
          <lpage>42</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brooke</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Jordan</surname>
              <given-names>PW</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>McClelland</surname>
              <given-names>IL</given-names>
            </name>
            <name name-style="western">
              <surname>Weerdmeester</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>SUS-A quick and dirty usability scale</article-title>
          <source>Usability Evaluation in Industry</source>
          <year>1996</year>
          <publisher-loc>Boca Raton, FL</publisher-loc>
          <publisher-name>CRC Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bangor</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kortum</surname>
              <given-names>PT</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>JT</given-names>
            </name>
          </person-group>
          <article-title>An Empirical Evaluation of the System Usability Scale</article-title>
          <source>Int J Hum-Comput Interact</source>
          <year>2008</year>
          <month>07</month>
          <day>30</day>
          <volume>24</volume>
          <issue>6</issue>
          <fpage>574</fpage>
          <lpage>594</lpage>
          <pub-id pub-id-type="doi">10.1080/10447310802205776</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ekblaw</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>MedRec: blockchain for medical data access, permission management and trend analysis</article-title>
          <source>Massachusetts Institute of Technology, Thesis</source>
          <year>2017</year>
          <access-date>2020-07-30</access-date>
          <publisher-loc>Cambridge</publisher-loc>
          <publisher-name>Massachusetts Institute of Technology</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dspace.mit.edu/handle/1721.1/109658">https://dspace.mit.edu/handle/1721.1/109658</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
          <article-title>General Data Protection Regulation (GDPR)</article-title>
          <source>Intersoft Consulting</source>
          <year>2018</year>
          <access-date>2020-07-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://gdpr-info.eu/">https://gdpr-info.eu/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
          <article-title>Overview of the national laws on electronic health records in the EU Member States (2016)</article-title>
          <source>European Commission</source>
          <year>2014</year>
          <access-date>2020-07-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ec.europa.eu/health/ehealth/projects/nationallaws_electronichealthrecords_en">https://ec.europa.eu/health/ehealth/projects/nationallaws_electronichealthrecords_en</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sasson</surname>
              <given-names>EB</given-names>
            </name>
            <name name-style="western">
              <surname>Chiesa</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Garman</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Green</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Miers</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Tromer</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Virza</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Decentralized anonymous payments from bitcoin</article-title>
          <year>2014</year>
          <conf-name>2014 IEEE Symposium on Security and Privacy</conf-name>
          <conf-date>May 18-21, 2014</conf-date>
          <conf-loc>San Jose, CA, USA</conf-loc>
          <fpage>459</fpage>
          <pub-id pub-id-type="doi">10.1109/sp.2014.36</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
          <article-title>Alteration of Medical Records</article-title>
          <source>Miller &#38; Zois</source>
          <access-date>2020-07-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.millerandzois.com/doctor-alter-records.html">https://www.millerandzois.com/doctor-alter-records.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
          <article-title>Health Insurance Fraud</article-title>
          <source>PA Insurance Fraud Prevention Authority</source>
          <access-date>2020-07-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.helpstopfraud.org/Types-of-Insurance-Fraud/Health">https://www.helpstopfraud.org/Types-of-Insurance-Fraud/Health</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <article-title>Medical Service Act</article-title>
          <source>Korea Legislation Research Institute</source>
          <access-date>2020-07-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://elaw.klri.re.kr/eng_service/lawView.do?hseq=40970&#38;lang=ENG">https://elaw.klri.re.kr/eng_service/lawView.do?hseq=40970&#38;lang=ENG</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
