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

Improve robustness of phenotype specificity scorer

    Details

      Description

      One of our users had an issue where their entire instance became virtually unusable because PT was timing out when communicating with the Monarch specificity scorer. Because the scorer is queried in a controller on every patient record save, it became almost impossible to use the instance.

      Can we please consider the following changes to make the scorer service more robust?

      • Prevent the score from being recalculated on every patient save. Only recalculate the specificity score in case it needs to be recalculated.
      • Set the timeout for querying the monarch service to be very small, something like 1 second.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                sdumitriu Sergiu Dumitriu
                Reporter:
                danielpgross Daniel Gross
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: