PHIN field: Difference between revisions

(11 intermediate revisions by 2 users not shown)

Line 13:

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 [[PHIN field#Pseudo-PHIN|Pseudo PHIN]].

~~{{DiscussTask|~~

* Pagasa just mentioned to me that she used to get many records needing a PseudoPHIN assigned (as many as ~50/day, ~20 average), but lately there are many fewer, e.g. ~5. Can we think of any reason why that would be right? Have some processes external to us changed that would cause this? Or might this be an indicator that we are missing these patients? [[User:Ttenbergen|Ttenbergen]] 14:41, 2022 March 24 (CDT)

}}

== MB Health PHINs only ==

Line 58:

Line 53:

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 [[data processor|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~~.

Use started in 1999 and starts in '1' and as of 2025-06-20 our last Pseudo number was 31329.

We observed that there was a drop in the number of PseudoPHINs during the part of COVID. We confirmed that fewer out-of-province patients would have been accepted during this time, so that change is legitimate.

=== Multiple PHINs or PHIN changes over time ===

~~~~

Also see [[Biographic changes over time]]

People may change PHINs over time or have multiple PHINs. This can occur in 3 main ways:

* moving from OOP to MB,

* moving from OOP (out of province) to MB,

* moving from MB to OOP, and

* a single individual having multiple PHINs (usually ~~somethign~~ went wrong in registration with MB Health)

* a single individual having multiple PHINs (usually something went wrong in registration with MB Health)

For the purpose of identifying "same person", and uniformity, we will enter the ~~current/~~most PHIN or PseudoPHIN into the PHIN field of all encounters of that patient in our database. Earlier PHINs or PseudoPHINs will be retained in [[Alias ID collection]]. '''This may mean that we change an existing PHIN to a PseudoPHIN. '''

For the purpose of identifying "same person", and uniformity, we will enter the '''most recent''' PHIN or PseudoPHIN into the PHIN field of all encounters of that patient in our database. Earlier PHINs or PseudoPHINs will be retained in [[Alias ID collection]]. '''This may mean that we change an existing PHIN to a PseudoPHIN. '''

~~~~

~~This~~ may trigger some errors in our cross ~~checks~~; if so, appropriate records will be added to the [[L_Problem table]] so the error goes away.

'''[[Data Processing]]''':

As discussed at [[Task Team Meeting - Rolling Agenda and Minutes 2019#ICU Database Task Group Meeting – February 25, 2019|Task]], this may trigger some errors in our [[cross check]]s; if so, appropriate records will be added to the [[L_Problem table]] so the error goes away.

Line 79:

Line 77:

[[Category: Identification numbers]]

[[Category:Identification numbers]]

[[Category: Data Collection Guide]]

[[Category:Data Collection Guide]]

[[Category: Demographics]]

[[Category:Demographics]]

@@ Line 13: / Line 13: @@
 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 [[PHIN field#Pseudo-PHIN|Pseudo PHIN]].
-{{DiscussTask|
-* Pagasa just mentioned to me that she used to get many records needing a PseudoPHIN assigned (as many as ~50/day, ~20 average), but lately there are many fewer, e.g. ~5. Can we think of any reason why that would be right? Have some processes external to us changed that would cause this? Or might this be an indicator that we are missing these patients? [[User:Ttenbergen|Ttenbergen]] 14:41, 2022 March 24 (CDT)
-}}
 == MB Health PHINs only ==
@@ Line 58: / Line 53: @@
 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 [[data processor|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.
+Use started in 1999 and starts in '1' and as of 2025-06-20 our last Pseudo number was 31329.
+We observed that there was a drop in the number of PseudoPHINs during the part of COVID. We confirmed that fewer out-of-province patients would have been accepted during this time, so that change is legitimate.
 === Multiple PHINs or PHIN changes over time ===
-<!-- if this changes, update [[Biographic changes over time]] -->
+Also see [[Biographic changes over time]]
 People may change PHINs over time or have multiple PHINs. This can occur in 3 main ways:
-* moving from OOP to MB,
+* moving from OOP (out of province) to MB,
 * moving from MB to OOP, and
-* a single individual having multiple PHINs (usually somethign went wrong in registration with MB Health)
+* a single individual having multiple PHINs (usually something went wrong in registration with MB Health)
-For the purpose of identifying "same person", and uniformity, we will enter the current/most PHIN or PseudoPHIN into the PHIN field of all encounters of that patient in our database. Earlier PHINs or PseudoPHINs will be retained in [[Alias ID collection]]. '''This may mean that we change an existing PHIN to a PseudoPHIN. '''
+For the purpose of identifying "same person", and uniformity, we will enter the '''most recent''' PHIN or PseudoPHIN into the PHIN field of all encounters of that patient in our database. Earlier PHINs or PseudoPHINs will be retained in [[Alias ID collection]]. '''This may mean that we change an existing PHIN to a PseudoPHIN. '''
-<!-- as per Task Team Meeting - Rolling Agenda and Minutes 2019#ICU Database Task Group Meeting – February 25, 2019 -->
-This may trigger some errors in our cross checks; if so, appropriate records will be added to the [[L_Problem table]] so the error goes away.
+'''[[Data Processing]]''':
+As discussed at [[Task Team Meeting - Rolling Agenda and Minutes 2019#ICU Database Task Group Meeting – February 25, 2019|Task]], this may trigger some errors in our [[cross check]]s; if so, appropriate records will be added to the [[L_Problem table]] so the error goes away.
 {{Guideline Minimal Data Set}}
@@ Line 79: / Line 77: @@
 {{Related Articles}}
-[[Category: Identification numbers]]
+[[Category:Identification numbers]]
-[[Category: Data Collection Guide]]
+[[Category:Data Collection Guide]]
-[[Category: Demographics]]
+[[Category:Demographics]]