<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "http://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="methods-article" dtd-version="1.2" xml:lang="en">
    <front>
        <journal-meta>
            <journal-id journal-id-type="pmc">F1000Research</journal-id>
            <journal-title-group>
                <journal-title>F1000Research</journal-title>
            </journal-title-group>
            <issn pub-type="epub">2046-1402</issn>
            <publisher>
                <publisher-name>F1000 Research Limited</publisher-name>
                <publisher-loc>London, UK</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="doi">10.12688/f1000research.10531.1</article-id>
            <article-categories>
                <subj-group subj-group-type="heading">
                    <subject>Method Article</subject>
                </subj-group>
                <subj-group>
                    <subject>Articles</subject>
                    <subj-group>
                        <subject>Health Systems &amp; Services Research</subject>
                    </subj-group>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>Blockchain protocols in clinical trials: Transparency and traceability of consent</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 1; peer review: 1 approved, 1 not approved]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>Benchoufi</surname>
                        <given-names>Mehdi</given-names>
                    </name>
                    <uri content-type="orcid">https://orcid.org/0000-0003-1948-719X</uri>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Porcher</surname>
                        <given-names>Raphael</given-names>
                    </name>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Ravaud</surname>
                        <given-names>Philippe</given-names>
                    </name>
                    <xref ref-type="aff" rid="a1">1</xref>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>D&#x00e9;partement d'Epid&#x00e9;miologie Clinique, H&#x00f4;pital H&#x00f4;tel Dieu, Paris, France</aff>
                <aff id="a2">
                    <label>2</label>Centre de recherche Inserm Epid&#x00e9;miologie et Statistique Paris Sorbonne Cit&#x00e9; (U1153), Centre de recherche Inserm, Paris, France</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:mehdi.benchoufi@aphp.fr">mehdi.benchoufi@aphp.fr</email>
                </corresp>
                <fn fn-type="con">
                    <p>Mehdi Benchoufi designed the work, initiated and led the analysis on blockchain impacts in the context of clinical trials. With the co-authors, he contributed to identify consent collection process as a substantial use-case for a blockchain implementation, in the idea of clinical trial transparency and traceability. He designed the blockchain collection website and was the medical coordinator of technical developments.</p>
                    <p>Rapha&#x00eb;l Porcher contributed to the design of the work, especially on identifying with the corresponding author which of the consent process steps could be wrapped into a Blockchain process. He has put in perspective the potential of implementing Blockchain in consent process, with regards to information of patients, ethics, data privacy.  </p>
                    <p>Philippe Ravaud brought his expertise to consolidate the design of work, identified with the corresponding author the issues related to consent process that should be tracked through Blockchain transactions, especially the ones related to protocol revisions and lack of consent collection renewal. He analysed the results with Rapha&#x00eb;l Porcher and the corresponding author and inferred from them improved methodology perspectives that Blokchain draw for the entire field of clinical research.  </p>
                    <p>Both Rapha&#x00eb;l Porcher and Philippe Ravaud reviewed the article, finally approved the article and agree to be accountable on any part of the article relatively of its accuracy and its integrity.</p>
                </fn>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>23</day>
                <month>1</month>
                <year>2017</year>
            </pub-date>
            <pub-date pub-type="collection">
                <year>2017</year>
            </pub-date>
            <volume>6</volume>
            <elocation-id>66</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>17</day>
                    <month>1</month>
                    <year>2017</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2017 Benchoufi M et al.</copyright-statement>
                <copyright-year>2017</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <self-uri content-type="pdf" xlink:href="https://f1000research.com/articles/6-66/pdf"/>
            <abstract>
                <p>Clinical trial consent for protocols and their revisions should be transparent for patients and traceable for stakeholders. Our goal is to implement a process allowing the collection of patients&#x2019; informed consent, which is bound to protocol revisions, storing and tracking the consent in a secure, unfalsifiable and publicly verifiable way, and enabling the sharing of this information in real time. For that, we will built a consent workflow using a rising technology called Blockchain. This is a distributed technology that brings a built-in layer of transparency and traceability. Additionally, it removes the need for third parties, and gives participative control to the peer-to-peer users. From a more general and prospective point of view, we believe Blockchain technology brings a paradigmatical shift to the entire clinical research field. We designed a Proof-of-Concept protocol consisting of time-stamping each step of the patient&#x2019;s consent collection using Blockchain; thus archiving and historicising the consent through cryptographic validation in a securely unfalsifiable and transparent way. For each revision of the protocol, consent was sought again. We obtained a single document, in a standard open format, that accounted for the whole consent collection process: timestamped consent status with regards to each version of the protocol. This document cannot be corrupted, and can be checked on any dedicated public website. It should be considered as a robust proof of data. In the future, we think that the complex data flow of a clinical trial can be tracked using Blockchain. Moreover, a blockchain core functionality, named Smart Contract, can help prevent clinical trial events not to happen in the right chronological order: including patients before they consented or analysing case report forms data before freezing the database. This will help reaching reliability, security, and transparency, and could be a consistent step towards reproducibility.</p>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>clinical trial</kwd>
                <kwd>blockchain</kwd>
                <kwd>smart contract</kwd>
                <kwd>consent</kwd>
                <kwd>e-consent</kwd>
                <kwd>transparency</kwd>
                <kwd>reliability</kwd>
                <kwd>reproducibility</kwd>
            </kwd-group>
            <funding-group>
                <funding-statement>The author(s) declared that no grants were involved in supporting this work.</funding-statement>
            </funding-group>
        </article-meta>
    </front>
    <body>
        <sec sec-type="intro">
            <title>Introduction</title>
            <p>Patient participation is the 
                <italic toggle="yes">sine qua non</italic> condition for clinical trials to happen and for medical research to improve
                <sup>
                    <xref ref-type="bibr" rid="ref-1">1</xref>,
                    <xref ref-type="bibr" rid="ref-2">2</xref>
                </sup> (
                <ext-link ext-link-type="uri" xlink:href="http://www.mc.vanderbilt.edu/crc/workshop_files/2011-09-09.pptx">http://www.mc.vanderbilt.edu/crc/workshop_files/2011-09-09.pptx</ext-link>). However, in practice, the informed consent process is hard to handle in a rigorous and satisfactory way. The US Food and Drug Administration (FDA) reports some metrics that are related to the frequency of clinical investigator-related deficiencies, which show that almost 10% of trials they monitored suffer from consent collection issues, such as failure to re-consent when new information becomes available, use of expired forms or non-validated, unapproved forms, consent document not signed or not dated, missing pages in consent document provided to subjects, failure to obtain written informed consent, parental permission obtained after child assent, changes made to the consent documents by hand and without IRB approval
                <sup>
                    <xref ref-type="bibr" rid="ref-3">3</xref>,
                    <xref ref-type="bibr" rid="ref-4">4</xref>
                </sup> (
                <ext-link ext-link-type="uri" xlink:href="http://www.fda.gov/downloads/AboutFDA/CentersOffices/CDER/UCM256376.pdf">http://www.fda.gov/downloads/AboutFDA/CentersOffices/CDER/UCM256376.pdf</ext-link>; 
                <ext-link ext-link-type="uri" xlink:href="http://www.yale.edu/hrpp/education/documents/CommonProblemsinInformedConsent_2013_vF.pptx">http://www.yale.edu/hrpp/education/documents/CommonProblemsinInformedConsent_2013_vF.pptx</ext-link>). The study by Seife
                <sup>
                    <xref ref-type="bibr" rid="ref-5">5</xref>
                </sup> analysed hundreds of clinical trial FDA inspection documents, covering the 1998&#x2013;2013 period, and showed that a substantial number of them presented evidence of research misconduct, among which 53% were related to failure to protect the safety of patients and/or issues with oversight or informed consent.</p>
            <p>This can lead to dramatic events, as in France in January 2016: a trial testing the &#x201c;BIA 10-2474&#x201d; as an analgesic molecule caused the death of a subject. The French health agency IGAS appeared to prove that re-consent was not sought after major neurological side effects occurred in some patients, leading to subjects being included in the clinical trial without being informed of this issue and still receiving doses of the analgesic molecule, (
                <ext-link ext-link-type="uri" xlink:href="http://www.liberation.fr/france/2016/02/04/drame-de-l-essai-clinique-a-rennes-le-deces-reste-inexplique_1431074">http://www.liberation.fr/france/2016/02/04/drame-de-l-essai-clinique-a-rennes-le-deces-reste-inexplique_1431074</ext-link>; 
                <ext-link ext-link-type="uri" xlink:href="https://fr.wikipedia.org/wiki/BIA_10-2474">https://fr.wikipedia.org/wiki/BIA_10-2474</ext-link>, version of 2016.09.05). Another example in the UK occurred when a general practitioner was struck off after testing drugs on patients who did not give their consent
                <sup>
                    <xref ref-type="bibr" rid="ref-6">6</xref>
                </sup>. A recent, popular case of serious scientific misconduct was the DECREASE studies performed by Don Poldermans. The results of these studies were invalidated and some related publications retracted as, amongst many other frauds including data invention, informed consent was not proved to have been obtained before the randomised controlled trials (
                <ext-link ext-link-type="uri" xlink:href="https://en.wikipedia.org/wiki/Don_Poldermans">https://en.wikipedia.org/wiki/Don_Poldermans</ext-link>, version of 2016.09.05; 
                <ext-link ext-link-type="uri" xlink:href="http://retractionwatch.com/category/by-author/don-poldermans/">http://retractionwatch.com/category/by-author/don-poldermans/</ext-link>).</p>
            <p>Obtaining an individual&#x2019;s consent is strictly tied to the Helsinki declaration
                <sup>
                    <xref ref-type="bibr" rid="ref-7">7</xref>,
                    <xref ref-type="bibr" rid="ref-8">8</xref>
                </sup> (
                <ext-link ext-link-type="uri" xlink:href="http://www.wma.net/en/30publications/10policies/b3/index.html">http://www.wma.net/en/30publications/10policies/b3/index.html</ext-link>), which provides the good practices that should follow any stakeholder conducting a clinical trial. Point 26 of the Declaration states that each subject should be informed of the aim, methods, sources of funding, conflict of interests, affiliations of the researchers, anticipated benefits and risks and post-study provisions, and these conditions must be met to obtain freely-given informed consent. In practice, regulation agencies, such as the FDA, provide recommendations and mandatory commitments for consent to be collected in the right conditions
                <sup>
                    <xref ref-type="bibr" rid="ref-9">9</xref>
                </sup> (
                <ext-link ext-link-type="uri" xlink:href="http://www.fda.gov/downloads/RegulatoryInformation/Guidances/UCM405006.pdf">http://www.fda.gov/downloads/RegulatoryInformation/Guidances/UCM405006.pdf</ext-link>). Among those and of major importance, informed consent should be documented by a signed and dated written consent, which is particularly meaningful with Blockchain technology.</p>
            <p>In addition, consent collection is a dynamic process; it is not a one-shot process ending when consent is sought before a clinical trial begins. As explained by Gupta
                <sup>
                    <xref ref-type="bibr" rid="ref-10">10</xref>
                </sup>, there are circumstances under which consent has to be sought again from a subject, corresponding to any time the trial protocol is majorly revised. This is a fundamental fact when ensuring to patients&#x2019; rights and transparency of a clinical trial
                <sup>
                    <xref ref-type="bibr" rid="ref-11">11</xref>,
                    <xref ref-type="bibr" rid="ref-12">12</xref>
                </sup>. Indeed, as detailed in these Institutional review board (IRB) guidelines (
                <ext-link ext-link-type="uri" xlink:href="http://www.irb.pitt.edu/sites/default/files/reconsent guidance.pdf">http://www.irb.pitt.edu/sites/default/files/reconsent guidance.pdf</ext-link>; 
                <ext-link ext-link-type="uri" xlink:href="http://www.mayo.edu/research/documents/29-re-consent-or-notification-of-significant-new-findingspdf/doc-10027714">http://www.mayo.edu/research/documents/29-re-consent-or-notification-of-significant-new-findingspdf/doc-10027714</ext-link>; 
                <ext-link ext-link-type="uri" xlink:href="http://www.yale.edu/hrpp/policies/documents/Reconsentingguidance.pdf">http://www.yale.edu/hrpp/policies/documents/Reconsentingguidance.pdf</ext-link>), there are many situations where patients re-consent has to be sought or where they should be notified of minor trial issues, such as novel risks, significant changes in the research procedures, and worsening of the medical condition. Documents that are to be sent to patients can be consent form addendums, an information letter or a fully revised consent form. Of course, the revised consent form has to be approved by an IRB. It must be stressed that the FDA has highlighted the necessity to conceive a mechanism that ensures that the most recent revised consent form is in use in a clinical trial, and stipulates that timestamping is such an approved mechanism
                <sup>
                    <xref ref-type="bibr" rid="ref-9">9</xref>
                </sup> (
                <ext-link ext-link-type="uri" xlink:href="http://www.fda.gov/downloads/RegulatoryInformation/Guidances/UCM405006.pdf">http://www.fda.gov/downloads/RegulatoryInformation/Guidances/UCM405006.pdf</ext-link>).</p>
            <p>As indicated in 
                <xref ref-type="fig" rid="f1">Figure 1</xref>, consent is a dynamic process that involves a complex circuit of data and interacting actors, which should all retain information of this on-going process. For example: what subjects were notified; when the notifications were delivered; whom of the subjects consented or re-consented; when did subjects consent or re-consent. This information should circulate between the clinical trial stakeholders in real time.</p>
            <fig fig-type="figure" id="f1" orientation="portrait" position="float">
                <label>Figure 1. </label>
                <caption>
                    <title>Consent collection Blockchain workflow.</title>
                </caption>
                <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/11349/b8069ea3-2ff2-4355-beff-61f4082e5c00_figure1.gif"/>
            </fig>
            <p>Blockchain is a dawn-aged technology, a giant public datastore, stored in a secure and decentralised way. It is widely announced to be a backbone of the circulation of digital assets, powering any kind of services by transparency, traceability. In this context, Blockchain&#x2019;s emerging and promising technology (
                <ext-link ext-link-type="uri" xlink:href="https://en.wikipedia.org/wiki/Blockchain_(database)">https://en.wikipedia.org/wiki/Blockchain_(database)</ext-link>) can bring solid basis in the enrolment phase transparently to all stakeholders of a clinical trial, especially in the context of obtaining participant&#x2019;s consent. Three core functional principles of this technology can play a fundamental role, as follows: 
                <list list-type="bullet">
                    <list-item>
                        <label>1. </label>
                        <p>Unfalsifiable timestamping information: this stands for proof of existence of any piece of data. When stored, this data is provable and immutable through a strong cryptographic protocol. Moreover, these proofs of existence can be checked on a public website. This transparency is of interest to any interested stakeholder.</p>
                    </list-item>
                    <list-item>
                        <label>2. </label>
                        <p>Smart contract: this is a contract that is algorithmically implemented and binds any change in the protocol to the patients&#x2019; consent seeking renewal.</p>
                    </list-item>
                    <list-item>
                        <label>3. </label>
                        <p>The decentralized nature of the Blockchain protocol gives to the patient, or more widely to patients&#x2019; communities, control over their consent and its revocation. The end-to-end connectivity creates a network that empowers patients and researchers as peers.</p>
                    </list-item>
                </list>
</p>
            <sec>
                <title>Blockchain comes into play</title>
                <p>

                    <bold>

                        <italic toggle="yes">At a clinical trial level.</italic>
</bold> Blockchain technology can act as a SafeGuard for the complex and wide range of actors required in clinical trials. In practice, the proof of existence for consent will be timestamped and stored in Blockchains, enabling clinical research stakeholders, such as sponsors, investigators and IRBs, which can be numerous in multi-center clinical investigations, to share consent and re-consent related data in real-time, and archive and historicize consent sets, which can be matched with each revision of the protocol.</p>
                <p>Obtaining consent must be a &#x2018;lock&#x2019; before subject inclusion in clinical trials. Indeed, with the help of Blockchain cryptographic keys, investigators won&#x2019;t be able to include a patient in the trial until their consent is collected. In addition, to ensure a strict parity between enrolled patients and included patients, the present study will use one core functionality that Blockchain enables: the Smart Contract (
                    <ext-link ext-link-type="uri" xlink:href="https://en.wikipedia.org/wiki/Smart_contract">https://en.wikipedia.org/wiki/Smart_contract</ext-link>, version of 2016.09.05). This is a piece of code that holds a programmatically written contract between as many parties as needed, without any third-party, which executes algorithmically according to the terms provided by the contracting parties. This makes it possible to build a Smart Contract that will be executed with the only condition that patients will only be included when the enrolment is complete (technically, every Blockchain transactions can have a lock associated to them and transactions can be pending and triggered at an agreed upon contract time).</p>
                <p>

                    <bold>

                        <italic toggle="yes">At a patient level.</italic>
</bold> Implementing a &#x201c;privacy by design&#x201d; technology, and archiving securely and transparently any dataset that needs to be stored, is a game changer towards improving enrolment phase methodology. Moreover, drawing on an entirely new way to collect informed consent, being careful with subjects rights, and so empowering them, could improve the enrolment rate. Indeed, the participation rate to clinical trial remains quite weak
                    <sup>
                        <xref ref-type="bibr" rid="ref-11">11</xref>
                    </sup>. Caldwell &amp; All performed a systematic review comparing different enrolment techniques, and showed that, amongst several other explanations, the conditions of collecting patients consent in an open and secure way is better at achieving an improved rate of enrolment
                    <sup>
                        <xref ref-type="bibr" rid="ref-11">11</xref>,
                        <xref ref-type="bibr" rid="ref-13">13</xref>
                    </sup>. At the patient community level, much literature documents barriers to enrolment, especially when barriers are strongly related to community or ethnicity-related issues
                    <sup>
                        <xref ref-type="bibr" rid="ref-14">14</xref>,
                        <xref ref-type="bibr" rid="ref-15">15</xref>
                    </sup>. We think that the decentralized, transparent and secure nature of Blockchain protocol may meet the conditions for an improved engagement of patient communities in clinical trials.</p>
                <p>The tools that we will present in the current study should be considered as a starting point to define a gold-standard of an open and secure informed consent collection process. This can help optimize patients enrolment, and in turn, through a more transparent and trusted process, can create a bridge between clinical research teams and patient communities, who are novel incomers in our digital age and whose commitment is critically dependent on building clinical trials as a highly trusted process.</p>
            </sec>
        </sec>
        <sec sec-type="methods">
            <title>Methods</title>
            <p>In this proof-of-concept (POC) study, we targeted 27 volunteers for enrolment, which was achieved at the Clinical Epidemiology Department at Hospital H&#x00f4;tel Dieu (Paris, France). There were no exclusion or inclusion criteria; the volunteers that were recruited were staff members of the Epidemiology Department (Hospital H&#x00f4;tel Dieu). However, we ensured each of the users had email access.</p>
            <p>A fake experimental clinical trial protocol was designed whose purpose was to compare the effect of &#x201c;cisplatin vs. ledgerlin&#x201d;, the last substance being a neologism, which was derived from the critical public datastore shared by all Blockchain users called &#x201c;ledger". The protocol was accompanied by a consent form, which mimicked a design used routinely.</p>
            <p>Each of the to-be-enrolled users were assigned a private key in order to sign data and documents, and in practice this would be used to publish their signed consent, which was to be anchored to the Blockchain.</p>
            <sec>
                <title>Blockchain networks</title>
                <p>There are several Blockchain networks, for example Ethereum (
                    <ext-link ext-link-type="uri" xlink:href="https://www.ethereum.org">https://www.ethereum.org</ext-link>), Bitcoin (
                    <ext-link ext-link-type="uri" xlink:href="https://en.wikipedia.org/wiki/Bitcoin_network">https://en.wikipedia.org/wiki/Bitcoin_network</ext-link>) and Hyperledger (
                    <ext-link ext-link-type="uri" xlink:href="https://www.hyperledger.org">https://www.hyperledger.org</ext-link>). For our purpose, transactions and their validations were run on the Bitcoin network. Our choice was motivated by stability and immutability of the Bitcoin Blockchain, due to its large mining network, and the API it provides facilitates development. Moreover, it is the more widely used Blockchain network; therefore, there is a relatively dense community of developers to enable an efficient support (
                    <ext-link ext-link-type="uri" xlink:href="https://bitcoin.stackexchange.com">https://bitcoin.stackexchange.com</ext-link>). The front-end and back-end technologies that are detailed hereafter were implemented by a Blockchain solutions provider, Stratumn SAS (
                    <ext-link ext-link-type="uri" xlink:href="https://stratumn.com/">https://stratumn.com/</ext-link>).</p>
                <p>A website was developed with a simple one-page interface (
                    <xref ref-type="fig" rid="f2">Figure 2</xref>). On the front-end, it displayed the consent document, a checkbox attesting that the protocol was read and understood, and a push button that triggered the consent process.</p>
                <p>In practice, the on-line signed document contained a piece of code called &#x201c;Chainscript&#x201d;, (
                    <ext-link ext-link-type="uri" xlink:href="http://chainscript.io">http://chainscript.io</ext-link>), which contained all the critical information about the user, and the version of the protocol attached to the signature. Each proof of signature had a manifest that takes the form of a hash that is the digital proof of signature.</p>
                <fig fig-type="figure" id="f2" orientation="portrait" position="float">
                    <label>Figure 2. </label>
                    <caption>
                        <title>Patients web-interface for blockchained consent collection website.</title>
                    </caption>
                    <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/11349/b8069ea3-2ff2-4355-beff-61f4082e5c00_figure2.gif"/>
                </fig>
                <p>On the back-end, pressing the &#x201c;consent button&#x201d; triggers Blockchain transactions: the proof of signature is timestamped and stored in the Blockchain. It should be emphasised that these signatures were shared in real-time through a restricted group of individuals, namely the present authors, who stand, in a real-life implementation, for investigators, IRBs or sponsors. This group obtains access to a dashboard (
                    <xref ref-type="fig" rid="f3">Figure 3</xref>) with the following: an admin panel displaying the consent status of each user; the protocol that transparently stores the public keys of each consenting user (through Chainscript); and the history of each released version of the protocol and the consent and re-consent of the user attached to each of these versions.</p>
                <fig fig-type="figure" id="f3" orientation="portrait" position="float">
                    <label>Figure 3. </label>
                    <caption>
                        <title>Investigator dashboard for blockchained consent collection website.</title>
                    </caption>
                    <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/11349/b8069ea3-2ff2-4355-beff-61f4082e5c00_figure3.gif"/>
                </fig>
            </sec>
            <sec>
                <title>Authentication method</title>
                <p>For each user a pair of private-public keys were provided, (
                    <ext-link ext-link-type="uri" xlink:href="https://msdn.microsoft.com/fr-fr/library/windows/desktop/aa387460(v=vs.85).aspx">https://msdn.microsoft.com/fr-fr/library/windows/desktop/aa387460(v=vs.85).aspx</ext-link>). These are asymmetric cryptographic data that enables authentication on Blockchain. These were randomly attached in one-to-one correspondence to a user&#x2019;s emails. We focused our interest to Blockchain&#x2019;s usage in the time-stamping and archiving logic. We did not let users create or use their own Blockchain authentication setup, i.e. if a user owned a Bitcoin account, the key and Bitcoin address were not allowed to be used. This restriction was not related to Blockchain complexity, but rather to maintain a simple and common email-focused authentication process. Other ways exist for authentication, such as physical devices, like USB keys or cell phone fingerprints, but this would have led us far from the focus point of our protocol-related problematics.</p>
            </sec>
            <sec>
                <title>Workflow</title>
                <p>The process that subjects were submitted is as follows: 
                    <list list-type="bullet">
                        <list-item>
                            <label>&#x2022;</label>
                            <p>The study investigators to send email to the patients.</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>The users receive the email, which contains a web hyperlink redirecting them to the web interface that displays the consent form.</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>In the background, after clicking the consent button without the user experience being bothered by any blockchain transaction related complexity, the user signature is registered to the Blockchain and is timestamped.</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>Each time the protocol is updated, investigators send an email explaining the major changes that occurred and users are invited to sign the revised consent form.</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>Each step of this process is updated on the investigators&#x2019; admin panel with the version of the consent document and the user's consenting status.</p>
                        </list-item>
                    </list>
</p>
            </sec>
            <sec>
                <title>Proof of existence - Chainscript</title>
                <p>Signatures of the evolving consent document were registered to the Blockchain. Moreover, all of the relevant interactions of the user with our platform was stored in the Blockchain, i.e. the consent form upload by the investigator; email requests to users; and patient signatures.</p>
                <p>The piece of data attesting and synthesising all this information is called a Chainscript. It is a JSON formatted data structure holding all the information related to the protocol and users&#x2019; consent. Chainscript is a JSON format developed by Stratumn SAS, especially dedicated to attest the steps in trusted workflows (
                    <ext-link ext-link-type="uri" xlink:href="http://chainscript.io/">http://chainscript.io/</ext-link>). Chainscript is an open standard. The philosophy behind it is to be able to prove the integrity of a process with a single JSON data structure by securing the who, when, what and where of a sequences of steps that are linked together in chronological order. Each sequence corresponds to a segment, and each segment holds some metadata, an identifier called a hash, and a pointer to the preceding segment. The critical information maintained in Chainscript are the hashes, which are the proofs of the existence of data. Since each Blockchain transaction has a cost, we decided to group the transactions. What makes Chainscript interesting is that a series of Blockchain transactions can be wrapped into the same logic flow, preventing too intensive requesting to the Blockchain network, which can prove to be costly.</p>
                <p>Therefore, with this information, how can we check proof of a specific data after they are merged? The ChainScript solution relies on a singular data structure, a Merkle Tree, which in a way &#x201c;hashes the hash&#x201d;, preserving in one single hash all the hashes, so that if any hash is corrupted, the entire tree is invalidated.</p>
                <p>In our implementation, the ChainScript code is held in the PDF consent document, storing its hashed content, all its versions (corresponding to protocol revisions) and all the signing users for each version. It is of major interest that ChainScript can be publicly verified without any proprietary tool.</p>
                <p>We should remark that a positive side effect of tracking each step of a user&#x2019;s interaction with the platform is that storing so exhaustively the data, raises the barrier to fraud.</p>
            </sec>
        </sec>
        <sec sec-type="results">
            <title>Results</title>
            <sec>
                <title>Clinical trial master document</title>
                <p>We were able to collect consent and re-consent of users and store them in a transparent, unfalsifiable, verifiable way. These data were encoded in a single document. This document holds the stakeholders&#x2019; identifiers, the users&#x2019; identifiers, timestamps of the protocols being sent, consent status, timestamps of the consent, and the version of the protocol to which the consent is attached.</p>
                <p>This master document was shared in real-time through key actors that ruled the POC study. It was registered to the Blockchain in a safe way, so that this group of stakeholders retains the timestamped proof of the consent status in an immutable document. We stress again the fact that this document is incorruptible, and it is possible to check its consistency on any dedicated public website (e.g. a website that enables checking of Bitcoin transactions), proving the correspondence between each version of the protocol and its related consent.</p>
                <p>Technically, these data are synthesized in the open data format we mentioned earlier, Chainscript, which is as follows:</p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">"segment": {</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">  "link": {</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    "state": {</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">      fileName: "protocole.pdf";</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">      uploadedBy: "investigateur";</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    },</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    "meta": {</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">      "title" : "Protocole",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">      "tags" :["POC", "Essai clinique", "H&#x00f4;pital H&#x00f4;tel-Dieu"],</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">      "priority": "0"</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">      "updatedAt": 1455532426303,</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">      "mapId": "56c11d0ea55773bc6e681fde",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    }</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">  },</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">  [{ "Document_ID": "NOTE D INFORMATION DESTINEE AU PATIENT.pdf"",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">   "Doctor_Name": "***",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">   "Doctor_Email": "***@aphp.fr",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">   "PDF_Title": "",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">   "Conditions": "",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">   "ExpiresIn": "XX",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">   "Max_Patients": "XXX",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">   Invites:</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">   [{</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">   "Email": "***@aphp.fr",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">   "Name": "***",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">   "Address": {</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">     "hash": "2568ce846c1391d94065df6cc4a42720369bcec9",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">     "type": "pubkeyhash",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">     "network": "livenet"</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">     }</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">  },],</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">  },[</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">        "signature",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    "***",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    "***@aphp.fr",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    0,</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    "H6qy9U3S+BNqreKwMgEnDAHij3wNMcq4T2+X9axzx65Zd+HDy16tr03YPT4oKkGtW820so0D+0Pk2UTrwnXiLKs=",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    {</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">        hash: "6786ce716b2ac8e14b20e0a2fd8b88a7994d4a10",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">        type: "pubkeyhash",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">        network: "livenet"</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    },</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    "2016-07-08T13:11:15.824Z",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    "method__saveSignature"</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">],[{</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    "DateSigned": "2016-07-08T13:11:15.824Z",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    "Signature":         "H6qy9U3S+BNqreKwMgEnDAHij3wNMcq4T2+X9axzx65Zd+HDy16tr03YPT4oKkGtW820so0D+0Pk2UTrwnXiLKs=",</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    Consent: 0</preformat>
                </p>
                <p>
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">    }]</preformat>
                </p>
                <p>All this information is bound together in one data structure, so that the whole set of obtained consent, with their uniquely attached version of the protocol, form an immutable global data. The change of a single element breaks the entire data structure.</p>
                <p>In the interest of user confidentiality, the master document cannot be made available.</p>
            </sec>
            <sec>
                <title>Technical details of the POC</title>
                <p>We sent two versions of the protocol (
                    <xref ref-type="other" rid="SF1">Supplementary File 1</xref> and 
                    <xref ref-type="other" rid="SF2">Supplementary File 2</xref>) during the study, through which we sought the users consent; each consent was attached to a specific version of the protocol.</p>
                <p>Users were given a digital signature and secured key, each of which consisted of a hash. Amongst the users of this experimental study, 14 gave their consent to the two versions of the protocol, 9 gave their consent to only one version of the protocol and 2 didn&#x2019;t give their consents at all and 2 did not respond to any consent form.</p>
                <p>The interaction of the user with the online interface, namely accepting or refusing to give consent, led to a transaction validated in Blockchain. Each version of the protocol had a unique identifier, called a hash. The hash is uniquely attached to the content of the protocol document. The correspondence between the consent document and the hash is one-to-one, namely if one single letter is changed then the hash is broken.</p>
                <p>

                    <xref ref-type="fig" rid="f4">Figure 4</xref> shows where the identifier of the protocol document is highlighted in the Chainscript master document. 
                    <xref ref-type="fig" rid="f5">Figure 5</xref> displays the investigator identifiers, and 
                    <xref ref-type="fig" rid="f6">Figure 6</xref> reveals the consent status bound to the protocol revision version.</p>
                <fig fig-type="figure" id="f4" orientation="portrait" position="float">
                    <label>Figure 4. </label>
                    <caption>
                        <title>Consent collection master document: unique identifier protocol.</title>
                    </caption>
                    <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/11349/b8069ea3-2ff2-4355-beff-61f4082e5c00_figure4.gif"/>
                </fig>
                <fig fig-type="figure" id="f5" orientation="portrait" position="float">
                    <label>Figure 5. </label>
                    <caption>
                        <title>Consent collection master document: investigator identifiers.</title>
                    </caption>
                    <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/11349/b8069ea3-2ff2-4355-beff-61f4082e5c00_figure5.gif"/>
                </fig>
                <fig fig-type="figure" id="f6" orientation="portrait" position="float">
                    <label>Figure 6. </label>
                    <caption>
                        <title>Consent collection master document: consents status bound to protocol revision versions.</title>
                    </caption>
                    <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/11349/b8069ea3-2ff2-4355-beff-61f4082e5c00_figure6.gif"/>
                </fig>
            </sec>
        </sec>
        <sec sec-type="discussion">
            <title>Discussion</title>
            <p>Blockchain is an emerging, fast-evolving technology. The boiling atmosphere around development and use of Blockchain is similar to tech development during the early stages of the web : It took several years before formatting as html or css became web standards. Blockchain technologies are gaining more and more attention, and Blockchain networks are proliferating, for example Ethereum, Bitcoin, Hyperledger or private Blockchain networks. It is not clear which of these will impose itself as a blockchain network standard, or even if there will be unique standard one. Public networks are interesting due to the idea of a community driven approach and scalability, but private ones can offer a certain level of customization.</p>
            <p>Alongside this fast-developing tech, there are still some infrastructure obstructions that are not yet circumvented, namely delays in transaction validation. On the Bitcoin network, the validation process (via the so-called mining) takes around 10 minutes (
                <ext-link ext-link-type="uri" xlink:href="https://www.quandl.com/data/BCHAIN/ATRCT-Bitcoin-Average-Transaction-Confirmation-Time">https://www.quandl.com/data/BCHAIN/ATRCT-Bitcoin-Average-Transaction-Confirmation-Time</ext-link>). In the present study&#x2019;s context, we are not tied by real-time requirements measured in seconds, and so it is not a major obstruction. Moreover, the ChainScript logic we implemented in our POC allows grouped network request validation, which preserves the Blockchain network from computation overload, and allows to scale our method to a large patient cohort. More generally, to tackle this challenge of scaling the network, in case there is a massive amount of transactions, there are some implementations of Bitcoin-based protocol isolated from the Blockchain, the most renown is called SideChain (
                <ext-link ext-link-type="uri" xlink:href="https://www.deepdotweb.com/2014/06/26/sidechains-blockchain-2-0/">https://www.deepdotweb.com/2014/06/26/sidechains-blockchain-2-0/</ext-link>; 
                <ext-link ext-link-type="uri" xlink:href="https://www.reddit.com/r/Bitcoin/comments/2kdxy8/">https://www.reddit.com/r/Bitcoin/comments/2kdxy8/</ext-link>).</p>
            <p>Moreover, with regard to the authentication process, we can expect that, when the use of Blockchain&#x2019;s technologies will be more common, there is an important chance that users already possess a Blockchain public-private-key identity. Therefore, sending keys for access and identification later in the signing process will be obsolete. This will require maintenance of a double key attribution (as explained above in the &#x201c;Authentication method" section) for users that do not have any Blockchain network identity and to be able to take into account those who have already one. In the latter case, verification of the digital signature of these users will have to occur.</p>
            <p>It should be noted that we did not implement a consent revocation workflow. However, there is no issue in transposing at that end the Blockchain transaction logic we implemented for the consent. On that point, we should be careful about the fact that if the consent or its revocation can be given or withdrawn with no problem, these actions cannot be erased from the Blockchain. Indeed, if subjects revoked their consent by accident, then the action can be reversed, but data will remain containing the revocation of the consent and the cancellation of this revocation.</p>
            <p>Finally, we evoked a possible improvement in the enrolment rate, by empowering patients and granting them information and control over the enrolment phase. However, Blockchain is certainly not a &#x201c;one size fits all&#x201d; solution to the problem of a low enrolment rate. Indeed, there are many other parameters that interfere with the enrolment, which fall beyond the scope of transparency, user control and reliability that Blockchain technology helps to achieve: age, sex, cultural background, socio-economic factors, lack of educational materials
                <sup>
                    <xref ref-type="bibr" rid="ref-16">16</xref>
                </sup>, readability and length of consent
                <sup>
                    <xref ref-type="bibr" rid="ref-17">17</xref>&#x2013;
                    <xref ref-type="bibr" rid="ref-19">19</xref>
                </sup>, limited awareness about clinical research or patient-physician relationship
                <sup>
                    <xref ref-type="bibr" rid="ref-20">20</xref>
                </sup> and momentum of consent request
                <sup>
                    <xref ref-type="bibr" rid="ref-21">21</xref>,
                    <xref ref-type="bibr" rid="ref-22">22</xref>
                </sup>. Besides, the scope of our method did not address the question of consent collected in singular situations, such as intensive care, unconscious patients or psychiatric pathologies.</p>
        </sec>
        <sec sec-type="conclusions">
            <title>Conclusion</title>
            <p>Keeping track of consent collection is consolidated through the use of Blockchain technology. We have seen in this proof-of-concept study that all consent-related data can leave an unfalsifiable and verifiable fingerprint on the Blockchain. This is important both on the stakeholder&#x2019;s side, letting them prove the existence and the consistency of the data, and on the patient&#x2019;s side, giving them more visibility, transparency, and hence control over their consent.</p>
            <p>Moreover, though it was not be the focus of this paper, we anticipate that Blockchain technology, in that it does not rely trust on third party but inversely empowers peer-to-peer users by granting them control over consent agreement and revocation, can help gathering conditions of an improved privacy-respected freely-given consent. Besides, given its decentralized protocol, it can help introduce communities to contemporary clinical research, opening, for clinical reasearch, the path to implementing community management techniques in order to enrol patients using a more targeted approach.</p>
            <p>From a global perspective, the application of Blockchain technologies in the context of clinical research is broad and promising. Indeed, tracking the complex data flow with numerous diverse stakeholders, and documenting it in real-time through a timestamping workflow, is a key step towards proving data consistency and inviolability, and will hence improve clinical trial methodology.</p>
        </sec>
        <sec>
            <title>Software availability</title>
            <p>Latest source code available at: 
                <ext-link ext-link-type="uri" xlink:href="https://github.com/benchoufi/DocChain">https://github.com/benchoufi/DocChain</ext-link>
</p>
            <p>Archived source code as at time of publication: doi, 
                <ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.5281/zenodo.237040">10.5281/zenodo.237040</ext-link> (
                <ext-link ext-link-type="uri" xlink:href="https://zenodo.org/record/237040#.WHSxorYrI_V">https://zenodo.org/record/237040#.WHSxorYrI_V</ext-link>)</p>
            <p>Licence: 3-clause BSD licence</p>
        </sec>
    </body>
    <back>
        <sec id="SM1" sec-type="supplementary-material">
            <title>Supplementary material</title>
            <p id="SF1">Supplementary File 1: Protocol and consent form (versions 0 and 1) used in the proof-of-concept study (in zipped file) (in French).</p>
            <p>

                <ext-link ext-link-type="uri" xlink:href="https://f1000researchdata.s3.amazonaws.com/supplementary/10531/2ae80474-0dca-4f19-ba4b-5c59d9b49877.zip">Click here to access the data</ext-link>.</p>
            <p id="SF2">Supplementary File 2: Protocol and consent form (versions 0 and 1) used in the proof-of-concept study (in zipped file) (in English).</p>
            <p>

                <ext-link ext-link-type="uri" xlink:href="https://f1000researchdata.s3.amazonaws.com/supplementary/10531/895c29be-d132-41f6-b65a-aa88ff5155fd.zip">Click here to access the data</ext-link>.</p>
        </sec>
        <ref-list>
            <ref id="ref-1">
                <label>1</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Gupta</surname>
                            <given-names>UC</given-names>
                        </name>
</person-group>:
                    <article-title>Informed consent in clinical research: Revisiting few concepts and areas.</article-title>
                    <source>

                        <italic toggle="yes">Perspect Clin Res.</italic>
</source>
                    <year>2013</year>;<volume>4</volume>(<issue>1</issue>):<fpage>26</fpage>&#x2013;<lpage>32</lpage>.
                    <pub-id pub-id-type="pmid">23533976</pub-id>
                    <pub-id pub-id-type="doi">10.4103/2229-3485.106373</pub-id>
                    <pub-id pub-id-type="pmcid">3601699</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-2">
                <label>2</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Lloyd</surname>
                            <given-names>Wendy</given-names>
                        </name>
</person-group>: BA, LPN, CIP,CCRP, Regulatory Affairs and Compliance Specialist
                    <article-title>Part 2 of 3 Part Series: Informed Consent, the process</article-title>.
                    <ext-link ext-link-type="uri" xlink:href="http://www.mc.vanderbilt.edu/crc/workshop_files/2011-09-09.pptx">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-3">
                <label>3</label>
                <mixed-citation publication-type="journal">
                    <article-title>Office of Scientific Investigations, Metrics.</article-title>US Food and Drug Administration.<year>2014</year>.
                    <ext-link ext-link-type="uri" xlink:href="http://www.fda.gov/downloads/AboutFDA/CentersOffices/CDER/UCM256376.pdf">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-4">
                <label>4</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Barney</surname>
                            <given-names>JR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Antisdel</surname>
                            <given-names>M</given-names>
                        </name>
</person-group>:
                    <article-title>Common problems in informed consent.</article-title>Human Research Protection Program (HRPP).<year>2013</year>.
                    <ext-link ext-link-type="uri" xlink:href="http://your.yale.edu/sites/default/files/commonproblemsininformedconsent_2013_vf.pptx">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-5">
                <label>5</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Seife</surname>
                            <given-names>C</given-names>
                        </name>
</person-group>:
                    <article-title>Research misconduct identified by the US Food and Drug Administration: out of sight, out of mind, out of the peer-reviewed literature.</article-title>
                    <source>

                        <italic toggle="yes">JAMA Intern Med.</italic>
</source>
                    <year>2015</year>;<volume>175</volume>(<issue>4</issue>):<fpage>567</fpage>&#x2013;<lpage>77</lpage>.
                    <pub-id pub-id-type="pmid">25664866</pub-id>
                    <pub-id pub-id-type="doi">10.1001/jamainternmed.2014.7774</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-6">
                <label>6</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Dillner</surname>
                            <given-names>L</given-names>
                        </name>
</person-group>:
                    <article-title>BSE linked to new variant of CJD in humans.</article-title>
                    <source>

                        <italic toggle="yes">BMJ.</italic>
</source>
                    <year>1996</year>;<volume>312</volume>(<issue>7034</issue>):<fpage>795</fpage>&#x2013;<lpage>800</lpage>.
                    <pub-id pub-id-type="pmid">8608277</pub-id>
                    <pub-id pub-id-type="doi">10.1136/bmj.312.7034.795</pub-id>
                    <pub-id pub-id-type="pmcid">2350704</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-7">
                <label>7</label>
                <mixed-citation publication-type="journal">
                    <article-title>WMA Declaration of Helsinki - Ethical Principles for Medical Research Involving Human Subjects</article-title>.
                    <ext-link ext-link-type="uri" xlink:href="http://www.wma.net/en/30publications/10policies/b3/">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-8">
                <label>8</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Myles</surname>
                            <given-names>PS</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Williamson</surname>
                            <given-names>E</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Oakley</surname>
                            <given-names>J</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Ethical and scientific considerations for patient enrollment into concurrent clinical trials.</article-title>
                    <source>

                        <italic toggle="yes">Trials.</italic>
</source>
                    <year>2014</year>;<volume>15</volume>:<fpage>470</fpage>.
                    <pub-id pub-id-type="pmid">25433679</pub-id>
                    <pub-id pub-id-type="doi">10.1186/1745-6215-15-470</pub-id>
                    <pub-id pub-id-type="pmcid">4258295</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-9">
                <label>9</label>
                <mixed-citation publication-type="journal">
                    <article-title>Informed Consent Information Sheet Guidance for IRBs, Clinical Investigators, and Sponsors</article-title>.
                    <ext-link ext-link-type="uri" xlink:href="http://www.fda.gov/downloads/RegulatoryInformation/Guidances/UCM405006.pdf">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-10">
                <label>10</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Gupta</surname>
                            <given-names>UC</given-names>
                        </name>
</person-group>:
                    <article-title>Informed consent in clinical research: Revisiting few concepts and areas.</article-title>
                    <source>

                        <italic toggle="yes">Perspect Clin Res.</italic>
</source>
                    <year>2013</year>;<volume>4</volume>(<issue>1</issue>):<fpage>26</fpage>&#x2013;<lpage>32</lpage>.
                    <pub-id pub-id-type="pmid">23533976</pub-id>
                    <pub-id pub-id-type="doi">10.4103/2229-3485.106373</pub-id>
                    <pub-id pub-id-type="pmcid">3601699</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-11">
                <label>11</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Caldwell</surname>
                            <given-names>PH</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Hamilton</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tan</surname>
                            <given-names>A</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Strategies for increasing recruitment to randomised controlled trials: systematic review.</article-title>
                    <source>

                        <italic toggle="yes">PLoS Med.</italic>
</source>
                    <year>2010</year>;<volume>7</volume>(<issue>11</issue>):<fpage>e1000368</fpage>.
                    <pub-id pub-id-type="pmid">21085696</pub-id>
                    <pub-id pub-id-type="doi">10.1371/journal.pmed.1000368</pub-id>
                    <pub-id pub-id-type="pmcid">2976724</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-12">
                <label>12</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Resnik</surname>
                            <given-names>DB</given-names>
                        </name>
</person-group>:
                    <article-title>Re-consenting human subjects: Ethical, legal and practical issues.</article-title>
                    <source>

                        <italic toggle="yes">J Med Ethics.</italic>
</source>
                    <year>2009</year>;<volume>35</volume>(<issue>11</issue>):<fpage>656</fpage>&#x2013;<lpage>657</lpage>.
                    <pub-id pub-id-type="pmid">19880699</pub-id>
                    <pub-id pub-id-type="doi">10.1136/jme.2009.030338</pub-id>
                    <pub-id pub-id-type="pmcid">3971530</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-13">
                <label>13</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>McDonald</surname>
                            <given-names>AM</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Knight</surname>
                            <given-names>RC</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Campbell</surname>
                            <given-names>MK</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>What influences recruitment to randomised controlled trials? A review of trials funded by two UK funding agencies.</article-title>
                    <source>

                        <italic toggle="yes">Trials.</italic>
</source>
                    <year>2006</year>;<volume>7</volume>:<fpage>9</fpage>.
                    <pub-id pub-id-type="pmid">16603070</pub-id>
                    <pub-id pub-id-type="doi">10.1186/1745-6215-7-9</pub-id>
                    <pub-id pub-id-type="pmcid">1475627</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-14">
                <label>14</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Swanson</surname>
                            <given-names>GM</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Ward</surname>
                            <given-names>AJ</given-names>
                        </name>
</person-group>:
                    <article-title>Recruiting minorities into clinical trials: toward a participant-friendly system.</article-title>
                    <source>

                        <italic toggle="yes">J Natl Cancer Inst.</italic>
</source>
                    <year>1995</year>;<volume>87</volume>(<issue>23</issue>):<fpage>1747</fpage>&#x2013;<lpage>59</lpage>.
                    <pub-id pub-id-type="pmid">7473831</pub-id>
                    <pub-id pub-id-type="doi">10.1093/jnci/87.23.1747</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-15">
                <label>15</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Lovato</surname>
                            <given-names>LC</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Hill</surname>
                            <given-names>K</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Hertert</surname>
                            <given-names>S</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Recruitment for controlled clinical trials: literature summary and annotated bibliography.</article-title>
                    <source>

                        <italic toggle="yes">Control Clin Trials.</italic>
</source>
                    <year>1997</year>;<volume>18</volume>(<issue>4</issue>):<fpage>328</fpage>&#x2013;<lpage>52</lpage>.
                    <pub-id pub-id-type="pmid">9257072</pub-id>
                    <pub-id pub-id-type="doi">10.1016/S0197-2456(96)00236-X</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-16">
                <label>16</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Hazen</surname>
                            <given-names>RA</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Eder</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Drotar</surname>
                            <given-names>D</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>A feasibility trial of a video intervention to improve informed consent for parents of children with leukemia.</article-title>
                    <source>

                        <italic toggle="yes">Pediatr Blood Cancer.</italic>
</source>
                    <year>2010</year>;<volume>55</volume>(<issue>1</issue>):<fpage>113</fpage>&#x2013;<lpage>8</lpage>.
                    <pub-id pub-id-type="pmid">20063423</pub-id>
                    <pub-id pub-id-type="doi">10.1002/pbc.22411</pub-id>
                    <pub-id pub-id-type="pmcid">2874099</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-17">
                <label>17</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Brehaut</surname>
                            <given-names>JC</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Carroll</surname>
                            <given-names>K</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Elwyn</surname>
                            <given-names>G</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Informed consent documents do not encourage good-quality decision making.</article-title>
                    <source>

                        <italic toggle="yes">J Clin Epidemiol.</italic>
</source>
                    <year>2012</year>;<volume>65</volume>(<issue>7</issue>):<fpage>708</fpage>&#x2013;<lpage>724</lpage>.
                    <pub-id pub-id-type="pmid">22537428</pub-id>
                    <pub-id pub-id-type="doi">10.1016/j.jclinepi.2012.01.004</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-18">
                <label>18</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Pandiya</surname>
                            <given-names>A</given-names>
                        </name>
</person-group>:
                    <article-title>Readability and comprehensibility of informed consent forms for clinical trials.</article-title>
                    <source>

                        <italic toggle="yes">Perspect Clin Res.</italic>
</source>
                    <year>2010</year>;<volume>1</volume>(<issue>3</issue>):<fpage>98</fpage>&#x2013;<lpage>100</lpage>.
                    <pub-id pub-id-type="pmid">21814628</pub-id>
                    <pub-id pub-id-type="pmcid">3146080</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-19">
                <label>19</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Paris</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Brandt</surname>
                            <given-names>C</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Cornu</surname>
                            <given-names>C</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Informed consent document improvement does not increase patients' comprehension in biomedical research.</article-title>
                    <source>

                        <italic toggle="yes">Br J Clin Pharmacol.</italic>
</source>
                    <year>2010</year>;<volume>69</volume>(<issue>3</issue>):<fpage>231</fpage>&#x2013;<lpage>237</lpage>.
                    <pub-id pub-id-type="pmid">20233193</pub-id>
                    <pub-id pub-id-type="doi">10.1111/j.1365-2125.2009.03565.x</pub-id>
                    <pub-id pub-id-type="pmcid">2829692</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-20">
                <label>20</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Mills</surname>
                            <given-names>EJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Seely</surname>
                            <given-names>D</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Rachlis</surname>
                            <given-names>B</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Barriers to participation in clinical trials of cancer: a meta-analysis and systematic review of patient-reported factors.</article-title>
                    <source>

                        <italic toggle="yes">Lancet Oncol.</italic>
</source>
                    <year>2006</year>;<volume>7</volume>(<issue>2</issue>):<fpage>141</fpage>&#x2013;<lpage>148</lpage>.
                    <pub-id pub-id-type="pmid">16455478</pub-id>
                    <pub-id pub-id-type="doi">10.1016/S1470-2045(06)70576-9</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-21">
                <label>21</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Eder</surname>
                            <given-names>ML</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Yamokoski</surname>
                            <given-names>AD</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Wittmann</surname>
                            <given-names>PW</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Improving informed consent: suggestions from parents of children with leukemia.</article-title>
                    <source>

                        <italic toggle="yes">Pediatrics.</italic>
</source>
                    <year>2007</year>;<volume>119</volume>(<issue>4</issue>):<fpage>e849</fpage>&#x2013;<lpage>59</lpage>.
                    <pub-id pub-id-type="pmid">17403829</pub-id>
                    <pub-id pub-id-type="doi">10.1542/peds.2006-2208</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-22">
                <label>22</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Smyth</surname>
                            <given-names>RM</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Jacoby</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Elbourne</surname>
                            <given-names>D</given-names>
                        </name>
</person-group>:
                    <article-title>Deciding to join a perinatal randomised controlled trial: experiences and views of pregnant women enroled in the Magpie Trial.</article-title>
                    <source>

                        <italic toggle="yes">Midwifery.</italic>
</source>
                    <year>2012</year>;<volume>28</volume>(<issue>4</issue>):<fpage>E478</fpage>&#x2013;<lpage>85</lpage>.
                    <pub-id pub-id-type="pmid">21944570</pub-id>
                    <pub-id pub-id-type="doi">10.1016/j.midw.2011.08.006</pub-id>
                </mixed-citation>
            </ref>
        </ref-list>
    </back>
    <sub-article article-type="reviewer-report" id="report21311">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.11349.r21311</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Himmelstein</surname>
                        <given-names>Daniel S.</given-names>
                    </name>
                    <xref ref-type="aff" rid="r21311a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-3012-7446</uri>
                </contrib>
                <aff id="r21311a1">
                    <label>1</label>Systems Pharmacology and Translational Therapeutics, Perelman School of Medicine, University of Pennsylvania, Philadelphia, PA, USA</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>11</day>
                <month>4</month>
                <year>2017</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2017 Himmelstein DS</copyright-statement>
                <copyright-year>2017</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport21311" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.10531.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>reject</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>Benchoufi&#x00a0;
                <italic>et al.</italic> propose and implement a method for notarizing participant consent for clinical trials using the Bitcoin blockchain. At a minimum, such an approach must accomplish two cryptographic objectives: 
                <list list-type="order">
                    <list-item>
                        <p>provide participants with a fraud-resistant&#x00a0;method to&#x00a0;irrefutably consent to the terms of a clinical trial.</p>
                    </list-item>
                    <list-item>
                        <p>provide clinical trial investigators with a method to retrospectively verify participant consent at a given point in time.</p>
                    </list-item>
                </list> I agree with the authors that cryptographically&#x00a0;notarizing consent would be a major advance. If possible, there would be strong incentives, both ethical and practical, for investigators to implement and regulatory agencies to mandate such an approach.</p>
            <p> </p>
            <p> By encoding a hash into the Bitcoin blockchain that derives from a "consent document", it is possible for investigators to timestamp a consent document and thereby retrospectively prove the existence of that consent document at a given point in time. However, I am not convinced that the study provides patients with a fraud-resistant, irrefutable method of consent. Specifically, I don't think the study provides a method for ensuring that a specific participant&#x00a0;provided consent. In other words, can clinical trial investigators prove that a specific participant consented rather than just proving that some entity consented under the supposed digital identify corresponding to a specific&#x00a0;participant?</p>
            <p> </p>
            <p> The study uses digital signatures to attest that a participant approved a specific consent form. The implementation relies on bitcoin private keys to provide digital signatures. The problem is that bitcoin addresses (which uniquely derive from a private key) are pseudonymous. For example, anyone with access to a consent form could create an unlimited number of bitcoin private keys and use these private keys to digitally sign the consent form. How does one prove that a bitcoin address solely belonged to a single participant?</p>
            <p> </p>
            <p> The generation of bitcoin private keys in this study occurs at 
                <ext-link ext-link-type="uri" xlink:href="https://git.io/vSPTE">https://git.io/vSPTE.</ext-link> I don't see anything in the code or manuscript that irrefutably links a participant to ownership of a given bitcoin address. Therefore, it appears to me that clinical trial investigators (or many other actors) could forge consent. In fact, the manuscript appears to concede this point with the statement:</p>
            <p> </p>
            <p> &gt;&#x00a0;Each of the to-be-enrolled users 
                <bold>
                    <italic>were assigned</italic>
                </bold> a private key in order to sign data and documents, and in practice this would be used to publish their signed consent.</p>
            <p> </p>
            <p> Linking digital identities to physical identities is difficult. However, this is a precondition to blockchain notarization of clinical trial consent. OpenPGP (the most established method for digital identity and signatures) relies on a web of trust model to link digital identities to physical identities. HTTPS relies on Certificate Authorities to link digital identities to organization identities.</p>
            <p> </p>
            <p> Since the manuscript does not sufficiently address how it links&#x00a0;digital and physical identities, I dug a bit deeper into Stratumn, the underlying service provider. 
                <ext-link ext-link-type="uri" xlink:href="https://stratumn.com/">Stratumn</ext-link> is a French company, which aims to "secure processes between partners through blockchain&#x00a0;technology."&#x00a0;Stratumn focuses on "proof of process" using a JSON data structure called 
                <ext-link ext-link-type="uri" xlink:href="http://chainscript.io/">chainscript</ext-link>.&#x00a0;I had difficulty uncovering the implementation details of&#x00a0;Stratumn's proof of process, as much of the available online material focuses on the implications of the technology rather than the technology itself. The&#x00a0;most helpful resource I found was the&#x00a0;
                <ext-link ext-link-type="uri" xlink:href="https://soundcloud.com/epicenterbitcoin/eb-159">Epicenter Podcast #159</ext-link>&#x00a0;titled "Richard Caetano &amp; Anuj Das Gupta: How Stratumn Secures Processes." This investigation did not answer how digital identities are linked to physical identities in Stratumn's services. The Stratumn proof-of-process 
                <ext-link ext-link-type="uri" xlink:href="https://stratumn.com/proof-of-process.html">white paper</ext-link>&#x00a0;
                <italic>does mention</italic> identity verification under "Non-Repudiation of Source and Destination", stating:</p>
            <p> </p>
            <p> &gt; Non-repudiation implies that the stakeholders of the information content of each and every step should not be able to deny their involvement with the steps representing their data through the digests. The tool we will use for this is Digital Signatures.</p>
            <p> </p>
            <p> &gt; Both Alice and Bob need to be responsible to their respective steps in such a way they they can not repudiate their involvement if challenged. The record of their identities would be maintained by having the stakeholders digitally sign the digest of their move and then storing the signatures and public keys along with the digest in the step. The private keys will not be stored in the steps; each player hold hers separately and securely. Anyone who has access to the proof can use the public key verification to ascertain whether or not Alice or Bob can be held responsible for a step.</p>
            <p> </p>
            <p> &gt; In this way we enable identity management and ownership in each and every step for the proof of a process to demonstrate the Who behind each and every step.</p>
            <p> </p>
            <p> Unfortunately, this description does not explain how digital identities are linked to physical identities. How does one know whether a digital signature is actually Alice or Bob's? Stratumn even 
                <ext-link ext-link-type="uri" xlink:href="https://stratumn.com/pdf/use-cases/Clinical-Trials.pdf">provides a document</ext-link> detailing the clinical trial consent use case. However, this document does not provide an identity solution.</p>
            <p> </p>
            <p> 
                <bold>Conclusion</bold>
            </p>
            <p> </p>
            <p> I am marking my review as 
                <italic>Not Approved</italic>. 
                <bold>If the authors can show that it is not trivial to forge a specific participant's consent, I would be happy to revisit my decision. However, absent a reliable method to link a digital identity to a participant's physical identity, there is little benefit to cryptographic notarization of clinical trial consent.</bold> Such an approach is only as useful as its most vulnerable step. At a minimum, the authors need to identify the trusted parties related to participant identity.</p>
            <p> </p>
            <p> 
                <bold>Minor points</bold>
            </p>
            <p> </p>
            <p> The study could do a better job citing the relevant cryptographic literature. For example, the study cites neither the 
                <ext-link ext-link-type="uri" xlink:href="https://bitcoin.org/bitcoin.pdf">Bitcoin white paper</ext-link> nor the 
                <ext-link ext-link-type="uri" xlink:href="https://stratumn.com/pdf/proof-of-process.pdf">proof-of-process white paper</ext-link>. In addition, the study should consider referencing 
                <ext-link ext-link-type="uri" xlink:href="https://arxiv.org/abs/1502.04015">OriginStamp</ext-link>,&#x00a0;
                <ext-link ext-link-type="uri" xlink:href="https://opentimestamps.org/">OpenTimestamps</ext-link>, and 
                <ext-link ext-link-type="uri" xlink:href="http://www.bgcarlisle.com/blog/2014/08/25/proof-of-prespecified-endpoints-in-medical-research-with-the-bitcoin-blockchain/">Carlisle's 2014 blog post</ext-link>.</p>
            <p> </p>
            <p> Figures 2 &amp; 3 are in French. I understand that it's important to show the consent form and interface as given to the participants. However, perhaps these should be supplements with English versions in the main text.</p>
            <p> </p>
            <p> The study states: "Smart contract: this is a contract that is algorithmically implemented and binds any change in the protocol to the patients&#x2019; consent seeking renewal." However, from my understanding the study does not propose any blockchain smart contracts. Instead, the Bitcoin blockchain is only used as a timestamping service.</p>
            <p> </p>
            <p> 
                <bold>Positives</bold>
            </p>
            <p> </p>
            <p> The study aims to replace trust with cryptography in medical research.</p>
            <p> </p>
            <p> The study makes its source code available under a permissive open source license on 
                <ext-link ext-link-type="uri" xlink:href="https://github.com/benchoufi/DocChain">GitHub</ext-link>&#x00a0;(
                <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5281/zenodo.237040">Zenodo archive</ext-link>).</p>
            <p> </p>
            <p> The study understands that directly writing every document hash to a secure &amp; immutable blockchain will be cost prohibitive, and therefore it is necessary to "group transactions", i.e. write one transactions that attests to the existence of many chainscript hashes.</p>
            <p>Reviewer Expertise:</p>
            <p>NA</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to state that I do not consider it to be of an acceptable scientific standard, for reasons outlined above.</p>
        </body>
        <sub-article article-type="response" id="comment2657-21311">
            <front-stub>
                <contrib-group>
                    <contrib contrib-type="author">
                        <name>
                            <surname>benchoufi</surname>
                            <given-names>mehdi</given-names>
                        </name>
                        <aff>Hotel-Dieu Hospital, Paris Descartes University, France</aff>
                    </contrib>
                </contrib-group>
                <author-notes>
                    <fn fn-type="conflict">
                        <p>
                            <bold>Competing interests: </bold>No competing interests were disclosed</p>
                    </fn>
                </author-notes>
                <pub-date pub-type="epub">
                    <day>19</day>
                    <month>4</month>
                    <year>2017</year>
                </pub-date>
            </front-stub>
            <body>
                <p>Dear&#x00a0;reviewer,&#x00a0;</p>
                <p> </p>
                <p> Thank you for drawing our attention on the questions you raised. Our answer focuses mainly on the issue related to the binding between digital identities and physical entities.&#x00a0;</p>
                <p> </p>
                <p> We updated the revised&#x00a0;version accordingly to all the questions you raised. &#x00a0;</p>
                <p> </p>
                <p> 
                    <bold>Target of the POC and digitale identities</bold>
                </p>
                <p> </p>
                <p> 
                    <italic>POC as a response to FDA raised issues</italic>
                </p>
                <p> </p>
                <p> Thank you for your constructive remarks. In fact, there are two main issues regarding the consent process. The first one is related to the quality of the process itself and the second one is related to the identity of the individual consenting. Monitoring of trials by the FDA has identified serious issues in about 10% of trials, major concerns being failure to obtain written informed consent, consent document not signed or not dated, missing pages in consent document provided to subjects,failure to re-consent when new information becomes available, use of expired, non-validated or unapproved forms (reference [3,4] in the manuscript and this 
                    <ext-link ext-link-type="uri" xlink:href="http://www.fda.gov/downloads/AboutFDA/CentersOffices/ CDER/UCM256376.pdf">link</ext-link>). In this POC study, we aimed at fighting these issues, where existing patients were included in a study in the presence of their physician or staff. In our implementation, we ensured that all the consent process was tracked in time all along the inclusion period, that the documents made available to the subjects were not corrupted, that they were in conformity with the current version of the protocol, and that (re-)consent was asked as many time as required. We however did not address the cases where consents were falsified by the investigating teams or where fake patients were invented for instance, which are more related to the second (identity) issue. This should be more explicit in the text, and has been emphasized in the revised manuscript. &#x00a0;</p>
                <p> </p>
                <p> 
                    <italic>Linking digital identities and physical entities</italic>
                </p>
                <p> </p>
                <p> We then agree with the reviewer that the second issue is important in the context of a real clinical trial. This relates to the question of pairing digital identification with physical persons. In our implementation of the POC study, the link between a participant and his/her digital identity is done through his/her email address. A participant cannot simply generate any Bitcoin address and use it to sign, because the private key is created on the server by the agent (but not saved on the server), then is sent to the email address. So the only guarantee is that the participant had access to that email address. This is pretty light, but seemed to be satisfactory given the scope and focus of the POC. Moreover, in the setting of a real online consent process, there is no chance that a patient who would not effectively consent&#x2014;for instance if there were some fraudulous operation registering him/her as a consenting subject&#x2014;would actually participate to the study.</p>
                <p> However, in a production application we must implement a more secure mechanism, and we thank the reviewer again for outlining the possibilities. There are indeed several solution to secure the digital identity of participants.</p>
                <p> </p>
                <p> First, we can mention that KYC processes are now quite widespread and there are plenty of examples where digital identities are linked to physical entities or human beings in the context of sensitive data: in most western countries the fiscal administration allows online service for taxpayers to declare their income and proceed to related operations, banking services also provides their services online such as bank transfer, account consultation. All these examples have in common that users (taxpayers, bank clients) are given a physical material, often by sending a document by regular postal service, or by giving a first card or document by hand. These documents carry an identification number. This approach could be implemented in production.</p>
                <p> </p>
                <p> Second, even in regular off-line consent process, ensuring that the patient really signed the document is not without carrying problems. We have in mind that the patient must meet the medical doctor and receive by hand their consent document. So that, when they go back to the medical doctor with the signed document, there is no way to prove that it was signed by the patients himself or that the patient was not influenced at the time of signing the consent form.</p>
                <p> Regarding a possible implementation of our blockchained consent process in a real clinical trial, we can provide, at the moment the patient meets the doctor, authentication cards with an identification number and so strengthen the binding between the electronic signature id and the physical one. Let&#x2019;s mention that some bitcoin companies also provide material keys, such as USB keys, that hold the cryptographic signature, which can be unlocked by an easy-to-remember code. This can be an excellent candidate to get stronger digital-physical binding. These issues are now covered in the revised discussion.</p>
                <p> </p>
                <p> Besides, we think that full online consent collection process raises more the issue to reach subjects that the one related to ensuring the targeted patient is really the one consenting.</p>
                <p> </p>
                <p> 
                    <italic>Patients invention</italic>
                </p>
                <p> </p>
                <p> Going further, we can summarily refer to the extreme case of patients invention. Unfortunately, there is almost no way to prevent data invention. And there are some documented case in the medical literature, fortunately very rare, where clinical trial patients and all related clinical data were invented from end to end. Let&#x2019;s notice here that, in the first implementation of our POC, we timestamped an extensive part of interactions between the subjects and the online email and web platform : time of the email sending, reception, time email was opened, the links being clicked on. We then validated the transactions into the blockchain, this way we could at least detect anomalies if such data appear grouped in time, so that it does not prevent from invention but higher the barrier to fraud. &#x00a0;</p>
                <p> </p>
                <p> 
                    <italic>Further technical improvements</italic>
                </p>
                <p> </p>
                <p> On a more technical side, Stratumn&#x2019;s technology, via proof-of-process, provide an implementation that would allow one to create an audit trail of the the different steps that happened until the participant provided enough evidence to convince the verifier of his/her identity, which is quite an upgrade to current KYC processes, because there would be a permanent record of what happened, and the process would impose rules that must be respected to the letter (by computer code) before moving to the next step. In short, this is not a complete out-of-the-box solution to linking digital identities, but Stratumn has the tools to build one. While implementing such a verification process with the technology is possible, this was beyond the scope of the POC.</p>
                <p> </p>
                <p> 
                    <bold>Smart Contracts</bold>
                </p>
                <p> </p>
                <p> Indeed, we did not implement it in our setting, we meant to mention that Smart Contract can bind the modifications occurred in the protocol and some to be defined events on which parties can agree. &#x00a0;</p>
                <p> Besides, we did not detail or implement in the article all the advantages that can be derived from the algorithmic nature of the Smart Contracts: the way consent process is monitored, the way the related informations are shared between the stakeholders, the investigators and the IRB or building Smart contracts with the condition patients will only be included when the enrolment is complete or building one checking the whole consistency between the data and the blockchained proof of data, preventing from the whole hassle of gathering the documents and checking them by hand</p>
                <p> </p>
                <p> </p>
                <p> 
                    <bold>Figures</bold>
                </p>
                <p> </p>
                <p> Indeed, some figures are in french and we complied to the F1000 policy that invited us to proceed so.</p>
                <p> </p>
                <p> 
                    <bold>Bibliography</bold>
                </p>
                <p> </p>
                <p> We thank the reviewer for the precious remarks about bibliography and to have brought to the knowledge of the authors two of them, namely the one referred as `OriginStamp` and the Carlisle blogpost. We add and referenced them in the revised document.</p>
                <p> </p>
                <p> </p>
                <p> Best regards,</p>
            </body>
        </sub-article>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report19560">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.11349.r19560</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Clarke</surname>
                        <given-names>Mike</given-names>
                    </name>
                    <xref ref-type="aff" rid="r19560a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-2926-7257</uri>
                </contrib>
                <aff id="r19560a1">
                    <label>1</label>Northern Ireland Methodology Hub, Centre for Public Health, Queen's University Belfast, Belfast, Ireland</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>I am involved in several initiatives to improve the quality and conduct of clinical trials.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>4</day>
                <month>4</month>
                <year>2017</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2017 Clarke M</copyright-statement>
                <copyright-year>2017</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport19560" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.10531.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>This is an important article, worthy of publication in F1000Research. There are some places in the article where the writing could be tidied up (e.g. references 1 and 10 are the same) but my main comments relate to questions that prompted in my mind, which the authors might wish to address if they revise it:</p>
            <p> </p>
            <p> Proof of concept, blockchain and the study generally 
                <list list-type="order">
                    <list-item>
                        <p>Is the reported study a "proof of concept" for the use in a real trial, or simply a demonstration that blockchain can be used for a series of sequential "signings"? If the latter, had that not been shown previously?</p>
                    </list-item>
                    <list-item>
                        <p>Are there any plans to test this in a real trial, perhaps as a SWAT[1] and to include it in Trial Forge[2]?</p>
                    </list-item>
                    <list-item>
                        <p>How would this system be used if patients cannot get online personally?</p>
                    </list-item>
                    <list-item>
                        <p>How would the system cope if someone's email addresses changes? (I raise this because I am currently locked out of my Twitter account because the email I used to set it up is no longer active following my move away from that institution.)</p>
                    </list-item>
                    <list-item>
                        <p>Can you reflect more on the challenges of doing online trials?</p>
                    </list-item>
                    <list-item>
                        <p>Do you believe that this system will be applicable to all trials, a majority or a minority? You seem very enthusiastic about the use of this system and the article might benefit from the addition of more caution about its general applicability. For example, you write "we evoked a possible improvement in the enrolment rate, by empowering patients and granting them information and control over the enrolment phase." but say little of the possible negatives (such as concerns about security of the data (see below); fear or discomfort with technology; and whether empowerment might come more from the ability to talk to a human being about the trial and the consent process).</p>
                    </list-item>
                    <list-item>
                        <p>Who will ensure that blockchain is future proof? Might people need to print or export a copy of the electronic record for long-term storage?</p>
                    </list-item>
                    <list-item>
                        <p>Does blockchain allow for "workarounds" (e.g. to move to the next step without completing the previous one if for some reason this is necessary)?</p>
                    </list-item>
                    <list-item>
                        <p>What do you mean by "transparency" in relation to the new system? If a potential participant thinks this means that others can see that they gave their consent, might this discourage them from joining the study?</p>
                        <p> </p>
                        <p> </p>
                        <p> Consent in general</p>
                    </list-item>
                    <list-item>
                        <p>How would this system cope with differences between the process for obtaining consent to take part in prospective research in different countries and cultures? For example, what if someone other than the patient might need to give consent?</p>
                    </list-item>
                    <list-item>
                        <p>Would patients be able to request that their ongoing consent is presumed without needing to be contacted again when there is a change in the trial? It might discourage patients from joining a trial if they are told that they will have to be contacted each time there is a change (especially if that change does not affect them personally).</p>
                    </list-item>
                    <list-item>
                        <p>What protocol changes should lead to new consent (e.g. should it only be those that directly affect the patient, or should it be those that might have influenced their decision to join?)</p>
                    </list-item>
                    <list-item>
                        <p>Would a patient need to be asked for their renewed consent if the change can no longer affect them? For example, if they have already completed treatment and are now on follow-up, do they need to be informed about changes in the evidence base about a side effect if they can no longer suffer that side effect?</p>
                    </list-item>
                    <list-item>
                        <p>Should patients be asked to consent again, or be asked if they want to withdraw? What assumption would be made if they do not reply?</p>
                    </list-item>
                    <list-item>
                        <p>Might it be worth discussing this new system in the context of other research into recruitment and retention (for example, as brought together in Cochrane Reviews [3,4,5,6]).</p>
                    </list-item>
                    <list-item>
                        <p>Is a lack of informed consent a source of bias (or might it be closer to the "truth" if patients don't realise that they are being studied) or bad ethical practice?</p>
                    </list-item>
                    <list-item>
                        <p>Might it be worth discussing the double standards of needing written consent for someone to receive a treatment in a trial but not needing it if they are given the treatment as part of "routine practice"?</p>
                    </list-item>
                    <list-item>
                        <p>How important is "written consent"? Is this unfair on difficult to reach populations who struggle to read or write?</p>
                        <p> </p>
                        <p> </p>
                        <p> Electronic consent</p>
                    </list-item>
                    <list-item>
                        <p>How would you ensure that the appropriate person "signed" the consent form if you do not see them do so? Is it easier to submit someone's electronic key, than to forge their signature?</p>
                        <p> </p>
                        <p> </p>
                        <p> Security</p>
                    </list-item>
                    <list-item>
                        <p>Might patients' concerns over the security of their data and the importance of confidentiality make them cautious about joining a trial if they had to use this system? How worried might they be because of news stories about data from banks and other supposedly secure systems being hacked and leaked?</p>
                    </list-item>
                    <list-item>
                        <p>Might it be worth writing something about how patients may think that paper consent forms locked in a filing cabinet are more difficult to access and make available to everyone online, than documents that are already available to the research team from anywhere on the internet.</p>
                        <p> </p>
                        <p> </p>
                        <p> Language</p>
                    </list-item>
                    <list-item>
                        <p>The words "subject" and "participant" are used to refer to people who take part in trials. I prefer to avoid "subject".</p>
                    </list-item>
                </list>
            </p>
            <p>Reviewer Expertise:</p>
            <p>NA</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard.</p>
        </body>
        <back>
            <ref-list>
                <title>References</title>
                <ref id="rep-ref-19560-1">
                    <label>1</label>
                    <mixed-citation publication-type="journal">
                        <person-group person-group-type="author"/>:
                        <article-title>The SWAT (study within a trial) programme; embedding trials to improve the methodological design and conduct of future research</article-title>.
                        <source>
                            <italic>Trials</italic>
                        </source>.<year>2015</year>;<volume>16</volume>(<issue>S2</issue>) :
                        <elocation-id>10.1186/1745-6215-16-S2-P209</elocation-id>
                        <pub-id pub-id-type="doi">10.1186/1745-6215-16-S2-P209</pub-id>
                    </mixed-citation>
                </ref>
                <ref id="rep-ref-19560-2">
                    <label>2</label>
                    <mixed-citation publication-type="journal">
                        <person-group person-group-type="author"/>:
                        <article-title>Making randomised trials more efficient: report of the first meeting to discuss the Trial Forge platform</article-title>.
                        <source>
                            <italic>Trials</italic>
                        </source>.<year>2015</year>;<volume>16</volume>(<issue>1</issue>) :
                        <elocation-id>10.1186/s13063-015-0776-0</elocation-id>
                        <pub-id pub-id-type="doi">10.1186/s13063-015-0776-0</pub-id>
                    </mixed-citation>
                </ref>
                <ref id="rep-ref-19560-3">
                    <label>3</label>
                    <mixed-citation publication-type="journal">
                        <person-group person-group-type="author"/>:
                        <article-title>Methods to improve recruitment to randomised controlled trials: Cochrane systematic review and meta-analysis.</article-title>
                        <source>
                            <italic>BMJ Open</italic>
                        </source>.<year>2013</year>;<volume>3</volume>(<issue>2</issue>) :
                        <elocation-id>10.1136/bmjopen-2012-002360</elocation-id>
                        <pub-id pub-id-type="pmid">23396504</pub-id>
                        <pub-id pub-id-type="doi">10.1136/bmjopen-2012-002360</pub-id>
                    </mixed-citation>
                </ref>
                <ref id="rep-ref-19560-4">
                    <label>4</label>
                    <mixed-citation publication-type="journal">
                        <person-group person-group-type="author"/>:
                        <article-title>Strategies to improve retention in randomised trials.</article-title>
                        <source>
                            <italic>Cochrane Database Syst Rev</italic>
                        </source>.<year>2013</year>;
                        <elocation-id>10.1002/14651858.MR000032.pub2</elocation-id>
                        <fpage>MR000032</fpage>
                        <pub-id pub-id-type="pmid">24297482</pub-id>
                        <pub-id pub-id-type="doi">10.1002/14651858.MR000032.pub2</pub-id>
                    </mixed-citation>
                </ref>
                <ref id="rep-ref-19560-5">
                    <label>5</label>
                    <mixed-citation publication-type="journal">
                        <person-group person-group-type="author"/>:
                        <article-title>Audio-visual presentation of information for informed consent for participation in clinical trials.</article-title>
                        <source>
                            <italic>Cochrane Database Syst Rev</italic>
                        </source>.<year>2014</year>;
                        <elocation-id>10.1002/14651858.CD003717.pub3</elocation-id>
                        <fpage>CD003717</fpage>
                        <pub-id pub-id-type="pmid">24809816</pub-id>
                        <pub-id pub-id-type="doi">10.1002/14651858.CD003717.pub3</pub-id>
                    </mixed-citation>
                </ref>
                <ref id="rep-ref-19560-6">
                    <label>6</label>
                    <mixed-citation publication-type="journal">
                        <person-group person-group-type="author"/>:
                        <article-title>Decision aids for people considering taking part in clinical trials.</article-title>
                        <source>
                            <italic>Cochrane Database Syst Rev</italic>
                        </source>.<year>2015</year>;
                        <elocation-id>10.1002/14651858.CD009736.pub2</elocation-id>
                        <fpage>CD009736</fpage>
                        <pub-id pub-id-type="pmid">26613337</pub-id>
                        <pub-id pub-id-type="doi">10.1002/14651858.CD009736.pub2</pub-id>
                    </mixed-citation>
                </ref>
            </ref-list>
        </back>
        <sub-article article-type="response" id="comment2656-19560">
            <front-stub>
                <contrib-group>
                    <contrib contrib-type="author">
                        <name>
                            <surname>benchoufi</surname>
                            <given-names>mehdi</given-names>
                        </name>
                        <aff>Hotel-Dieu Hospital, Paris Descartes University, France</aff>
                    </contrib>
                </contrib-group>
                <author-notes>
                    <fn fn-type="conflict">
                        <p>
                            <bold>Competing interests: </bold>No competing interests were disclosed</p>
                    </fn>
                </author-notes>
                <pub-date pub-type="epub">
                    <day>19</day>
                    <month>4</month>
                    <year>2017</year>
                </pub-date>
            </front-stub>
            <body>
                <p>
                    <bold>Proof of concept, blockchain and the study generally</bold>
                </p>
                <p> </p>
                <p> Dear reviewer,&#x00a0;</p>
                <p> </p>
                <p> Here are some responses to the questions that were raised. Besides, thank you for your remark related to the bibliography and the reference duplicate.&#x00a0;</p>
                <p> </p>
                <p> </p>
                <p> 1. 
                    <italic>Is the reported study a "proof of concept" for the use in a real trial, or simply a demonstration that blockchain can be used for a series of sequential "signings"? If the latter, had that not been shown previously?</italic>
                </p>
                <p> </p>
                <p> In the idea of establishing all the consent process in real conditions, we claim it is a proof of concept. We developed a complete and realistic set of interactions between fake patients and stakeholders, and we paired consent status and protocol revision through blockchain held by a single master document accounting for the whole process.</p>
                <p> </p>
                <p> 2. 
                    <italic>Are there any plans to test this in a real trial, perhaps as a SWAT[1] and to include it in Trial Forge[2]?</italic>
                </p>
                <p> </p>
                <p> For the moment, we have no specific plan to implement in a real trial but our POC is precisely a preparation to go further to a real setting.</p>
                <p> We have no expertise in SWAT or in using Trail Forge platform, but it should comply with no difficulty with our implementation.</p>
                <p> </p>
                <p> 3. 
                    <italic>How would this system be used if patients cannot get online personally?</italic>
                </p>
                <p> </p>
                <p> This is more a problem related to online consent than a blockchain related question. In situations where patients cannot get online personally, then the medical doctor should provide the consent form to the subjects by hand. Besides, let's indicate that in most countries, the written consent is legally mandatory.</p>
                <p> There are other situations where the online access is not possible, related for example to disabilities, then either the legal representative should be given access to the online consent form, or written consent should be sought.</p>
                <p> </p>
                <p> 4.
                    <italic> How would the system cope if someone's email addresses changes? (I raise this because I am currently locked out of my Twitter account because the email I used to set it up is no longer active following my move away from that institution.)</italic>
                </p>
                <p> </p>
                <p> In a real clinical trial, we would set multiple ways to reach a patient : digitally, phone number, postal mail. For sure, email is not sufficient, and we would use a stronger identifying system than email, i.e. material objects storing cryptographic keys, such as a USB key. We could also build a Smart Contract triggered by a destination email error callback. Then, when this condition is met, Smart Contract would cause the other reaching methods to be proceeded. Since Smart Contract are pieces of code, this automatized processed can be customized at will.</p>
                <p> However, although this is not the situation you are pointing to, this procedure may find a limit: there is no way to distinguish between the situation where an email has been sent without response, and the one where the email is still maintained by the institution with no access anymore for the previous account holder. But, we think this very case looks quite exceptional.</p>
                <p> </p>
                <p> 5. 
                    <italic>Can you reflect more on the challenges of doing online trials?</italic>
                </p>
                <p> </p>
                <p> There are some challenges regarding online trials:</p>
                <p> - people that are not in a condition to access an online platform: severe conditions, lack of consciousness, learning disability, no access to internet or people not friendly to online tools</p>
                <p> - the current state of technologies do not allow interventional trials. However, the explosion of IoT, miniaturization could lead to imagine some specific interventional trials to be conducted online. In this respect, we mention the existence of blockchain systems specifically dedicated to connected objects.</p>
                <p> - ensuring that the person consenting is effectively the one pretending to be: this should lead to use a strong identifier, and at minimum use KYC process (Know Your Customer) implemented to bind digital identities to physical entities in the case of sensitive data. Fiscal administration, Banks makes use of that.</p>
                <p> It is worth noting that from a blockchain point of view, the email is by no mean a method to identify. In our settings, we generate identifiers for each patient which consists in complex cryptographic strings. It would be possible in addition of these informations stored in the local machine of the subject, to duplicate this information on a USB key or identifier cards on the model of KYC procedure. Let's state that there are some companies providing material supports to keep the blockchain id's.</p>
                <p> </p>
                <p> 6. 
                    <italic>Do you believe that this system will be applicable to all trials, a majority or a minority? You seem very enthusiastic about the use of this system and the article might benefit from the addition of more caution about its general applicability. For example, you write "we evoked a possible improvement in the enrolment rate, by empowering patients and granting them information and control over the enrolment phase." but say little of the possible negatives (such as concerns about security of the data (see below); fear or discomfort with technology; and whether empowerment might come more from the ability to talk to a human being about the trial and the consent process).</italic>
                </p>
                <p> </p>
                <p> Indeed, blockchain is not without carrying some issues. Our point was to put in a perspective a trend. Every new technological gap raises some fears, as the internet at its very beginning, but the overall trend is that usages have imposed. It is worth noting that users shape also technologies and their fear pushes the improvement of technologies conducting these to take more account of their needs and apprehensions.</p>
                <p> Besides, our idea is not to rely on a technology by itself but to complete the blockchain network ability to ensure data consistency by a strong human support at any step of the clinical trial, first and foremost the consent process.</p>
                <p> Besides, from the data security point of view, we positively think that it is much better ensured by blockchain-like technologies than the one currently used : first, because of the strong crypto-oriented transaction validation, second the distributed nature of the network prevent from the "single point of failure" problem related to centralized data collection. By the way, we can take the Bitcoin network as an example, which carries sensitive money data and which is proving to be resistant for almost ten years.</p>
                <p> </p>
                <p> 7. 
                    <italic>Who will ensure that blockchain is future proof? Might people need to print or export a copy of the electronic record for long-term storage?</italic>
                </p>
                <p> </p>
                <p> Blockchain consist of a network of peers, anybody involved in the network storing in his computer the archive of all the history of transactions, i.e. the public ledger. So that, even if the network had to fail for one or other reason, any single node can restore the last state of the network. Moreover, if necessary, depending on the design of the blockchain implementation, we might enable the only stakeholders or if we want any participant, to export and print the copy of electronic transactions.</p>
                <p> We may have in mind that data stored are "proof of data" that can be checked to match the true data on any dedicated public website. &#x00a0;&#x00a0;&#x00a0;</p>
                <p> </p>
                <p> 8. 
                    <italic>Does blockchain allow for "workarounds" (e.g. to move to the next step without completing the previous one if for some reason this is necessary)?</italic>
                </p>
                <p> </p>
                <p> Yes, one core functionality of blockchain technologies, is Smart Contract. They allow to write algorithmically any set of conditions that modules the execution of some instructions.</p>
                <p> But, we stress the fact the system can be "fault-tolerant" but there are no "roll-back" possibility. So, suppose that someone stores some informations but has mistaken, then he'll be able to add the new corrected information (that's what we can call a "fork"), but the first errored information is still accessible in the blockchain.</p>
                <p> </p>
                <p> 9. 
                    <italic>What do you mean by "transparency" in relation to the new system? If a potential participant thinks this means that others can see that they gave their consent, might this discourage them from joining the study?</italic>
                </p>
                <p> </p>
                <p> We mean by transparency that the rules are clear for anybody taking part in the process. This is the very role of the Smart Contract we already mentioned.</p>
                <p> Besides, the perimeter of the people sharing the data can be controlled : we can decide that data can be shared by the only stakeholders, or decide that participants will be able to share access to their data with persons of trust. All this fine-grained control can be powered on the top of blockchain.</p>
                <p> </p>
                <p> 
                    <bold>Consent in general</bold>
                </p>
                <p> </p>
                <p> 10. 
                    <italic>How would this system cope with differences between the process for obtaining consent to take part in prospective research in different countries and cultures? For example, what if someone other than the patient might need to give consent?</italic>
                </p>
                <p> </p>
                <p> Differences between cultures, countries need to be tackled one by one. So that we need true implementation of clinical trials to face with those kinds of issues. I don&#x2019;t think there is a one general answer.</p>
                <p> Online tools can help orienting the participant regarding to their specific situation. Moreover, we believe chat support should be provided in order to take account of specific situations &#x00a0;</p>
                <p> </p>
                <p> 11. 
                    <italic>Would patients be able to request that their ongoing consent is presumed without needing to be contacted again when there is a change in the trial? It might discourage patients from joining a trial if they are told that they will have to be contacted each time there is a change (especially if that change does not affect them personally).</italic>
                </p>
                <p> </p>
                <p> Indeed, there is no need to overwhelm patients with a flood of informations. However, from a general point of view, patients association often complain about lack of informations regarding the clinical trial progress, so that some calibrated informations can be delivered conveniently to the patients. &#x00a0;</p>
                <p> Moreover, in case of a major change in the protocol, they should be specifically targeted to get an email asking to consent again. &#x00a0;</p>
                <p> </p>
                <p> 12. 
                    <italic>What protocol changes should lead to new consent (e.g. should it only be those that directly affect the patient, or should it be those that might have influenced their decision to join?)</italic>
                </p>
                <p> </p>
                <p> There is heavy litterature about this. We refer it in the article: [10,11,12] in our bibliograhy &#x00a0;and we mentionned these links detailing the protocol changes that should lead to renew the consent: http://www.irb.pitt.edu/sites/default/files/reconsent guidance.pdf; http://www.mayo.edu/research/documents/29-re-consent-or-notification-of-significant-new-findingspdf/doc-10027714; http://www.yale.edu/hrpp/policies/documents/Reconsentingguidance.pdf)</p>
                <p> </p>
                <p> 13. 
                    <italic>Would a patient need to be asked for their renewed consent if the change can no longer affect them? For example, if they have already completed treatment and are now on follow-up, do they need to be informed about changes in the evidence base about a side effect if they can no longer suffer that side effect?</italic>
                </p>
                <p> </p>
                <p> Yes, these kind of new informations should be given to patients and require to ask for a renewed consent again, even if they are not supposed to suffer this side effect thereafter. &#x00a0;&#x00a0;</p>
                <p> </p>
                <p> 14. 
                    <italic>Should patients be asked to consent again, or be asked if they want to withdraw? What assumption would be made if they do not reply?</italic>
                </p>
                <p> </p>
                <p> If patients want to withdraw, they should not be asked again.</p>
                <p> When patients do not reply, and after ensuring by other means (emails, mail, phone call if available) that they do not provide an answer, then they should be considered has consenting because they already gave their consent.</p>
                <p> Besides, this kind of situation can be advantageously scheduled in a Blockchain Smart Contract, that can be adapted to local legal contexts.</p>
                <p> </p>
                <p> 15. 
                    <italic>Might it be worth discussing this new system in the context of other research into recruitment and retention (for example, as brought together in Cochrane Reviews [3,4,5,6]).</italic>
                </p>
                <p> </p>
                <p> Indeed, we might implement some Smart Contracts, checking the recruitment and retention process. So Cochrane reviewers could have an insight about whether this process was done conformally to standard procedures. However, we notice that the code of the Smart Contract should also be reviewed, so that an experienced developer should be required.</p>
                <p> </p>
                <p> 16. 
                    <italic>Is a lack of informed consent a source of bias (or might it be closer to the "truth" if patients don't realise that they are being studied) or bad ethical practice?</italic>
                </p>
                <p> </p>
                <p> Lack of informed consent is for sure a bad ethical practice, in a strict contradiction to Helsinki declaration, Nuremberg declaration and good clinical practices.</p>
                <p> Regarding the matter of generalisability bias, the latter is more related to the setting of inclusive criteriae than related to consent.</p>
                <p> </p>
                <p> 17. 
                    <italic>Might it be worth discussing the double standards of needing written consent for someone to receive a treatment in a trial but not needing it if they are given the treatment as part of "routine practice"?</italic>
                </p>
                <p> </p>
                <p> In any case, the participant to a clinical trial must to sign the consent form, even he is already taking the medication for which the consent form is seeking his/her consent. At this occasion, the patients may be informed of actual informations related to the treatment, for example new side effects of a drug.</p>
                <p> </p>
                <p> 18. 
                    <italic>How important is "written consent"? Is this unfair on difficult to reach populations who struggle to read or write?</italic>
                </p>
                <p> </p>
                <p> The written status of the consent by opposition of the electronic has not by itself more credit. However, depending on the local legal context, &#x201c;written consent&#x201d; is mandatory.</p>
                <p> Besides, collecting consent of people with reading, writing or learning disabilities needs care. The person collecting the consent must assess the ability of the person to understand correctly the informations and to make a decision. The information must be given orally and to the legal representative if any. Some ethics committees allow the mediation of families or other supports at this stage.</p>
                <p> </p>
                <p> 
                    <bold>Electronic consent</bold>
                </p>
                <p> 19. 
                    <italic>How would you ensure that the appropriate person "signed" the consent form if you do not see them do so? Is it easier to submit someone's electronic key, than to forge their signature?</italic>
                </p>
                <p> </p>
                <p> In this POC, we generated cryptographic keys for each patient. So, in this design indeed, we can't ensure that the person consenting is the person he or she pretends to be. This can be improved in different manner.</p>
                <p> At least, using KYC standard procedures, i.e. doubling the electronic identification by one related to a physical object holding some number code. One step further would be to provide patients with an objects storing USB key storing the cryptographic signature and unlocked by a easy-to-remember id.</p>
                <p> </p>
                <p> 
                    <bold>Security</bold>
                </p>
                <p> 20. 
                    <italic>Might patients' concerns over the security of their data and the importance of confidentiality make them cautious about joining a trial if they had to use this system? How worried might they be because of news stories about data from banks and other supposedly secure systems being hacked and leaked?</italic>
                </p>
                <p> </p>
                <p> We refer to the question 6 on the notion of &#x201c;single point of failure&#x201d;, which answers at some level the raised issue.</p>
                <p> </p>
                <p> </p>
                <p> In any case, patients are very sensitive to the security and the privacy of their data and this system addresses precisely this issue. Indeed, the decentralized structure of the blockchain, the involvement of anyone as a peer on the network, the ability to finegrain the data sharing perimeter, allows more control of the patients over the data workflow.</p>
                <p> </p>
                <p> However, we are conscious that this system is very new and needs some pedagogical support. Anyway, Bitcoin is now a widespread, trusted electronic currency, available on payment platform of a wide range of websites such as Amazon, Apple&#x2019;s App Store. An implementation of such processes in a real clinical trial should be the occasion to add different media support : documents, videos in order to inform patient of the benefit of using such technologies .</p>
                <p> For the second part of the question, see the response to question 6. of the present reviewing question list. &#x00a0;&#x00a0;&#x00a0;&#x00a0;</p>
                <p> </p>
                <p> 21. 
                    <italic>Might it be worth writing something about how patients may think that paper consent forms locked in a filing cabinet are more difficult to access and make available to everyone online, than documents that are already available to the research team from anywhere on the internet.</italic>
                </p>
                <p> </p>
                <p> Absolutely it might be very interesting.</p>
                <p> </p>
                <p> 
                    <bold>Language</bold>
                </p>
                <p> 22. The words "subject" and "participant" are used to refer to people who take part in trials. I prefer to avoid "subject".</p>
                <p> </p>
                <p> We substituted the usage of "subjects" by "participants" in the revised document.</p>
                <p> </p>
                <p> Best regards,</p>
            </body>
        </sub-article>
    </sub-article>
</article>
