Electronic Medical Record

How might we simplify the data entry process for nurses gathering and reviewing patient information for physicians?

Healthcare

Overview

The work on this page is part of a design exercise for a private healthcare software company that creates electronic records for medical professionals and patients.
Due to the secure nature of healthcare services, I removed company and branding as a design candidate. The work on this page demonstrates my thought process in a short, fixed timeframe.

Problem

Data collection in short amount of time The constant expansion of support for healthcare providers, home, and mobile support is ever-changing and a necessary process to support our patients and medical professionals.

Staying up to date with modern technology The advancement of technology and our ability to build in-house software presents an opportunity to evaluate how we can reimagine how we collect and review patient information.

Outcome

Prioritize questionaires Gather information based on appointment visit whether follow-up or concern.

Become omnichannel Support handheld devices on the go and not constraint to a room.

Role UX Designer Candidate

Duration 3-days

Contributions user research, user design

Platform Web

Constraint

Assumptions needed to be made to test and validate due to limited context on current experience being evaluated.

Critical 3-day turnaround Limited time to conduct research and ideation sessions for user validation.

Approach

My primary user is a nurse role collecting information from a patient to prepare for a physician. Key areas to focus on gathering include, but are not limited to current and past health records, immunization and childhood diseases, and family history.

Ideation

Initial exploration for user interface layout based on analysis from looking at competitor experiences and grouped information.

Patient questionnaires Capture information prior to physician visit.

Review and save updates Sync updates across for patient and physician to review.

User Flow

Features

For this design challenge, responsive and interaction design were critical considerations. I needed this interaction to be mobile and an immediate form of validation to confirm that the required fields of data were captured.

Design system Standardize components to differentiate component states during user interactions.

Visual language CSS styles to differentiate primary, secondary and error or required information.

Navigation panel Maximize screen real estate by truncating when in client focus view.

Key screens

Sign on screen Secure patient privacy and verify nurse & physician access by location

Navigation panel Expand/Collapse navigation options

Patient vitals View vitals and collect new patient information

Family history Collect/update patient family history information

Chart review Verify new and existing information before updating for physician notification

Takeaway

This design exercise was one of my first introductions to using prototyping to convey behavior beyond interactive states. The opportunity to regain screen real estate allowed me to start expanding my deeper understanding of spacing principles in user interfaces.

Lessons learned

Ambiguity is a normal reality when navigating a problem space and areas to focus on to address with iterative updates.
Focus on context, user goals and tasks before investing too much time on visual design that may not solve user painpoints.
There is a distinction outside of mobile first foundations when it comes to designing for native iOS and Android and not just responsive web.

Some potential next steps

Conduct a moderated usability test to define user insights and additional areas for improvement.
Test and iterate until design interactions are meeting goals presented by stakeholders.
Focus on patient user experience and their after visit for sentiment and satisfaction qualitative insights.

View all work