Query Import request matcher: Difference between revisions

m Text replacement - "|DIC_LProblem=no" to "|DIC_LProblem=No"
 
(2 intermediate revisions by the same user not shown)
Line 2: Line 2:
|DIC_summary=Records in for which we have patients in L_Log but no lab records from DSM
|DIC_summary=Records in for which we have patients in L_Log but no lab records from DSM
|DIC_related_concepts=Instructions for importing a batch of DSM Data; Instructions for requesting a batch of data from DSM; DSM Labs data.accdb
|DIC_related_concepts=Instructions for importing a batch of DSM Data; Instructions for requesting a batch of data from DSM; DSM Labs data.accdb
|DIC_firmness=
|DIC_timing=
|DIC_coding=query ''Import_request_matcher''
|DIC_coding=query ''Import_request_matcher''
|DIC_implementation_date=
|DIC_status=needs review
|DIC_status=needs review
|DIC_LProblem=
|DIC_LProblem=No
|DIC_app=DSM Labs Consistency check.accdb
|DIC_app=DSM Labs Consistency check.accdb
|DIC_backlogged=No
}}
}}
=== D_IDs in CFE for which no DSM labs exist ===
=== D_IDs in CFE for which no DSM labs exist ===
==== Instructions ====
==== Instructions ====
Line 26: Line 23:
=== D_IDs in DSM data for which no CFE record exists ===
=== 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.  
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.  
{{Discuss | who = Tina|
* This one is fairly easy, Pagasa will try to make it. Decided ages ago, but put on Pagasa's list today.
** We only send Vetted data to Allun now.[[User:PTorres|PTorres]] 14:25, 2022 March 17 (CDT)
*** That eliminates the biggest source of errors, but does it eliminate all? Do we still need some kind of cross check for this? What? Will re-route to Julie. [[User:Ttenbergen|Ttenbergen]] 16:55, 2022 March 17 (CDT)
**** Discussed with Julie; we will only request vetted (not discontinued) but I need to update the DSM and discuss with Pagasa. [[User:Ttenbergen|Ttenbergen]] 16:47, 2022 June 8 (CDT) }}


=== re-request ===
=== 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...).  
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 Labs Extract]]
[[Category:DSM check‎‎]]
[[Category:DSM check‎‎]]