-
-
Notifications
You must be signed in to change notification settings - Fork 3
[BACK-4025] Expand patient count with additional details #173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
darinkrauss
commented
Sep 16, 2025
- Expand patient count with additional details
- Add refresh patient count for service
- Add missing delete OAuth authorization endpoint for service
- Add missing twiist data ingestion endpoint
- https://tidepool.atlassian.net/browse/BACK-4025
- Expand patient count with additional details - Add refresh patient count for service - Add missing delete OAuth authorization endpoint for service - Add missing twiist data ingestion endpoint - https://tidepool.atlassian.net/browse/BACK-4025
ewollesen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one question, not blocking per se, but should be addressed
lostlevels
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Non-blocking comments but nice to haves for future clarity.
| The count of patients that have a specific provider as a data source. | ||
| type: integer | ||
| minimum: 0 | ||
| states: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: since the possible states are known ahead of time, I'd prefer to have the keys explicitly listed out as optional fields rather than described in the description.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair enough. I am likely expanding the choice of states for a data source (which this is derived from) for the Oura work. Okay if I update this then?
reference/clinic.v1.yaml
Outdated
| description: Accepted | ||
| description: |- | ||
| An internal endpoint to refresh the patient count for this clinic. This request may or may not be processed asynchronously. | ||
| A successful response means the patient count will be refreshed shortly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For my curiosity, how does the client know when the count will be refreshed? Do they just poll the patients count endpoint? There's nothing in the patient count endpoint (to my eye) that indicates the last update time for the client to know if it was refreshed or not. Might be useful to add in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the comment and removed the asynchronous aspect. I also updated the response code from Accepted 202 to OK 200.
89a7a49