source: cprs/branches/tmg-cprs/Server_KIDS/TMG-CPRS-LOOKUP-1.0-2.TXT@ 1245

Last change on this file since 1245 was 656, checked in by Kevin Toppenberg, 15 years ago

Adding patch for Custom CPRS patient Lookup

File size: 7.9 KB
RevLine 
[656]1$TXT Created by TOPPENBERG,KEVIN at FAMILY PHYSICANS OF GREENEVILLE (KIDS) on Thursday, October 29, 2009
2============================================================================
3Run Date: OCT 29,2009 Designation: TMG-CPRS-LOOKUP*1.0*2
4Package : TMG - FAMILY PHYSICANS OF GREENEVILLE Priority: Optional
5Version : 1 SEQ #1 Status: Released
6============================================================================
7
8Associated patches: None
9
10Subject: Patch to support custom lookups in CPRS (does not require TMG-CPRS)
11
12Category:
13 - Routine
14
15Dependancies:
16============
17 This patch provides 1 stand-alone routine. It's only dependancies are Fileman calls,
18 and the original module ORWPT. These should be already installed on every system
19 that currently can utilize CPRS. There are no other TMG patches that need to be
20 installed prior to installing this patch.
21
22 Version 1 (TMG-CPRS-LOOKUP*1.0*1) is not required for the installation of this patch.
23
24License:
25============
26 This patch is copyright 10/29/2009. GNU Lessor General Public License (LGPL) applies.
27
28Authors:
29============
30 Eddie Hagood and Kevin Toppenberg, Greeneville Family Physicians, PC
31
32Description:
33============
34
35 This patch provides for enhanced patient lookup in CPRS, based on date of birth (DOB),
36 partial name lookup (e.g. Smi,Jo for Smith,John etc), or telephone number.
37
38 How to use:
39 1. For DOB Lookup.
40 There are no special selection buttons etc needed in CPRS to use this extra functionality.
41 Where the user would normally type in the patients last name, instead a date of birth can
42 be entered. Examples:
43
44 10/1/67
45 10/01/1967
46 October 1, 1967
47 Oct 1,1967
48
49 Each of the above examples will return a list of patients born on that date.
50
51 2. For Partial Name Lookup.
52 Enter a few letters from the last name, and then a few letters from the
53 first name. A list of matching patients will be returned. Examples:
54
55 Smi,Jo <-- Will find all patients with last name starting with Smi, and first name starting
56 with Jo
57 Cutsha,C <-- E.g. will finds Cutshaws, Cutshalls etc with first name starting with C
58
59 3. For Telephone Numbers.
60 Enter the telephone number, either using parathesis around the area code, hyphens
61 between the sets of numbers, or spaces between the sets of numbers. Examples:
62
63 (555)222-2222
64 555 555 5555
65 555-555-5555
66 (555) 222-2222
67
68 This return results from Residence, Work, and Cell Phone Numbers.
69
70 TECHNICAL DETAILS
71 ==========================
72
73 When retrieving a list of patients based on user input, CPRS calls a remote procedure call (RPC)
74 named ORWPT LIST ALL. This normally points to server code found at LISTALL^ORWPT. In order
75 to customize the functionality, it was necessary to redirect this call to custom code, namely
76 LISTALL^TMGHRPC2. This code handles the special cases shown above, and if not found passes the
77 call on to the original LISTALL^ORWPT.
78
79 The installation process changes the ROUTINE field of the REMOTE PROCEDURE file from ORWPT to
80 TMGHRPC2. If there is an error, or the functionality is unwanted, then this field may be changed
81 back to its original value using Fileman edit functions. That will return one's VistA system to
82 it's original state.
83
84 The code has been developed on a GT.M mumps system. Every attempt was made to use coding
85 techniques that would be cross-platform to Cache'. But the patch has NOT been tested on Cache'.
86
87 INSTALLATION INSTRUCTIONS:
88 ==========================
89 This patch should cause minimal impact on live systems, as it provides only 1 routine,
90 Installation will take less than 1 minute. Users may remain on the system in roll-and-
91 scroll mode.
92
93 NOTE HOWEVER: All CPRS applications should be exited before installing the patch. Otherwise
94 CPRS users will find that the RPC call has been redirected to a routine that does not yet
95 exist in their instance. In GT.M, recompilation of routines etc only occurrs with a client
96 first connects to the server. We are not sure if this behavior applies to Cache' systems. But
97 the safest approach would be to have all users of CPRS exit their applications, and restart after
98 application of the patch.
99
100 Note: the follow instructions were copied from another KIDS install and modified. There may be
101 some discrepancies.
102
103 The following are instructions for those using the Packman method:
104 ------------------------------------------------------------------
105 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu.
106
107 2. Review your mapped set. If any of the routines listed in the
108 ROUTINE SUMMARY section are mapped, they should be removed
109 from the mapped set at this time.
110
111 3. From the Kernel Installation and Distribution System Menu, select
112 the Installation menu.
113
114 4. From this menu, you may elect to use the following options
115 (when prompted for INSTALL NAME, enter TMG-CPRS-LOOKUP*1.0*1:
116 a. Backup a Transport Global
117 b. Compare Transport Global to Current System
118 c. Verify Checksums in Transport Global
119
120 5. Use the Install Package(s) option and select the package TMG-CPRS-LOOKUP*1.0*1
121
122 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//'
123 respond NO.
124
125 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and
126 Protocols? YES//', respond NO.
127
128 8. If routines were unmapped as part of step 2, they should be returned
129 to the mapped set once the installation has run to completion.
130
131 9. (See step 9 below)
132
133 The following are instructions for those loading the patch via Host File System:
134 ---------------------------------------------------------------------------------
135 1. Navigate the menu option path to reach the Kernel Installation and Distribution
136 System Menu. Or, the menu option XPD MAIN may be entered directly.
137
138 2. Next, at the menu displaying:
139 Edits and Distribution ...
140 Utilities ...
141 Installation ... <---------- pick this one.
142
143 3. Next, at the menu displaying the options as below, choose each of the options
144 in a step-by-step fashion, in numerical order (i.e. 1, 2, 3 etc.) Step #1 will
145 prompt the user to enter the file path on the host file system where the source
146 file is stored. The filename to enter is TMG-CPRS-LOOKUP-1.0-1.KIDS, but add the
147 appropriate path. E.g. /tmp/TMG-CPRS-LOOKUP-1.0-1.KIDS
148
149 1 Load a Distribution
150 2 Verify Checksums in Transport Global
151 3 Print Transport Global
152 4 Compare Transport Global to Current System
153 5 Backup a Transport Global
154 6 Install Package(s)
155 Restart Install of Package(s)
156 Unload a Distribution
157
158 4. From this menu, you may elect to use the following options
159 (when prompted for INSTALL NAME, enter TMG-CPRS-LOOKUP*1.0*1
160 a. Backup a Transport Global
161 b. Compare Transport Global to Current System
162 c. Verify Checksums in Transport Global
163
164 5. Use the Install Package(s) option and select the package TMG-CPRS-LOOKUP*1.0*1
165
166 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//'
167 respond NO.
168
169 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and
170 Protocols? YES//', respond NO.
171
172 8. If routines were unmapped as part of step 2, they should be returned
173 to the mapped set once the installation has run to completion.
174
175
176=============================================================================
177User Information:
178Entered By : TOPPENBERG,KEVIN Date Entered : Oct 29,2009
179Completed By: TOPPENBERG,KEVIN Date Completed: Oct 29,2009
180Released By : TOPPENBERG,KEVIN Date Released : Oct 29,2009
181=============================================================================
182
183Packman Mail Message:
184=====================
185
186$END TXT
Note: See TracBrowser for help on using the repository browser.