Open ChristopherRiedel opened 3 years ago
@ChristopherRiedel Do you know how existing and differing entries should be updated? This can have a lot of implications especially regarding other calculations that are based on this date. Do we just adopt the earliest date?
@kwa20
@kwa20 German health departments state that they would prefer to use always the last selected onset date.
@ChristopherRiedel ,
@bernardsilenou since we are talking about visits, you can select a new symptom onset date in every visit symptoms
@ChristopherRiedel is there a specific reason why they would like to use the latest? For me, it is not very logical to overwrite an onset date with a visit onset date that is later because it contradicts the meaning of the field. To be fair, the interpretation of the onset field in visits is debatable and probably not explicitly clear because we merely copy the symptoms page for visits. However, in the context of the onset date on the case symptoms tab, the meaning is clear, i.e. the date where the case person showed the first symptom or symptoms. Since changing this influences the follow-up calculation, we should be careful with constant changes which incoming visits.
As discussed with users, the date being updated on the symptoms tab in the case should be the earliest onset date of any of the existing visits.
To consider: If the symptom onset date is update and subsequently the follow-up period of the case adjusted, the user should get informed about this adjustment
Feature Description
The symptom onset date from visits should be transferred to the general symptoms of the case like the other fields.
Additional Information
This is a demand from some German health departments.