Centralized data Vetting Process: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m (→‎steps: clean-up)
 
(52 intermediate revisions by 3 users not shown)
Line 1: Line 1:
*'''need to make sure all in [[Data Appending Process]] is addressed.'''
"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]].
 
 
== Pull data ==
*[["Pull" Centralized data.mdb]]
 
==prep CFE for use==
*Double click to open ''Centralized_data_front_end.mdb''
*click Reconnect
== steps ==
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"'''
 
Perform the Queries in this order:
 
# [[Orphans in Centralized data.mdb| "NDC_orphans"]]
# NDC_Diff_Phin_SameLN_FN_DOB
#* Home, Advanced, Advanced Filter/Sort, LastName (double click or drag & drop), Sort by ''ascending'', Home, Toggle Filter
# NDC_PHIN_fake_or_blank
# NDC_SameChart_Site_Diff_Phin
# NDC_SamePhin_Diff_LN_FN_DOB_Sex
#* Home, Advanced, Advanced Filter/sort, Phin (double click or drag & drop), Sort by ''ascending'', Home, Toggle Filter
# NDC_SamePHIN_Site_Diff_chart
 
??
NDC_discharged_incomplete
NDC_Highest_PseudoPHIN
 
QA checks
# see [[Generating PseudoPHINs]]
#* should always be zero
# NDC_Chart_9_Digit
# NDC_Bad_Postal_Code
# NDC_Missing_TransferDate_w_pivot
 
# NDC_CLI_AcqDX_but_NoCLI_DateinTMPV2
# NDC_CLI_No_AcqDX_but_CLI_DateinTMPV2
# NDC_CLI_unacceptable_date
# NDC_VAP_AcqDX_but_NoVAP_DateinTMPV2 (see [[VAP Dx vs Tmp checking]])
# NDC_VAP_No_AcqDX_but_VAP_DateinTMPV2 (see [[VAP Dx vs Tmp checking]])
# NDC_VAP_unacceptable_date (see [[VAP Dx vs Tmp checking]])
 


== Instructions ==
* [["Pull" Centralized data.mdb]]
* 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]]
* [[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.mdb]] to return data to [[Regional Server]] so [[Data collector]]s can [[send]]


== Set record as vetted ==
== Related articles ==
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".
{{Related Articles}}
 
# Press the "vet all sent" button.
# The program will display a count of how many records have each of the recorstatatus possibilities.
#* take note of the "sent" number and click OK
# The program will tell how many records it is about to update. 'you are about to update ___ rows'
#* If this number is the same as the number of sent records, click OK, if not click cancel and try to figure out what is wrong.
# This will change all records currently set to "sent" to "vetted".
 
== Push up data ==
When all processing is done, run [[Push_up_centralized_data.vbs]] to return the data to where collectors can add to it.


== backup and confirm data backups ==
see [[Centralized data backup process]]


[[Category:Data Processing]]
[[Category:Data Processing]]

Latest revision as of 21:25, 2022 March 24

"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:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Centralized_data_Vetting_Process&oldid=155230"