MOVO-X
Loading MOVO-X…
Rolling out a queue management system across 5, 10, or 28 hospital locations (like KPJ) is a different challenge from a single-site deployment. This guide covers the project governance, phasing strategy, and risk management for a network-scale rollout.
Appoint a Programme Director (typically Group IT Director or COO) with authority over all site implementations. Establish a Programme Board meeting monthly. Require each hospital to appoint a Site Lead who is accountable for their local deployment.
Wave 1 (pilot, 1–3 hospitals): highest-volume, most technologically mature, with experienced IT staff. Wave 2 (early adopters, 5–10 hospitals): high-readiness sites. Wave 3 (mainstream, remaining hospitals). Each wave validates the approach and informs the next.
After Wave 1, document the standard system configuration: queue templates, appointment types, HIS integration parameters, kiosk placement guidelines, training curriculum. Each subsequent hospital uses this template, with site-specific adjustments only. Deviations require PMO approval.
Not all hospitals use the same HIS. Build a HIS inventory: which hospitals use which system? Build integrations for the most common HIS first (covers the most hospitals). Plan for long-tail HIS integrations in Wave 3.
For 28 hospitals with 2 kiosks each: 56 kiosk units. Order hardware 12 weeks before first deployment (supply chain delays are common). Stage hardware at a central warehouse. Deploy with 2-person installation teams working 2 sites per week.
Each hospital gets 30 days of intensive support post-go-live: vendor engineer on-site for first 3 days, daily check-in calls for weeks 1–2, weekly review for weeks 3–4. Issues logged and resolved within 48 hours during hypercare.
Never skip the pilot wave. The first 3 hospitals will surface integration issues, workflow mismatches, and staff training gaps that you cannot anticipate in planning. The insights from Wave 1 save months of rework in Wave 2 and 3.
Resist pressure to go faster. Hospital network deployments that rush Wave 1 to Wave 2 almost always encounter the same problems at each Wave 2 site — multiplied.
Build a shared community of practice between Site Leads across the network. Monthly calls where Site Leads share what is working and what is not accelerate adoption across the whole network.
Wave 1 (3 hospitals): months 1–4. Wave 2 (10 hospitals): months 5–10. Wave 3 (15 hospitals): months 10–18. Total: 18 months for a well-managed 28-hospital rollout. Faster is possible but increases risk.
Wave 1 hospitals need to be above average IT maturity — they will identify integration and configuration issues. Wave 3 hospitals (lower maturity) benefit from the standardised template developed in Waves 1 and 2, plus the lessons learned from earlier sites.
KPJ Healthcare Berhad uses a centralised Group IT function that manages vendor relationships and technical standards, with Hospital Directors accountable for operational adoption. Effective multi-hospital rollouts require both central coordination and local ownership.
MOVO-X deploys AI kiosk and queue management systems for clinics and hospitals across Malaysia and Southeast Asia. Talk to our team about your specific setup.