Query s tmp comfort care gt one: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 4: Line 4:
|DIC_firmness=hard check
|DIC_firmness=hard check
|DIC_coding=query ''s_tmp_comfort_care_gt_one''
|DIC_coding=query ''s_tmp_comfort_care_gt_one''
|DIC_status=implemented
|DIC_status=retired
|DIC_app=CCMDB.accdb
|DIC_app=CCMDB.accdb
|DIC_backlogged=No
|DIC_backlogged=No
}}
}}
===Log===
* 2023-11-26 - deleted query since it is long defunct. SQL was
SELECT L_TmpV2.Pat_ID, "Pt has more than one comfort care tmp entry." AS Problem
FROM L_TmpV2
WHERE (((L_TmpV2.Project)="Comfort Care"))
GROUP BY L_TmpV2.Pat_ID, "Pt has more than one comfort care tmp entry."
HAVING (((Count(L_TmpV2.Tmp_ID))>1));

Latest revision as of 10:28, 2023 November 26

Data Integrity Checks
Summary: Only one entry allowed per patient.
Related: Comfort Care
Firmness: hard check
Timing: always
App: CCMDB.accdb
Coding: query s_tmp_comfort_care_gt_one
Uses L Problem table: not relevant for this app
Status: retired
Implementation Date: not entered
Backlogged: No
  • Cargo


  • SMW


  • Categories:  
  • form:

Log

  • 2023-11-26 - deleted query since it is long defunct. SQL was
SELECT L_TmpV2.Pat_ID, "Pt has more than one comfort care tmp entry." AS Problem
FROM L_TmpV2
WHERE (((L_TmpV2.Project)="Comfort Care"))
GROUP BY L_TmpV2.Pat_ID, "Pt has more than one comfort care tmp entry."
HAVING (((Count(L_TmpV2.Tmp_ID))>1));