๐Ÿฅ SCM ยท NUMS System Architecture ยท Management & Audit
๐Ÿฅ

SCM-NUMS
System Architecture

Supply Chain Management โ€“ Nurse Uniform Management System

For Management & Auditors ยท Audit-Ready Architecture

Version: 3.0 Date: August 2026 Classification: Internal

Table of Contents

1. Executive Summary
2. System Overview & Scale
3. Enterprise Architecture Layers
4. Governance & Audit Framework
5. Security Architecture
6. Role-Based Access Control (RBAC)
7. Data Architecture & Database Schema
8. Process Flows
9. Integration Points
10. Deployment & Infrastructure
11. Audit Assurance & Compliance
12. Management Benefits

1. Executive Summary

The Supply Chain Management โ€“ Nurse Uniform Management System (SCM-NUMS) is a centralized, secure, enterprise-scale web application designed to manage the entire lifecycle of nursing uniforms across KwaZulu-Natal.

๐ŸŽฏ Purpose: To provide a unified, transparent, and auditable platform for nurse registration, uniform ordering, supervisor approval, distribution tracking, financial reporting, and compliance monitoring.

32,000+
Nurses & Users
Province-wide coverage
11
Health Districts
KwaZulu-Natal
700+
Health Facilities
Hospitals, clinics, CHCs
โœ… Key Management Benefits
  • Provincial standardisation of uniform ordering
  • Real-time visibility of orders and approvals
  • Complete financial accountability
  • Audit-ready transaction logs
  • Fraud prevention and detection
๐Ÿ“‹ Audit Readiness
  • Every transaction is logged and time-stamped
  • Full traceability to individual users
  • Continuous audit evidence
  • Internal & external audit support
  • PHSDSBC Resolution 1 of 2022 compliant

2. System Overview & Scale

2.1 System Purpose

SCM-NUMS is a provincial enterprise platform that digitizes and automates the uniform management process for all nurses in KwaZulu-Natal. It replaces manual paper-based systems with a secure, web-based solution that provides end-to-end visibility and control.

2.2 Scale & Reach

32,000+
Active Users
Nurses & authorised staff
5,000+
Monthly Orders
Average monthly volume
100%
Audit Coverage
All transactions logged

2.3 Stakeholder Groups

Stakeholder Role System Access
NursesPlace uniform orders, view historyNurse Portal
SupervisorsApprove/reject orders, activate nursesSupervisor Dashboard
District AdministratorsManage district operationsDistrict Admin Portal
Head OfficeOversee province, manage settingsHead Office Portal
AuditorsReview logs, verify complianceAudit Reports

3. Enterprise Architecture Layers

A four-layer architecture designed for security, scalability, performance, and maintainability

Presentation
Nurse Portal Supervisor Dashboard District Admin Head Office Responsive
Application
Auth Orders Approvals Catalogue Reports Audit
Data
User & HR Orders Catalogue Audit Logs Reference
Infrastructure
Linux Apache PHP 8.2 MariaDB HTTPS Backup
๐Ÿ” Authentication

Session-based login with password hashing

๐Ÿ›ก๏ธ RBAC

Role-Based Access Control with data filtering

๐Ÿ“‹ Audit

Complete transaction logging with IP tracking

โ˜๏ธ Scalable

Supports 32,000+ users with high availability

4. Governance & Audit Framework

A comprehensive governance model ensuring accountability, transparency, and compliance at every level of the organisation.

๐Ÿ”‘ Accountability
  • All actions traceable to individuals
  • Clear role-based responsibilities
  • Audit trail for every transaction
๐Ÿ‘๏ธ Transparency
  • Real-time visibility of orders
  • Status tracking for all orders
  • Open reporting and analytics
๐Ÿ“œ Compliance
  • PHSDSBC Resolution 1 of 2022
  • KZN Health ICT governance
  • Public service regulations

4.1 Audit Trail Architecture

๐Ÿ‘ค
Who
User ID, Role
๐Ÿ•
When
Date, Time
๐Ÿ“
What
Action, Values
๐Ÿ“
Where
IP, Device
โ“
Why
Reason

4.2 Audit Logging Tables

Table Logged Actions Key Fields
admin_audit_logAdmin actions: activate, deactivate, editadmin_id, action, description, ip_address, created_at
supervisor_approvalsOrder approvals, rejections, re-openingssupervisor_id, nurse_id, action, rejection_reason
document_audit_trailDocument uploads and changesuser_id, action, filename, file_size, ip_address
uniform_ordersOrder status changesid, status, approved_by, approved_date

Audit Assurance: The system provides continuous audit evidence rather than retrospective manual verification. All electronic records are time-stamped and tamper-evident.

5. Security Architecture

Multi-layer security protecting all system components and data

๐Ÿ” Layer 1: Authentication
  • Password hashing (bcrypt)
  • Session-based authentication
  • Session timeout (30 minutes)
  • Secure password reset flow
  • Failed login attempt tracking
Secure
๐Ÿ›ก๏ธ Layer 2: Authorization
  • Role-Based Access Control (RBAC)
  • Menu-level permissions
  • Action-level permissions
  • Data-level filtering
RBAC
๐Ÿ”’ Layer 3: Data Security
  • Input sanitization
  • Prepared statements
  • XSS prevention
  • CSRF protection
  • SSL/TLS encryption
