Centralized data Vetting Process: Difference between revisions
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) |
||
| Line 12: | Line 12: | ||
== Make PseudoPHINs == | == 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 == | == Check for problems == | ||
Revision as of 12:22, 13 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
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:
- 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:
- 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
- NDC_Missing_TransferDate_wPivot
- a) started: NDC_VAPinAcqDX_NoVAP_DateinTMPV2
- b)started: ND_sub_VAPinAcqDX_NoVAP_DateinTMPV2_sub_TMPV2_component
- a) started: NDC_No_VAPinAcqDX_VAP_dateinTMPV2
- b)started: ND_sub_NoVAPinAcqDX_VAP_DateinTMPV2_sub_had_VAP_acqDX
- 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 & b above: NDC_VAPinAcqDX_NoVAP_DateinTMPV2
- started in centralize front end: see 9 above: NDC_No_VAPinAcqDX_VAP_dateinTMPV2
- need to create: CLIinAcqDX_NoCLI_DateinTMPV2
- 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)
- How and when do you see Pagasa using this field?
- record that with recordstatus = vetted has been processed and cleaned to the level (or better) previously done during appending and Julie-checks. Once the record is set to this Julie knows she can use this with confidence, e.g. for reports. Ttenbergen 14:15, 2014 March 11 (CDT)
- 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.