CCMDB Wiki

Centralized data Vetting Process

Revision as of 12:06, 14 March 2014 by Ttenbergen (talk | contribs) (→Check for problems)

see also Query for centralized for now. see Basic Analysis Capabilities for functionality not related to vetting new data

Need to resolve all http://ccmdb.kuality.ca/index.php/Special:WhatLinksHere/Centralized_data_Vetting_Process

need to make sure all in Data Appending Process is addressed.

Pull down data

not yet implemented... Ttenbergen 11:43, 2014 February 9 (CST)

Before processing run Pull_down_centralized_data.bat to do backups and move data from the regional server for local processing. This also prevents collectors from sending while data is being processed.

Make PseudoPHINs

If it is determined that a patient legitimately without PHIN (e.g. out of province) has not been encountered before, generate a PseudoPHIN:

  1. open the patient from the patient list
  2. click the pseudo button to the left of the PHIN field label
  3. the program will look up the highest previous PseudoPHIN and enter that + 1 into the PHIN field

Check for problems

Use Centralized data front end.mdb "NDC" (New Data Check) queries and fix data as needed; if a patient shows up in one of the queries fix if possible; if question to collector is required, set Record Status field to "questioned".

  1. NDC_SamePHIN_Site_Diff_chart - fix
  2. NDC_Chart_9_Digit - fix
  3. NDC_DiffPhin_SameLN_FN_DOB - ?
  4. NDC_SamePhin_Diff_LN_FN_DOB_Sex - ?
  5. NDC_SameChart_site_Diff_PHIN
  6. NDC_Missing_TransferDate_wPivot
  7. NDC_VAPinAcqDX_NoVAP_DateinTMPV2
    • query finds all records for which a complication 3900 exists and for whom a corresponding tmp entry with item "VAP" and datevar <> null does not exist
    • uses subquery "ND_Sub_VAPinAcqDX_NoVAP_DateinTMPV2_Sub_TMPV2_Component"
  8. NDC_No_VAPinAcqDX_VAP_dateinTMPV2
    • finds all records that have a tmp entry with item "VAP" for which a l_dxs complication entry with code 3900 does not exist
    • uses query ND_sub_NoVAPinAcqDX_VAP_DateinTMPV2_sub_had_VAP_acqDX
  9. need to create: CLIinAcqDX_NoCLI_DateinTMPV2
  10. need to create: No_CLIinAcqDX_CLI_DateinTMPV2

Set record as vetted

At this point all records with problems will have had the Record Status field set to "questioned" so the remaining ones that are set to "sent" are clean and can be set to "vetted". Press the "vet all sent" button. This will change all records currently set to "sent" to "vetted".

Push up data

not yet implemented... Ttenbergen 11:43, 2014 February 9 (CST)

When all processing is done, run Push_up_centralized_data.bat to return the data to where collectors can add to it.

Retrieved from "https://ccmdb.kuality.ca/index.php?title=Centralized_data_Vetting_Process&oldid=37602"