Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic calculation for clinical, epid and lab confirmation #4116

Open
6 tasks
MartinWahnschaffe opened this issue Jan 22, 2021 · 2 comments
Open
6 tasks
Labels
cases change A change of an existing feature (ticket type)

Comments

@MartinWahnschaffe
Copy link
Contributor

MartinWahnschaffe commented Jan 22, 2021

Feature & Problem Description

The current fields in sormas can be edited by the user. It's not possible to map this with the SUrvNet fields that distinguish between computed and manual fields (for CVD manual is only relevant for epid, so we ignore the other two manual fields).

Proposed Change

  • Add automatic calculation for clinical confirmation
  • Add automatic calculation for epidemiological confirmation
  • Add automatic calculation for laboratory confirmation
  • Make the existing fields read-only in the UI
  • Add new field epidemiologicalConfirmationManual that allows to manually override the epi data
  • Migration: set the value of epidemiologicalConfirmationManual to the existing epidemiologicalConfirmation

For now the automatic calculation is done whenever the case is saved. Later it could be done directly in the form whenever a related value is changed.

@JonasCir Please add the calculation rules.

@MartinWahnschaffe MartinWahnschaffe added change A change of an existing feature (ticket type) cases labels Jan 22, 2021
@MartinWahnschaffe MartinWahnschaffe added the needs-refinement Refinement or further specification required label Jan 22, 2021
@MartinWahnschaffe MartinWahnschaffe added this to the Sprint 99 - 1.55.0 milestone Jan 22, 2021
@JonasCir
Copy link
Contributor

Here are the rules (in German) https://www.rki.de/DE/Content/InfAZ/N/Neuartiges_Coronavirus/Falldefinition.pdf?__blob=publicationFile

I would like to defer the translation to point where it is clear that the person who is going to implement this is not speaking German if this is ok.

@bernardsilenou
Copy link

This issues is planned but the specification is not clear, the variables involved and rules in both directions.

One point that we can keep in mind is how the system should act when automatic computation was overridden and latter comes in new data (lab results) data that lead to a different case classification.
How should auto computation and user specification work in both directions? If user override the system and more data is added, should system go back to auto mode using the updated data or stay on user classification?
A similar situation exist with contact type and contact category

  • It would be good to have a read only variable: "classifier" : automatic or user name
  • Suggested solution:
    * If any variable used in computing the classifications is updated after the date the users last classification, then show a pront like "Addition information added to the case after the last classification warrant another classification. Do you want system to auto classify?"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cases change A change of an existing feature (ticket type)
Projects
None yet
Development

No branches or pull requests

5 participants