HORIZON HIS
Turning a complex HIS vision into a navigable product experience
Product Design-led prototype for SALUX's next hospital information system.
- Role
- UX Lead / Product Designer
- Domain
- Healthtech / Hospital Information System
- Year
- 2025
- Deliverable
- High-fidelity navigable prototype
- Context
- Presented at Hospitalar 2025
- Status
- Presented and reviewed
SALUX's next Hospital Information System
SALUX wanted to materialize its vision for a new Hospital Information System in a market with established platforms such as MV and Tasy. The goal of this phase was to make that vision tangible enough to experience, discuss and present before committing to a complete production implementation.
The work started from a strategic product question, not from a production roadmap.
Making a broad HIS vision tangible before full implementation
A hospital information system can contain a large number of workflows, users, states and dependencies. The challenge was to decide what needed to exist in the prototype so the product vision could become concrete, navigable and presentable for Hospitalar 2025.
The phase had to stay focused on clarity, not on premature build scope.
End-to-end Product Design ownership
I was UX Lead at SALUX and the Product Designer directly responsible for HORIZON HIS. No other Product Designer was dedicated to HORIZON, while the other designers I led remained focused on other SALUX initiatives. That focus allowed me to concentrate on the HIS vision.
- Journey selection
- Experience structure
- UX
- UI
- Component strategy
- Prototype construction
- Product-vision presentation
The overview establishes breadth. The details below highlight selected areas of the mapped experience at a readable size.
Selecting the journeys that made the vision understandable
The goal was not to reproduce every possible HIS workflow. The Product Design decision was to identify the journeys and states necessary to communicate how HORIZON should behave as a coherent product experience.
Building the experience, not the infrastructure around it
A complete Design System was intentionally not the priority for this phase. The focus was to build the reusable component foundation necessary for consistency, prioritize journeys and prototype work, and keep iteration fast.
This was a phase-specific Product Design decision, not a general statement about design systems.
Designing the product before committing to building it
The high-fidelity navigable prototype made the future HIS tangible. It supported experiencing proposed flows, understanding behavior, and reviewing and discussing product direction before full implementation.
Presented to the CEO as the proposed Hospitalar experience
The approach and prototype were presented to and reviewed with the CEO as the Product Design direction intended for Hospitalar 2025. The purpose was to demonstrate that the intended experience could be materialized and discussed without making full implementation the first step.
The product experience at Hospitalar 2025
HORIZON was presented at Hospitalar 2025. SALUX positioned HORIZON as its main product at the event, and visitors at the SALUX presence could experience the product vision.
From abstract vision to navigable product experience
SALUX moved from an abstract HIS ambition to a concrete product experience that could be navigated, discussed, reviewed and presented.
- Selected journeys structured
- Coherent interface created
- Focused reusable component foundation
- Navigable prototype delivered
- Executive discussion supported
- Hospitalar presentation enabled
High-fidelity prototyping as strategic product work
High-fidelity prototyping can be a strategic Product Design tool when the primary uncertainty is the product experience itself. A product phase does not always require the maximum possible infrastructure; it requires the level of structure necessary to answer the current product question.
This is author reflection, not a business claim.