ClientGUID field: Difference between revisions
Ttenbergen (talk | contribs) |
No edit summary |
||
| Line 15: | Line 15: | ||
=== Background === | === Background === | ||
Many patients don't have MB [[PHIN]]s so we generate [[PseudoPHIN]]s. EPR solves this by using a field ClientGUID, which we get as part of the [[Cognos EPR Report]]. 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. | Many patients don't have MB [[PHIN]]s so we generate [[PseudoPHIN]]s. EPR solves this by using a field ClientGUID, which we get as part of the [[Cognos EPR Report]]. 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. | ||
* The Client GUID is not visible in EPR | |||
=== Concerns === | === Concerns === | ||
==== Data that is entered without a ClientGUID ==== | ==== Data that is entered without a ClientGUID ==== | ||
* Could be a problem: | * Could be a problem: | ||
** Manual entry if we miss an admission and this is identified later past the 28 day of data in COGNOS | ** Manual entry if we miss an admission and this is identified later past the 28 day of data in COGNOS | ||
** [[Definition_of_a_Medicine_Laptop_Admission#Excluded_service_admissions_can_lead_to_missed_records]] | ** [[Definition_of_a_Medicine_Laptop_Admission#Excluded_service_admissions_can_lead_to_missed_records]] | ||
* Not a problem: | * Not a problem: | ||