Quick question for medical device engineers:
When building a medical device UI, what actually slows you down the most?
A) Display & touch integration
B) Application logic and workflow design
C) Both
For many teams, the hidden time sink isn’t the core function of the device. It is everything around making the display system stable, responsive, and manufacturable. Interface validation, signal tuning, boardtoboard compatibility… all of this adds up before real UI work can even begin.
This challenge became especially clear in a recent healthcare application in Japan. The device required a compact embedded display with additional functions such as a buzzer, realtime clock (RTC), and EEPROM. Annual volumes were relatively low, making a full PCB redesign impractical. The priority was clear: add functionality without disrupting an already validated hardware architecture.
By using a semicustom Smart Embedded® approach that integrates the display, touch, and MCU board into a single module, the team was able to move forward without rebuilding the PCB, while still supporting a customized 4 mm PMMA cover lens. Instead of managing multiple integration risks, engineers could focus directly on UI behavior and system logic.
This is the core idea behind Smart Embedded® displays:
Reduce integration overhead so development effort goes where it matters.
For medical equipment teams, that means faster UI development, fewer unexpected delays, and a clearer path from concept to deployment—without turning display integration into a project of its own.
So back to the question:
A, B, or C?
Please Contact Us for your design thoughts and learn more information.