metaSOFT Incident & Risk Management enables any staff member to report a clinical or operational incident in under 2 minutes, with structured root-cause analysis tools, corrective action tracking and patient safety dashboards — all aligned with JCI, CBAHI and WHO international standards.
Any staff member submits an incident or near-miss report in under 2 minutes from any device; anonymous reporting is available to encourage a just-culture environment.
Structured RCA with fishbone diagram, 5-Why and fault-tree analysis tools are built into the workflow; findings are linked directly to corrective action tasks.
Corrective and preventive action tasks are assigned to named owners with due dates; escalation fires automatically for overdue actions; closure requires evidence upload and supervisor sign-off.
Near-miss rate, sentinel events, time-to-close and repeat-incident rate visible to quality and risk management without waiting for a weekly summary email.
One-click report packs for JCI, CBAHI and MOH submissions; all incidents are classified to WHO international adverse event taxonomy and NCC MERP medication error scale.
Severity 1 incidents trigger immediate notification to the quality officer, CMO and CEO; escalation rules, notification recipients and response timelines are configured per incident type.
The Incident Management module is fully integrated with clinical data in the HMS. When a medication error incident is reported, the system automatically pulls the patient's medication administration record and the dispensing log into the investigation workspace — investigators do not request reports from pharmacy; they see the data directly. When an equipment failure is reported, the asset register entry from the Fixed Assets module is attached to the incident record.
For accreditation bodies and regulators, the module generates submission-ready report files with all required data fields pre-populated. JCI Required Organisation Practices, CBAHI Hospital Standards and MOH adverse event reporting requirements are mapped to incident types in the system — so every completed incident record automatically satisfies the documentation requirement for the applicable standard.
