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