TABLE 2. Informing engineering design from contextual inquiry.
| Design Characteristic | R | C | F | M | |
|---|---|---|---|---|---|
| Effectiveness | 1. Provide awareness of clinic state. | ✓ | |||
| 2. Support cognitive workload. | ✓ | ||||
| 3. Automate dose calculations. | ✓ | ||||
| 4. Display remaining vials/doses. | ✓ | ||||
| 5. Store data for all users to view. | ✓ | ||||
| 6. Connect to cloud server. | ✓ | ||||
| Efficiency | 7. Provide transparency of inputs. | ✓ | |||
| 8. Aggregate data on one screen. | ✓ | ||||
| 9. Displays history of data inputs. | ✓ | ||||
| 10. Easy to navigate data inputs. | ✓ | ||||
| 11. Easy to update and edit data. | ✓ | ||||
| 12. Minimal time burden to use. | ✓ | ||||
| Satisfaction | 13. Secure data from misuse. | ✓ | |||
| 14. Control user-clinic access. | ✓ | ||||
| 15. Admin controlled accounts. | ✓ | ||||
| 16. Use anywhere in the clinic. | ✓ | ||||
| 17. Cross-platform use. | ✓ | ||||
| 18. Prevents accidental misuse. | ✓ | ||||
| 19. Separate controls from display. | ✓ | ||||
| 20. Separate stakeholder inputs. | ✓ | ||||
| 21. Enjoyable user experience. | ✓ | ||||
| 22. Display username and role. | ✓ |
R – requirement, C – constraint, F – function, and M – means