Merged
Conversation
Linking the CVD Risks to Patients on a logical level forces each CVD Risk to have a corresponding patient; but at the time this is being synced from the mobile, we only have a patient_id for the CVD Risk record; no patient yet created with that ID. This would be created later. This is an effect of allowing relational entities sync without their relations.
aagrawalrtsl
approved these changes
Feb 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Story card: SIMPLEBACK-52
Because
Syncing patients with cvd risks fails
This addresses
Loosening up the link between CVD Risks and Patients
Test instructions
n/a