{"aaData": [["POSTMASTER", "", "", "", "", "", "", "", "", "
\nThis is a complete list of all the verifiers who will need to be sent Other reaction information.\n\n
\nThis mail group is used to transmit the reports generated by the\nAR Data Collector.\n\n
\nThis is a test mail group for the MST status transmission\n\n
\nThis mail group receives summary bulletins from the 'Clinic Appointment\nWaiting Time Extract' distributed in patch SD*5.3*192.\n\n
\nThis mail group should contain person(s) responsible for ensuring\nthe integrity of the Patient Information Management System (PIMS)\ndata. The members of this group will be notified upon login that\nthere are patients awaiting review.\n\n
\nThis is the mail group that will receive notifications of problems that\nCIRN has when interacting with the VISTA HL7 package.\n\n
\nThis is the mail group that is used to send HL7 messags via the MailMan\nprotocol to the MPI in Austin.\n\n
\nThe members of this group will receive mail that there may be a\nproblem with a CIRN Master of Record Requests either from another\nfacility or to another facility.\n\n
\nMPI Exception Messages to be addressed. These messages are all technical\nin nature, involving problems with HL7 messages or conflicts with CMORs or\nICN not found. There normally isn't anything the site can do about these,\nso these messages are sent to a remote mail group. The remote mail group\nG.CIRN EXCEPTION MGT@DOMAIN.EXT gets the messages instead of local\nmembers. If necessary, the remote mail group members will contact the\nsite's personnel for assistance.\n\n
\nThis mail group will be used to notify members of an Enrollment Group Threshold (EGT) setting change.\n\n
\nThis mail group contains the members of the Pharmacy and Therapeutic (P&T) committee. Whenever an agent is signed off the committee will get a message. \n\n
\nMail group used by the SCD hl7 interface to transmit data to the National\nSCD registry\n\n
\nThis mail group will receive PCMM HL7 reject messages from Austin.\n\n
\nRepository for PCMM Primary Care HL7 messages.\nMake Austin a member of this mail group so these HL7 messages\nare transmitted to the NPCD.\n\n
\nMembers of this mail group will receive a message if a user is attempting\nto access a PATIENT (#2) file entry and he/she do not have a social\nsecurity number assigned in the NEW PERSON (#200) file.\n\n
\nThis mail group is used to notify the local site of detailed changes about\nthe patient's Means and Copay Test status changes including hardships.\n\n
\nThis mail group is used to send payment processing information messages.\n\n
\nThis mail group contains users responsible for DSS extracts. A\nmessage is sent to this group upon completion of package extracts.\n\n
\nThis group should contain the individuals who should receive any messages\nregarding the transmission of ASISTS 2162 data to the AAC or from the AAC. \n\n
\nThis mail group will receive messages concerning errors with the results\nfrom the CareVue system.\n\n
\nMAIL GROUP TO RECEIVE WORKLOAD CONFIRMATION MESSAGES FROM AUSTIN.\n\n
\nMail group that will receive any recoverable errors that occur\nwhen using PDX. These errors will generally happen when a PDX\nmessage can not be properly received by the PDX Server or when\na PDX message can not be properly created by the PDX Transmitter.\nThis group will typically consist of the ADPAC(s) and IRM personnel\nresponsible for PDX.\n\n
\nThis mail group will receive confirmation and reject messages from Austin\nfor TOP transmissions.\n\n
\nThis mail group is used to notify the local site that PCMM HL7\nTransmission errors were received from the Austin Automation Center (AAC).\n\n
\nThis mail group will receive HL7 transmission messages for the Resident\nAssessment Instrument / Minimum Data Set - Vendor HL7 Interface\n\n
\nMail group to receive RAI/MDS notifications\n\n
\nThis mail group is sent a bulletin whenever someone conducts a Super\nfor just cause. The more people there are, who are aware that a\nSuper Search has been conducted, the less likely it is that the\ncapability will be abused.\n \nThe site Information Security Officer should be the coordinator of\nthis group.\nSearch using the XM SUPER SEARCH option. The bulletin tells who\nconducted the search and what search criteria were used.\n\nMembers of this mail group should be anyone who ought to be notified\nwhenever a Super Search is conducted. At an absolute minimum, the\nsite ISO and alternate ISO(s) should be members. There should be\nenough responsible members of the group so that a certain level of\ncomfort is achieved that the Super Searches will only be conducted\n\n
\nThis is the mail group for ISMS transactions to IFCAP.\n\n
\nThis is the mail group for FMS transactions to IFCAP.\n\n
\nThis mail group is used to notify A&MM that an amendment is Pending\nFiscal Action for 4 or more days.\n\n
\nMembers of this group are notified whenever an obligation\namount is decreased through use of the "Obligate Data" option.\n \nThis mail group is also used to notify Fiscal when the\ndelivery date has been changed in a Purchase Order by\nA&MM Service.\n \nThis mail group is used to notify Fiscal when an amendment has been\nPending Fiscal Action for 4 or more days.\n\n
\n \n\n
\nMail group that will receive notification of a PDX Request that\nhas been received and requires manual processing. This group\nwill typically consist of users that authorize the release of\npatient data to other facilities.\n\n
\nThis mail group will be used to receive the electronic reception of the\ndaily Purchase Card Bills as well as other daily, monthly or quarterly\nmessages from the vendor bank concerning the Purchase Card Program.\n\n
\nMAIL GROUP FOR Q-PRC RESPONSES FROM AUSTIN, TEXAS.\n\n
\nThis is the mail group for confirmation messages from Q-LOG.\n\n
\nMail group to receive any notification messages on incoming\nweb-based 1010EZ submission entries.\n\n
\nThis mail group contains members from Worker's Compensation. This group will\nreceive notification whenever the Supervisor signs a CA1/CA2 claim.\n\n
\nThis group will receive messages regarding the transmission of CA1/CA2 data to\nthe AAC.\n\n
\nThis mail group receives error messages when a cap tracking transaction\nfrom file 354.71 cannot be transmitted to at least one of the patient's\ntreating facilities for at least 2 days.\n\n
\nThis mail group receives messages related to the Master File Server.\n\n
\nThis mail group notifies members of update messages received from the Master\nFile Server related to the INSTITUTION (#4) file.\n\n
\nMail group that will receive notification when an Unsolicited\nPDX has been received. This group will typically consist of\nusers that receive patient data from other facilities.\n\n
\nMail group to send messages regarding accessing images on offline\njukebox platters.\n\n
\nMail group to manage Image activity messages.\n\n
\nThis mail group receives incoming messages, acknowledgements, and notifications\nfrom the HEC on the Veteran Site Extract merge at the HEC.\n\n
\nIf defined, members of this mail group will receive the messages which\ncontain the raw data sent to Austin as a part of the Clinic Wait Time\nextract. It facilitates the occasional monotoring of this process if\nindicated.\n \nThis mail group should not normally have members defined. The presence of\ndefined members will result in extract messages being stored in the local\nMESSAGE (#3.9) file. Storage of these messages locally will not occur if\nthere are no local recipients.\n\n
\nIf the patient ID filter blocks an incoming data request because it\ndetected possible invalid health summary data, a warning is sent to\nmembers of this group.\n\n
\nThis mail group has been established to receive messages from HEC\nregarding veterans Means Test Signature status. \n\n
\n This mail group is accessed to determine who should be notified by the\n Drug Accountability software when an items price or NDC has changed.\n\n
\n This mail group contains the personnel who are to receive the message\n generated for the drugs whose stock level has fallen below the reorder\n level. Previously, anyone holding the PSA ORDERS key would receive this\n message.\n\n
\nMembers of this mail group will be used to receive the ASI Case Finder Report.\n\n
\nThis is a mail group that receives the prosthetics PCE messages.\n\n
\nThis mail group will be used to deliver messages regarding Inter-facility\nConsult errors due to unknown patients.\n\n
\nThe members of this mail group will receive Kernel alerts when \nInter-facility consult transactions fail for reasons most likely due to \nimproper setup or implementation.\n\n
\nThe members of this mail group will receive Kernel alerts when \nInter-facility consult transactions fail due to technical problems with \nnetwork connectivity or VistA HL7. \n\n
\nThis mail group will receive error and confirmation messages dealing with\nEDI transmissions and return messages for IB.\n\n
\nThe members of this mail group will be the recipients of mail messages\ncontaining reports that cannot be divided by claim or batch that are sent by\nthe clearinghouse for EDI.\n\n
\nMail group for EAS automated Means Test letters statistics and reports\n\n
\nMembers of this mail group will receive notifications related to the\nAustin web-based Missing Patient Register application.\n\n
\nThe members of this mail group receive messages during the ClaimsManager\nMultiple Claim send option when bills have ClaimsManager errors.\n\n
\nThe members of this mail group receive messages when there is a \ncommunication failure between the ClaimsManager server and VistA.\n\n
\nThis mail group receives incoming messages, acknowledgements, and notifications\nfrom the HEC on the Veteran Site MPI seeding at the HEC.\n\n
\nThis mail group will receive messages when LTC care is provided to a \npatient and the patient has no 1010EC information on file.\n\n
\nThis mail group will receive messages when a patient has a change of LTC \ncare (new, edit, deletion) that is after monthly LTC processing has \noccurred. The message indicates that there is a possible LTC Back\nBilling issue.\n\n
\nThis mailgroup was created by patch TIU*1*146. It must remain. It was \ncreated as a mechanism to update key staff when patient safety-related \ninformation is distributed. The name must not change as it is used by \nthe National Center for Patient Safety when distributing some \ninformational bulletins.\n\n
\nThis is the mail group that will receive messages from the HUI event of \nchanges either to New Person record for a Provider or if the Provider key \nis allocated or de-allocated.\n\n
\nRepository for PCMM Primary Care Workload HL7 messages.\nMake Austin a member of this mail group so these HL7 messages\nare transmitted to the NPCD.\n\n
\nFIM COORDINATORS Mail Group.\n\n
\nThis mail group is used for the transmission of FIM data to the FSOD database\nin Austin. No members need to be in this group. The mail group should\nhave REMOTE MEMBER: XXX@Q-FIM.DOMAIN.EXT which should have been present\nwhen it was created by the install.\n\n
\nThis mail group may be used in the future for better communication between\nFacility System and the Austin System in regards to ACK or ERR status.\n\n
\nUsed to alert users of problems encountered with the Prescription Practices Utilities.\n\n
\nThis is the mail used by the HL7 MailMan logical link for sending out the\nHL7 PMU messages to support the Office of Academic Affiliations' Clinical\nTrainee Core Data Set project.\n\n
\nThis mail group is for the Radiology Performance Indicator Summary report.\n\n
\nThis mail group gets messages about problems with the communicating with\nthe CRL server.\n\n
\nThis Mail Group is used to Notify responsible users that there has been\na problem with sending information to the Contingency Workstation.\n\n
\nWhen the OAAA HL7 messages are generated a message is generated with the \nnumber of records that are transmitted to the OAA national database.\n\n
\nThis is the default mail group for receiving Patient Record Flag \nAssignment Review notifications.\n\n
\nThis mail group is used to notify Patient Record Flag administrators of \ntransmission errors that occur during the processing of HL7 messages.\n\n
\nThis mail group will be used to deliver notifications for\nthe Insurance Verification process.\n\n
\nThis mail group will be used to send information about the status of ICD9 \ncodes attached to problems on problem selection lists.\n\n
\nThis mail group will be used to define the recipients of a mail message \ncontaining a list of quick orders from the ORDER DIALOG (#101.41) file \nthat are affected by an ICD-9 code set version installation.\n\n
\nPopupulate this mail group with the ISO staff who should receive notification\nwhen a supervisor accesses Employee data but does not create a claim.\n\n
\nThis is the mail group that will receive most of the bulletins produced \nby the 3rd Party EDI Lockbox process in VistA.\n\n
\nThis is the mail group for 3rd Part EDI Lockbox processing that will \nreceive the bulletins regarding the transfer of EOBs to another site.\n\n
\nThis is the mail queue that will receive all the EDI 3rd Party Lockbox\ntransmissions from Austin.\n\n
\nThis is the mail group that will receive the bulletins produced by the\n3rd Party EDI Lockbox process that relate to exceptions found when the EFT\nand ERA messages are received in VistA.\n\n
\nThe mail group will receive DG ALL ADDRESS CHANGE REPORT\n\n
\nEach site must determine the IB/Pharmacy staff members/responsibility \nfor researching and canceling Rx charges. These staff members must\nbe included in this e-mail group in order to receive the MailMan\nmessages\n\n
\nMail group to receive PAIT HL7 messages\n\n
\nMembers of this mail group will receive weekly mail messages regarding\nthe HL7 transmission of the Transitional Pharmacy Benefit data.\n\n
\nMail group for local receipt of Performance Measure access extracts.\n\n
\nWhen adding a new allergy entry the user is prompted for the reactant. \nIf the user cannot find a reactant to match their input then they are \ngiven the option to send an email message requesting that the new \nreactant be added.\n \nMembers of this mail group will be recipients of that message.\n\n
\nThis mail group will receive the IVM Address Updates Pending Review [IVM \nADDR UPDT PENDING REVIEW] report.\n\n
\nMail group used for transmission of Encounter Performance Monitor summary \ndata to Austin Automation Center. DO NOT USE THIS MAIL GROUP FOR OTHER \nPURPOSES.\n\n
\nThis mail group is used to notify local staff of completion for the\nextraction and transmission of the Additional Performance Monitor (TIU)\nNational Rollup to Austin Automation Center (AAC) for National Reporting.\nThis process is queued to run on the 15th of each month and transmits data\nfor the previous month starting with the first day and ending with the\nlast day of the month. The menu option used to run this option is\n'Schedule APM Performance Monitor TasK' [SCRPW APM TASK JOB] and it is\nscheduled via TASKMAN.\n\n
\nPrimary Mail Group for Medical Device errors.\n\n
\nThis group is setup to provide a place to send unprocessed alerts if \nthere is no other mechanism by which to reach a recipient. If other \nmechanisms, such as BACKUP REVIEWER entries in the PARAMETER file, are \navailable, alerts will not be sent to this group. This group will only \nbe used if all other mechanisms result in no active users to send the \nalert to.\n\n
\nReceive's Project Planning messages from the Regional Construction Database\n\n
\nThis mail group will recieve automatic notification via alert if taskman\nis running when the classification or manhour AMIS acuity batch jobs are\nnot run to completion.\n\n
\nThis mail group will receive all FTP error messages for the CBO\nAR Data Extracts.\n\n
\nNew Test que for HIPAA EDI Enhancements\n\n
\nThis mail group will receive Means Test error messages from integrated billing.\nerrors and the editing/deletion of records which are associated with\nMeans Test/Category C billing.\n\n
\nThis mail group is used to send messages for IHD Query to Austin Automation \nCenter.\n\n
\nUsed to recieve ACK messages from Austin for the IHD Query project\n\n
\nThis mail group contains users responsible for DSS extracts. A message is\nsent to this group upon completion of package extracts. \n\n
\nThis mail group will automatically alert UR persons that entries\nare ready for/or received transmition.\n\n
\nThis mail group contains the persons who will receive mail message\nreports from the D&PPM monthly background job.\n\n
\nThis mail group receives messages related to the Master File Server.\n\n
\nExchange mailgroup which will receive the ERT bulletins identifying \nsite ready for ERT file update.\n\n
\nUsed to notify HDR personnel that a file at a facility is ready to\nhave the HDR Triggers turned on.\n\n
\nThis mail group will be used to alert staff who maintain the Item Master \nFile and Vendor File when an error occurs during attempts to update the \nCOTS inventory system.\n\n
\nThis mail group will be used to alert staff of inconsistencies or \nproblems IFCAP finds with the Audit File while processing RILs, 2237s and \nPurchase Orders.\n\n
\nThis mail group is used by the DG SENSITIVE RCDS RPT-FORMAT and \nDG SENSITIVE RCDS RPT-TASK options.\n\n
\nAlerts users when status of SD WAIT LIST types(pcmm,clinic,specialty)\nchange.\n\n
\nContains members to receive IVM HL7 transmissions\n\n
\nThis mail group receives the delinquent patch notices.\n\n
\nThe regular patch monitor user.\n\n
\nThis mail group is for the administration of the SD Wait List \nInter-Facility Transfer function.\n \nWhen an appropriate action has occurred, such as the receipt of a request \nto transfer a patient from a Wait List to this facility, the members \nof this mail group are notified that the action has occurred.\n\n
\nThis mail group is for receiving of PTF 801 screen data to PCE filing \nerror messages. \n\n
\nVDEF processing alerts.\n\n
\nThis Mailgroup will receive a message whenever an error is\nencountered while building an HL7 message for PFSS.\n\n
\nThe purpose of this mail group is to receive any error message generated\nin IBB during processing of charge transaction data. Processing of a\ncharge transaction is initiated by a call from a clinical application\nto CHARGE^IBBAPI.\n \nThis mail group is added to the MAIL GROUP file via patch IB*2.0*286.\nA post-installation routine adds this mail group to the MAIL GROUP FOR\nCHARGE field (#.06) in the PFSS SITE PARAMETERS file (#372).\n\n
\nThis mail group will be used to alert staff of status updates and \nexceptions concerning processes related to the Clinical Logistics Report \nServer. The mail group will be exported with PRC*5.1*83 and the site \nwill determine the members as advised by the Clinical Logistics Office.\n\n
\nThis mail group will receive any error notifications or conditions from \nthe PFSS Event Driver and Scheduling RSA API calls.\n\n
\nThis mail group is for the purpose of receiving problem alerts for TIU. These alerts should be for problems in TIU Notes that are caused by a system bug. It is meant as a management tool - not an alert system for the end user.\n\n
\nThis mail group will receive messages pertaining to erroneous data\ntransmitted to the IVM Center and for data to be uploaded from the IVM\nCenter.\n\n
\nThis mail group will receive the response message when either a scan of \nthe COUNTY CODE(#5.13) and STATE(#5) whenever a manual scan is requested \nby doing from the programmer prompt:\n>D ^XIPMAIL\nor in response to a request of server:\n XIPMAILSERVER[Check file 5.13 & file 5]\n \nper XU*8*449\n\n
\nThis is the mail group that will receive separation notices.\n\n
\nThis mail group is intended to alert Surgery personnel that a Surgery \nRequest Consultation has been entered and does not contain the minimum \nrequired elements to initiate a pre-certification.\n\n
\nThis mail group contains users responsible for DSS extracts. A message is\nsent to this group upon completion of package extracts. \n\n
\nReceive information on PCMM patient and provider inactivation\n\n
\nThis mail group will receive information about activities that need \ninvestigation by site personnel. Examples would be a refill Release \nmessage is sent to Vista by the External Dispense machines, but the refill\nis not on file any longer, possibly was deleted.\n\n
\nThis mail group receives messages related to the Master File Server.\n\n
\nThis mail group will receive the VistA e-mail message that will be \ngenerated by Kernel Server Option: XIPSRVR[Postal Code Update Server]. The\nmessage text will contain the detail records for which Postal Code/ZIP\ncode that were either Added, Edited, or Inactivated in an up arrow\nformat. The first line will be the Header Row.\n \nPER XU*8*449\n\n
\nThis cross-reference identifies the people who should receive \ninformational bulletins concerning the implementation of the Text \nIntegration Utilities (TIU) Package.\n\n
\nMembers of this mail group will automatically receive an email verification entry\nfor each NPI Extract file that has been generated at the sites.\n\n
\nThis mail group is for ASCD (Automated Service Connected Designation)\nsoftware. A breakdown of records reviewed during the nightly process will\nbe sent to this mail group.\n\n
\nThis mail group is forwarded notifications that are associated with\nelectronic Pharmacy (ePharmacy) processing of claims.\n\n
\nThis group receives error messages from the HL7 system when problems \narise sending messages to the Mental Health National database.\n\n
\nThis mail group automatically receives a message when a value is entered\nin the NON-SPACE FILE LOCATION field of the EQUIPMENT INV. (#6914) file. \nThe mail group is intended to have members that can add appropriate\nentries to the ENG SPACE (#6928) file based on the NON-SPACE FILE LOCATION\nvalue.\n\n
\nThis mail group receives messages about assignments of responsibility for \nIT equipment from the Engineering (AEMS/MERS) application. IT staff \nresponsible for managing and monitoring the assignments of responsibility\nshould be members of this group.\n\n
\nThis mail group is used to send reject messages for Home Telehealth \nRegistrations. \n\n
\nINFORMATION RESOURCE MANAGEMENT\n\n
\nMail Group used by the Ambulatory Care Reporting Project to\ntransmit data to the National Patient Care Database via HL7\n\n
\nThis mail group receives mail messages pertaining to and generated by\nthe Surgery Transplant Assessment module.\n\n
\nMembers of this mail group will receive notifications that there are \nActive Duty patients that have been admitted or discharged to your \nfacility. The data needs to be reviewed and marked as ready to transmit \nto the national collecting point. The option to review and mark entries \nis WII REVIEW ADT EVENTS.\n\n
\nThis mail group is used to inform radiology users about issues regarding \nthe HL7 interface between the VistA Radiology/Nuclear Medicine application\nand Commercial Off The Shelf (COTS) applications.\n\n
\nThis mail group will be used to pass information to those individuals \nsupporting the VistA Blood Establishment Computer system (VBECS).\n\n
\nTHIS MAIL GROUP IS USED TO RECEIVE ALERT/ERROR MESSAGES FROM VBECS HL7 \nINTERFACES AND VISTALINK ISSUES.\n\n
\nPATCH XM*999*81 DATED 1/3/95\n\n
\nThis mail group contains staff monitoring compliance to policies for 1358\nMiscellaneous Obligation usage.\n\n
\nThis mail group will receive messages for patients who have been \nscheduled in Recall Reminder, but have a bad address flag set.\n\n
\nThis mail group contains the HBHC Medical Foster Home (MFH) members.\n\n
\nThis mail group contains Event Capture supervisors.\n\n
\nThis mail group will receive information when a CMOP prescription with a\nstatus of Transmitted or Retransmitted is discontinued by a background\nprocess to the Pharmacy Options, e.g. CPRS or Registration packages.\n\n
\nMembers of this mail group will receive various notifications that impact\nEnhanced Order Checks (drug-drug interactions, duplicate therapy and dosing\nchecks) introduced with PRE V. 0.5 utilizing a COTS database.\n\n
\nThis mail group contains the list of users that will received messages \nrelated to the auto-renewal process. The auto-renewal process is \nperformed by the Computerized Patient Record System (CPRS), but is \ninitiated by Outpatient Pharmacy.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nTO RECEIVE TRICARE RX NOT PROCESSED FOR SITE.\n\n
\nThis Mail Group identifies the Clinical Applications Coordinators at the \nfacility.\n\n
\nThis mail group gets FileGrams from the XTERSUM3 routine.\nThese are summary snapshots of the error trap being send to a \nconsolidation site, DOMAIN.EXT for VA sites.\nCould also go to EELS or other places.\n\n
\nThis is the group that should get a copy of the message, when the loading\nof an Error Summary messages gets an error.\n\n
\nThis mail group was added for use in the Police and Security package.\nIt will receive confirmation messages from Q-VAP where the crime\nreports are sent.\n\n
\nThis mail group will receive confirmation mail messages from the Austin\nInformation Technology Center (AITC) postmaster for 1358 transaction\nmessages sent by the IFCAP package to Domain Q-OLP.DOMAIN.EXT. This mail\ngroup supports the interface between IFCAP and the Online Certification\nSystem (PRC*5.1*153).\n\n
\nThis is the mail group that will receive warning bulletins produced by the\nePayments Workload Notification process. Warnings for overdue EFT and ERA\nare sent to this group.\n\n
\nThis is the mail group that will receive bulletins sent by the AR nightly \nprocess. Details of EOB any move or copy transactions from the EDI Lockbox\nmenu option 'EEOB Move/Copy' are included in the bulletin.\n\n
\nTO RECEIVE CHAMPVA RX NOT PROCESSED FOR SITE.\n\n
\nThis is the Medicare Deductible Alert (MDA) queue that will receive all\nthe MDA transmissions from Austin.\n\n
\nPersons in this mail group will receive the Mental Health NO SHOW \nreport that is generated from the scheduling nightly background job.\n\n
\nRecipients of the Outpatient mailman message created when the Date\nof Death is deleted from a patient. This is created if the patient\nhad prescriptions that were discontinued when the Date of Death was\nentered for the patient.\nIf this mail group is not populated (e.g., there are no members),\nthen the message will go to the holders of the PSORPH key.\n\n
\nTHIS MAIL GROUP WILL RECEIVE CONFIRMATION MAIL MESSAGES FROM THE \nAUSTIN INFORMATION TECHNOLOGY CENTER (AITC) POSTMASTER FOR\nGPF DONATIONS RECEIVED THROUGH PAY.GOV.\n\n
\nTHIS MAIL GROUP IS USED TO RECEIVE ALERT/ERROR MESSAGES FROM LRADT HL7 INTERFACES.\n\n
\nExchange mail group that will be notified of Lab exceptions\n\n
\nUsed for sending automated system messages to the recipients when \ncertain fields of monitored files are added and/or modified.\n \nExample: When a NAME field (#.01) of ETIOLOGY FIELD file (#61.2) is \ncreated or modified, an ERT alert is automatically generated\nand members of this mailgroup receive a message containing ERT tracking\ninformation.\n\n
\nReceives confirmation messages from Austin Postmaster for\nmessages sent by the Engineering package (via Generic\nCode Sheet) to Domain Q-FAM.DOMAIN.EXT (Fixed Assets).\n\n
\nThis mail group receives messages from the Fee Basis software when \nThe FBAA BATCH SERVER, FBAA VOUCHER SERVER, and FBAA REJECT SERVER options\nmay send a message to this mail group.\nexceptions occur during processing of messages sent by Central Fee that\nare related to payment batches previously transmitted to Central Fee.\n \nThis mail group was created for finance staff. The messages sent to this \nmail group are also sent to another mail group (FEE). Since the FEE mail\ngroup also receives messages that may not be of interest to finance staff,\nthe seperate FEE FINANCE mail group was created.\n \n\n
\nThis mail group contains the server process email to receive messages \nfrom the IBN DMI queue. Messages are sent to this group for confirmation \nof outbound messages as well as inbound messages.\n\n
\nThis mail group contains the server process email to receive messages \nfrom the IBH DMI queue. Messages are sent to this group for confirmation \nof outbound messages as well as inbound messages.\n\n
\nThis mail group contains the server process email to receive messages \nfrom the IBX DMI queue. Messages are sent to this group for confirmation \nof outbound messages as well as inbound messages.\n\n
\nThis mail group contains the server process email to receive messages \nfrom the IBK DMI queue. Messages are sent to this group for confirmation \nof outbound messages as well as inbound messages.\n\n
\nIf extracted files are not found within the due time, or if after sending the extract files to AITC and confirmation messages are not received within the due time, an Email is sent to this mail group.\n\n
\nMessages are sent to this group for notification of HMS XML file \navailability.\n\n
\nMail group to receive notifications associated with the national High Risk for Suicide Patient Record Flag\n\n
\nThis mail group receives the Hospital Location System Change Management\nextract report generated by the TaskMan option:\nLRJ SYS MAP HL TASKMAN RPT\n \nIt should contain LIMS and COTS Configuration Managers responsible for\nkeeping Hospital Location Rooms and Beds on Vista in synchronization with\nthose defined on a remote Lab configuration run by the VA Medical Center.\n\n
\nThis mail group receives File 60 audit reports generated by TaskMan.\n\n
\nThis mail group receives delimited file extracts from File 60 audits.\n\n
\nAlerts are sent to this mail group when a valid Clinic Order filed in the\nNON-VERIFIED ORDERS (#53.1) file is associated with a location that is \nnot defined in the CLINIC DEFINITION (#53.46) file.\n\n
\nThis mail group is to receive updated Person Class messages from the Master Person Class file from Forum account.\n\n
\nThis mail group will receive error notifications when the background job responsible for transmitting controlled substance prescriptions to the state fails.\n\n
\nThe mail group to receive requests from the FSC or eBusiness Team to \nactivate communication with the NIF, beginning with a batch query to \ncatch the system up to the current state of the NIF.\n\n
\nReport errors in HL7 message generation and processing between VistA GMRC \nConsults and the Healthcare Claims Processing System (HCPS) in Austin.\n\n
\nThis mail group is organized to inform Scheduling users\nwhenever a clinic is inactivated either on the current\ndate or on a future date. If this group is not populated\nwith the corresponding users, or if it is deleted, the\nclinic inactivation messages will error out. The routine\nSDNACT needs this mail group in order to work properly.\n\n
\nThis mail group will receive confirmation mail messages from the\nAustin Information Technology Center (AITC) postmaster for PTF\ntransaction messages sent to the Domain Q-PTI.DOMAIN.EXT.\nThis mail group supports the interface between PTF and the\nAITC.\n\n
\nThe BT Claims Processing mail group is established to provide a\ncentral source of information on Veterans identified during the IVM\nprocess to meet BT administrative eligibility for payment based on income\nthat is determined to be inaccurate. Members of the mail group when\nnotified will review the BT claim database for any payments provided based\non inaccurate income during the identified period.\n\n
\nThis is the mail group that will receive alerts from the eHMP subscription\nprocess if the usage of global ^XTMP reaches the limit allowed and begins \nto pause subscriptions until disk space is available. The mail group also\nalso receives notifications when disk space is available and subscriptions \nare proceeding normally again.\n\n
\nThis mail group will be used to deliver notifications for the IBRFI 277 \nHL7 messages.\n\n
\nThis mail group is used to deliver notifications for Healthcare Services \nReview (HCSR) process.\n\n
\nThis mail group is used to deliver notifications for table/payer update \nHL7 messages.\n\n
\nThis mail group will receive confirmation and reject messages from Austin\nfor Cross Servicing transmissions.\n\n
\nThis TPC mail group will receive confirmation messages\nfrom Austin for Cross Servicing transmissions to the\nQ-TPC.DOMAIN.EXT domain.\n\n
\nThis TPL mail group will receive confirmation messages\nfrom Austin for Cross Servicing transmissions to the\nQ-TPL.DOMAIN.EXT domain.\n\n
\nMail group for DRUG file audits.\n\n
\nThis MAIL GROUP is to receive 2507 Request Reroute information.\n\n
\nThis mail group is used to send messages to the CCRA support team when an \nissue or problem with the GMRC CCRA SEND HL7 Application Parameter \ndetects a problem with sending HL7 messages to the CCRA HealthShare \nserver.\n\n
\nPharmacy Supervisors Group for reporting Narcotic Balance Discrepancies\n\n
\nPharmacy Supervisors Group for end of RX Numbering Alert\n\n
\nThis is the mail group for individuals authorized to approve/reject\nrequests for active national (Cat I) PRF flag ownership transfer.\n\n
\nMembers of this mail group will automatically receive an email from the \nXUSERDIS/XUSERDEAC bulletins for each user that has the DISUSER field \nset to "YES", or is deactivated at the sites.\n\n
\nPSAS GROUP TO RECEIVE ELIGIBILITY REQUEST MESSAGES\n\n
\nPPS MAIL GROUP TO MANAGE PPS DAT downloads and installs.\n\n
\nUsed to transmit changes to the SDEC SETTINGS file (#409.98).\n\n
\nThis Mail Group informs members of any clinical errors arising from IFC messages from Cerner.\n\n
\nThis Mail Group informs members of any non-clinical and non-technical errors arising from IFC messages from Cerner. \n\n
\nThis Mail Group informs members of any technical errors arising from IFC messages from Cerner. \n\n
\nTier II Errors Mail Group\n\n
\nThis Mail Group gets bulletins sent from vendors and filing errors.\n\n
\nThis mail group will receive weekly bulletins generated by the AR nightly \nprocess. The content of the bulletin will be generated from the RCDPE \n1ST PARTY AUTO VS MAN report, the summary version for the previous 7 days.\n\n
\nThis Mail Group is used for the receipt of mail messages that are\ncreated to log the transmission of HL7 messages for Clozapine\npatients.\n\n
\nHL7 MESSAGE ERRORS RECEIVED FROM HSRM.\n\n
\nThis Mail Group will contain the external email addresses for everyone \nwho may need to receive alerts or messages from the Repayment Plan \nNightly Process. Mail sent using this group must not contain any PII \nor PHI.\n\n
\nThis mail group will receive messages when an immunization is running low on\nstock.\n\n
\nThis mail group receives messages concerning charges in the Integrated \nBilling (IB) that would have created a duplicate transaction in Accounts \nReceivable (AR) or charges in IB that were at a higher precedence level \nthan existing charges in AR. The higher precedence level charges in IB \nwere passed over to AR and the existing charges in AR were cancelled.\n \nThe charges listed in these mail messages should be reviewed by the \nappropriate staff to verify that they were properly handled and that no \nadditional charges or corrections need to be made.\n\n
\nMembers of this mail group will receive various notifications that impact\nthe VistA Audit Solution (VAS) Registration application.\n\n
\neMail group to notify designated users via Outlook email of oversized \nstatements waiting to be printed.\n\n
\nThis mail group contains external email addresses for technicians\nwho need to receive alerts about AR repayment plans. Mail sent using this \ngroup must not contain any PII or PHI.\n\n
\nThis mail group contains external email addresses for supervisors who need\nto receive alerts about AR repayment plans. Mail sent using this group\nmust not contain any PII or PHI.\n\n
\n eMail group to notify designated users via Outlook email of exceptions \nencountered when processing Urgent Care push to requesting remote site.\n\n
\nMailGroup used for notification of HL7 error responses from VDIF\nregarding the Means Test Billing Clock syncing process.\n\n
\nThis mail group is used for the transmission of HL7 messages derived from \nthe parameters defined in the EMERGING PATHOGEN file (#69.5) to the \nAustin Automation Center. This mail group will also receive Confirmation \nand Processing Report Messages from Austin.\n\n
\nThis mail group will receive notification whenever a new insurance policy is added.\n\n
\nThis mail group is used to deliver a formatted report taken from the \nHL7 message that is created to assist in the verification of data.\n\n\n
\nThis mail group receives mail messages containing the Quarterly Report for\nSurgical Service, VHA Headquarters. This mail group receives an\nacknowledgment message from the national database when the transmitted\nQuarterly Report is received. Also, this group may receive alerts and\nother mail messages relating to the Quarterly Report.\n\n
\nThis mail group will receive information about updates to NDF.\n\n
\nThis mail group is for the Accounts Receivable bills that are\nreferred to the Regional Counsel Office. The users in this \nmail group should be responsible for the coordination\nof bills referred to RC.\n \nEach RC will have a mailgroup established with the same name.\n\n
\nThis Mail Group contains the names of user to receive messages from\nthe Patient Funds Package.\n\n
\nMail group for pre-registration notifications\n\n
\nThis mail group is used to transmit and receive the interim report.\n\n\n
\nThis mailgroup is used to report billing transactions rejected\nfrom the CHAMPUS fiscal intermediary.\n\n
\nThis mail group will be automatically mailed the IB Unbilled Amounts\nreport each month.\n\n
\nThis mailgroup is used to report cancellation transactions rejected\nfrom the CHAMPUS fiscal intermediary.\n\n
\nThis is used to report when the CHAMPUS billing engines have\nbeen started. It also reports when AWP updates are received.\n\n
\nThis group is used to receive messages from Austin regarding DMC Weekly\nCodesheets.\n\n
\nThis group is used to receive messages from Austin regarding DMC Master\nCodesheets.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis is a list of users who will need to mark a patient's chart that an adverse reaction/allergy was recorded. \n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nThis mail group contains users responsible for DSS extracts.\nA message is sent to this group upon completion of package extracts.\n\n
\nFOR NETWORK MESSAGES\n\n
\nThis mail group is used by the LAB MESSAGING package to notify appropiate Lab\nand IRM staff of conditions affecting LAB MESSAGING that may need corrective\naction.\n\n
\nThis is a complete list of all the verifiers who will need to be sent Drug reaction information.\n\n
\nThis group should contain the Safety Officer(s) for the site. This group\nreceives a message everytime there is an injury or illness reported and\nwhen the supervisor signs off on the 2162.\n\n
\nThis mail group should contain members from Human Resources Management,\nCompensation Specialists, that manage the CA-1 and CA-2 forms. Whenever\nan injury or illness is reported, a message is sent to this mail group.\n\n
\nThis mail group should contain members from Employee Health and Infection\nControl. This group will receive a message whenever there is an incident\ninvolving Exposure to Body Fluids, Needlesticks, or Sharps Exposures.\n\n
\nThis mail group should contain union representatives that monitor the CA-1\nand CA-2 forms. Whenever an injury or illness is reported, a message is\nsent to this mail group.\n\n
\nThis mail group is used by the Surgery Interface ORU receiver routine to\nreport message discrepancies. The discrepancies will include invalid file\nvalues for certain files, as well as invalid text identifiers from the\nSURGERY INTERFACE PARAMETER file (#133.2).\n\n
\nThis mail group is used to transmit HL7 messages to and recieve\nacknowledgement messages from the Austin Automation Center.\n\n
\nThis mail group is used to deliver NCH verification reports. These reports\nare the human readable format taken from the NCH HL7 message that was sent\nto the Austin Automation Center.\n\n
\nThis Mail Group contains users responsible for DSS Extracts in general\nand (specifically) the prosthetics extract.\n\n
\nThis is a complete list of all the verifiers who will need to be sent Food reaction information.\n\n
\nMail group used for transmission of inpatient ADT/R information to the\nNational Patient Care Database.\n \nDO NOT USE THIS MAILGROUP FOR OTHER PURPOSES.\n\n
\nThis mail group will receive confirmation messages from the Q-NPP domain\nlocated at the Austin Automation Center.\n\n
\nThis mail group is used to notify the local site of problems discovered\nduring the upload of enrollment/eligibility data received from HEC. \n\nIt is also used by HEC to communicate directly with the local site\nabout a patient's enrollment and eligibility.\n\n
\nMembers of this mail group will receive a message listing medications\nreinstated when a patient transfer or discharge is deleted.\n\n
\nThis patch creates the PHARMACY PRIME VENDOR mail group. The Prime Vendor\nLine Item Report will be sent to this mail group from the Austin\nAutomation Center twice per week.\n\n
\nThis mail group is being used by Mental Health to transmit data to the National\nPatient Care Database via HL7.\n\n
\nThis mail group will receive a message when a GAF score is transmitted to the\nNational Patient Care Database or an error in the transmission has occurred.\n\n
\nThis mail group will receive messages for all Capacity Management packages\n(SAGG, RUM).\n\n
\nThis is a mail group that will receive messages from Prosthetics Inventory\nSystem.\n\n