iAssets · DHA Compliance
DHA medical equipment management standards: the CMMS requirement
The Dubai Health Authority issued its Standards for Medical Equipment Management on 16 November 2023, effective 16 January 2024. The document sets the minimum requirements for managing medical equipment at DHA-licensed health facilities — and it is explicit that a computerized maintenance management system, or an equivalent biomedical engineering system, is required for logging planned preventive maintenance.
For facilities still running maintenance on spreadsheets, that turns a long-standing operational preference into a licensing requirement. This page covers what the standard asks for and how iAssets meets it.
What the DHA standard requires
The standard applies to health facilities licensed by DHA and sets minimum requirements for managing medical equipment across its lifecycle. Central to it is that PPM activities, scheduling, checklists and spare-parts records are logged in a CMMS or biomedical engineering system, and that these records are readily available for audit.
Preventive maintenance frequency is expected to follow the device's risk classification rather than a single blanket interval — which means the system has to support risk-based scheduling, not just a calendar.
- A CMMS or BMES for logging PPM activities
- Scheduling, checklists and spare-parts records held in the system
- Records readily available for DHA audit
- PM frequency based on device risk classification
- Lifecycle management from acquisition through disposal
What this means in practice for Dubai facilities
The practical consequence is that maintenance evidence has to be produced on demand, per device, during an audit. Spreadsheets and email trails technically constitute documentation, but they fail the "readily available" test — assembling the history of one ventilator from three files and a mailbox is exactly the scenario the standard is written to prevent.
The same applies to spare parts: if part consumption is tracked separately from the work order, the record of what was actually done to a device is incomplete.
- Per-device history retrievable during an audit, not reconstructed afterwards
- Checklists completed in the system rather than on paper and filed later
- Spare-part consumption tied to the work order and the device
- Schedules that demonstrably reflect risk classification
How iAssets meets the standard
iAssets holds one lifecycle record per device covering acquisition, every work order and PM, calibration, parts consumed and eventual disposal. Because technicians close work in the system, the audit evidence is produced by the work itself.
It is deployed across the Saudi MOH Tabuk Health Cluster — 12 hospitals and 84 primary healthcare centres — with more than 25,000 medical assets tracked and preventive maintenance coverage raised from roughly 45% to 85%.
- Risk-based PM scheduling per device class
- Digital checklists completed at the point of work
- Spare parts consumed against the work order and device history
- Audit reports generated on demand
- Arabic and English interfaces and reports
- Cloud or on-premise deployment
FAQ
Does DHA require a CMMS for medical equipment?
Yes. The DHA Standards for Medical Equipment Management, issued 16 November 2023 and effective 16 January 2024, require a computerized maintenance management system or biomedical engineering system for logging planned preventive maintenance activities, scheduling, checklists and spare-parts records, with those records readily available for audit.
When did the DHA medical equipment standards take effect?
The standards were issued on 16 November 2023 with an effective date of 16 January 2024. Facilities licensed by DHA have been operating under them since then, which means a maintenance programme still running on spreadsheets is not simply inefficient — it is misaligned with a current licensing standard.
Does the standard apply to clinics as well as hospitals?
The standard sets minimum requirements for managing medical equipment at health facilities licensed by DHA, so its scope follows DHA licensing rather than facility size. Smaller facilities often have fewer devices but the same documentation obligation, which is where a lightweight, well-structured system matters more than a large enterprise deployment.
What does risk-based PM frequency mean?
Rather than servicing every device on an identical interval, PM frequency follows the device's risk classification — so a ventilator or infusion pump is maintained more frequently than a low-risk item. iAssets supports scheduling by risk class, which both satisfies the requirement and concentrates technician time where a failure would have the greatest clinical consequence.
Do spare parts records have to be in the same system?
The standard lists spare-parts records among what must be logged in the CMMS or BMES. Keeping parts in a separate inventory system is a common gap, because it leaves the device history incomplete — you can see that maintenance occurred but not what was replaced, which is precisely the detail an auditor asks about.
Is iAssets used in the UAE?
iAssets' largest verifiable healthcare deployment is the Saudi Ministry of Health Tabuk Health Cluster — 12 hospitals and 84 primary healthcare centres. The platform is built around Gulf regulatory requirements including DHA's, and Intrazero serves the UAE from its Dubai office. We state the deployment where it is rather than implying a UAE reference we do not have.
Can the system be hosted in the UAE?
Yes — iAssets supports cloud and fully on-premise deployment, so hosting can be arranged to meet a facility's data-residency requirements. This is a practical differentiator against global CMMS products, which are generally cloud-only and hosted outside the region.
Bring your equipment records to audit standard
Talk to the Intrazero team about deploying iAssets — the CMMS running the Saudi MOH Tabuk Health Cluster — with Arabic and English interfaces and cloud or on-premise hosting.
Talk to the Intrazero team about deploying iAssets — the CMMS running the Saudi MOH Tabuk Health Cluster — with Arabic and English interfaces and cloud or on-premise hosting.
Programar demo de la plataforma
Experimente el ecosistema. Complete el formulario para alinear su demo con los especialistas de producto correctos.