Skip to content
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

Consolidate question in Medical history (physical conditions) [4h] #1338

Open
adamhstewart opened this issue Sep 23, 2024 · 3 comments
Open
Assignees

Comments

@adamhstewart
Copy link
Member

The questions below should be made into a single multi select field:

  • Uterine Myoma:
  • Bowed Legs:
E-Heza_System

As such (in two columns with "None of the Above" below a horizontal rule):
Does she have any of the following physical conditions:

  • Uterine Myoma-current
  • Uterine Myoma- surgical resection
  • Bowed legs
  • None

Tasks

  • Remove the existing fields
  • Add the new question
  • Create an update script that moves old data into new format (map Uterine Myoma -> Uterine Myoma (current) )
@adamhstewart adamhstewart added this to the TIP - Maintenance milestone Sep 23, 2024
@adamhstewart adamhstewart changed the title Consolidate question in Medical history [4h] Consolidate question in Medical history (physical conditions) [4h] Sep 23, 2024
@anvmn
Copy link
Collaborator

anvmn commented Sep 29, 2024

@adamhstewart

Per requirements, Uterine Myoma is split into 2 options.
What should be the logic for migration?

@adamhstewart
Copy link
Member Author

Create an update script that moves old data into new format (map Uterine Myoma -> Uterine Myoma (current) )

Map legacy data to Uterine Myoma-current

@adamhstewart adamhstewart moved this from Ready for Review to QA Testing in E-Heza Development Oct 2, 2024
@anvmn
Copy link
Collaborator

anvmn commented Oct 10, 2024

Create an update script that moves old data into new format (map Uterine Myoma -> Uterine Myoma (current) )

Map legacy data to Uterine Myoma-current

Decision here was updated - instead of mapping, keep legacy value.

@adamhstewart adamhstewart moved this from QA Testing to Ready for Release in E-Heza Development Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready for Release
Development

No branches or pull requests

2 participants