Claims operations platform
Approved, production-ready standby (failover) for the company's live claims system at Zororo-Phumulani
Role-based platform for funeral-case processing: claims, cash services and courtesy services. Approved, production-ready standby (failover) for the company's live claims system at Zororo-Phumulani.
Architecture
Problem
Funeral-case processing needs role-based claims, cash services and courtesy services, with department hand-offs and a standby if the current claims system fails.
What I built
Roles and shifts route into a case state machine with department hand-offs across claims, cash services and courtesy services. PII is encrypted at the app layer, masked by default on list views, and every PII read is audited. Middleware and API layers both enforce access. A public case-tracking link and compliance exports sit beside the staff workspace.
Engineering decisions
- 01
The platform is a failover for the current claims system, not a replacement that is live today.
- 02
A case state machine plus role- and shift-based routing handles department hand-offs.
- 03
PII is encrypted at the app layer and masked by default on list views; who read PII is written to an audit log.
- 04
Access is enforced at both the middleware and API layers.
- 05
A public case-tracking link and compliance exports support POPIA-aware operations.
Outcome
Approved, production-ready standby (failover) for the company's live claims system at Zororo-Phumulani. Private repo.
