Details of request “The use of catheter-directed thrombolysis to treat arterial occlusions

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 created_at described_state last_described_at calculated_state link
4313594  sent  2019-03-29 16:35:23 +0000  waiting_response  2019-03-29 16:35:23 +0000  waiting_response  outgoing  
4319867  response  2019-04-01 09:32:51 +0100    2019-04-01 09:33:47 +0100  waiting_response  incoming  
4319872  status_update  2019-04-01 09:33:47 +0100  waiting_response  2019-04-01 09:33:47 +0100  waiting_response   
4481989  overdue  2019-05-01 00:00:00 +0100         
4499096  followup_sent  2019-05-03 09:23:31 +0100        outgoing  
4499098  status_update  2019-05-03 09:23:57 +0100  waiting_response  2019-05-03 09:23:57 +0100  waiting_response   
4499101  status_update  2019-05-03 09:24:48 +0100  waiting_response  2019-05-03 09:24:48 +0100  waiting_response   
4642213  very_overdue  2019-05-31 00:00:00 +0100         
4653582  followup_sent  2019-06-02 12:02:04 +0100  internal_review  2019-06-02 12:02:04 +0100  internal_review  outgoing  
4653585  status_update  2019-06-02 12:03:49 +0100  internal_review  2019-06-02 12:03:49 +0100  internal_review   
4816789  followup_sent  2019-07-02 09:54:14 +0100        outgoing  
4816924  response  2019-07-02 10:34:15 +0100    2019-07-02 10:54:55 +0100  waiting_response  incoming  
4816979  status_update  2019-07-02 10:54:54 +0100  waiting_response  2019-07-02 10:54:55 +0100  waiting_response   
4960571  followup_sent  2019-07-26 07:14:23 +0100        outgoing  
5021619  followup_sent  2019-08-05 10:09:13 +0100        outgoing  
5094652  response  2019-08-15 12:58:04 +0100    2019-08-15 13:31:13 +0100  successful  incoming  
5094694  followup_sent  2019-08-15 13:31:03 +0100        outgoing  
5094695  status_update  2019-08-15 13:31:13 +0100  successful  2019-08-15 13:31:13 +0100  successful   
5706621  edit  2019-11-16 03:45:22 +0000         
5706622  edit  2019-11-16 03:45:22 +0000         
5706623  edit  2019-11-16 03:45:22 +0000         
5706624  edit  2019-11-16 03:45:22 +0000         
5706625  edit  2019-11-16 03:45:22 +0000         
5706626  edit  2019-11-16 03:45:22 +0000         
5706627  edit  2019-11-16 03:45:22 +0000         
5706628  edit  2019-11-16 03:45:22 +0000         
5706629  edit  2019-11-16 03:45:22 +0000         
5706630  edit  2019-11-16 03:45:22 +0000         
5706631  edit  2019-11-16 03:45:22 +0000         
5706632  edit  2019-11-16 03:45:22 +0000         
5706633  edit  2019-11-16 03:45:22 +0000         
5706634  edit  2019-11-16 03:45:22 +0000         
5706635  edit  2019-11-16 03:45:22 +0000         
5706636  edit  2019-11-16 03:45:22 +0000         
5706637  edit  2019-11-16 03:45:22 +0000         
5706638  edit  2019-11-16 03:45:22 +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.