Uploaded image for project: 'PhenoTips'
  1. PT-2816

Improve family studies back-end code (refactor on top of Entities part1)

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects versions: None
    • Fix versions: 1.3-milestone-3
    • Components: family-studies
    • Labels:
      None

      Description

      Right now the responsibilities of various classes in family-studies code are very inter-linked and not clearly separated. There are 4 classes

      Family
      FamilyRepository
      FamilyTools
      PedigreeUtils

      All of which manipulate on and modify parts of both family and its member patients. The code should be refactored so that, for example:

      • Family mostly deals with family document itself (Like PrimaryEntity)
      • FamilyReposiory does what EntityGroupManager does (adds/removes links to patients)
      • FamilyTools is a "secure" version of FamilyRepository, which assumes current user as the actor (similar to how SecurePatientRepository works)

      This can be considered the first step of rebasing family-studies on top of Entities API

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                asm Andrew Misyura
                Reporter:
                asm Andrew Misyura
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: