Responsibility & architecture
Technical Lead for occupational health, safety and corrective-action workflows.
Constraints
Compliance, incidents and worker-health follow-up share organizational context but require distinct roles and access boundaries.
Domain-focused backend modules
Express modules separate compliance, incident investigation, corrective actions and occupational health. React and TypeScript support the interface.
Engineering tradeoff: Domain separation clarifies ownership; cross-module reporting still needs explicit definitions and authorization checks.
Tenant-aware database infrastructure
The codebase includes Prisma and PostgreSQL infrastructure for organization-scoped data access.
Engineering tradeoff: The presence of this infrastructure does not establish that every production module has migrated to it.
Architecture overview based on implementation scope. The tradeoffs describe engineering considerations, not measured outcomes.
Delivery context
The public product is positioned as a test deployment with Conformity, CAPA, HealthMeter and SafetyBot. Measured safety or compliance improvements are not claimed.
The challenge
Occupational health teams, safety managers and HR need shared visibility across audits, incidents, preventive actions and worker-health follow-up. NormSafety brings these workflows into a single platform.
Technical scope
I lead the technical work on NormSafety. The application combines a React, TypeScript and Vite frontend with a Node.js/Express API. Backend modules separate compliance, incident investigations, corrective actions and occupational health, with dedicated organization, role and authorization layers. The codebase also includes Prisma/PostgreSQL infrastructure for tenant-scoped data access.
Platform scope
Conformity, CAPA and HealthMeter organize compliance work, corrective and preventive actions, and occupational health follow-up. SafetyBot supports assisted recommendations; the public site presents the platform for test deployments.