Radial Bg
Hoskit

Static Hospital Information System Website

-

Project Category

Stack

Overview

Hoskit is a hospital management system built from the hospital’s internal side — designed to simplify how staff handle patient visits, referrals, and scheduling on a day-to-day basis. As a static application without a live database connection, it focuses purely on demonstrating the full frontend experience: registering a patient for a visit, assigning that patient to the nearest available hospital, setting up an appointment, and placing it directly onto a calendar for easy tracking.


This project was built together with Alfan Olivan, who took on a dual role as both a frontend developer and project manager keeping our workflow on track, and Judha Maygustya, who led the UI/UX design and shaped how the product should feel to use. I worked as the full frontend developer on the team, responsible for turning every design decision into a functioning, polished interface.

Tech Stack

These are the tools and libraries I used with my team to bring Hoskit’s frontend to life, chosen to keep the interface fast, consistent, and pleasant to interact with.

  • Next.js
  • TypeScript
  • Tailwind CSS
  • shadcn/ui
  • motion.dev

Features

Referrals

This feature lets hospital staff assign a patient to a specific doctor based on a clear reason for the visit, direct them to a specific hospital, and attach any files relevant to that patient’s case — such as prior medical records or supporting documents. It was built to mirror how referrals actually happen in a real hospital workflow, keeping every relevant detail attached to the right patient from the start.

Patient

The Patient feature acts as the core of the system’s patient management — giving staff a clear, centralized view of patient profiles and their visit history. It was designed to make it easy for hospital staff to look up, update, and keep track of patient information without digging through scattered records.

Dashboard

The Dashboard gives staff an at-a-glance overview the moment they log in, surfacing recently accessed menus alongside charts summarizing hospital data. It was designed to cut down on unnecessary navigation, so the most relevant information and shortcuts are always within reach.

As the Frontend Developer on this project, I focused on making sure every one of these features felt cohesive and intuitive from a staff member’s point of view — since a hospital’s internal tools need to be fast and dependable above all else.

Things I Learned

Working on Hoskit pushed me to think more seriously about component scalability. With features like Referrals, Patient, and Dashboard all sharing overlapping UI patterns, I learned how to design components that could flex across different contexts without turning into one-off, disposable code.

I also became a lot more intentional about folder structuring as the project grew. Early on, it was easy to let files pile up without a clear system, but I learned to organize the codebase in a way that stayed navigable even as more features were added. On top of that, working through referrals, appointments, and calendar scheduling all interacting with each other taught me a lot about complex state management — specifically how to keep interdependent flows predictable instead of letting shared state turn into a tangled mess. These lessons pushed me to write code that’s not just functional, but genuinely maintainable as a project scales.

@ Mohamad Rafi Irfansyah 2024