Skip to content

Conversation

@darinkrauss
Copy link
Contributor

  • 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
Copy link
Contributor

@ewollesen ewollesen left a 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

ewollesen
ewollesen previously approved these changes Oct 13, 2025
ewollesen
ewollesen previously approved these changes Nov 5, 2025
lostlevels
lostlevels previously approved these changes Nov 9, 2025
Copy link
Contributor

@lostlevels lostlevels left a 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:
Copy link
Contributor

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.

Copy link
Contributor Author

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?

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.
Copy link
Contributor

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.

Copy link
Contributor Author

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.

@darinkrauss darinkrauss dismissed stale reviews from lostlevels and ewollesen via 89a7a49 November 10, 2025 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants