Details of request “Request access to all communications between Minister for Health and ASADA between 23/12/2014 and 13/1/17

Event history

This table shows the technical details of the internal events that happened to this request on Right to Know. 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 Right to Know. 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 created_at described_state last_described_at calculated_state link
21820  sent  2017-01-20 10:41:16 +1100  waiting_response  2017-01-20 10:41:16 +1100  waiting_response  outgoing  
21981  response  2017-01-27 11:16:36 +1100    2017-02-02 15:49:31 +1100  waiting_response  incoming  
22179  status_update  2017-02-02 15:49:31 +1100  waiting_response  2017-02-02 15:49:31 +1100  waiting_response   
22858  response  2017-02-20 11:10:56 +1100    2017-03-03 15:51:00 +1100  waiting_response  incoming  
53779  overdue  2017-02-21 00:00:00 +1100         
23356  status_update  2017-03-03 15:51:00 +1100  waiting_response  2017-03-03 15:51:00 +1100  waiting_response   
23901  response  2017-03-20 11:53:01 +1100    2017-03-21 12:40:47 +1100  waiting_response  incoming  
23956  status_update  2017-03-21 12:40:47 +1100  waiting_response  2017-03-21 12:40:47 +1100  waiting_response   
23976  response  2017-03-21 16:35:08 +1100    2017-03-23 16:25:18 +1100  waiting_response  incoming  
55736  very_overdue  2017-03-23 00:00:00 +1100         
24082  status_update  2017-03-23 16:25:17 +1100  waiting_response  2017-03-23 16:25:17 +1100  waiting_response   
24136  followup_sent  2017-03-24 17:55:29 +1100        outgoing  
24170  response  2017-03-27 08:07:18 +1100        incoming  
24196  response  2017-03-27 17:23:26 +1100        incoming  
24197  response  2017-03-27 17:25:58 +1100        incoming  
24198  response  2017-03-27 17:26:44 +1100    2017-03-28 10:20:59 +1100  partially_successful  incoming  
24207  status_update  2017-03-28 10:20:59 +1100  partially_successful  2017-03-28 10:20:59 +1100  partially_successful   
24331  followup_sent  2017-03-29 19:58:00 +1100  internal_review  2017-03-29 19:58:00 +1100  internal_review  outgoing  
24348  response  2017-03-30 08:56:51 +1100    2017-04-03 17:54:58 +1000  not_held  incoming  
24430  comment  2017-03-31 17:30:03 +1100         
24530  status_update  2017-04-03 17:54:58 +1000  not_held  2017-04-03 17:54:58 +1000  not_held   

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 Right to Know 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.