<?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="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Form Res</journal-id><journal-id journal-id-type="publisher-id">formative</journal-id><journal-id journal-id-type="index">27</journal-id><journal-title>JMIR Formative Research</journal-title><abbrev-journal-title>JMIR Form Res</abbrev-journal-title><issn pub-type="epub">2561-326X</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">v9i1e68906</article-id><article-id pub-id-type="doi">10.2196/68906</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Exploratory Co-Design on Electronic Health Record Nursing Summaries: Case Study</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Park</surname><given-names>Suhyun</given-names></name><degrees>PhD, RN</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Marquard</surname><given-names>Jenna L</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Austin</surname><given-names>Robin R</given-names></name><degrees>PhD, DNP, DC, RN, NI-BC</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Martin</surname><given-names>Christie L</given-names></name><degrees>PhD, MPH, RN-BC</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Pieczkiewicz</surname><given-names>David S</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Delaney</surname><given-names>Connie W</given-names></name><degrees>PhD, RN</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib></contrib-group><aff id="aff1"><institution>Cizik School of Nursing, The University of Texas Health Science Center at Houston</institution><addr-line>#557, 6901 Bertner Ave</addr-line><addr-line>Houston</addr-line><addr-line>TX</addr-line><country>United States</country></aff><aff id="aff2"><institution>School of Nursing, University of Minnesota</institution><addr-line>Minneapolis</addr-line><addr-line>MN</addr-line><country>United States</country></aff><aff id="aff3"><institution>Institute for Health Informatics, University of Minnesota</institution><addr-line>Minneapolis</addr-line><addr-line>MN</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Mavragani</surname><given-names>Amaryllis</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Kuusisto</surname><given-names>Anne</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Alshammari</surname><given-names>Moustafa</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Suhyun Park, PhD, RN, Cizik School of Nursing, The University of Texas Health Science Center at Houston, #557, 6901 Bertner Ave, Houston, TX, 77030, United States, 1 713-500-2246; <email>Suhyun.Park@uth.tmc.edu</email></corresp></author-notes><pub-date pub-type="collection"><year>2025</year></pub-date><pub-date pub-type="epub"><day>11</day><month>3</month><year>2025</year></pub-date><volume>9</volume><elocation-id>e68906</elocation-id><history><date date-type="received"><day>19</day><month>11</month><year>2024</year></date><date date-type="rev-recd"><day>15</day><month>02</month><year>2025</year></date><date date-type="accepted"><day>19</day><month>02</month><year>2025</year></date></history><copyright-statement>&#x00A9; Suhyun Park, Jenna L Marquard, Robin R Austin, Christie L Martin, David S Pieczkiewicz, Connie W Delaney. Originally published in JMIR Formative Research (<ext-link ext-link-type="uri" xlink:href="https://formative.jmir.org">https://formative.jmir.org</ext-link>), 11.3.2025. </copyright-statement><copyright-year>2025</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 JMIR Formative Research, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://formative.jmir.org">https://formative.jmir.org</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://formative.jmir.org/2025/1/e68906"/><abstract><sec><title>Background</title><p>Although electronic health record nursing summaries aim to provide a concise overview of patient data, they often fall short of meeting nurses&#x2019; information needs, leading to underutilization. This gap arises from a lack of involvement of nurses in the design of health information technologies.</p></sec><sec><title>Objective</title><p>The purpose of this exploratory co-design case study was to solicit insights from nurses regarding nursing summary design considerations, including key information types and the preferred design prototype.</p></sec><sec sec-type="methods"><title>Methods</title><p>We recruited clinical nurses (N=33) from 7 inpatient units at a university hospital in the Midwestern United States using a purposive sampling method. We used images from a simulated nursing summary to generate visual card versions of the 46 information types currently included in an electronic health record vendor&#x2013;generated nursing summary. Participants selected which cards to include and arranged them in their designs based on their perceived relevance of the information types to the summary and their preferred reading layout. The nurses&#x2019; perceived relevance of information types to the summary was analyzed by quantifying the frequency of included cards, while the nurses&#x2019; preferred reading layout was analyzed by quantifying the occurrence of closely paired cards to identify common groupings. After participants evaluated the information type cards, debriefing interviews were conducted and analyzed thematically to explore their rationales for the desired content and its arrangement.</p></sec><sec sec-type="results"><title>Results</title><p>The participants demonstrated a high level of engagement in the activities. On average, all 33 participants included 61% (n=28) of the total information types (n=46). The most frequently included cards were &#x201C;unit specimen&#x201D; (results of the analysis of body fluid, tissue, or urine), &#x201C;activity,&#x201D; &#x201C;diet,&#x201D; and &#x201C;hospital problems,&#x201D; each included by 33 participants. Participants most frequently preferred adjacency of the following pairs: &#x201C;activity&#x201D; and &#x201C;diet&#x201D; (paired by 26 participants; 79%) and &#x201C;notes to physicians&#x201D; and &#x201C;notes to treatment team&#x201D; (paired by 25 participants; 76%). Participants preferred arranging the cards to improve information accessibility, focusing on key information types.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>Involving nurses in the co-design process may result in more useful and usable designs, thereby reducing the time required to navigate nursing summaries. Future work should include refining and evaluating prototypes based on the designs created by the nurses.</p></sec></abstract><kwd-group><kwd>electronic health records</kwd><kwd>interview</kwd><kwd>nurses</kwd><kwd>user-computer interface</kwd><kwd>co-design</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><sec id="s1-1"><title>Background</title><p>Ineffective communication among clinicians is a leading cause of sentinel events, such as falls and delays in treatments [<xref ref-type="bibr" rid="ref1">1</xref>]. Given time constraints, nurses review vast amounts of patient information in electronic health records (EHRs) at the beginning of each shift; thus, effective tools for summarizing patient information are crucial [<xref ref-type="bibr" rid="ref2">2</xref>]. Nursing summaries in EHRs are intended to provide a concise overview of essential patient data (eg, vital signs, intake and output, weight) on a single page, but rigid and incomplete formats have led to underutilization [<xref ref-type="bibr" rid="ref3">3</xref>], resulting in nurses developing highly variable methods, such as paper notes, for summarizing patient information.</p><p>End-users are involved in the EHR development phase to prevent low usability and support optimal EHR utilization [<xref ref-type="bibr" rid="ref4">4</xref>]. Co-design (or participatory design) has gained attention as a strategy to integrate stakeholder viewpoints, bridging the gap between tools and users&#x2019; needs to ensure the long-term adoption of tools [<xref ref-type="bibr" rid="ref5">5</xref>]. Co-design aims to actively involve potential user groups in designing tools and interventions, leveraging their lived experiences to tailor outputs to their expressed needs and preferences, while aligning with existing workflows and available resources [<xref ref-type="bibr" rid="ref6">6</xref>]. In health care, co-design has been applied across various settings and user groups, including in the creation of predictive analytics dashboards and decision support systems to enhance care quality and client outcomes in aged care [<xref ref-type="bibr" rid="ref6">6</xref>]. Co-design has also been used to examine clinical nurses&#x2019; general ideas about information display design in a nursing summary [<xref ref-type="bibr" rid="ref2">2</xref>] and to develop a mobile health application to assist patients with obesity in self-managing their preparation for elective surgery [<xref ref-type="bibr" rid="ref7">7</xref>].</p><p>The use of information cards as a tool for stakeholder engagement is an approach adopted by designers to structure the co-design ideation process [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. Card sorting, a prevalent user-centered design technique, actively involves participants categorizing labeled cards based on criteria that most resonate with them [<xref ref-type="bibr" rid="ref10">10</xref>]. Card sorting offers numerous benefits, including facilitating the organization of complex information into intuitive groupings, promoting consensus building among diverse user groups, enhancing the user experience by ensuring content and functionality are logically structured, and providing valuable insights into users&#x2019; preferences and priorities [<xref ref-type="bibr" rid="ref11">11</xref>]. Although we did not fully follow the card sorting technique, we adapted key principles from the card sorting method, such as labeling and analyzing the arrangement of cards, to suit this study context. This exploratory research focused on nurses&#x2019; perceived usability and their feedback to inform nursing summary design strategies. The design strategies informed by nurse users&#x2019; input could streamline navigational pathways, thereby reducing cognitive load. This aligns with the goals of the National Burden Reduction Collaborative, which unites health care organizations, federal agencies, and standards organizations to reduce clinical burden nationwide [<xref ref-type="bibr" rid="ref12">12</xref>].</p></sec><sec id="s1-2"><title>Problem Statement</title><p>Nurses&#x2019; participation in EHR design is often limited, despite their role as key users [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref13">13</xref>]. A deeper understanding of their unique requirements and suggestions for EHR design is needed. Recognizing the pivotal role of end-user involvement in design [<xref ref-type="bibr" rid="ref5">5</xref>], we used a co-design activity to examine nurses&#x2019; perspectives on the use and arrangement of information types (eg, vital signs, intake and output, weight) within an existing EHR vendor&#x2019;s nursing summary. Specifically, the co-design activity aimed to gain insights into nurses&#x2019; perspectives on nursing summary design, including which information types to include and how to arrange the information types.</p></sec></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Study Design</title><p>This was an exploratory, single session of co-design activities that gathered nurses&#x2019; feedback and identified their design preferences. Although conducted independently, this study was part of an eye-tracking simulation, which focused on examining nurses&#x2019; visual attention to EHR nursing summary information types (submitted to another journal).</p></sec><sec id="s2-2"><title>Participants and Recruitment</title><p>We recruited participants from 5 adult medical-surgical and 2 intermediate care units at a university hospital using a purposive sampling method. We aimed to recruit 30 or more participants, as this is recommended for eye-tracking simulations. These units used the same summary layout as the example summary employed in this study. To be included, participants must have had at least 12 months of experience as a registered nurse. We excluded nurses who were not in frontline patient care, such as nurse educators, nurse managers, and nurse research coordinators. Recruitment was facilitated by nurse managers, who distributed email flyers providing details about the study.</p></sec><sec id="s2-3"><title>Data Collection</title><p>Participants were individually invited to a shared research space from August to September 2023. We used a nursing summary from a simulated patient case on a training platform that mirrored the EHR system used by the recruiting hospital. Since the hospital had used the Epic EHR system (Epic Systems) since 2011, we assumed all participants were familiar with its layout. The EHR vendor&#x2013;generated nursing summary included 46 information types (eg, vital signs, intake and output, weight). We printed and cut out cards for each information type so the participants could move them around as they liked (<xref ref-type="fig" rid="figure1">Figure 1</xref>). See <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> for the full original nursing summary layout and <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> for details of the information types. A lead researcher (SP) conducted all co-design activities independently, while a co-author (JLM) who is a human factors expert provided guidance on the study design and monitored the co-design activities after each session.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Example of an information type card. Each information type card used a consistent design, including a colored boundary, heading, and optional content.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="formative_v9i1e68906_fig01.png"/></fig><p>First, each participant reviewed each information type card to determine whether it was important enough to be included in the summary. Participants then arranged the included cards they wanted to present in the nursing summary on a desk to develop their preferred layout for the nursing summary screen. We clarified that the focus of the study was on determining the relevance of specific types of information (ie, social determinants of health) in the context of a nursing summary and arranging them, rather than the graphical design or the content of the information within the cards. We photographed each participant&#x2019;s design prototype for subsequent analysis. <xref ref-type="fig" rid="figure2">Figure 2</xref> shows an example of a design prototype created by one participant. Following the activity, a debriefing interview was conducted to collect feedback, and each conversation was audio-recorded via Zoom for subsequent transcription and analysis. Participants were prompted with the following guided questions: (1) explain your reasoning process in relation to the design layout; (2) discuss any specific considerations you made regarding information arrangement; and (3) offer any additional comments on your design.</p><p>We collected demographic information through a survey administered after the debriefing interviews.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>A sample summary design prototype by a participant. The layout shows the information types to include and their preferred arrangement.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="formative_v9i1e68906_fig02.png"/></fig></sec><sec id="s2-4"><title>Ethical Considerations</title><p>The study protocol was approved by the University of Minnesota Institutional Review Board (STUDY00018047). The principal investigator (SP) provided verbal and written information about the study to the participants and obtained verbal consent, as the requirement for written consent was waived. All data collected during the study were deidentified and securely stored in a university cloud-based storage system. The audio recordings and transcripts were deleted after the data analysis was completed. As this study was a part of an eye-tracking simulation, participants received a US $65 gift card for their time and effort upon completing all activities.</p></sec><sec id="s2-5"><title>Data Analysis</title><p>We evaluated the relevance of each information type to the summary by quantifying the number of nurses who chose to include the information type card in the design output. We then quantified the frequency of card pairs to identify which information type cards nurses tended to place next to each other in their design prototype, providing insights into the cohesive grouping of information [<xref ref-type="bibr" rid="ref11">11</xref>]. One researcher (SP) reviewed the deidentified transcripts of the debriefing interviews for accuracy and coded for thematic analysis. The codes and overarching themes were reviewed in weekly meetings with another researcher (JLM).</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Sample Characteristics</title><p>The characteristics of the 33 participants are presented in <xref ref-type="table" rid="table1">Table 1</xref>. More than half (n=19, 58%) of the participants were 25&#x2010;44 years old, 85% (n=28) were female, 76% (n=25) were White, and none were Hispanic. Most nurses included in this analysis had at least a baccalaureate degree related to nursing (n=30, 91%). The participants generally had fewer years of nursing experience and worked fewer hours compared to a representative sample of national nurses (median=13 years and median=37 hours, respectively) [<xref ref-type="bibr" rid="ref14">14</xref>].</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Baseline characteristics of the participants (N=33).</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Characteristic</td><td align="left" valign="bottom">Value</td></tr></thead><tbody><tr><td align="left" valign="top">Age (years), n (%)</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top">&#x2003;18&#x2010;24</td><td align="left" valign="top">9 (27)</td></tr><tr><td align="left" valign="top">&#x2003;25&#x2010;44</td><td align="left" valign="top">19 (58)</td></tr><tr><td align="left" valign="top">&#x2003;45&#x2010;64</td><td align="left" valign="top">5 (15)</td></tr><tr><td align="left" valign="top">&#x2003;&#x2265;65</td><td align="left" valign="top">0 (0)</td></tr><tr><td align="left" valign="top">Sex, n (%)</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top">&#x2003;Male</td><td align="left" valign="top">5 (15)</td></tr><tr><td align="left" valign="top">&#x2003;Female</td><td align="left" valign="top">28 (85)</td></tr><tr><td align="left" valign="top">&#x2003;Other</td><td align="left" valign="top">0 (0)</td></tr><tr><td align="left" valign="top">Race, n (%)</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top">&#x2003;Black or African American</td><td align="left" valign="top">5 (15)</td></tr><tr><td align="left" valign="top">&#x2003;White</td><td align="left" valign="top">25 (76)</td></tr><tr><td align="left" valign="top">&#x2003;Asian</td><td align="left" valign="top">2 (6)</td></tr><tr><td align="left" valign="top">&#x2003;Native American or Alaskan</td><td align="left" valign="top">0 (0)</td></tr><tr><td align="left" valign="top">&#x2003;Other</td><td align="left" valign="top">0 (0)</td></tr><tr><td align="left" valign="top">&#x2003;Prefer not to say</td><td align="left" valign="top">1 (3)</td></tr><tr><td align="left" valign="top">Ethnicity, n (%)</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top">&#x2003;Hispanic or Latinx</td><td align="left" valign="top">0 (0)</td></tr><tr><td align="left" valign="top">&#x2003;Non-Hispanic</td><td align="left" valign="top">33 (100)</td></tr><tr><td align="left" valign="top">&#x2003;Other</td><td align="left" valign="top">0 (0)</td></tr><tr><td align="left" valign="top">Relationship status, n (%)</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top">&#x2003;Single</td><td align="left" valign="top">14 (42)</td></tr><tr><td align="left" valign="top">&#x2003;Married</td><td align="left" valign="top">14 (42)</td></tr><tr><td align="left" valign="top">&#x2003;Partnered</td><td align="left" valign="top">2 (6)</td></tr><tr><td align="left" valign="top">&#x2003;Divorced</td><td align="left" valign="top">2 (6)</td></tr><tr><td align="left" valign="top">&#x2003;Separated</td><td align="left" valign="top">1 (3)</td></tr><tr><td align="left" valign="top">Highest nursing degree, n (%)</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top">&#x2003;Diploma</td><td align="left" valign="top">3 (9)</td></tr><tr><td align="left" valign="top">&#x2003;BSN</td><td align="left" valign="top">28 (85)</td></tr><tr><td align="left" valign="top">&#x2003;MS or MSN</td><td align="left" valign="top">2 (6)</td></tr><tr><td align="left" valign="top">&#x2003;PhD or DNP</td><td align="left" valign="top">0 (0)</td></tr><tr><td align="left" valign="top">Hours worked per week, median (IQR)</td><td align="left" valign="top">36 (30-36)</td></tr><tr><td align="left" valign="top">Years of registered nurse experience, median (IQR)</td><td align="left" valign="top">4 (1.5-8)</td></tr><tr><td align="left" valign="top">Years of using electronic health records, median (IQR)</td><td align="left" valign="top">4 (1.5-8)</td></tr></tbody></table></table-wrap></sec><sec id="s3-2"><title>Card Frequency</title><p>On average, participants included 28 of the 46 information type cards in their design prototypes. Notably, all participants (N=33) included &#x201C;unit specimen&#x201D; (results of the analysis of body fluid, tissue, or urine), &#x201C;hospital problems,&#x201D; &#x201C;diet,&#x201D; and &#x201C;activity&#x201D; in their design prototype (<xref ref-type="fig" rid="figure3">Figure 3</xref>). However, certain information type cards were included less frequently: fewer than 50% of participants included 15 of the information type cards, and fewer than 10 participants included &#x201C;key history and social determinants&#x201D; (n=9), &#x201C;about me&#x201D; (individualized notes) (n=8), &#x201C;intravenous pump settings&#x201D; (n=7), &#x201C;patient history notes&#x201D; (n=3), and &#x201C;scale and screen documentation&#x201D; (n=2).</p><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>Frequency of included cards. Participants selected information type cards that they think are relevant to include in nursing summaries. EKG: electrocardiogram; Hgb: hemoglobin; INR: international normalized ratio; IO: intake and output; IV: intravenous; LDA: lines, drains, and airways; POCT: point-of-care testing; SDOH: social determinants of health; WBC: white blood cell.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="formative_v9i1e68906_fig03.png"/></fig></sec><sec id="s3-3"><title>Card Adjacency</title><p><xref ref-type="fig" rid="figure4">Figure 4</xref> shows the number of participants who placed each pair of information type cards next to each other in their design. Darker shading was used to highlight cells where 2 information type cards were located next to each other more frequently. The pairs of information type cards located next to each other most frequently were &#x201C;activity&#x201D; and &#x201C;diet&#x201D; (n=26, 79%), followed by &#x201C;notes to physicians&#x201D; and &#x201C;notes to treatment team&#x201D; (n=25, 76%). Other pairs of cards that were placed next to each other included &#x201C;orders&#x201D; and &#x201C;hospital problems&#x201D; (n=16, 48%) and &#x201C;orders&#x201D; and &#x201C;vital signs&#x201D; (n=16, 48%). &#x201C;Orders&#x201D; and &#x201C;hospital problems,&#x201D; and &#x201C;orders&#x201D; and &#x201C;vital signs&#x201D; are not located next to each other in the current EHR design.</p><fig position="float" id="figure4"><label>Figure 4.</label><caption><p>Item-by-item matrix of card adjacency. The frequency of adjacency was manually counted when 2 cards were placed next to each other with no third card in between. EKG: electrocardiogram; Hgb: hemoglobin; INR: international normalized ratio; IO: intake and output; IV: intravenous; LDA: lines, drains, and airways; POCT: point-of-care testing; SDOH: social determinants of health; WBC: white blood cell.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="formative_v9i1e68906_fig04.png"/></fig></sec><sec id="s3-4"><title>Interview Findings</title><p><xref ref-type="table" rid="table2">Table 2</xref> presents themes, subthemes, and exemplary quotes derived from the debriefing interviews. The participants emphasized the importance of readability in their design choices, opting for a layout that facilitates top-to-bottom reading of key information based on priority. They noted that grouping related information together would facilitate information scanning. They also prioritized identifying immediate action items (eg, physicians&#x2019; orders) over delving into patient characteristics, such as social determinants of health. Owing to the typical time constraints needed to review patient information at the beginning of a shift, participants removed redundant information cards that hindered a swift and effective patient overview. Last, beyond the given design layout, participants provided design-related commentaries, pointing out that some information types required unnecessary clicks to get to the desired information, which limited usability.</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Common themes, subthemes, and supporting quotes from debriefing sessions based on their co-design activities, uncovering participants&#x2019; reasoning process and design considerations.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Themes and subthemes</td><td align="left" valign="bottom">Quotes</td></tr></thead><tbody><tr><td align="left" valign="top">Improving information accessibility</td><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Key information positioned upward</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;I have it from top to bottom. So it&#x2019;s the least important thing towards the bottom.&#x201D; [P11]</p></list-item><list-item><p>&#x201C;Diet is not as important, so I kept it going to the bottom.&#x201D; [P24]</p></list-item><list-item><p>&#x201C;I usually place it at the top of the page, not necessarily because it&#x2019;s important, but because it needs to be visible for everyone to see&#x2026;Otherwise, no one else will notice it. Not everyone will scroll down.&#x201D; [P4]</p></list-item><list-item><p>&#x201C;Most important would be at like the top, in a top-down order.&#x201D; [P1]</p></list-item><list-item><p>&#x201C;I like that the orders are at the top because they&#x2019;re the most important; they&#x2019;re what the doctor wants us to be doing with the patient.&#x201D; [P9]</p></list-item></list></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Proximity of similar information</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;I want lab results in the same spot.&#x201D; [P24]</p></list-item><list-item><p>&#x201C;That&#x2019;d be nice if they were together. Orders around orders. Orders can stick together.&#x201D; [P1]</p></list-item></list></td></tr><tr><td align="left" valign="top">Focusing on key information types</td><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Go-to action items over background details</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;I believe that social determinants of health are important. However, during my admission process, I do not check the social determinants of health. It is crucial for social workers and us to better understand the patient, but it is not my initial priority. When I first receive patients, I do not check the social determinants of health.&#x201D; [P26]</p></list-item><list-item><p>&#x201C;I always want to know what orders are because these would be done right away.&#x201D; [P22]</p></list-item></list></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Removing redundancy</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;The additional report things have a fall risk timeline, but then there&#x2019;s a fall risk injury (information card). I just feel like it&#x2019;s totally redundant.&#x201D; [P22]</p></list-item><list-item><p>&#x201C;The card, &#x2018;Getting to know me,&#x2019; I feel like this was redundant with &#x2018;About me.&#x2019; I honestly never use this.&#x201D; [P5]</p></list-item></list></td></tr><tr><td align="left" valign="top">Easy-to-use design</td><td align="left" valign="top"/></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Unnecessary steps to the desired information</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;We cannot see the treatment team unless we do another click here and check the treating team.&#x201D; [P26]</p></list-item><list-item><p>&#x201C;...a lot of people have a hard time with, like, everything&#x2019;s here but you have to click a lot to get out of here, right? If there&#x2019;s a transfusion order, this shouldn&#x2019;t be bold or an asterisk (on the order name). There should be an order you need to give blood or something that you could click on&#x2026;Why do you need extra things to press?&#x201D; [P22]</p></list-item><list-item><p>&#x201C;I really don&#x2019;t use this summary page that much, because it&#x2019;s just so overwhelming. I guess it&#x2019;s just too many things there that I don&#x2019;t even know, like how to navigate it, which is why I made my system, which is more clicking.&#x201D; [P5]</p></list-item></list></td></tr></tbody></table></table-wrap></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Results</title><p>The co-design case study highlights the importance of aligning EHR nursing summary design with nurses&#x2019; cognitive workflows, demonstrating that nurses prioritize and organize information in ways that make sense to them. Concise, relevant information allows nurses to quickly review a patient&#x2019;s status, while strategically grouping related data helps them navigate and interpret complex information more efficiently. The current nursing summary contains overwhelming amounts of information that is often presented ineffectively, necessitating extensive searching to consolidate scattered data. The findings indicate a significant need to remove less relevant information from the summary. Also, nurses emphasized the importance of &#x201C;unit specimen&#x201D; (results of the analysis of body fluid, tissue, or urine), &#x201C;activity,&#x201D; &#x201C;diet,&#x201D; and &#x201C;hospital problems&#x201D; in their design prototype, suggesting these are the key information types for patient overviews. Nurses tended to prioritize obtaining information on current problems, daily living status, or treatment plans. Medical history or miscellaneous notes can be a source of information but are not always necessary for the initial patient overview. Our findings are consistent with prior work in which clinicians used a limited number of clinical information concepts at the time of patient admission, suggesting better electronic data management strategies, including the priority display of frequently used clinical concepts [<xref ref-type="bibr" rid="ref15">15</xref>].</p><p>Participants strategically arranged information cards to align with their cognitive workflow by placing them adjacent to other relevant cards. The adjacency of information often signifies the similarity or relative importance of the information [<xref ref-type="bibr" rid="ref16">16</xref>]. Previous studies have also emphasized the benefits of placing paired EHR information adjacent to each other on the screen to facilitate user interface navigation [<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref19">19</xref>]. Some information pairs nurses identified with high frequency did not align with the current nursing summary layout. For example, &#x201C;orders&#x201D; and &#x201C;hospital problems,&#x201D; &#x201C;orders&#x201D; and &#x201C;vital signs,&#x201D; &#x201C;orders&#x201D; and &#x201C;point-of-care-testing order&#x201D; (tests that are conducted at the patient&#x2019;s bedside), and &#x201C;point-of-care-testing order&#x201D; and &#x201C;activity&#x201D; were frequently located next to each other in the participant designs, but not in the existing layout. In addition to the adjacent placement of relevant information, top-to-bottom organization of information was commonly found in the designs. The placement of items at the top of the screen naturally calls attention to those items [<xref ref-type="bibr" rid="ref20">20</xref>]. Instead of scrolling down for details on the screen, nurses tended to place good-to-know but not essential information toward the bottom of their designs. The concise and cognitively aligned design supports nurses in narrowing their focus from the comprehensive patient record to a targeted subset of relevant information, thereby enhancing the efficiency of initial assessments and ensuring that pertinent details are readily accessible when required [<xref ref-type="bibr" rid="ref21">21</xref>].</p></sec><sec id="s4-2"><title>Strengths and Limitations</title><p>These findings show the value of co-design activities that involve nurses in the design process&#x2014;to create an EHR nursing summary that better supports their needs. By prioritizing the most relevant patient information and streamlining the data presentation, the study offers design strategies that could alleviate the EHR burden of navigating from one piece of information to another. The identified design strategies could enhance efficiency and support the National Burden Reduction Collaborative&#x2019;s mission to reduce the overall burdens on health care professionals [<xref ref-type="bibr" rid="ref12">12</xref>].</p><p>While this case study successfully identified nurses&#x2019; information preferences aligning with their workflow, it has limitations. The use of a single simulated patient case for the co-design activities and the small sample size from a single institution may limit the generalizability of the findings. Due to the small sample size, we did not group participants by demographics (eg, unit-specific role, shift, work experience). While this study aimed to explore general information needs and design considerations for nursing summaries by including participants from multiple units, nurses&#x2019; specific needs may vary based on their characteristics. For example, nurses in surgical units may prioritize surgery-related information, while nurses in general medical units may focus on different aspects. Additionally, night shift nurses may prioritize information about upcoming examinations for the next day. Nurses&#x2019; characteristics may also influence their priorities and responsibilities, underscoring the importance of considering these variables in future research.</p></sec><sec id="s4-3"><title>Conclusion</title><p>This co-design case study provides valuable insights into nurses&#x2019; preferences and strategies for organizing information in an EHR nursing summary, underscoring the need to redesign the layout based on its practical use. We emphasized the significance of reducing less relevant information and optimizing the layout according to nurses&#x2019; information priorities. These efforts have the potential to improve the usefulness of the current nursing summary. The direct involvement of nurses as co-designers holds promise for developing user-centered EHR tools that support nursing cognition, decision-making, and workflow.</p></sec></sec></body><back><ack><p>We would like to express our gratitude to the participants for generously sharing their time and experiences. This study was supported by SP&#x2019;s Doctoral Dissertation Fellowship, University of Minnesota and Midwest Nursing Research Society/Council for Advancement of Nursing Science Dissertation Grant (grant CON000000104586).</p></ack><notes><sec><title>Data Availability</title><p>The data generated during this study are available from the corresponding author upon reasonable request.</p></sec></notes><fn-group><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">EHR</term><def><p>electronic health record</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="web"><article-title>Sentinel event data summary</article-title><source>The Joint Commission</source><year>2024</year><access-date>2024-11-19</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.jointcommission.org/resources/sentinel-event/sentinel-event-data-summary/">https://www.jointcommission.org/resources/sentinel-event/sentinel-event-data-summary/</ext-link></comment></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Park</surname><given-names>S</given-names> </name><name name-style="western"><surname>Marquard</surname><given-names>J</given-names> </name></person-group><article-title>Nurse-centered co-design of an electronic health record nursing summary</article-title><source>Human Factors in Healthcare</source><year>2024</year><month>06</month><volume>5</volume><fpage>100065</fpage><pub-id pub-id-type="doi">10.1016/j.hfh.2024.100065</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Staggers</surname><given-names>N</given-names> </name><name name-style="western"><surname>Clark</surname><given-names>L</given-names> </name><name name-style="western"><surname>Blaz</surname><given-names>JW</given-names> </name><name name-style="western"><surname>Kapsandoy</surname><given-names>S</given-names> </name></person-group><article-title>Why patient summaries in electronic health records do not provide the cognitive support necessary for nurses&#x2019; handoffs on medical and surgical units: insights from interviews and observations</article-title><source>Health Informatics J</source><year>2011</year><month>09</month><volume>17</volume><issue>3</issue><fpage>209</fpage><lpage>223</lpage><pub-id pub-id-type="doi">10.1177/1460458211405809</pub-id><pub-id pub-id-type="medline">21937463</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Busse</surname><given-names>TS</given-names> </name><name name-style="western"><surname>Jux</surname><given-names>C</given-names> </name><name name-style="western"><surname>Laser</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Involving health care professionals in the development of electronic health records: scoping review</article-title><source>JMIR Hum Factors</source><year>2023</year><month>07</month><day>10</day><volume>10</volume><fpage>e45598</fpage><pub-id pub-id-type="doi">10.2196/45598</pub-id><pub-id pub-id-type="medline">37428524</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Voorend</surname><given-names>R</given-names> </name><name name-style="western"><surname>Derboven</surname><given-names>J</given-names> </name><name name-style="western"><surname>Slegers</surname><given-names>K</given-names> </name></person-group><article-title>Distributed user-generated card based co-design: a case study</article-title><conf-name>CHI &#x2019;19</conf-name><conf-date>May 4-9, 2019</conf-date><conf-loc>Glasgow, Scotland, United Kingdom</conf-loc><pub-id pub-id-type="doi">10.1145/3290607.3312815</pub-id></nlm-citation></ref><ref id="ref6"><label>6</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ludlow</surname><given-names>K</given-names> </name><name name-style="western"><surname>Westbrook</surname><given-names>J</given-names> </name><name name-style="western"><surname>Jorgensen</surname><given-names>M</given-names> </name><etal/></person-group><article-title>Co-designing a dashboard of predictive analytics and decision support to drive care quality and client outcomes in aged care: a mixed-method study protocol</article-title><source>BMJ Open</source><year>2021</year><month>08</month><day>25</day><volume>11</volume><issue>8</issue><fpage>e048657</fpage><pub-id pub-id-type="doi">10.1136/bmjopen-2021-048657</pub-id><pub-id pub-id-type="medline">34433599</pub-id></nlm-citation></ref><ref id="ref7"><label>7</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Song</surname><given-names>T</given-names> </name><name name-style="western"><surname>Yu</surname><given-names>P</given-names> </name><name name-style="western"><surname>Bliokas</surname><given-names>V</given-names> </name><etal/></person-group><article-title>A clinician-led, experience-based co-design approach for developing mhealth services to support the patient self-management of chronic conditions: development study and design case</article-title><source>JMIR Mhealth Uhealth</source><year>2021</year><month>07</month><day>20</day><volume>9</volume><issue>7</issue><fpage>e20650</fpage><pub-id pub-id-type="doi">10.2196/20650</pub-id><pub-id pub-id-type="medline">34283030</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Alvarez</surname><given-names>CP</given-names> </name><name name-style="western"><surname>Martinez-Maldonado</surname><given-names>R</given-names> </name><name name-style="western"><surname>Buckingham Shum</surname><given-names>S</given-names> </name></person-group><article-title>LA-DECK: a card-based learning analytics co-design tool</article-title><conf-name>LAK &#x2019;20: 10th International Conference on Learning Analytics and Knowledge</conf-name><conf-date>Mar 23-27, 2020</conf-date><conf-loc>Frankfurt, Germany</conf-loc><pub-id pub-id-type="doi">10.1145/3375462.3375476</pub-id></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Kwiatkowska</surname><given-names>J</given-names> </name><name name-style="western"><surname>Sz&#x00F3;stek</surname><given-names>A</given-names> </name><name name-style="western"><surname>Lamas</surname><given-names>D</given-names> </name></person-group><article-title>(Un)structured sources of inspiration: comparing the effects of game-like cards and design cards on creativity in co-design process</article-title><conf-name>PDC &#x2019;14: Participatory Design Conference</conf-name><conf-date>Oct 6-10, 2014</conf-date><conf-loc>Windhoek, Namibia</conf-loc><pub-id pub-id-type="doi">10.1145/2661435.2661442</pub-id></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Tankala</surname><given-names>S</given-names> </name><name name-style="western"><surname>Sherwin</surname><given-names>K</given-names> </name></person-group><article-title>Card sorting: uncover users&#x2019; mental models</article-title><year>2024</year><month>02</month><day>2</day><access-date>2024-04-01</access-date><publisher-name>Nielsen Norman Group</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.nngroup.com/articles/card-sorting-definition/">https://www.nngroup.com/articles/card-sorting-definition/</ext-link></comment></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Righi</surname><given-names>C</given-names> </name><name name-style="western"><surname>James</surname><given-names>J</given-names> </name><name name-style="western"><surname>Beasley</surname><given-names>M</given-names> </name><etal/></person-group><article-title>Card sort analysis best practices</article-title><source>J Usability Stud</source><year>2013</year><access-date>2025-02-26</access-date><volume>8</volume><issue>3</issue><fpage>69</fpage><lpage>89</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://uxpajournal.org/card-sort-analysis-best-practices-2/">https://uxpajournal.org/card-sort-analysis-best-practices-2/</ext-link></comment></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="web"><article-title>New group hopes to focus efforts to trim clinician burdens</article-title><source>Health Data Management</source><year>2023</year><month>02</month><access-date>2024-11-16</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.healthdatamanagement.com/articles/new-group-hopes-to-focus-efforts-to-trim-clinician-burdens">https://www.healthdatamanagement.com/articles/new-group-hopes-to-focus-efforts-to-trim-clinician-burdens</ext-link></comment></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Martikainen</surname><given-names>S</given-names> </name><name name-style="western"><surname>Kaipio</surname><given-names>J</given-names> </name><name name-style="western"><surname>L&#x00E4;&#x00E4;veri</surname><given-names>T</given-names> </name></person-group><article-title>End-user participation in health information systems (HIS) development: physicians&#x2019; and nurses&#x2019; experiences</article-title><source>Int J Med Inform</source><year>2020</year><month>05</month><volume>137</volume><fpage>104117</fpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2020.104117</pub-id><pub-id pub-id-type="medline">32179254</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Melnick</surname><given-names>ER</given-names> </name><name name-style="western"><surname>West</surname><given-names>CP</given-names> </name><name name-style="western"><surname>Nath</surname><given-names>B</given-names> </name><etal/></person-group><article-title>The association between perceived electronic health record usability and professional burnout among US nurses</article-title><source>J Am Med Inform Assoc</source><year>2021</year><month>07</month><day>30</day><volume>28</volume><issue>8</issue><fpage>1632</fpage><lpage>1641</lpage><pub-id pub-id-type="doi">10.1093/jamia/ocab059</pub-id><pub-id pub-id-type="medline">33871018</pub-id></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Pickering</surname><given-names>BW</given-names> </name><name name-style="western"><surname>Gajic</surname><given-names>O</given-names> </name><name name-style="western"><surname>Ahmed</surname><given-names>A</given-names> </name><name name-style="western"><surname>Herasevich</surname><given-names>V</given-names> </name><name name-style="western"><surname>Keegan</surname><given-names>MT</given-names> </name></person-group><article-title>Data utilization for medical decision making at the time of patient admission to ICU</article-title><source>Crit Care Med</source><year>2013</year><month>06</month><volume>41</volume><issue>6</issue><fpage>1502</fpage><lpage>1510</lpage><pub-id pub-id-type="doi">10.1097/CCM.0b013e318287f0c0</pub-id><pub-id pub-id-type="medline">23528804</pub-id></nlm-citation></ref><ref id="ref16"><label>16</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Wagemans</surname><given-names>J</given-names> </name><name name-style="western"><surname>Elder</surname><given-names>JH</given-names> </name><name name-style="western"><surname>Kubovy</surname><given-names>M</given-names> </name><etal/></person-group><article-title>A century of Gestalt psychology in visual perception: I. Perceptual grouping and figure-ground organization</article-title><source>Psychol Bull</source><year>2012</year><month>11</month><volume>138</volume><issue>6</issue><fpage>1172</fpage><lpage>1217</lpage><pub-id pub-id-type="doi">10.1037/a0029333</pub-id><pub-id pub-id-type="medline">22845751</pub-id></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Marian</surname><given-names>AA</given-names> </name><name name-style="western"><surname>Dexter</surname><given-names>F</given-names> </name><name name-style="western"><surname>Tucker</surname><given-names>P</given-names> </name><name name-style="western"><surname>Todd</surname><given-names>MM</given-names> </name></person-group><article-title>Comparison of alphabetical versus categorical display format for medication order entry in a simulated touch screen anesthesia information management system: an experiment in clinician-computer interaction in anesthesia</article-title><source>BMC Med Inform Decis Mak</source><year>2012</year><month>05</month><day>29</day><volume>12</volume><issue>1</issue><fpage>46</fpage><pub-id pub-id-type="doi">10.1186/1472-6947-12-46</pub-id><pub-id pub-id-type="medline">22643058</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Senathirajah</surname><given-names>Y</given-names> </name></person-group><article-title>Safer design - composable EHRs and mechanisms for safety</article-title><source>Stud Health Technol Inform</source><year>2015</year><volume>218</volume><fpage>86</fpage><lpage>92</lpage><pub-id pub-id-type="medline">26262532</pub-id></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zheng</surname><given-names>K</given-names> </name><name name-style="western"><surname>Padman</surname><given-names>R</given-names> </name><name name-style="western"><surname>Johnson</surname><given-names>MP</given-names> </name><name name-style="western"><surname>Diamond</surname><given-names>HS</given-names> </name></person-group><article-title>An interface-driven analysis of user interactions with an electronic health records system</article-title><source>J Am Med Inform Assoc</source><year>2009</year><volume>16</volume><issue>2</issue><fpage>228</fpage><lpage>237</lpage><pub-id pub-id-type="doi">10.1197/jamia.M2852</pub-id><pub-id pub-id-type="medline">19074301</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Senathirajah</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Kaufman</surname><given-names>D</given-names> </name><name name-style="western"><surname>Bakken</surname><given-names>S</given-names> </name></person-group><article-title>The clinician in the driver&#x2019;s seat: part 2 - intelligent uses of space in a drag/drop user-composable electronic health record</article-title><source>J Biomed Inform</source><year>2014</year><month>12</month><volume>52</volume><fpage>177</fpage><lpage>188</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2014.09.008</pub-id><pub-id pub-id-type="medline">25445921</pub-id></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Horsky</surname><given-names>J</given-names> </name><name name-style="western"><surname>Ramelson</surname><given-names>HZ</given-names> </name></person-group><article-title>Development of a cognitive framework of patient record summary review in the formative phase of user-centered design</article-title><source>J Biomed Inform</source><year>2016</year><month>12</month><volume>64</volume><fpage>147</fpage><lpage>157</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2016.10.004</pub-id><pub-id pub-id-type="medline">27725292</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Nursing summary layout.</p><media xlink:href="formative_v9i1e68906_app1.pdf" xlink:title="PDF File, 1437 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>Descriptions of information types in nursing summaries.</p><media xlink:href="formative_v9i1e68906_app2.docx" xlink:title="DOCX File, 18 KB"/></supplementary-material></app-group></back></article>