Case Study – 2024

Electronic Medical Record (EMR) - Payment Processing and Remote Patient Monitoring (RPM)

Electronic Medical Record (EMR) - Payment Processing and Remote Patient Monitoring (RPM)

Role

UX Designer

Business Analyst

Timeline

Nov 2024 - Apr 2025

Team

Product Owner

Business Analysts

UX Designers

Engineers

Skills

UI Design

User Research

Dev Handoff

Role

UX Designer

Business Analyst

Team

Product Owner

Business Analysts

UX Designers

Engineers

Timeline

Nov 2024 - Apr 2025

Skills

UI Design

User Research

Dev Handoff

Role

UX Designer

Business Analyst

Team

Product Owner

Business Analysts

UX Designers

Engineers

Timeline

Nov 2024 - Apr 2025

Skills

UI Design

User Research

Dev Handoff

1 - Overview

Simplifying healthcare

Navigating one's health journey can be daunting – I believe in the importance of helping patients understand the ins-and-outs of living a healthy life and the systems that go along with it. For this project, I was able to work as both UX Designer and Business Analyst, gathering insights, analyzing requirements, and designing two key features for an EMR system – payment processing and remote patient monitoring.

2 - Problem

Payment processing and remote patient monitoring

I was responsible for finalizing requirements and designs for payment processing, integrations, and remote patient monitoring features. Although different, their overall goals were the same – streamline workflows so that users can access their healthcare information in one place.


Prior to modernizing our client's system and processes, manual data entry and in-person transactions were the norm. With our new EMR system, patients and providers now have the opportunity to connect online and in-person, allowing for faster, more efficient healthcare for all.

3 - Design Process

Ins and outs

Stepping into the Business Analyst role, I collaborated with our Product Owner and Technical Lead to finalize workflows and diagrams that display the relationships between the payment processing workflow and affected parts of the entire solution.


Below is a snapshot of one of the diagrams for payment processing.

In addition to creating workflows and diagrams, I have also written requirement documents containing user stories, acceptance criteria, and other functional requirements. Afterward, I switched into the UX Designer role and started planning layouts via wireframes and designing high-fidelity mockups.

4 - Final Solution

From requirements to designs

Getting to experience working in both Business Analyst and UX Designer roles was quite eye-opening. From aligning with our Product Owner and Technical Leads to generate feasible workflows, designing those exact workflows, and then eventually performing dev handoff, it was daunting yet rewarding to contribute from multiple perspectives.

Payment Processing

The payment processing workflow spread across multiple areas of the system. From the patient portal, appointment scheduling, intake, and RCM, it was important that we made it simple and intuitive for all users, both patients and internal staff.

Figure 1. High-fidelity mockups of payment collection within the patient portal.

Figure 2. Make Payment modals used across the system.

Remote Patient Monitoring (RPM)

The RPM feature was one I found interesting due the the direct communication between the patient and their provider. Through remote patient monitoring, a provider is able to monitor their patient's progress and overall health by using devices that send data to their system directly from the devices themselves.


A key focus in designing this feature was clear, intuitive, and helpful language within the process. It was important that both patient and provider understood where each individual was in the health plan and what was needed to be done. This also meant that data that was being collected and sent had to be visualized properly for both parties.

Figure 1. Configure Accounts screen, Notifications list, and Unauthorize Device dialog.

Figure 2. Monitoring screen, data visualization, and Assigned Devices modal.