[data-colorid=dohwf794oh]{color:#97a0af} html[data-color-mode=dark] [data-colorid=dohwf794oh]{color:#505968}[data-colorid=j3t7movkb6]{color:#97a0af} html[data-color-mode=dark] [data-colorid=j3t7movkb6]{color:#505968}[data-colorid=qhpg0wvyi7]{color:#97a0af} html[data-color-mode=dark] [data-colorid=qhpg0wvyi7]{color:#505968}
| Target release | 13 Dec 2024 |
| Epic | Type /Jira to add Jira epics and issues |
| Document status | DRAFT |
| Document owner | Vikas Chowdhry |
| Designer | Meha Elhence (Unlicensed) Vikas Chowdhry Sally Hong NC (Unlicensed) |
| Tech lead | @ lead |
| Technical writers | @ writers |
| QA |
Objective
-
We need to create/evolve a new UI for the TraumaCareAI landing app that can incorporate multiple AI models (the current one is specific to trauma mortality).
-
The model specific view (for trauma mortality for example) needs to be updated or evolved as well for three reasons
- The current UI looks dated/stale 2)
- Our model now has more variables and can perhaps provide more information than what this UI can provide (for example - our model can now run earlier than previous 12 hour pst admission limit) 3)
- The current UI visually looks too similar to blinkUX stuff. Even though at the end of the day these are generic UI elements - cards, tables, line graphs etc. and we created the entire app from scratch, we should get more visual separation.
The best way to generate ideas for this project will be think of it from first principles and assume that we don’t have the current UI.
Who faces this problem and how important is it to them?
Our product’s end-users: trauma and critical care medical team need to understand the output from our AI models so that they can incorporate that information in their decision making process. Without a user experience that aligns with their workflow needs, AI model is useless/less-useful to them.
How do they solve these problems today?
Typically, today, trauma and critical care medical teams don’t have access to applications with UX that is built around their needs. The IT teams at these health systems attempt to configure more generic UI that is available from EHR vendors for these workflows which is far from optimal.
Success metrics
| Goal | Metric |
|---|---|
Assumptions
Requirements
| Requirement | User Story | Importance | Jira Issue | Notes |
|---|---|---|---|---|
| HIGH | ||||
Open Questions
| Question | Answer | Date Answered |
|---|---|---|
Out of Scope
App does not need to be mobile friendly. It will only be accessed via standard, desktop version of the browser.