Timestamp in accumulated error list

[kbhCGI]

Is it possible to add a validation timestampe in the accumulated error list?
So we can tell the end user when the error was validated. #172

[TueCN]

From #172 (comment):

Does the validate timestamp change, if ex. there is a rule telling, that a code need to be registrated before 10 days and it is not reported to LPR3 i time? (actionsdiagnose not registreted)

No, the validation issue status is simply updated from warning to error. This means, the warning turns into an error - without being revalidated.

If the required code was registered less than 10 days after the warning, the warning would have disappeared and thereby never turning into an error.

Note: Many warnings give a time limit starting from the encounter end date, not starting from the time of validation!
This means that if an encounter is submitted today with an end date 9 days ago, the warning would turn into an error already tomorrow. This in turn means that the error will appear on the accumulated error list the day after tomorrow.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[kbhCGI]

I still think it will a good idea ;-)

[KirstenLHSDS]

This is transfered to the LPR backlog