Problems related to event timing of data consistency checks: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
These are related to when checks run and how the events for usage work. They need to be looked into but are tricky to troubleshoot, and change to these could affect other checks. Will need good testing. | These are related to when checks run and how the events for usage work. They need to be looked into but are tricky to troubleshoot, and change to these could affect other checks. Will need good testing. These would be addressed by [[Cross Check Engine]]. | ||
* with reg already checked, was able to change discharge date to a future date and it didn't uncheck initially; it did catch on trying to final-check, so this is a low-grade bug, just should be fixed eventually. Only way for a bad date to go through is if it were changed after final-check had already been set. Ttenbergen 20:37, 2012 November 1 (EDT) | * with reg already checked, was able to change discharge date to a future date and it didn't uncheck initially; it did catch on trying to final-check, so this is a low-grade bug, just should be fixed eventually. Only way for a bad date to go through is if it were changed after final-check had already been set. Ttenbergen 20:37, 2012 November 1 (EDT) | ||
* able to uncheck checkboxes without finalcheck unchecking. Need to determine if this could lead to bad data going through. [[User:Ttenbergen|Ttenbergen]] 14:45, 2012 May 22 (CDT) | * able to uncheck checkboxes without finalcheck unchecking. Need to determine if this could lead to bad data going through. [[User:Ttenbergen|Ttenbergen]] 14:45, 2012 May 22 (CDT) | ||
* if an error handler turns the dx tab yellow this is not automatically reset when a new patient is opened. Ttenbergen 13:15, 2012 October 31 (EDT) | * if an error handler turns the dx tab yellow this is not automatically reset when a new patient is opened. Ttenbergen 13:15, 2012 October 31 (EDT) | ||
Also, some checks cause requeries and refreshes, leading to [[CCMDB.accdb flickers or flashes]] | |||
See also [[Multiple LOS errors]] | See also [[Multiple LOS errors]] | ||
| Line 15: | Line 13: | ||
| todo_added = 2022-04-13 | | todo_added = 2022-04-13 | ||
| todo_action = 2022-04-13 | | todo_action = 2022-04-13 | ||
| question = | | question = _dev_ccmdb | ||
* Listed as ready to fix so needs to be on list. }} | * Listed as ready to fix so needs to be on list. See also [[Cross Check Engine]] }} | ||
== Related articles == | |||
{{Related Articles}} | |||
[[Category:Ready-to-fix bug]] | [[Category:Ready-to-fix bug]] | ||
Latest revision as of 14:30, 2022 November 29
These are related to when checks run and how the events for usage work. They need to be looked into but are tricky to troubleshoot, and change to these could affect other checks. Will need good testing. These would be addressed by Cross Check Engine.
- with reg already checked, was able to change discharge date to a future date and it didn't uncheck initially; it did catch on trying to final-check, so this is a low-grade bug, just should be fixed eventually. Only way for a bad date to go through is if it were changed after final-check had already been set. Ttenbergen 20:37, 2012 November 1 (EDT)
- able to uncheck checkboxes without finalcheck unchecking. Need to determine if this could lead to bad data going through. Ttenbergen 14:45, 2012 May 22 (CDT)
- if an error handler turns the dx tab yellow this is not automatically reset when a new patient is opened. Ttenbergen 13:15, 2012 October 31 (EDT)
Also, some checks cause requeries and refreshes, leading to CCMDB.accdb flickers or flashes
See also Multiple LOS errors
|
_dev_ccmdb
|
|
Related articles
| Related articles: |