<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article article-type="article-commentary" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIRxMed</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIRx Med</journal-id>
      <journal-title>JMIRx Med</journal-title>
      <issn pub-type="epub">2563-6316</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v3i2e37323</article-id>
      <article-id pub-id-type="pmid"/>
      <article-id pub-id-type="doi">10.2196/37323</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Peer-Review Report</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Peer-Review Report</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Peer Review of “Patient Recommendations for the Content and Design of Electronic Returns of Genetic Test Results: Interview Study Among Patients Who Accessed Their Genetic Test Results via the Internet”</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Meinert</surname>
            <given-names>Edward</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="no">
          <collab>Anonymous</collab>
        </contrib>
      </contrib-group>
      <pub-date pub-type="collection">
        <season>Apr-Jun</season>
        <year>2022</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>31</day>
        <month>5</month>
        <year>2022</year>
      </pub-date>
      <volume>3</volume>
      <issue>2</issue>
      <elocation-id>e37323</elocation-id>
      <history>
        <date date-type="received">
          <day>15</day>
          <month>2</month>
          <year>2022</year>
        </date>
        <date date-type="accepted">
          <day>15</day>
          <month>2</month>
          <year>2022</year>
        </date>
      </history>
      <copyright-statement>© . Originally published in JMIRx Med (https://med.jmirx.org), 31.05.2022.</copyright-statement>
      <copyright-year>2022</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIRx Med, is properly cited. The complete bibliographic information, a link to the original publication on https://med.jmirx.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://med.jmirx.org/2022/2/e37323" xlink:type="simple"/>
      <related-article related-article-type="companion" id="preprint29706" ext-link-type="doi" xlink:href="https://doi.org/10.2196/preprints.29706" vol="3" page="e29706" xlink:title="Preprint:" xlink:type="simple">https://preprints.jmir.org/preprint/29706</related-article>
      <related-article related-article-type="companion" id="v3i2e37170" ext-link-type="doi" xlink:href="10.2196/37170" vol="3" page="e37170" xlink:title="Authors' Response to Peer-Review Reports:" xlink:type="simple">https://med.jmirx.org/2022/2/e37170/</related-article>
      <related-article related-article-type="companion" id="v3i2e29706" ext-link-type="doi" xlink:href="10.2196/29706" vol="3" page="e29706" xlink:title="Published Article:" xlink:type="simple">https://med.jmirx.org/2022/2/e29706/</related-article>
      <kwd-group>
        <kwd>user-centered design</kwd>
        <kwd>genomic medicine</kwd>
        <kwd>patient portals</kwd>
        <kwd>electronic health records</kwd>
        <kwd>return of results</kwd>
        <kwd>bioethics</kwd>
        <kwd>EHR</kwd>
        <kwd>genetics</kwd>
        <kwd>genetic testing</kwd>
        <kwd>patient preferences</kwd>
        <kwd>design</kwd>
        <kwd>human factors</kwd>
      </kwd-group>
      
    </article-meta>
  </front>
  <body>
    <p>
      <italic>This is a peer-review report submitted for the paper “Patient Recommendations for the Content and Design of Electronic Returns of Genetic Test Results: Interview Study Among Patients Who Accessed Their Genetic Test Results via the Internet."</italic>
    </p>
    <sec>
      <title>Round 1 Review</title>
      <sec>
        <title>General Comments</title>
        <p>This paper [<xref ref-type="bibr" rid="ref1">1</xref>] describes the results of an interview study of patients regarding preferences for receiving genetic test results through an electronic patient portal. All participants had already had a genetic test and were active users of their patient portal. Some suggestions/comments to consider to improve manuscript:</p>
      </sec>
      <sec>
        <title>Specific Comments</title>
        <sec>
          <title>Major Comments</title>
          <sec>
            <title>Introduction</title>
            <list list-type="order">
              <list-item>
                <p>The actual purpose and study rationale/goal of the study was not described until the middle of the <italic>Methods</italic> section (minus the abstract). At the end of the <italic>Introduction</italic>, no information about the study was provided, and so, I was a little lost when transitioning from the <italic>Introduction</italic> to the <italic>Methods</italic> section for a study that hadn’t been mentioned at all. The second sentence in the <italic>Data Collection</italic> section could be moved up as the last sentence of the Introduction.</p>
              </list-item>
              <list-item>
                <p>Toward the end of the <italic>Introduction</italic>, the inclusion about barriers to the utilization of patient portals is very broad and not specific to genetics. I would suggest limiting it to genetic test results.</p>
              </list-item>
            </list>
          </sec>
          <sec>
            <title>Methods</title>
            <list list-type="order">
              <list-item>
                <p>Perhaps include a <italic>Study Overview</italic> section before <italic>Participant Recruitment</italic> if you do not wish to introduce the study in the <italic>Introduction</italic>.</p>
              </list-item>
              <list-item>
                <p>Either provide the semistructured interview guide or provide more detail about the content and structure (eg, funnel approach?).</p>
              </list-item>
              <list-item>
                <p>There is no mention of the analysis of content-related themes in the <italic>Data Analysis</italic> section.</p>
              </list-item>
            </list>
          </sec>
          <sec>
            <title>Results</title>
            <list list-type="order">
              <list-item>
                <p>Confirm whether the patient demographics were the same for both study groups. Perhaps redo the table to include a breakdown of demographics between the two groups.</p>
              </list-item>
              <list-item>
                <p>Clarify if the content recommendations came from the group that was asked to compare their experiences receiving genetic vs nongenetic test results through a patient portal.</p>
              </list-item>
              <list-item>
                <p>Did you conduct any analysis to factor in patients’ background (eg, education, gender, age) or the specific type of experience with genetic testing to provide some context of their responses?</p>
              </list-item>
              <list-item>
                <p>Without a better understanding of what the questions were, it is not totally clear if the questions were totally open-ended or if you asked them to provide feedback on specific suggestions (like the summary sheet). I assume the questions were more open-ended, given the data analysis description, but the results appear to be narrowly confined.</p>
              </list-item>
              <list-item>
                <p>It seems to me that design recommendation #3 about smartphone functionality is not specific to genetics and should not be reported as a recommendation.</p>
              </list-item>
              <list-item>
                <p>Some confusion about recommendations—is a simple coversheet (design recommendation #1) the same as an electronic summary (design recommendation #2) and a patient-friendly results summary (domain 2 subheading, content recommendations #2-#4).</p>
              </list-item>
            </list>
          </sec>
          <sec>
            <title>Discussion</title>
            <list list-type="order">
              <list-item>
                <p>Include some discussion of the implementation of the recommendations. Many would take considerable time to complete for multiple testing vendors/lab reports. Are they really feasible? Do you anticipate that the laboratories will do some of this work or will it fall to test orderer? </p>
              </list-item>
              <list-item>
                <p>In the section <italic>Comparison to Prior Work</italic>, I would suggest including more discussion about the format and design of current lab reports. Many are made available through labs on their websites. It is difficult to generalize lab reports for different indications/purposes and come up with a best fit with respect to design/formatting. Certainly, patient feedback will be valuable for learning how to improve the comprehension of genetic testing lab reports. Many results cannot be analyzed without the consideration of more clinical information. Test reports are intended for health providers, and thus the style, jargon, and information will understandably differ for patients. The authors should consider reviewing reports intended for patients (eg, 23andMe), which are delivered electronically.</p>
              </list-item>
            </list>
          </sec>
        </sec>
        <sec>
          <title>Minor Comments</title>
          <list list-type="order">
            <list-item>
              <p>Remove the extra numbers outside at the bottom of table.</p>
            </list-item>
          </list>
        </sec>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Korngiebel</surname>
              <given-names>DM</given-names>
            </name>
            <name name-style="western">
              <surname>West</surname>
              <given-names>KM</given-names>
            </name>
          </person-group>
          <article-title>Patient recommendations for the content and design of electronic returns of genetic test results: Interview study among patients who accessed their genetic test results via the internet</article-title>
          <source>JMIRx Med</source>
          <year>2022</year>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>e29706</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://med.jmirx.org/2022/2/e29706/"/>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
