$TXT Created by BAKKE,ANDREW at DEVCUR.FO-SLC.MED.VA.GOV (KIDS) on Thursday, 06/26/03 at 13:57 ============================================================================= Run Date: JUL 13, 2003 Designation: TIU*1*158 Package : TIU - TEXT INTEGRATION UTILITIES Priority: Mandatory Version : 1 SEQ #148 Status: Released Compliance Date: AUG 14, 2003 ============================================================================= Associated patches: (v)TIU*1*151 <<= must be installed BEFORE `TIU*1*158' Subject: TIU ALERT TOOLS Category: - Routine - Enhancement (Mandatory) - Other Description: ============ This patch provides a new set of Alert Tools that satisfies the following E3Rs: #13527 IDENTIFIED SIGNERS NOT GETTING VIEW ALERTS #16045 2ND ALERT FOR UNSIGNED OR UNCOSIGNED TIU DOCUMENTS #16078 FORWARD UNSIGNED NOTES VA TO SVC CHIEF #17785 ABILITY TO GENERATE ALERT TO 3RD PARTY SIGNER #17784 UNSIGNED DOC ALERT TO COSIGNER WHEN AUTHOR GONE Using the List Manager interface, users can search for documents by STATUS (single, multiple or all), and AUTHOR/DICTATOR, EXPECTED COSIGNER, ATTENDING PHYSICIAN, and ADDITONAL SIGNER* (single, multiple, or all), and REFERENCE DATE (single date or date range) for an user entered individual**. * Additional Signers will only appear if they have NOT signed the document ** The user will be notified if the individual entered as part of the search criteria is inactive or DIUSER'd. All TIU documents will be searched regardless of document class or type; Progress notes, Discharge Summaries, and Interdisciplinary Notes will all be included if they meet the search criteria. Any document will only be listed once even if it meets multiple search criteria. Only documents that match each search category will be included; descendant documents whose parent document matches the search criteria will be listed concurrent with their parent document even if other documents fall in between their REFERENCE DATE. This affects the document display order only; as shown below. Example Display (Date Range 06/21/02-06/30/02): Cnt Patient Document Title Ref Date Status 1 VADER,D _ Discharge Summary 06/21/02 UNSIGNED 2 VADER,D _Addendum to Discharge Summary 06/28/02 UNSIGNED 3 FETT,B MEDICINE NOTE 06/23/02 UNSIGNED If a parent document does NOT meet the search criteria, the descendant will be listed as shown below (Child documents that are NOT addendums will have their title displayed). The only difference is the modified date range. Notice the addendum has been listed AFTER the Medicine Note since it's parent document no longer meets the search criteria. Example Display 2 (Date Range 06/23/02-06/30/02): 1 FETT,B MEDICINE NOTE 06/23/02 UNSIGNED 2 VADER,D Addendum to Discharge Summary 06/28/02 UNSIGNED Once documents have been found and displayed, the user can select a single document (#), multiple documents(#,#,#), range of documents(#-#), or combination (#,#,#-#) of documents. Once a document or documents have been selected, the TIU Alert Tools provide the following alert functions: BROWSE DOCUMENT - If authorized, read only view of selected document. CHANGE VIEW - Allows user to enter new search criteria. COMBINATION ALERTS - Allows users to send new alerts for single or multiple documents to the expected signers (AUTHOR/ DICTATOR, EXPECTED COSIGNER/ATTENDING PHYSICIAN, and ADDITIONAL SIGNER(S)) and one or more third parties. The rules outlined below for RESEND ALERTS apply for a document's expected signers. DELETE ALERTS - Allows users to delete all of the alerts for a single or multiple documents. DETAILED DISPLAY - If authorized, allows the user to view document details. EDIT DOCUMENT - If authorized, allows the user to edit a selected TIU document. IDENTIFY SIGNERS - If authorized, allows the user to edit the expected signers of a TIU document and add/remove additional signers. RESEND ALERTS - Allows users to regenerate alerts for a single document or multiple documents; all alerts associated with each document are deleted before being resent - previously sent 3rd Party Alerts would be deleted and would need to be resent. Alerts are sent appropriate to the document's status and only to expected signers as follows: Author/Dictator & Expected Co-signer/Attending - will only receive alerts if they have not signed. Additional Signer(s) - will only receive alerts if the document has been signed. THIRD PARTY ALERTS* - Allows users to send new alerts for a single document or multiple documents to one or more third parties regardless of the document's status. *All manually generated alerts can be tracked using the ALERT TRACKING (#8992.1) file with the field GENERATED BY (#.05) After installation, the new option entitled TIU Alert Tools [TIU ALERT TOOLS] will be located on the TIU Maintenance Menu [TIU IRM MAINTENANCE MENU] as shown: 1 TIU Parameters Menu ... 2 Document Definitions (Manager) ... 3 User Class Management ... 4 TIU Template Mgmt Functions ... 5 TIU Alert Tools Example Search for ALL TIU Documents by a given user over a date range: Select STATUS: UNSIGNED// ? 1 undictated 5 unsigned 9 purged 2 untranscribed 6 uncosigned 10 deleted 3 unreleased 7 completed 11 retracted 4 unverified 8 amended Enter selection(s) by typing the name(s), number(s), or abbreviation(s). Select STATUS: UNSIGNED// ALL undictated untranscribed unreleased unverified unsigned uncosigned completed amended purged deleted retracted Select SEARCH CATEGORY: AUTHOR// ? 1 Author 3 Expected Cosigner 5 Additional Signer 2 Dictator 4 Attending Physician Enter selection(s) by typing the name(s), number(s), or abbreviation(s). Select SEARCH CATEGORY: AUTHOR// ALL Author Dictator Expected Cosigner Attending Physician Additional Signer Select NEW PERSON: DOE,JOE JD COMPUTER SPECIALIST Start Reference Date [Time]: T-7//1/1/90 (JAN 01, 1990) Ending Reference Date [Time]: Mar 11, 2003// (MAR 11, 2003) Frequently Asked Questions: ========================== 1. My search results by an ADDITIONAL SIGNER and UNSIGNED documents aren't showing any matches but I know they exist. What's wrong? Additional signers are usually added AFTER a document has been signed or co-signed. Add UNCOSIGNED and COMPLETED documents to your search criteria. 2. I want to regenerate alerts for an UNCOSIGNED document, but I don't want the AUTHOR to get alerted. Should I just send a 3rd Party Alert to the EXPECTED COSIGNER? You could, but if you select RESEND ALERTS, the regenerated alerts are context sensitive and sent only to individuals that have NOT signed the document; in this case, only the EXPECTED COSIGNER and any ADDITIONAL SIGNERS that have not signed will be alerted. 3. I selected RESEND ALERTS and my 3rd Party Alerts disappeared! What happened? A document's alerts are deleted before being regenerated so that they remain accurate regarding the document's status; 3rd Party Alerts are deleted as well and must be resent since they are not officially part of the document's record and cannot be automatically regenerated. 4. I changed the ADDITIONAL SIGNER for a document using IDENTIFY SIGNERS, but it didn't update in the display. Why not? Because there can be more than one ADDITIONAL SIGNER, unless the ADDITIONAL SIGNER matches the search criteria, it won't be displayed. 5. I added an ADDITIONAL SIGNER for a document using IDENTIFY SIGNERS, but it didn't update in the display. Why not? See # 4. 6. The AUTHOR of several documents (requiring co-signature) is gone and I want to regenerate the alerts for the EXPECTED COSIGNER so they can SIGN and COSIGN these UNSIGNED documents. Should I use RESEND? It depends. Default alert behavior would be to send the alert AFTER the author has signed and in this case, the EXPECTED COSIGNER would have never received the alerts initially or even after using RESEND. However, with TIU*1*151, a new document parameter was added that could be set so that the EXPECTED COSIGNER could receive the alert IMMEDIATELY; even if the AUTHOR has not signed. This parameter is shown below: ------ SEND COSIGNATURE ALERT: After Author has SIGNED// ? Specify when the alert for cosignature should be sent Choose from: 0 After Author has SIGNED 1 Immediately ------ If you have NOT specifically set this parameter or have it set to "After Author has SIGNED", you'll need to use a 3rd Party Alert to the EXPECTED COSIGNER or change the parameter's setting to "Immediately" before using RESEND. If you HAVE set this parameter to "Immediately", you can use RESEND. 7. I used RESEND ALERT and the EXPECTED COSIGNER didn't get alerted! Why? Two possible reasons. The first, please see #6. The second, the EXPECTED COSIGNER may be inactivated or DIUSER'd. Currently, kernel does not alert these individuals who are inactive or terminated. TIU*1.0*158 will inform the user that an individual entered as a 3rd Party Alert recipient is inactive/DIUSER'd. However, it does not verify every individual attached to a document since this would be too system intensive and time consuming on a batch send of alerts. 8. I used RESEND ALERT and no alerts were resent to anyone, even though it appeared that alerts were being re-generated. Why? While TIU may create and attempt to regenerate the alerts (this will always happen if TIU Alerts attempts to fulfill a user's request), it has no way of actually confirming whether or not kernel will send an alert to an individual associated with a document (See #7). The important rule to remember is that kernel will not actually send alerts to inactivated or terminated users. Additionally, TIU sends alerts based on the current status of the document and whether or not the recipient still needs to sign the document. If an individual has already signed, they should not receive an alert. However, if a user associated with a document has already signed and they are sent a 3RD PARTY ALERT, they will receive another alert. 9. I sent the AUTHOR (who has already signed) a 3RD PARTY ALERT and now they can't process it! What should I do? Just RESEND ALERTs for that document. All alerts will be deleted and regenerated; 3RD PARTY ALERTS that had been manually generated will have to be re-entered (See #3). NOIS Calls Resolved: =================== LEX-0403-41713 Alerts not generated after TIU 151 and 158 loaded Removes the code that halted alerting on an addendum when the parent is not complete. Routine Summary: =============== The following is a list of the routine(s) included in this patch. The second line of each of these routine(s) will look like: ;;1.0;TEXT INTEGRATION UTILITIES;**[patch list]**;Jun 20, 1997 Routine name Before Patch After Patch Patch List ============ ============ =========== ========== TIUAL1 N/A 23722905 158 TIUALFUN N/A 24047690 158 TIUALRT 10633575 10738605 21,84,79,88 58,61,151,158 TIUALSET N/A 9073322 158 Installation Instructions: ========================= This patch may be installed with users on the system; however, it should be installed at a non-peak time to minimize disruption to the users. Installation of this patch should take less than 2 minutes. 1. Use the INSTALL/CHECK MESSAGE option on the Packman Menu. 2. Review your mapped set. If any of the routines listed in this patch are mapped, they should be removed from the mapped set at this time. 3. From the Kernel Installation and Distribution System (KIDS) Menu, select the Installation menu. 4. From the Installation menu, you may elect to use the following options (when prompted for INSTALL NAME, enter TIU*1.0*158): a. Backup a Transport Global b. Compare Transport Global to Current System c. Verify Checksums in Transport Global 5. Use the Install Package(s) option and select the package TIU*1.0*158. 6. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES//', respond NO. 7. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//', respond NO. 8. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//', respond YES, and DISABLE the TIU* Options and Protocols as shown below: 'Enter options you wish to mark as 'Out Of Order':', respond TIU* 'Enter protocols you wish to mark as 'Out Of Order':', respond TIU* 9. When prompted 'Delay Install (Minutes): (0-60): 0//', respond '0'. 10. If routines were unmapped as part of step 2, they should be returned to the mapped set once the installation has run to completion. Routine Information: ==================== Routine Name: - TIUALRT Routine Checksum: Routine Name: - TIUALFUN Routine Checksum: Routine Name: - TIUAL1 Routine Checksum: Routine Name: - TIUALSET Routine Checksum: ============================================================================= User Information: Entered By : BAKKE,ANDREW J Date Entered : JAN 23, 2003 Completed By: HULET,LEE ANN Date Completed: JUL 02, 2003 Released By : GIVENS,DALE S Date Released : JUL 13, 2003 ============================================================================= Packman Mail Message: ===================== $END TXT