Social Case Management for UNICEF

I was the only developer on a social case management system for the UN and UNICEF. It keeps one secure record of each social case, shares it across subsystems, and turns it into reports for decision makers. It is part of the UNICEF social protection work I built at Nabdah, which served 5,000+ beneficiaries.

The problem

Social protection agencies worked with case data spread across several subsystems. They needed one trusted record per case, access away from the office, and reports for decisions. The data is sensitive, so each person may see only what their role allows.

How it works

• One central registry. Every registrant has one record in a central MySQL database. The subsystems work from that record.
• An API between subsystems. The subsystems exchange data through one defined API, so an update in one place is visible in the others.
• Role-based access. Authentication and a permission model per role decide who can see and change each part of a case.
• Web and mobile. A JSF web interface, and a mobile app for work in the field.
• Reports. Reports built from the central data support decisions by the agencies.

Result

• Part of the UNICEF social protection work that served 5,000+ beneficiaries.
• The systems I ran at Nabdah kept about 99.8% uptime.
• I built it alone, from requirements to backend, front end, and mobile app. I later built the sibling system, ISPMIS, on the same stack.

My role

Sole developer, on contract through Nabdah (2017 to 2021). I owned the backend in Java, the web interface in JSF, the MySQL database, the API between subsystems, and the mobile app.

About the client: UNICEF.