PL 2Phin Fake or Blank: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
Line 4: | Line 4: | ||
|DIC_firmness=hard check | |DIC_firmness=hard check | ||
|DIC_coding=query ''PL_2Phin_Fake_or_Blank'' | |DIC_coding=query ''PL_2Phin_Fake_or_Blank'' | ||
|DIC_status= | |DIC_status=ready to implement | ||
|DIC_app=Centralized data front end.accdb | |DIC_app=Centralized data front end.accdb | ||
}} | }} | ||
{{DT | As per meeting with Allan, Julie and Pagasa: (1) only if complete AND (2) only do links in incomplete if have PHIN. }} | |||
== Related articles == | == Related articles == | ||
{{Related Articles}} | {{Related Articles}} |
Revision as of 14:35, 2019 September 18
Data Integrity Checks | |
Summary: | Finds blank PHINs and those entered to meet function Validate_PHIN so Data Processor can apply PseudoPHIN via Generating PseudoPHINs. |
Related: | PHIN field |
Firmness: | hard check |
Timing: | always |
App: | Centralized data front end.accdb |
Coding: | query PL_2Phin_Fake_or_Blank |
Uses L Problem table: | not entered |
Status: | ready to implement |
Implementation Date: | not entered |
Backlogged: | true |
As per meeting with Allan, Julie and Pagasa: (1) only if complete AND (2) only do links in incomplete if have PHIN. |
Related articles
Related articles: |