Re: [Hardhats] Re: Setting up VistA to use non-SSN ID numbers

Thank you! Did you happen to document those places that you had to make changes because it only read the first digits of the SSN? I think that will help those that are not as concerned about the length of the number they want to use because it is within the 9 digits plus hyphens plus P for CPRS (12) but may be willing to make the code changes to accommodate more. But, I think it might be better to just do the work of adopting Medsphere's changes. Maybe the Code Refactoring Group could take that on. -- Nancy Anthracite On Wednesday, February 13, 2013, you wrote: > As far as Jordan's experience with SSN/HRN and National ID, what we did > simply was that we extended the SSN field to hold our 10 digits ID and did > a proof of concept back in 2010, we found out that there should be some > changes related to WV Enhanced lookup (it checks the first 9 digits), we > also had to do a change on BCMA GUI application to show the whole 10 > digits, if you are not worried about the formatting that VistA uses for SSN > (like the dashes) it will work fine, however there were other places that > we found needs to be changed to adapt the new SSN. We also added NationalID > field. Also as the number of patients grows the patient lookup becomes > slower, so instead of searching once you enter the first digit we made to > start searching once you enter the 6th digit but that is a side note but I > thought you might need to know that as you are saying you want 13 digit > number so the population you are talking about is huge. > > For Arabic-based you will face a problem related to direction (rtl and > ltr), if you are enabling Arabic on your windows machine, the digits will > show up in Arabic (or Indic number - Second row in this image > http://upload.wikimedia.org/wikipedia/commons/thumb/2/21/Arabic_numerals-en > .svg/500px-Arabic_numerals-en.svg.png) but will be mis-formatted as the > dashes are English and the numbers are Arabic and it will show numbers > from the end at the beginning and from the beginning at the end like this: > Original: 998-33-11111 will become 11111-998-33, > > We are fixing these issues as we find them and as we discover more and more > from VistA. All the major VistA modules are working fine and are showing > the NID as we want it (10 digits), > > Regards, > > On Tuesday, February 12, 2013 4:26:59 PM UTC+2, Nancy Anthracite wrote: > > As I understand it the length does matter because of the RPCs and some > > other > > reasons I forget. I know that we discussed this issue with retired VA > > CPRS > > programmers and if you change the length, you may have unintended > > consequences. You might not as well, but I would not want to find out > > the hard way. > > > > On Tuesday, February 12, 2013, Kevin Toppenberg wrote: > > > I don't know how Medsphere made the changes, or to which codebase. I > > > suspect it was with OpenCIS. > > > > > > I can say that I am fairly sure that that there only a few places that > > > > that > > > > > CPRS would have to be changed. The SSNum is treated as a string, and > > > > thus > > > > > length doesn't matter. So the issue would be the display of the SSNum. > > > > And > > > > > I think there is only one place (other than reports) that this is > > > displayed. As I mentioned before, TMG-CPRS already has changed the > > > formatting so that there are no longer hyphens inserted. And I think > > > it will handle variable length. > > > > > > Kevin > > > > > > On Monday, February 11, 2013 7:51:09 PM UTC-5, Nancy Anthracite wrote: > > > > One concern I have about adopting this is being sure about what it > > > > does > > > > > > with > > > > CPRS. Do you know if this was done with CPRS, or with OpenCIS? And > > > > as you pointed out, it would involve a lot of code changes. It > > > > might not be easy to > > > > sort out where those are just because you can download the code base. > > > > > > > > On Monday, February 11, 2013, Kevin Toppenberg wrote: > > > > > Rather than re-invent the wheel, I wish someone would port these > > > > > changes over to VistA. > > > > > > > > > > Kevin > > > > > > > > > > On Saturday, February 9, 2013 12:26:15 PM UTC-5, George Timson > > > > wrote: > > > > > > Nancy mentioned this morning that "...Medsphere has a PATIENT > > > > > > File #2, field #21400 named ENTERPRISE PATIENT IDENTIFIER..." > > > > > > This is correct. We invented it when implementing Midland > > > > > > Memorial > > > > Hospital > > > > > > > > in > > > > > > > > 2005-2006. > > > > > > > > > > Field 21400 is set up to allow a variable format. (SSN remains > > > > > > as > > > > > > > > Field > > > > > > > > > > .09). Medsphere also uses the HRN, and an ACCOUNT NUMBER (from > > > > > > Sea Island Systems' "ADT Filer") to identify a particular > > > > > > episode of care. > > > > > > > > > > > > We had to change many places in the code that assumed the 4- or > > > > > > 9- > > > > > > > > digit > > > > > > > > > > patient id in field .09, but we did that, and the modified > > > > > > > > ("OpenVista") > > > > > > > > > > code base has been available for 5 full years open-source. See > > > > > > http://sourceforge.net/projects/openvista/files/OldFiles/. > > > > > > > > > > > > --George Timson
like0

Comments

Task is created

Afsin Ustundag's picture

Thanks Nancy.  I entered a task

http://issues.osehra.org/browse/REF-105

We will take a look at it after some of the current issues are resolved. 

 

 

like0