Data Integrity Check ready to implement: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Created page with "== Cross checks that need review == Current number of Data Integrity Checks: {{#ask: DICStatus::ready to implement |format=count }} {{#ask: DICStatus::ready to implement..."
 
mNo edit summary
Line 1: Line 1:
== Cross checks that need review ==
== Cross checks that are ready to implement ==
Current number of Data Integrity Checks: {{#ask: [[DICStatus::ready to implement]] |format=count }}
Current number of Data Integrity Checks: {{#ask: [[DICStatus::ready to implement]] |format=count }}
{{#ask: [[DICStatus::ready to implement]]
{{#ask: [[DICStatus::ready to implement]]

Revision as of 23:54, 26 October 2018

Cross checks that are ready to implement

Current number of Data Integrity Checks: 3

 DICSummaryDiscussQuestionDiscussWhoLast editor is"Last editor is" is a predefined property that contains the page name of the user who created the last revision and is provided by Semantic MediaWiki.
Link_suspect_visitAdmitDtTm_mult_to-from-home queryChecks for records that are likely part of the same admission but have different Visit Admit DtTm field.
  • implement this
  • with L_Problems tie in
  • tell Pagasa it exists
TinaTtenbergen
Query Check_from_ED_and_prev_location_same_siteA patient would not usually be sent from their own site to their own ED. It can happen, so this is a soft check.Ttenbergen
Query cardiac arrest throughout admissionAny patient who is admitted to ICU from Med or another ICU with a #Cardiac Arrest dx should have one in their immediately preceeding Med or ICU record also.Ttenbergen