Query check pt from ER: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 5: Line 5:
| DIC_timing = always
| DIC_timing = always
| DIC_app = CCMDB.accdb
| DIC_app = CCMDB.accdb
| DIC_coding = function Validate_Accept_DtTm(); (function from_ER(); query ''check_pt_from_ER'' but those are also used in new boarding loc based validation)
| DIC_coding = function from_ER(); query ''check_pt_from_ER''  
| DIC_status = implemented
| DIC_status = implemented
| DIC_implementation_date = date change was rolled out / first applied
| DIC_implementation_date = date change was rolled out / first applied
Line 12: Line 12:
This query in [[CCMDB.accdb]] identifies patients from ER. The name would lead you to think it's a cross check query, but it isn't.
This query in [[CCMDB.accdb]] identifies patients from ER. The name would lead you to think it's a cross check query, but it isn't.


Query is used by by function from_ER() which is in turn used by function Validate_Accept_DtTm() which validates the [[Accept DtTm]].
Query is used by by function from_ER() which is in turn used [[query check_tmp_ER_Boarding_Loc_should_exist_if_from_ER]]


== Related articles ==
== Related articles ==

Revision as of 15:52, 2022 April 21

Data Integrity Checks
Summary: part of validating Accept DtTm
Related: Accept DtTm, Previous Location
Firmness: soft check
Timing: always
App: CCMDB.accdb
Coding: function from_ER(); query check_pt_from_ER
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: date change was rolled out / first applied
Backlogged: true
  • Cargo


  • SMW


  • Categories: 
  • form:

This query in CCMDB.accdb identifies patients from ER. The name would lead you to think it's a cross check query, but it isn't.

Query is used by by function from_ER() which is in turn used query check_tmp_ER_Boarding_Loc_should_exist_if_from_ER

Related articles

Related articles: