Files > EVENT

parent
366.14
name
EVENT
number
366.141
Fields
#NameLocationTypeDetailsIndexDescription
.01event type(+)0;1SET OF CODES0:UNKNOWN
1:BILLABLE STATUS CHECK
2:SUBMIT
3:BILL
4:RELEASE
5:REVERSE
6:CLOSE
7:REOPEN
BThe event types represent the various ePharmacy billing events during the processing of outpatient Rx claims.
.03patient0;3POINTER2DPATIENT on the Rx claim
.04job0;4NUMERICThe job number of the job currently executing
.05time0;5DATE-TIMEDate and time of the event
.06epharmacy user0;6POINTER200USystem user who triggered the e-pharmacy event. This can be the system user who enters prescription or makes billing operation on e-pharmacy claims. It also can be POSTMASTER if the operation (like claims auto-reversal process) was performed by a background job.
.07result0;7NUMERICResult of the event processing - return code
.08result message0;8FREE TEXTResult of the event processing - message
.09e-pharmacy division0;9POINTER9002313.56E-Pharmacy division (BPS PHARMACY).
.11auth #1;1FREE TEXTECME approval/authorization number
.12bcid1;2FREE TEXTThis field contains the Prescription/Service Reference Number (also known as the ECME#) and the Date of Service separated by a semi-colon.
.13claimid1;3FREE TEXTThis is a 7 or 12 digit ECME number with leading zero(s).
.14patient in ibd1;4POINTER2PATIENT identifier passed in IBD ARRAY when outside application calls $$STORESP^IBNCPDP (IA #4299)
.15medical center division1;5POINTER40.8Division identifier
.16response1;6FREE TEXTResponse from the payer: ACCEPTED PAYABLE REJECTED DUPLICATE
.17reversal reason1;7FREE TEXTReversal reason
.18rts-del1;8NUMERICReturn to Stock-Delete status
.19status1;9FREE TEXTBill status - one of the following values: "PAID","REJECTED","REVERSED", "CLOSED", "RELEASED", or "SUBMITTED"
.201prescription2;1POINTER52IPointer TO PRESCRIPTION FILE (#52) as passed into $$STORESP^ IBNCPDP (IA # 4299) in "PRESCRIPTION" node
.202rx no2;2FREE TEXTRRX Number from file #52 passed into $$STORESP^IBNCPDP (IA # 4299) in the "RX NO" node
.203fill number2;3NUMERICRefill # 0 - for original refill 1...n - for other refills
.204drug2;4FREE TEXTPrescription Drug on the claim
.205ndc2;5FREE TEXTNational Drug Code number
.206date of service2;6DATE-TIMEDate of Service of the outpatient pharmacy Rx.
.207release date2;7DATE-TIMEThis is the date the Rx was released. This field is populated only if the Rx was released.
.208qty2;8NUMERICThis is the prescription billed quantity. This may be different than the NCPDP quantity.
.209days supply2;9NUMERICRX Days Supply
.21dea2;10FREE TEXTDrug Enforcement Agency number
.211filled by2;11POINTER200Person, who filled the RX refill.
.212rx #2;12POINTER52IPointer TO PRESCRIPTION FILE (#52) as passed into $$RX^IBNCPDP (IA # 4299) in "IEN" node
.213billing units2;13FREE TEXTThis is the type of billing units associated with the billing quantity. Examples include "TAB", "CAP", "EA", "ML", "VI", "GM", and so forth.
.214ncpdp qty2;14NUMERICThis is the NCPDP Quantity for the prescription. This may be different than the billed quantity.
.215ncpdp units2;15FREE TEXTThis is the NCPDP standard for unit type: EA - each ML - milliliters GM - grams This is the type of unit associated with the NCPDP quantity.
.301bill3;1POINTER399IB bill
.302billed3;2NUMERICAmount billed to the insurance
.303plan3;3POINTER355.3Group insurance plan
.304cost3;4NUMERICCost - dollar amount per Dispensed Unit
.305paid by insurance3;5NUMERICAmount paid by the Insurance
.306close/reopen comment3;6FREE TEXTClose or reopen comment
.307close reason3;7POINTER356.8Close reason
.308drop to paper3;8NUMERICDrop to Paper flag.
.309release copay3;9NUMERICRelease Copay flag.
.31ecme user in ibd3;10POINTER200System user who triggered the ECME event and whose identifier was passed in IBD ARRAY when outside application calls $$STORESP^IBNCPDP (IA #4299). This can be the system user who enters prescription or makes billing operation on e-pharmacy claims. It also can be POSTMASTER if the operation (like claims auto-reversal process) was performed by a background job.
.311copay amount3;11NUMERICThis is to store the copayment amount specified by the payer for amounts that are to be charge for non-Veteran copayment charges such as TRICARE or CHAMPVA.
.312ingredient cost paid3;12NUMERICThis is the amount of the ingredient cost paid as reported by the payer.
.313dispensing fee paid3;13NUMERICThis is the amount of the dispensing fee paid as reported by the payer.
.314patient responsibility (ins)3;14NUMERICThis is the amount for which the patient is responsible as reported by the payer.
.401ao4;1SET OF CODES0:NO
1:YES
2:NO ANSWER
3:OVERRIDDEN
Agent Orange indicator
.402cv4;2SET OF CODES0:NO
1:YES
2:NO ANSWER
3:OVERRIDDEN
Combat Veteran indicator
.403swa4;3SET OF CODES0:NO
1:YES
2:NO ANSWER
3:OVERRIDDEN
Southwest Asia indicator.
.404ir4;4SET OF CODES0:NO
1:YES
2:NO ANSWER
3:OVERRIDDEN
Ionizing radiation exposure indicator
.405mst4;5SET OF CODES0:NO
1:YES
2:NO ANSWER
3:OVERRIDDEN
Military Sexual trauma indicator
.406hnc4;6SET OF CODES0:NO
1:YES
2:NO ANSWER
3:OVERRIDDEN
Head/neck cancer indicator
.407sc4;7SET OF CODES0:NO
1:YES
2:NO ANSWER
3:OVERRIDDEN
Service Connected indicator
.408shad4;8SET OF CODES0:NO
1:YES
2:NO ANSWER
3:OVERRIDDEN
Project 112/SHAD indicator
2insurance5;0MULTIPLE366.1412Insurance data
7.01rx cob7;1SET OF CODES0:UNKNOWN
1:PRIMARY
2:SECONDARY
The Coordination Of Benefits (COB) indicator designates the payer sequence for the claim.
7.02primary bill7;2POINTER399This field will hold the Primary bill associated with the original prescription/refill related to this claim.
7.03prior payment7;3NUMERICThis field will store a prior payment amount that the primary insurer agreed to pay for the original prescription/refill related to this claim.
7.04rate type selected by user7;4POINTER399.3This is the Rate Type selected by the user for ECME Pharmacy billing purposes. Users may select the rate type in the option "Process Secondary/TRICARE Rx to ECME" [BPS COB PROCESS SECOND TRICARE].
7.05eligibility7;5SET OF CODESV:VETERAN
T:TRICARE
C:CHAMPVA
This is the patient's eligibility as determined by IB billing determination during the finish event.

Error: Invalid Global File Type: 366.141