{"aaData": [["XUSIGNON", "
\nUser |2| has signed on at Device |3|.\n
\n
\n", "
\n
\n\n
\n", "", "
USER SIGNING ON
\n", "", "", "
\nThis bulletin is triggered whenever someone signs on thru 'XUS'\n
\n
\n"], ["XMRDACK", "
\nYour message:\nSubj: |1|\nhas been read by |2|.\n
\n
\n", "
\n
\n\n
\n", "", "
Confirmation of message
\n", "", "", "
\nThis bulletin is used by MailMan to inform the sender of a message\nthat a recipient has read the message.\nThe sender of the message must have set the CONFIRMATION REQUESTED\nflag to ON when the message was created.\n
\n
\n"], ["PRCNEQC3", "
\nThe Equipment Committee has approved Equipment Request,\nTransaction #: |1| for purchase.\n
\n
\n", "
\n
\n\n
\n", "", "
REQUEST APPROVED!
\n", "", "", "
\nThis mail message is sent when the Equipment Committee approves\nthe equipment request and passes it on to become a 2237.\n
\n
\n"], ["PRCNEQC4", "
\nThe Equipment Committee has approved Equipment Request,\nTransaction #: |1| pending funding.  It will\nbe purchased as soon as funding is received.\n
\n
\n", "
\n
\n\n
\n", "", "
REQUEST APPROVED
\n", "", "", "
\nThis message is sent when the Equipment Committee approves the\nequipment request, but no funds are available at this time.\n
\n
\n"], ["PRCNEQFN", "
\nTransaction #: |1|, |2|, should\nbe reviewed for any changes that may need to be made\nprior to creation of a 2237.\n
\n
\n", "
\n
\n\n
\n", "", "
FINAL CMR CONFIRMATION
\n", "", "", "
\nThis message will be sent to the appropriate CMR Official if a NX\ntransaction should be reviewed/edited one more time before a 2237\nis created.  This should be done in those cases where a request\nhas been in the pipeline for a lengthy period of time.\n
\n
\n"], ["PRCNWHSE", "
\nYou have been assigned to pickup the items found on Turn-In\nRequest #: |1|.\n
\n
\n", "
\n
\n\n
\n", "", "
ASSIGNED ITEM PICKUP
\n", "", "", "
\nThis bulletin is to be used to send a message to those persons\npicked by the Warehouse Manager to pickup assigned turn-in\nrequests.\n
\n
\n"], ["PRCHQ 864 NORMAL", "
\n864 Text Message # |3| has arrived from vendor |2| for\nfor RFQ # |1|.\n
\n
\n", "", "", "
864 Text Message has been received for RFQ # |1|
\n", "
\n
\n\n
\n", "", "
\nReporting arrival of 864 Text Message for review.\n
\n
\n"], ["PRCHQ 864 ERROR", "
\nDuring the filing of a 864 Text Message from vendor |3|\n|10|\n|11|\n|12|\n|13|\nfor RFQ # |1| the following error(s) occured:\n|2|\n|4|\n|5|\n|6|\n|7|\n|8|\n|9|\n
\n
\n", "", "", "
Error during filing 864 message for RFQ # |1|
\n", "
\n
\n\n
\n", "", "
\nReporting error during filing of 864 Message from vendor for an RFQ\n
\n
\n"], ["PRCHQ 843 UPDATE VENDOR INFO", "
\n Dun #: |1|                    Vendor Name: |2|\n Socioeconomic Factors\n  Business Size:   |11|\n  Minority Small:  |12|\n  Minority Large:  |13|\n  Woman Small:     |14|\n  Woman Large:     |15|\n  Disadv. Small:   |16|\n  Vietnam Vet:     |17|\n  Section 8(A):    |18|\n Payment Address\n Tax ID: |3|                   Phone #: |4|\n  Addr Name 1:  |19|\n  Addr Name 2:  |20|\n  Line #1:      |21|\n  Line #2:      |22|\n  Line #3:      |23|\n  City:         |24|\n  State         |25|\n  Zip Code:     |26|\n \n Please review this information and determine if the File #440 values for\n Ordering Address\n this vendor need to be updated.\n \n The vendor supplied this information in support of a quote for RFQ\n # |27|.\n  Line #1:   |5|\n  Line #2:   |6|\n  Line #3:   |7|\n  City:      |8|\n  State:     |9|\n  Zip Code:  |10|\n
\n
\n", "", "", "
On 843 Transaction update of vendor info for Dun# |1|
\n", "
\n
\n\n
\n", "", "
\nVendor supplied information updating addresses and socio-economic status\nfor vendor already in file #440.\n
\n
\n"], ["TIU PRN CONVERSION CLEAN", "
\n         *******  CONVERSION COMPLETED  *******\n     NOTES CONVERTED:  |3|\n  \nThe conversion of Progress Notes into Text Integration Utility\n(TIU) has successfully completed.  The Progress Note File \n^GMR(121 should be archived and removed from the system at your\nconvenience.\n   \n  CONVERSION STARTED:  |1|\nCONVERSION COMPLETED:  |2|\n
\n
\n", "
\n
\n\n
\n", "", "
PROGRESS NOTE CONVERSION
\n", "", "", "
\nThis bulletin will be delivered to the user who initiated the\nconversion as a notice that processing has completed without\nerror.\n
\n
\n"], ["TIU PRN CONVERSION ERRORS", "
\n           *******  CONVERSION COMPLETED  *******\nCONVERSION COMPLETED:  |2|\n    \n     NOTES CONVERTED:  |3|\n NOTES NOT CONVERTED:  |4|\n   \n========================================================================\nERRORS:\n|5|\n  \nThe Progress Note conversion has completed.  The following is\na listing of notes that were not converted during the processing.\n   \n            PROGRESS NOTE CONVERSION ERROR REPORT\n            =====================================\n  \n  CONVERSION STARTED:  |1|\n
\n
\n", "
\n
\n\n
\n", "", "
PROGRESS NOTE CONVERSION
\n", "", "", "
\nThis bulletin will be delivered to the mail group indicated in\nresponse to "mail group" question.  If a mail group is not named,\nthe user who initiated the conversion will be sent the bulletin.\nIt contains a listing of notes that could not be converted \nduring processing.\n
\n
\n"], ["TIU DS CONVERSION CLEAN", "
\n           *******  CONVERSION COMPLETED  *******\n SUMMARIES CONVERTED:  |3|\n  \nThe conversion of Discharge Summaries to Text Integration Utility\n(TIU) has successfully completed.  The GMR REPORTS File \n^GMR(128, should be archived and removed from the system at your\nconvenience.\n   \n  CONVERSION STARTED:  |1|\nCONVERSION COMPLETED:  |2|\n
\n
\n", "
\n
\n\n
\n", "", "
DISCHARGE SUMMARY CONVERSION
\n", "", "", "
\nThis bulletin will be delivered to the user who initiated the\nconversion as a notice that processing has completed without\nerror.\n
\n
\n"], ["TIU DS CONVERSION ERRORS", "
\n             *******  CONVERSION COMPLETED  *******\n                     CONVERSION STARTED:  |1|\n                   CONVERSION COMPLETED:  |2|\n    \n                    SUMMARIES CONVERTED:  |3|\n\n                SUMMARIES NOT CONVERTED:  |4|\n                  - MISSING INFORMATION:  |5|\n                  -  NO ADMISSION FOUND:  |6|\n========================================================================\n\n  \nYou may see a list of the records which failed to convert by using the\nM global lister (i.e., ^%G) to examine the ^GMR(128,"CNV","FAIL",DS #, \nsubscript.  The DS # refers to the entry number in file 128.\nThe Discharge Summary conversion has completed.  One or more Summaries\nwere not converted due to missing information, or inability to match\nthe record to an existing admission.\n   \n            DISCHARGE SUMMARY CONVERSION ERROR REPORT\n            =========================================\n  \n
\n
\n", "
\n
\n\n
\n", "", "
DISCHARGE SUMMARY CONVERSION
\n", "", "", ""], ["PRS LAST SAT OT/CT", "
\n|1| worked less than 2 hours of overtime or comptime \n           "Display Employee Pay Period"\n\nIf this period of work is supposed to be abbutted to a tour beginning\nat midnight on Sunday of pay period |3|, then perform the \nfollowing actions in order.\n\n  1.  The timekeeper for T&L unit |4| should update \n      |1|'s tour of duty for pay period |3| through \n      the option, "Enter/Edit Employee Tour of Duty".\n\non the last saturday of pay period |2|.  This work has been \n  2.  Payroll should return |1|'s record to the \n      timekeeper for T&L unit |4| through option,\n      "Return Record to Timekeeper".  \n\n  3.  The supervisor for T&L unit |4| should certify \n      |1|'s record again.\ncalculated as two hours of call back and is included in the 8B string.\nThe work was posted as ending at midnight.  At the time that the \nsupervisor certified this timecard the work ending at midnight was not \nabutted to a tour in the next pay period.\n\nThe pay period can be reviewed through the payroll main menu option.\n\n
\n
\n", "
\n
\n\n
\n", "", "
Call Back OT/CT is being paid
\n", "", "", "
\n  This bulletin is designed to warn payroll when a nurse has worked less\n     1.  OT ends at midnight on the last saturday of the pay period.\n     2.  Sunday tour begins at midnight\n     3.  Overtime is abutted to the Sunday tour\n     4.  OT/CT is less than 2 hours.\n\nthan 2 hours overtime or comptime and is being paid 2 hrs call back. The\nbulletin is only sent when the OT/CT is worked on the last saturday of\nthe pay period and the work is performed up to midnight. call back. \n\n  It is crucial that when timekeepers are posting overtime for nurses \nunder the following conditions that they are sure that the tour of duty \nfor the new pay period is up to date.\n\n
\n
\n"], ["VAFH ADT/HL7 ERROR", "
\n \nAn error has occurred while generating a message/segment for \n|1| for event on |2|, pivot number |3|.\n \nError Message(s):\n
\n
\n", "
\n
\n\n
\n", "", "
ADT/HL7 ERROR BULLETIN
\n", "", "", "
\nBulletin for error messages that occur while generating a message or\nsegment for VAFH PIMS HL7.\n
\n
\n"], ["SCDX INCOMPLETE ENCOUNTER MGMT", "
\n \n
\n
\n", "
\n
\n\n
\n", "", "
|1|
\n", "", "", "
\nBulletin sent at completion of Incomplete Encounter Mgmt report\ngeneration.  Allows single bulletin to be used for multiple\nreports.\n
\n
\n"], ["OOPS CASE", "
\n              ****INFORMATION ONLY***\na. Complete a Report of Accident through the option:\n     Complete/Validate/Sign Accident Report 2162.\n \nb. Inform the injured employee on rights and benefits for completing\n   the CA-1 (Injury) or CA-2 (Illness) Compensation Claims.\n\nThe supervisors on this case are:\n \nSupervisor:           |4|\nSecondary Supervisor: |5| \nAn incident (injury, illness or accident) has occurred.\n \nDate of incident:        |2|\nCase #:                  |3|\nInjury/Illness:          |6|\n  \nThe 1st line supervisor is required to:\n \n
\n
\n", "
\n
\n\n
\n", "", "
ASISTS Case Notification
\n", "", "", "
\nThis bulletin will notify interested parties of the creation\nof a Case.\n
\n
\n"], ["OOPS SAFETY", "
\nA Report of Accident and Illness has been released for your review.\n \n|1|\nDate of Injury/Illness: |2|\nCase# |3|\n
\n
\n", "
\n
\n\n
\n", "", "
Safety Officer Notification
\n", "", "", "
\nThis Bulletin will notify the Safety Officer of cases ready\nfor review.\n
\n
\n"], ["OOPS EMPLOYEE", "
\nA CA-1 or CA-2 for the following incident has been signed by the employee.\n \nDate of Incident: |2|\nCase# |3|\n \nThe Incident Report is ready for review by the supervisor. It must be\ncompleted and filed with the Agency Worker's Compensation office within 2-3 \nworking days.\n
\n
\n", "
\n
\n\n
\n", "", "
Employee Notification to Supervisor
\n", "", "", "
\nThis Bulletin will notify supervisors and union representatives that a\nCA-1 or CA-2 has been signed by an employee.\n
\n
\n"], ["OOPS BILL OF RIGHTS", "
\n \n \n  Entitlements include the option to receive medical treatment by either\n  the VA Employee Health Unit or by your primary care physician.\n \n  You have the right to request union representation.\n \n  For additional information and explanation of your rights and\n  responsibilities, contact your Workers' Compensation\n  Specialist/Coordinator/Manager.\nEMPLOYEES' BILL OF RIGHTS FOR ACCIDENT AND OCCUPATIONAL ILLNESSES\n \n  The Federal Employees' Compensation Act (FECA) describes an employee's\n  rights and entitlements to benefits following a work-related\n  injury or illness.\n \n  You have the right to file a CA-1 (injury) or CA-2 (illness), to apply\n  for compensation.\n
\n
\n", "", "", "
Employee Bill of Rights for Accidents and Occupational Illnesses
\n", "", "", "
\nThe Employee Bill of Rights for Accidents and Occupational Illnesses\n
\n
\n"], ["OOPS SUPERVISOR", "
\nThe supervisor has signed the CA-1 or CA-2 for the following incident:\n \nDate of Incident: |2|\nCase# |3|\n
\n
\n", "
\n
\n\n
\n", "", "
Supervisor has signed CA-1/CA-2
\n", "", "", "
\nThis message is sent to the OOPS UNION mail group when a supervisor signs\na CA-1 or CA-2\n
\n
\n"], ["PRCH GPF", "
\nThe following |1| transaction was not processed\nby |2| and is returned without action\nfor the reason(s) indicated.\n \nTransaction number: |3|   Amount: $|4|\n \n
\n
\n", "
\n
\n\n
\n", "", "
GPF |1| Transaction Return Notification
\n", "", "", "
\nGeneral post fund transaction return from Fiscal bulletin\n
\n
\n"], ["TIU RE-INDEX DOCUMENT FILE", "
\n    *******  RE-INDEXING OF TIU DOCUMENTS COMPLETED  *******\n            UNSIGNED Documents Re-indexed:             |5|\n          UNCOSIGNED Documents Re-indexed:             |6|\n\n          TOTAL # of Documents Re-indexed:            |7|\n                             ELAPSED TIME:        |8|\n                         DOCUMENTS/SECOND:           |9|\n\nNOTE: Not every document in file 8925 will be included in one of these\nindices, so you shouldn't expect agreement between the total # of\ndocuments re-indexed and the total # of entries in the file.\n  \nThe Re-indexing of the TIU DOCUMENTS file (#8925) has successfully\ncompleted.\n   \n                         RE-INDEX STARTED:  |1|\n                       RE-INDEX COMPLETED:  |2|\n\n           COMPLETED Documents Re-indexed:            |4|\n
\n
\n", "
\n
\n\n
\n", "", "
RE-INDEX TIU DOCUMENT FILE
\n", "", "", "
\nThis bulletin will be delivered to the user who initiated the re-indexing\nprocess as a notice that processing has completed without error.\n
\n
\n"], ["OR CONVERSION ERRORS", "
\nThe following |1| protocol(s) were not successfully converted to a new\nentry in the Order Dialog file (#101.41).  Use the CPRS Implementation\nMenu to create dialogs for these protocols, if desired.\n   \nProtocol IEN   Protocol Name\n------------   -------------\n
\n
\n", "
\n
\n\n
\n", "", "
OE/RR Version 3 Protocol File Conversion
\n", "", "", "
\nThis bulletin will be delivered to the user who initiated the Protocol file\nconversion upon its completion.  Listed here will be the protocol entries\nfor which conversion was attempted but not successful; not all protocols\nwill be converted by this process, only those which are currently in use\nvia an active Add Orders menu.\n
\n
\n"], ["OCX POSTINIT COMPLETE", "
\n \n     The Order Check Post Init has completed \n      on |2| by |3|.\n \n   |1|\n \n     Elapsed Time: |4|.\n \n
\n
\n", "
\n
\n\n
\n", "", "
Order Check Postinit Completed
\n", "", "", "
\nBulletin sent to Order Check Expert System Developers\nwhen the OCX package postinits have completed\n
\n
\n"], ["OCX COMPILER RUN", "
\n \n      Elapsed time Logging Mode: |7|\n          Raw Data Logging Mode: |8| \n        Lines of code generated: |9|\n \n      |10|\n  The Order Check routine compiler |11| \n      on |2| by |3|.\n \n       |1|\n \n                   Elapsed time: |4|\n                                 |5|\n           Execution Trace Mode: |6|\n
\n
\n", "
\n
\n\n
\n", "", "
Order Check Compiler Status
\n", "", "", "
\nBulletin sent to Order Check Expert System Developers\nwhen the OCX routine compiler has finished.\n
\n
\n"], ["ORB SURROGATE RECIPIENT", "
\n     |1|\n     |2|\n
\n
\n", "
\n
\n\n
\n", "", "
Surrogate Recipient for OE/RR Notifications/Alerts
\n", "", "", "
\nThis bulletin is used to notify users when they have been identified as the\nsurrogate recipient of another user's OE/RR Notifications/Alerts.  It is\nalso sent when they are removed as the surrogate recipient.\n
\n
\n"], ["XMNEWUSER", "
\nUser |1| has been added to the New Person file.\n
\n
\n", "
\n
\n\n
\n", "", "
NEW USER ADDED TO SYSTEM
\n", "", "", "
\nThis message is  sent whenever a new user is added to \nthe user file\n
\n
\n"], ["RG CIRN DEMOGRAPHIC ISSUES", "
\nAn event has occurred on your system which may require further action.\n \n \n
\n
\n", "", "", "
NOTIFICATION FROM MPI/PD PACKAGE
\n", "", "", ""], ["GMPL DUPLICATE PROBLEMS", "
\nAfter installing patch GMPL*2*12 the background job that cleaned up the \nDuplicates from the file found |1| Duplicate(s) and hid them from view.\n
\n
\n", "
\n
\n\n
\n", "", "
Duplicates from Patient Problem List
\n", "", "", "
\nThis bulletin is sent to the person installing the patch GMPL*2*12. It will \ntell them the number of duplicate problems "HIDDEN" (deleted) from view of\nany user.\n
\n
\n"], ["XM SEND ERR RECIPIENT", "
\nYour message [#|5|]\nSUBJECT: |1|\nwas not delivered to |2|.\nThe error message was:\n\n|3|\n<|4|>\n
\n
\n", "
\n
\n\n
\n", "", "
Message not delivered to recipient
\n", "", "", "
\nThis message is issued by the MailMan network processor when a message\nrecipient has been rejected by the remote node.  The rejection message\nof the remote node is included in the bulletin.\n
\n
\n"], ["XM SEND ERR SERVER MSG", "
\nMessage not delivered to server |1|\nbecause the message was not in the message file (3.9).\n\nTask #|2| has been left for your action.\n
\n
\n", "
\n
\n\n
\n", "", "
XMIT Err: Server Message not found
\n", "", "", "
\nThis bulletin is fired when a task tries to send a message to a server,\nbut the message is not in the Message global.\n
\n
\n"], ["XM SEND ERR REMOTE MSG ID", "
\nMessage #|1| originated from a remote site.\nIt should have a 'remote message id' on node 5, but it doesn't.\nTo prevent duplicate message deliveries, it was not delivered.\n
\n
\n", "
\n
\n\n
\n", "", "
Transmit Error: No Remote Msg ID
\n", "", "", "
\nWhile trying to send a response to a message which originated from a\nremote site, we noticed that the 'remote message id' is missing from\nthe original message.  Without this id, we can't tell the site which\nmessage we are responding to.\n\n'remote message id' is field 9 in file 3.9.\n
\n
\n"], ["XM SEND ERR MSG", "
\nYour message, SUBJECT: |1|\nwas rejected by |2|\n\nThe error message was:\n|3|\n\nIntended recipients were:\n
\n
\n", "
\n
\n\n
\n", "", "
Message not delivered
\n", "", "", "
\nWhen a remote site rejects an entire message for whatever reason\n(too many lines, for example), this bulletin is sent to the message\noriginator.\n
\n
\n"], ["XM FWD ADDRESS DELETE", "
\nYour forwarding address: |1|\nhas been deleted because it is not valid.\nThe error message is:\n|2|\n
\n
\n", "
\n
\n\n
\n", "", "
Forwarding Address Deleted
\n", "", "", "
\nThis bulletin is sent when MailMan notices that a user has an invalid\nforwarding address.  The forwarding address is deleted, and the user\nis notified why.\n
\n
\n"], ["XM GROUP ERROR", "
\nWhile addressing a message to mail group: |1|\nthe following problems were noted:\n
\n
\n", "
\n
\n\n
\n", "", "
Error in Mail Group
\n", "", "", "
\nNotifies selected users of problems with a mail group.\nSuch problems may include:\n- Group contains a circular reference to a group.\n- Local member should not be receiving mail (no access code).\n- Remote member has invalid or ambiguous or closed domain.\n- Distribution list domain is invalid or ambiguous or closed.\n
\n
\n"], ["DG SENSITIVITY REMOVED", "
\nThe level of sensitivity assigned by |1|\nhas been removed from |2|\non |7|.\n \n|3|\n|4|\n \n|5|\n|6|\n
\n
\n", "
\n
\n\n
\n", "", "
Patient Sensitivity Removed
\n", "", "", "
\nBulletin to notify mail group when patient sensitivity is removed.\n
\n
\n"], ["XUTM PROBLEM DEVICES", "
\nThis is the XUTM PROBLEM DEVICE bulletin, it reports devices that TaskMan\nis having problems opening.\nThe list shows the $I value for the device.\n
\n
\n", "", "", "
Problem Devices
\n", "", "", "
\nThis bulletin is used by the XUTMKA routine to report devices that TaskMan\nis having problems opening.\n
\n
\n"], ["MPIF CMOR COMPARE COMPLETE", "
\nCMOR Compare Message Processed.\n
\n
\n", "", "", "
CMOR COMPARE MSG COMPLETED
\n", "", "", "
\nThis bulletin is to alert the install team that the CMOR compare message\nhas been processed on the CMOR site and that X patients had their CMOR\nchanged.  This will assist the team in knowing that these messages have\nbeen processed and how many where changed.\n
\n
\n"], ["XUVISIT", "
\n                 |1|\nThis user has a DUZ of |6| on the authenticating system, and a phone\nnumber of |7|.\n \nThis is the bulletin named XUVISIT.\n \n     A visitor has been added to your New Person File with no Access or\nVerify Codes.\n \n     Name: |2|\n     DUZ: |3|\n \n     This visitor was authenticated at |4|, (|5|).\n
\n
\n", "
\n
\n\n
\n", "", "
A visitor has been added to your New Person File
\n", "", "", "
\n     This is the default XUESSO bulletin which is issued at the time a new\nvisitor is intered in the New Person File.  A "visitor" is a user who has\nbeen validated at another VA site and is entered in you data base so that\nhe or she may look up patient data.\n
\n
\n"], ["DGRU REJECT", "
\n   Patient |1|,    SSN# |2|\n \n   An HL7 |7| event code message sent to the Accu-Max system has been\n   rejected.\n \n      |4|\n \n   Message ID:    |5|\n   Date/Time:     |6|\n
\n
\n", "
\n
\n\n
\n", "", "
RAI/MDS Update Message Reject
\n", "", "", "
\nThis bulletin will handle reject messages from the COTS RAI/MDS system\nand forward the reject notification.\n
\n
\n"], ["DGRU RAI ERROR", "
\n     Patient |1|,\n \n         The following error occurred when the HL7 |2| message\n         to the COTS RAI/MDS system was created or transmitted:\n           |3|\n \n     Entered By  |4|\n     Date/Time   |5|\n
\n
\n", "", "", "
RAI/MDS HL7 MESSAGE ERROR
\n", "", "", "
\nThis will be generated when there is a problem building or sending an\nHL7 message for the RAI/MDS system.\n
\n
\n"], ["DGRU HL7SND", "
\nA |1| HL7 message has been sent to the RAI/MDS COTS system for\n|2| - SSN |5|.\n                 \nMessage Number:    |3|\nMessage Date/Time: |4|\n
\n
\n", "
\n
\n\n
\n", "
NO
\n", "
RAI/MDS Message Transmit to COTS
\n", "", "
7
\n", "
\nNotification bulletin that an HL7 message has been sent to the RAI/MDS\nCOTS system.  \n
\n
\n"], ["XM SUPER SEARCH", "
\n|1| conducted a Super Search of the Message file.\n \nThe criteria used were:\n
\n
\n", "
\n
\n\n
\n", "", "
Super Search Conducted
\n", "", "
90
\n", "
\nEvery time a super search is conducted, this bulletin is sent to alert\nThe ISO should be a member of that group.\n\nSee the XM SUPER SEARCH option for more information.\nthose responsible for ensuring that the capability is not misused.\n\nA super search is a search of the entire Message file based on any number\nof criteria.  All messages are looked at, regardless of who sent them.\n\nThis bulletin reports who performed the search and what criteria were used.\n\nThis bulletin is sent to the mail group XM SUPER SEARCH.\n
\n
\n"], ["XM FILTER FWD ADDRESS DELETE", "
\nYour 'forward to' address: |1|\nhas been deleted from your filter: |2|\nbecause it is not valid.  The error message is:\n|3|\n
\n
\n", "
\n
\n\n
\n", "", "
Filter 'forward to' Address Deleted
\n", "", "
30
\n", "
\nThis bulletin is sent when MailMan notices that a user has an invalid\n'forward to' address in one of the filters.  The 'forward to' address\nis deleted, and the user is notified why.\n
\n
\n"], ["XM DOMAIN ADDED", "
\nThis site has just received an incoming transmission from  \na MailMan patch. \n\nIf you think this domain may be a poorly named VHA domain, \nplease enter a trouble ticket. All new VHA domains should end in \n'.DOMAIN.EXT'.\n'|2|'. Since we have no record of this domain \nin the DOMAIN file 4.2, and did not find '|1|' in the \nINTERNET SUFFIX file 4.2996, we have added '|1|' to the \nDOMAIN file.\n\nIf you think this domain should be added to file 4.2996, \nplease enter a trouble ticket. Only internationally recognized internet \nsuffixes should be added to file 4.2996, and then only via \n
\n
\n", "
\n
\n\n
\n", "", "
New Domain: |1|
\n", "", "", "
\nThis bulletin is sent to alert IRM to the new domain. This shouldn't happen \nvery often, and if it does, the domain name should be investigated. \n\nIf you think that it is a bad name, enter a trouble ticket so it can be investigated. \n\nIf this new top-level domain is a valid internet suffix, it should be\ndeleted from the DOMAIN file and added to file 4.2996, INTERNET SUFFIX,\nand a trouble ticket should be entered for MailMan, so that a patch can be sent\nout to add this top-level domain to file 4.2996 at every site.\n
\n
\n"], ["PRCP_NO_REFILL", "
\nGIP did not get refill information on the following items in order |1|\nto update |2| or |3|.\n \nPlease determine the correct quantities received and enter an emergency\norder to correct the counts in the primary and secondary inventory points.\n
\n
\n", "
\n
\n\n
\n", "", "
Notification of ordered items without a refill amount
\n", "", "
15
\n", "
\nThis bulletin alerts staff that a posted distribution order includes items\nthat were not marked as refilled by the supply station.  It is expected\nthat staff will verify the correct refill amount for these items by\ncreating another order of emergency or call-in to correct discrepancies\nresulting in both the primary and secondary inventory points.\n
\n
\n"], ["XM BANNER MESSAGE", "
\nThe MailMan "banner" for |2| has been changed to read:\n|1||TAB|\n
\n
\n", "
\n
\n\n
\n", "", "
CHANGE IN USER'S 'BANNER' for MAILMAN
\n", "", "", "
\nThis bulletin might be generated when a user changes his banner.\n
\n
\n"], ["PRCP_BAD_ORDER", "
\nAn HL7 item refill/post order transaction on order # |1| for the\nsecondary inventory point, |2|, rejected.\nPlease note the problem and make any corrections.\n
\n
\n", "
\n
\n\n
\n", "", "
Notification of trouble with an HL7 refill transaction
\n", "", "
15
\n", "
\nThis bulletin alerts staff of refill activity that cannot be processed\nbecause the transaction information conflicts with system data or data\nrequirements.\n \nProblems include: item not on the order specified, order not for the\nsecondary specified, amount refilled inappropriate, HL7 transaction\ncorrupted, order number specified is not in GIP\n
\n
\n"], ["PRCP_BAD_ACTIVITY", "
\nAn HL7 utilization transaction for |1| rejected. \n
\n
\n", "
\n
\n\n
\n", "", "
Notification of error in HL7 supply station activity transaction
\n", "", "
15
\n", "
\nThis bulletin alerts staff of problems in HL7 transactions that update\na secondary inventory point with supply station activity.\n \nProblems include: item not on this inventory point, quantity is too large\nor too small, inventory point not in GIP.\n
\n
\n"], ["PRCP_QTY_MISMATCH", "
\nAn on-hand discrepancy with |1| exists for the\nitem |2|.\n \nThe quantity in |1| is |3|\nThe quantity on the supply station is |4|\n \n(Information acquired from HL7 txn# |5|)\n
\n
\n", "
\n
\n\n
\n", "", "
Notification of inventory mismatches between systems
\n", "", "
15
\n", "
\nThis bulletin will notify the secondary inventory staff of inventory\ninconsistencies between the inventory point and its associated supply\nstation.  Staff need to investigate these discrepancies and make the\nnecessary adjustments.\n
\n
\n"], ["PRCP_ALL_ITEMS_QTY_UPDATE", "
\nA supply station QOH response was received for |1|.\n \nPlease investigate any discrepancies listed below.\n \n   Quantities  \n  GIP   SuplSta Item No Description (first 30 chars)   **comments\n------- ------- ------- -----------------------------------------------\n
\n
\n", "
\n
\n\n
\n", "", "
Receipt of QOH response from supply station.
\n", "", "
15
\n", "
\nThis bulletin alerts staff to the receipt to a QOH request.  If any\nquantity discrepancies are found between the items in the supply station\nand those in the inventory point, they will be listed.\n
\n
\n"], ["PRCP_ITEM_NAME", "
\nThere is a name discrepancy in |1| for item# |2|.\n
\n
\n", "
\n
\n\n
\n", "", "
List item name differences between GIP and the Supply Station
\n", "", "
15
\n", "
\nAlerts staff in a secondary inventory point of item name discrepancies\nbetween the invetory point and the linked supply station.\n
\n
\n"], ["PRCP_BAD_QUERY", "
\nA query on hand response for |1| \ncould not be processed.  Please place the request again.\n
\n
\n", "
\n
\n\n
\n", "", "
Notification of rejection of HL7 on-hand transaction
\n", "", "
15
\n", "
\nThis message alerts users when a response to a quantity on hand query\ncould not be processed by GIP.\n
\n
\n"], ["PRCP_BAD_ITEM_QOH", "
\nThe supply station for |1| contains an item not in GIP.\nItem: |2|.\n \n(Information acquired from HL7 txn# |3|)\n
\n
\n", "
\n
\n\n
\n", "", "
Notification of items in a Supply Station not in GIP
\n", "", "
15
\n", "
\nThis item will display when GIP receives a QOH response from the supply\nstation containing an item not in file 441.\n
\n
\n"], ["PRCP_ORDER_NOT_GENERATED", "
\nThe scheduler was unable to generate a distribution order for\n|1| because\n
\n
\n", "
\n
\n\n
\n", "", "
Scheduled Order Not Generated
\n", "", "
30
\n", "
\nThis message alerts staff expecting an order to be autogenerated for an\ninventory point that the order was not generated.\n
\n
\n"], ["XM GROUP EDIT NOTIFY", "
\n|1| added the following users\nas members to mail group '|2|':\n \n
\n
\n", "
\n
\n\n
\n", "", "
Users have been added to your mail group
\n", "", "
30
\n", "
\nThis bulletin is sent to a mail group's organizer and coordinator\nwhenever someone other than themselves adds users to:\n1) a public mail group which doesn't allow users to self-enroll, or\n2) any private mail group.\nThe purpose is to let them know of the change.\n
\n
\n"], ["XM DATE PURGE WARNING", "
\nAttention!  On |1|, all* messages (and their responses)\nSelect MailMan Menu Option: Query/Search for Messages\n                            =\nSelect message search method: M  Search my Mailbox by multiple criteria\n                              =\nSelect search action: Enter 'Subject contains' string// DB  Enter 'Message\nsent on or before' date                                 ==\nMessage sent on or before: |2|\n                           |3|\n\nThis search will find all of your messages which will be deleted.\nsent on or before |2| will be deleted from the system.\n\n* Messages in SHARED,MAIL's mailbox, and messages in the POSTMASTER's\nremote transmit queues and server baskets (includes released patches\non FORUM) are exempt from the purge.\nThey will be gone forever.\n\nYou can find out if this will affect any messages in your mailbox and\ntake appropriate measures.\n\nFrom the main MailMan menu, respond to the prompts as follows:\n\n
\n
\n", "
\n
\n\n
\n", "
YES
\n", "
Date Purge Scheduled for |1|
\n", "", "", "
\nThis is the warning bulletin that is broadcast to all users whenever\noption XMPURGE-BY-DATE is used to purge messages older than a certain\ndate.  See that option for more information.\n
\n
\n"], ["OOPS WC EDITED", "
\nThe Supervisor's signature has been removed from the CA1 for the following\nincident:\n \nDate of Incident: |3|\n          Case #: |2|\n\nThe Worker's Compensation Manager has signed the claim.\n \n
\n
\n", "
\n
\n\n
\n", "", "
Worker's Compensation edited CA1
\n", "", "", "
\nThis is the message that is sent to the Supervisor if the Worker's\nCompensation personnel edited one of the following fields after the\nSupervisor has signed the form:  INJURED PERFORMING DUTY(#146), NOT INJURED\nPERFORMING DUTY (#147), INJURY CAUSED BY EMPLOYEE (#148), INJURY CAUSED BY\nEMPLOYEE EXPLAIN (#149), SUPERVISOR AGREE/DISAGREE (#163), SUPERVISOR NOT\nAGREE EXPLAIN (#164), or REASON FOR CONTROVERTS (#165).\n
\n
\n"], ["OOPS WORKERS COMP", "
\nThe Supervisor signed the CA1/CA2 for the following incident on |4|:\n\nDate of Incident: |3|\n          Case #: |2|\n\nNote to Supervisor:  The CA1/CA2 must be electronically signed by the\n                     employee and supervisor. Then a copy of the CA1/CA2 must \n                     be printed out, hand-signed and dated in blue ink, and \n                     sent to the Worker's Compensation Manager's Office.\n
\n
\n", "
\n
\n\n
\n", "", "
Worker's Comp Notification
\n", "", "", "
\nThis bulletin will be sent to the Workers Comp personnel when the Supervisor\nhas signed the CA1/CA2 claim.\n
\n
\n"], ["OOPS WC SIGNED", "
\nThe Worker's Compensation Manager has signed the CA-1 or CA-2 for\nelectronic transmission to DOL for the following incident:\n \nDate of Incident: |3|\n          Case #: |2|\n\n
\n
\n", "
\n
\n\n
\n", "", "
Worker's Compensation has signed CA-1/CA-2
\n", "", "", "
\nThis message is sent to the Supervisor when a Worker's Compensation Manager\nhas signed a CA-1/CA-2.\n
\n
\n"], ["OOPS SIGNATURE SECURITY", "
\nThis is to notify the Employee, Supervisor, and Workers' Compensation Personnel\n \nthat the Employee portion of a claim has been changed since the Employee \nelectronically signed their portion of the claim.\n\nThe claim WAS NOT transmitted to the AAC.  All electronic signatures have been\nremoved.  The claim must be reviewed, amended as required, and resigned prior \nbeing transmitted to the AAC.\n \nThe affected claim number is: |2|\n
\n
\n", "
\n
\n\n
\n", "", "
Notification of changed Employee data
\n", "", "", "
\nMail bulletin to notify the employee, supervisor, and workers' compensation\npersonnel that data has been altered after the employee has electronically\nsigned their portion of the claim.\n
\n
\n"], ["OOPS WCPBOR", "
\nThe following individual has indicated that they do NOT understand\nthe Employee Bill of Rights and needs assistance from their\nWorker's Compensation Representative.\n \nIndividual: |1|\n
\n
\n", "
\n
\n\n
\n", "", "
Employee understanding Bill of Rights
\n", "", "", "
\nThis bulletin will be sent to the WCP worker if the employee indicates\nthat they do not understand the Bill of Rights when entering a\nCA1 or CA2.\n
\n
\n"], ["OOPS CONSENT", "
\nThe employee has consented to a review of case: |1|.  The following\n         Education: |7|\n   Cost Center/Org: |8|\n        Grade/Step: |9|\n        Supervisor: |10|\n        Sec. Super: |11|\ninformation is provided to the local bargaining unit for review.\n \nDt/Time Occurrance: |2|     \n    Injury/Illness: |3|\n  Personnel Status: |4|\n  Type of Incident: |12|\n               Sex: |5|\n    Station Number: |6|\n
\n
\n", "
\n
\n\n
\n", "", "
Employee Signed CA1 or CA2 with consent
\n", "", "", "
\nThis bulletin will be sent to the Union representatives if the employee\nsigned a consent to release additional incident details to the union.\n
\n
\n"], ["XUMF INSTITUTION", "
\nThe following Master File Notification (MFN) message was\n  UPDATED ENTRY\n  -------------\n  NAME: |5|\n  OFFICIAL VA NAME: |6|\n  FACILITY TYPE: |7|\n  INACTIVE FACILITY FLAG: |11|\n  VISN: |13|\n  PARENT FACILITY: |14|\n  \n  STREET ADDR. 1: |19|\nreceived and processed by the Master File Server:\n  CITY: |20|\n  STATE: |12|\n  ZIP: |22|\n \n  ST. ADDR. 1 (MAILING): |23|\n  CITY (MAILING): |24|\n  STATE (MAILING): |25|\n  ZIP (MAILING): |26|\n \n \n \n  OLD VALUES\n  ----------\n  NAME: |8|\n  OFFICIAL VA NAME: |9|\n  FACILITY TYPE: |10|\n  INACTIVE FACILITY FLAG: |15|\n  VISN: |17|\n  PARENT FACILITY: |18|\n \n  STREET ADDR. 1: |27|\n  HL7 Message ID:  |1|\n  CITY: |28|\n  STATE: |16|\n  ZIP: |29|\n \n  ST. ADDR. 1 (MAILING): |30|\n  CITY (MAILING): |31|\n  STATE (MAILING): |32|\n  ZIP (MAILING): |33|\n  \nThe following INSTITUTION (#4) file entry has been |2|:\n \n  IEN: |3|   STATION NUMBER: |4|\n \n
\n
\n", "
\n
\n\n
\n", "", "
Master File Server - update notification - INSTITUTION file
\n", "
\n
\n\n
\n", "", "
\nThis bulletin notifies the XUMF INSTITUTION\nmail group that an unsolicited update message\nhas been received and processed by the Master\nFile Server mechanism.  An INSTITUTION (#4)\nfile entry has been added/updated.\n
\n
\n"], ["XUMF ERROR", "
\nThe Master File Server has received a Message Acknowledgement (MSA) segment\n \n  HL7, FM, or other message:\n \n|3|\n \n|4|\n \nThis message must be investigated our the master file related to this message\nwill be out of sync with the national standard table.\nwith an Acknowledgement Code indicating an application error for the following\nmessage:\n \n  HL7 Message ID:  |1|\n \n  Server message:\n \n|2|\n
\n
\n", "
\n
\n\n
\n", "", "
Master File Server - error message
\n", "", "", "
\nThis bulletin is triggered upon receipt of a Master File Notification message\nfrom the Master File Server.\n
\n
\n"], ["PRCP_ORDER_PARTIALLY_LOST", "
\nOrder #|1| will not be completed by station, |2|.   \n \nThe items refilled are:\n \nQuantity  Item Number and Description\n--------  -----------------------------------------------------------\nIt has been |3|.\n \nThe supply station already refilled some items.   This may cause\non-hand discrepancies with GIP requiring your attention:\n \n|4|           \n|5|\n|6|\n
\n
\n", "
\n
\n\n
\n", "", "
Partially filled order lost
\n", "", "
15
\n", "
\nThis message will be sent to the secondary inventory point managers when\na supply station has reported refills against a distribution order but\nhas not completed it.  The purpose of the message is to notify staff of\npossible inconsistencies in the on-hand quantity between the supply\nstation and the secondary.\n
\n
\n"], ["EAS MTCOMPLETION", "
\nA Means Test for |1|, SSN(Last4) |2|\nwas completed on |3| by |4|\n
\n
\n", "
\n
\n\n
\n", "", "
MEANS TEST COMPLETION
\n", "", "", "
\nThis bulletin is for sending Means Test completion notices\n
\n
\n"], ["XM FWD ADDRESS CHANGE", "
\nThe new forwarding address for |1| is:\n\n|2|\n
\n
\n", "
\n
\n\n
\n", "", "
New forwarding address for |1|
\n", "", "", "
\nThis bulletin is generated when a user's forwarding address changes.\nIt is meant to be sent to IRM, or anyone with a need to know about\na user's forwarding address.\n
\n
\n"], ["XM SEND ERR TRANSMISSION", "
\nTransmission has failed to |1|\n|2| times with the latest script.\n\nThe following errors occurred in the latest script:\n
\n
\n", "
\n
\n\n
\n", "", "
Transmit Failure to |1|
\n", "", "
30
\n", "
\nThis bulletin is sent when MailMan is unable to transmit to a site\nafter it has tried all the available scripts.\n
\n
\n"], ["XM TOO MANY MESSAGES", "
\nYou have at least |1| messages in your mailbox.\n(|2| in your IN basket)\n\nPlease terminate all of your unnecessary messages.\n\nThank-you.\n
\n
\n", "
\n
\n\n
\n", "
YES
\n", "
Please Terminate Messages
\n", "", "
30
\n", "
\nThis bulletin is sent by option XMMGR-DISK-MANY MESSAGE-MAINT, to ask\nusers to terminate excess messages.\n
\n
\n"], ["XM FWD ADDRESS CHECK", "
\nThis is a test to confirm that the forwarding address\n\n     |2|\n\nbelonging to |1| does not generate an error.\n\nPlease ignore this message.\n
\n
\n", "
\n
\n\n
\n", "", "
Test new forwarding address for |1|
\n", "", "
30
\n", "
\nThis bulletin is sent when a user's forwarding address changes.\nIt is sent to the forwarding address.  If it gets through, fine.\nIf it doesn't, then the sender of the bulletin is notified.  The\nsender is the POSTMASTER.  Field 7.01 in file 4.3 controls whether\nthe message is also sent to the POSTMASTER.\n
\n
\n"], ["XM IN BASKET PURGE WARNING", "
\nYou have not read the following messages in over |1| days.\nMailMan will delete them on |2|, unless they become new\nor you read them or save them to another basket.\n
\n
\n", "
\n
\n\n
\n", "", "
Mailbox Maintenance
\n", "", "", "
\nSent by option XMMGR-IN-BASKET-PURGE\n
\n
\n"], ["XM IN BASKET PURGE REQUEST", "
\nYou have not read the following messages in over |1| days.\nIf you don't need them, consider deleting them.\nMailMan will not delete them.\n
\n
\n", "
\n
\n\n
\n", "", "
Mailbox Maintenance
\n", "", "", "
\nSent by TEST^XMUPIN.\n
\n
\n"], ["XUSSPKI CRL SERVER", "
\nAt |2| The CRL Upload task reported the following problem.\n  "|1|"\n \nBe sure that the "CRLService" is running on the server.  Try stopping and\nrestarting the service. It should be listening on port 10270.\n
\n
\n", "
\n
\n\n
\n", "", "
CRL UPLOAD MESSAGE
\n", "", "", "
\nThis bulletin is sent when the CRL UPLOAD TASK has a problem.\n
\n
\n"], ["OOPS SENSITIVE DATA", "
\nThis is a notification that the following supervisor \n\n\n\n|1|\n\nused the ASISTS software to View sensitive data for the following employee:\n\n|2|  on |3|.\n\nwithout creating an Illness or Injury case. \n
\n
\n", "
\n
\n\n
\n", "", "
ASISTS Employee Sensitive data .
\n", "", "", "
\nBulletin is sent when a supervisor views Employee sensitive data but does not\ncreate an ASISTS case. \n
\n
\n"], ["XM RELAY ATTEMPTED", "
\nA site calling itself |1|\nspam or viruses is to ensure that any mail servers in operation accept\nonly outgoing mail from machines within their own domains.  This prohibits\nSMTP relaying, denying spammers and virus propagators a necessary\ncomponent of anonymity.\nattempted to relay a message\nfrom: |3|\nto:   |2|\nthrough this site.\n\nThis attempt was denied.\n\nBy far the most important thing that a service provider can do to reduce\n
\n
\n", "
\n
\n\n
\n", "", "
Potential SPAM or VIRUS stopped
\n", "", "
7
\n", "
\nThis bulletin is sent when MailMan prevents an outside site from\nrelaying a message to an outside site through this site.\n
\n
\n"], ["OOPS CASE CLOSE NOTIFICATION", "
\nAn ASISTS Case has been closed:\n\n      ASISTS Case Number:  |1|\n          Case Closed By:  |2|\n        Date Case Closed:  |3|\n\n
\n
\n", "
\n
\n\n
\n", "", "
ASISTS CASE CLOSED NOTIFICATION
\n", "", "", "
\nThis bulletin will be sent to the OOPS SAFETY and OOPS WCP mail groups\nwhenever an ASISTS case status is set to 'Closed'.  If the case is opened and\nclosed multiple times, a bulletin will be sent every time.  The Name of the \nperson closing the case is obtained from the DUZ for the user and the Date \nClosed is the system date when the user actually closed the case. New data\nfields HAVE NOT been created for this.  The person who closed the case nor the\nDate Closed is stored.\n
\n
\n"], ["LA7 AMENDED RESULTS RECEIVED", "
\nLaboratory results on the following patient have been received via a HL7\n    File #62.49: |2|\n \n   Patient Name: |3|\n     Patient ID: |4|\n \n    Specimen ID: |5|\n Collection D/T: |6|\n   Test/analyte: |7|\n       Producer: |8|\n  Producer's ID: |9|\ninterface that indicate the results have been amended. Please use the\n                  \n \n     Observation\n     -----------\n          Value: |10|\n          Units: |11|\n      Ref range: |12|\n          Flags: |13|\n \nappropriate laboratory option to amend these results on this system.\n \n  \n Action: |14|\n \n \n      Interface: |1|\n
\n
\n", "", "", "
LAB AMENDED RESULTS RECEIVED
\n", "", "", "
\nMail bulletin created by Laboratory package when processing a LEDI\ninterface type HL7 result (ORU) message which contains laboratory\ntesting results that are flagged as amended.\n
\n
\n"], ["LA7 ORDER STATUS CHANGED", "
\nAn order status change has been received for a patient via a HL7 interface\n    File #62.49: |3|\n \n   Patient Name: |4|\n     Patient ID: |5|\n \n    Specimen ID: |6|\n Collection D/T: |7|\n   Test/analyte: |8|\n  Producer's ID: |9|\n       Manifest: |10|\nthat indicates the order has been changed. Please use the appropriate\n                  \nlaboratory option to update this order on this system.\n \n  \n Action: |1|\n \n \n      Interface: |2|\n
\n
\n", "", "", "
LAB ORDER STATUS CHANGED
\n", "", "", "
\nMail bulletin created by Laboratory package when processing a LEDI\ninterface type HL7 message.\n \nIf an order acknowledgment (ORR) message which contains laboratory test\norder status changes that indicate the order is not correct or cannot\nbe performed/completed.\n \nIf an order result (ORU) message and it indicates that a laboratory\ntest has been added by the reference laboratory to the original order.\n
\n
\n"], ["LA7 UNITS/NORMALS CHANGED", "
\nLaboratory results on the following patient have been received via a HL7\n    Patient Name: |3|\n      Patient ID: |4|\n \n     Specimen ID: |5|\n  Collection D/T: |6|\n    Test/analyte: |7|\n        Producer: |8|\n   Producer's ID: |9|\n        File #60: |10|\n \ninterface that indicate the results have units and/or normals different\n \n      Observation\n      -----------\n           Units: |11|\n       Ref range: |12|\nfrom those specified in the LABORATORY TEST file (#60). Please use the\nappropriate laboratory option to review these units/normals on this system.\n \n \n       Interface: |1|\n     File #62.49: |2|\n \n
\n
\n", "", "", "
REFERENCE LAB UNITS/NORMALS CHANGED
\n", "", "", "
\nMail bulletin created by Laboratory package when processing a LEDI\ninterface type HL7 result (ORU) message which contains laboratory\ntest result units and/or normals different from values specified for\ntest in LABORATORY TEST file (#60) and which are flagged to be used\nfor reference testing purposes.\n
\n
\n"], ["LA7 ABNORMAL RESULTS RECEIVED", "
\nLaboratory results on the following patient have been received via a HL7\n     Patient ID: |4|\n \n    Specimen ID: |5|\n Collection D/T: |6|\n   Test/analyte: |7|\n       Producer: |8|\n  Producer's ID: |9|\n                  \n \n     Observation\ninterface that indicate the results are critical or abnormal. Please use\n     -----------\n          Value: |10|\n          Units: |11|\n      Ref range: |12|\n          Flags: |13|\nthe appropriate laboratory option to review these results on this system.\n \n  \n      Interface: |1|\n    File #62.49: |2|\n \n   Patient Name: |3|\n
\n
\n", "", "", "
LAB ABNORMAL/CRITICAL RESULTS RECEIVED
\n", "", "", "
\nMail bulletin created by Laboratory package when processing a LEDI\ninterface type HL7 result (ORU) message which contains laboratory\ntesting results that are flagged as critical or abnormal.  Values\nthat are critical will always trigger the alert and bulletin. Values\nthat are abnormal low or high will be triggered when site has flagged\nthe corresponding test in AUTO INSTRUMENT file (#62.4), NOTIFY ABNORMAL\nFLAGS field (#22) within the CHEM TEST multiple (#30) for the interface.\n
\n
\n"], ["HDIS XML MSG PROCESS ERROR", "
\nAn error occurred when attempting to process an XML message that was sent\nError(s)\n========\nto an HDIS MailMan Server.  The message was not deleted and left in the \nserver basket.\n \nMessage Number : |1|\nMessage Sender : |2|\nServer Option  : |3|\n \n \n
\n
\n", "
\n
\n\n
\n", "", "
ERROR(S) DURING MESSAGE PROCESSING
\n", "
\n
\n\n
\n", "", "
\nBulletin is generated when a problem processing a received XML encoded \nmessage occurs.\n
\n
\n"], ["HDIS ERRORS", "
\nAn error has occurred at |1|\nOn |2|\nError message: |3|\n
\n
\n", "
\n
\n\n
\n", "
NO
\n", "
HDIS Error has occurred
\n", "
\n
\n\n
\n", "
10
\n", "
\nNotification of an error occurring during HDIS VUID processing.\n
\n
\n"], ["HDIS NOTIFY ERT", "
\nData Standardization VUID processing at |1| (in the |4| account) for file |2| was completed on |3|.\n \nSite needs full file update as soon as possible.\n
\n
\n", "
\n
\n\n
\n", "
YES
\n", "
Site: |5| File: |6| in |4| ready for ERT Update
\n", "
\n
\n\n
\n", "
10
\n", "
\nNotifies ERT mailgroup that site needs file update for specific domain.\n
\n
\n"], ["HDIS NOTIFY HDR", "
\nData Standardization VUID processing at |1| (in the |4| account) for file |2| was\ncompleted on |3|. \n \nFile is ready for activation of HDR Triggers.\n
\n
\n", "
\n
\n\n
\n", "
YES
\n", "
Site: |5|, File: |6| in |4| ready for HDR Triggers
\n", "
\n
\n\n
\n", "
10
\n", "
\nUsed to notify HDR personnel that a file at a specific site is ready\nfor activation of the HDR Triggers.\n
\n
\n"], ["PRCV_AUDIT_FILE_ERROR", "
\nWhile |1|\n \nThe following data pertains to this transaction:\ninvolving an item with DynaMed Doc ID #: |2|,\nthe following error occurred: |3|.\n \nThe DynaMed DOC ID gets saved into the Audit file when a request is \nreceived from DynaMed and a RIL is built. This value is the key used\nto update Due-ins in Dynamed. Therefore \n \nPLEASE INCLUDE APPROPRIATE DYNAMED USERS WHEN RESOLVING THIS ERROR\n
\n
\n", "
\n
\n\n
\n", "", "
ERROR WHILE PROCESSING DYNAMED-RELATED DATA ITEM
\n", "", "", "
\nThis bulletin will be used by processes within the IFCAP-DynaMed \ninterface software to notify Control Point Officials and Control Point \nClerks when an error condition occurs.  The error would occur while\nprocessing a DynaMed-originating item in a RIL, a 2237, or a Purchase\nOrder.\n
\n
\n"], ["OOPS EMPSIGNCA7", "
\nA CA7 has been signed by the employee.\n\nDate of Injury/Illness:  |1|\n           Case Number:  |2|\n \nThis is a reminder to the Workers' Compensation Staff that all CA-7s\nare to be submitted to the OWCP within 5 calendar days from the date \nthe employee signed the form.\n
\n
\n", "
\n
\n\n
\n", "", "
Employee signed CA7
\n", "", "", "
\nThis bulletin is sent to the WC mail group when the employee has successfully\nsigned the CA7.\n
\n
\n"], ["SD API ERROR NOTICE", "
\nThe following error condition was reported:\n|5|\n \nPatient Name    : |1|\nClinic          : |3|\nAppt. Date/Time : |2|\n \nMessage Type: |4|\n \nError:\n
\n
\n", "
\n
\n\n
\n", "", "
SCHEDULING PFSS NOTICE
\n", "", "", "
\nThis bulletin is for posting error conditions that occur during the \nScheduling API or PFSS Event Driver processes.\n
\n
\n"], ["OR DRUG ORDER CANCELLED", "
\nDrug Order Cancelled:\n              |1| (|2|)\nPatient:      |3|\nReason:       Entered In Error\nCancelled By: |4|\n
\n
\n", "
\n
\n\n
\n", "", "
Drug Order Cancelled
\n", "
\n
\n\n
\n", "", ""], ["XUSERDEAC", "
\n \n      User name : |1|\n      Title     : |2|\n      Service   : |3|\n      IEN       : |4|\n      Station # : |5|\n \nwas deactivated on |6|.\n
\n
\n", "
\n
\n\n
\n", "", "
XUSER DEACTIVATION
\n", "
\n
\n\n
\n", "", "
\nThis bulletin will be sent to an assigned mail Group when a user gets \ndeactivated.\n
\n
\n"], ["KMPD ECHO", "
\nThe 'CP Echo Server' [KMPD ECHO] encountered an error.\n \n   Date/Time: |1|\n      Sender: |2|\n Option name: |3|\n     Subject: |4|\n   Message #: |5|\n \n    Comments: |6|\n
\n
\n", "
\n
\n\n
\n", "", "
CP Echo Server Error
\n", "
\n
\n\n
\n", "
1
\n", "
\nThis bulletin is sent to the KMP-CAPMAN mail group when the 'CP Echo \nServer' [KMPD ECHO] encounters an error.\n
\n
\n"], ["SCMC PROVIDER INACTIVATION", "
\nProvider |1|  was inactivated from position |2|\n
\n
\n", "
\n
\n\n
\n", "", "
PCMM PROVIDER AUTOMATICALLY INACTIVATED
\n", "", "", ""], ["TIU ENTERPRISE STANDARD TITLES", "
\n                  *** TIU TITLE DEPLOYMENT COMPLETED ***\n \n  DEPLOYMENT STARTED:  |1|\nDEPLOYMENT COMPLETED:  |2|\n  \nThe VHA Enterprise Standard Title Deployment has completed. The following\nis a listing of titles which were either activated or inactivated by the\ndeployment. If the Clinical Applications Coordinator(s) at your facility \nare not among the recipients of this bulletin, please forward it to them.\n \n                  TITLE DEPLOYMENT STATUS CHANGE REPORT\n                  =====================================\n
\n
\n", "
\n
\n\n
\n", "", "
Enterprise Standard Title Deployment
\n", "
\n
\n\n
\n", "
21
\n", "
\nThis bulletin will be delivered to members of the TIU CAC and XUMF SERVER\nmail groups when a deployment of Enterprise Standard Titles modifies the\nactivation status of one or more Titles.\n
\n
\n"], ["EN NON-SPACE FILE LOC", "
\nA new value has been entered in the NON-SPACE FILE LOCATION field of the \n \nSome sites may choose to respond to this message when the location is \navailable so the requester can update the equipment record.\n \nNON-SPACE FILE LOCATION: |2|\nwas entered for Equipment Entry #: |1|\nby |3| on |4|\nEQUIPMENT INV. (#6914) file because an appropriate selection was not \navailable in the ENG SPACE (#6928) file.\n \nPlease use the Enter New Room Space Data to create an appropriate location\nin the ENG SPACE file.  Once an appropriate location is available, the\nLOCATION field of the equipment should be updated.  The NON-SPACE FILE\nLOCATION field will be automatically deleted when the equipment location\nis changed.\n
\n
\n", "
\n
\n\n
\n", "
NO
\n", "
Non-Space File Location |2|
\n", "", "", "
\nThis bulletin is automatically generated when a value is entered in the \nNON-SPACE FILE LOCATION field of the EQUIPMENT INV. (#6914) file.\n
\n
\n"], ["OOPS INCIDENT OUTCOME REQUIRED", "
\nA new incident has been entered or an existing incident has been\nmodified where the Initial Return to Work Status for the incident\nis "Days Away Work" or "Job Transfer/Restriction".\n \nThe Case Number is: |1|\n \nAn entry in the Classify Incident Outcome option is required to  \nrecord the dates and the incident outcome for this case. \n
\n
\n", "
\n
\n\n
\n", "", "
ASISTS - Incident Outcome Required
\n", "", "", "
\nThis bulletin is sent to the safety group when the response to the\nINITIAL RETURN TO WORK STATUS field is "Days Away Work" or \n"Job Transfer/Restriction". It notifies the Safety officer that\nIncident Outcome information must be entered for this incident.\n
\n
\n"], ["DVBA CAPRI 2507 CANCELLATION", "", "", "", "
CAPRI: Cancellation of 2507 Exams
\n", "", "", "
\nNotifies DVBA C 2507 CANCELLATION group of cancellation of exams and/or\nrequests. There are no parameters needed for this bulletin as all data\nis contained in the text portion of the bulletin.\n
\n
\n"], ["XUSLOCK", "
\nDevice |1| has made |2| bad sign-on attempts \nand has been locked.\nThe device will automatically clear after the Lockout time in the Kernel\nSystem Parameters.\nTo make the device or IP address useable before the lockout time is up\nuse the "CLEAR TERMINAL" or "Release IP lock" option to make the device\navailable again.\nSelect |3| as the device to release.\n
\n
\n", "
\n
\n\n
\n", "", "
DEVICE LOCKED DUE TO BAD SIGN-ONS
\n", "", "", "
\nThis bulletin is triggered when the number of bad sign-ons\ncauses a terminal device or IP address to be "locked out".\n
\n
\n"], ["DVBA CAPRI NEW C&P VETERAN", "", "", "", "
CAPRI: New C&P Veteran Added to Patient File
\n", "", "", "
\nAlerts MAS of new C&P veteran when added to Patient file (#2).\nThere are no parameters needed for this bulletin as all data is contained in\nthe text portion of the bulletin.\n
\n
\n"], ["OR PROBLEM NTRT BULLETIN", "
\n                *** New Problem/Diagnosis Term Request ***\n  \nA New Term Rapid Turnaround (NTRT) mail message has been sent to you \nbecause a user from your facility using the CPRS Problem List application\nhas chosen to request a new term to the Problem List Standard (PLS). The\nProblem List Standard is a pick list of "PROBLEMs" represented in SNOMED\nCT, a clinical terminology, displayed in the Problem Lexicon Search\ndialog.\n  \nPlease review the user requested term and if the term is appropriate for \nthe Problem List domain (e.g. Is a Problem/Diagnosis and NOT an allergy, \n \nmedication, etc.), then submit a NTRT request at the NTRT Request site. If\nthe term needs more clarification, please query the requester for more\ninformation before submitting the request.\n  \nThe Problem List domain steward will review each request and respond to \nyou with the outcome. If the term is approved by the Problem List NTRT\ncommittee it will be added to the Problem List Standard and distributed \nin the upcoming Lexicon Quarterly Code Set update patch. \n \nIf there are questions, please contact this mail group: VHA OI SDD HDS \n       Requested term: |1|  \nNTRT VHAOISDDHDSNTRT@domain.ext\n \nThank-you.\n Date/Time of request: |2| \n    Name of requester: |3| \n              Service: |4| \n             Location: |5| \n              Patient: |6| \n Clinician's Comments: |7| \n
\n
\n", "
\n
\n\n
\n", "", "
NEW PROBLEM/DIAGNOSIS TERM REQUEST
\n", "
\n
\n\n
\n", "", "
\nThis bulletin will be delivered to the OR CACS Mail Group. It informs the\nthe upcoming Lexicon Quarterly Code Set update patch.\n  \nIf the local group does not concur with the request, they should defer \nsubmitting a NTRT Request, and discuss the decision with the requester.\ngroup that a new NTRT Request has been initiated by a Clinician at their\nfacility. Upon receipt, the CACs should discuss the request internally. If\nthe group concurs, they should submit a NTRT request for the new term at\nthe NTRT Request site.\n  \nThe NTRT Terminology Stewards for the Problem List Domain will consider \nthe request, and inform the facility of their decision as to whether the\nnew term should be added to the Problem List Standard and distributed in \n
\n
\n"], ["PSS FDB INTERFACE", "", "", "
YES
\n", "
ORDER CHECK DATABASE DOWN
\n", "", "
3
\n", ""], ["PSS FDB INTERFACE RESTORED", "", "", "
YES
\n", "
ORDER CHECK DATABASE IS BACK UP
\n", "", "
3
\n", ""], ["FBAA SERVER", "
\n                 |1|\nComments: |6|\n   \nThis is the bulletin named FBAA SERVER.\n   \n  \nA request for execution of a server option has been received.\n  \nSender: |2|\nOption name: |3|\nSubject: |4|\nMessage #: |5|\n  \n
\n
\n", "
\n
\n\n
\n", "", "
Fee Server Notification |7|
\n", "", "", "
\nThis bulletin is used by the Fee Basis software to notify users about \nserver request events.\n
\n
\n"], ["XUSSPKI SAN", "
\nThe "Subject Alternative Name" field in New Person File (#200) has been \nchanged or deleted for: |3| \n \nBefore: |1|\n After: |2|    <-- if null, field was deleted!\n
\n
\n", "
\n
\n\n
\n", "", "
\"Subject Alternative Name\" field
\n", "", "", "
\nThis bulletin is sent when the "Subject Alternative Name" field has been \nchanged or deleted. The bulletin is sent to users holding the PSDMGR key.\n
\n
\n"], ["GMPL PROBLEM NTRT BULLETIN", "
\n             *** Unmapped Problem/Diagnosis NTRT Request ***\n \nA New Term Rapid Turnaround (NTRT) mail message has been sent to the NTRT\nProblem List domain steward, and the site coordinator has been copied on \nthe message thread. This is informational only and no work is required by\nthe site coordinator for processing of this request.\n  \nThis request is generated when a user from the listed facility selects a \nvalid SNOMED CT problem/diagnosis from the Extended search button and \nmapped to the ICD code of R69. The term will be mapped to a valid ICD\ncode(s) if appropriate and added to the Problem List Standard (PLS) or to\n \nthe pick list using the initial search. These requests will be\ndistributed in the upcoming Lexicon Quarterly Code Set update patch.\n  \nThank you.\n Selected SNOMED CT term: |1|\n   Selected SNOMED CT ID: |2|\n       Name of requester: |3|\n    Date/Time of request: |4| \n                 Service: |5|\n                Location: |6|\n          Search History: |7|\n
\n
\n", "
\n
\n\n
\n", "", "
UNMAPPED PROBLEM/DIAGNOSIS NTRT REQUEST
\n", "", "", "
\nThis bulletin will be delivered to the G.PROBLEM LIST NTRT Mail Group on\nFORUM.  It informs the group that a user has chosen a term from the \nExtend Search button. The NTRT Problem List domain steward will add the \nterm to the Problem List Standard.\n
\n
\n"], ["EAS BT CLAIMS PROCESSING", "
\n \n \nICN:  |3|    \n \nDFN:  |4|\n \nSTATION NUMBER:  |5|\n \nPrev Category:  |6|\n \nNew Category:  |7|\n \n \nDate of Test:  |8|\n \nIncome Year of Conversion:  |9|\nAn Income Verification Match verified Beneficiary Travel Information has \nbeen uploaded for the following patient.\n \n \nPatient Name:  |1|\n \nLast 4 of SSN:  |2|\n
\n
\n", "
\n
\n\n
\n", "
NO
\n", "
IVM - Beneficiary Travel Financial Indicator UPLOAD FOR |10|
\n", "
\n
\n\n
\n", "
7
\n", "
\nThe VistA System will trigger a BT Bulletin so that the appropriate VistA \nstaff will be notified of a change in the BT Financial Indicator. A \nbulletin will be triggered in VistA and sent to the BT Claims Processing\nmail group when there is a change to the BT Financial Indicator received\nfrom the Enrollment System.\n
\n
\n"], ["UNMATCHED RADIOLOGY PROCEDURE", "
\nA new Radiology Procedure has been marked as having been submitted to NTRT\nLocal IEN: |7|\n|1| days ago and is not yet matched to a Master Radiology Procedure \nFile entry.\nProcedure: |2|\nCPT: |3|\nCreated: |5|\n \nFacility/Facility number: |4|\n \n
\n
\n", "
\n
\n\n
\n", "
NO
\n", "
Unmatched Radiology Procedure
\n", "", "
30
\n", "
\nThis bulletin is posted when an unmatched radiology procedure reaches\nX+days after NTRT is given with new entry and it has not been matched\nto an entry in the MRPF file.\n
\n
\n"], ["DVBA CAPRI REROUTE", "", "", "", "
CAPRI 2507 EXAM REQUEST REJECTED
\n", "", "", "
\nThis message is sent to DVBA C 2507 REROUTE mail group when a 2507 Exam \nRequest is rejected.\n
\n
\n"], ["XUSERDIS", "
\n      User name    : |1|\n      Title        : |2|\n      Service      : |3|\n      IEN          : |4|\n      Station #    : |5|\n  \n  was DISUSERED on |6|.  \n
\n
\n", "
\n
\n\n
\n", "", "
USER DISUSER
\n", "
\n
\n\n
\n", "", "
\nThis bulletin will be sent to an assigned email Group when a\nuser has the DISUSER field set to "YES". \n
\n
\n"], ["PX ICE INTERFACE DOWN", "", "", "
YES
\n", "
ICE INTERFACE DOWN
\n", "", "
3
\n", ""], ["PX ICE INTERFACE RESTORED", "", "", "
YES
\n", "
ICE INTERFACE IS BACK UP
\n", "", "
3
\n", ""], ["XMVALBAD", "
\nvalidation breach to domain |1|.\n
\n
\n", "
\n
\n\n
\n", "", "
Invalid validation number received
\n", "", "", "
\nThis bulletin is fired whenever a remote mailman domain attempts to \nestablish a connection with this domain and the validation numbers\ndo not properly match.  This may indicate a attempted breach of security\nor some other network failure.  In order to re-establish communication with \nthis domain, call the site manager to reset your validation numbers.\n
\n
\n"], ["XM_TRANSMISSION_ERROR", "
\nDuring message delivery, the following error was detected:\n \n
\n
\n", "", "", "
MailMan Error Detected During Message Delivery
\n", "", "", "
\nThis bulletin is fired off when the background delivery process\ndetects an error.  The message or response it is supposed to deliver\ndoes not exist.  We just move on to the next message.\n\nThere are no parameters.  The error text is appended to the bulletin.\n
\n
\n"], ["XDR VERIFIED", "
\n|WRAP|\n|WRAP|\nThe FROM record will be merged to the TO record.  Please resolve any\npackage discrepancies so that the merge may proceed.\nThe following records have been identified as Verified Duplicates\nof the |1| file:\n|NOWRAP|\n \nFrom record DA/DFN: |2|                      To record DA/DFN: |3|\n \n|4|                                       |5|\n \n
\n
\n", "
\n
\n\n
\n", "", "
NOTIFICATION OF VERIFIED DUPLICATES
\n", "", "", "
\nThis bulletin is sent by the Kernel Duplicate Resolution software\nanytime a pair of Potential Duplicates are reviewed and the \noperator determines that the pair are indeed Verified Duplicates.\n \nThis bulletin is sent only if a package merge developer does not\nhave a routine that sends its own customized verified message.\n
\n
\n"], ["XDR MERGED", "
\n|WRAP|\nThe FROM Record has now been merged to the TO Record.\n|NOWRAP|\n \n|6|\nThe following records from the |1| file have been merged.\n|NOWRAP|\n \nFrom record DA/DFN: |2|              To record DA/DFN: |3|\n \n|4|                               |5|\n \n|WRAP|\n
\n
\n", "
\n
\n\n
\n", "", "
NOTIFICATION OF DUPLICATES MERGED
\n", "", "", "
\nThis bulletin is sent by the Kernel Duplicate Resolution\nsoftware when a Verified Duplicate pair are merged together.\n \nThis bulletin is sent only if a package merge developer does not\nhave a routine that sends its own customized merge message.\n
\n
\n"], ["XDR ERROR", "
\n|NOWRAP|\n|WRAP|\n|6|\nThis is to notify you that an error was encountered while trying to\neither check for duplicates or during the early merge process of\nthe |1| file.\n \nFrom DA/DFN: |2|                           To DA/DFN: |3|\n \n|4|                                     |5|\n \n
\n
\n", "
\n
\n\n
\n", "", "
ERROR DURING DUPLICATE CHECKING OR MERGE
\n", "", "", "
\nThis bulletin is sent by the Kernel Duplicate Resolution software\nwhen an error that halts the process is encountered by a background\ntask.  It is only sent if there is a entry in the 'Duplicate Manager\nMail Group' in the Duplicate Resolution file.\n
\n
\n"], ["FHDIREQ", "
\nYou have a |1| request.\nPatient is |3| on ward |4|, room |2|.\n|5|\n
\n
\n", "
\n
\n\n
\n", "", "
Dietetic Consultation Request
\n", "", "", "
\nBulletin Ward Clinician when consult is entered on a\npatient on a ward for which the clinician is responsible.\n
\n
\n"], ["FHDIORD", "
\n|1| on ward |2|, room |5| has been ordered\n|3|\nEffective |4|\n
\n
\n", "
\n
\n\n
\n", "", "
Diet Order
\n", "", "", "
\nBulletin Ward Clinician when 'Bulletinized' Diet Order\nis entered.\n
\n
\n"], ["XUSTIME", "
\n"|2|" attempted to sign on to device |1| with code "|3|",\nbut the device is locked out during the time period |4|.\n
\n
\n", "
\n
\n\n
\n", "", "
SIGN-ON TO A TERMINAL DURING PROHIBITED TIME
\n", "", "", "
\nThis bulletin is triggered by the Sign-on system if the device being\nused has a "PROHIBITED SIGN-ON TIMES" value, and somebody has tried to\nsign on during that prohibited time period.\nthe prohibited time frame.\n
\n
\n"], ["FHDITF", "
\nYou have a Tubefeeding Order for |1|  ( |2| )\non ward |3|, room |4|\n \n|5|\n
\n
\n", "
\n
\n\n
\n", "", "
Tubefeeding Order
\n", "", "", "
\nBulletin to alert Ward Clinician of Tubefeeding Order.\n
\n
\n"], ["FHDIOO", "
\n|6|  Additional Order: |1|\n \n                   |3|, |4|, |2|\n \nComment: |5|\n
\n
\n", "
\n
\n\n
\n", "", "
Additional Order
\n", "", "", "
\nBulletin to alert Ward Clinician of Additional Order.\n
\n
\n"], ["FHDIDIP", "
\n|1| on ward |2|, room |3| has no meal pattern for\n|4|\nEffective |5|\n
\n
\n", "
\n
\n\n
\n", "", "
Meal Pattern
\n", "", "", "
\nBulletin Ward Clinician when a Diet Order has no Meal Pattern.\n
\n
\n"], ["EN NEW EQUIPMENT", "
\nA new equipment record has been added to the AEMS/MERS database.\nThe ENTRY NUMBER is |1|.\nIt was entered by |2|.\nThe MFGR EQUIPMENT NAME is |3|.\nThe EQUIPMENT CATEGORY is |4|.\nThe SERVICE is |5|.\nThe STATION NUMBER is |6|.\n \n|7|\n
\n
\n", "
\n
\n\n
\n", "", "
NEW EQUIPMENT: ENTRY #|1|
\n", "", "", "
\nBulletin to alert users (generally in Engineering and A&MM Services)\nthat a new equipment record has been added to the AEMS/MERS database.\n
\n
\n"], ["OR FLAGGED ORDER", "
\nThe following order has been flagged for clarification:\n   |6|\n   |7|\n \nREASON FOR FLAG:\n|10|\n \n       Patient: |1|                     |2|             |3|\n    Order Date: |4|\n    Start Time: |8|\n     Stop Time: |9|\n        Status: |11|\n \n   |5|\n
\n
\n", "
\n
\n\n
\n", "", "
Order flagged for clarification
\n", "", "", "
\nThis bulletin is used to notify the requestor of an order that one\nof the orders has been flagged and is in need of clarification.\n
\n
\n"], ["DG EMBOSSER", "
\nThis is to inform you that the |1| card for \n|2| was not successfully embossed. It has been placed in hold\nstatus. Please check the embosser to make sure it is on-line and clear\nerror if one exists.\n
\n
\n", "
\n
\n\n
\n", "", "
EMBOSSERS
\n", "", "", "
\n^ALERTS USERS TO UNEMBOSSED CARDS AND TELLS THEM TO CHECK THE EMBOSSERS \n
\n
\n"], ["DG EMBOSSER1", "
\nEmbosser has encountered an ERROR. Please check embosser and clear\nerror.  The data card for |1| was in the process \nof being embossed. It will be completed as soon as error is cleared.\n
\n
\n", "
\n
\n\n
\n", "", "
EMBOSSER ERROR
\n", "", "", "
\nAlerts users to problem with embosser.\n
\n
\n"], ["DG SENSITIVITY", "
\nThe user indicated above has accessed the following sensitive\npatient record:\n \n  Patient Name: |1|\n  SSN         : |2|\n  Option Used : |3|\n  Date/time   : |4| \n
\n
\n", "
\n
\n\n
\n", "", "
Sensitive Patient Record Accessed
\n", "", "", "
\nThis bulletin is sent if the following two conditions are\ntrue:\n  a. The user does not hold the DG SENSITIVITY key and\n  b. the ADT Parameter for SENSITIVITY BULLETIN is set to\n     '1'.\n
\n
\n"], ["XUSECURITY", "
\nUser |1| tried to sign on to device |2|, which has SECURITY code |3|,\nbut |1| has security code '|4|'.  Use ^UTIO to edit the device's\nSECURITY, if necessary.\n
\n
\n", "
\n
\n\n
\n", "", "
SIGN-ON DISALLOWED ON SECURED TERMINAL
\n", "", "", "
\nThis bulletin is sent by the sign-on system if a user uses\na terminal that has 'SECURITY' to sign on, and his 'DUZ(0)'\ncode is not found in the terminal's 'SECURITY' code.\ncode as the FILE MANAGER ACCESS CODE attempts to sign on.\n
\n
\n"], ["DG CONSISTENCY", "
\nI attempted to update inconsistencies for the below indicated patient but\nINITIALLY IDENTIFIED BY:  |4|\nINITIALLY IDENTIFIED ON:  |3|\nwas unable to complete the task because I don't hold the 'DG ELIGIBILITY'\nsecurity key and certain data have been verified already.  Please use the\n'EDIT INCONSISTENT DATA' option to clear up these inconsistencies asap.\n   \nPATIENT NAME:  |1|                            SSN:  |2|\n   \nNOTIFICATION STATUS:  |5|\n    \n
\n
\n", "", "", "
INCONSISTENCY EDIT
\n", "", "", ""], ["DG UNVERIFIED ELIG", "
\n|2|, |3|, has been |4|\nand his/her eligibility has not been verified.\n
\n
\n", "
\n
\n\n
\n", "", "
|1| WITHOUT VERIFIED ELIGIBILITY
\n", "", "", ""], ["PRCF FMS ADJUSTMENTS", "
\nThe FMS conversion CCP message |1|, has been filed.  To generate the\nreports you should D REPORT^PRCFOOR2.\n
\n
\n", "
\n
\n\n
\n", "", "
Bulletin for CCP message
\n", "", "", "
\nThis bulletin is used to notify IRM users that the CCP message has\nbeen filed and the conversion reports are ready to be printed.\n
\n
\n"], ["PRCF_850_BULLETIN", "
\n \n  The message number |1|, for your Outstanding Obligation\n  Report (850), has been processed successfully. Please run\n  option 'Outstanding Obligation Report' (PRCF OUTSTANDING)\n  to print your report. This report is for Fiscal service.\n \n
\n
\n", "
\n
\n\n
\n", "", "
Notification to user of successful completion of OOR message.
\n", "", "", "
\nThis bulletin will notify the user of a successful completion of the\nthe OOR message.\n
\n
\n"], ["PRCF_850_BULLETIN1", "
\n \n  The message number |1| has failed. Please contact IRM.\n \n
\n
\n", "
\n
\n\n
\n", "", "
Unsuccessful processing of OOR message notice.
\n", "", "", "
\nThis bulletin will notify the user of a unsuccessful completion of the\nOOR message processing.\n
\n
\n"], ["PRCVUP", "
\n|1| has been updated by FMS.\n
\n
\n", "
\n
\n\n
\n", "", "
FMS VENDOR FILE UPDATE
\n", "", "", "
\nThis bulletin will notify the FMS mail group that an entry\nin their VENDOR file has been updated by FMS.  They will see\nboth the original data and what has been changed.\n
\n
\n"], ["PRC_IFCAP_CHANGE", "
\nPurchase Order |1| for inventory point |2| has been\nchanged as follows:\n
\n
\n", "
\n
\n\n
\n", "", "
Notification from IFCAP of a CHANGE through an amendment
\n", "", "", "
\nThis bulletin will be used to notify users that there has been\na change to a P.O. to allow updating the inventory point.\n   \nThis bulletin is called from 'PRCHAMYD' routine.\n
\n
\n"], ["PRCOEDI ACKNOWLEDGE", "
\nThis is to let you know that a POA transaction has arrived for site\n|2| on |3| at |4|.  This transaction is for |5|. \n
\n
\n", "
\n
\n\n
\n", "", "
Receipt of a POA transaction created on |1|
\n", "
\n
\n\n
\n", "", "
\nThis is a test bulletin to see:\na.  if any POAs arrive at this ISC.\nb.  if I can create a bulletin properly.\n
\n
\n"], ["PRCA NIGHTLY PROCESS ABORT", "
\nAccounts Receivable Nightly process aborted.  Pointer files corrupted.\n \nNOTICE:   This corruption *MUST* BE CORRECTED ASAP.  Until this is\ncorrected, Patient Statements, interest/admin charges, UB forms, etc.\nwill not take place.\n \n  Following is a summary of the error:\n \n
\n
\n", "", "", "
ABORTION OF ACCOUNTS RECEIVABLE NIGHTLY PROCESS
\n", "", "", "
\nThis bulletin will be sent if the Accounts Receivable Nightly Process\naborts because of corruption of the AR pointer files.\n
\n
\n"], ["GMRA MARK CHART", "
\nThe |6| for the following patient needs to be updated to\nindicate that the following allergy/adverse reaction has been recorded.\n      Patient: |1|\n   Patient ID: |4|\n     Location: |3|\n     Reactant: |2|\n    Mechanism: |5|\n
\n
\n", "
\n
\n\n
\n", "", "
Mark Patient |7|
\n", "", "", "
\nThis bulletin will alert the appropriate users to mark the chart and/or ID\nband for the patient and allergy/adverse reaction specified in the\nbulletin.\n
\n
\n"], ["XUSERTERM", "
\nUSER |1| has been terminated as of |2|\nThe error message was '|3|'.\n
\n
\n", "
\n
\n\n
\n", "", "
USER TERMINATION
\n", "", "", "
\nThis bulletin is issued whenever a message cannot be delivered after the\nSimple Mail Transfer Protocol "DATA" command is issued.  It indicates that\nthat the "Mail From:" and RCPT (recipient) commands were successfully \nissued, but that something in the header of the message was rejected,\nsuch as duplicate message ID.  The error message returned by the remote\nreceiver is included in the bulletin.\n
\n
\n"], ["GMRA VERIFY ALLERGY", "
\nThe following allergy/adverse reaction needs to be verified for the \nfollowing patient:\n   Patient: |1|\n       SSN: |4|\n  Reaction: |2|\n   OBS/HIS: |5|\n  Location: |3|\n
\n
\n", "
\n
\n\n
\n", "", "
ALLERGY/ADVERSE REACTION TO BE VERIFIED
\n", "", "", "
\nThis bulletin will indicate that an allergy/adverse reaction needs to be\nverified.\n
\n
\n"], ["GMRA P&T COMMITTEE FDA", "
\nAn observed drug reaction has been entered.   Please ensure that an FDA\nreport has been filed.\n \n             Patient: |1| |2|\n     Causative Agent: |3|\n         Sign Off By: |4|\n        Sign Off D/T: |5|\n
\n
\n", "
\n
\n\n
\n", "", "
NOTIFICATION OF OBSERVED DRUG REACTION
\n", "", "", "
\nThis bulletin will be issued when an agent is both observed and\na drug and has been signed off.\n
\n
\n"], ["GMRA ENTERED IN ERROR", "
\nThe following reaction has been ENTERED IN ERROR.  Please ensure that the\n   Entered in Error on: |7|\npatient's Chart/ID Band |8|are updated to reflect this change.\n               Patient: |1|\n                   SSN: |2|\n              Reaction: |3|\n              Location: |4|\n            Originator: |5|\n            Originated: |9|\n   Entered in Error by: |6|\n
\n
\n", "
\n
\n\n
\n", "", "
REACTION ENTERED IN ERROR
\n", "", "", "
\nThis bulletin is to be sent to both the verifiers and the chart marking\ngroups so that the reaction can be corrected on the patient record.\n \nIn addition, if the reactant is an observed drug reaction, the\nP&T committee members will also be notified.\n
\n
\n"], ["GMRA SIGNS/SYMPTOMS UPDATE", "
\nThe following reaction has had the Signs/Symptoms changed.  Please\nreview the MEDWatch form if needed.\n             Patient: |1|\n                 SSN: |2|\n            Reaction: |3|\n            Location: |4|\n          Originator: |5|\n
\n
\n", "
\n
\n\n
\n", "", "
P&T REVIEW MEDWATCH FORM
\n", "", "", "
\nThis bulletin is to be set to the P&T committee if a reaction has had\nthe Signs/Symptoms changed at anytime.\n
\n
\n"], ["RT RECORD FOUND", "
\nThe |2|for |1| |9|was found.\n \nFor more information use the 'Record Inquiry' option of the 'Record\nInformation' menu.\n \nThe following is information concerning the finding of the record:\n      - WHO entered the record as FOUND   : |6|\n      - BORROWER who had missing record   : |5|\n      - PHONE #/Physical LOCATION         : |7|\n      - WHEN was the record found         : |3|\n      - STATUS of missing record          : |4|\n      - MOVEMENT attempted when found     : |8|\n
\n
\n", "
\n
\n\n
\n", "", "
Missing |10| has been FOUND
\n", "", "", ""], ["RT ATTEMPT-ON-MISSING-REC", "
\nAn attempt was made to process |1|'s |7|\n \n                       missing |2|.\n \nThe following is information related to the attempt:\n        - WHO made the attempt        : |6|\n        - WHEN was the attempt made   : |3|\n        - What DEVICE was it made on  : |5|\n        - What CPU was it made on     : |8|\n        - Type of MOVEMENT attempted  : |4|\n
\n
\n", "
\n
\n\n
\n", "", "
ATTEMPT TO PROCESS A MISSING RECORD
\n", "", "", ""], ["RT RECORD DELETION", "
\nThe following record has been deleted:\n              Name             : |1|\n              Type of Record   : |2|\n              Volume           : |3|\n              Record Number    : |4|\n              User             : |5|\n              Date/Time        : |6|\n \n
\n
\n", "
\n
\n\n
\n", "", "
Notification of a Deletion of a Record
\n", "", "", ""], ["RT MISSING RECORD", "
\nThe following record has been flagged as missing:\nThank you.\n              Name               : |1|\n              Type of Record     : |2|\n              Volume             : |3|\n              |5|\n \nIf you find this record please call |4| or respond\nto this message.\n \n
\n
\n", "
\n
\n\n
\n", "", "
A |2| has been flagged as MISSING
\n", "", "", ""], ["RT CANCELED REQ", "
\nThe following request has been canceled:\n \n              Name            : |1|\n              Type of Record  : |2|\n              Volume          : |3|\n              Record Number   : |4|\n              Requestor       : |5|\n              Request Number  : |7|\n              Canceled by     : |6|\n
\n
\n", "
\n
\n\n
\n", "", "
Notification of a cancelation of a request.
\n", "", "", "
\nThis bulletin is to notify the users of a request that is canceled.\n
\n
\n"], ["RT REQUEST/NOTICE TRANSFER", "
\n===============================================================================\n       |5|                                                                \n-------------------------------------------------------------------------------\n  5. [CN]  |6|                        [SS]  |7|                     \n-------------------------------------------------------------------------------\n  6. [SN]  |8|                                                       \n-------------------------------------------------------------------------------\n  8. TYPE OF TRANSFER      [|10|] Permanent   [|11|] Temporary          \n-------------------------------------------------------------------------------\n  11. TRANSFER CLAIMS FOLDER   [|12|]                                \n-------------------------------------------------------------------------------\n                 |1|                                                          \n  12a. DATE OF TRANSFER     12b. REC. STAT. NO.     12c. TRF. STA. NO.    \n      |14|         |15|                    |16|\n-------------------------------------------------------------------------------\n  13. OTHER FOLDER TRANSFER\n                               MED      HOSP         X-\n  [|21|] LG  [|22|] PG  [|23|] OPT  [|24|] REC  [|25|] CORRESP  [|26|] RAY\n \n                        COUNSELING/TRAINING\n  [|27|] R&E  [|28|] INS  [|29|] SUBFOLDER  [|30|] SPECIFY\n   SPECIFY:  |300|\n-------------------------------------------------------------------------------\n-------------------------------------------------------------------------------\n  14. REASON FOR TRANSFER OR REMARKS\n       |31|\n       |32|\n-------------------------------------------------------------------------------\n  15. ADJUDICATION ACTION PENDING  [|33|] YES     [|34|] NO\n-------------------------------------------------------------------------------\n  16. FROM (originating office)  |35|\n-------------------------------------------------------------------------------\n  17. DATE   |36|\n                     Station Name            Number      Mail Routing Symbol          \n-------------------------------------------------------------------------------\n  18. CHECK WHEN COPY 2 IS SENT TO TELECOM    [|37|] UNIT\n-------------------------------------------------------------------------------\n|100|     |100A|\n  1a.   |2|\n  1b.   |3|\n  1c.   |4|\n-------------------------------------------------------------------------------\n  4. NAME (Last,First,Middle)                                            \n
\n
\n", "", "", "
BULLETIN FOR THE REQUEST OR NOTICE OF TRANSFER
\n", "", "", "
\nLJFGKL\n
\n
\n"], ["XUS ACCESS CODE VIOLATION", "
\nThe user above tried to assign the ACCESS CODE that\nalready belonged to |1|.\n|1| should change his/her code as soon as possible, since its\nsecrecy has now been compromised.\n
\n
\n", "
\n
\n\n
\n", "", "
A USER HAS SEEN ANOTHER USER'S ACCESS CODE
\n", "", "", "
\nThis bulletin is sent by the Syntax check of the ACCESS CODE field\nof the USER file, whenever someone tries to assign an ACCESS CODE\nthat is already in use for a different USER.\n The bulletin goes to whoever is in the MAIL GROUP, plus the user\nwho tried to input the code.\n
\n
\n"], ["PSX CMOP", "
\n----CMOP message----\n
\n
\n", "", "", "
CMOP BULLETIN
\n", "", "", "
\nThis bulletin is required by the Consolidated Mail Outpatient Pharmacy\nsystem.\n
\n
\n"], ["DVB HINQ RESPONSE", "
\n Processing of the HINQ Suspense file has finished.\n A total of |1| HINQ request(s) have been completed.\n \n |4| returned a successful response.\n \n |3| returned an abbreviated response  |5|\n \n |2| returned an error response.\n \n
\n
\n", "
\n
\n\n
\n", "", "
Processed HINQs
\n", "
\n
\n\n
\n", "", "
\nThis bulletin is used to inform the users of returned HINQs.\n
\n
\n"], ["DVBA C 2507 EXAM READY", "
\n \nreviewed for release to the regional office.\n \nA 2507 request for:\n \n               Name: |1|\n                SSN: |2|\n       Request Date: |3|\n \nhas been completely transcribed and may now be\n
\n
\n", "
\n
\n\n
\n", "", "
C & P Exam Ready for Release
\n", "", "", "
\nAlerts selected personnel that a 2507 exam is ready for release.\n
\n
\n"], ["DVBA C 2507 EXAM REOPENED", "
\n \n \n|6|\nOne or more C&P exams for:\n \n                Name: |1|\n                 SSN: |2|\n        Request date: |3|\nRequest Release Date: |5|\n \nhas been reopened by |4|.\n
\n
\n", "
\n
\n\n
\n", "", "
2507 Exam Reopened |7|
\n", "", "", "
\nAlerts supervisors to a 2507 exam being reopened.\n
\n
\n"], ["DVBA C NEW C&P VETERAN", "
\n \nThe following veteran has been added to the Patient file\nfor Compensation and Pension exam purposes:\n \n Name: |1|\n  SSN: |2|\n \nAdded by: |3| on |4|.\n \n
\n
\n", "
\n
\n\n
\n", "", "
New C&P Veteran Added to Patient File
\n", "", "", "
\nAlerts MAS of new C&P veteran when added to Patient file (#2).\n
\n
\n"], ["DVBA C EDIT ADDRESS", "
\nThe address information for |1|\nwas changed on |2| by |3|.\n \n        Old Permanent Address               Changed Permanent Address\n        ---------------------               -------------------------\n
\n
\n", "
\n
\n\n
\n", "", "
Editing of patient address
\n", "", "", "
\nThis bulletin will contain which patient address got changed by whom and\nwhen.\n
\n
\n"], ["YS PSYCHTEST", "
\nTests and/or interviews were undertaken by |1|.\nThey were initiated by |2| on |3|,\nwith |4| listed as requesting the tests.\n\nTest(s) and/or Interview(s):  |5|\n   |6| |7| |8| |9| |10| |11| |12| |13| |14| |15|\n
\n
\n", "
\n
\n\n
\n", "", "
Surrogate Entry of Tests and Interviews
\n", "", "", "
\nNotifies mental health professionals when someone requests\ntests or interviews in their names.\n
\n
\n"], ["PRSA LV TK", "
\n|1| has requested |2| beginning |3|.\nThat date has already been posted.\n
\n
\n", "
\n
\n\n
\n", "", "
Notify TK of Past Leave Request
\n", "", "", "
\nThis bulletin will notify the timekeeper that a leave request\nhas been entered for a day which has already been posted.\nThe bulletin is not generated if the same type of leave was\nposted for the date.\n
\n
\n"], ["PRS UPDATE CCORG", "
\nAn incomplete record was found while PAID user, |2| was running the\n     Select FILE: COST CENTER/ORGANIZATION\n     Select COST CENTER/ORGANIZATION CODE: |1|\n     CODE:  |1|\n     DESCRIPTION: <enter description here>\n\n|3| report for employee, |4|.  \nThe missing data is a description in the PAID code file for \nthe cost center/organization code |1|.  This needs to be updated.  \nCorrect the problem through the Update PAID Codes option. First enter \nthe code |1| at the COST CENTER/ORGANIZATION CODE prompt.  Then \nupdate the description field.  An example follows.\n\n     Select OPTION NAME: PRSD UPDATE PAID CODES\n
\n
\n", "
\n
\n\n
\n", "", "
Needed update PAID code: Cost Center/Organization
\n", "", "", "
\nThis bulletin is sent when either of the two options, Employee Leave Used and\nEmployee Leave Requested are run from the menu path, T&A Supervisor Menu,\nEmployee Reports, Employee Leave Reports.  The condition that the code for an\nemployees Cost Center/Organization code (field #458 in file 450) does not\nresolve with a human readable description in file 454.1 will cause this \nbulletin to be sent.\n\n\n
\n
\n"], ["PXCA PCE ERROR BULLETIN", "
\nThere were error(s) in processing the encounter for |1|\nat Appointment Date/Time of |2|.\n \nError number |3| was recorded at |4|.\n
\n
\n", "
\n
\n\n
\n", "", "
Error in PCE's processing of data from Data Capture
\n", "", "", "
\nThis bulletin is sent when PCE has error(s) in processing data from ATOY's\nGeneric Interface.\n
\n
\n"], ["XUPROGMODE", "
\nUser # |1| has dropped into programmer mode on device |2| .\n
\n
\n", "
\n
\n\n
\n", "", "
DROPPING INTO PROGRAMMER MODE
\n", "", "", "
\nUser going into progmode message.\n
\n
\n"], ["FBAA PURGE", "
\n|1| has run the Fee Purge data routine. The data was purged on |2|.\nAll payment data which was Finalized prior to |3| was purged. A report\ncontaining all purged data (by veteran name) was created.\n                                                                   \n|4| Outpatient Medical payments were purged.                                          \n|5| Pharmacy payments were purged.                                                                      \n|6| Travel payments were purged.                                                                             \n
\n
\n", "
\n
\n\n
\n", "", "
Fee Payment Data Purged
\n", "", "", "
\nInforms Fee Supervisor(s) when IRM staff executes the Fee Purge routine.\n
\n
\n"], ["FBAA BATCH PURGE", "
\n|1| has run the Fee Batch Number purge routine.  The batches were purged on |2|.  All batches that were finalized prior to |3| were purged.  The total number of batches purged was |4|.\n
\n
\n", "
\n
\n\n
\n", "", "
Fee Batch Numbers Purged
\n", "", "", "
\nInforms Fee Supervisor(s) when the IRM staff executes the Fee Batch\nNumber purge routine.\n
\n
\n"], ["FB INSURANCE CHANGE", "
\nThere appears to be a change of insurance information \nfor |1| with PT.ID of |2|.\nThe explanation of change is as follows:\n \n   |3|\n
\n
\n", "
\n
\n\n
\n", "", "
FEE NOTIFICATION OF INSURANCE CHANGE
\n", "", "", "
\nThis bulletin will be used to notify MCCR that there is a possible\ndiscrepancy found on a patient's insurance information.  Fee Basis\nis not allowed to directly change a patient's insurance information\nthat is the reason for this bulletin.\n
\n
\n"], ["FBAA PURGE TRANSMITTED MRA'S", "
\nThe purge of transmitted MRA's has completed.\n \nTotal Veteran MRA's deleted: |1|.\nTotal Vendor MRA's deleted: |2|.\nTotal IPAC Vendor Agreement MRA's deleted: |3|.\n
\n
\n", "
\n
\n\n
\n", "", "
PURGE OF TRANSMITTED MRA'S
\n", "", "", "
\nBulletin is triggered upon completion of the 'Purge Transmitted MRA's'\noption.\n
\n
\n"], ["RAD/NUC MED EXAM DELETED", "
\nThe following exam has been deleted:\n          1) Patient        : |1|\n          2) SSN            : |2|\n          3) Case Number    : |3|\n          4) Exam Date      : |4|\n          5) Requested Date : |5|\n          6) Imaging Loc    : |6|\n          7) Procedure      : |7|\n
\n
\n", "
\n
\n\n
\n", "", "
Imaging Exam Deleted (|2|)
\n", "", "
0
\n", "
\nThis bulletin is used to notify the radiology supervisor that a radiology\nexam has been deleted and the computer user who did the deletion.\n
\n
\n"], ["RAD/NUC MED REPORT DELETION", "
\nThe report for the exam with the following identification was deleted:\n             1) Patient         : |1|\n             2) Patient SSN     : |2|\n             3) Case Number     : |3|\n             4) Exam Date/Time  : |4|\n             5) Desired Date    : |5|\n             6) Report Status   : |6|\n             7) Imaging Loc     : |7|\n
\n
\n", "
\n
\n\n
\n", "", "
Imaging Report Deleted (|2|)
\n", "", "", "
\nThis bulletin is used to notify a mail group that a radiology report\nhas been deleted.\n
\n
\n"], ["RAD/NUC MED REPORT UNVERIFIED", "
\nThe following verified radiology report has been unverified:\n   9) Imaging Loc          : |9|\n  10) Interpreting Staff   : |10|\n  11) Interpreting Resident: |11|\n   1) Patient              : |1|\n   2) SSN                  : |2|\n   3) Case Number          : |3|\n   4) Exam Date            : |4|\n   5) Desired Date         : |5|\n   6) New Status           : |6|\n   7) Requesting Physician : |7|\n   8) Procedure            : |8|\n
\n
\n", "
\n
\n\n
\n", "", "
Imaging Report Unverified (|2|)
\n", "", "
0
\n", "
\nThis bulletin is used to notify the radiology supervisor that a 'verified'\nradiology report was 'unverified' and the computer user who did the\n'unverifing'.\n
\n
\n"], ["RAD/NUC MED REQUEST CANCELLED", "
\nThe request for exam with the following identification was cancelled:\n          9) User                 : |9|\n          1) Patient              : |1|\n          2) Patient SSN          : |2|\n          3) Procedure            : |3|\n          4) Reason for Study     : |4|\n          5) Date Desired         : |5|\n          6) Requesting Physician : |6|\n          7) Requesting Location  : |7|\n          8) Reason               : |8|\n
\n
\n", "
\n
\n\n
\n", "", "
Imaging Request Cancelled (|2|)
\n", "", "", "
\nThis bulletin is used to notify the 'RA REQUEST CANCELLED' mail group that\na radiology request has been cancelled.\n
\n
\n"], ["RAD/NUC MED REQUEST HELD", "
\nThe request for exam with the following identification was held:\n          9) User                 : |9|\n          1) Patient              : |1|\n          2) Patient SSN          : |2|\n          3) Procedure            : |3|\n          4) Reason for Study     : |4|\n          5) Date Desired         : |5|\n          6) Requesting Physician : |6|\n          7) Requesting Location  : |7|\n          8) Reason               : |8|\n
\n
\n", "
\n
\n\n
\n", "", "
Imaging Request Held (|2|)
\n", "", "", "
\nThis bulletin is used to notify the 'RA REQUEST HELD' mail group that a\nradiology request has been held. \n
\n
\n"], ["XQSERVER", "
\n                 |1|\nComments: |6|\n   \nThis is the bulletin named XQSERVER.\n   \n  \nA request for execution of a server option has been received.\n  \nSender: |2|\nOption name: |3|\nSubject: |4|\nMessage #: |5|\n  \n
\n
\n", "
\n
\n\n
\n", "", "
Server Request Notice
\n", "", "", "
\nThis is the standard, or default, bulletin used by the menu system\nto notify IRM staff and users about server request events.\n
\n
\n"], ["RAD/NUC MED CREDIT FAILURE", "
\nA credit failure occurred for the following:\n      9) Interpreter        : |9|\n     10) Imaging Location   : |10|\n|11|\n|12|\n|14|\n      1) Patient            : |1|\n      2) SSN                : |2|\n      3) Exam Date          : |3|\n      4) Case Number        : |4|\n      5) Procedure          : |5|\n      6) CPT Code           : |6|\n      7) CPT Modifiers      : |7|\n      8) Imaging loc DSS ID : |8|\n
\n
\n", "
\n
\n\n
\n", "", "
Imaging Credit Failure for (|13|)
\n", "", "", "
\nThis bulletin will notify users in the selected mailgroup(s) that\na crediting failure occurred.\n
\n
\n"], ["SCDX AMBCARE TO NPCDB SUMMARY", "
\nTransmission of data to the National Patient Care Database has completed.\n \nPlease review the IEMM Error listing for further details.\n \nA total of |1| Encounters were sent.\nA total of |3| Outpatient Encounters were sent.\nA total of |4| Inpatient Encounters were sent.\n \nA total of |2| Encounters were not sent.\nA total of |5| Outpatient Encounters were not sent. \nA total of |6| Inpatient Encounters were not sent.\n
\n
\n", "
\n
\n\n
\n", "", "
Transmission of data to NPCDB completed
\n", "", "", "
\nBulletin sent at the [un]successful completion of generating workload\ninformation to be transmitted to the National Patient Care Database via\nHL7.\n
\n
\n"], ["ESP UOR COMPLETED", "
\nUOR # |1| has been investigated by |2| and \nis ready to review.  The UOR was entered into the records \nby |3|.\n
\n
\n", "
\n
\n\n
\n", "", "
UOR COMPLETED- READY FOR REVIEW
\n", "", "", "
\nBulletin to Police Supervisors that a UOR has been completed and\nis ready to review.\n
\n
\n"], ["ESP SUPERVISOR REVIEW", "
\nYour offense report, UOR # |1|, has been reviewed and\nadditional information is needed.  Please see me for\nfurther details.\n
\n
\n", "
\n
\n\n
\n", "", "
UOR REVIEWED
\n", "", "", "
\nThis bulletin is sent to an investigating officer when his\nUOR has been reviewed and needs additional information.\n
\n
\n"], ["ESP VACO 48 HR CRITERIA", "
\nUOR # |1| has been input.  This UOR falls within the VACO\n48 hour reporting criteria.\n
\n
\n", "
\n
\n\n
\n", "", "
UOR INPUT
\n", "", "", "
\nBulletin to Chiefs that a UOR input that falls within the VACO 48\nhour reporting criteria.\n
\n
\n"], ["RMPR CANCEL TRANSACTION", "
\nThe above user has cancelled the following Prosthetics transaction.\n \nReference: |1|\n \nInitiator: |2|\n \nCancellation Date: |3|\n \nReason for cancellation: |4|\n
\n
\n", "
\n
\n\n
\n", "", "
PROSTHETICS TRANSACTION CANCELLATION
\n", "", "", "
\nBULLETIN IS SENT TO MAILGROUP RMPR CANCEL TRANSACTION WHEN PROSTHETICS\n CANCELS A TRANSACTION\n
\n
\n"], ["QAM MONITOR TOOL 1", "
\n|3|\nFall outs:   |8|\nSample size: |9|\nCalculated percentage: |10|\n \nDate threshold met: |11|\n \nMonitor code:  |2|\nMonitor title: |4|\n \nTime frame: |5|\nThreshold:  |6|\nMin sample: |7|\n \n
\n
\n", "
\n
\n\n
\n", "", "
|1|: |2|
\n", "", "", "
\nThis bulletin is automatically sent when:\n 1) The threshold is met or exceeded.\n 2) The minimum sample size is met or exceeded.\n 3) The end of the time frame has been reached.\nEach of these conditions may be turned on or off in the QA MONITOR\nfile (#743).\n
\n
\n"], ["QAM MONITOR TOOL 2", "
\n|3|\nFall outs:   |8|\nSample size: |9|\nCalculated percentage: |10|\n \nDate threshold met: |11|\n \nMonitor code:  |2|\nMonitor title: |4|\n \nTime frame:  |5|\nThreshold:   |6|\nAlert level: |7|\n \n
\n
\n", "
\n
\n\n
\n", "", "
|1|: |2|
\n", "", "", "
\nThis bulletin is automatically sent when:\n 1) The threshold is met or exceeded.\n 2) The pre-threshold alert level is met or exceeded.\n 3) The end of the time frame has been reached.\nEach of these conditions may be turned on or off in the QA MONITOR\nfile (#743).\n
\n
\n"], ["XTRMON", "
\nA check of the routines in |3| on |1|\nshowed that |2| routines changed, Here is the list:\n \n
\n
\n", "", "", "
Changes to routines
\n", "", "", "
\nThis bulletin is used by the XTRMON routine to send mail messages\nabout routines that change in the set of routines being tracked.\n
\n
\n"], ["RMPFMESSAGE (ASPS)", "
\nYour ROES transaction file has been updated.\n
\n
\n", "", "", "
REMOTE ORDER ENTRY UPDATE
\n", "", "", "
\nThis bulletin serves as a notification that a ROES update message has been\nloaded for Audiology and Speech Pathology Service.\n
\n
\n"], ["RMPF-FILE-UPDATE", "
\n                 |1|\nComments: |6|\n \n              This is the server bulletin RMPF-FILE-UPDATE\n \nA request for execution of a server option has been recieved.\n \nSender: |2|\nOption name: |3|\nSubject: |4|\nMessage #: |5|\n \n
\n
\n", "
\n
\n\n
\n", "", "
Server Request Notice
\n", "", "", "
\nThis is the bulletin which notifies ROES administrative staff at a station that file updates have been performed at the DDC, and duplicated at the station.\n
\n
\n"], ["RMPFMESSAGE (PSAS)", "
\nYour ROES Order File has been updated.\n
\n
\n", "", "", "
REMOTE ORDER ENTRY UPDATE
\n", "", "", "
\nThis bulletin serves as a notification that a ROES update message has\nbeen loaded for Prosthetic and Sensory Aids Service.\n
\n
\n"], ["PRCNCMR1", "
\nYour Equipment Request, Transaction #: |1| was not\napproved.  Please make any necessary corrections and either\nresubmit or cancel the request.\nExplanation:\n
\n
\n", "
\n
\n\n
\n", "", "
REQUEST NOT APPROVED
\n", "", "", "
\nThis message will be sent to the requestor when the CMR official\ndid not approve an equipment request.\n
\n
\n"], ["PRCNCMR2", "
\nYour Turn-in Request, Transaction # |1| was not approved.\nPlease make any necessary corrections and either resubmit\nor cancel the request.\nExplanation:\n
\n
\n", "
\n
\n\n
\n", "", "
TURN-IN REQUEST NOT APPROVED
\n", "", "", "
\nThis message will be sent when a turn-in request has not been\napproved by the CMR Official.\n
\n
\n"], ["PRCNPPM1", "
\nThe Equipment Request, Transaction #: |1| is being returned\nbecause the line item(s) requested are not considered non-expendable.\nExplanation:\n
\n
\n", "
\n
\n\n
\n", "", "
REQUEST ITEMS NOT NX
\n", "", "", "
\nThis mail message is sent from the Personal Property Manager\n(PPM) if the items are determined to not be non-expendable.\n
\n
\n"], ["PRCNCONC", "
\nYou have been selected to review Equipment Request,\nTransaction #: |1| for your approval/disapproval.  Please\nreview and indicate your decision by |2|.  Thank you.\n
\n
\n", "
\n
\n\n
\n", "", "
CONCURRENCE REQUESTED
\n", "", "", "
\nThis message is sent to those individuals selected to\nreview and concur with the equipment request.\n
\n
\n"], ["PRCNEQC1", "
\nThe Equipment Committee has deferred Equipment Request,\nTransaction #: |1| until a later time.  Please resubmit this\nrequest later.\n
\n
\n", "
\n
\n\n
\n", "", "
REQUEST DEFERRED
\n", "", "", "
\nThis message will be sent if the Equipment Committee defers\nthe equipment request.\n
\n
\n"], ["PRCNEQC2", "
\nThe Equipment Committee has not approved Equipment Request,\nTransaction #: |1|.  Please cancel this request.\nExplanation:\n
\n
\n", "
\n
\n\n
\n", "", "
REQUEST NOT APPROVED
\n", "", "", "
\nThis message will be sent if the Equipment Committee does not\napprove the equipment request.\n
\n
\n"], ["PRCNPPM2", "
\nEquipment Request, Transaction #: |1| did not pass the\nconcurrence process.  Fifty percent or more of the concurring\nofficials did not approve this request.\n
\n
\n", "
\n
\n\n
\n", "", "
CONCURRENCE NOT APPROVED
\n", "", "", "
\nThis message is sent if a majority of concurring officials did\nnot approve the equipment request.\n
\n
\n"]]}