Consanguinity should only be changed if it is not previously set, but detected in the pedigree

Description

Steps to reproduce the problem:

  • create patient and click "Y" on consanguinity; save

  • create pedigree; use any non-consanguineous template; save

  • close pedigree

  • PROBLEM: consanguinity was overwritten to "N". Patient may know that there was consanguinity in the family, without knowing details as whose relationship in the family tree was consanguineous.

Environment

None

Activity

Show:
Sasha Andjic
June 15, 2018, 4:33 AM

I believe this regression was introduced with PT-3455.

Andrew Misyura
July 10, 2018, 6:35 AM
Edited

aditionally we probably should mark patient's parent relationship (if it exists) to be consanguineous if patient is marked as such on the patient form

Sasha Andjic
July 10, 2018, 12:21 PM

Good point. I'll bring this on dev meeting for discussion.

Andrew Misyura
July 10, 2018, 1:09 PM

There is not much to discuss, just needs to be done, lets not waste everyone time at a dev.meeting. At most we neede to confirm with only

Andrew Misyura
July 19, 2018, 2:33 AM

New issue is created - PT-3777. There are a lot of special cases about marking relationship as consanguineous, in particular if we do that we should NOT do what this issue describes since that would potentially contradict user input. So all of those cases should be discussed and dealt with in PT-3777, while this issue implements the most basic fix as described in issue title

Fixed

Assignee

Andrew Misyura

Reporter

Sasha Andjic

Labels

External issue ID

None

Epic Link

Components

Fix versions

Affects versions

Priority

Medium