Kevin,
I believe that if you use the FM Reindex option to reindex the B
cross-reference of the .01 field of that ALIAS multiple that you will
get your x-refs back and be just fine.
As you do, I suspect that what happened is that someone reindexed the
B cross-reference of the top level .01 field of the PATIENT file.
When FM reindexes a Regular x-ref, it first kills the whole thing and
then rips through all of the entries to do the [re]set. If so , your
mnemonic x-refs became unintended casualties.
Chuck
On Jul 8, 2006, at 8:11 AM, Kevin Toppenberg wrote:
> For many patients, I have aliases declared for different names. This
> is typically used when a woman gets married and changes her name. It
> has always worked fine to look up their name either way.
>
> Except that has stopped working, I'm not sure when. I look at the
> patient record, and the aliases are still there. So I am assuming
> that one of the cross references has been messed up somehow.
>
> When I look at field 1 (ALIAS) in the PATIENT file, I find that the
> .01 field (ALIAS) has two cross references: ANAM201, which is MUMPS
> type index which the descriptions states has a purpose of keeping the
> name components in sync. This doesn't seem like it would be used for
> lookup.
>
> Then, there is a "B" index of type MNEMONIC. This seem like it would
> be more for the use I am looking for. But I can't tell for sure if
> this is a "B" index for the subfile, or for the entire PATIENT file.
> This is it's set node:
> S:'$D(^DPT("B",$E(X,1,30),DA(1),DA)) ^(DA)=1
>
> So, to me, this looks like it is affecting the "B" index of the entire
> file, and inserting the alias name into the "B" index.
>
> So I look in ^DPT("B",AliasName), and I don't find my entry. This may
> explain why it's not working.
>
> I wonder if the lookup in CPRS is not more sophisticated than a simply
> fileman lookup. This is because CPRS will add the words ALIAS after a
> patient name in the lookup box when appropriate. Either there is
> another way that aliases are looked up, or it does a standard fileman
> lookup, then compares the record to see if it was found by the name or
> whether one of the aliases match.
>
> Anyway, does anyone have any ideas how to get the "B" index recreated
> properly? If I just reindex the file in fileman, I don't think that
> the aliases will be added. And come to think of it, maybe this is
> what I did at some point to break it in the first place. I am able to
> write code to do this manually, but I wonder if there is another way
> that this "should" be done.
>
> Thanks
> Kevin
>
> Using Tomcat but need to do more? Need to support web services,
> security?
> Get stuff done quickly with pre-integrated technology to make your
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?
> cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
