PHIN field: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) |
||
| Line 40: | Line 40: | ||
=== Patient changes PHIN over time === | === Patient changes PHIN over time === | ||
A Patient's PHIN | |||
Regarding PHIN/pseudPHINs for people with multiple such identifiers. This can occur in 3 main ways: | |||
* moving from OOP to MB, | |||
* moving from MB to OOP, and | |||
* a single individual having multiple PHINs | |||
For the purpose of identifying “same person”, and uniformity, we '''agreed that we will capture the current/most recent identifier (PHIN or pseudoPHIN) and record prior identifiers in the ALIAS location.''' | |||
{{DiscussTask | | {{DiscussTask | | ||
* What do we do if a person's insurance status changes or they move in or out of [[Province]]? Do we change those PHINs? If we wanted to keep the same person_ID for different PHINs we would need to remove the first step in [[Generate Person IDs]] that blows away Person_IDs for duplicate PHINs. but: if we remove that step we will no longer make sure that the scenario of multiple PHINs per Person_ID doesn't happen accidentally. | * What do we do if a person's insurance status changes or they move in or out of [[Province]]? Do we change those PHINs? If we wanted to keep the same person_ID for different PHINs we would need to remove the first step in [[Generate Person IDs]] that blows away Person_IDs for duplicate PHINs. but: if we remove that step we will no longer make sure that the scenario of multiple PHINs per Person_ID doesn't happen accidentally. | ||
| Line 48: | Line 57: | ||
{{DT | In all three cases, newest and most current is stored in PHIN and old would go into ALIAS field. }} | {{DT | In all three cases, newest and most current is stored in PHIN and old would go into ALIAS field. }} | ||
<!-- as per Task Team Meeting - Rolling Agenda and Minutes 2019#ICU Database Task Group Meeting – February 25, 2019 --> | |||
=== Changing PHINs === | === Changing PHINs === | ||