<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="reviewer-report"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIRx Med</journal-id><journal-id journal-id-type="publisher-id">xmed</journal-id><journal-id journal-id-type="index">34</journal-id><journal-title>JMIRx Med</journal-title><abbrev-journal-title>JMIRx Med</abbrev-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">v7i1e82612</article-id><article-id pub-id-type="doi">10.2196/82612</article-id><article-categories><subj-group subj-group-type="heading"><subject>Peer-Review Report</subject></subj-group></article-categories><title-group><article-title>Peer Review of &#x201C;Automating Individualized Notification of Drug Recalls to Patients: Complex Challenges and Qualitative Evaluation&#x201D;</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Marshall</surname><given-names>Robert Carter</given-names></name><xref ref-type="aff" rid="aff1"/></contrib></contrib-group><aff id="aff1"><institution>Madigan Army Medical Center</institution><addr-line>2001 28th Street Court NW</addr-line><addr-line>Gig Harbor</addr-line><addr-line>WA</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Hang</surname><given-names>Ching Nam</given-names></name></contrib></contrib-group><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>13</day><month>1</month><year>2026</year></pub-date><volume>7</volume><elocation-id>e82612</elocation-id><history><date date-type="received"><day>18</day><month>08</month><year>2025</year></date><date date-type="accepted"><day>18</day><month>08</month><year>2025</year></date></history><copyright-statement>&#x00A9; Robert Carter Marshall. Originally published in JMIRx Med (<ext-link ext-link-type="uri" xlink:href="https://med.jmirx.org">https://med.jmirx.org</ext-link>), 13.1.2026. </copyright-statement><copyright-year>2026</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 (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), 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 <ext-link ext-link-type="uri" xlink:href="https://med.jmirx.org/">https://med.jmirx.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://xmed.jmir.org/2026/1/e82612"/><related-article related-article-type="companion" ext-link-type="doi" xlink:href="10.1101/2024.09.18.24312141v1" xlink:title="Preprint (medRxiv)" xlink:type="simple">https://www.medrxiv.org/content/10.1101/2024.09.18.24312141v1</related-article><related-article related-article-type="companion" ext-link-type="doi" xlink:href="10.2196/82609" xlink:title="Authors' Response to Peer-Review Reports:" xlink:type="simple">https://med.jmirx.org/2026/1/e82609</related-article><related-article related-article-type="companion" ext-link-type="doi" xlink:href="10.2196/68345" xlink:title="Published Article" xlink:type="simple">https://med.jmirx.org/2026/1/e68345</related-article><kwd-group><kwd>notification system</kwd><kwd>drug recalls</kwd><kwd>patient safety</kwd><kwd>medication</kwd><kwd>electronic health records</kwd><kwd>prescriptions</kwd><kwd>decision support</kwd></kwd-group></article-meta></front><body><p><italic>This is a peer review report for &#x201C;Automating Individualized Notification of Drug Recalls to Patients: Complex Challenges and Qualitative Evaluation.&#x201D;</italic></p><sec id="s2"><title>Round 1 Review</title><sec id="s1-1"><title>General Comments</title><p>This paper [<xref ref-type="bibr" rid="ref1">1</xref>] describes a qualitative study that aims to leverage the US Food and Drug Administration (FDA)&#x2019;s Healthy Citizen prototype platform, which provides information about recalls, to automatically notify patients of relevant recalls.</p></sec><sec id="s1-2"><title>Specific Comments</title><sec id="s1-2-1"><title>Major Comments</title><list list-type="order"><list-item><p>Because of the setup of this document, it is challenging to add comments or do any editing. Not sure what happened, but it treated every line as a single object when opened in Microsoft Word. Please check your formatting.</p></list-item><list-item><p>On page 2, within the abstract, under Background, there is an error in the formatting. There should be a section that begins with Aim. Instead, that section is folded into the Background section and needs to be corrected.</p></list-item><list-item><p>On page 8, with the MyChart message, I can see why patients felt too much wording was in this layout. Surprisingly, the Patient Advisory Council agreed to this layout and the wordiness. The focus must be on the patient&#x2019;s needs, not what the FDA requires. We all have seen the Prescribers' Digital Reference, and we know that the information is too dense and too small. This is similar to that in terms of format. Enlarge the font, eliminate extraneous information, and only include information that is important to the patient and in simple English. This should be pretty feasible in the formatting of the Health Citizen and/or the MyChart message.</p></list-item><list-item><p>You identified problems and that patients would feel obligated to contact their provider regarding the recall. Instead of exploring how to address this so that patients wouldn&#x2019;t do that, thereby increasing the significant workload on the provider&#x2019;s health care team, you simply gave up. I think you could have done much more with this than say, &#x201C;oh, it can&#x2019;t be done.&#x201D; How could you word the MyChart to direct the patients only to the pharmacy that dispenses their medication instead of the primary care provider? If you didn&#x2019;t ask that question, you should have. This is not the time to give up. It&#x2019;s time to inquire more to find the right answers so that this could move forward and better serve both the patients and their providers.</p></list-item><list-item><p>It is certainly possible, given the technical requirements to create this capability, that you ran out of time and money. However, you can still benefit your team and others by focusing on the lessons learned and how you would go forward with another study.</p></list-item><list-item><p>One of the things that you did not do is a first round of qualitative testing and using that feedback to make changes and do a second round. Per Nielsen [<xref ref-type="bibr" rid="ref2">2</xref>], you only need about 5 test subjects per round to get the desired, usable results. What was preventing you from doing that? Put that in the manuscript as a limitation in your Discussion.</p></list-item><list-item><p>Also, on page 11, in the last paragraph of the page under Discussion, there is a comment regarding patients expecting their providers to know when a recall has occurred; I think we all know this is an unreasonable expectation. Part of the communication with the MyChart message is to inform the patients not to call their provider but to call the pharmacy that dispenses their medication, which should be right on the bottle. Again, one component of the MyChart portal messaging system, as well as any other portal messaging system, is to keep patients informed and educate them. That should be a focus of this project, just as much as the technical components.</p></list-item><list-item><p>On page 12, in the last full paragraph on the page, you make a statement regarding the project that a strong case can be made for requiring each pill bottle to include the lot number (maybe) and National Drug Code of the pills. Since the FDA was a component of this project, that should probably have been something you recommended for the FDA to require and not leave to the state boards of pharmacy, as then you would get a patchwork of regulations. This would require the FDA to say that lot numbers and National Drug Codes are required on the bottles of all medications with an appropriate implementation period to allow for appropriate software and hardware adjustments. That is just as valuable a recommendation out of the study as any other.</p></list-item></list></sec></sec></sec><sec id="s3"><title>Round 2 Review</title><sec id="s2-1"><title>General Comments</title><p>This paper describes a small qualitative study that aims to leverage the FDA&#x2019;s Healthy Citizen prototype platform, which provides information about recalls, to notify patients of relevant recalls automatically. The project team deemed the goal unattainable and provided limited lessons learned and recommendations for potential advocacy/future solutions.</p></sec><sec id="s2-2"><title>Specific Comments</title><sec id="s2-2-1"><title>Major Comments</title><list list-type="order"><list-item><p>On page 11, in the section/paragraph beginning with &#x201C;Major thematic findings included...&#x201D;: these are some of the lessons learned that I mentioned in my feedback.</p></list-item><list-item><p>On page 12, in the paragraph beginning with &#x201C;The project team concluded that...&#x201D;: The &#x201C;project team&#x201D; felt this. Did the Patient Advisory Council and the test subjects share the same feeling?</p></list-item><list-item><p>On page 13, in the second paragraph on the page, in the sentence beginning with &#x201C;Note that the FDA does not...&#x201D;: this would clearly be a lesson learned and could be advocated for via Congress and the Department of Health and Human Services.</p></list-item><list-item><p>On page 13, in the second paragraph, the next sentence, beginning with &#x201C;The manufacturer and lot number of dispensed medications...&#x201D;: agreed. See previous comment.</p></list-item></list></sec></sec></sec></body><back><fn-group><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">FDA</term><def><p>Food and Drug Administration</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Gadgil</surname><given-names>M</given-names> </name><name name-style="western"><surname>Pavlakos</surname><given-names>R</given-names> </name><name name-style="western"><surname>Carini</surname><given-names>S</given-names> </name><etal/></person-group><article-title>Automating individualized notification of drug recalls to patients: complex challenges and qualitative evaluation</article-title><source>JMIRx Med</source><year>2026</year><volume>7</volume><fpage>e68345</fpage><pub-id pub-id-type="doi">10.2196/68345</pub-id></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="web"><article-title>Nielsen Norman Group</article-title><source>Why you only need to test with 5 users</source><access-date>2025-10-14</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/</ext-link></comment></nlm-citation></ref></ref-list></back></article>