Surgeons need a cross-platform application to monitor the recovery process of their patients in order to measure the effectiveness of implants. There must be an emphasis on data visualization and communication to ensure that the pre and post op data can be interpreted correctly. For the purpose of this project, we focused on a Posterior Lumbar Inter body Fusion.

The goal is for our solution to incorporate all Stryker implants. Surgeons should be able to view data to determine if different implants are successful and if they should or should not be used for future surgeries. Stryker should also be able to access this data to look at the success of their implants. Surgeons should also be able to look at individual patient data.  

Users

It was important to keep the user groups in mind when designing our final solution. Our primary user group is a spinal surgeon, whose goal is to be able to access patient from pre and post operation in order to visualize the success rate of different implants.

Stryker is a secondary user whose goal is to view implant success on their implant parts to determine which parts to use.

Deliverables

1. A report that outlines the design process (documentation)
   
2. Written synthesis of research findings
   
3. Mockup: A hi-fidelity, interactive prototype for desktop
   

• Health data visualizations tend to focus on three areas: Healthcare Provider (data), Personal Health (practices), and Population Health (volume)
  
• Quantitative measurements include alignment, control, and balance
  
• Questionnaires, indexes, and scores can be used as measuring tools
  
• Surgeons look for bone growth, solid fusion, and spinal stability
  
• Features used to understand patients include status tracking, feedback through portals, and performance reports
  

We started ideaing using low-fi sketches to put our ideas on paper. Individually we created a series of four desktop pages that exemplified a dashboard, patient data, implant data, and brand success.After individual sketching, we did a master list activity. We managed to create a master list that included the features that many of us agreed to provide or consider for the surgeon’s application. This will help us with detailed ideation as we move further into the design process. The list is as follows:

• Visualizing adjustment
  
• Pre-op visual
  
• Patient comparison
  
• Graph of angle progression
  
• Pre/post-op comaprison
  
• Add comments
  
• Recent activity
  
• Search
  
• Pain level scale
  
• 2 different headers
  

• Next meeting date for patient's info page
  
• Progress bar for patient page
  
• Visualization of implants
  
• Interactive visual input
  
• Flagged/bookmarked patients
  
• Filter patients
  
• Calendar
  
• Overall implant success
  
• Hover over feature
  

Next we moved on to low-fi mockups of our design. The goal of our low-fis was to implement what we learned from our preliminary sketches and create a first iteration of what our final product will look like. Using Figma, we created lo-fi mockups of what we thought the layout of the desktop app would look like. Since these are lofi mockups, the majority of the screens are filled with place holders instead of actual information. As our process continues, we will continue to move towards higher fidelity mockups. Below are a few of the screens:

• Representatives are the party who choose the implant
  
• Make scans more prominent
  
• Stryker and Surgeon have different goals
  
• Make it easy for surgeon to get the info they need
  
• What about other users such as nurses?
  

• Fusion is the ultimate measure of success
  
• Surgeons evolved from looking at x-ray to measuring success based on how the patient feels
  
• Brand distinction might not be important (K2M and Stryker are merging)
  

• The representative chooses the parts to use in the surgery, not the surgeon
  
• The surgeon and representative communicate to determine success of parts
  
• Representatives need to see implant data
  

• 1st iteration: We had each team member individually apply the items from the master list to their individual lo-fi design, and translate it into a mid-fi
  
• 2nd iteration: We combined designs from members on each of 2 teams into one design, thereby creating 2 combined mid-fis with the best features from the individual mid-fis.
  
• 3rd iteration: We did more research into how the data portions of our design could be visualized, since were mostly placeholders. We then translated our data visualization research into another iteration.