Data collection log form: Difference between revisions

Line 11:

*Pagasa, can you put in point form, what you use these forms for? [[User:TOstryzniuk|TOstryzniuk]] 19:17, 17 May 2010 (CDT)

**to check for patients which ~~was~~ missed on the PDA.

**to check on dates discrepancies ~~also another way of checking~~ if ~~there~~ is a ~~problem in~~ on there ~~computer.~~

**to check for patients which were missed on the PDA. Not used very often. Only when statistician is linking data between wards or ICU/Med, is when this type of problem is identified.

**can cross check the actual number of patient

***example: When minimal data is not being entered by some of the staff directly into PDA/laptop, I asked the staff to fax a copy of PDA Collection Log Form. Staff will complete this form first before they input patient information into PDA.

**to check on dates discrepancies. Statistician usually catch them and advises Processor, who first check PDA Collection Log Form, and if not clear on this paper for (not all collectors fill in all the information on this logs so they are not always helpful), then she will email collector to follow up.

**Database Registry Log is printed out from Database. This log provide processor with a list of patients already appended to the databse. List has names & admit/discharge dates, site/loc and STUDY NUMBERS. This list is used to put study number on TISS form and check dates before scanning. If the Dates on the TISS don't match the dates on the Database Registry printout Log, then the processor uses the PDA Collection Log Form to crosscheck dates. Data entry error are common for dates.

**If the Regional Server is down, or there is no backup copy of the files that are accessible (some do not do regular backukps to server), there is no other way to check basic information

**can cross check the actual number of patient. This is not done very often at all.

===Plans===

@@ Line 11: / Line 11: @@
 {{Discussion}}
 *Pagasa, can you put in point form, what you use these forms for? [[User:TOstryzniuk|TOstryzniuk]] 19:17, 17 May 2010 (CDT)
-**to check for patients which was missed on the PDA.
-**to check on dates discrepancies also another way of checking if there is a problem in on there computer.
+**to check for patients which were missed on the PDA.   Not used very often. Only when statistician is linking data between wards or ICU/Med, is when this type of problem is identified.
-**can cross check the actual number of patient
+***example: When minimal data is not being entered by some of the staff directly into PDA/laptop, I asked the staff to fax a copy of PDA Collection Log Form.  Staff will complete this form first before they input patient information into PDA.
+**to check on dates discrepancies.  Statistician usually catch them and advises Processor, who first check PDA Collection Log Form, and if not clear on this paper for (not all collectors fill in all the information on this logs so they are not always helpful), then she will email collector to follow up.
+**Database Registry Log is printed out from Database. This log provide processor with a list of patients already appended to the databse.  List has names & admit/discharge dates, site/loc and STUDY NUMBERS.  This list is used to put study number on TISS form and check dates before scanning.  If the Dates on the TISS don't match the dates on the Database Registry printout Log, then the processor uses the PDA Collection Log Form to crosscheck dates.  Data entry error are common for dates.
+**If the Regional Server is down, or there is no backup copy of the files that are accessible (some do not do regular backukps to server),  there is no other way to check basic information
+**can cross check the actual number of patient. This is not done very often at all.
 ===Plans===