It is expected that there should be a capability to report against expected national metrics for booking and a clear mechanism to share these data with commissioners and other key stakeholders.
The below tables identify the key metrics required to meet the national commissioning reporting requirements as well the most common local operational reporting and performance metrics. This specification is still in draft and is developing and evolving.
Requirement ID | Requirement | Which will produce the following data.... |
---|---|---|
rep-cons-01 | Number of appointments successfully booked vs number of successful referrals. Grouped by each service selected or patients registered practice, over a date range | In December there were 2000 appointments booked in total, 50 for practice A, 32 for practice B etc.. |
rep-cons-02 | Number of appointments not booked where there were no slots presented to the user and a successful referrals was made over a date range. Grouped by each service selected or patients registered practice | In December there were 200 appointments not been able to be made as the appointment slots were not available, but a referral to the service was made. |
rep-cons-03 | Number of appointments not booked where there were slots presented to the user and a successful referral was made over a date range. Grouped by each service selected or patients registered practice | In December there were 100 appointments not been able to be made but some appointment slots were available, but a referral to the service was made |
rep-cons-04 | Number of appointments where an attempt to book into an offered slot failed because it was no longer available when the booking was made. Grouped by each service selected or patients registered practice | In December there were 25 appointments not been able to be made successfully after the initial pre-allocation stage |
rep-cons-05 | Number of times a user rejected the top DOS entry where the top DOS entry would allow the user to book an appointment over a date range | In December there were 52 times where the user did not select the top service and the top service had an option to book appointment |
rep-cons-06 | Number of times that a user tried to book an appointment and got an error message over a date range. Grouped by error message | In December there were 2 times where the appointment booking button was clicked and an error occurred |
rep-cons-07 | Number of times that a user books an appointment and then cancels it before the end of the encounter. the appointment over a date range. Grouped by each service selected or patients registered practice. | In December there were 7 times a user booked an appointment and then cancelled it. |
rep-cons-08 | Number of times that a user books an appointment and the subsequently re-books the appointment over a date range. Grouped by each service selected or patients registered practice | In December there were 8 times a user booked an appointment and then re-books it. |
rep-cons-09 | Number of times that a user books an appointment and the subsequently cancelled the appointment over a date range. Grouped by each service selected or patients registered practice | In December there were 8 times a user booked an appointment and then cancels it when the patient calls back |
rep-cons-10 | Number of appointments successfully booked and number of appointment slots available that would not cause a breach over a date range | In December there were 200 “DX05” appointments booked and there were 400 appointment slots available that would not cause a breach. |
rep-cons-11 | Number of appointments successfully booked and number of appointment slots available that would cause a breach over a date range | In December there were 200 “DX05” appointments booked and there were 800 appointment slots available that would cause a breach. |
rep-cons-12 | Number of appointments not booked where there were slots presented to the user, but the slots would have caused a breach and a successful referrals was made over a date range | In December there were 30 appointments not been able to made but the appointment slots that were available were outside of the disposition time frame |
Requirement ID | Requirement | Which will produce the following data.... |
---|---|---|
rep-prov-01 | Number of appointments successfully booked in over a date range | In December there were 20 appointments booked |
rep-prov-02 | Number of appointments successfully booked vs number of successful referrals over a date range | In December there were 20 appointments booked and 25 referrals, showing that we have a 80% booking utilisation rate |
rep-prov-03 | Number of appointments successfully booked and number of appointment slots made available over a date range | In December there were 20 appointments booked and there were 30 appointment slots available |
rep-prov-04 | Number of appointments not booked vs number of successful referrals over a date range | In December there were 20 appointments booked and 50 referrals, showing that we have a 20% non-booking utilisation rate for this service |
rep-prov-05 | Number of times that appointments were subsequently cancelled over a date range | In December there were 7 times an appointment was cancelled |
Future Requirements
The items in the following table are expected to become requirements in the near future:
Requirement ID | Requirement | Which will produce the following data.... |
---|---|---|
None | There are currently no future requirements published. |
Sharing Mechanism
We are expecting that existing arrangements for sharing metrics are utilised. There may be a possibility that an API standard for data sharing will be published in the future.