Clinfotech
Hospital System — Complex UX for simplifying clinical workflows, patient records, and staff dashboards
Hospital System — Complex UX for simplifying clinical workflows, patient records, and staff dashboards
Challenge
Modern hospitals manage hundreds of medications, complex inventory systems, regulatory compliance requirements, and numerous stakeholders — yet most hospital management systems were built on outdated paradigms that don't reflect how healthcare actually works.
Clinfotech's challenge was to build a unified system that simultaneously served pharmacists, nurses, administrative staff, and hospital leadership with a single platform. Each user type had fundamentally different needs, workflows, and pain points. The UX challenge was not just to accommodate these differences, but to make them feel like one coherent system rather than separate tools stitched together.
Users
Clinfotech serves four distinct user groups within hospital systems, each with different expertise, workflows, and time pressures.
Pharmacists
Manage drug inventory, pricing, compliance, and patient medications. Need real-time visibility into stock levels and regulatory requirements. Work under strict time constraints.
Nursing Staff
Administer medications and need quick access to drug information, dosing guidelines, and patient records. Often work on mobile devices in patient rooms.
Administrative Staff
Handle claims processing, billing, and insurance coordination. Need tools that reduce manual entry and flag issues early.
Hospital Leadership
Make strategic decisions about medication costs, compliance risk, and operational efficiency. Need dashboards, reports, and insights that distill complexity into actionable data.
The system needed to feel like it was designed for each group specifically, even though they all operated from the same underlying database.
My Role
I led UX strategy and design for the Clinfotech hospital management system, focusing on making complex workflows feel intuitive across four distinct user groups.
My focus was to make hospital staff feel like the system understood their constraints and priorities, not like they were conforming to the system's logic.
Research
Research involved spending time in actual hospital environments observing how staff currently managed medications, complied with regulations, and coordinated care.
Key research findings:
Key insight
Hospital staff don't want to learn a new system — they want the system to understand their existing workflows and make them easier, not different.
Problem
The core problem was that hospital staff managed medication workflows across fragmented systems that didn't communicate with each other. A pharmacist's inventory data didn't talk to the nurse's bedside system. Neither talked to the billing system. And none of them provided leadership with the insights needed to make cost-effective decisions.
The UX problems
1. Role-specific complexity
One interface can't serve pharmacists managing inventory, nurses administering care, and administrators processing claims. Each role needs different information prioritized differently.
2. Information overload
Drug information includes dosing, interactions, contraindications, pricing, and regulations. Nurses need just dosing. Pharmacists need everything. The UI needs to adapt.
3. Speed vs. completeness
Bedside nurses need information instantly. Pharmacists need depth. Finding the right balance without forcing users to choose is the core challenge.
4. Regulatory burden
Compliance requirements are non-negotiable, but they shouldn't create friction in everyday workflows. The UX must enforce compliance invisibly.
5. Mobile and desktop parity
Some staff work entirely on phones at the bedside. Others need desktop depth for serious analysis. Neither experience can be compromised.
Design goal
Create a unified hospital platform where pharmacists, nurses, administrators, and leadership each experience an interface designed for their specific role, even though they're all working with the same data.
Architecture
The system was organized around role-based views that adapted interface, information hierarchy, and available actions based on who was logged in.
PRIMARY WORKFLOWS
Drug Search → Inventory Management → Compliance Review → Claims Processing → Analytics Dashboard
Role-based navigation:
All roles worked with the same underlying data, but the interface reflected what mattered to each group.
Wireframes
Wireframes were designed to show how the same core functionality could be presented completely differently depending on the user's role and context — pharmacy management for one group, clinical support for another, business intelligence for a third.
High-fidelity mockups were created for:
Evolution
The design evolved through six phases, each addressing a core challenge in unifying a complex hospital system.
01 — Role-based architecture
Established that users logged into fundamentally different systems based on their role, not just different views of the same interface.
02 — Drug information hierarchy
Designed context-aware drug information that showed pharmacists everything, but nurses only critical details in seconds.
03 — Inventory visualization
Created real-time inventory dashboards that made stock levels, alerts, and reorder points immediately visible.
04 — Compliance patterns
Built regulatory requirements into workflows so compliance happened automatically rather than as extra steps.
05 — Mobile-first bedside
Optimized the nurse interface for one-handed mobile use while maintaining feature depth on desktop.
06 — Analytics-first leadership
Designed leadership dashboards that turned transaction data into strategic insights about medication costs and safety.
Final direction
The evolution was about recognizing that "one system for everyone" actually meant "one database, many interfaces" — each adapted to the reality of how staff actually worked.
Decisions
Seven core decisions shaped how hospital staff interact with medications and medication data across the system.
01 — Role determines interface
A pharmacist and nurse searching for the same drug see completely different information prioritized differently. This is intentional.
02 — Compliance is invisible
Regulatory requirements are baked into workflows. Users don't check compliance boxes — the system enforces it automatically.
03 — Context determines depth
Nurses get quick answers. Pharmacists get complete information. Leadership gets aggregates. Same data, different surfaces.
04 — Alerts are filtered
Staff only see alerts relevant to their role. Noise kills trust in the system.
05 — Mobile is first, desktop is deep
Nurses work entirely on phones. Pharmacists need desktop power. Both experiences are complete.
06 — Data is bidirectional
When a nurse logs a medication, it updates inventory. When inventory is updated, nurses see it. No sync delays.
07 — Search is always first
Drug search is the gateway to the entire system. Make search fast and accurate and you've solved 80% of the UX problem.
Reflection
Hospital workflows are constrained by regulations, time pressure, and safety requirements. Good enterprise UX doesn't pretend these constraints away — it designs around them.
01 — One system means many interfaces
A single unified database doesn't require a single unified interface. In fact, it might require the opposite.
02 — Speed is a feature, not a detail
In healthcare, slow software kills. Every extra click or second of load time represents risk and frustration.
03 — Compliance should be invisible
The best regulatory interface is the one users don't notice. Compliance happens as a side effect of good workflows.
04 — Trust is earned through consistency
Hospital staff trust systems that behave predictably. When they can predict how the system will respond, they can work faster and safer.
05 — Mobile is not a secondary experience
For bedside staff, mobile is the primary experience. Desktop is secondary. Don't compromise mobile to add desktop features.
The biggest takeaway from Clinfotech was that enterprise UX isn't about making complex systems simple — it's about making them feel inevitable. When hospital staff use the system, it should feel like it was designed specifically for their workflow, even though it serves four completely different user types with different workflows, different priorities, and different constraints.