Ebenezer Osei-Bonsu
Back to all work

Case study · Healthcare · Devnest

Kordzi EMR

paperless hospital management

Ownership: Team · Senior QA

My role: Senior QA Engineer at Devnest Systems, as part of the delivery team.

Sector
Healthcare & life sciences
Context
Devnest Systems
Ownership
Team · Senior QA
Kordzi EMR dashboard showing admitted patients, appointments and bills, a visit-trends chart by pay-group category, and available beds per ward.
Kordzi EMR appointments calendar in month view, for managing patient appointments with doctors.

Real screenshot · seeded test data

01 — What it was

A paperless electronic medical records and hospital management system, built to support a hospital’s workflow regardless of its size.

02 — Why it mattered

Moving a hospital off paper touches admissions, appointments, billing and wards at once, so the system has to be dependable from day one.

03 — My role

Senior QA Engineer | Systems Implementation Engineer at Devnest Systems, as one member of the delivery team. I didn’t build the system.

04 — Technical problems

Its size: like GWTS, it has many modules and sections, and each needed covering end to end. Its integrations with other systems also had to be tested, not just the EMR on its own.

05 — What I did

As part of the Devnest team, I contributed to end-to-end quality validation and launch of the Kordzi EMR core, across its modules and its integrations with other systems. I ran Playwright regression suites, and supported data migration and multi-tenant setup with Postman and SQL Server. I also took part in production deployments, and trained and supported end users through documentation and remote troubleshooting.

Kordzi EMR pay-group management screen listing insurer, company and private accounts with their billing type.
Real screenshot · seeded test data

06 — Tools

Playwright, Postman, Microsoft SQL Server

  • Playwright
  • Postman
  • SQL Server

07 — Result

Launched as a paperless hospital management platform.

08 — What I learned

On a system this large, regression suites have to carry the parts already covered. That's what freed my attention for the integrations with other systems, where the hardest testing was.