Centralized data Vetting Process: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Line 51: Line 51:


== Set record as vetted ==
== 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".
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.
When all data is cleaned, the last query is ''NDC_unvetted''
# The program will display a count of how many records have each of the recorstatatus possibilities.
* does that query actually do anything for us? Ttenbergen 23:07, 2014 September 29 (CDT)
#* 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'
On the 'RecStatus' column
#* 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".
Right click the first one
 
Sort by Z to A which will sort by Sent, Questioned, Incomplete statuses
 
Scroll down to the last 'sent' record, to see how many records will be vetted
* should that query just change to have only "sent"s? Ttenbergen 23:07, 2014 September 29 (CDT)
 
Then click the ''Vet All Sent'' button
 
Prompts 'are you sure'
 
answer Yes
 
prompts 'you are about to run ...'
 
answer Yes
 
prompts 'you are about to update ___ rows'  
 
answer Yes
 
The number in the ''___ rows'', should be the same as the last 'sent' record from your scroll down
 
e.g. if your last 'sent' record was 25, then the prompt will say 'you are about to update 25 rows'
* has the number ever been anything different?  Ttenbergen 23:07, 2014 September 29 (CDT)
** yes it has [[User:PTorres|PTorres]] 10:55, 2014 October 1 (CDT)
 
* Tina will replace this process with a tally msgox that comes up when "vet all" is pressed, ok, how many will be updated, ok, [[User:PTorres|PTorres]] 10:55, 2014 October 1 (CDT)
* NDC unvetted can then be deleted[[User:PTorres|PTorres]] 10:55, 2014 October 1 (CDT)
{{discussion}}


== Push up data ==
== Push up data ==

Revision as of 15:06, 1 October 2014


Pull data

prep CFE for use

  • Double click to open Centralized_data_front_end.mdb
  • click Reconnect

cross-check tables

  • Open Patient List
  • on the Left side,
  • scroll All Access Objects
  • Tables
    • L_Log - write down the number
    • L_PHI - write down the number
  • click back to top
    • Queries
    • L_Log_PHI - write down the number

**ALL 3 must be the same**


Make PseudoPHINs

see Generating PseudoPHINs

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"

Perform the Queries in this order:

  1. "NDC_orphans"
    • should always be zero
  2. NDC_Chart_9_Digit
  3. NDC_Diff_Phin__SameLN_FN_DOB
    • Home, Advanced, Advanced Filter/Sort, LastName (double click or drag & drop), Sort by ascending, Home, Toggle Filter
  4. NDC_SameChart_Site_Diff_Phin
  5. NDC_SamePhin_Diff_LN_FN_DOB_Sex
    • Home, Advanced, Advanced Filter/sort, Phin (double click or drag & drop), Sort by ascending, Home, Toggle Filter
  6. NDC_SamePHIN_Site_Diff_chart
  7. NDC_CLI_AcqDX_but_NoCLI_DateinTMPV2 (see CLI Dx vs Tmp checking)
  8. NDC_CLI_No_AcqDX_but_CLI_DateinTMPV2 (see CLI Dx vs Tmp checking)
  9. NDC_CLI_unacceptable_date (see CLI Dx vs Tmp checking)
  10. NDC_VAP_AcqDX_but_NoVAP_DateinTMPV2 (see VAP Dx vs Tmp checking)
  11. NDC_VAP_No_AcqDX_but_VAP_DateinTMPV2 (see VAP Dx vs Tmp checking)
  12. NDC_VAP_unacceptable_date (see VAP Dx vs Tmp checking)
  13. NDC_unvetted

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".

  1. Press the "vet all sent" button.
  2. 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
  3. 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.
  4. 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