CCMDB Data cleaner.mdb general information

The data cleaning tool is used by the Data Processor to flag and fix internal inconsistencies in data already submitted by data collectors.

File:Change pot.svg

It is an Access program which is also known as the CCMDB Cleaner.mdb program.

The goal is to pull as many of these checks ahead to be done in CCMDB.mdb, but some checks (e.g. those that required TISS data to be available) need to be included in this in office data cleaner.mdb program.

Importing into the CCMDB_Cleaner.mdb

• what steps are actually taken? Right now Pagasa sent me an error that, I think, might be related to date format conventions, or else to required steps during import. Is this documented? Ttenbergen
  • I think you need to click "edit import file locations" button and change the names to reflect the date part of the export from Ed. Ttenbergen 16:54, 2012 September 11 (CDT)

Progress

The Data Cleaning process is a work in progress.

• some checks Julie usually runs have not yet been implemented
• some checks need to be added to the CCMDB.mdb instead of cleaner (do it sooner)

Discussion

• Trish/Pagasa, which check would you like to work on next? Ttenbergen 12:28, 8 December 2009 (CST) Ttenbergen 10:19, 2012 September 11 (CDT)
  • will look.--TOstryzniuk 17:35, 8 December 2009 (CST)
• I will work with Pagasa to explore ways to streamline the process she is using when processing files in the cleaner program.--Fschumacher (talk) 14:01, 2012 September 17 (CDT)

File Location

File name is CCMDB Cleaner.mdb

A master copy of the file is on X:\Data_cleaning\CCMDB Cleaner.mdb

For use, Pagasa copies the file to her C:\ drive. The file can grow to >1GB in size during use so working with it on the network would be too slow.

The CCMDB_Cleaner.mdb pulls and pushes data from various file locations. The addresses are stored in the table x_defaults.

L_Aux

The table L_Aux contains some calculated values that are exported by TMSX. They are:

• Apache -
  • Not sure where you are getting your data from for this. The registry screen maybe? Ed scores APACHE in the APACHE II file for each patient and also records the total Apache score into the Registry file for each patient.
    • The first (APACHE) arrives with the registry file, the second with the apa file. Are the two identical? Ttenbergen 10:34, 9 December 2009 (CST)
      • yes they are suppose to be.--TOstryzniuk 12:13, 9 December 2009 (CST)

• Inits - Patient initials generated from patient name. Used for error listings to keep info more private.

• Age - Admit date M_D_Y minus DOB M-D-Y = Date of Birth

• LOS -length of stay. discharge D_M_Y_time minus admit D_M_Y_time

• Enc - Encounter - currently not used. A sorting utility program that use to tally the number of encounter to the database. Sorting was done using, FN, LN, DOB and PHIN? We had suspending using it when we found many data errors in DOB or name spelling, PHIN. Since we have worked on fixing this problem we have not continue to use it.
  • see: Identification Numbers

• Index - not calculated. This was a old file system number we used. See: Identification Numbers

• Serial - serial numbers are collection site organization number used during collection. These are not calculated. No sure what you mean? See: Identification Numbers

• HMORT-Hospital Mortality-this is not calculation just "S"urvive or "E"xpired if we know it. Dan wanted us to track hospital outcome but we were not able to get this data easily.

• apspts-APACHE Acute Physiological points see APACHE Scoring table. (For added detail Ed's program showed APS score using APACHE Scoring table items 1-11 and GCS score separately. APS = APS + GSW (which includes all physiological variables including GCS).

• agepts -Age Points-as per Age Points

• chempts - Chronic Health Points as per Chronic Health Points (0 , 2 or 5)

• totApache total Apache Score -(how is this different from "Apache" above?)- see story under Apache above.
  • TotApache = APS + GCS + chempts + agepts

History/change log

2012-09-11

• changed regional server in x_defaultsTtenbergen 12:37, 2012 September 11 (CDT)
• deleted tables lab*_ImportErrors* (not worried since Lab collection has changed since this was implemented and would no longer work anyways)Ttenbergen 12:37, 2012 September 11 (CDT)
• cleaning out checks that are no longer required, e.g. green sheets, old labs, old pharm; we should update this with new requirements Ttenbergen 12:37, 2012 September 11 (CDT)
• stopped Medicine iTISS importTtenbergen 12:37, 2012 September 11 (CDT)

pre 2012-09-22

• Original SAS data checking/cleaning queries developed by Julie in SAS who obtained input from Trish, data collectors or others where she needed.
• Tina was developing these checks in Access so that others who are not familiar with SAS programming can run or add additional queries into it when needed.
• Pagasa was running the queries and distributing problem ID, by email, fax or phone to data collectors.
• data cleaner.mdb was outputting many false +ve's, and collectors were complaining about the number of items they were being required to check that were not errors.
• The data cleaner.mdb was reviewed by Trish with Pagasa. The problems found and also the original items in the data cleaning.mdb list from Julie is posted below. The list of checks for this program that were are X drive were also transcribed to this list.

Related articles

• for a list of articles relating to data cleaner see: Data Cleaner.mdb Category
• for a list of integrity checks, See: ! Automated Data Integrity Checks (this list is being thinned out into smaller articles which will be place in the Category Data Cleaner.mdb.