Can a param filter please be added to the Rota Practitioner Diary that filters out rows in which a practitioner is no available? It makes sense that in endpoint we the only are looking at dates in which our practitioners are available, and we can make the assumption the practitoner is not available a certain as there is no data for it.
+9- Community Manager
Hi
I’ll pass this onto the product team for review - if you have any further points or context to add around why this would be useful, or if any other practices have further insight, please feel free to drop additional comments below 😊
+2- Enthusiast
Hello,
For context:
| Row | Practititoner_id | Day | End_time | Start_time | Unavailable | ID | Breaks |
|---|---|---|---|---|---|---|---|
| 1 | 123456 | 01/01/2026 | null | null | TRUE | abcd | [] |
| 2 | 123456 | 02/01/2026 | 17:00 | 8:00 | FALSE | abce | [] |
| 3 | 123456 | 03/01/2026 | null | null | TRUE | abcf | [] |
This is how the End point for the Rota_Practitioner_diary looks, for a data perspective only row 2 contains relavent information for us as a company. row 1 and 3 are just “fluff”.
It would make since to either have a filter in your back-end that automatically removes rows where the ‘unavailable’ is TRUE, or add a parameter to the API where we can filter the ‘unavailable’ column ourselves (or potentially both options applied, like how inactive practitioners are handled)
The reason for asking is the Rota_practitioner_diary is already quite a hefty API call, its consumes most of our ETL time. Reducing the number of rows in the call will reduce the load for us.
+15- Community Manager
Hey
Thanks for the additional details. I can see your point and I agree it’s not optimised right now. I’ll pass this to our product manager working on all the API enhancement. Thanks again for sharing your feedback!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.