Function Validate PHIN

Revision as of 11:39, 25 September 2018 by Ttenbergen (talk | contribs) (Created page with "{{Data Integrity Check | DIC_summary = what is the check (one-liner) | DIC_related_concepts = list of related pages (probably the one it's on, but there might be others...) |...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Data Integrity Checks
Summary: what is the check (one-liner)
Related: list of related pages (probably the one it's on, but there might be others...)
Firmness: hard check or soft check
Timing: always
App: CCMDB.mdb
Coding: how to find this in containing program, eg. SAS file, function name, query name...
Uses L Problem table: not relevant for this app
Status: implementation status (needs review, ready to implement, implemented, not feasible)
Implementation Date: date change was rolled out / first applied
Backlogged: true
  • Cargo


  • SMW

"implementation status (needs review, ready to implement, implemented, not feasible)" is not in the list (needs review, ready to implement, implemented, not entered, not feasible, declined, retired) of allowed values for the "DICStatus" property. "CCMDB.mdb" is not in the list (SAP, not entered, Centralized data front end.accdb, DSM Labs Consistency check.accdb, CCMDB.accdb, TISS28.accdb) of allowed values for the "DICApp" property.

  • Categories:  
  • form:
  • for patients with Province = MB, the PHIN has to be (> 100 000 000 and <= 130 000 000) or 999 999 999 (to accommodate PHIN_field#Location_Manitoba_and_no_PHIN
  • for out-of-province patients, the PHIN must be entered as blank

Related articles

Related articles: