The "ShareMedata" healthcare platform aims to streamline and optimize the management of electronic health records (EHRs) in private medical practices. The platform focuses on providing a user-friendly interface for healthcare professionals to efficiently capture, organize, and access patient information.
The primary mission of the project is to enhance the user experience of healthcare professionals interacting with the "ShareMedata" platform. The goal is to address usability issues, improve system adaptability to different medical specialties, and ensure efficient data management in both routine and emergency medical scenarios.
Research Methods:
SUS Test (System Usability Scale):
Objective: Evaluate the usability of the Electronic Health Records (EHR) platform.
Approach: Provides a score reflecting perceived ease of use by users.
Heuristic Evaluation:
Objective: Identify strengths and weaknesses of the module using Jakob Nielsen's 10 heuristic principles.
Approach: Determine areas for improvement from a usability perspective.
Contextual Observation:
Objective: Uncover current user needs and observe the work context to gather information on technologies used, frequency of clinical data collection, doctor-patient interaction with clinical data, and interaction with the current system.
Card Sorting:
Objective: Use card sorting to generate a site map accessible to key users, organizing necessary data into categories or sections for later use in design.
Prototyping:
Low-Fidelity Prototyping:
Objective: Develop an initial low-fidelity design of the module.
Approach: Create sketches and wireframes representing the general structure and layout of interface elements. This low-fidelity prototype allows for an overall view of the design and quick concept and navigation testing.
High-Fidelity Prototyping:
Objective: Develop a high-fidelity prototype based on the validated low-fidelity design.
Approach: Create complete screens and interactions, reflecting the final visual appearance and user experience, including colors, typography, images, and specific functionalities.
Persona Creation:
Objective: Create personas based on gathered information to better understand the characteristics, needs, and behaviors of different user groups.
Customer Journey Map:
Objective: Identify critical moments and gain an overview of the user experience with the current system.
Approach: Provide valuable information related to platform improvement needs and opportunities.
User Testing:
Objective: Validate the design from the user's perspective.
Approach: Conduct tests to identify potential improvements and ensure the final product meets user expectations and needs.
The Results
Heuristic Evaluation:
Real-world Relationship:
Implementation of understandable text and icons promotes user interaction.
Cohesiveness in adjusting knowledge levels enhances user experience.
Opportunities for improvement: Enhance content presentation logic, align options with user thinking, optimize language for quicker comprehension, and improve button labeling specificity.
Control and User Freedom:
Undo functionality and clear exit options provide user flexibility.
Lack of font size customization may limit user personalization.
Overall, good attention to control and freedom aspects.
Consistency and Standards:
Link labels align with destination titles for coherent navigation.
Inconsistencies in action results need attention to avoid confusion.
Adequate error prevention measures in place.
Recognition over Recall:
Effortless retrieval of information is a strength.
Areas for improvement include minimizing reliance on prior page information and optimizing information organization for easy retrieval.
Flexibility and Efficiency of Use:
Effective flexibility and efficiency with room for improvement.
Opportunities include minimizing repeated data entry, incorporating shortcuts, and evaluating user-customizable actions.
Aesthetic and Minimalist Design:
Focus on essential information with room for text presentation improvements.
Considerations for concise and fluid text presentation.
Help and Documentation:
Attention to help information with room for optimization.
Considerations for improved visibility, contextual adaptation, and comprehensive guidance.
Visibility of System State:
Clear purpose and objectives for user understanding.
Feedback during and after actions contributes positively.
Opportunities to improve site structure visibility, including visible titles and breadcrumb navigation.
Consistency and Cognitive Load:
Lack of consistency and identifiable patterns.
Adjustments needed for a more uniform user experience.
Contextual Observation:
Capturing essential data device-wise in clinical history.
Detailed examination of specific tasks, scenarios, key participants, and physical environments.
Identification of challenges and repetitive processes in the current system.
Usability Score:
Calculation based on Busquets' method resulted in a score below Sauro's average, indicating areas for improvement.
General Observations:
Chaotic work environment, particularly during emergencies.
Multiple tasks performed simultaneously using computers and smartphones.
Observations on task analysis, acute episodes, chronic diseases, and undifferentiated symptoms.
Personas:
Developed personas based on contextual observations.
Consideration for accessibility scenarios in persona creation.
SUS Usability Test:
10 healthcare professionals recruited for SUS usability testing.
Calculated scores indicated areas for improvement in usability.
This case study outlines the comprehensive approach to evaluating and improving the "ShareMedata" healthcare platform, incorporating heuristic evaluation, contextual observation, usability tests, and user persona development. The identified areas for enhancement will guide the design and development efforts to ensure a more effective and user-friendly healthcare experience.
Conclusion:
Initial Screen
The initial screen, designed in read-only mode, displays the patient's complete medical history, ensuring a clean interface without accidental changes. Essential information is shown, empty states at the start of the consultation, and a panel highlighting vital signs, observations, and allergies. Additionally, an icon for consultations and emergencies is incorporated to change the working mode of medical staff.
Navigation and Data Organization
The top tabs function as a navigation system, allowing quick access to specific areas such as the reason for consultation, physical examination, diagnosis, and treatment. Attachments are displayed chronologically, providing a clear and organized view. The toolbar offers options to request complementary studies and generate digital prescriptions, with the integration of an artificial intelligence assistant to provide support and accurate answers.
Visual Identity Improvement
The implementation of an atomic design-based system ensures consistency in colors, typography, and behaviors. Primary and secondary colors are established, and the palette is simplified to avoid misunderstandings. In the login screen, the option for external login is added, providing convenience and security to users who prefer trusted external accounts.
Continuous Improvement Proposals:
Iterative Feedback: Initiate an iterative feedback process with medical staff and end-users for continuous adjustments to the interface and functionalities.
User Testing: Conduct user testing to assess the usability and effectiveness of the system, incorporating feedback for additional improvements.
Scalability: Consider the scalability of the system for future expansions and updates, ensuring platform flexibility.
Security: Prioritize and enhance security measures, especially in handling sensitive patient data.
Performance Optimization: Continue optimizing system performance to ensure a smooth and efficient user experience.
Implementing these proposals will not only enhance the interface and user experience but will also ensure that ShareMedata is a robust platform centered around the needs of medical staff and patients.
Feature Release and Success Metrics:
Future iterations may involve ongoing user testing to gather post-launch feedback and further refine the application based on real-world usage patterns.
