Pre-send Checker: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) |
||
| Line 16: | Line 16: | ||
=== checks against current tmp projects === | === checks against current tmp projects === | ||
{{#ask: [[DICApp::CCMDB.mdb]] [[Category: Tmp check]] | {{#ask: [[DICApp::CCMDB.mdb]] [[Category: Tmp check]] [[DICStatus::implemented]] | ||
|format=UL | |format=UL | ||
}} | }} | ||
Revision as of 21:52, 16 January 2019
The "Pre-send Checker" button on the main screen of CCMDB.mdb applies the same checks that will happen automaticlaly before sending.
Use
Use of the button is completely optional. It is intended so collectors can check if their data is complete before leaving the ward, so they don't need to go back to get additional information when they try to send, and sending rejects their data. The same checks get applied automatically before sending, so there is no need to click this button before sending.
What is actually checked
This data may be out-of date, for the actual checks see the Tmp_checker module in CCMDB.mdb.
The following things get checked, in this order:
- are there any patients that don't have the Minimal Data Set?
- Check duplicate patient
- are there any TMP entries not consistent with table s_tmp? (query s_tmp_project_item_consistent)
- any #checks against current tmp projects
- are there any patients with diagnoses we are eliminating?