Check APACHE physiological variable high low: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
m Text replacement - "CCMDB.mdb" to "CCMDB.accdb"
 
Line 4: Line 4:
| DIC_firmness = hard check and soft check  
| DIC_firmness = hard check and soft check  
| DIC_timing =
| DIC_timing =
| DIC_app = CCMDB.mdb
| DIC_app = CCMDB.accdb
| DIC_coding = functions ''validate_x'', function ''Min_Max_Checker''  
| DIC_coding = functions ''validate_x'', function ''Min_Max_Checker''  
| DIC_status = implemented
| DIC_status = implemented
Line 11: Line 11:


== Implementation ==
== Implementation ==
The various validate_x functions in [[CCMDB.mdb]] call the function ''Min_Max_Checker'' with parameters for absolute and warning thresholds.  
The various validate_x functions in [[CCMDB.accdb]] call the function ''Min_Max_Checker'' with parameters for absolute and warning thresholds.  


The function has "absolute" and "rare" minima and maxima as a parameter. The "absolute" ones are never allowed. The "rare" ones require an explanation in the [[Notes field]].  
The function has "absolute" and "rare" minima and maxima as a parameter. The "absolute" ones are never allowed. The "rare" ones require an explanation in the [[Notes field]].  

Latest revision as of 10:43, 2019 September 22

Data Integrity Checks
Summary: an APACHE physiological variable is extremely high or low
Related: AaDO2, AP Dias BP Field, AP Sys BP Field, Creatinine (APACHE), FiO2, HCT, Hemat, HR, K, Na, PCO2, PH, PO2, RR, Serum CO2, Temperature, WBC
Firmness: hard check and soft check
Timing:
App: CCMDB.accdb
Coding: functions validate_x, function Min_Max_Checker
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: 2008-01-01
Backlogged: true
  • Cargo


  • SMW


  • Categories:  
  • form:

Implementation

The various validate_x functions in CCMDB.accdb call the function Min_Max_Checker with parameters for absolute and warning thresholds.

The function has "absolute" and "rare" minima and maxima as a parameter. The "absolute" ones are never allowed. The "rare" ones require an explanation in the Notes field.

This was implemented with the first version of CCMDB, so not clear now what the date was.

Related articles

Related articles: