Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

The User Experience process of healthcare apps

93 Aufrufe

Veröffentlicht am

Healthcare is one of the most sensitive domains, that’s why when you create software apps designed for hospitals, you need to be aware that the main beneficiary of them is the patient. Those being said, and also taking into consideration the specialized users you are working with, the caregivers, in our case, it is very important to follow a protocol when you are designing apps. It is not rocket science, but it is a process that is followed for each project which has as finality an app that will be used in hospitals.

Veröffentlicht in: Design
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

The User Experience process of healthcare apps

  1. 1. the User Experience process of healthcare apps
  2. 2. hello Andreea Popescu A full-time UX Designer at Ascom and part-time at Telekom. I’m passionate about neuroscience, nature photography, and reading. More details on linkedIn.com/andreeazpopescu.
  3. 3. agenda • understanding caregivers • having in mind the patients • take care of the process • repeat for every project (and release) • Q&A
  4. 4. “UX doesn’t live inside our phones or our websites. We need to step way outside of those devices to understand what people are doing in the real world.” Matt Hryhorsky, UX Manager @Shopify
  5. 5. Caregivers
  6. 6. to easily access the right patient’s information
  7. 7. to avoid task stress
  8. 8. to avoid confusion
  9. 9. to communicate faster with other caregivers
  10. 10. to be aware about what’s happening
  11. 11. to have process traceability
  12. 12. Patients
  13. 13. … because they are the really end users.
  14. 14. Process
  15. 15. 1 Understand 2 Research 3 Analyse 4 Design 5 Validate my process
  16. 16. • UEP (Usability Engineering Plan): all the information about the application (e.g. the primary functions of the app, hazarduous situations etc.). • UEF (Usability Engineering File): all the information related to the intended user profiles, groups, personas, storyboards, and the planification for usability testing sessions. • PRS (Product Requirement Specifications): all the requirements for the product, and also the user stories. + the following documents
  17. 17. • IDS (Interaction Design Specifications): a document with the specifications for the developers based on the wireframes and, also, the UI details. Also, this document can be replaced by: ❖ WS (Wireframes Specifications): just the details/specs about the wireframes. ❖ UIS (User Interface Specifications): just the details/specs about the UI. • FUEP (Formative Usability Engineering File): the description of the whole formative usability testing to be + SUS (System Usability Scale) questionnaire. • FUER (Formative Usability Engineering Report): the report created after the usability testing session.
  18. 18. • SUEP (Summative Usability Engineering File): the description of the whole summative usability testing to be. • SUER (Summative Usability Engineering Report): the report created after the usability testing session. • TPU (Test Plan Usability): contains all the dates, summary, and, also, links to all FUEPs created (usability sessions). • TRU (Test Report Usability): the main report with the results for all the usability tests for the product.
  19. 19. Q&A time :)
  20. 20. thank you :)

×