Skip to content

Change patient parent association - consent flow#6760

Draft
stevehook wants to merge 4 commits intochange-patient-parent-association-switch-modelfrom
change-patient-parent-association-consent-flow
Draft

Change patient parent association - consent flow#6760
stevehook wants to merge 4 commits intochange-patient-parent-association-switch-modelfrom
change-patient-parent-association-consent-flow

Conversation

@stevehook
Copy link
Copy Markdown
Contributor

This PR is a follow up to #6747 and adapts the consent flow to persist parent details to the new model (new attributes of ParentRelationship) as well as the old model (Parent).

The writes to the new model are not covered by the one_patient_per_parent feature flag because they will not be surfaced by anything in this PR.

...

Jira Issue - MAV-6057

Screenshots

...

Duplicates `verbal_consent_given_spec.rb` feature spec into a variant
with and without the `one_patient_per_parent` feature flag. The
`verbal_consent_given_without_parent_association_feature_flag_spec`
variant can be deleted when we drop the feature flag.

Jira-Issue: MAV-6057
`Parent#phone_receive_updates` can end up with a `nil` value which
is invalid as it's a mandatory boolean attribute.
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.

1 participant