Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the amp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the gotmls domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170
Denggi di Perak Makin Membimbangkan – Independent

Denggi di Perak Makin Membimbangkan

Reading Time: < 1 minute

IPOH, 27 Jun 24 – Peningkatan kes denggi di Perak semakin membimbangkan. Terkini, sebanyak 4,410 kes dilaporkan berbanding 2,726 pada tempoh yang sama tahun lalu. Ini menunjukkan peningkatan sebanyak 162%.

Lima kes kematian direkodkan di daerah Kinta manakala 1 di Manjung.

Menurut kenyataan oleh EXCO Kesihatan negeri Perak, A. Sivanesan, sebanyak 7 lokaliti hotspot aktif (empat lokaliti di daerah Kinta, diikuti dengan dua lokaliti di daerah Larut Matang dan Selama (LMS) dan satu lokaliti di daerah Hulu Perak.

Punca utama kejadian demam denggi yang telah dikenalpasti adalah kerana tempat pembiakan Aedes yang tinggi di lokaliti wabak/hotspot tersebut. Antara tempat pembiakan nyamuk dijumpai adalah di lot kosong terbiar, rumah kosong tidak berpenghuni, longkang yang tidak diselenggara dengan baik, tangki septik individu tidak bertutup/ terdedah, tong tadahan air tidak bertutup di dalam dan luar rumah, di samping sampah sarap yang boleh menakung air di persekitaran.

Jabatan Kesihatan Negeri (JKN) Perak telah melaksanakan aktiviti pemeriksaan tempat pembiakan (PTP) di dalam premis di kawasan kes dan wabak dan diikuti dengan aktiviti penguatkuasaan bagi memutuskan rantaian jangkitan. Sehingga 22 Jun 2024, sebanyak 232,469 premis telah diperiksa dengan 2,508 notis kompaun kesalahan dan 295 notis pembersihan di bawah Seksyen 8(1) Akta Pemusnahan Serangga Pembawa Penyakit 1975 telah dikeluarkan.

Selain itu, Pejabat Kesihatan Daerah dengan kerjasama Pihak Berkuasa Tempatan (PBT) pihak JKN Perak juga melaksanakan aktiviti larviciding, Semburan Ruang Termal (SRT) dan Semburan Ultra Low Volume (ULV) di semua lokaliti berwabak dan berpotensi wabak di negeri Perak bagi membasmi vektor pembawa penyakit demam denggi iaitu nyamuk Aedes.

Sivanesan berkata beliau menasihatkan orang ramai supaya sentiasa peka dengan kebersihan sekitar kediaman dan lakukan pembersihan kawasan setiap minggu bagi mengelak menjadi tempat pembiakan nyamuk Aedes.