Author: Emily Ying Yang Chan Holly Lam Janice Ho

For heat warnings to work, Hong Kong must have one clear, integrated system

Source(s): South China Morning Post
  • On the hottest day of the year, three different warnings were in force, having come on at different times – an integrated system would more clearly communicate the risk
  • Besides policy and supportive employers, public awareness and education is also important as temperatures continue to rise with climate change

Hong Kong’s new heating stress warning system for workers, introduced by the Labour Department last month, is a good start to the city’s management of health emergencies and disaster risks from climate change. This comes as research shows strong associations among temperature, morbidity and mortality in Hong Kong.

[...]

But what should be tackled is how to integrate this new system with the Hong Kong Observatory’s existing hot-weather warnings to simplify the city’s health disaster warning system for heat risks. There have been successful examples in the use of typhoon and rainstorm warning systems for workers.

[...]

Tier 1 is triggered by a heat index of 29.5 with Tier 2 warnings in place when the heat index hits 30.5. These thresholds are scientifically based – at 29.5, the excess hospitalisation ratio starts to pick up, increasing more rapidly after 30 and, by 30.5, reaches an alarming level.

[...]

In contrast, the new three-tier Heat Stress at Work Warning has thresholds for amber, red and black set at heat index readings of 30, 32 and 34 – which look too conservative. This is particularly because outdoor workers are much more exposed to weather than the general population.

[...]

Explore further

Hazards Heatwave
Themes Early warning
Country and region Hong Kong (China)
Share this

Please note: Content is displayed as last posted by a PreventionWeb community member or editor. The views expressed therein are not necessarily those of UNDRR, PreventionWeb, or its sponsors. See our terms of use

Is this page useful?

Yes No
Report an issue on this page

Thank you. If you have 2 minutes, we would benefit from additional feedback (link opens in a new window).