Edit Data Integrity Check: Query Import request matcher

Are you logged on?

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: CCMDB_legit.

Summary (what is the check, one-liner):
links to related pages:
Firmness (is this a warning only (soft check) or will it stop sending (hard check) - applicable only in CCMDB.accdb app):	None/unknown hard check soft check
Timing (does this query run for all records or only complete ones):	None/unknown complete always
Name of the function or query this is implemented as:	query ''Import_request_matcher''
Implementation date:
Implementation Status:
L_Problem (are false positive special cases addressed in table L_Problems - applicable only in CFE):	None/unknown yes no
App:
Backlogged (is this query cleaned up to date or backlogged? Applicable only in CFE):

Free text:

=== 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 ==== # 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?''' # 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? # 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...). == Related articles == {{Related Articles}} [[Category:DSM Labs Extract]] [[Category:DSM check‎‎]]

Explain your edit, if you think it needs explanation (e.g. "as discussed with ...", or "content moved to ...", or "duplicate content, see ..."):

This is a minor edit

Watch this page

Cancel

Edit Data Integrity Check: Query Import request matcher

Navigation menu

Search