Uploaded image for project: 'Reference Application'
  1. Reference Application
  2. RA-534

Provide migration path when making the switch to using the allergy module

    Details

    • Type: Story
    • Status: Accepted
    • Priority: Must
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Complexity:
      Low
    • Sprint:
      Allergy Sprint 1

      Description

      The way allergies are captured in OpenMRS has been evolving over the past couple of versions.
      A new module was created and added to the reference application to handle patient allergies and stores them in a different DB table, the module code will be ported to OpenmRS core in a later version. Currently, when you upgrade to OpenMRS 2.0 or install the allergies module, any allergies created will be stored in different table therefore they will never show up on the old patient dashboard which is fine, however, it also implies that any previously recorded allergies captured using the ActiveListService in core will appear as though they lost in the new interface.
      We need to provide a migration path to copy any previously stored unvoided allergies from the old table to the new one when the allergy module is installed and void them in the new table.

      TODO:

      • Update the liquibase.xml in the module to copy over all unvoided allergies from the old table to the one in the module.

        Gliffy Diagrams

          Attachments

            Attachments-Category-Modification

              Activity

                People

                • Assignee:
                  wyclif Wyclif Luyima
                  Reporter:
                  wyclif Wyclif Luyima
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: