Centralized data Vetting Process: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
TOstryzniuk (talk | contribs)
m Text replacement - "[["Pull" Centralized_data.accdb]]" to ""Pull" Centralized_data.accdb"
 
(177 intermediate revisions by 4 users not shown)
Line 1: Line 1:
"Vetting" is our name for the initial quality control our data goes through after [[Data collector]]s finish [[sending]] it. It is one of the main responsibilities of the [[Data Processor]].


{{Discussion}}
== Instructions ==
Where is the article that listed the 6 QA checks and the Pivot article?  I need to show Pagasa how is was transcribe into this here. [[User:TOstryzniuk|Trish Ostryzniuk]] 15:29, 2014 January 24 (CST)
* [["Pull" Centralized_data.accdb]]
* Double click to open ''Centralized_data_front_end.mdb''
* [[Reconnect CFE and initial error checks]]
* [[Pre-linking checks]] (PL checks)
* [[Populate linking_pairs]]
* [[Correcting suspect links]]
* [[Quality Assurance queries in CFE]] - NDC Queries
** as part of any of those, there might be [[Questioning data back to collectors]]
* [["Vet all sent" button]]
* [[Generate Person IDs]]
* [["Push" Centralized_data.accdb]] to return data to [[Regional Server]] so [[Data collector]]s can [[send]]


'' see [[Basic Analysis Capabilities]] for functionality not related to vetting new data
== Related articles ==
{{Related Articles}}


'''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.
== Check for problems ==
Use [[Centralized data front end.mdb]] "NDC" (New Data Check) queries and fix data as needed:
# NDC_PHIN_Fake_Blank
# NDC_Highest_PseudoPhin
# NDC_SamePHIN_Site_Diff_chart - fix
# NDC_Chart_9_Digit - fix
# NDC_DiffPhin_SameLN_FN_DOB - confirm correct (do we have a list for false positives?), fix if needs
# NDC_SamePhin_Diff_LN_FN_DOB_Sex - confirm correct (do we have a list for false positives?), fix if needs
#NDC_SameChart_site_Diff_PHIN
#a) started: NDC_VAPinAcqDX_NoVAP_DateinTMPV2
#*b)started: ND_sub_VAPinAcqDX_NoVAP_DateinTMPV2_sub_TMPV2
#Started: NDC_No_VAPinAcqDX_VAP_dateinTMPV2
#need to create: CLIinAcqDX_NoCLI_DateinTMPV2
#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)''
#started in centralized front end: See 8a above: VAPinAcqDX_NoVAP_DateinTMPV2
#started in centralize front end: see 8b above: No_VAPinAcqDX_VAP_dateinTMPV2
#need to create: CLIinAcqDX_NoCLI_DateinTMPV2
#need to create: No_CLIinAcqDX_CLI_DateinTMPV2
== Make PseudoPHINs ==
# NDC_PHIN_Blank (renamed for consistency)
# NDC_Highest_PseudoPHIN
== any other checks after pseudoPhin? ==
{{discussion}}
== 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) {{discussion}}
**How and when do you see Pagasa using this field?
[[Category:2013 data upgrades]]
[[Category: Data Processing]]
[[Category:Data Processing]]
[[Category:Data Processing]]

Latest revision as of 15:42, 23 July 2025

"Vetting" is our name for the initial quality control our data goes through after Data collectors finish sending it. It is one of the main responsibilities of the Data Processor.

Instructions

Related articles

Related articles: