Going in the other direction: I currently work with organizations that are undergoing mergers, which means that patients from 2 organizations (thus with 2 different patient IDs) need to be merged. Is there a mechanism in GNU Health to manage multiple patient IDs?
If that exists, the idea of generating a temporary patient ID and later a definite one could be handled by this possibility of a a single record having multiple IDs. 2014-09-23 17:40 GMT+02:00 ronald munjoma <[email protected]>: > Hi Andrew and Bounmy, > > In some countries and implementations they are talking of a single unique > identifier for life. It will be interesting to find out how Jamaica is > handling this. Here is Zimbabwe there has been talk of a single unique > identifier for life but I do not see it happening any time soon. > > A few articles from the net (Mainly US related): > > http://www.cardiosource.org/Advocacy/Issues/Health-Information-Technology/ACC-Policies-and-Activities/Unique-Patient-Identifier-Principles.aspx > > http://online.wsj.com/news/articles/SB10001424052970204124204577154661814932978 > > http://www.poweryourpractice.com/revenue-cycle-management/patient-identifier-best-practices/ > > http://ncvhs.hhs.gov/app3.htm > > Best and Regards > Ronald Munjoma > > > > On 23 September 2014 17:15, [email protected] > <[email protected]> wrote: >> >> Thanks for the replies on this important issue. >> >> I think that GNU Health >> should, by default, create a temporary patient number e.g. - "TPN-00001" - >> if >> an actual patient number is not entered in the PUID field. >> >> It should then be >> possible to over-ride this temporary number when the correct patient ID >> number >> is known. >> >> Regards >> >> Andrew >> > > > > -- > Best and Regards > Ronald Munjoma > +263 775 625 283, +263 776 444 309
