Details of request “2019冠狀病毒死者的死因實際有多少個與2019冠狀病毒病有關?

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
14238  sent    2022-07-20 16:26:36 +0800  waiting_response  waiting_response  2022-07-20 16:26:36 +0800  outgoing  
14239  response    2022-07-20 16:31:01 +0800        incoming  
14254  response    2022-07-21 18:56:22 +0800        incoming  
14255  followup_sent    2022-07-22 11:04:22 +0800  internal_review  internal_review  2022-07-22 11:04:22 +0800  outgoing  
14256  response    2022-07-22 11:05:07 +0800        incoming  
14392  response    2022-07-28 17:13:43 +0800    partially_successful  2022-07-29 17:59:50 +0800  incoming  
14423  status_update  described_state  2022-07-29 17:59:50 +0800  partially_successful  partially_successful  2022-07-29 17:59:50 +0800   
17495  edit metadata  allow_new_responses_from  2023-01-30 11:45:09 +0800         
17496  edit metadata  allow_new_responses_from  2023-01-30 11:45:10 +0800         
17497  edit metadata  allow_new_responses_from  2023-01-30 11:45:10 +0800         
17498  edit metadata  allow_new_responses_from  2023-01-30 11:45:10 +0800         
17499  edit metadata  allow_new_responses_from  2023-01-30 11:45:10 +0800         
17500  edit metadata  allow_new_responses_from  2023-01-30 11:45:10 +0800         
17501  edit metadata  allow_new_responses_from  2023-01-30 11:45:10 +0800         
29059  edit metadata  allow_new_responses_from  2024-07-30 11:45:11 +0800         
29060  edit metadata  allow_new_responses_from  2024-07-30 11:45:11 +0800         
29061  edit metadata  allow_new_responses_from  2024-07-30 11:45:11 +0800         
29062  edit metadata  allow_new_responses_from  2024-07-30 11:45:11 +0800         
29063  edit metadata  allow_new_responses_from  2024-07-30 11:45:11 +0800         
29064  edit metadata  allow_new_responses_from  2024-07-30 11:45:11 +0800         
29065  edit metadata  allow_new_responses_from  2024-07-30 11:45:11 +0800         
29066  edit metadata  allow_new_responses_from  2024-07-30 11:45:12 +0800         
29067  edit metadata  allow_new_responses_from  2024-07-30 11:45:12 +0800         
29068  edit metadata  allow_new_responses_from  2024-07-30 11:45:12 +0800         
29069  edit metadata  allow_new_responses_from  2024-07-30 11:45:12 +0800         
29070  edit metadata  allow_new_responses_from  2024-07-30 11:45:12 +0800         
29071  edit metadata  allow_new_responses_from  2024-07-30 11:45:12 +0800         
29072  edit metadata  allow_new_responses_from  2024-07-30 11:45:12 +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.