CASE STUDY · 03
Aldino Medika
Medical Check-Up (MCU) Management System
- Client
- Aldino Medika
- Role
- Frontend Engineer, API Contract Designer, Deployment
- Context
- Side project
Overview
End-to-end platform for corporate medical check-ups: client onboarding, MCU planning, patient registration, inspection results, SOAP notes, and result delivery.
Staff app
For clinic staff, doctors and coordinators: run MCU projects, record results, print labels, publish reports.
Client portal
For client companies: MCU projects, analytics, and result documents.
What I built
- Built the staff app and client portal on Next.js App Router in an Nx monorepo, with shared api-client, schemas, and query libraries
- Designed the backend ↔ frontend API contracts (errors, pagination, filter/sort syntax, dates, enums, uploads, JWT flow), used by both the Django and frontend teams
- Built a type-safe data layer: Zod schemas validate every API response at runtime and map errors straight into React Hook Form
- Owned production deployment
Engineering highlights
Contract-first API with end-to-end type safety
Domain-driven architecture (one Django app per business domain)
Designed for SATUSEHAT (HL7 FHIR R4) interoperability: FHIR-aligned visit status, NIK identity, ICD-10; integration designed, not yet built
Key features
- MCU project lifecycle (Draft → Scheduled → Ongoing → Completed)
- Multi-step patient pre-assessment with lock/unlock
- Hierarchical inspection catalog with bulk result submission
- Permanent medical record numbers across visits
- SOAP clinical notes with ICD-10 coding
- XLSX bulk import; bulk fitness certificates as a ZIP of PDFs
- Zebra label printing for specimens and patients
- Project analytics with patient-level drill-down
- Versioned consent management and full audit trail
- Role-based access control
Stack
Frontend
Next.jsReactTypeScriptNxTanStack QueryReact Hook FormZodPlaywrightBiome
Backend
DjangoDjango REST FrameworkJWTPostgreSQLRedisAWS S3Docker