Details of request “Another 5 questions about Image sharing of "e-Health Record Sharing System eHRSS"

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
8130  sent    2021-09-30 23:47:11 +0800  waiting_response  waiting_response  2021-09-30 23:47:11 +0800  outgoing  
8131  response    2021-09-30 23:50:11 +0800    waiting_response  2021-10-04 18:30:38 +0800  incoming  
8242  status_update    2021-10-04 18:30:38 +0800  waiting_response  waiting_response  2021-10-04 18:30:38 +0800   
8291  response    2021-10-07 12:18:52 +0800        incoming  
8293  response    2021-10-07 12:18:58 +0800    waiting_response  2021-10-10 17:18:09 +0800  incoming  
8351  status_update    2021-10-10 17:18:09 +0800  waiting_response  waiting_response  2021-10-10 17:18:09 +0800   
8559  response    2021-10-20 18:53:16 +0800        incoming  
8561  response    2021-10-20 18:53:22 +0800    partially_successful  2021-10-31 16:09:32 +0800  incoming  
8803  status_update  described_state  2021-10-31 16:09:32 +0800  partially_successful  partially_successful  2021-10-31 16:09:32 +0800   
12771  edit metadata  allow_new_responses_from  2022-05-01 11:45:06 +0800         
12772  edit metadata  allow_new_responses_from  2022-05-01 11:45:06 +0800         
12773  edit metadata  allow_new_responses_from  2022-05-01 11:45:06 +0800         
12774  edit metadata  allow_new_responses_from  2022-05-01 11:45:06 +0800         
12775  edit metadata  allow_new_responses_from  2022-05-01 11:45:06 +0800         
12776  edit metadata  allow_new_responses_from  2022-05-01 11:45:06 +0800         
12777  edit metadata  allow_new_responses_from  2022-05-01 11:45:06 +0800         
12778  edit metadata  allow_new_responses_from  2022-05-01 11:45:06 +0800         
12779  edit metadata  allow_new_responses_from  2022-05-01 11:45:06 +0800         
22695  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22696  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22697  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22698  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22699  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22700  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22701  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22702  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22703  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22704  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22705  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22706  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22707  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22708  edit metadata  allow_new_responses_from  2023-11-01 11:45:07 +0800         
22709  edit metadata  allow_new_responses_from  2023-11-01 11:45:08 +0800         
22710  edit metadata  allow_new_responses_from  2023-11-01 11:45:08 +0800         
22711  edit metadata  allow_new_responses_from  2023-11-01 11:45:08 +0800         
22712  edit metadata  allow_new_responses_from  2023-11-01 11:45:08 +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.