Centralized data Vetting Process: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Line 4: Line 4:
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.


When you 'pull'  
When you 'pull'
 
''centralized.mdb''
''centralized.mdb''
''phi.mdb''
 
and ''phi.mdb''
 
It goes into the desktop ''Centralized...'' (folder icon)
It goes into the desktop ''Centralized...'' (folder icon)
from the ''Regional...'' (wreath icon)
from the ''Regional...'' (wreath icon)


Pull is for the data processor to do edits, etc
Pull is for the data processor to do edits, etc.


Push is for everyone else to see the data
Push is for everyone else to see the data


'''**''' Before going home
'''**''' Before going home
'''ALWAYS''' make sure you are in the 'push' mode
'''ALWAYS''' make sure you are in the 'push' mode
[[User:PTorres|PTorres]] 13:52, 2014 July 16 (CDT)


==clean ups==
==clean ups==

Revision as of 13:55, 2014 July 16

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.

When you 'pull'

centralized.mdb

and phi.mdb

It goes into the desktop Centralized... (folder icon)

from the Regional... (wreath icon)

Pull is for the data processor to do edits, etc.

Push is for everyone else to see the data

** Before going home

ALWAYS make sure you are in the 'push' mode

clean ups

do ONLY once when we import Ed's to centralized.mdb

  • 1use_only_update_3000_transfer_dates_to_null

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:

  1. open the patient from the patient list
  2. click the pseudo button to the left of the PHIN field label
  3. 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".

  1. "NDC_orphans"
  2. NDC_SamePHIN_Site_Diff_chart - fix
  3. NDC_Chart_9_Digit - fix
  4. NDC_DiffPhin_SameLN_FN_DOB - ?
  5. NDC_SamePhin_Diff_LN_FN_DOB_Sex - ?
  6. NDC_SameChart_site_Diff_PHIN
  7. NDC_Missing_TransferDate_wPivot
  8. NDC_VAP_AcqDX_but_NoVAP_DateinTMPV2 (see VAP Dx vs Tmp checking)
  9. NDC_VAP_No_AcqDX_but_VAP_DateinTMPV2 (see VAP Dx vs Tmp checking)
  10. NDC_VAP_unacceptable_date (see VAP Dx vs Tmp checking)
  11. NDC_CLI_AcqDX_but_NoCLI_DateinTMPV2 (see CLI Dx vs Tmp checking)
  12. NDC_CLI_No_AcqDX_but_CLI_DateinTMPV2 (see CLI Dx vs Tmp checking)
  13. NDC_CLI_unacceptable_date (see CLI Dx vs Tmp checking)

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.

Confirm data backups

Until we are comfortable with the process working, check that the backups for centralized are being created as they should be b Pull down centralized data.vbs and Push up centralized data.vbs. Once we are confident I would recommend a monthly Outlook task to check, with the link to the directory included. Ttenbergen 16:43, 2014 April 30 (CDT)

As per Trish, moved from 1Backup.bat, the Data Processor must regularly (at least once per week) check if backup went to location expected or not. In the past main office has experienced backup batch files that for some reason stopped working. Because no one did regular checks we had long period with with no backup!Trish Ostryzniuk 18:54, 2014 April 29 (CDT)