Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Routine: IBCNEMS1

IBCNEMS1.m

Go to the documentation of this file. 
  1. IBCNEMS1 ;AITC/DM - Consolidated Mailman messages; 12-JUNE-2018
  1.  ;;2.0;INTEGRATED BILLING;**621,631,659,752**;21-MAR-94;Build 20
  1.  ;;Per VA Directive 6402, this routine should not be modified.
  1.  ;
  1.  ; 
  1.  ; These routines are being consolidated in one area for ease in maintenance 
  1.  ; The calling routine is responsible for setting the target MAILGROUP, Subject text 
  1.  ; and finally calling MSG^IBCNEUT5(...) to send the actual Mailman message
  1.  ; 
  1. MSG001(MSG,EXNAME) ; error msg for $$SDAPI^SDAMA301 appointment api issue from an extract 
  1.  ; MSG is the global that will be populated with message text.
  1.  ; EXNAME is the extract that had the issue (e.g. "EICD") 
  1.  ; It is assumed that ^TMP($J,"SDAMA301") has been populated by the failed call
  1.  ;
  1.  N IBMSG,IBII
  1.  S MSG(1)="On "_$$FMTE^XLFDT(DT)_" the "_EXNAME_" Extract for eIV encountered"
  1.  S MSG(2)="one or more errors while attempting to get Appointment data"
  1.  S MSG(3)="from the scheduling package."
  1.  S MSG(4)=""
  1.  S MSG(5)="Error(s) encountered: "
  1.  S MSG(6)=""
  1.  S MSG(7)="  Error Code   Error Message"
  1.  S MSG(8)="  ----------   -------------"
  1.  S IBMSG=8,IBII=0
  1.  F  S IBII=$O(^TMP($J,"SDAMA301",IBII)) Q:IBII=""  S IBMSG=IBMSG+1,MSG(IBMSG)="  "_$$LJ^XLFSTR(IBII,13)_$G(^TMP($J,"SDAMA301",IBII))
  1.  S IBMSG=IBMSG+1,MSG(IBMSG)=""
  1.  S IBMSG=IBMSG+1,MSG(IBMSG)="As a result of this error the extract was not done.  The extract"
  1.  S IBMSG=IBMSG+1,MSG(IBMSG)="will be attempted again the next night automatically.  If you"
  1.  S IBMSG=IBMSG+1,MSG(IBMSG)="continue to receive error messages you should contact your IRM"
  1.  S IBMSG=IBMSG+1,MSG(IBMSG)="and possibly call the Help Desk for assistance."
  1.  ;
  1.  Q
  1.  ;
  1. MSG002(MSG,ERRGB,TQ) ; error msg when writing to EIV EICD TRACKING (#365.18) from IBCNEDE4
  1.  ; MSG is the global that will be populated with message text.
  1.  ; ERRBG is the ERROR global that was passed to a Fileman ^DIE call
  1.  ; TQ IEN of the associated IIV Transmission Queue
  1.  ; The user should verify that there is an existing error before making this call  
  1.  ; Set to IB site parameter MAILGROUP
  1.  ;
  1.  S MSG(1)="Tried to create an entry in the EIV EICD TRACKING file #365.18"
  1.  S MSG(2)="without success."
  1.  S MSG(3)=""
  1.  S MSG(4)="Error encountered: "_$G(ERRGB("DIERR",1,"TEXT",1))
  1.  S MSG(5)=""
  1.  S MSG(6)="The associated IIV Transmission Queue IEN: "_TQ
  1.  S MSG(7)=""
  1.  S MSG(8)="If you continue to receive this error message, you should contact"
  1.  S MSG(9)="your IRM and possibly call the Help Desk for assistance."
  1.  Q
  1.  ;
  1. MSG003(MSG,ERRGB,TQN,RESP,BUFF) ;  Create and send a response processing error warning message
  1.  ; Output Variables
  1.  ; ERFLG=1
  1.  ;
  1.  S MSG(1)="Tried to create an entry in the CREATION TO PROCESSING TRACKING file #355.36"
  1.  S MSG(2)="without success."
  1.  S MSG(3)=""
  1.  S MSG(4)="Error encountered: "_$G(ERRGB("DIERR",1,"TEXT",1))
  1.  S MSG(5)=""
  1.  S MSG(6)="The associated IIV Transmission Queue IEN: "_$G(TQN)
  1.  S MSG(7)="The associated IIV Repsonse IEN: "_$G(RESP)
  1.  S MSG(8)="The associated INSURANCE VERIFICATION PROCESSOR IEN: "_$G(BUFF)
  1.  S MSG(9)=""
  1.  S MSG(10)="If you continue to receive this error message, you should contact"
  1.  S MSG(11)="your IRM and possibly call the Help Desk for assistance."
  1.  Q
  1.  ;
  1.  ;/vd-IB*2*659 - The following module of code was added.
  1. MSG004(MSG,SITE) ;  Create a message that the IIV EC logical link is stuck/down.
  1.  ;
  1.  S MSG(1)="Check of IIV EC Logical Link: No activity seen in link"
  1.  S MSG(2)="for site: "_SITE_"."
  1.  S MSG(3)="The IIV EC logical link needs to be bounced or turned on."
  1.  Q
  1.  ;
  1.  ;IB*752/CKB - Notify FSC when a new code was learned ON THE FLY
  1. MSG005(IBMSG) ; Create a message providing FSC with the following info:
  1.  ; file # ^ site # ^ code being added ^ associated trace #
  1.  ;
  1.  S MSG(1)="A new X12 code was added on the fly. Contact the Payer to"
  1.  S MSG(2)="determine if it is a valid code. If it is a valid code, add it"
  1.  S MSG(3)="to the appropriate table in FSC with the proper description so"
  1.  S MSG(4)="all sites get this new code. If it is an invalid code, please"
  1.  S MSG(5)="advise the payer so they do not send it again in the future."
  1.  S MSG(6)=""
  1.  S MSG(7)="      Site Number: "_$P(IBMSG,U,2)
  1.  S MSG(8)="VistA File Number: "_$P(IBMSG,U)
  1.  S MSG(9)="   New Code Added: "_$P(IBMSG,U,3)
  1.  S MSG(10)="     Trace Number: "_$P(IBMSG,U,4)
  1.  S MSG(11)=" "
  1.  Q