Details of request “累計住院及危殆/嚴重數目

Event history

This table shows the technical details of the internal events that happened to this request on AccessInfoHongKong. This could be used to generate information about the speed with which authorities respond to requests, the number of requests which require a postal response and much more.

Caveat emptor! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on AccessInfoHongKong. How, why and by whom requests are categorised is not straightforward, and there will be user error and ambiguity. You will also need to understand FOI law, and the way authorities use it. Plus you'll need to be an elite statistician. Please contact us with questions.

id event_type details created_at described_state calculated_state last_described_at link
14871  sent    2022-08-29 15:34:45 +0800  waiting_response  waiting_response  2022-08-29 15:34:46 +0800  outgoing  
14876  response    2022-08-31 18:01:07 +0800        incoming  
14972  followup_sent    2022-09-06 11:22:54 +0800  internal_review  internal_review  2022-09-06 11:22:54 +0800  outgoing  
15028  response    2022-09-09 17:07:11 +0800        incoming  
15030  response    2022-09-09 17:07:14 +0800    waiting_response  2022-09-16 09:29:28 +0800  incoming  
15086  status_update  described_state  2022-09-16 09:29:27 +0800  waiting_response  waiting_response  2022-09-16 09:29:28 +0800   
15183  response    2022-09-21 15:43:15 +0800        incoming  
15185  response    2022-09-21 15:43:17 +0800        incoming  
15251  followup_sent    2022-09-22 15:55:32 +0800  internal_review  internal_review  2022-09-22 15:55:32 +0800  outgoing  
15339  response    2022-09-30 09:43:36 +0800        incoming  
15341  response    2022-09-30 09:43:38 +0800        incoming  
15502  response    2022-10-11 14:31:54 +0800        incoming  
15504  response    2022-10-11 14:31:56 +0800    not_held  2022-10-11 16:02:27 +0800  incoming  
15506  status_update  described_state  2022-10-11 16:02:27 +0800  not_held  not_held  2022-10-11 16:02:27 +0800   
18434  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
18435  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
18436  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
18437  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
18438  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
18439  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
18440  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
18441  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
18442  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
18443  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
18444  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
18445  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
18446  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
18447  edit metadata  allow_new_responses_from  2023-04-12 11:45:10 +0800         
30156  edit metadata  allow_new_responses_from  2025-05-02 11:45:44 +0800         
30157  edit metadata  allow_new_responses_from  2025-05-02 11:45:44 +0800         
30158  edit metadata  allow_new_responses_from  2025-05-02 11:45:44 +0800         
30159  edit metadata  allow_new_responses_from  2025-05-02 11:45:44 +0800         
30160  edit metadata  allow_new_responses_from  2025-05-02 11:45:44 +0800         
30161  edit metadata  allow_new_responses_from  2025-05-02 11:45:44 +0800         
30162  edit metadata  allow_new_responses_from  2025-05-02 11:45:44 +0800         
30163  edit metadata  allow_new_responses_from  2025-05-02 11:45:44 +0800         
30164  edit metadata  allow_new_responses_from  2025-05-02 11:45:44 +0800         
30165  edit metadata  allow_new_responses_from  2025-05-02 11:45:44 +0800         
30166  edit metadata  allow_new_responses_from  2025-05-02 11:45:44 +0800         
30167  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30168  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30169  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30170  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30171  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30172  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30173  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30174  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30175  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30176  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30177  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30178  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30179  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30180  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30181  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30182  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         
30183  edit metadata  allow_new_responses_from  2025-05-02 11:45:45 +0800         

Here described means when a user selected a status for the request, and the most recent event had its status updated to that value. calculated is then inferred by AccessInfoHongKong for intermediate events, which weren't given an explicit description by a user. See the search tips for description of the states.

You can get this page in computer-readable format as part of the main JSON page for the request. See the API documentation.