Link suspect not same visitAdmitDtTm query: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Created page with "{{Data Integrity Check |DIC_summary=Checks for records where Visit Admit DtTm field should likely be the same but is not. {{Discussion}} should be based on what? |DIC_rela..."
 
mNo edit summary
Line 1: Line 1:
{{Data Integrity Check
{{Data Integrity Check
|DIC_summary=Checks for records where [[Visit Admit DtTm field]] should likely be the same but is not. {{Discussion}} should be based on what?
|DIC_summary=Checks for records where [[Visit Admit DtTm field]] should likely be the same but is not. {{Discussion}} should be based on what?
|DIC_related_concepts=Pre-admit Inpatient Institution field; Service/Location field
|DIC_related_concepts=Visit Admit DtTm field
|DIC_firmness=soft check
|DIC_firmness=soft check
|DIC_coding=query ''Link_suspect_not_same_visitAdmitDtTm''
|DIC_coding=query ''Link_suspect_not_same_visitAdmitDtTm''

Revision as of 21:53, 2018 October 29

Data Integrity Checks
Summary: Checks for records where Visit Admit DtTm field should likely be the same but is not. Template:Discussion should be based on what?
Related: Visit Admit DtTm field
Firmness: soft check
Timing: always
App: Centralized data front end.accdb
Coding: query Link_suspect_not_same_visitAdmitDtTm
Uses L Problem table: Yes
Status: implemented
Implementation Date: not entered
Backlogged: true
  • Cargo


  • SMW


  • Categories:  
  • form:

confirm:

  • this one likely uses the L Problem table... no?
  • is description really what this does?
  • SMW


  • Cargo


  • Categories

Related articles

Related articles: