person cluster patient assignment endpoints #172
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #172 +/- ##
==========================================
+ Coverage 97.59% 97.65% +0.05%
==========================================
Files 31 32 +1
Lines 1541 1576 +35
==========================================
+ Hits 1504 1539 +35
Misses 37 37 ☔ View full report in Codecov by Sentry. |
bamader
left a comment
There was a problem hiding this comment.
The code changes themselves all look fine to me. I'm wondering what the rationale is for making the functions that previously operated on a single patient or person now perform bulk retrievals / updates. That seems to actually be a fairly dangerous process (see my example above about how that could corrupt linkage results and degrade future cluster quality) if we're performing this on any kind of updates to person clusters in between processing new in coming records. This seems like a case where I'm missing some context though, such as maybe this is only used for seeding.
Description
Two new person API endpoints for assigning patients to different person clusters.
Related Issues
closes #158
Additional Notes
<--------------------- REMOVE THE LINES BELOW BEFORE MERGING --------------------->
Checklist
Please review and complete the following checklist before submitting your pull request:
Checklist for Reviewers
Please review and complete the following checklist during the review process: