Case study
Clamo — moving years of clinic licensing records out of Excel
A licensing platform for hospitals whose history lived in spreadsheets. The import had to be safe to run twice, and the APIs had to be fast enough for a frontend team to build on.
- Role
- Backend Developer, IQ Tech
- Timeline
- Jun 2025 — Jul 2025
- Location
- Kitob, Uzbekistan
- Live
- clamo.uz
- Stack
- DjangoPostgreSQLGitGitLab
The problem
The licensing centre kept years of hospital licensing records in Excel files. The new platform needed that history inside a relational schema, and the import had to survive being run more than once: a half-finished migration must not leave duplicated or partial records behind.
What I built
- Modelled the licensing domain in Django and PostgreSQL first, so the import had a schema with real constraints to fail against instead of a dumping ground.
- Wrote import scripts that validate every row before writing and key each record so a re-run updates instead of duplicating. The migration became safe to repeat while the source files were still being cleaned.
- Designed the REST APIs the frontend team integrated with, and cut response times by roughly 20% by removing N+1 queries and adding the indexes the real access patterns needed.
Result
- Thousands of legacy records moved into the new system without manual re-entry.
- The import could be re-run on demand as source files were corrected.
- Roughly 20% faster API responses after query optimisation.