For Dental, Aesthetic, TCM & Specialist Clinic Groups
Training Evidence An Audit Can Trust
Protocols change, staff rotate, audits arrive. MagiLearn OS keeps every branch on the current protocol version, every certification current, and every acknowledgement on record — by name, version and timestamp.

The Problems Every Clinic Group Knows
Protocol Updates Reach Some Branches And Miss Others
Protocols live as versioned SOPs scoped to every branch. Publishing an update re-triggers acknowledgement for everyone affected — nobody works from the old version unknowingly.
“Everyone Was Briefed” Is Unprovable In An Audit
Acknowledgements are recorded per person, per version, with timestamp and IP. The audit answer is a report you export, not a memory you defend.
Front-Desk Service Varies By Receptionist
Front-desk SOPs plus phone-conversation roleplay — the anxious patient, the billing question — rehearsed and scored before they happen live.
Staff Certifications Lapse Unnoticed
The certification register tracks expiry per person; renewal training assigns itself before the lapse and the compliance dashboard stays audit-green.
Built In, Day One
From Hiring To Audit Day
- Clinical-protocol SOPs with versioning and review cycles
- Per-version acknowledgement records with timestamp and IP
- Certification register with automatic renewal assignment
- Front-desk service courses and phone roleplay
- Per-branch compliance dashboards and CSV exports
- Audit-ready records with per-person PDPA export
Certifications
- Nurul AisyahInfection Control · May 2027Valid
- Grace TeoPhlebotomy · Aug 202630 days
- Vikram MenonCPR / BLS · Jun 2026Expired
Renewal training auto-assigned to 2 staff
Audit-Ready, Daily
From New Nurse To Clean Audit
Compliance that accumulates as a by-product of daily work — so audit day is an export, not a scramble.
- Day 1
Policies Before Patients
Hygiene, PDPA and incident-reporting policies acknowledged with version, timestamp and IP — before the first shift.
- Week 1
Clinical Protocols As Micro-Courses
Sterilisation, triage and front-desk protocols in sequence, each gated by a server-scored quiz.
- Week 2
Procedures Observed, Not Assumed
A senior nurse watches the real sterilisation run and signs the checklist — recorded with who, where and when.
- Monthly
Checklists Run Themselves
Equipment checks and cold-chain logs generate on schedule; a missed check flags the practice manager the same day.
- Audit Day
Evidence Exports In Minutes
Per-person acknowledgements, certifications and observation records go to CSV — the inspector gets records, not recollections.
When The Auditor Asks, The Answer Is A Report
“Who read the updated protocol?” has one good answer: a list of names, versions and timestamps, exported in one click. That record builds itself with every acknowledgement — not the night before the audit.
Clinic Questions, Answered Directly
How do we prove staff read an updated protocol?
Every protocol is versioned, and each acknowledgement is recorded against the exact version with the person's name, timestamp and IP. Publishing an update automatically requires re-acknowledgement, and the resulting report exports to CSV for auditors.
What happens when a certification is about to expire?
The register sorts every certificate by urgency — expired, expiring soon, current — and branch managers see their own compliance while HQ sees all branches. Auto-recertification handles the renewals (see Verification on the features page).
Can front-desk staff practise difficult phone calls?
Yes. AI roleplay plays the caller — the anxious patient, the fee dispute — and scores the receptionist against your service rubric, so difficult conversations are rehearsed before they are real.
How is staff personal data handled?
Training records are isolated per workspace and protected by data-layer permissions. Per-person PDPA export and erasure are built into the product, and erasure preserves the anonymous compliance evidence the clinic must retain.