// 01, The Device
The analysis was right. The interface had become a liability.
Electrolyte measurement systems are used to analyze blood chemistry. The results they display inform clinical decisions. An interface that’s slow, confusing, or difficult to navigate under pressure can be a patient safety risk.
This manufacturer had the analysis technology right. The interface didn’t match it. A text-based UI that made sense when the product launched had become a liability as competitors raised the bar on user experience and the clinical environments using the device grew more demanding.
The internal Android development team was fully committed to other high-priority programs. The product launch deadline wasn’t moving.
// 02, The Challenge
Medical-grade Android, inside an existing architecture, on a deadline.
The challenge wasn’t finding someone who could build an Android UI. It was finding someone who could build a medical-grade Android UI, one that worked within the manufacturer’s existing firmware and software architecture, met the standard clinical environments demand, and could be delivered on a timeline the internal team couldn’t hit.
Architecture decisions made here would also carry forward. Code that couldn’t be reused across the product line meant higher costs on every future release. That constraint shaped the entire approach.
// 03, What Geisel Built
Safety-critical HMI, reusable by design.
Safety-Critical HMI Development for a Diagnostic Medical Device
Geisel worked directly with the manufacturer’s firmware and software teams throughout the program. The solution incorporated existing code wherever feasible, avoiding unnecessary rewrites, reducing risk, and keeping the project on schedule. Where new code was required, it was architected for reuse across the manufacturer’s other products, lowering development costs on future releases.
The application software was simplified without sacrificing capability, a meaningful achievement in a medical device context where complexity tends to accumulate and rarely gets removed.
Screen Navigator Storyboard for Reduced Development and Maintenance Overhead
Geisel created a screen navigator storyboard that mapped the full interface flow before a line of production code was written. That upfront investment reduced software development and maintenance effort on this release and will shorten development time for future product iterations.
In a product category where every release requires rigorous validation, reducing the complexity of what needs to be validated has compounding value.
Android Expertise That Carried Forward
The manufacturer’s engineers had direct access to Geisel’s Android expertise throughout the engagement, including best practices, architectural guidance, and practical knowledge that didn’t stay within the boundaries of this project. That transfer of knowledge carries forward into how the internal team approaches future Android development.
// 04, The Result
Delivered ahead of schedule, architected for the next release too.
A preliminary version of the new product was made available to the manufacturer’s scientists ahead of schedule, compressing the overall product development cycle at a point in the program where time is most valuable. The interface shipped. The deadline held. The architecture was built to serve the next release, not just this one.
In a clinical setting, the interface between a clinician and a diagnostic device is part of the instrument itself. It needs to be clear, fast, and reliable in real-world conditions. Geisel delivered on that standard, stepping in to meet an aggressive timeline and building an architecture designed to support this release and everything that follows.
Medical Device Manufacturer · Diagnostic Blood Analyzer
