Centralized data Vetting Process: Difference between revisions
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
== Pull down data == | == Pull down data == | ||
Before processing run [[Pull_down_centralized_data.vbs]] to do backups and move data from the regional server for local processing. This also prevents collectors from sending while data is being processed. | Before processing run [[Pull_down_centralized_data.vbs]] to do backups and move data from the regional server for local processing. This also prevents collectors from sending while data is being processed. | ||
| Line 42: | Line 40: | ||
== Push up data == | == 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. | When all processing is done, run [[Push_up_centralized_data.vbs]] to return the data to where collectors can add to it. | ||
[[Category:2013 data upgrades]] | [[Category:2013 data upgrades]] | ||
[[Category:Data Processing]] | [[Category:Data Processing]] | ||
Revision as of 13:53, 21 March 2014
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
Before processing run Pull_down_centralized_data.vbs 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:
- open the patient from the patient list
- click the pseudo button to the left of the PHIN field label
- 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".
- NDC_SamePHIN_Site_Diff_chart - fix
- NDC_Chart_9_Digit - fix
- NDC_DiffPhin_SameLN_FN_DOB - ?
- NDC_SamePhin_Diff_LN_FN_DOB_Sex - ?
- NDC_SameChart_site_Diff_PHIN
- NDC_Missing_TransferDate_wPivot
- NDC_VAPinAcqDX_NoVAP_DateinTMPV2
- records for which a complication 3900 exists and for which a corresponding tmp entry with item "VAP" and datevar <> null does not exist
- uses subquery "ND_Sub_VAPinAcqDX_NoVAP_DateinTMPV2_Sub_TMPV2_Component"
- NDC_No_VAPinAcqDX_VAP_dateinTMPV2
- 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
- NDC_CLIinAcqDX_NoCLI_DateinTMPV2
- records for which a complication 8600 exists and for which a corresponding tmp entry with item "CLI" and datevar <> null does not exist
- uses subquery "ND_sub_CLI_DateinTMPV2"
- NDC_No_CLIinAcqDX_CLI_DateinTMPV2
- records that have a tmp entry with item "CLI" for which a l_dxs complication entry with code 8600 does not exist
- uses subquery "ND_sub_has_dx8600"
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
When all processing is done, run Push_up_centralized_data.vbs to return the data to where collectors can add to it.