Healthcare Infrastructure # 01
A modular hospital information system designed to digitize healthcare operations and support scalable hospital infrastructure.
Role
Product engineer
Status
Selected work
Stack in practice
- Java
- What it does
Build typed backend services and domain logic.
- How it is used
Model business rules in classes, expose service contracts and verify them with automated tests.
- How I use it
I model hospital workflows and business rules in the backend services.
- Spring Boot
- What it does
Structure Java applications with configurable web and data services.
- How it is used
Connect controllers, business services and repositories through dependency injection.
- How I use it
I organize hospital APIs into controllers, business services and persistence layers.
- React
- What it does
Build interactive web interfaces from reusable components.
- How it is used
Use props, state and hooks to connect screens to application data and user actions.
- How I use it
I build the hospital workspace as reusable screens for clinical and administrative workflows.
- TypeScript
- What it does
Make JavaScript data contracts explicit before runtime.
- How it is used
Define types for component props, API responses and application state, then check them during builds.
- How I use it
I define the frontend's API contracts, form values and component props explicitly.
- PostgreSQL
- What it does
Persist structured application data with relational guarantees.
- How it is used
Define schemas, constraints and migrations, then read and update data through SQL transactions.
- How I use it
I persist hospital records and service data using relational schemas and migrations.
- Kafka
- What it does
Distribute durable events between independent services.
- How it is used
Publish to topics and process events with consumer groups, versioned contracts and retry handling.
- How I use it
I connect hospital domains through events such as patient changes, appointments and billing updates.
- Redis
- What it does
Store fast-access and short-lived data outside the main database.
- How it is used
Use scoped keys, expiration times and explicit invalidation for cached values.
- How I use it
I cache authorization lookups and invalidate cached permissions when access rules change.
- Docker
- What it does
Package applications and their runtime dependencies.
- How it is used
Build images from Dockerfiles and coordinate local services with Docker Compose.
- How I use it
I start the hospital services and their infrastructure together with Docker Compose.
- Kubernetes
- What it does
Describe and orchestrate containerized service deployments.
- How it is used
Declare deployments, services, configuration and ingress routing in manifests.
- How I use it
I describe service deployments, configuration and routing in the project's Kubernetes manifests.
- GitHub Actions
- What it does
Automate repository checks and delivery tasks.
- How it is used
Define event-triggered workflows that run builds, tests and deployment steps on runners.
- How I use it
I automate repository checks with versioned CI workflows before delivery.
The brief
Make the complex feel calm without hiding what matters.
This project started with a familiar tension: powerful software often asks too much of the people using it. The work was to reduce noise, reveal the important path, and give the system a structure people could trust.
I worked across product definition, interface architecture, and the underlying services that make the experience reliable in practice.
Open channel