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

Phenotype features get saved when "This patient is clinically normal" checkbox is clicked

Description

Currently, after having selected phenotype features, clicking on the "This patient is clinically normal" (clinical status) checkbox persists saving the phenotype features when it should not do so. Example output from REST:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 {{ "clinicalStatus": { "clinicalStatus": "unaffected" }, "features": [ { "id": "HP:0010862", "observed": "yes", "label": "Delayed fine motor development", "type": "phenotype" }, { "id": "HP:0000750", "observed": "yes", "label": "Delayed speech and language development", "type": "phenotype" }, { "id": "HP:0001263", "observed": "yes", "label": "Global developmental delay", "type": "phenotype" } ]}}

This is conceptually incorrect as an "unaffected" clinical status should not result in any observed phenotype features. In this case, while clicking on the checkbox can easily result in lost data caused by the user, a confirmation button for the checkbox can resolve this issue. If confirmed, then the patient is "unaffected" and all features selected will not be saved. If confirmation is cancelled, then the patient is "affected" and features get saved. This behaviour will be consistent with an identical feature in a Gene42 neurology extension.

Environment

None

Status

Assignee

Unassigned

Reporter

Teyden Nguyen

Labels

None

External issue ID

None

External issue ID

None

Components

Priority

Medium