Query Import request matcher

From CCMDB Wiki
Revision as of 15:23, 2019 April 17 by Ttenbergen (talk | contribs) (Created page with "{{Data Integrity Check |DIC_summary=Records in for which we requested DSM data but did not receive any. |DIC_related_concepts=Instructions for importing a batch of DSM Data, I...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Data Integrity Checks
Summary: Records in for which we requested DSM data but did not receive any.
Related: Instructions for importing a batch of DSM Data, Instructions for requesting a batch of data from DSM, DSM Labs data.accdb
Firmness:
Timing:
App: DSM Labs Consistency check.accdb
Coding: query NDC_DSM_Unmatched_records
Uses L Problem table: not relevant for this app
Status: needs review
Implementation Date:
Backlogged: true
  • Cargo


  • SMW


  • Categories: 
  • form:

Could be in Centralized data front end.accdb but more likely in DSM Labs Consistency check.accdb

  • SMW


  • Cargo


  • Categories
  • We are expecting proportion of unmatched records each time. Last email from Alun had 1%, not sure what it has been over time. So, anything that shows up on this list might just be somethign Alun could not match, and it might even be a case of a patient legitimately not having any labs. So, what do we actually want to list, and what would Pagasa do with any contents of the list?
  • SMW


  • Cargo


  • Categories