Centralized data Vetting Process

From CCMDB Wiki
Jump to navigation Jump to search

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

As a first step, make PseudoPHINs for all entries, since the further checks depend on there beeing meaningful PHINs.

  1. Run NDC_PHIN_Fake_Blank and resolve PHINs using the "likely matches" form, accessed via the shaking hands button. Resolve all records on list until that query returns no results.

(Template:Discussion NDC_Highest_PseudoPHIN canlikely go since we now have the pseudophin button. agreed? Ttenbergen 11:39, 2014 February 9 (CST))

Check for problems

Use Centralized data front end.mdb "NDC" (New Data Check) queries and fix data as needed:

  1. NDC_SamePHIN_Site_Diff_chart - fix
  2. NDC_Chart_9_Digit - fix
  3. NDC_DiffPhin_SameLN_FN_DOB - confirm correct (do we have a list for false positives?), fix if needs
  4. NDC_SamePhin_Diff_LN_FN_DOB_Sex - confirm correct (do we have a list for false positives?), fix if needs
  5. NDC_SameChart_site_Diff_PHIN
  6. NDC_Missing_TransferDate_wPivot
  7. a) started: NDC_VAPinAcqDX_NoVAP_DateinTMPV2
    • b)started: ND_sub_VAPinAcqDX_NoVAP_DateinTMPV2_sub_TMPV2_component
  8. a) started: NDC_No_VAPinAcqDX_VAP_dateinTMPV2
    • b)started: ND_sub_NoVAPinAcqDX_VAP_DateinTMPV2_sub_had_VAP_acqDX
  9. need to create: CLIinAcqDX_NoCLI_DateinTMPV2
  10. need to create: No_CLIinAcqDX_CLI_DateinTMPV2

changes needing to be implemented

CCMDB changes

the following could be done in CCMDB.mdb since all data is already available at collection; still can also do them in front end, should implement them so they translate easily... Ttenbergen 11:22, 2014 February 5 (CST)

  1. started in centralized front end: See 8a & b above: NDC_VAPinAcqDX_NoVAP_DateinTMPV2
  2. started in centralize front end: see 9 above: NDC_No_VAPinAcqDX_VAP_dateinTMPV2
  3. need to create: CLIinAcqDX_NoCLI_DateinTMPV2
  4. need to create: No_CLIinAcqDX_CLI_DateinTMPV2

Set record as vetted

  • last: set Record Status field to ... how does "vetted" sound? if so, get rid of this comment. Ttenbergen 15:01, 2014 January 16 (CST) Template:Discussion
    • How and when do you see Pagasa using this field?

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=37081"