We're updating the issue view to help you get more done. 

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

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

Environment

None

Status

Assignee

Andrew Misyura

Reporter

Andrew Misyura

Labels

None

External issue ID

None

External issue ID

None

Epic Link

Components

Fix versions

Priority

Medium