Open lwlshawn opened 3 years ago
We did not do this because we think that it does not make sense for us to arbitrarily define the duration between the last visit and the next visit. For example, an elderly could have 2 consecutive visits for 2 different purposes, and the user may want to document that using a similar schema as you provided in the screenshot. Hence, we do not think this warrants a bug. Thanks for the suggestion
Team chose [response.Rejected
]
Reason for disagreement: Not wanting to arbitrarily define the duration between the last visit and the next visit is partially reasonable, but if the next visit and last visit have the EXACT same date and time, this would imply that a visit lasted a duration of 0 minutes. Given that this is extremely unrealistic, and thus more likely to have been a error by the user, I still believe that at the very least a warning when this happens should be given.
The application at present appears to allow the exact same datetime for Nextvisit and Lastvisit. Perhaps this should be disallowed, given that this is most likely a user error if it comes up in practice?