01
User workflow
Define the information and actions required for the intended device workflow.
Medical & Healthcare Devices
Start with the clinical or operator workflow, then choose the HMI platform.
Medical and healthcare devices can have very different display, interaction and software workloads. Define the product workflow and product-specific validation needs before fixing the embedded architecture.
What matters first
Clarify the product constraints before choosing components.
Use these questions to narrow the HMI workload, then compare compute, display, GUI and engineering paths.
02
Display clarity
Set screen size, information density and viewing requirements from actual use cases.
03
System interfaces
Map sensors, host systems, networking and peripheral connections before architecture selection.
04
Validation scope
Identify product-specific software, usability, documentation and validation requirements early in the project.
Architecture options
Let the workload decide the architecture class.
A focused serial or MCU interface, a richer RTOS HMI and an application-class Linux system solve different problems. The HMI Selector uses the rest of your brief to narrow the starting point.
Smart Display / Compact MCU
For focused control and status interfaces where integration effort, startup and cost matter strongly.
Performance RTOS HMI
For richer graphics, more pages and broader I/O while retaining an embedded real-time product model.
Embedded Linux HMI
For complex workflows, larger software stacks, networking, media or application-style functionality.
Reference evaluation path
Turn the application brief into a hardware and software comparison.
No single architecture is assumed for this application. Use the workflow, display, UI, interfaces and project constraints to compare the practical HMI paths.
1 · Device workflow + information hierarchy2 · Display / touch + system I/O3 · Software architecture + update model4 · Validate on target hardware and intended workflow
Planning a product in this category?
Start with the application brief, not a fixed processor.
Use the selector for an initial architecture direction, or share the project constraints for a more specific discussion.