Protected
๐Ÿ“‹ Layer 4: Audit
  • Admin action logging
  • Supervisor approval logging
  • IP address tracking
  • User agent tracking
Audited

5.1 Security Controls Summary

Control Type Implementation Purpose
Access ControlRBAC with role-based permissionsEnsure only authorised users access data
Data ProtectionEncryption, sanitization, prepared statementsProtect data from unauthorized access
Audit TrailComplete logging of all transactionsProvide evidence for compliance
Session ManagementSecure session handling with timeoutPrevent session hijacking
Infrastructure SecuritySSL/TLS, Linux, Apache securitySecure hosting environment

6. Role-Based Access Control (RBAC)

Clear role hierarchy with defined permissions and responsibilities

Head Office Admin

  • Full System access
  • Manage all districts & facilities
  • System settings & configuration
  • Financial reporting (province-wide)
  • Bulk user activation

District Admin

  • Limited Manage nurses in their district
  • District-level reporting
  • Single nurse activation
  • View district orders

Supervisor

  • Restricted Approve/reject supervisee orders
  • Activate nurses under supervision
  • Re-open approved orders for correction
  • View supervisee order history

Nurse

  • Basic Place uniform orders
  • View own order history
  • Edit pending orders
  • Track order status

7. Data Architecture & Database Schema

Centralized data management with 14 core tables organised into logical domains

7.1 Database Platform

MariaDB 10.4+

Relational database architecture

Transaction-Safe

ACID compliance with rollback

Centralized

Single source of truth

Indexed

Optimized for reporting

7.2 Entity Relationship Diagram

๐Ÿ”‘ PK = Primary Key ๐Ÿ”— FK = Foreign Key
nurses_users
๐Ÿ”‘ id INT PK
๐Ÿ”‘ persal_number VARCHAR(100)
surname, name, district
facility, gender
๐Ÿ”— position_id FK
๐Ÿ”— department_id FK
is_supervisor, is_active
uniform_orders
๐Ÿ”‘ id INT PK
๐Ÿ”— user_id FK
order_date, status
approved_by, approved_date
rejection_reason
total_amount DECIMAL(12,2)
uniform_catalogue
๐Ÿ”‘ id INT PK
category, item_name, color
price DECIMAL(10,2)
sizes TEXT
max_quantity_per_order
is_active TINYINT
order_items
๐Ÿ”‘ id INT PK
๐Ÿ”— order_id FK
๐Ÿ”— uniform_id FK
item_name, size, quantity
price, subtotal DECIMAL
admin_users
๐Ÿ”‘ id INT PK
username UNIQUE
password, email
full_name, role
district, is_active
admin_audit_log
๐Ÿ”‘ id INT PK
๐Ÿ”— admin_id FK
action, description
ip_address, user_agent
created_at TIMESTAMP

8. Process Flows

8.1 User Registration & Activation


Registration
โ†’

Persal Validation
โ†’

Pending
โ†’

Supervisor Activates
โ†’

Active

8.2 Order Placement & Approval


Nurse Orders
โ†’

Pending
โ†’

Supervisor Review

Approve
โ†

Reject
โ†

Re-open

Approved
โ†’

Delivered
โ†

Rejected

9. Integration Points

โœ… Active Integrations
  • HR Database โ€“ Persal validation during registration
  • Excel/CSV Export โ€“ Financial and operational reporting
  • Browser Print โ€“ Physical report generation
Active
โณ Future Integrations
  • SCM Stores Module โ€“ Inventory and vendor ordering
  • Active Directory/LDAP โ€“ Single Sign-On
  • Mobile App โ€“ iOS and Android platform
Planned

10. Deployment & Infrastructure

Development

  • Local XAMPP/WAMP stack
  • Developer machines
  • Version control (Git)

Staging

  • Mirror of production
  • Dedicated server (Linux)
  • UAT & Performance testing

Production

  • Red Hat Enterprise Linux
  • Live provincial operations
  • Daily backup protection

11. Audit Assurance & Compliance

Audit Assurance Statement: SCM-NUMS provides continuous, tamper-evident audit evidence for all uniform management transactions. Every action is logged, time-stamped, and traceable to an individual user.

11.1 Audit Evidence Captured

Audit Area What is Captured Where Retention
User ActivityLogins, logouts, failed attemptsSystem logsIndefinite
Account ChangesActivations, deactivations, editsadmin_audit_logIndefinite
Order LifecycleCreation, approval, rejectionuniform_ordersIndefinite
Catalogue ChangesAdd, edit, delete, activateadmin_audit_logIndefinite
System ConfigurationOrder cycles, settings changesadmin_audit_logIndefinite

12. Management Benefits

โœ“
Full Visibility
Real-time order tracking
โœ“
Financial Control
Complete order value reporting
โœ“
Audit Readiness
Continuous audit evidence
โœ“
Fraud Prevention
Full traceability of actions
โœ“
Operational Efficiency
Eliminates manual processes
โœ“
Provincial Standardisation
Consistent across all districts

SCM-NUMS provides the KwaZulu-Natal Department of Health with a fully auditable, transparent, and efficient uniform management platform.

SCM-NUMS ยท KwaZulu-Natal Department of Health ยท Information Technology Division
Version 3.0 ยท August 2026 ยท Proudly South African