Function Validate Chart: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 9: Line 9:
| DIC_timing =
| DIC_timing =
| DIC_app = CCMDB.mdb
| DIC_app = CCMDB.mdb
| DIC_coding =   
| DIC_coding =  Function ''Validate_Chart''
| DIC_status = implemented
| DIC_status = ready to implement
| DIC_implementation_date = 2008-01-01
| DIC_implementation_date = 2008-01-01
}}
}}
Approximate implementation date


The numerical-check is relevant because chart is relevant because the field is stored as a string. Reason unknown.
Add check equivalent to [[PL Chart 9 Digit]].
 
The numerical-check is relevant because the field is stored as a string. Reason unknown.
 
== Log ==
* 2008-01-01 - Approximate implementation date


== Related articles ==
== Related articles ==
{{Related Articles}}
{{Related Articles}}
[[Category:Registry checks]]
[[Category:Registry checks]]

Revision as of 18:26, 2018 November 6

Data Integrity Checks
Summary: validates the Chart number:
  • Chart must be numerical
  • chart must be
  • checks Function PHIN same as Chart
  • no further checks at this time because chart numbers are different at different hospitals
Related: PHIN, Chart number
Firmness: hard check
Timing:
App: CCMDB.mdb
Coding: Function Validate_Chart
Uses L Problem table: not relevant for this app
Status: ready to implement
Implementation Date: 2008-01-01
Backlogged: true
  • Cargo


  • SMW
"CCMDB.mdb" is not in the list (CCMDB.accdb, Centralized data front end.accdb, TISS28.accdb, SAP, DSM Labs Consistency check.accdb, not entered) of allowed values for the "DICApp" property. 
  • Categories: 
  • form:

Add check equivalent to PL Chart 9 Digit.

The numerical-check is relevant because the field is stored as a string. Reason unknown.

Log

  • 2008-01-01 - Approximate implementation date

Related articles

Related articles: