No my fingers didn't slip, but I didn't copy everything from my original email. Here is the last of the paragraph.
I am, also, going to have a similar problem with the 270/271 and 278, but I noticed in these transaction sets the BHT03 is used. Would it be reasonable to use this data element to put the originating business unit in the 270 and 278 request, if I do will the trading partner send back my information in the 271 and 278 response or will they put their own information? We do put the location and client number in the TRN02 data element, we have added the business unit code, but I was hoping we could do this in upper level loop, so we wouldn't have to parse it out by subscriber. Our problem is that we have one server and each business unit has its own database, so we need to know where the information from the file needs to be loaded and our trading partner is telling me I can't have a Trading Partner for each of my business units. Thanks, Jean Gidcumb HIPAA Project Manager Almost Family, Inc -----Original Message----- From: William J. Kammerer [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2003 11:27 AM To: WEDI SNIP Transactions Workgroup List Subject: Re: 276/277 BHT Reference Identification Jean, can't you just use the Claim Submitter Trace Number in the 2000D Subscriber Level loop in the 276? The submitter (you, I presume) gets to pick the arbitrary "cookie" to be placed in TRN02 - which the receiver (the payer) is obliged to return, verbatim, in the Subscriber Level loop within the 277. "but I...."?? Did your fingers just slip? William J. Kammerer Novannet, LLC. Columbus, US-OH 43221-3859 +1 (614) 487-0320 ----- Original Message ----- From: "Jean Gidcumb" <[EMAIL PROTECTED]> To: "WEDI SNIP Transactions Workgroup List" <[EMAIL PROTECTED]> Sent: Wednesday, 02 April, 2003 09:04 AM Subject: 276/277 BHT Reference Identification Hi, We are trying to setup a way to identify which business unit a particular claim status transaction set needs to be sent when we receive the response from our Trading Partner. I am looking at the BHT segment data element BHT03. It seemed like this would be the place to put the Originating business unit information. The problem is that in the 276 the data element is not used, but in the 277 the data element is used. Also, in the 277 it is a required data element. Does anyone know why they did it this way and if it will change in future versions? I am, also, going to have a similar problem with the 270/271 and 278, but I Jean Gidcumb HIPAA Project Manager Almost Family, Inc --- The WEDI SNIP listserv to which you are subscribed is not moderated. The discussions on this listserv therefore represent the views of the individual participants, and do not necessarily represent the views of the WEDI Board of Directors nor WEDI SNIP. If you wish to receive an official opinion, post your question to the WEDI SNIP Issues Database at http://snip.wedi.org/tracking/. These listservs should not be used for commercial marketing purposes or discussion of specific vendor products and services. They also are not intended to be used as a forum for personal disagreements or unprofessional communication at any time. You are currently subscribed to wedi-transactions as: [EMAIL PROTECTED] To unsubscribe from this list, go to the Subscribe/Unsubscribe form at http://subscribe.wedi.org or send a blank email to [EMAIL PROTECTED] If you need to unsubscribe but your current email address is not the same as the address subscribed to the list, please use the Subscribe/Unsubscribe form at http://subscribe.wedi.org --- The WEDI SNIP listserv to which you are subscribed is not moderated. The discussions on this listserv therefore represent the views of the individual participants, and do not necessarily represent the views of the WEDI Board of Directors nor WEDI SNIP. If you wish to receive an official opinion, post your question to the WEDI SNIP Issues Database at http://snip.wedi.org/tracking/. These listservs should not be used for commercial marketing purposes or discussion of specific vendor products and services. They also are not intended to be used as a forum for personal disagreements or unprofessional communication at any time. You are currently subscribed to wedi-transactions as: [EMAIL PROTECTED] To unsubscribe from this list, go to the Subscribe/Unsubscribe form at http://subscribe.wedi.org or send a blank email to [EMAIL PROTECTED] If you need to unsubscribe but your current email address is not the same as the address subscribed to the list, please use the Subscribe/Unsubscribe form at http://subscribe.wedi.org
