Skip to content
Lumimeds project logo

Lumimeds

SQA

Lead QA Engineer

Visit Live Site

Overview

Lumimeds is an advanced healthcare platform designed to streamline patient-provider interactions through telemedicine, pharmacy management, and appointment handling — all in one seamless ecosystem.

As Lead QA Engineer, I owned the responsibility of ensuring excellence, consistency, and user trust across the entire platform — from backend APIs to patient-facing UI.

The Problem

Healthcare software requires extreme precision — one small bug can disrupt real patient care. Multiple interconnected modules with shared data dependencies, real-time features requiring precision testing, and critical HIPAA compliance needs.

The Solution

Designed a modular test plan divided by product area, built a scalable QA framework with version-controlled test suites, implemented real-time defect tracking, and created a cross-portal testing matrix for the Admin, Provider, and Patient portals.

Key Contributions

End-to-End Product Understanding

Invested time to fully understand workflows from patient booking to provider encounters to pharmacy fulfillment, identifying undocumented edge cases.

  • Mapped complete user journeys across Admin, Provider, and Patient portals
  • Identified undocumented edge cases through thorough workflow analysis
  • Created comprehensive understanding of data dependencies between modules

Scalable QA Framework

Designed a modular test plan divided by product area with reusable, version-controlled test suites.

  • Appointments: Time zone validation, slot conflicts, status transitions
  • Messages & Notifications: Real-time counter updates, read/unread states
  • Encounters: Dynamic forms, prescription flows, attachments
  • Pharmacy: Patient selection, prescription preparation, crash handling

Cross-Portal Testing

Built a cross-portal testing matrix highlighting dependencies and side effects across Admin, Provider, and Patient portals.

  • Tested holistic flows across all three portals
  • Prevented dozens of potential live issues
  • Ensured data consistency across all portals

Example: If a provider updates an encounter, notification triggers for the patient, and admin dashboard updates real-time.

Impact Metrics

Post-Deployment Bugs

Before

Multiple per release

After

Zero for 5 releases

Testing Turnaround

Before

Standard timeline

After

40% reduction

Release Confidence

Before

Moderate

After

Very High

Tech Stack

Testing & QA Management

JIRATestRailClickUp

Automation & Debugging

PostmanSwaggerBrowser DevTools

Collaboration

SlackGitHubLoom

Challenges

1

Multiple interconnected modules with shared data dependencies — solved with cross-portal testing matrix

2

Real-time features requiring precision testing — solved with comprehensive sync testing plans

3

Staging vs production environment differences — solved with split testing strategy

4

Frequent releases creating regression risk — solved with smarter regression grouping (40% faster)

5

HIPAA compliance requirements — solved with security-focused testing protocols

Key Results

  • Zero post-deployment critical bugs for 5 consecutive releases
  • Reduced testing turnaround by 40% through smarter regression grouping
  • Identified high-severity crashes in pharmacy workflows before production
  • Improved communication between QA and development teams
  • Contributed UX-level insights beyond traditional bug reports

Leadership

Worked at the intersection of development, design, and product management — transforming business logic into flawless user journeys. Advocated for user-centric quality ensuring features made sense for real-world healthcare audiences.

Key Takeaways

  • Always test like a user, not a tester
  • Communication is the bridge between finding and fixing
  • A great QA doesn't just identify issues — they prevent them
  • Healthcare software requires extra diligence
  • Quality became a culture, not a checkbox