Details of request “Medicine Optimisation contact information for GP practices in your CCG

Event history

This table shows the technical details of the internal events that happened to this request on WhatDoTheyKnow. 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 WhatDoTheyKnow. 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
2396400  set_embargo    2017-06-13 13:18:40 +0100         
2396401  sent    2017-06-13 13:18:40 +0100  waiting_response  waiting_response  2017-06-13 13:18:41 +0100  outgoing  
2397385  response    2017-06-14 09:58:24 +0100        incoming  
2447955  response    2017-07-11 10:48:35 +0100    successful  2017-09-13 12:01:10 +0100  incoming  
2526066  embargo_expiring    2017-09-05 00:00:00 +0100         
2528821  embargo_expiring    2017-09-05 00:00:00 +0100         
2530793  embargo_expiring    2017-09-05 00:00:00 +0100         
2532659  embargo_expiring    2017-09-05 00:00:00 +0100         
2534404  embargo_expiring    2017-09-05 00:00:00 +0100         
2535015  embargo_expiring    2017-09-05 00:00:00 +0100         
2535907  embargo_expiring    2017-09-05 00:00:00 +0100         
2538048  embargo_expiring    2017-09-05 00:00:00 +0100         
2539697  expire_embargo    2017-09-13 00:00:26 +0100         
2540470  status_update    2017-09-13 11:51:32 +0100  waiting_response  waiting_response  2017-09-13 11:51:32 +0100   
2540497  status_update  described_state  2017-09-13 12:01:09 +0100  successful  successful  2017-09-13 12:01:10 +0100   
2816078  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816079  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816080  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816081  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816082  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816083  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816084  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816085  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816086  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816087  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816088  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816089  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816090  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816091  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         
2816092  edit metadata  allow_new_responses_from  2018-03-14 03:46:18 +0000         

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 WhatDoTheyKnow 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.