Details of request “Claim and payment breakdown by therapy type 2016/17

Event history

This table shows the technical details of the internal events that happened to this request on FYI. 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 FYI. 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 OIA 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
43348 sent 2017-08-07 14:11:46 +1200 waiting_response 2017-08-07 14:11:46 +1200 waiting_response outgoing
43920 followup_sent 2017-08-21 12:25:27 +1200 outgoing
43929 response 2017-08-21 13:53:33 +1200 2017-08-21 13:55:32 +1200 attention_requested incoming
43930 status_update 2017-08-21 13:54:39 +1200 attention_requested 2017-08-21 13:55:32 +1200 attention_requested
44434 response 2017-09-04 12:47:04 +1200 2017-09-04 14:42:14 +1200 partially_successful incoming
44440 status_update 2017-09-04 14:42:14 +1200 partially_successful 2017-09-04 14:42:14 +1200 partially_successful
44441 followup_sent 2017-09-04 14:42:26 +1200 outgoing
44442 comment 2017-09-04 14:48:38 +1200
44458 followup_sent 2017-09-05 08:48:10 +1200 outgoing
44470 response 2017-09-05 11:47:04 +1200 2017-09-05 11:48:10 +1200 partially_successful incoming
44471 status_update 2017-09-05 11:48:10 +1200 partially_successful 2017-09-05 11:48:10 +1200 partially_successful
44574 response 2017-09-08 15:37:05 +1200 2017-09-11 08:23:23 +1200 partially_successful incoming
44607 status_update 2017-09-11 08:23:23 +1200 partially_successful 2017-09-11 08:23:23 +1200 partially_successful
44623 followup_sent 2017-09-11 12:07:00 +1200 outgoing
45425 response 2017-10-06 14:57:04 +1300 2017-10-06 15:07:43 +1300 successful incoming
45427 status_update 2017-10-06 15:07:43 +1300 successful 2017-10-06 15:07:43 +1300 successful
46066 response 2017-10-25 12:27:11 +1300 2017-10-25 12:34:05 +1300 partially_successful incoming
46067 status_update 2017-10-25 12:34:05 +1300 partially_successful 2017-10-25 12:34:05 +1300 partially_successful
46068 followup_sent 2017-10-25 12:34:13 +1300 outgoing
46293 response 2017-11-01 16:37:05 +1300 2017-11-01 16:41:22 +1300 successful incoming
46294 status_update 2017-11-01 16:41:22 +1300 successful 2017-11-01 16:41:22 +1300 successful
46295 followup_sent 2017-11-01 16:42:29 +1300 outgoing
46296 comment 2017-11-01 16:42:41 +1300
46374 followup_sent 2017-11-03 11:53:26 +1300 outgoing
46460 response 2017-11-06 16:17:10 +1300 2017-11-06 16:19:21 +1300 partially_successful incoming
46461 status_update 2017-11-06 16:19:21 +1300 partially_successful 2017-11-06 16:19:21 +1300 partially_successful
46934 response 2017-11-23 18:47:05 +1300 2017-11-24 08:17:30 +1300 successful incoming
46944 status_update 2017-11-24 08:17:30 +1300 successful 2017-11-24 08:17:30 +1300 successful

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