ClientGUID field

From CCMDB Wiki
Revision as of 08:20, 2022 March 24 by Ttenbergen (talk | contribs) (Created page with "{{Data element |field_name=ClientGUID |Rank=N/A |in_table=Cognos_Import3 |data_type=string |datafield_length=16 |program_collecting=Med and CC |created_raw=Raw |data_element_sort_index= |element_description=The unique person identifier from Cognos. }} Many patients don't have MB PHINs so we generate PseudoPHINs. I figured EPR must already solve this problem, and they use this field. We now get this as part of the Cognos data dump. If we set up the infra...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Data Element (edit)
Field Name: ClientGUID
CCMDB Label: not stated
CCMDB tab: not stated
Table: Cognos_Import3
Data type: string
Length: 16
Program: Med and CC
Created/Raw: Raw
Start Date: 1988-07-11
End Date: 2300-01-01
Sort Index:

The unique person identifier from Cognos.

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


Many patients don't have MB PHINs so we generate PseudoPHINs. I figured EPR must already solve this problem, and they use this field. We now get this as part of the Cognos data dump. If we set up the infrastructure to actually put this into patient records then we might be able to step away from the PseudoPhin process, and should have many fewer link errors.

  • Do all collectors now add records from Cognos only or do some still do manual entry? Manual entry would break this. Ttenbergen 09:20, 2022 March 24 (CDT)
  • SMW


  • Cargo


  • Categories

Changing D_IDs

Changing D_IDs

Related Articles

Related articles: