Flatiron EHR

Overview

This was a design sprint held by Flatiron. The goal of this design sprint was to build a user-friendly EMR to solve the problem of oncologists spend too much time on reviewing the EHR of cancer patients. My role involved in storyboarding, paper prototyping, and interaction design. After the design sprint, I took it further with the feedbacks we received, made improvements on information architecture, designed the new UI, and built the digital prototype.

The Solution

Work smarter, not harder- A EHR system built for Oncologists practice

Flatiron- an EHR dashboard to reduce Ontologists’ time and effort on administration work.

Flatiron EHR is an easy-viewing dashboard for Ontologists to quickly review the patient. Through graphs and charts, ontologists can quickly understand current status of patients, medication reaction and details medication information to facilitate the decision making process.

Prompt

Designing an EHR to better review patient’s information

John Doe is currently on two different treatment regimens for his lung cancer, each containing between 6-10 individual medications. John comes into his doctor's office for chemo treatment. When he's meeting with his doctor, his doctor reviews his treatment plan to understand what medications he has received and when.

Before sending John to have his medications administered, his doctor needs to review much of each medication John will be receiving to make sure that the course of treatment is still appropriate. 

Research

Sketching to understand the doctor’s contexts and needs

Diagnostic Journey

I started with mapping out the flows of follow-up visit to understand the end-to-end diagnostic process and relate to challenges associated with doctors.

When. Assuming each visit is 20 minutes long. A doctor may have 30-40 patients per shift.

Where. At clinic during the day.

Storyboarding

We created storyboarding to visualize the John’s doctor diagnostic experience. The storyboard helped better understand the contexts on how the EHR will be used and the challenges that doctors face.

1. Recap: quickly browse the patient’s information, medical records and symptoms history.

2. Visit & Communicate: listen and assess patient’s description of symptoms and development.

3. Documentation: documenting patient’s symptoms progress and reactions to previous treatment and medication.

4. Diagnosis: review the medications list before making future medical decisions

Competitor Review

What are the existing solution can’t solve?

I also went through some reviews on the oncology EHR reviewing website to identify any feedback from the doctors’ comments, and learnt the current problems doctors are facing and also positive feedbacks so that I can put more emphasis on it.

• "Spend a lot of time on key in.

• No Overview of patients health”Documentation of past events with no sense of what’s current and how our health has evolved over time.”

• Mixed Medication Plans”Current prescriptions mixed with past ones, inconsistent dosage wording, and no link between prescriptions and conditions”

Synthesis

通過查看用戶評論，各種上下文情況和情節提要，我認為以下是我可以解決的一些痛點，以提升整體用戶體驗。

• Fast documentating major concern to health-care professionals is time. The time taken to view charts and enter data can be deterring.

• 無法沿相當相似的路線接受多個作業以提高效率。

• No sense of what’s current and how our health has evolved over time.

• INFORMATION WITH NO SENSE OF PRIORITY

我列出了一些在用戶流程流程中至關重要的階段的好壞經驗。

1. Recap

   • Good Experience：能夠在進行訪談前，快速瀏覽目前的治療階段。

   • Bad Experience：No overview on patient’s medication and health status

2. Visit & Communication

• Good experience：Fast entry and documentation

• Bad experience：

3. Diagnosis:

• Good Experience：能夠examine 上一階段的用藥和藥品細節。

• 不良經驗：。

Design Goals

在進行Lo-Fi原型製作時，我確保屏幕基於2個重要概念

Minimize the effort required to perform necessary tasks.

1) Efficiency:

• Reduce information distraction: clean UI, only emphasize the most important information

• Clear shows a history of medicines administered, the course of treatment, the dates the drugs need to be taken)

  2) learnability: keep the interaction simple and UI consistent to reduce the learning curve:

  3) memorability:

• Take consideration of ontocologist user group, and long-time use scenario
  
  此外，在進行Lo-Fi原型製作時，我確保屏幕基於2個重要概念

  1. 將行動或功能的調用映射到特定區域或屏幕以供承受

  2. 提供不超過2個選項以在任何給定屏幕上執行操作

  應用內導航應用可提供完整的端到端體驗

  • 它可以更好地控制性能測量，並提供非常個性化的建議，以改善駕駛員的性能，最終提升整體體驗。

  • 刪除經驗/表演無法擁有的任何第三方可靠性

  輕巧的應用程序可以完成工作

  • 功能純淨的準系統應用程序。

  • 減少學習新系統的成本

Design Decision 1

Specifically, to ensure it is a helpful tool and is not causing further issues for the patient's safety :

• 藥物治療: 不使用縮寫或非標準命名約定，避免藥物信息混淆

• 實驗數據：根據以前的結果和當前結果將它們清楚地分開，並明確標記需要採取措施的異常結果

• 數值顯示: 實驗室結果和診斷測試通常以數字格式顯示。在千位級別和小數之前添加零，例如1000和0.25，而不是1000和.2。提供正確閱讀和解釋。

• 顯示文字：文本需要在屏幕上輕鬆閱讀，字體不能太小。念縮寫的捷徑，避免和患者交流錯誤。

IA

Mapping out the information architecture of the app

Information architecture could structure the information
EHR在復雜系統中進行有效的用戶體驗設計至關重要。如果所有內容都相同且處於同一水平，則會對可用性產生負面影響。您不想一次展示太多信息；將最重要的信息帶到表面，然後改進搜索和篩選工具，以便用戶可以輕鬆訪問所需的信息
To defines how content will be structured and presented to a user when they are interacting with your design, I organized the app by creating its information architecture.

1. Our team first build out the process of user scenario, and identify the key users needs.

We identify three key user scenarios:
1. Recap: Review the history, status and previous medication
2. Documentation: record patient’s reaction of treatment and medication
3. Diagnosis: Information that help doctor to make dignosis reaction