Centralized data Vetting Process: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
'' see [[Basic Analysis Capabilities in TMSX]] 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 resolve all http://ccmdb.kuality.ca/index.php/Special:WhatLinksHere/Centralized_data_Vetting_Process | ||
Revision as of 13:15, 13 January 2014
see Basic Analysis Capabilities in TMSX for functionality not related to vetting new data
Need to resolve all http://ccmdb.kuality.ca/index.php/Special:WhatLinksHere/Centralized_data_Vetting_Process
- find blank PHINs and create PseudoPHIN
- this is likely also the right spot to identify Multiple Encounters and Readmissions, since the step is required anyways
- this may be also the time to identify continuous admission
- Query for centralized
- should have a list here as we identify and implement, incl the best order to do this in
- last: set Record Status field to "<what?>"