| DESCRIPTION OF ENHANCEMENTS |
NOIS
cross-reference of each field. The post-INIT will reindex the data
corresponding entry in the Name Components file.
For example, if FIX^XLFNP176 finds a name in the .01 field of the New
Person file stored as:
Name: SMITH,JOHN M D
it assumes M D is a suffix, and changes the name to SMITH,JOHN MD. It also
stores MD in the SUFFIX field (#5) in the Name Components file.
to setup the cross-reference. Some experamental fields from the
How to use:
----------
FIX^XLFNP176 can be run with VISTA users online. However, it is
recommended that it be run during non-peak times.
Run FIX^XLFNP176 from programmer mode:
>D FIX^XLFNP176
development account were send and will be removed. Routine XUINPCH3
The routine need only be run onced to fix the problem.
Customizing the list of problem suffixes checked by FIX^XLFNP176
----------------------------------------------------------------
If you wish to modify the list of problem suffixes checked by XLFNP176,
you can edit the text at line tag LINE^XLFNP176. Replace the list with an
up-arrow (^)-delimited list of suffixes that may occur at the end of the
Names stored in your New Person file.
is just the Post-INIT routine. The discription was changed on other
Blood Bank Team Coordination:
=============================
Clearance - Nov. 2, 2000
Routine Summary
The following routines are included in this patch. The second line of each
of these routines now looks like:
;;8.0;KERNEL;<patchlist>;Jul 10, 1995
fields.
Checksum
Routine Old New 2nd Line
XLFNP176 n/a 9524118 **176**
XUINPCH3 555958 1351290 **115,176**
List of preceding patches: 115
Sites should use CHECK^XTSUMBLD to verify checksums.
=========================================================================
Installation:
The fields being loaded:
>>>Users may remain on the system.
>>>Taskman does not need to be stopped.
1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This
option will load the KIDS package onto your system.
2. The patch has now been loaded into a Transport global on your
system. You now need to use KIDS to install the Transport global.
53.1,53.2,53.3,53.4,53.6,53.7,53.8,54.1
On the KIDS menu, under the 'Installation' menu, use the following
options:
Verify Checksums in Transport Global
Print Transport Global
Compare Transport Global to Current System
Backup a Transport Global
3. Users can remain on the system.
This patch can be queued and installed at any time.
4. On the KIDS menu, under the 'Installation' menu, use the following
option:
Install Package(s) 'XU*8.0*176'
=========
Want KIDS to INHIBIT LOGONs during the install? YES// NO
No Options or Protocols need to be placed out-of-order.
Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO
==
=========================================================================
MIA-0700-30488
NAME STANDARDIZATION: SPACES WITHIN SUFFIXES
NOIS
====
ANN-0800-42960
MAN-0800-12845
Background
==========
The Name Standardization Patch (Kernel Patch XU*8.0*134), which was
released on April 6, 2000, includes a data conversion run as part of the
LEB-0800-20388
Post-Installation of that patch. The data conversion converts all names
stored in the .01 field of the New Person file to standard form. It also
parses each name into its component parts (Given Name, Middle Name, Family
Name, and Suffix), and stores those component parts in the Name Components
file (#20) also released with the patch.
Problem
=======
The data conversion looks for specific suffixes at the end of the name,
DAY-1000-40325
such as MD, PHD, and DDS. However, it was not accounting for suffixes that
contain periods, such as M.D., Ph.D. and D.D.S. When the data conversion
finds a name with a suffix that contains periods the name could be
incorrectly parsed.
For example, suppose the name as stored in the .01 field of the New Person
file before patch XU*8.0*134 was installed was:
Original name: SMITH,JOHN M.D.
SBY-1000-30177
The result after the data conversion would be:
New standardized name: SMITH,JOHN M D
Name components as stored in the Name Components file:
Given: JOHN M.
Middle: D.
Family: SMITH
Suffix:
Note that in the above, the suffix M.D. was not recognized as a suffix.
'M' was considered part of the person's first (given) name, and 'D' was
considered the middle initial.
Solution
========
In order to correct names that were parsed incorrectly by the data
conversion, routine XLFNP176 is included in this patch. The FIX^XLFNP176
entry point loops through the entries in the New Person file and looks for
Patch XU*8*165 unintentionly send all fields in file 200 not just the
names that may have been standardized and parsed incorrectly. It will then
optionally correct the name in the New Person file and the corresponding
name components in the Name Components file.
NOTE: Sites should still install patch XU*8*134. The FIX^XLFNP176 entry
point is designed to run on systems on which the data conversion has
already been run.
FIX^XLFNP176 Description
ones needed for the patch. This patch fixes the problem caused in
========================
This directly mode utility loops through all entries in the New Person
file (#200) and looks in the .01 field for names that end in any of the
following strings (without the single quotes (')):
' M D'
' D D S'
' PH D'
' R N'
' D P M'
the DEA# and VA# fields. The main problem was a change made to the
' D O'
' P A'
' N P'
' C R N A'
' L P N'
If it finds any of the above strings at the end of the name, it assumes
that string is a suffix. It removes the spaces from the suffix and stores
the modified name in the .01 field of the New Person file. It also stores
the suffix (without embedded spaces) in the Suffix field (#5) of the
|
