Details of request “Podaci o Sveučilišnoj bolnici Zagreb

Event history

This table shows the technical details of the internal events that happened to this request on Imamo pravo znati. 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 Imamo pravo znati. 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
31831  sent  2018-12-16 10:06:29 +0100  waiting_response  2018-12-16 10:06:29 +0100  waiting_response  outgoing  
31838  comment  2018-12-17 23:56:51 +0100         
31839  followup_sent  2018-12-17 23:57:36 +0100        outgoing  
31850  response  2018-12-18 10:52:42 +0100    2018-12-18 10:53:03 +0100  waiting_response  incoming  
31852  status_update  2018-12-18 10:53:03 +0100  waiting_response  2018-12-18 10:53:03 +0100  waiting_response   
31899  response  2018-12-25 17:50:41 +0100    2018-12-25 17:52:05 +0100  waiting_response  incoming  
31902  status_update  2018-12-25 17:52:05 +0100  waiting_response  2018-12-25 17:52:05 +0100  waiting_response   
32029  response  2019-02-01 12:39:46 +0100    2019-04-01 20:25:45 +0200  partially_successful  incoming  
32798  status_update  2019-03-10 11:00:57 +0100  not_held  2019-03-10 11:00:57 +0100  not_held   
32969  comment  2019-04-01 20:25:32 +0200         
32970  status_update  2019-04-01 20:25:45 +0200  partially_successful  2019-04-01 20:25:45 +0200  partially_successful   
35548  edit  2019-11-06 04:45:40 +0100         
35549  edit  2019-11-06 04:45:40 +0100         
35550  edit  2019-11-06 04:45:40 +0100         
35551  edit  2019-11-06 04:45:40 +0100         
35552  edit  2019-11-06 04:45:40 +0100         
35553  edit  2019-11-06 04:45:40 +0100         
35554  edit  2019-11-06 04:45:40 +0100         
35555  edit  2019-11-06 04:45:40 +0100         
35556  edit  2019-11-06 04:45:40 +0100         
35557  edit  2019-11-06 04:45:40 +0100         
35558  edit  2019-11-06 04:45:40 +0100         
66519  edit  2022-04-02 05:45:09 +0200         
66520  edit  2022-04-02 05:45:09 +0200         
66521  edit  2022-04-02 05:45:09 +0200         
66522  edit  2022-04-02 05:45:09 +0200         
66523  edit  2022-04-02 05:45:09 +0200         
66524  edit  2022-04-02 05:45:09 +0200         
66525  edit  2022-04-02 05:45:09 +0200         
66526  edit  2022-04-02 05:45:09 +0200         
66527  edit  2022-04-02 05:45:09 +0200         
66528  edit  2022-04-02 05:45:09 +0200         
66529  edit  2022-04-02 05:45:09 +0200         
66530  edit  2022-04-02 05:45:10 +0200         
66531  edit  2022-04-02 05:45:10 +0200         
66532  edit  2022-04-02 05:45:10 +0200         
66533  edit  2022-04-02 05:45:10 +0200         
66534  edit  2022-04-02 05:45:10 +0200         
66535  edit  2022-04-02 05:45:10 +0200         
66536  edit  2022-04-02 05:45:10 +0200         
66537  edit  2022-04-02 05:45:10 +0200         
66538  edit  2022-04-02 05:45:10 +0200         
66539  edit  2022-04-02 05:45:10 +0200         
66540  edit  2022-04-02 05:45:10 +0200         

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 Imamo pravo znati 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.