Neda.
One platform. Different centers. Clearer healthcare workflows.
A physician management and appointment platform for public hospitals and healthcare centers. Shared workflows, configurable features, and role-aware interfaces support the needs of different institutions.
Frontend architecture & delivery lead
Husan
May 2023 onward
The problem worth solving.
Healthcare centers share many operational needs, but their requirements are rarely identical. The frontend needed to accommodate those differences without duplicating the entire application for every deployment.
Where I took ownership.
- Led frontend architecture and delivery.
- Analyzed common and center-specific requirements with product and backend teams.
- Established reusable patterns for forms, permissions, components, and data access.
Decisions behind the experience.
Shared core, configurable features
Used modular configuration and feature controls to keep common functionality reusable while accommodating center-specific workflows.
Access that follows the role
Applied protected routes, permission-aware rendering, session handling, and support for users working across multiple roles.
Structure for long-term change
Separated presentation from API mapping, combined shared components with healthcare-specific UI, and kept forms and data flows consistent.
Engineering that serves the workflow.
A configurable frontend foundation supports related healthcare deployments while preserving a consistent administrative experience and room for future requirements.
Discuss a similar challenge
