Query Import request matcher

Data Integrity Checks
Summary:	Records in for which we have patients in L_Log but no lab records from DSM
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 Import_request_matcher
Uses L Problem table:	not relevant for this app
Status:	needs review
Implementation Date:
Backlogged:	true

• Cargo

• SMW

• Categories:  

• form:

D_IDs in CFE for which no DSM labs exist

Instructions

• Open query Import_request_matcher in pivot chart or pivot table view. The percentage should be higher than 97%, if it is lower, review.

Scenarios

1. legitimately no labs done (pt dies before labs are done, palliative, short stay)
   • In the past we would have entered a "no labs" for these. Do we want to do something similar? It would have to be something Pagasa enters; not sure based on what. Might be a lot of extra work. Need to review. For now we do not have an entry like that. And it might not be worth it - what would Pagasa do to check that the no-labs are legit?
2. Alun unable to match
   • eg. we have a bad Chart number / PHIN - Pagasa could review and fix our data and re-request; added benefit would be data validation
   • would we expect other reasons why data is present with DSM but Alun would be unable to match?
3. we change/fix a D_ID after we request data (ex. wrong D_ID when exported but found it error and so fixed it before the data for import comes back)
   • Pagasa would need to #re-request data for this patient

D_IDs in DSM data for which no CFE record exists

Could happen if we change/fix a D_ID after requesting. Problem is, we can find if one doesn’t exist, but not if one was changed, but the one that was in the export is actually in present now. Not sure how we would catch that.

re-request

We would not want to re-request separately for each problem found, or Alun would get annoyed with us. so Pagasa would need to manually track these somehow to add to the next request. We would need to document that process here (or possibly in a separate page, if any other DSM queries result in need to re-request...).