PHIN field: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
Line 52: Line 52:
* ensure that [[PHIN field]] and [[Chart number]] are not identical  
* ensure that [[PHIN field]] and [[Chart number]] are not identical  
* ensure that not (PHIN > 130 000 000 and PHIN <> 999 999 999) (to accomodate PseudoPHIN)  
* ensure that not (PHIN > 130 000 000 and PHIN <> 999 999 999) (to accomodate PseudoPHIN)  
 
{{Discussion}}
*2018-Sept-11:
**Tina to fix integrity check:  if there are two pts on laptop that are complete and being sent with Rrov of MB with PHIN of 999999999, collecting will get sending error message regarding ....same pt with overlapping admission.
***The Error message box also has a link to an integrity check on Wiki that does not exist.  This message needs to be cleaned out of ccmdb.


[[Category: Identification numbers]]
[[Category: Identification numbers]]
[[Category: Data Collection Guide]]
[[Category: Data Collection Guide]]
[[Category: Demographics]]
[[Category: Demographics]]

Revision as of 13:16, 2018 September 11

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 manually by Pagasa based on a series she maintains. List of pseudo PHIN's used and next number available is kept in a blue book at Pagasa work station.

Use started in 1999 and starts in '1' and as of today Mar 18, 2013 our last Pseudo number is 7043. PTorres 15:45, 2013 March 18 (EDT)(EDT)

PseudoPHINs are generated automatically, see Generating PseudoPHINs.

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

Template:CCMDB Data Integrity Checks

  • for patients with Province = MB, the PHIN has to be > 100000000 and < 999999999, i.e. it has to have 9 digits
  • for out-of-province patients, the PHIN must be entered as blank. (PHIN entered as blank will be replaced by pseudo-PHIN by the Data Processor)
  • ensure that PHIN field and Chart number are not identical
  • ensure that not (PHIN > 130 000 000 and PHIN <> 999 999 999) (to accomodate PseudoPHIN)

Template:Discussion

  • 2018-Sept-11:
    • Tina to fix integrity check: if there are two pts on laptop that are complete and being sent with Rrov of MB with PHIN of 999999999, collecting will get sending error message regarding ....same pt with overlapping admission.
      • The Error message box also has a link to an integrity check on Wiki that does not exist. This message needs to be cleaned out of ccmdb.