<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v23i2e21615</article-id>
      <article-id pub-id-type="pmid">33595448</article-id>
      <article-id pub-id-type="doi">10.2196/21615</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Viewpoint</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Viewpoint</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>A Novel Patient Values Tab for the Electronic Health Record: A User-Centered Design Approach</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
        <contrib contrib-type="editor">
          <name>
            <surname>Kukafka</surname>
            <given-names>Rita</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Bose-Brill</surname>
            <given-names>Seuli</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Lee</surname>
            <given-names>Robert</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Desai</surname>
            <given-names>Anjali Varma</given-names>
          </name>
          <degrees>MSCE, MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Memorial Sloan Kettering Cancer Center</institution>
            <addr-line>1275 York Avenue</addr-line>
            <addr-line>New York, NY, 10065</addr-line>
            <country>United States</country>
            <phone>1 917 865 2495</phone>
            <email>Desaia2@mskcc.org</email>
          </address>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8586-7188</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Michael</surname>
            <given-names>Chelsea L</given-names>
          </name>
          <degrees>MS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9525-7591</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Kuperman</surname>
            <given-names>Gilad J</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4130-1577</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Jordan</surname>
            <given-names>Gregory</given-names>
          </name>
          <degrees>BS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7904-3470</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Mittelstaedt</surname>
            <given-names>Haley</given-names>
          </name>
          <degrees>MFA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6932-1652</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Epstein</surname>
            <given-names>Andrew S</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1808-3070</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Connor</surname>
            <given-names>MaryAnn</given-names>
          </name>
          <degrees>MSN, RN-BC, CPHIMS, FAMIA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2340-7770</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author">
          <name name-style="western">
            <surname>B Villar</surname>
            <given-names>Rika Paula</given-names>
          </name>
          <degrees>BSN, MSHI, RN-BC</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3346-5176</ext-link>
        </contrib>
        <contrib id="contrib9" contrib-type="author">
          <name name-style="western">
            <surname>Bernal</surname>
            <given-names>Camila</given-names>
          </name>
          <degrees>MPH</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0867-1688</ext-link>
        </contrib>
        <contrib id="contrib10" contrib-type="author">
          <name name-style="western">
            <surname>Kramer</surname>
            <given-names>Dana</given-names>
          </name>
          <degrees>NP</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1501-9236</ext-link>
        </contrib>
        <contrib id="contrib11" contrib-type="author">
          <name name-style="western">
            <surname>Davis</surname>
            <given-names>Mary Elizabeth</given-names>
          </name>
          <degrees>RN, DNP, AOCNS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3771-8289</ext-link>
        </contrib>
        <contrib id="contrib12" contrib-type="author">
          <name name-style="western">
            <surname>Chen</surname>
            <given-names>Yuxiao</given-names>
          </name>
          <degrees>BS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7597-246X</ext-link>
        </contrib>
        <contrib id="contrib13" contrib-type="author">
          <name name-style="western">
            <surname>Malisse</surname>
            <given-names>Catherine</given-names>
          </name>
          <degrees>BS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9454-8581</ext-link>
        </contrib>
        <contrib id="contrib14" contrib-type="author">
          <name name-style="western">
            <surname>Markose</surname>
            <given-names>Gigi</given-names>
          </name>
          <degrees>MBA, MSN, RN-BC</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4848-5030</ext-link>
        </contrib>
        <contrib id="contrib15" contrib-type="author">
          <name name-style="western">
            <surname>Nelson</surname>
            <given-names>Judith E</given-names>
          </name>
          <degrees>MD, JD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3624-3111</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Memorial Sloan Kettering Cancer Center</institution>
        <addr-line>New York, NY</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Medicine</institution>
        <institution>Weill Cornell Medical College</institution>
        <addr-line>New York, NY</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Anjali Varma Desai <email>Desaia2@mskcc.org</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>2</month>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>17</day>
        <month>2</month>
        <year>2021</year>
      </pub-date>
      <volume>23</volume>
      <issue>2</issue>
      <elocation-id>e21615</elocation-id>
      <history>
        <date date-type="received">
          <day>14</day>
          <month>7</month>
          <year>2020</year>
        </date>
        <date date-type="rev-request">
          <day>1</day>
          <month>8</month>
          <year>2020</year>
        </date>
        <date date-type="rev-recd">
          <day>21</day>
          <month>8</month>
          <year>2020</year>
        </date>
        <date date-type="accepted">
          <day>21</day>
          <month>10</month>
          <year>2020</year>
        </date>
      </history>
      <copyright-statement>©Anjali Varma Desai, Chelsea L Michael, Gilad J Kuperman, Gregory Jordan, Haley Mittelstaedt, Andrew S Epstein, MaryAnn Connor, Rika Paula B Villar, Camila Bernal, Dana Kramer, Mary Elizabeth Davis, Yuxiao Chen, Catherine Malisse, Gigi Markose, Judith E Nelson. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 17.02.2021.</copyright-statement>
      <copyright-year>2021</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on http://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="http://www.jmir.org/2021/2/e21615/" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The COVID-19 pandemic has shined a harsh light on a critical deficiency in our health care system: our inability to access important information about patients’ values, goals, and preferences in the electronic health record (EHR). At Memorial Sloan Kettering Cancer Center (MSK), we have integrated and systematized health-related values discussions led by oncology nurses for newly diagnosed cancer patients as part of routine comprehensive cancer care. Such conversations include not only the patient’s wishes for care at the end of life but also more holistic personal values, including sources of strength, concerns, hopes, and their definition of an acceptable quality of life. In addition, health care providers use a structured template to document their discussions of patient goals of care.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>To provide ready access to key information about the patient as a person with individual values, goals, and preferences, we undertook the creation of the Patient Values Tab in our center’s EHR to display this information in a single, central location. Here, we describe the interprofessional, interdisciplinary, iterative process and user-centered design methodology that we applied to build this novel functionality as well as our initial implementation experience and plans for evaluation.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We first convened a working group of experts from multiple departments, including medical oncology, health informatics, information systems, nursing informatics, nursing education, and supportive care, and a user experience designer. We conducted in-depth, semistructured, audiorecorded interviews of over 100 key stakeholders. The working group sought consensus on the tab’s main content, homing in on high-priority areas identified by the stakeholders. The core content was mapped to various EHR data sources. We established a set of high-level design principles to guide our process. Our user experience designer then created wireframes of the tab design. The designer conducted usability testing with physicians, nurses, and other health professionals. Data validation testing was conducted.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>We have already deployed the Patient Values Tab to a pilot sample of users in the MSK Gastrointestinal Medical Oncology Service, including physicians, advanced practice providers, nurses, and administrative staff. We have early evidence of the positive impact of this EHR innovation. Audit logs show increasing use. Many of the initial user comments have been enthusiastically positive, while others have provided constructive suggestions for additional tab refinements with respect to format and content.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>It is our challenge and obligation to enrich the EHR with information about the patient as a person. Realization of this capability is a pressing public health need requiring the collaboration of technological experts with a broad range of clinical leaders, users, patients, and families to achieve solutions that are both principled and practical. Our new Patient Values Tab represents a step forward in this important direction.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>electronic health record</kwd>
        <kwd>health informatics</kwd>
        <kwd>supportive care</kwd>
        <kwd>palliative care</kwd>
        <kwd>oncology</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Besides inadequate personal protective equipment and limited intensive care surge capacity, the COVID-19 pandemic has shined a harsh light on another critical deficiency in our system of health care delivery: our inability to access important information about patients’ values, goals, and preferences in the electronic health record (EHR) [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>]. All over the United States, frontline clinicians in the field, emergency departments, intensive care units (ICUs), and on rapid response teams and hospital floors have struggled with urgent decisions about the use of life-supporting technologies to treat serious complications of COVID-19 infection without sufficient information about the patient as a person, what means most to this individual, how the patient defines living well, and whom the patient trusts to make important decisions about health care [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. Such information is rarely accessible even for older adults and others with underlying diseases, such as cancer or chronic comorbid conditions, who are most vulnerable. Either this information was not previously elicited or, although it was discussed, it was not documented or is difficult to find in the EHR [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref9">9</xref>].</p>
        <p>This is not a new problem, and it will certainly persist after COVID-19 in the absence of major innovative efforts. Although many clinicians consider the EHR to pose a barrier to patient-centered care by literally shifting the attention from the patient to the computer screen [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>], the EHR is also a potentially powerful tool that can support clinician-patient communication, team collaboration, personalized and respectful care, continuity across settings, patient engagement, and shared decision making in accordance with patients’ individual needs and priorities [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. Several recent initiatives have utilized digital platforms and tools (eg, documentation templates, automated prompts, and electronic order sets) to optimize documentation of advance care planning and goals of care discussions [<xref ref-type="bibr" rid="ref15">15</xref>-<xref ref-type="bibr" rid="ref17">17</xref>]. Some have focused primarily on the documentation of advance care planning in patients who are older or have advanced disease [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. A more recent initiative leverages the Epic EHR by assembling information about serious illness conversations, including prognostic information given by clinicians to the patient and family, the patient’s understanding of the course of the illness, hopes and worries, priorities, and clinician recommendations, into a new EHR template [<xref ref-type="bibr" rid="ref20">20</xref>].</p>
        <p>At Memorial Sloan Kettering Cancer Center (MSK), we integrated and systematized health-related values discussions led by oncology nurses for newly diagnosed cancer patients as part of routine comprehensive cancer care, regardless of the patient’s stage, prognosis, or treatment intent [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. These discussions are revisited quarterly or as deemed appropriate after prespecified clinical events (eg, progression of disease through first-line therapy, hospitalization, or admission to the ICU). In this model, communication encompasses not only the patient’s wishes for care at the end of life but also more basic and holistic personal values, including sources of strength, concerns, hopes, definition of an acceptable quality of life, and what the patient wants the clinical team to know about them as a person in order to provide the best care and preserve dignity [<xref ref-type="bibr" rid="ref22">22</xref>]. In addition, oncologists and other physicians and advanced practice providers use a structured template to document their discussions of patient goals of care, which may address the expected course of the patient’s illness, intent of the current treatment, goals identified by the patient, preferences for end-of-life care, and, if relevant, hospice enrollment.</p>
      </sec>
      <sec>
        <title>The Patient Values Tab: Concept and Design</title>
        <p>To provide ready access to these crucial communications between clinicians and patients as well as key information about the patient as a person with individual values, goals, and preferences, we undertook the creation of the Patient Values Tab in our center’s EHR to display this information in a single centralized location. Our institution’s EHR platform is Allscripts Sunrise Clinical Manager (Allscripts Healthcare LLC), which organizes data displays into tabs, as do many other EHR platforms. Here, we describe the interprofessional, interdisciplinary, iterative process and user-centered design methodology we applied to build this novel functionality [<xref ref-type="bibr" rid="ref23">23</xref>].</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Working Group and Stakeholder Interviews</title>
        <p>We first convened a working group of experts from multiple departments, including medical oncology, health informatics, information systems, nursing informatics, nursing education, and supportive care (a multidisciplinary palliative care service), and a user experience designer. Members of the working group were selected for their previous experience leading large-scale institutional initiatives and unique expertise in the integration of supportive care and oncology. This core team met every 2 weeks to collaborate on the development and design of the new tab.</p>
        <p>To understand the needs and perspectives of a broad range of institutional stakeholders, we also conducted in-depth, semistructured, audiorecorded interviews of over 100 key stakeholders based on a written guide prepared by the core team. Analysis of these interviews, which is reported in a separate publication (which includes selected stakeholder comments in an appendix), was used to inform content and format of the tab [<xref ref-type="bibr" rid="ref24">24</xref>]. As active contributors to the creative process, those who were interviewed were more inclined to buy in to the ultimate product. In addition, many of these stakeholders held leadership positions within divisions and departments and went on to share enthusiasm about the upcoming tab with their colleagues, enhancing the visibility of the ongoing development effort among a broader group of users.</p>
      </sec>
      <sec>
        <title>Mapping Tab Content</title>
        <p>The core team sought consensus on the Patient Values Tab’s main content, homing in on high-priority areas identified in the stakeholder interviews while also incorporating their input on format and considering suggestions on the logistics of the implementation process. The core content was mapped to various data sources within the EHR (as shown in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>).</p>
        <p>For example, oncology nurses use a structured document entitled “Assessment, Patient Personal Values” to summarize their values discussions. The patient’s preferred name, language, and communication preferences are elicited through the digital patient portal system via an electronic care questionnaire, which the nurse verifies and updates as needed at the first clinic visit on the nursing health assessment. Education about health care proxy (HCP) and other advance directives is provided in the hospital by patient representatives, who also record designation of and information about the HCP in a specific clinical document.</p>
      </sec>
      <sec>
        <title>High-Level Design Principles</title>
        <p>As the data sources were clarified, we also established a set of high-level design principles (shown in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>) to guide this process.</p>
        <boxed-text id="box1" position="float">
          <title>High-level design principles.</title>
          <list list-type="order">
            <list-item>
              <p>The Patient Values Tab should provide users with an at-a-glance understanding of the patient as a person.</p>
            </list-item>
            <list-item>
              <p>The Patient Values Tab should offer easy access to data that can be viewed in aggregate in the context of other relevant information to support clinical decision making.</p>
            </list-item>
            <list-item>
              <p>The Patient Values Tab will specify the context in which the information was collected (with the source and date the information was updated).</p>
            </list-item>
            <list-item>
              <p>The Patient Values Tab will be in a read-only format (ie, the data displayed will be captured and edited elsewhere).</p>
            </list-item>
            <list-item>
              <p>The Patient Values Tab will contain the most high-yield information while presenting this information in a succinct, streamlined way to minimize cognitive load for users.</p>
            </list-item>
            <list-item>
              <p>The Patient Values Tab will be accessible to all health care team members across the spectrum of patient care.</p>
            </list-item>
          </list>
        </boxed-text>
        <p>One such principle was that the tab would be in a read-only display format, populated with existing source documents in the EHR that could not be directly edited in the tab itself. We chose this approach because we and various key stakeholders we interviewed were concerned that the content would become unwieldy and unstable, ultimately leading to inefficiency for users if multiple modifications were allowed. We concluded that reliance on existing workflows and processes would reduce the cognitive load for clinicians and enable a communal responsibility for the underlying documentation, with important roles for various team members as contributors to a shared understanding of the patient as a person.</p>
      </sec>
      <sec>
        <title>User Testing</title>
        <p>The next step was close collaboration with our user experience designer to create and refine wireframes of the tab design. During this process, the designer conducted usability testing with physicians, nurses, and other health professionals. All participants were asked to provide general usability feedback on the design. To obtain more detailed feedback, participants were presented with specific clinical tasks calling for the use of information contained in the Patient Values Tab in scenarios that the core team generated and adapted for particular roles and responsibilities. For example, in one scenario, the physician was preparing to “discuss serious results with the patient,” while the nurse needed to “provide information for medication management.” This process revealed a lack of familiarity among users with some of the underlying documentation that sourced the data displayed in the tab. To address this issue, we created a frequently asked questions tile (ie, section) in the tab including basic information about data sources and directing users to the appropriate underlying document to update the information, if needed.</p>
      </sec>
      <sec>
        <title>Refinement and Validation</title>
        <p>Additional design refinements incorporated (1) suggestions from the user experience designer (eg, creating a banner at the top of the tab with the preferred name information, color coding the different categories of information to help users recognize and navigate among them quickly, including a separate feedback tile within the tab inviting users’ input and comments about their experience using the tab); (2) input from the core team (eg, placing the goals of care discussions and the nurse values summary in the most central, prominent positions in the tab; extracting and separately displaying the essential information regarding emergency contact, HCP, and next of kin for rapid access during clinical emergencies, with relevant advance directive scanned forms located below this information); and (3) insights gleaned from the stakeholder interviews (eg, providing expedited access to consultant notes from supportive care, psychiatry, and ethics as the highest yield and most consistently complete sources of information about patient values and personhood). During this iterative process, the designer shared mock-up options and elicited feedback from the core team via email and throughout the series of biweekly core team meetings.</p>
        <p>Members of our core team with informatics expertise conducted data validation testing to ensure the fidelity of the information displayed in the tab to the underlying source of this information (ie, confirming that the tab displayed the correct information from the intended source document in the intended format for the correct patient). In addition, to detect delays in displaying information to the user that might decrease usability, we assessed the time to launch the tab content for selected patients. If time delays were identified, we worked with the information systems team to identify the source of the delay so that it could be rectified; specifically, technical optimizations were made to bring the load times in line with other feature load times in our EHR (ie, no longer than a few seconds).</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Initial Deployment and Implementation</title>
        <p>We have already deployed the Patient Values Tab to a pilot sample of users in the Gastrointestinal (GI) Medical Oncology Service at our center, including the physicians, advanced practice providers (APPs), nurses, and administrative staff. We chose this service for this first phase of our pilot deployment because it is the largest solid tumor service at MSK, with approximately 40 physicians varying in age, gender, race and ethnicity, number of years in clinical practice, and disease focus who care for a large number of cancer patients with diverse demographics (eg, age, gender) and types and stages of cancer with wide variability in the pace of the disease process and overall clinical course. Patients of the GI Medical Oncology Service represent the largest proportion of admissions to our Memorial Hospital, thus frequently involving both outpatient and inpatient teams in their care.</p>
        <p>We have executed a detailed implementation plan, which includes (1) discussion with the physician, APP, and nursing leaders of the service about the tab and its integration in clinical care by that service; (2) email notification to users about the availability and basic content of the new tab; and (3) presentations encompassing key features and functionality of the tab together with options for incorporating its use in regular clinical workflows. For each of these steps, we have targeted the professional groups individually, since they have different needs, roles, and workflows in providing patient care, although ultimately, they must all collaborate and communicate as a team to optimize this care.</p>
      </sec>
      <sec>
        <title>Further Iteration and Evaluation</title>
        <p>Learnings from this pilot will inform further refinement of the Patient Values Tab before broader implementation. We are measuring usage of the tab through audit logs, which specify the time, user, and patient involved each time it is launched. In addition, we have included a feedback tile within the tab itself that asks in closed-ended items for users’ broad impressions (“It’s great,” “It’s okay,” or “It needs improvement”) and provides space for free-text comments. In-depth feedback will be gathered from selected clinicians through brief individual interviews. We plan to select these clinicians based on audit log data indicating those who are low adopters or high adopters in terms of the frequency and timing of their tab use. Through the interviews, we will explore whether the tab fits with the clinician’s workflow and patterns of use (or lack of use) in clinical practice, the perceived value of the tab to the clinician, and suggestions for improvement (eg, with respect to content and format).</p>
        <p>Guided by this diverse user input, we have continued cycles of refinement and deployment to additional groups incrementally, with a plan for institution-wide rollout by the fall of 2020. The core team is continuing its biweekly meetings, monitoring every step in the implementation and evaluation process, and collaborating to address and incorporate user feedback in order to ensure that the use of the tab is maximized and sustained.</p>
      </sec>
      <sec>
        <title>Early Findings</title>
        <p>We already have early evidence of the positive impact of this EHR innovation. Audit logs show increasing use among different user groups. Among users who have engaged with the feedback section within the tab, 25 of 48 (52%) users reported that “it is great” compared with 18 of 48 (38%) users who reported that “it needs improvement” and provided specific constructive suggestions and 5 of 48 (10%) users who reported that “it is okay.” Many of these initial user comments have been enthusiastically positive (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>).</p>
        <boxed-text id="box2" position="float">
          <title>Illustrative quotes.</title>
          <p>“[I] love the easy access to [health care proxy] and Advance directives!”</p>
          <p>“Being able to quickly check the patient's preferred name is incredibly helpful!”</p>
          <p>“I like that it captures information from many different areas and placed in one area. I will be using this tab.”</p>
          <p>“Numerous tiles you have developed give the patient a ‘voice’ in our [electronic health record]. Strong work….This will be a great advance in Cognitive Support for our clinical teams.”</p>
        </boxed-text>
        <p>Users also suggested specific enhancements to the tab’s content quality and design.</p>
        <p>Our early pilot data have also revealed potential barriers to large-scale implementation, which include perceived lack of time to engage with the tab, competing priorities, incomplete or inaccurate tab content, technical glitches, and difficulty remembering to launch the tab as part of routine workflow. To address these challenges, we have enacted several proactive educational strategies when deploying to additional user groups, including (1) emphasizing that the tab is a display-only feature that is intended to save time by consolidating key information in a central location, (2) describing the processes by which incomplete or inaccurate tab content can be updated by the user, and (3) highlighting the “share feedback” section as a means for providing feedback on technical (or content-related) glitches that can be addressed by the Patient Values Tab interdisciplinary working group. In all circumstances, the Patient Values Tab working group follows up with each individual user who provides feedback to ensure closed-loop communication and enhance transparency in the ongoing effort to refine and optimize the tab’s functionality.</p>
        <p>We are also increasingly receiving reports of specific patient situations in which the information displayed in the tab, including the outpatient oncology nurse’s values summary, allowed the hospital team to support families in difficult decisions about the use of intensive care therapies. In one such case, the family described hearing the ICU physician reading the values summary aloud as feeling that the patient, who no longer was conscious and had not discussed this type of situation with them previously, “was in the room, speaking directly to them,” clarifying his priorities, providing guidance, and relieving them of burden and guilt in deciding to limit life support at that time. Immediate access that the Patient Values Tab provides to primary physicians’ goals of care discussions greatly facilitates the work of our emergency department and rapid response team clinicians, who must act quickly in emergencies.</p>
        <p>Similarly, we are hearing that the communication preferences section within the Patient Values Tab is particularly helpful to teams as they are preparing for family meetings and goals of care discussions. For example, one Patient Values Tab user recounted:</p>
        <disp-quote>
          <p>I did use it actually this week.…We were going to go have an impromptu family meeting and the attending physician asked, “Would the patient want to be involved?” and I said, “Well, let’s look at the Patient Values Tab”….We clicked there and it said “patient wants a lot of information with her partner present”…so…we used it in real time.</p>
        </disp-quote>
        <p>In this case, knowing how the patient preferred to receive medical information (ie, in detail) and with whom present (ie, her partner) helped guide the health care team’s approach to having a goals of care conversation at a timely moment.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <p>Even at this pilot stage of deployment, it is becoming clear that the Patient Values Tab enables care and decision making that honors the personhood and values of our patients. During the COVID-19 pandemic, as life-threatening emergencies have occurred without warning to patients who were then too ill to speak for themselves, we have learned—again, in a more painful but perhaps more enduring lesson—that high-quality care is heavily dependent on immediate access to this crucial information. As implementation and usage of the tab expands and our center moves beyond the current COVID-19 crisis, we will be able to examine its impact on a variety of outcomes at the level of the patient, clinician, work process, and health care system. Although the Patient Values Tab was built in MSK’s specific EHR (ie, Allscripts), this software can be configured in other EHR platforms as well, including Epic (the predominant platform in the United States). Further research is needed on the best ways to optimize and enhance the patient centeredness of various EHR systems through the synergistic integration of tools that capture broader, holistic patient values (eg, the Patient Values Tab), with ongoing efforts that are primarily focused on advance care planning (eg, Epic’s Advance Care Planning tab).</p>
      <p>All EHRs contain extensive quantitative information and voluminous data about patients that are mostly impersonal. Now, it is our challenge and obligation to enrich the EHR with information about the patient as a person, which is rarely included or readily accessible. Patient-centered care is highly prioritized by the Institute of Medicine [<xref ref-type="bibr" rid="ref25">25</xref>], patients and families, and professional caregivers [<xref ref-type="bibr" rid="ref26">26</xref>], but it can only be delivered if the patient’s personal values are as prominent as the laboratory values in the EHR on which health care professionals rely and spend the bulk of their time. Although it can be burdensome and distracting for clinical care, the EHR has tremendous untapped potential to support patient-centered care. Realization of this capability is a pressing public health need requiring the full collaboration of technological experts with a broad range of clinical leaders, users, patients, and families to achieve solutions that are both principled and practical. Our new Patient Values Tab is a step forward in this important direction.</p>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Table S1. Mapping the Patient Values Tab content to source documentation.</p>
        <media xlink:href="jmir_v23i2e21615_app1.docx" xlink:title="DOCX File , 20 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">APP</term>
          <def>
            <p>advanced practice providers</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">GI</term>
          <def>
            <p>gastrointestinal</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">HCP</term>
          <def>
            <p>health care proxy</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">ICU</term>
          <def>
            <p>intensive care unit</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">MSK</term>
          <def>
            <p>Memorial Sloan Kettering Cancer Center</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-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>Sanders</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Paladino</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Reaves</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Luetke-Stahlman</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Anhang Price</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Lorenz</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hanson</surname>
              <given-names>LC</given-names>
            </name>
            <name name-style="western">
              <surname>Curtis</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Meier</surname>
              <given-names>DE</given-names>
            </name>
            <name name-style="western">
              <surname>Fromme</surname>
              <given-names>EK</given-names>
            </name>
            <name name-style="western">
              <surname>Block</surname>
              <given-names>SD</given-names>
            </name>
          </person-group>
          <article-title>Quality Measurement of Serious Illness Communication: Recommendations for Health Systems Based on Findings from a Symposium of National Experts</article-title>
          <source>J Palliat Med</source>
          <year>2020</year>
          <month>01</month>
          <volume>23</volume>
          <issue>1</issue>
          <fpage>13</fpage>
          <lpage>21</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1089/jpm.2019.0335"/>
          </comment>
          <pub-id pub-id-type="doi">10.1089/jpm.2019.0335</pub-id>
          <pub-id pub-id-type="medline">31721629</pub-id>
        </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>Prater</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Sanchez</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Modan</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Burgess</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Frier</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Richards</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Bose-Brill</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Electronic Health Record Documentation Patterns of Recorded Primary Care Visits Focused on Complex Communication: A Qualitative Study</article-title>
          <source>Appl Clin Inform</source>
          <year>2019</year>
          <month>03</month>
          <volume>10</volume>
          <issue>2</issue>
          <fpage>247</fpage>
          <lpage>253</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1055/s-0039-1683986"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0039-1683986</pub-id>
          <pub-id pub-id-type="medline">30970382</pub-id>
          <pub-id pub-id-type="pmcid">PMC6458018</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>Varpio</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Rashotte</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Day</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>King</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kuziemsky</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Parush</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The EHR and building the patient's story: A qualitative investigation of how EHR use obstructs a vital clinical activity</article-title>
          <source>Int J Med Inform</source>
          <year>2015</year>
          <month>12</month>
          <volume>84</volume>
          <issue>12</issue>
          <fpage>1019</fpage>
          <lpage>28</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.ijmedinf.2015.09.004"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2015.09.004</pub-id>
          <pub-id pub-id-type="medline">26432683</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(15)30039-3</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>Curtis</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Kross</surname>
              <given-names>EK</given-names>
            </name>
            <name name-style="western">
              <surname>Stapleton</surname>
              <given-names>RD</given-names>
            </name>
          </person-group>
          <article-title>The Importance of Addressing Advance Care Planning and Decisions About Do-Not-Resuscitate Orders During Novel Coronavirus 2019 (COVID-19)</article-title>
          <source>JAMA</source>
          <year>2020</year>
          <month>05</month>
          <day>12</day>
          <volume>323</volume>
          <issue>18</issue>
          <fpage>1771</fpage>
          <lpage>1772</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2020.4894</pub-id>
          <pub-id pub-id-type="medline">32219360</pub-id>
          <pub-id pub-id-type="pii">2763952</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Abrukin</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Flores</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gavin</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Romney</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Blinderman</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Nakagawa</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Early Intervention of Palliative Care in the Emergency Department During the COVID-19 Pandemic</article-title>
          <source>JAMA Intern Med</source>
          <year>2020</year>
          <month>09</month>
          <day>01</day>
          <volume>180</volume>
          <issue>9</issue>
          <fpage>1252</fpage>
          <lpage>1254</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32501486"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamainternmed.2020.2713</pub-id>
          <pub-id pub-id-type="medline">32501486</pub-id>
          <pub-id pub-id-type="pii">2767018</pub-id>
          <pub-id pub-id-type="pmcid">PMC7275262</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>Lamas</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Panariello</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Henrich</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Hammes</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Hanson</surname>
              <given-names>LC</given-names>
            </name>
            <name name-style="western">
              <surname>Meier</surname>
              <given-names>DE</given-names>
            </name>
            <name name-style="western">
              <surname>Guinn</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Corrigan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hubber</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Luetke-Stahlman</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Block</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Advance Care Planning Documentation in Electronic Health Records: Current Challenges and Recommendations for Change</article-title>
          <source>J Palliat Med</source>
          <year>2018</year>
          <month>04</month>
          <volume>21</volume>
          <issue>4</issue>
          <fpage>522</fpage>
          <lpage>528</lpage>
          <pub-id pub-id-type="doi">10.1089/jpm.2017.0451</pub-id>
          <pub-id pub-id-type="medline">29360417</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>Curtis</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Sathitratanacheewin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Starks</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>RY</given-names>
            </name>
            <name name-style="western">
              <surname>Kross</surname>
              <given-names>EK</given-names>
            </name>
            <name name-style="western">
              <surname>Downey</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Sibley</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lober</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Loggers</surname>
              <given-names>ET</given-names>
            </name>
            <name name-style="western">
              <surname>Fausto</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Lindvall</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Engelberg</surname>
              <given-names>RA</given-names>
            </name>
          </person-group>
          <article-title>Using Electronic Health Records for Quality Measurement and Accountability in Care of the Seriously Ill: Opportunities and Challenges</article-title>
          <source>J Palliat Med</source>
          <year>2018</year>
          <month>03</month>
          <volume>21</volume>
          <issue>S2</issue>
          <fpage>S52</fpage>
          <lpage>S60</lpage>
          <pub-id pub-id-type="doi">10.1089/jpm.2017.0542</pub-id>
          <pub-id pub-id-type="medline">29182487</pub-id>
          <pub-id pub-id-type="pmcid">PMC5756465</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Walker</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>McMahan</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Barnes</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Katen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lamas</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sudore</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Advance Care Planning Documentation Practices and Accessibility in the Electronic Health Record: Implications for Patient Safety</article-title>
          <source>J Pain Symptom Manage</source>
          <year>2018</year>
          <month>02</month>
          <volume>55</volume>
          <issue>2</issue>
          <fpage>256</fpage>
          <lpage>264</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0885-3924(17)30497-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jpainsymman.2017.09.018</pub-id>
          <pub-id pub-id-type="medline">28943360</pub-id>
          <pub-id pub-id-type="pii">S0885-3924(17)30497-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC5794631</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lakin</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Isaacs</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Sullivan</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Harris</surname>
              <given-names>HA</given-names>
            </name>
            <name name-style="western">
              <surname>McMahan</surname>
              <given-names>RD</given-names>
            </name>
            <name name-style="western">
              <surname>Sudore</surname>
              <given-names>RL</given-names>
            </name>
          </person-group>
          <article-title>Emergency Physicians' Experience with Advance Care Planning Documentation in the Electronic Medical Record: Useful, Needed, and Elusive</article-title>
          <source>J Palliat Med</source>
          <year>2016</year>
          <month>06</month>
          <volume>19</volume>
          <issue>6</issue>
          <fpage>632</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1089/jpm.2015.0486</pub-id>
          <pub-id pub-id-type="medline">27203483</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Makoul</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Curry</surname>
              <given-names>RH</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>PC</given-names>
            </name>
          </person-group>
          <article-title>The use of electronic medical records: communication patterns in outpatient encounters</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2001</year>
          <volume>8</volume>
          <issue>6</issue>
          <fpage>610</fpage>
          <lpage>5</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/11687567"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/jamia.2001.0080610</pub-id>
          <pub-id pub-id-type="medline">11687567</pub-id>
          <pub-id pub-id-type="pmcid">PMC130071</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rathert</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Mittler</surname>
              <given-names>JN</given-names>
            </name>
            <name name-style="western">
              <surname>Banerjee</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McDaniel</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Patient-centered communication in the era of electronic health records: What does the evidence say?</article-title>
          <source>Patient Educ Couns</source>
          <year>2017</year>
          <month>01</month>
          <volume>100</volume>
          <issue>1</issue>
          <fpage>50</fpage>
          <lpage>64</lpage>
          <pub-id pub-id-type="doi">10.1016/j.pec.2016.07.031</pub-id>
          <pub-id pub-id-type="medline">27477917</pub-id>
          <pub-id pub-id-type="pii">S0738-3991(16)30326-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Street</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Farber</surname>
              <given-names>NJ</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Calvitti</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zuest</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gabuzda</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Bell</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gray</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Rick</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ashfaq</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Agha</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Provider interaction with the electronic health record: the effects on patient-centered communication in medical encounters</article-title>
          <source>Patient Educ Couns</source>
          <year>2014</year>
          <month>09</month>
          <volume>96</volume>
          <issue>3</issue>
          <fpage>315</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/24882086"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.pec.2014.05.004</pub-id>
          <pub-id pub-id-type="medline">24882086</pub-id>
          <pub-id pub-id-type="pii">S0738-3991(14)00184-0</pub-id>
          <pub-id pub-id-type="pmcid">PMC4339111</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>White</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Danis</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Enhancing patient-centered communication and collaboration by using the electronic health record in the examination room</article-title>
          <source>JAMA</source>
          <year>2013</year>
          <month>06</month>
          <day>12</day>
          <volume>309</volume>
          <issue>22</issue>
          <fpage>2327</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/23757080"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jama.2013.6030</pub-id>
          <pub-id pub-id-type="medline">23757080</pub-id>
          <pub-id pub-id-type="pii">1696109</pub-id>
          <pub-id pub-id-type="pmcid">PMC4849541</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>Delbanco</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Walker</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bell</surname>
              <given-names>SK</given-names>
            </name>
            <name name-style="western">
              <surname>Darer</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Elmore</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Farag</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Feldman</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>Mejilla</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ngo</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ralston</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Ross</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Trivedi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Vodicka</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Leveille</surname>
              <given-names>SG</given-names>
            </name>
          </person-group>
          <article-title>Inviting patients to read their doctors' notes: a quasi-experimental study and a look ahead</article-title>
          <source>Ann Intern Med</source>
          <year>2012</year>
          <month>10</month>
          <day>02</day>
          <volume>157</volume>
          <issue>7</issue>
          <fpage>461</fpage>
          <lpage>70</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.acpjournals.org/doi/10.7326/0003-4819-157-7-201210020-00002?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub%3dpubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.7326/0003-4819-157-7-201210020-00002</pub-id>
          <pub-id pub-id-type="medline">23027317</pub-id>
          <pub-id pub-id-type="pii">1363511</pub-id>
          <pub-id pub-id-type="pmcid">PMC3908866</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>Karim</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Harle</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>O'Donnell</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Booth</surname>
              <given-names>CM</given-names>
            </name>
          </person-group>
          <article-title>Documenting Goals of Care Among Patients With Advanced Cancer: Results of a Quality Improvement Initiative</article-title>
          <source>J Oncol Pract</source>
          <year>2018</year>
          <month>09</month>
          <volume>14</volume>
          <issue>9</issue>
          <fpage>e557</fpage>
          <lpage>e565</lpage>
          <pub-id pub-id-type="doi">10.1200/JOP.18.00031</pub-id>
          <pub-id pub-id-type="medline">30113873</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>Huber</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Highland</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Krishnamoorthi</surname>
              <given-names>VR</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>JW</given-names>
            </name>
          </person-group>
          <article-title>Utilizing the Electronic Health Record to Improve Advance Care Planning: A Systematic Review</article-title>
          <source>Am J Hosp Palliat Care</source>
          <year>2018</year>
          <month>03</month>
          <volume>35</volume>
          <issue>3</issue>
          <fpage>532</fpage>
          <lpage>541</lpage>
          <pub-id pub-id-type="doi">10.1177/1049909117715217</pub-id>
          <pub-id pub-id-type="medline">28627287</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>Haley</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Meisel</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gitelman</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Dingfield</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Casarett</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>O'Connor</surname>
              <given-names>NR</given-names>
            </name>
          </person-group>
          <article-title>Electronic Goals of Care Alerts: An Innovative Strategy to Promote Primary Palliative Care</article-title>
          <source>J Pain Symptom Manage</source>
          <year>2017</year>
          <month>05</month>
          <volume>53</volume>
          <issue>5</issue>
          <fpage>932</fpage>
          <lpage>937</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0885-3924(16)31230-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jpainsymman.2016.12.329</pub-id>
          <pub-id pub-id-type="medline">28062333</pub-id>
          <pub-id pub-id-type="pii">S0885-3924(16)31230-1</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>Turley</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Meng</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kanter</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Garrido</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Impact of a Care Directives Activity Tab in the Electronic Health Record on Documentation of Advance Care Planning</article-title>
          <source>Perm J</source>
          <year>2016</year>
          <volume>20</volume>
          <issue>2</issue>
          <fpage>43</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27057820"/>
          </comment>
          <pub-id pub-id-type="doi">10.7812/TPP/15-103</pub-id>
          <pub-id pub-id-type="medline">27057820</pub-id>
          <pub-id pub-id-type="pii">15-103</pub-id>
          <pub-id pub-id-type="pmcid">PMC4867824</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>Paladino</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bernacki</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Neville</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>Kavanagh</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Miranda</surname>
              <given-names>SP</given-names>
            </name>
            <name name-style="western">
              <surname>Palmor</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lakin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Desai</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lamas</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sanders</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Gass</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Henrich</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Lipsitz</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fromme</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Gawande</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Block</surname>
              <given-names>SD</given-names>
            </name>
          </person-group>
          <article-title>Evaluating an Intervention to Improve Communication Between Oncology Clinicians and Patients With Life-Limiting Cancer: A Cluster Randomized Clinical Trial of the Serious Illness Care Program</article-title>
          <source>JAMA Oncol</source>
          <year>2019</year>
          <month>06</month>
          <day>01</day>
          <volume>5</volume>
          <issue>6</issue>
          <fpage>801</fpage>
          <lpage>809</lpage>
          <pub-id pub-id-type="doi">10.1001/jamaoncol.2019.0292</pub-id>
          <pub-id pub-id-type="medline">30870556</pub-id>
          <pub-id pub-id-type="pii">2728562</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>Wilson</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Bernacki</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Lakin</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Alexander</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Jackson</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Jacobsen</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Rapid Adoption of a Serious Illness Conversation Electronic Medical Record Template: Lessons Learned and Future Directions</article-title>
          <source>J Palliat Med</source>
          <year>2020</year>
          <month>02</month>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>159</fpage>
          <lpage>161</lpage>
          <pub-id pub-id-type="doi">10.1089/jpm.2019.0420</pub-id>
          <pub-id pub-id-type="medline">32023189</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>Desai</surname>
              <given-names>AV</given-names>
            </name>
            <name name-style="western">
              <surname>Klimek</surname>
              <given-names>VM</given-names>
            </name>
            <name name-style="western">
              <surname>Chow</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Epstein</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Bernal</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Okpako</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rawlins-Duell</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kramer</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Romano</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Goldberg</surname>
              <given-names>JI</given-names>
            </name>
            <name name-style="western">
              <surname>Nelson</surname>
              <given-names>JE</given-names>
            </name>
          </person-group>
          <article-title>1-2-3 Project: A Quality Improvement Initiative to Normalize and Systematize Palliative Care for All Patients With Cancer in the Outpatient Clinic Setting</article-title>
          <source>J Oncol Pract</source>
          <year>2018</year>
          <month>12</month>
          <volume>14</volume>
          <issue>12</issue>
          <fpage>e775</fpage>
          <lpage>e785</lpage>
          <pub-id pub-id-type="doi">10.1200/JOP.18.00346</pub-id>
          <pub-id pub-id-type="medline">30537456</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Epstein</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Desai</surname>
              <given-names>AV</given-names>
            </name>
            <name name-style="western">
              <surname>Bernal</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Romano</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wan</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>Okpako</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Chow</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Kramer</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Calderon</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Klimek</surname>
              <given-names>VV</given-names>
            </name>
            <name name-style="western">
              <surname>Rawlins-Duell</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Reidy</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>Goldberg</surname>
              <given-names>JI</given-names>
            </name>
            <name name-style="western">
              <surname>Cruz</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Nelson</surname>
              <given-names>JE</given-names>
            </name>
          </person-group>
          <article-title>Giving Voice to Patient Values Throughout Cancer: A Novel Nurse-Led Intervention</article-title>
          <source>J Pain Symptom Manage</source>
          <year>2019</year>
          <month>07</month>
          <volume>58</volume>
          <issue>1</issue>
          <fpage>72</fpage>
          <lpage>79.e2</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31034869"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jpainsymman.2019.04.028</pub-id>
          <pub-id pub-id-type="medline">31034869</pub-id>
          <pub-id pub-id-type="pii">S0885-3924(19)30233-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC6849206</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abras</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Maloney-Krichmar</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Preece</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Bainbridge</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>User-Centered Design</article-title>
          <source>Encyclopedia of Human-Computer Interaction</source>
          <year>2004</year>
          <publisher-loc>Thousand Oaks, CA</publisher-loc>
          <publisher-name>Sage Publications</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Desai</surname>
              <given-names>AV</given-names>
            </name>
            <name name-style="western">
              <surname>Agarwal</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Epstein</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Kuperman</surname>
              <given-names>GJ</given-names>
            </name>
            <name name-style="western">
              <surname>Michael</surname>
              <given-names>CL</given-names>
            </name>
            <name name-style="western">
              <surname>Mittelstaedt</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Connor</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bernal</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lynch</surname>
              <given-names>KA</given-names>
            </name>
            <name name-style="western">
              <surname>Ostroff</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Katz</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Corrigan</surname>
              <given-names>KL</given-names>
            </name>
            <name name-style="western">
              <surname>Kramer</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Nelson</surname>
              <given-names>JE</given-names>
            </name>
          </person-group>
          <article-title>Needs and Perspectives of Cancer Center Stakeholders for Access to Patient Values in the Electronic Health Record [published online ahead of print, 2021 Feb 8]</article-title>
          <source>JCO Oncol Pract</source>
          <year>2021</year>
          <fpage>OP2000644</fpage>
          <pub-id pub-id-type="doi">10.1200/OP.20.00644</pub-id>
          <pub-id pub-id-type="medline">33555928</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <collab>Institute of Medicine</collab>
          </person-group>
          <source>Crossing the Quality Chasm: A New Health System for the 21st Century</source>
          <year>2001</year>
          <publisher-loc>Washington, DC</publisher-loc>
          <publisher-name>National Academies Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Gerteis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Edgman-Levitan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Daley</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Delbanco</surname>
              <given-names>TL</given-names>
            </name>
          </person-group>
          <source>Through the Patient's Eyes: Understanding and Promoting Patient-Centered Care</source>
          <year>1993</year>
          <publisher-loc>San Francisco, CA</publisher-loc>
          <publisher-name>Jossey-Bass</publisher-name>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
