| Literature DB >> 35319469 |
Alexandra T Strauss1, Cameron Morgan2, Christopher El Khuri3, Becky Slogeris2, Aria G Smith3, Eili Klein3, Matt Toerper3,4, Anthony DeAngelo4, Arnaud Debraine4, Susan Peterson3, Ayse P Gurses3,5,6, Scott Levin3,4, Jeremiah Hinson3,4.
Abstract
BACKGROUND: The availability of patient outcomes-based feedback is limited in episodic care environments such as the emergency department. Emergency medicine (EM) clinicians set care trajectories for a majority of hospitalized patients and provide definitive care to an even larger number of those discharged into the community. EM clinicians are often unaware of the short- and long-term health outcomes of patients and how their actions may have contributed. Despite large volumes of patients and data, outcomes-driven learning that targets individual clinician experiences is meager. Integrated electronic health record (EHR) systems provide opportunity, but they do not have readily available functionality intended for outcomes-based learning.Entities:
Keywords: ER; closed-loop learning; emergency medicine; emergency room; feedback; health informatics; human-centered design; outcomes; platform; practice-based learning and improvement; usability
Year: 2022 PMID: 35319469 PMCID: PMC8987968 DOI: 10.2196/30130
Source DB: PubMed Journal: JMIR Hum Factors ISSN: 2292-9495
Figure 1Human-centered design methods used to develop Linking Outcomes Of Patients. CDEM: Center for Data Science in Emergency Medicine.
Examples of high priority questions from the design research stage interview guide.
| Question category | Examples |
| Rapport building | What does a perfect day at the emergency department look like for you? |
| Stress | What things currently complicate your decision making in the emergency department? (individual, institutional, environmental) |
| Feedback | How do you find out what happens to your patients after they leave the emergency department? |
| Design | What format would prefer to receive feedback on what happens to respiratory infection patients and why? (Prompt: ask about how they prefer seeing info, ie, text, charts, images, video, voice messages) |
| Diagnostic/decision making | Walk me through how you develop a set of possible diagnoses and how you differentiate between them to come to a final diagnosis. |
Themes from observations and semistructured interviews during the research stage of the human-centered design studio.
| Theme | Examples of observations | Examples of interview quotations |
| Emergency Medicine clinicians value postencounter outcomes–driven feedback. | Physician writes down patient’s phone number and reports they do this when they want feedback about that patient’s outcome. | |
| Existing systems for delivery of information about patient outcomes are severely limited. | Physician pulls out the list of patients they keep track of from their pocket. Says they are only able to track a couple of patients in each shift. | … |
| Currently available outcomes-driven feedback is predominantly negative. | Physician reports that if something bad happens, clinicians find out from leadership. Physician seems tense when discussing. | … |
| Emergency Medicine clinicians use workaround solutions to obtain outcome information for cases perceived as interesting or high risk. | Physician leaves patient notes unsigned so that patients’ charts will remain in their electronic health record workflow, forcing additional case review |
|
Figure 2Six user personas generated during human-centered design studios and used to drive tool development and to perform internal prototype testing.
Design requirements established during ideation and prototyping phases of our human-centered design studio.
| Design features | Purpose |
| Comprehensive lists | Allows users to find information of all the patients they have cared for |
| Electronic health record interoperability | Allows users to transition between platform and patient’s clinical chart |
| Data tagging | Gives users the power to drill down through the use of data labels/tags |
| Pin a patient | Allows users to prioritize patients of interest for future review |
| Glow moments | Allows other users to appreciate the work of fellow clinicians |
| Task timer | Allows a user to customize their experience based on time availability |
| Home/hospital toggle | Limits visibility of protected health information outside of hospital setting |
| Patient timeline | Allows users to see a patient’s journey after their care |
| Notification/reminder | Allows users to set an alarm to review outcomes |
Figure 3Evolution of Linking Outcomes Of Patients from human-centered design studios going from (A) physician prototypes to the (B) final version used in the usability evaluation. EHR: electronic health record; LOOP: Linking Outcomes Of Patients.
Figure 4Participant attitudes about usefulness of access to outcomes at individual patient level and across all their patients.
Figure 5Participant attitudes about Linking Outcomes Of Patients. LOOP: Linking Outcomes Of Patients.