PHIN field

From CCMDB Wiki
Jump to navigation Jump to search
Data Element (edit)
Field Name: PHIN
CCMDB Label: PHIN
CCMDB tab: Top Row
Table: L_Log table, L_PHI table
Data type: number
Length: Long Integer
Program: Med and CC
Created/Raw: Raw
Start Date: 1988-07-11
End Date: 2300-01-01
Sort Index: 4

The patient's PHIN .

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


The PHIN (Personal Health Information number) is a unique nine-digit numeric identifier assigned by Manitoba Health to every person registered for health insurance in Manitoba. For patients who are not registered with Manitoba Health we assign a Pseudo PHIN.

MB Health PHINs only

Manitoba Health PHIN numbers only.

If patient permanently resides outside of the province of Manitoba the Province field should not be MB and the PHIN field should be left blank.

Please make every effort to obtain this information and call medical records to help.

Special Cases

Location Manitoba and no PHIN

There are scenarios where a PHIN will not be available for a Manitoba patient, including but not limited to

  • immigrants on visas
  • some prison inmates

In these and similar cases, use 999999999 as the PHIN. The data processor will assign a Pseudo PHIN.

Location Outside Manitoba and no PHIN

PHIN must be entered by data collector as blank. A Pseudo PHIN will be entered by the data processor after file is appended to master database.

Canadian Forces patients

see Canadian Forces patients.

PseudoPHIN

Since the PHIN is used as a unique identifier for patients to detect repeat and continuous visits, a "pseudoPHIN" is assigned for patients who don't have a PHIN. At this point, pseudoPHINS are assigned by Pagasa, see see Generating PseudoPHINs.

Use started in 1999 and starts in '1' and as of Mar 18, 2013 our last Pseudo number was 7043.

Minimal Data Set

This entry is part of the Minimal Data Set. Special collection instructions apply, see that page for more info.

L_PHI vs L_Log

This field is stored in the L_PHI table in CFE but in the L_Log table in CCMDB.accdb. See L_PHI table for details why.

Changing PHINs

Changing PHINs

Cross checks

Data Integrity Checks (automatic list)

 AppStatus
Check duplicate patientCCMDB.accdbimplemented
Query check minimal data set incompleteCCMDB.accdbimplemented
Function Validate PHINCCMDB.accdbimplemented
Function PHIN same as ChartCCMDB.accdbimplemented
Function Validate ChartCCMDB.accdbimplemented
Function Validate ProvinceCCMDB.accdbimplemented
Link suspect dead then alive queryCentralized data front end.accdbimplemented
Link suspect mismatch from ours incomplete queryCentralized data front end.accdbimplemented
Link suspect mismatch to ours incomplete queryCentralized data front end.accdbimplemented
Link suspect negative transit time queryCentralized data front end.accdbimplemented
PL SamePHIN Site Diff chartCentralized data front end.accdbimplemented
PL SameCHART Site Diff PHINCentralized data front end.accdbimplemented
PL Diff Phin SameLN FN DOBCentralized data front end.accdbimplemented
PL 2Phin Fake or BlankCentralized data front end.accdbimplemented
PL SamePhin Diff DOB SexCentralized data front end.accdbimplemented

Related articles

Related articles: