Pre-send Checker: Difference between revisions

(13 intermediate revisions by the same user not shown)

Line 1:

~~When complete/final checked patients are being [[Sending patients |sent]] some data is also sent for patients who are not yet complete, for example:~~

The '''"Pre-send Checker"''' button on the main screen of [[CCMDB.accdb]] applies the same checks that will happen automaticlaly before sending.

* [[Minimal Data Set]]

* certain [[:Category: Special Short Term Projects]]

* certain [[:Category: All Projects]] data

Since these patients are not [[Final Check]]ed this can not be used as a trigger to ensure all is correct before sending. For that reason, this data is checked when either the '''Send Records''' or the '''Pre-send ~~TmpV2~~ Checker''' button ~~is pressed~~.

== 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~~]].''

''This data may be out-of date, for the actual checks see the Tmp_checker module in [[CCMDB.accdb]].''

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]] (see below)

# are there any patients with [[Eliminating a diagnosis from collection|diagnoses we are eliminating]]?

~~First, a number of tests get run successively on every record in the table L_TmpV2:~~

=== checks against current tmp projects ===

~~# a patient must exist for every entry in L_TmpV2~~

{{#ask: [[DICApp::CCMDB.accdb]] [[Category:Tmp check]] [[DICStatus::implemented]]

~~# the patient must have a '''location'''~~

|format=UL

~~#*some~~ tmp ~~studies only apply in some location, and those checks will fail if this were not entered~~

}}

# ~~there must be an item for every entry in L_TmpV2~~

~~# various checks for the~~ [[~~Transfusion Audit~~]]

~~# various checks for the~~ [[~~SmartPump Audit~~]]

~~# various checks for the~~ [[~~EuroScore~~]]

~~# various checks for [[Moves for Medicine]]~~

~~Then, a number of tests are run on the entire L_TmpV2 table:~~

~~# do all patients that ought to have a move, have one?~~

~~# are there several moves with identical times?~~

~~# are there two consecutive transfusions in < 5min?~~

~~Then there is one check that is run at this time even though it's not really related to tmp:~~

== Related articles ==

* Are there any patients that don't have the [[Minimal Data Set]]?

[[Category: CCMDB.~~mdb~~]]

[[Category:CCMDB.accdb]]

[[Category: Main Form]]

[[Category:Main Form]]

@@ Line 1: / Line 1: @@
-When complete/final checked patients are being [[Sending patients |sent]] some data is also sent for patients who are not yet complete, for example:
+The '''"Pre-send Checker"''' button on the main screen of [[CCMDB.accdb]] applies the same checks that will happen automaticlaly before sending.
-* [[Minimal Data Set]]
-* certain [[:Category: Special Short Term Projects]]
-* certain [[:Category: All Projects]] data
-Since these patients are not [[Final Check]]ed this can not be used as a trigger to ensure all is correct before sending. For that reason, this data is checked when either the '''Send Records''' or the '''Pre-send TmpV2 Checker''' button is pressed.
+== 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]].''
+''This data may be out-of date, for the actual checks see the Tmp_checker module in [[CCMDB.accdb]].''
 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]] (see below)
+# are there any patients with [[Eliminating a diagnosis from collection|diagnoses we are eliminating]]?
-First, a number of tests get run successively on every record in the table L_TmpV2:
+=== checks against current tmp projects ===
-# a patient must exist for every entry in L_TmpV2
+{{#ask: [[DICApp::CCMDB.accdb]] [[Category:Tmp check]] [[DICStatus::implemented]]
-# the patient must have a '''location'''
+|format=UL
-#*some tmp studies only apply in some location, and those checks will fail if this were not entered
+}}
-# there must be an item for every entry in L_TmpV2
-# various checks for the [[Transfusion Audit]]
-# various checks for the [[SmartPump Audit]]
-# various checks for the [[EuroScore]]
-# various checks for [[Moves for Medicine]]
-Then, a number of tests are run on the entire L_TmpV2 table:
-# do all patients that ought to have a move, have one?
-# are there several moves with identical times?
-# are there two consecutive transfusions in < 5min?
-Then there is one check that is run at this time even though it's not really related to tmp:
+== Related articles ==
-* Are there any patients that don't have the [[Minimal Data Set]]?
+{{Related Articles}}
-[[Category: CCMDB.mdb]]
+[[Category:CCMDB.accdb]]
-[[Category: Main Form]]
+[[Category:Main Form]]