Classify first.
Localize after.
Most health-tech “localization” pages start with a factory or a hospital. This one starts with the file: what the asset is, who owns the GCC rights, how EDE or MoHAP will treat it, and whether a buyer exists. Plant and clinical footprint follow that — they do not precede it.
What this program is for
Diagnostics and devices
IVD, imaging, monitoring, dental and specialty hardware that still need a UAE classification.
Specialty and consumer health
Oral formats, sprays, nutraceutical-adjacent SKUs where pharmacy is the first commercial door.
Digital health
Software and data products that only localize if residency, buyer and licence path are real.
What we will not write on this page
We do not bypass EDE or MoHAP
We map the file to the right lane and assemble what those bodies actually ask for. No sandbox shortcut.
We do not award a hospital
Clinical sites are candidates after qualification. 360Disruption does not assign investigators.
We do not name a data-center deal
Sovereign residency is a requirement to test, not a G42 contract we pretend to hold.
We do not sell a plant as week-one FDI
Assembly and manufacturing are destination outcomes. They wait on classification, demand and ICV logic.
How a health-tech file moves
Is there a UAE case
Asset inventory, ownership, free GCC rights, home classification, likely UAE lane, first channel. Go / hold / redirect.
Proof, not presence
Regulatory path, commercial evidence, pharmacy or distributor where the SKU fits, clinical exploration only if the asset requires it.
The licence the file earned
Entity, importer or marketing authorization holder — only the structure the evidence supports.
People, stock, then plant
Warehousing, QA, assembly, manufacturing — sized to demand. Not to a localization slogan.
The sequence lives on uaehealthpathway.com. The healthcare platform is 360FutureHealth. This page is the 360Disruption sector program that runs both.
Pharmacy is a path. It is not the market.
For selected SKUs, Zaitoona is a pharmacy and retail door while the longer file is built. That is useful. It is not GCC coverage, and it is not a substitute for classification.